SIST EN 303 146-1 V1.3.1:2018

EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Mobile Device (MD) information models and protocols;
Part 1: Multiradio Interface (MURI)

2 ETSI EN 303 146-1 V1.3.1 (2018-06)

Reference
REN/RRS-0218
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
3 ETSI EN 303 146-1 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 . 7
4 Introduction . 7
5 System Identification . 9
5.1 Radio Computer Structure . 9
5.2 MURI 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 . 22
8.1 Interface Overview . 22
8.2 Administrative Services . 23
8.2.1 Overview on Administrative Services . 23
8.2.2 Messages for Administrative Services . 24
8.3 Access Control Services . 25
8.3.1 Overview on Access Control Services . 25
8.3.2 Messages for Access Control Services . 25
8.4 Data Flow Services . 26
8.4.1 Overview on Data Flow Services . 26
8.4.2 Messages for Data Flow Services . 26
8.5 Class Definitions for Interface . 27
Annex A (informative): Abstract Data Definitions . 29
Annex B (informative): MURI Qualification Methods for Validation . 33
History . 34

ETSI
4 ETSI EN 303 146-1 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 1 of a multi-part deliverable covering the Mobile Device 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: 5 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
5 ETSI EN 303 146-1 V1.3.1 (2018-06)
1 Scope
The present document defines an information model and protocol for multiradio interface for reconfigurable mobile
devices. 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 [i.7] and on the radio reconfiguration related architecture for mobile devices defined in ETSI
EN 303 095 [i.2].
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.
Not applicable.
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".
[i.3] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device Information Models
and Protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".
[i.4] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software
Defined Radio (SDR) Mobile Device Architecture and Services".
TM
[i.5] 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.6] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[i.7] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
ETSI
6 ETSI EN 303 146-1 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: connecting one location to another through a given Radio Access Technology for the purpose of transmitting and
receiving digital information
NOTE: Each link is conveyed over a given Channel.
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.
reconfigurable mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable Mobile Devices include but are not limited to: Smartphones, Feature Phones, Tablets, and
Laptops.
ETSI
7 ETSI EN 303 146-1 V1.3.1 (2018-06)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASN.1 Abstract Syntax Notation One
BLER BLock Error Rate
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
ID IDentification
IR Intermediate Representation
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
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
RCM Radio Connection Manager
RF Radio Frequency
RM Resource Manager
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
SINR Signal to Interference plus Noise Ratio
SW SoftWare
TCP/IP Transmission Control Protocol/Internet Protocol
UML Unified Modeling 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 in ETSI EN 303 095 [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
8 ETSI EN 303 146-1 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 which is the scope of the present document;
• RRFI for interfacing URA and RF Transceiver in ETSI TS 103 146-2 [i.3];
• URAI for interfacing URA and RCF in ETSI TR 102 839 [i.4];
• RPI for allowing an independent and uniform production of RAs in ETSI TR 102 839 [i.4].
The present document defines MURI.
ETSI
9 ETSI EN 303 146-1 V1.3.1 (2018-06)
< >
IMUR I
< >
IRR F I
R adioComput 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 in ETSI EN 303 095 [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 MURI, other modeling languages could
be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how CSL and RCF interact with each other using MURI.
ETSI
10 ETSI EN 303 146-1 V1.3.1 (2018-06)

Figure 5.1: Interconnection between CSL and RCF using MURI for Reconfigurable MD
As shown in figure 5.1, MURI supports 3 kinds of services:
• Administrative Services
These services are used by some device configuration application i.e. Administrator which is included in the CSL, to
(un)install a new URA into the Reconfigurable MD and create/delete an instance of the URA. Installation and loading
may take place both at device start-up time to set up the network connection as well as during run-time, whenever
reconfiguration of available URAs is needed. MURI does not make any assumption on how and when the mobile device
will detect the need of the reconfiguration.
• Access Control Services
These services are used by the MPM to maintain the user policies and preferences related to the usage of different
RATs and to make a selection between them. Modelling of such preferences and selection algorithms is not in the scope
of the present document; however, the MURI specification covers the information exchange of RAT selection decisions
between CSL and RCF. The preferences themselves may originate either locally from applications or end user settings
as well as in a distributed manner from network operator or from a cognitive radio management framework.
• Data Flow Services
These services are used by the networking stack of the Reconfigurable MD, such as the TCP/IP stack. Therefore data
flow services represent the set of (logical) link layer services, which are provided in a uniform manner regardless of
which URAs are active.
The Communication Services Layer (CSL) and Radio Control Framework (RCF) are defined in ETSI EN 303 095 [i.2].
5.2 MURI System Requirement Mapping
The Radio Computer components above described shall support the MURI system requirements shown in table 5.1 and
described in clauses 6.1 and 6.2 of ETSI EN 302 969 [i.7].
ETSI
11 ETSI EN 303 146-1 V1.3.1 (2018-06)
Table 5.1: Mapping of Radio Computer Components to
the system requirements described in ETSI EN 302 969
Entity/Component/Unit System Requirements Comments
[i.7]
Administrator R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7].
R-FUNC-RA-01 The requirement is described in clause 6.2.1 of [i.7].
R-FUNC-MDR-01 The requirement is described in clause 6.4.1 of [i.7].
R-FUNC-MDR-02 The requirement is described in clause 6.4.2 of [i.7].
R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of [i.7].
Mobility Policy Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7].
R-FUNC-RAT–04 The requirement is described in clause 6.1.4 of [i.7].
R-FUNC-RA-03 The requirement is described in clause 6.2.3 of [i.7].
Networking Stack R-FUNC-RAT–05 The requirement is described in clause 6.1.5 of [i.7].
R-FUNC-RA-04 The requirement is described in clause 6.2.4 of [i.7].
Configuration Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7].
R-FUNC-RAT–02 The requirement is described in clause 6.1.2 of [i.7].
R-FUNC-RA-01 The requirement is described in clause 6.2.1 of [i.7].
R-FUNC-MDR-01 The requirement is described in clause 6.4.1 of [i.7].
R-FUNC-MDR-02 The requirement is described in clause 6.4.2 of [i.7].
R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of [i.7].
Radio Connection Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7].
R-FUNC-RAT–02 The requirement is described in clause 6.1.2 of [i.7].
R-FUNC-RAT–03 The requirement is described in clause 6.1.3 of [i.7].
R-FUNC-RAT–04 The requirement is described in clause 6.1.4 of [i.7].
R-FUNC-RAT–06 The requirement is described in clause 6.1.6 of [i.7].
R-FUNC-RA-03 The requirement is described in clause 6.2.3 of [i.7].
Flow Controller R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7].
R-FUNC-RAT–03 The requirement is described in clause 6.1.3 of [i.7].
R-FUNC-RAT–05 The requirement is described in clause 6.1.5 of [i.7].
R-FUNC-RAT–06 The requirement is described in clause 6.1.6 of [i.7].
R-FUNC-RA-04 The requirement is described in clause 6.2.4 of [i.7].

6 Notational Tools
6.1 Notational Tool for Information Model Classes
TM
Table 6.1 shows a template for defining information model classes in IEEE 1900.4 -2009 [i.5]. 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
12 ETSI EN 303 146-1 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 of the present document.
- 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 MURI. Each interface class for MURI will be defined in
clause 8.5 in accordance with the template shown in table 6.2.
Table 6.2: Template for defining Interface Classes
Class[(abstract class)]

OPERATIONS
Return type: Value type:




ETSI
13 ETSI EN 303 146-1 V1.3.1 (2018-06)
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 of the present document.
- 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 MURI which are required to support
Software Reconfiguration.
ETSI
14 ETSI EN 303 146-1 V1.3.1 (2018-06)
RadioA pp
-RadioAppID: NameType
0.* 0.*
-RAVersion: Version
-listOfSupportedOptions:
RAOptions
RCUse r
<>
IMURI
RadioOS
1 1
0,1
-rOSID: NameType
-rOSVersion: Version
Radio Comput er
RCMeas ur ements
RCCap abilit ies
-listOfActiveMeasurements:
1 -listOfSupportedOptions: RCOptions
ActiveMeasurementsList
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo
RCP rof ile
-softwareProfile: SoftwareInfo
-RCID: NameType 1
RCConfi gu r ation
Channe l
0.*
Channe lP rof ile
Link
-channelID: NameType
0.*
-channelFrequecyRange:
FrequencyRange
-radioInterface:
RadioInterface
-cellID: NameType
RF Conf igurat ion
LinkP r of il e
-linkID: NameType
-cellID: NameType
Channe lMeasur ements
-associatedChannelID:
TxP ath
OptiaonlObjectName
-listOfChannelMeasurements:
-linkDirection : Direction
-txStartTime: TxStartTime ChannelMeasurementsList
0,1
-CarrierFrequecy: Frequency
-txStopTime: TxStopTime -appliedMeasurementConfiguration:
-nominalRFPower:
C onfigu rati o nMesur ements
AnaloguePower
-samplingRate: SamplingRate
RxP ath
-bandwidth: Bandwidth
-rxStartTime: RxStartTime
An tenna
-rxStopTime: RxStopTime
1.*
LinkMe asure me nts
-receiveBLER: RxBLER
-trasmitPower: TxPower
An tennaPr ofi le
-receiveSINR: RxSINR
-antennaID:
-transmittedBits: TxBits
NameType
Figure 7.1: UML class diagram for Radio Computer classes related to MURI
The Radio Computer classes related to MURI are defined as follows:
• RCUser
This class describes information related to a user of the Radio Computer. Each instance of RCUser class depends on
one instance of RadioComputer class.
ETSI
15 ETSI EN 303 146-1 V1.3.1 (2018-06)
• RadioApp
This class describes an installed Radio Application. Each instance of a "Radio Computer" class can relate to zero or
several instances of RadioApp class (0.*). Each instance of RadioApp class is associated with one instance of Radio
OS class.
• RadioOS
This class describes an installed Radio OS. Each instance of a "Radio Computer" class can relate to zero or one instance
of RadioOS class (0,1). Each instance of RadioOS class is associated with zero or several instances of RadioApp
class (0.*).
• RadioComputer
This class contains all URA(s) related information about resources and interactions related to hardware and software of
a reconfigurable MD, for example, computational/spectral resource usage, collection of context information, channel
measurement results, etc.
• RCProfile
This class contains general information about the Radio Computer, for example, terminal Identification (ID). Each
instance of a "RadioComputer" class can have only one instance of RCProfile class as a member.
• RCCapabilities
This class contains information about Radio Computer capabilities including hardware, software, transmission and
measurement capabilities such as supported RATs and maximum transmission power. Each instance of RadioComputer
class shall have only one instance of RCCapabilities class as a member.
• Channel
This class contains one radio channel that may or may not be used by an active radio link. Each instance of
RadioComputer class can have zero, one or several instances of Channel class as members (0.*). In case of an active
radio link, at least one Channel class is available.
• ChannelProfile
This class contains general information about the radio channel such as channel ID, center frequency, bandwidth, and
used RAT. Each instance of Channel class shall have only one instance of Channel Profile class as a member.
• ChannelMeasurements
This class contains current measurements (instantaneous measurement data and related metadata) and the applied
measurement configuration related to this radio channel such as interference and load measurements. Each instance of
Channel class shall have only one instance of ChannelMeasurements class as a member.
• Antenna
This class contains information about antenna selection. Each instance of Channel class shall have at least one instance
of Antenna class as a member. (1.*).
• AntennaProfile
This class contains general information about this antenna, such as antenna port, applicable frequency range and
antenna gain. Each instance of Antenna class shall have only one instance of AntennaProfile class as a member.
• RCConfiguration
This class contains information about the current configuration of Radio Computer. Each instance of RadioComputer
class shall have only one instance of RCConfiguration class as a member.
• Link
This class contains information about one active URA and the corresponding connection between the Reconfigurable
MD and the Radio Access Network (RAN). Each instance of RCConfiguration class has zero, one or several instances
of Link
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.085,Reconfigurable Radio Systems (RRS) - Mobile Device (MD) information models and protocols - Part 1: Multiradio Interface (MURI)35.200Vmesniška in povezovalna opremaInterface and interconnection equipment33.060.01Radijske komunikacije na splošnoRadiocommunications in generalICS:Ta slovenski standard je istoveten z:ETSI EN 303 146-1 V1.3.1 (2018-06)SIST EN 303 146-1 V1.3.1:2018en01-september-2018SIST EN 303 146-1 V1.3.1:2018SLOVENSKI
STANDARD
EUROPEAN STANDARD SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 2
Reference REN/RRS-0218 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.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETM 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. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 3 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 . 7 4 Introduction . 7 5 System Identification . 9 5.1 Radio Computer Structure . 9 5.2 MURI 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 . 22 8.1 Interface Overview . 22 8.2 Administrative Services . 23 8.2.1 Overview on Administrative Services . 23 8.2.2 Messages for Administrative Services . 24 8.3 Access Control Services . 25 8.3.1 Overview on Access Control Services . 25 8.3.2 Messages for Access Control Services . 25 8.4 Data Flow Services . 26 8.4.1 Overview on Data Flow Services . 26 8.4.2 Messages for Data Flow Services . 26 8.5 Class Definitions for Interface . 27 Annex A (informative):
Abstract Data Definitions . 29 Annex B (informative):
MURI Qualification Methods for Validation . 33 History . 34
ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 4 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 1 of a multi-part deliverable covering the Mobile Device 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: 5 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. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 5 1 Scope The present document defines an information model and protocol for multiradio interface for reconfigurable mobile devices. 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 [i.7] and on the radio reconfiguration related architecture for mobile devices defined in ETSI EN 303 095 [i.2]. 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. Not applicable. 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". [i.3] ETSI EN 303 146-2: "Reconfigurable Radio Systems (RRS); Mobile Device Information Models and Protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)". [i.4] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software Defined Radio (SDR) Mobile Device Architecture and Services". [i.5] IEEE 1900.4TM-2009: "IEEE Standard for Architectural Building Blocks Enabling Network-Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous Wireless Access Networks". [i.6] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". [i.7] ETSI EN 302 969: "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Requirements for Mobile Devices". SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 6 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: connecting one location to another through a given Radio Access Technology for the purpose of transmitting and receiving digital information NOTE: Each link is conveyed over a given Channel. 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. reconfigurable mobile device: mobile device with radio communication capabilities providing support for radio reconfiguration NOTE: Reconfigurable Mobile Devices include but are not limited to: Smartphones, Feature Phones, Tablets, and Laptops. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 7 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One BLER BLock Error Rate CM Configuration Manager CSL Communication Services Layer FC Flow Controller ID IDentification IR Intermediate Representation MD Mobile Device MDRC Mobile Device Reconfiguration Class 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 RCM Radio Connection Manager RF Radio Frequency RM Resource Manager ROS Radio Operating System RPI Radio Programming Interface RRFI Reconfigurable Radio Frequency Interface SINR Signal to Interference plus Noise Ratio SW SoftWare TCP/IP Transmission Control Protocol/Internet Protocol UML Unified Modeling 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 in ETSI EN 303 095 [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. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 8
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 which is the scope of the present document; • RRFI for interfacing URA and RF Transceiver in ETSI TS 103 146-2 [i.3]; • URAI for interfacing URA and RCF in ETSI TR 102 839 [i.4]; • RPI for allowing an independent and uniform production of RAs in ETSI TR 102 839 [i.4]. The present document defines MURI. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 9 RadioComputer<>IMURI<>IRRFI<>IRPI<>IURAI 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 in ETSI EN 303 095 [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 MURI, other modeling languages could be used as well. 5 System Identification 5.1 Radio Computer Structure Figure 5.1 illustrates how CSL and RCF interact with each other using MURI. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 10
Figure 5.1: Interconnection between CSL and RCF using MURI for Reconfigurable MD As shown in figure 5.1, MURI supports 3 kinds of services: • Administrative Services These services are used by some device configuration application i.e. Administrator which is included in the CSL, to (un)install a new URA into the Reconfigurable MD and create/delete an instance of the URA. Installation and loading may take place both at device start-up time to set up the network connection as well as during run-time, whenever reconfiguration of available URAs is needed. MURI does not make any assumption on how and when the mobile device will detect the need of the reconfiguration. • Access Control Services These services are used by the MPM to maintain the user policies and preferences related to the usage of different RATs and to make a selection between them. Modelling of such preferences and selection algorithms is not in the scope of the present document; however, the MURI specification covers the information exchange of RAT selection decisions between CSL and RCF. The preferences themselves may originate either locally from applications or end user settings as well as in a distributed manner from network operator or from a cognitive radio management framework. • Data Flow Services These services are used by the networking stack of the Reconfigurable MD, such as the TCP/IP stack. Therefore data flow services represent the set of (logical) link layer services, which are provided in a uniform manner regardless of which URAs are active. The Communication Services Layer (CSL) and Radio Control Framework (RCF) are defined in ETSI EN 303 095 [i.2]. 5.2 MURI System Requirement Mapping The Radio Computer components above described shall support the MURI system requirements shown in table 5.1 and described in clauses 6.1 and 6.2 of ETSI EN 302 969 [i.7]. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 11 Table 5.1: Mapping of Radio Computer Components to the system requirements described in ETSI EN 302 969 Entity/Component/Unit System Requirements [i.7] Comments Administrator R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7]. R-FUNC-RA-01 The requirement is described in clause 6.2.1 of [i.7]. R-FUNC-MDR-01 The requirement is described in clause 6.4.1 of [i.7]. R-FUNC-MDR-02 The requirement is described in clause 6.4.2 of [i.7]. R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of [i.7]. Mobility Policy Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7]. R-FUNC-RAT–04 The requirement is described in clause 6.1.4 of [i.7]. R-FUNC-RA-03 The requirement is described in clause 6.2.3 of [i.7]. Networking Stack R-FUNC-RAT–05 The requirement is described in clause 6.1.5 of [i.7]. R-FUNC-RA-04 The requirement is described in clause 6.2.4 of [i.7]. Configuration Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7]. R-FUNC-RAT–02 The requirement is described in clause 6.1.2 of [i.7]. R-FUNC-RA-01 The requirement is described in clause 6.2.1 of [i.7].
R-FUNC-MDR-01 The requirement is described in clause 6.4.1 of [i.7]. R-FUNC-MDR-02 The requirement is described in clause 6.4.2 of [i.7]. R-FUNC-MDR-03 The requirement is described in clause 6.4.3 of [i.7]. Radio Connection Manager R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7]. R-FUNC-RAT–02 The requirement is described in clause 6.1.2 of [i.7]. R-FUNC-RAT–03 The requirement is described in clause 6.1.3 of [i.7]. R-FUNC-RAT–04 The requirement is described in clause 6.1.4 of [i.7]. R-FUNC-RAT–06 The requirement is described in clause 6.1.6 of [i.7]. R-FUNC-RA-03 The requirement is described in clause 6.2.3 of [i.7]. Flow Controller R-FUNC-RAT–01 The requirement is described in clause 6.1.1 of [i.7]. R-FUNC-RAT–03 The requirement is described in clause 6.1.3 of [i.7]. R-FUNC-RAT–05 The requirement is described in clause 6.1.5 of [i.7]. R-FUNC-RAT–06 The requirement is described in clause 6.1.6 of [i.7]. R-FUNC-RA-04 The requirement is described in clause 6.2.4 of [i.7].
6 Notational Tools 6.1 Notational Tool for Information Model Classes Table 6.1 shows a template for defining information model classes in IEEE 1900.4TM-2009 [i.5]. 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. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 12 Table 6.1: Template for defining Information Model Classes Class[(abstract class)] DERIVED FROM ATTRIBUTES [] Value type: Possible access: Default value: CONTAINED IN CONTAINS ] - exactly n instances, [ - ] - not less than m and not more than n instances.> SUPPORTED EVENTS
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 of the present document.
- 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 MURI. Each interface class for MURI will be defined in clause 8.5 in accordance with the template shown in table 6.2. Table 6.2: Template for defining Interface Classes Class[(abstract class)] OPERATIONS Return type: Value type:
ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 13 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 of the present document. - 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 MURI which are required to support Software Reconfiguration. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 14 <>IMURIRadioComputerRCMeasurements-listOfActiveMeasurements: ActiveMeasurementsListRCConfigurationLinkRCCapabilities-listOfSupportedOptions: RCOptions-listOfSupportedRadioInterfaces: RadioInterfaces-listOfSupportedChannels: ChannelIDs-hardwareProfile: HardwareInfo-softwareProfile: SoftwareInfoChannelAntennaChannelProfile-channelID: NameType-channelFrequecyRange: FrequencyRange-radioInterface: RadioInterface-cellID: NameTypeChannelMeasurements-listOfChannelMeasurements: ChannelMeasurementsList-appliedMeasurementConfiguration:ConfigurationMesurementsAntennaProfile-antennaID: NameTypeRFConfigurationTxPath-txStartTime: TxStartTime-txStopTime: TxStopTimeRxPath-rxStartTime: RxStartTime-rxStopTime: RxStopTimeLinkMeasurements-receiveBLER: RxBLER-trasmitPower: TxPower-receiveSINR: RxSINR-transmittedBits: TxBitsLinkProfile-linkID: NameType-cellID: NameType-associatedChannelID: OptiaonlObjectName-linkDirection : Direction-CarrierFrequecy: Frequency-nominalRFPower: AnaloguePower-samplingRate: SamplingRate-bandwidth: Bandwidth10.*11110.*11110,111.*RCProfile-RCID: NameType1RadioOS-rOSID: NameType-rOSVersion: VersionRadioApp-RadioAppID: NameType-RAVersion: Version-listOfSupportedOptions: RAOptions0,10.*0.*1RCUser1Figure 7.1: UML class diagram for Radio Computer classes related to MURI The Radio Computer classes related to MURI are defined as follows: • RCUser This class describes information related to a user of the Radio Computer. Each instance of RCUser class depends on one instance of RadioComputer class. SIST EN 303 146-1 V1.3.1:2018

ETSI ETSI EN 303 146-1 V1.3.1 (2018-06) 15 • RadioApp This class describes an installed Radio Application. Each instance of a "Radio Computer" class can relate to zero or several instances of RadioApp class (0.*). Each instance of RadioApp class is associated with one instance of Radio OS class. • RadioOS This class describes an installed Radio OS. Each instance of a "Radio Computer" class can relate to zero or one instance of RadioOS class (0,1). Each instance of RadioOS class is associated with zero or several instances of RadioApp class (0.*). • RadioComputer This class contains all URA(s) related information about resources and interactions related to hardware and software of a reconfigurable MD, for example, computational/spectral resource usage, collection of context information, channel measurement results, etc. • RCProfile
This class contains general information about the Radio Computer, for example, terminal Identification (ID). Each instance of a "RadioComputer" class can have only one instance of RCProfile class as a member. • RCCapabilities This class contains information about Radio Computer capabilities including hardware, software, transmission and measurement capabilities such as supported RATs and maximum transmission power. Each instance of RadioComputer class shall have only one instance of RCCapabilities class as a member. • Channel This class contains one radio channel that may or may not be used by an active radio link. Each instance of RadioComputer class can have zero, one or several instances of Channel class as members (0.*). In case of an active radio link, at least one Channel class is available. • ChannelProfile This class contains general information about the radio channel such as channel ID, center frequency, bandwidth, and used RAT. Each instance of Channel class shall have only one instance of Channel Profile class as a member. • ChannelMeasurements This class contains current measurements (instantaneous measurement data and related metadata) and the applied measurement configuration related to this radio channel such as interference and load measurements. Each instance o
...