Changes between Version 34 and Version 35 of PHAL-OE_Concept

Timestamp:

01/29/09 22:33:58 (16 years ago)

Author:

antoni (IP: 77.210.149.0)

Comment:

--

PHAL-OE_Concept

@@ -7 +7 @@
 One of the most relevant objectives in the process of defining a common framework to develop and deploy software radio applications is to eliminate platform (hardware and support software) dependencies. On the other hand, radio applications are built through a set of software modules (hardware or software based) that communicates among them. The common used terms denominates such modules as “objects”. Therefore each one of such objects are signal processing blocks, some of them with important requirements in terms of computing resources, that needs to acquire/deliver information from/to other objects through proper interfaces. Nevertheless, one of the most relevant assumptions of PHAL-OE is that such interfaces between objects are unknown at object development time. Only at execution time all the required objects will be integrated and the entire radio application will be built.
 
-[[Image(ALOEV0.png, 400px, align=right)]] 
-
 All these objectives have pushed us to define and develop a multi-platform software abstraction layer and execution environment, ALOE (Abstraction Layer & Operating Environment), capable to provide such features. The list of the main functionalities where the PHAL-OE must provide support on includes:
 
@@ -16 +14 @@
 
 •       Hide the platform heterogeneity to the radio application. Abstraction layers are required are basic mechanisms to provide such feature.
-
+[[Image(ALOEV0.png, 400px, align=right)]] 
 •       Computing resource management. Under a scenario with limited computing resources the need of a specific mechanism to manage the available resources promotes the efficiency in the whole system and extends its interactions with the radio resources management part. In addition it is capable to assure the overcoming of the real-time constraints.