The scope of the present document is to define an information model and protocol for unified radio application interface
for mobile device reconfiguration. The work is based on the Use Cases defined in ETSI TR 102 944 [i.1], on the system
requirements defined in ETSI EN 302 969 [1] and on the radio reconfiguration related architecture for mobile devices
defined in ETSI EN 303 095 [i.2] and on the mobile device information models and protocols related Multiradio
Interface defined ETSI EN 303 146-1 [i.3].

Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in protokoli za mobilne naprave (MD) - 3. del: Enotni radijski aplikacijski vmesnik (URAI)

Področje uporabe tega dokumenta opredeljuje informacijski model in protokol za enotni radijski aplikacijski vmesnik za preoblikovanje mobilnih naprav. Delo temelji na primerih uporabe iz dokumenta ETSI TR 102 944 [i.1], sistemskih zahtevah iz dokumenta ETSI EN 302 969 [1] in preoblikovanju radia glede na arhitekturo za mobilne naprave iz dokumenta ETSI EN 303 095 [i.2] ter na informacijskih modelih in protokolih za mobilne naprave, ki se nanašajo na večradijski vmesnik iz dokumenta ETSI EN 303 146-1 [i.3].

General Information

Status
Published
Public Enquiry End Date
31-May-2018
Publication Date
08-Jul-2018
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
18-Jun-2018
Due Date
23-Aug-2018
Completion Date
09-Jul-2018

Buy Standard

Standard
SIST EN 303 146-3 V1.3.1:2018
English language
33 pages
sale - 10%
Preview
sale - 10%
Preview

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN 303 146-3 V1.3.1:2018
01-september-2018
Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in
protokoli za mobilne naprave (MD) - 3. del: Enotni radijski aplikacijski vmesnik
(URAI)
Reconfigurable Radio Systems (RRS) - Mobile Device (MD) information models and
protocols - Part 3: Unified Radio Application Interface (URAI)
Ta slovenski standard je istoveten z: ETSI EN 303 146-3 V1.3.1 (2018-06)
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
SIST EN 303 146-3 V1.3.1:2018 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN 303 146-3 V1.3.1:2018
---------------------- Page: 2 ----------------------
SIST EN 303 146-3 V1.3.1:2018
ETSI EN 303 146-3 V1.3.1 (2018-06)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Mobile Device (MD) information models and protocols;
Part 3: Unified Radio Application Interface (URAI)
---------------------- Page: 3 ----------------------
SIST EN 303 146-3 V1.3.1:2018
2 ETSI EN 303 146-3 V1.3.1 (2018-06)
Reference
REN/RRS-0219
Keywords
interface, mobile, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or

print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the

print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx

If you find errors in the present document, please send your comment to one of the following services:

https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

and microfilm except as authorized by written permission of ETSI.

The content of the PDF version shall not be modified without the written authorization of ETSI.

The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM

DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

TM TM

3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and

of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 4 ----------------------
SIST EN 303 146-3 V1.3.1:2018
3 ETSI EN 303 146-3 V1.3.1 (2018-06)
Contents

Intellectual Property Rights ................................................................................................................................ 4

Foreword ............................................................................................................................................................. 4

Modal verbs terminology .................................................................................................................................... 4

1 Scope ........................................................................................................................................................ 5

2 References ................................................................................................................................................ 5

2.1 Normative references ......................................................................................................................................... 5

2.2 Informative references ........................................................................................................................................ 5

3 Definitions and abbreviations ................................................................................................................... 6

3.1 Definitions .......................................................................................................................................................... 6

3.2 Abbreviations ..................................................................................................................................................... 6

4 Introduction .............................................................................................................................................. 7

5 System Identification ................................................................................................................................ 9

5.1 Radio Computer Structure .................................................................................................................................. 9

5.2 URAI System Requirement Mapping............................................................................................................... 10

6 Notational Tools ..................................................................................................................................... 11

6.1 Notational Tool for Information Model Classes ............................................................................................... 11

6.2 Notational Tool for Interface Classes ............................................................................................................... 12

7 Information Model for Radio Computer ................................................................................................ 13

7.1 Radio Computer ............................................................................................................................................... 13

7.2 Class Definitions for Information Model ......................................................................................................... 16

8 Interface Definition ................................................................................................................................ 23

8.1 Interface Overview ........................................................................................................................................... 23

8.2 Radio Application Management Services ........................................................................................................ 24

8.2.1 Overview on Radio Application Management Services ............................................................................. 24

8.2.2 Messages for Radio Application Management Services ............................................................................. 25

8.3 User Data Flow Services .................................................................................................................................. 25

8.3.1 Overview on User Data Flow Services ....................................................................................................... 25

8.3.2 Messages for User Data Flow Services ....................................................................................................... 25

8.4 Multiradio Control Services ............................................................................................................................. 26

8.4.1 Overview on Multiradio Control Services .................................................................................................. 26

8.4.2 Messages for Multiradio Control Services .................................................................................................. 26

8.5 Class Definitions for Interface .......................................................................................................................... 27

Annex A (informative): Abstract Data Definitions .............................................................................. 28

Annex B (informative): URAI Qualification Methods for Validation ............................................... 32

History .............................................................................................................................................................. 33

ETSI
---------------------- Page: 5 ----------------------
SIST EN 303 146-3 V1.3.1:2018
4 ETSI EN 303 146-3 V1.3.1 (2018-06)
Intellectual Property Rights
Essential patents

IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

server (https://ipr.etsi.org/).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

server) which are, or may be, or may become, essential to the present document.
Trademarks

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.

ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no

right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does

not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

Foreword

This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).

The present document is part 3 of a multi-part deliverable covering the Mobile Device (MD) information models and

protocols, as identified below:
Part 1: "Multiradio Interface (MURI)";
Part 2: "Reconfigurable Radio Frequency Interface (RRFI)";
Part 3: "Unified Radio Application Interface (URAI)";
Part 4: "Radio Programming Interface (RPI)".
National transposition dates
Date of adoption of this EN: 11 June 2018
Date of latest announcement of this EN (doa): 30 September 2018
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 2019
Date of withdrawal of any conflicting National Standard (dow): 31 March 2019
Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and

"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of

provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
---------------------- Page: 6 ----------------------
SIST EN 303 146-3 V1.3.1:2018
5 ETSI EN 303 146-3 V1.3.1 (2018-06)
1 Scope

The scope of the present document is to define an information model and protocol for unified radio application interface

for mobile device reconfiguration. The work is based on the Use Cases defined in ETSI TR 102 944 [i.1], on the system

requirements defined in ETSI EN 302 969 [1] and on the radio reconfiguration related architecture for mobile devices

defined in ETSI EN 303 095 [i.2] and on the mobile device information models and protocols related Multiradio

Interface defined ETSI EN 303 146-1 [i.3].
2 References
2.1 Normative references

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the

referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found at

https://docbox.etsi.org/Reference/.

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

their long term validity.

The following referenced documents are necessary for the application of the present document.

[1] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related

requirements for Mobile Devices".
2.2 Informative references

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the

referenced document (including any amendments) applies.

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

their long term validity.

The following referenced documents are not necessary for the application of the present document but they assist the

user with regard to a particular subject area.

[i.1] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for

Unified Radio Applications of Mobile Device".

[i.2] ETSI EN 303 095: "Reconfigurable Radio Systems (RRS); Radio reconfiguration related

architecture for Mobile Devices (MD)".

[i.3] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device Information Models

and Protocols; Part 1: Multiradio Interface (MURI)".

[i.4] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device (MD) information

models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".

[i.5] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software

Defined Radio (SDR) Mobile Device Architecture and Services".

[i.6] IEEE 1900.4-2009™: "IEEE Standard for Architectural Building Blocks Enabling Network-

Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous

Wireless Access Networks".

[i.7] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One

(ASN.1): Specification of basic notation".
ETSI
---------------------- Page: 7 ----------------------
SIST EN 303 146-3 V1.3.1:2018
6 ETSI EN 303 146-3 V1.3.1 (2018-06)
3 Definitions and abbreviations
3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

association: logical communication link to a Radio Access Network or a peer equipment

NOTE 1: Typically, some control signalling is necessary to maintain the association. No user data transfer may

occur with only an association present, but a data flow may be established into an association for this

purpose.

NOTE 2: Peer equipment is any communication counterpart of a reconfigurable mobile device. It can be reached by

establishing a logical communication link (i.e. an association) between the reconfigurable mobile device

and peer equipment.

channel: designated part of the information transfer capability having specified characteristics, provided at the user

network interface

NOTE: It is the over-the-air wireless propagation channel which is used to convey an information signal from

transmitter to receiver. This definition is specified in ETSI EN 303 095 [i.2].

communication services layer: layer related to communication services supporting generic applications

NOTE: A communication services layer supports generic applications like Internet access. In the present

document, it consists of Administrator, Mobility Policy Manager (MPM), Networking stack and Monitor.

link: connection from one location to another through a given Radio Access Technology for the purpose of transmitting

and receiving digital information

Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the

receive RF signals

NOTE 1: The Software is executed on a particular radio platform or an RVM as part of the radio platform.

NOTE 2: RAs might have different forms of representation. They are represented as:

 source codes including Radio Library calls of Radio Library native implementation and Radio HAL

calls;

 IRs including Radio Library calls of Radio Library native implementation and radio HAL calls;

 Executable codes for a particular radio platform.

radio computer: part of mobile device hardware working under ROS control and on which RAs are executed

NOTE: A Radio Computer typically includes programmable processors, hardware accelerators, peripherals, etc.

RF part is considered to be part of peripherals.

Radio Control Framework (RCF): control framework which, as a part of the OS, extends OS capabilities in terms of

radio resource management

NOTE: RCF is a control framework which consists of Configuration Manager (CM), Radio Connection Manager

(RCM), Flow Controller (FC) and Multiradio Controller (MRC). The Resource Manager (RM) is

typically part of OS.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASN Abstract Syntax Notation
ASN.1 Abstract Syntax Notation One
BLER BLock Error Rate
ETSI
---------------------- Page: 8 ----------------------
SIST EN 303 146-3 V1.3.1:2018
7 ETSI EN 303 146-3 V1.3.1 (2018-06)
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
ID IDentification
MD Mobile Device
MPM Mobility Policy Manager
MRC MultiRadio Controller
MURI MUltiRadio Interface
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RCF Radio Control Framework
RCID Radio Computer IDentification
RCM Radio Connection Manager
RF Radio Frequency
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RX Receiver
SINR Signal to Interference plus Noise Ratio
TX Transmitter
UML Unified Modelling Language
URA Unified Radio Applications
URAI Unified Radio Application Interface
4 Introduction

A reconfigurable MD is capable of running multiple radios simultaneously and of changing the set of radios by loading

new Radio Application Package (RAP). All Radio Applications (RAs) are called Unified Radio Applications (URAs)

when they exhibit a common behaviour from the reconfigurable MD's point of view [i.2]. In order to run multiple

URAs, the reconfigurable MD will include Communication Services Layer (CSL), Radio Control Framework (RCF),

Radio Platform and 4 sets of interfaces for their interconnection.
ETSI
---------------------- Page: 9 ----------------------
SIST EN 303 146-3 V1.3.1:2018
8 ETSI EN 303 146-3 V1.3.1 (2018-06)
Figure 4.1: Four sets of interfaces for Reconfigurable MD

Figure 4.1 illustrates the Reconfigurable MD architecture with the 4 sets of interfaces, i.e.:

• MURI for interfacing CSL and RCF [i.3];
• RRFI for interfacing URA and RF Transceiver [i.4];
• URAI for interfacing URA and RCF which is the scope of the present document;
• RPI for allowing an independent and uniform production of RAs [i.5].
The present document defines URAI.
ETSI
---------------------- Page: 10 ----------------------
SIST EN 303 146-3 V1.3.1:2018
9 ETSI EN 303 146-3 V1.3.1 (2018-06)
<>
IMUR I
<>
IRR F I
RadioComput er
<>
IRPI
<>
IUR AI
Figure 4.2: UML class diagram for Radio Computer interfaces

Figure 4.2 illustrates UML class diagram for Radio Computer interfaces. The reconfigurable MD may be seen as a

Radio Computer where individual URAs are engineered as software entities [i.2].
The present document is organized as follows:
• clause 5 describes the system identification;

• clause 6 describes the notational tool for defining both information model classes and interface classes;

• clause 7 describes the information model for radio computer; and
• clause 8 describes the interface definition.

While UML is used for defining the information model and protocol related to URAI, other modelling languages could

be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how RCF and URA interact with each other using URAI.
ETSI
---------------------- Page: 11 ----------------------
SIST EN 303 146-3 V1.3.1:2018
10 ETSI EN 303 146-3 V1.3.1 (2018-06)
Figure 5.1: Interconnection between RCF and URA using URAI for Reconfigurable MD
As shown in figure 5.1, URAI supports 3 kinds of services:
• Radio Application Management Services

These services are used by Radio Connection Manager (RCM) which is included in the RCF, to control URA functions

such as reporting of discovered Peer Equipments, creating/terminating association with Peer Equipment,

starting/stopping communication with Peer Equipment, etc.
• User Data Flow Services

These services are used by Flow Controller (FC) which is included in the RCF, to transmit user data to URA, or used by

URA to transmit received user data to FC. These services also include management of data flow, which is provided by

FC.
• Multiradio Control Services

These services are used by Multiradio Controller (MRC) which is included in RCF, to manage spectral resource usage.

The RCF and URA are defined in ETSI EN 303 095 [i.2].
5.2 URAI System Requirement Mapping

The Radio Computer components above described shall support the URAI system requirements shown in table 5.1 and

described in clause 6 of ETSI EN 302 969 [1].
ETSI
---------------------- Page: 12 ----------------------
SIST EN 303 146-3 V1.3.1:2018
11 ETSI EN 303 146-3 V1.3.1 (2018-06)
Table 5.1: Mapping of Radio Computer Components to
the system requirements described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Flow Controller R-FUNC-RAT-05 The requirement is described in clause 6.1.5 of
ETSI EN 302 969 [1].
R-FUNC-RA-04 The requirement is described in clause 6.2.4 of
ETSI EN 302 969 [1].

Multiradio Controller R-FUNC-RAT-01 The requirement is described in clause 6.1.1 of

ETSI EN 302 969 [1].
R-FUNC-RAT-02 The requirement is described in clause 6.1.2 of
ETSI EN 302 969 [1].
R-FUNC-RAT-03 The requirement is described in clause 6.1.3 of
ETSI EN 302 969 [1].
R-FUNC-RAT-06 The requirement is described in clause 6.1.6 of
ETSI EN 302 969 [1].
R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of
ETSI EN 302 969 [1].

Radio Connection Manager R-FUNC-RAT-04 The requirement is described in clause 6.1.4 of

ETSI EN 302 969 [1].
R-FUNC-RAT-05 The requirement is described in clause 6.1.5 of
ETSI EN 302 969 [1].
R-FUNC-RAT-06 The requirement is described in clause 6.1.6 of
ETSI EN 302 969 [1].
R-FUNC-RA-03 The requirement is described in clause 6.2.3 of
ETSI EN 302 969 [1].
R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of
ETSI EN 302 969 [1].
6 Notational Tools
6.1 Notational Tool for Information Model Classes

Table 6.1 shows a template for defining information model classes [i.6]. Each information model class is defined in

clause 7.2 in accordance with the template shown in table 6.1.

NOTE: ASN.1 is used throughout the present document for abstract type definitions; however, alternative ways

are possible and are not excluded.
ETSI
---------------------- Page: 13 ----------------------
SIST EN 303 146-3 V1.3.1:2018
12 ETSI EN 303 146-3 V1.3.1 (2018-06)
Table 6.1: Template for defining Information Model Classes
Class[(abstract class)]

DERIVED FROM
ATTRIBUTES
Possible access:
Value type: Default value:
[]
qualifier>

CONTAINED IN

class is an abstract class, that is, it is used for further refinement only and will

never be instantiated, then this list is empty.>
class. Constraints used are:
• [*] - zero or more instances,
CONTAINS
• [+] - one or more instances,
• [] - exactly n instances,
• [ - ] - not less than m and not more than n instances.>
SUPPORTED
EVENTS
corresponding event report.>
Further details on the template in table 6.1 are given below.

• is the name of the Class as it appears in the corresponding model. Additional information is also

included in case the class in question has been specified as an abstract one.

• DERIVED FROM field identifies the super class of the class in case of sub-classing.

• ATTRIBUTES field describes the attributes that have been defined in the class. More specifically:

- identifies the name of an attribute, as it is included in the class definition.

- holds the type of the attribute specified in Abstract Syntax Notation One

(ASN.1). Details related to the ASN.1 module are specified in annex A.

- provides information about the level of accessibility of the attribute. This

may include: 'Read', 'Write', 'Read-Write', 'Add-Remove' (for list-type attributes), 'Read-Add-Remove',

and 'None' (for internal access only).

• CONTAINED IN field includes a list of classes whose instances may contain an instance of this class;

containment is a strong aggregation relationship, that is, a contained instance is for its lifetime bound to its

container object and it is contained only in this one container.

• CONTAINS field provides a list of classes whose instances may be contained in an instance of the class in

question.

• SUPPORTED EVENTS field includes a list of event names that are detected by this class and lead potentially

to a corresponding event report.
6.2 Notational Tool for Interface Classes

Table 6.2 shows a template for defining interface classes for URAI. Each interface class for URAI will be defined in

clause 8.5 in accordance with the template shown in table 6.2.
ETSI
---------------------- Page: 14 ----------------------
SIST EN 303 146-3 V1.3.1:2018
13 ETSI EN 303 146-3 V1.3.1 (2018-06)
Table 6.2: Template for defining Interface Classes
Class[(abstract class)]

OPERATIONS
Return type: Value type:



The template fields in table 6.2 are described below.

• is the name of the Class as it appears in the corresponding model. Additional information is also

included in case the class in question has been specified as an abstract one.

• OPERATIONS field describes the operations that have been defined in the class. More specifically:

- identifies the name of an operation, as it is included in the class definition.

- identifies the type of return value at the corresponding operation. Details related to the

ASN.1 module are specified in annex B.

- identifies the access levels for member functions: public, private, protected.

7 Information Model for Radio Computer
7.1 Radio Computer

Figure 7.1 shows the UML class diagram for Radio Computer classes related to URAI which are required to support

Software Reconfiguration. The diagram includes classes which are directly and indirectly related to URAI.

ETSI
---------------------- Page: 15 ----------------------
SIST EN 303 146-3 V1.3.1:2018
14 ETSI EN 303 146-3 V1.3.1 (2018-06)
RCProf ile RCMeas urements
-RCID: NameType -listOfActiveMeasurements:
<>
ActiveMeasurementsList
IURAI
RCConfi guration RadioComput er
RadioOS
0,1 1
0..* -rOSID: NameType
RCCapabilit ies
-rOSVersion: Version
Link
0..* -listOfSupportedOptions: RCOptions
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo 0..*
RadioApp
-softwareProfile: SoftwareInfo
0..*
0..*
LinkP r of il e
Channe l
-linkID: NameType
-cellID: NameType
-associatedChannelID:
Radio AppP r of il e
OptiaonlObjectName
-linkDirection : Direction
-RadioAppID: NameType
Channe lProf ile
-CarrierFrequecy: Frequency
-RAVersion: Version
-nominalRFPower:
-direction: Direction
-channelID: NameType
AnaloguePower
-listOfSupportedOptions:
-channelFrequecyRange:
-samplingRate: SamplingRate
RAOptions
FrequencyRange
-bandwidth: Bandwidth
-listOfAssociatedLinks: Links
-radioInterface:
RadioInterface
-cellID: NameType
LinkMe asure me n ts
-receiveBLER: RxBLER
RadioAppCapabili tie s
-trasmitPower: TxPower
-receiveSINR: RxSINR
Channe lMeasurements
-listOfSupportedApplication
-transmittedBits: TxBits
1 Measurements:
-listOfChannelMeasurements:
ApplicationMeasurementsIds
ChannelMeasurementsList
-appliedMeasurementConfiguration:
RFConf igurat ion
C onf igu ra ti o nM e sur e m ents
RadioAppMe asure me nts
An tenna
-listOfActiveApplication
1..*
1 Measurements:
0,1
ApplicationMeasurements
-requestOfContext
TxPath RxPath
Informations:
Antenn aPr ofi le
ContextInformationInfo
-txStartTim
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.