ETSI TS 103 146-1 V1.1.1 (2013-11)

Reconfigurable Radio Systems (RRS); Mobile Device Information Models and Protocols; Part 1:Multiradio Interface (MURI)

DTS/RRS-02008-1

General Information

• Status: Published
• Publication Date: 14-Nov-2013
• Technical Committee: RRS 2 - REA - Reconfigurable Radio Equipment Architecture
• Current Stage: 12 - Completion
• Due Date: 05-Dec-2013
• Completion Date: 15-Nov-2013

Standards Content (Sample)

ETSI TS 103 146-1 V1.1.1 (2013-11)






Technical Specification
Reconfigurable Radio Systems (RRS);
Mobile Device Information Models and Protocols;
Part 1: Multiradio Interface (MURI)

---------------------- Page: 1 ----------------------
2 ETSI TS 103 146-1 V1.1.1 (2013-11)



Reference
DTS/RRS-02008-1
Keywords
interface, mobile, SDR
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the 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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2013.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 146-1 V1.1.1 (2013-11)
Contents
Intellectual Property Rights . 4
Foreword . 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 System Identification . 6
4.1 Communication Services Layer . 7
4.2 Radio Control Framework . 7
4.3 Radio Computer Interfaces . 8
5 Notational Tools . 8
5.1 Notational Tool for Information Model Classes . 8
5.2 Notational Tool for Interface Classes . 9
6 Information Model for Radio Computer . 10
6.1 Information Model Classes. 10
6.2 Class Definitions for Information Model . 13
7 Interface Definition . 17
7.1 Interface Overview . 17
7.2 Administrative Services . 18
7.2.1 Interfaces for Administrative Services . 18
7.2.2 Messages for Administrative Services . 19
7.3 Access Control Services . 19
7.3.1 Interfaces for Access Control Services . 19
7.3.2 Messages for Access Control Services . 20
7.4 Data Flow Services . 20
7.4.1 Interfaces for Data Flow Services . 20
7.4.2 Messages for Data Flow Services . 21
7.5 Class Definitions for Interface . 21
8 Conclusion . 23
Annex A (informative): Abstract data definitions . . 24
History . 27

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 146-1 V1.1.1 (2013-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://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.
Foreword
This Technical Specification (TS) 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 Applications Interface (URAI)";
Part 4: "Radio Programming Interface (RPI)".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 146-1 V1.1.1 (2013-11)
1 Scope
The present document defines an information model and protocol for multiradio interface for mobile device
reconfiguration. The work will be based on the Use Cases defined in TR 103 062 [i.1], TR 102 839 [i.2] and
TR 102 944 [i.3], on the system requirements defined in TS 102 969 [1] and on the radio reconfiguration related
architecture for mobile devices defined in TS 103 095 [2].
2 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
http://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.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 102 969 (V1.1.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
[2] ETSI TS 103 095 (V1.1.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Architecture for Mobile Devices".
2.2 Informative references
The following referenced documents arenot necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software
Defined Radio (SDR) Mobile Device Architecture and Services".
[i.3] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
[i.4] 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.5] Recommendation ITU-T X.680:"Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 146-1 V1.1.1 (2013-11)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Communication Services Layer (CSL): software layer related to communication services supporting generic
applications
NOTE: 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.
Radio Control Framework (RCF): control framework which, as a part of 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.1 Abstract Syntax Notation One
BLER Block Error Rate
CM Configuration Manager
CSL Communication Services Layer
FC Flow Controller
ID Identification
MD Moblile Device
MPM Mobility Policy Manager
MRC Multiradio Controller
MURI Multiradio Interface
OS Operating System
RA Radio Application
RAN Radio Access Network
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
UML Unified Modeling Language
URA Unified Radio Applications
URAI Unified Radio Application Interface
4 System Identification
Multiradio Interface (MURI) is an interface to be defined between Communication Services Layer (CSL) and Radio
Control Framework (RCF) [2] in the present document. Figure 4.1 illustrates how CSL and RCF interact with each
other using MURI. As shown in figure 4.1, MURI supports 3 kinds of services, i.e. Administrative Services, Access
Control Services and Data Flow Services. Note that CSL consists of L3 (Layer 3) and above, while RCF consists of
L1/L2.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 146-1 V1.1.1 (2013-11)

Figure 4.1: System architecture
4.1 Communication Services Layer
CSL is a software layer that is related to communication services supporting generic applications like, for example,
Internet access. CSL includes the following functional components [2]: Administrator, Mobility Policy Manager
(MPM), Networking stack and Monitor. Mobile Device (MD) user can control and manage each Radio Application
(RA) through the components of CSL because each component of CSL can control and manage the RA through the
interaction with each component of RCF. The main functionality of the 4 entities of CSL should include the following
ones.
1) Administrator requests the installation or uninstallation of an RA, and the creating or deleting instance of an
RA. It also requests RA list and the status of each RA.
2) MPM monitors the radio environments and MD capabilities, to request activation or deactivation of the RA,
and to request information about the RA list. It also selects among different Radio Access Technologies
(RATs) and discovers peer communication equipment and the arrangement of associations.
3) Networking stack is responsible for sending and receiving user data.
4) Monitor is for the MD users to monitor the context information. It is also to transfer the context information to
the desired destination(s) such as Administrator and/or MPM.
4.2 Radio Control Framework
RCF is a control framework which, as a part of the Operating System (OS), extends the OS capabilities in terms of radio
resource management. Any appropriate OS empowered by RCF, is referred to as Radio Operating System (ROS). RCF
provides functionalities of processing instructions for the CSL to manage the URA. RCF consists of 5 functional
components [2], i.e. Configuration Manager (CM), Radio Connection Manager (RCM), Flow Controller (FC),
Multiradio Controller (MRC), and Resource Manager (RM), of which the function is described as follows.
1) CM provides commands for the ROS to perform installation/uninstallation and creating/deleting instance of
RAs into Radio Processor as well as management of, and access to, the radio parameters of the RAs.
2) RCM provides commands for the ROS to perform activation/deactivation of RAs according to user requests,
and overall management of user data flows, which can also be switched from one RA to another.
3) FC is responsible for sending and receiving of user data packets and controlling the flow of signalling packets.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 146-1 V1.1.1 (2013-11)
4) MRC schedules the requests for radio resources issued by concurrently executing RAs and detects and
manages the interfaces among the concurrently executing RAs.
5) RM manages the computational resources to share them among simultaneously active RAs, and to guarantee
their real-time requirements.
4.3 Radio Computer Interfaces
<< inter face> >
IMURI
<< inter face> >
IURAI
RadioC omputer
<< inter face> >
IRPI
<< inter face> >
IRRFI

®
Figure 4.2: UML class diagram for Radio Computer Interfaces
® TM
Figure 4.2 illustrates UML (Unified Modeling Language ) class diagram for Radio Computer Interfaces. As shown in
figure 4.2, Radio Computer shall realize 4 interfaces, i.e. MURI, Unified Radio Applications Interface (URAI), Radio
Programming Interface (RPI), and Reconfigurable Radio Frequency Interface (RRFI). MURI is an interface between
CSL and RCF, which are defined in figure 4.1. URAI is an interface between RCF and URA [2]. RPI is an internal
interface in URA. Finally, RRFI is an interface between URA and RF part [2]. Note that the present document defines
an information model and protocol related to MURI only.
5 Notational Tools
5.1 Notational Tool for Information Model Classes
Table 5.1 shows a template for defining information model classes [i.4]. Each information model class will be defined
in clause 6.2 in accordance with the template shown in table 5.1. Although neither "DERIVED FROM" nor
"SUPPORTED EVENTS" are used in present document, these are presented in table 5.1 to maintain compatibility with
the IEEE 1900.4 standard [i.4].
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 146-1 V1.1.1 (2013-11)
Table 5.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>

A description of the template is provided within the following list:
• is the name of the Class as it is appeared 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). Readers shall refer to the ASN.1 module for details (see 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.
5.2 Notational Tool for Interface Classes
Table 5.2 shows a template for defining interface classes for MURI. Each interface class for MURI will be defined in
clause 7.5 in accordance with the template shown in table 5.2.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 146-1 V1.1.1 (2013-11)
Table 5.2: Template for defining Interface Classes
Class[(abstract class)]

OPERATIONS
Return type: Value type:




A description of the template is provided within the following list:
• 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. Readers shall refer to
the ASN.1 module for details (see annex A).
- identifies the access levels for member functions: public, private, protected.
6 Information Model for Radio Computer
6.1 Information Model Classes
In this clause, each class of Radio Computer is defined using the template presented in clause 5.1. In order to define
®
each class of Radio Computer, UML class diagram for all the Radio Computer classes related to MURI should be
®
determined [i.4]. Figure 6.1 illustrates the UML class diagram for Radio Computer classes related to MURI.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 146-1 V1.1.1 (2013-11)
-RadioAppID: NameType
-RAVersion: Version
<>
-listOfSupportedOptions:
RAOptions
-rOSID: NameType
-rOSVersion: Version
-listOfInstalledRA:
RadioApplicationID
-listOfSupportedOptions:
RCOptions
-listOfSupportedRadioInterfaces:
RadioInterface
-listOfSupportedChannels:
ChannelIDs
-RCID: NameType
-hardwareProfile: HardwareInfo
-softwareProfile: SoftwareInfo
-linkID: NameType
-cellID: NameType
-associatedChannelID:
OptionalObjectName
-listOfActiveMeasurements:
-linkDirection: Direction
ListActiveMeasurements
-receiveBLER: RxBLER
-transmitPower: TxPower
-receiveSINR: RxSINR
-transmittedBits: TxBits
-channelID: NameType
-channelFrequencyRange:
FrequencyRange
-radioInterface: RadioInterface
-cellID: NameType
-listOfChannelMeasurements:
ListChannelMeasurements

®
Figure 6.1: UML class diagram for Radio Computer classes related to MURI
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 146-1 V1.1.1 (2013-11)
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.
• RadioComputer
This class describes all resources and interfaces related to hardware and software of a reconfigurable wireless
terminalas well as measurement information related to radio resources within the terminal.
• RCCapabilities
This class contains information about Radio Computer capabilities including hardware, software, transmission
and measurement capabilities, for example, supported radio interfaces, maximum transmission power, etc.
Each instance of Radio Computer class can have only one instance of RCCapabilities class as a member.
• RadioApp
This class describes installed Radio Application. Each instance of Radio Computer class can relate to zero or
several instances of RadioApp class. Each instance of RadioApp class is associated with one instance of Radio
OS class.
• RadioOS
This class describes installed Radio OS. Each instance of Radio Computer class can relate to zero or one
instance of RadioOS class.Each instance of RadioOS class is associated with zero or several instances of
RadioApp class.
• RCProfile
This class contains general information about the Radio Computer, for example, terminal Identification (ID).
Each instance of RadioComputer class can have only one instance of RCProfile class as a member.
• RCConfiguration
This class contains information about the current configuration of Radio Computer. Each instance of
RadioComputer class can have only one instance of RCConfiguration class as a member.
• Link
This class contains information about one active Radio Application and corresponding connection between
Reconfigurable Radio terminal and Radio Access Networks (RANs). Each instance of RCConfiguration class
can have zero or several instances of Link class as members. Each instance of Link class is associated with one
instance of Channel class.
• LinkProfile
This class contains general information about this active connection, for example, link ID, serving cell ID,
channel used, etc. Each instance of Link class can have only one instance of LinkProfile class as a member.
• LinkMeasurments
This class contains current measurements (instantaneous measurement data and performance statistics derived
from this data) related to this active connection, such as Block Error Rate (BLER), power, and Signal to
Interference plus Noise Ratio (SINR) measurements. Each instance of Link class can have only one instance of
LinkMeasurements class as a member.
• RCMeasurements
This class contains current measurements (instantaneous measurement data and performance statistics derived
from this data) related to Reconfigurable Radio terminal, for example, battery capacity and terminal location
measurements. Each instance of RadioComputer class can have only one instance of RCMeasurements class as
a member.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 146-1 V1.1.1 (2013-11)
• Channel
This class describes one frequency channel that may or may not have active connections on it. Each instance
of RadioComputerclass can have zero or several instances of Channel class as members.
• ChannelProfile
This class contains general information about this frequency channel, for example, channel ID, central
frequency, bandwidth, and radio interface used. Each instance of Channel class can have only one instance of
Channel Profile class as a member.
• ChannelMeasurements
This class contains current measurements (instantaneous measurement data and performance statistics derived
from this data) related to this frequency channel, for example, interference and load measurements. Each
instance of Channel class can have only one instance of ChannelMeasurements class as a member.
6.2 Class Definitions for Information Model
®
Each class of Radio Computer can be defined using the template presented in clause 5.1 in accordance with the UML
diagram of figure 6.1 which specifies relations among all the classes of Radio Computer. Radio Computer classes are
defined as follows:
Table 6.1: RadioComputerClass
Class RadioComputer
This class describes all resources and interfaces related to hardware and software of a reconfigurable
wireless terminal, as well as, measurement information related to radio resources within the terminal.
DERIVED FROM
ATTRIBUTES
CONTAINED IN
RCCapabilities [1], RCProfile [1], RCConfiguration [1],
CONTAINS
RCMeasurements [1], Channel [1], RadioApp[*], RadioOS[0-1]
SUPPORTED EVENTS

Table 6.2: RadioAppClass
Class RadioApp
This class describes installed Radio Application.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
RadioAppID
NameType Read Not specified
This attribute describes ID of installed Radio Application.
Value type: Possible access: Default value:
RAVersion
Version Read Not specified
This attribute describes a version of Radio Application.
Value type: Possible access: Default value:
listOfSupportedOptions
RAOptionsList Read Not specified
This attribute contains a list of supported options.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 146-1 V1.1.1 (2013-11)
Table 6.3: RadioOSClass
Class RadioOS
This class describes installed Radio OS.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
rOSID
NameType Read Not specified
This attribute describes ID of Radio OS.
Value type: Possible access: Default value:
rOSVersion
Version Read Not specified
This attribute describes a version of Radio OS.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS

Table 6.4: RCCapabilitiesClass
Class RCCapabilities
This class contains information about Radio Computer capabilities including hardware, software, transmission
and measurement capabilities.
DERIVED FROM
ATTRIBUTES
Possible access:
Value type: Default value:
listOfInstalledRA Read-Add-
RadioApplicationIDList Not specified
Remove
This attribute describes a list of installed Radio Application.
Value type: Possible access: Default value:
listOfSupportedOptions
RCOptionsList Read-Write Not specified
This attribute describes a list of supported options.
Value type: Possible access: Default value:
listOfSupportedRadioInterfaces
RadioInterfacesList Read-Write Not specified
This attribute describes radio interfaces supported by
...