SIST EN 303 146-2 V1.2.1:2016
(Main)Reconfigurable Radio Systems (RRS) - Mobile Device Information Models and Protocols - Part 2: Reconfigurable Radio Frequency Interface (RRFI)
Reconfigurable Radio Systems (RRS) - Mobile Device Information Models and Protocols - Part 2: Reconfigurable Radio Frequency Interface (RRFI)
The present document defines an information model and protocol for reconfigurable radio frequency interface for
reconfigurable MDs. 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.8].
Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in protokoli za mobilne naprave - 2. del: Spremenljivi radiofrekvenčni vmesnik (RRFI)
Ta dokument opredeljuje informacijski model in protokol za spremenljivi radiofrekvenčni vmesnik za spremenljive MD-je. Delo temelji na primerih uporabe iz dokumenta ETSI TR 102 944 [i.1], sistemskih zahtevah iz dokumenta ETSI EN 302 969 [1] ter preoblikovanju radia glede na arhitekturo za mobilne naprave iz dokumenta ETSI EN 303 095 [i.2].
General Information
Standards Content (Sample)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Mobile Device (MD) information models and protocols;
Part 2: Reconfigurable Radio Frequency Interface (RRFI)
2 ETSI EN 303 146-2 V1.2.1 (2016-06)
Reference
REN/RRS-0246
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.
© European Telecommunications Standards Institute 2016.
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
3 ETSI EN 303 146-2 V1.2.1 (2016-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 . 8
5 System Identification . 9
5.1 Radio Computer Structure . 9
5.2 URA . 11
5.3 RF Transceiver . 11
5.4 RF Interfaces . 11
5.5 Radio Computer RF System Requirement Mapping . 11
6 Notational Tools . 12
6.1 Notational Tool for Information Model Classes . 12
6.2 Notational Tool for Interface Classes . 13
7 Information Model for Radio Computer . 13
7.1 Radio Computer . 13
7.2 Class Definitions for Information Model . 16
8 Interface Definition . 21
8.1 Interface Overview . 21
8.2 Spectrum Control Services . 24
8.2.1 Overview on Spectrum Control Services . 24
8.2.2 Messages for Spectrum Control Services . 24
8.3 Power Control Services . 25
8.3.1 Overview on Power Control Services . 25
8.3.2 Messages for Power Control Services . 25
8.4 Antenna Management Services . 25
8.4.1 Overview on Antenna Management Services . 25
8.4.2 Messages for Antenna Management Services. 26
8.5 Tx/Rx Chain Control Services. 26
8.5.1 Overview on Tx/Rx Chain Control Services . 26
8.5.2 Messages for Tx/Rx Chain Control Services . 26
8.6 RVM Protection Services . 27
8.6.1 Overview on RVM Protection Services . 27
8.6.2 Messages for RVM Protection Services . 28
8.7 Class Definitions for Interface . 28
Annex A (informative): Abstract Data Definitions . 31
Annex B (informative): RRFI Qualification Methods for Validation . 34
History . 35
ETSI
4 ETSI EN 303 146-2 V1.2.1 (2016-06)
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 (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.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
The present document is part 2 of a multi-part deliverable covering the Mobile Device (MD) information models and
protocols, as identified below:
ETSI EN 303 146-1: "Multiradio Interface (MURI)";
ETSI EN 303 146-2: "Reconfigurable Radio Frequency Interface (RRFI)";
ETSI EN 303 146-3: "Unified Radio Application Interface (URAI)";
ETSI TS 103 146-4: "Radio Programming Interface (RPI)".
National transposition dates
Date of adoption of this EN: 30 May 2016
Date of latest announcement of this EN (doa): 31 August 2016
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2017
Date of withdrawal of any conflicting National Standard (dow): 28 February 2017
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-2 V1.2.1 (2016-06)
1 Scope
The present document defines an information model and protocol for reconfigurable radio frequency interface for
reconfigurable MDs. 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.8].
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
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.
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 969 (V1.2.1): "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] Recommendation ITU-T Q.1290: "Glossary of Terms used in the Definition of Intelligent
Networks".
[i.3] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software
Defined Radio (SDR) Mobile Device Architecture and Services".
[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] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device Information Models
and Protocols; Part 1: Multiradio Interface (MURI)".
SM SM
Working Group: "MIPI® Alliance Specification for DigRF v4".
[i.6] DigRF
[i.7] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
ETSI
6 ETSI EN 303 146-2 V1.2.1 (2016-06)
[i.8] ETSI EN 303 095 (V1.2.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Architecture for Mobile Devices".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Processor (AP): part of mobile device hardware working under OS control and on which User
Applications, among others, are executed
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 Recommendation ITU-T Q.1290 [i.2].
Communication Services Layer (CSL): 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
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 (RC): 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), Multiradio Controller (MRC) and Resource Manager (RM) which is
typically part of OS.
Radio Frequency (RF) transceiver: part of radio platform converting, for transmission, baseband signals into radio
signals, and, for reception, radio signals into baseband signals
Radio Operating System (ROS): any appropriate OS empowered by RCF
NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of
RP such as resource management, file system support, unified access to hardware resources, etc.
ETSI
7 ETSI EN 303 146-2 V1.2.1 (2016-06)
radio platform: part of mobile device hardware which relates to radio processing capability, including programmable
components, hardware accelerators, RF transceiver, and antenna(s)
NOTE: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals. By
nature, it is heterogeneous hardware including different processing elements such as fixed accelerators,
e.g. Application-Specific Integrated Circuit (ASIC), or reconfigurable accelerators, e.g. FPGAs, etc.
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: An RVM may be implemented as a controlled execution environment which allows the selection of a
trade-off between flexibility of base band code development and required (re-)certification efforts.
reconfigurable Mobile Device (MD): 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.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACK ACKnowledgement
ACKM ACKnowledgement with Modification
AP Application Processor
ASIC Application-Specific Integrated Circuit
ASN.1 Abstract Syntax Notation One
BBIC Base-Band Integrated Circuit
BLER Block Error Rate
CSL Communication Services Layer
EU European Union
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multiple Input Multiple Output
MPM Mobility Policy Manager
MURI MUltiRadio Interface
NACK Negative ACKnowledgement
OOB Out Of Band
OS Operating System
RA Radio Application
RAN Radio Access Network
RAP Radio Application Package
RAT Radio Access Technology
RC Radio Computer
RCF Radio Control Framework
RF Radio Frequency
RFIC Radio Frequency Integrated Circuit
ROS Radio Operating System
RPI Radio Programming Interface
RRFI Reconfigurable Radio Frequency Interface
RVM Radio Virtual Machine
RX Reception
SINR Signal to Interference plus Noise Ratio
TR Technical Report
UML Unified Modeling Language
URA Unified Radio Applications
URAI Unified Radio Applications Interface
ETSI
8 ETSI EN 303 146-2 V1.2.1 (2016-06)
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 [1]. 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.
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.5].
• RRFI for interfacing URA and RF Transceiver, which is the scope of the present document.
• URAI for interfacing URA and RCF [i.3].
• RPI for allowing an independent and uniform production of RAs [i.3].
The present document defines RRFI.
ETSI
9 ETSI EN 303 146-2 V1.2.1 (2016-06)
<>
IMUR I
<>
IRR F I
R adioComput er
<>
IRPI
<>
IUR AI
Figure 4.2: UML class diagram for RC interfaces
Figure 4.2 illustrates UML class diagram for RC interfaces. The reconfigurable MD may be seen as a RC where
individual URAs are engineered as software entities [i.8].
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 RC; and
• clause 8 describes the interface definition.
While UML is used for defining the information model and protocol related to RRFI, other modelling languages could
be used as well.
5 System Identification
5.1 Radio Computer Structure
Figure 5.1 illustrates how URA and RF Transceiver interacts with each other using RRFI.
ETSI
10 ETSI EN 303 146-2 V1.2.1 (2016-06)
Figure 5.1: Interconnection between URA and RF Transceiver
using RRFI for reconfigurable MD
As shown in figure 5.1, RRFI can support up to 5 kinds of services depending on the applicable MDRC [1].
A Reconfigurable MD shall support all the services as required by the corresponding MDRC as shown in table 5.1 and
fully detailed in clause 8 of the present document. In case that a reconfigurable MD supports multiple MDRCs, the
concerned reconfigurable MD shall support all the services as defined in table 5.1.
Table 5.1: Required services of RRFI according to each MDRC
Mobile Device Antenna
Spectrum Power Control Tx/Rx Chain RVM Protection
Reconfiguration Management
Control services services Control services services
Class services
MDRC-0 No No No No No
MDRC-1 Yes Yes No No Yes
Yes
MDRC-2, MDRC-5 Yes Yes Yes Yes
(see note)
MDRC-3, MDRC-6 Yes Yes Yes Yes Yes
MDRC-4, MDRC-7 Yes Yes Yes Yes Yes
NOTE: Among the various Tx/Rx Chain Control services, only the service related with Tx/Rx timing is required in this
case.
A corresponding summary of the services is given below.
• Spectrum Control services
These services are used to set up spectrum-related parameters such as carrier frequency, bandwidth, sampling
frequency, etc. that will be determined according to the URAs they are related to.
• Power Control services
These services are used to set up RF power-related parameters such as maximum transmit (Tx) power level, Tx
power level per antenna, receive (Rx) gain, etc. Specific power schemes which have to be controlled according
to the communication circumstance around the reconfigurable MD are also included in the Power Control
services.
• Antenna Management services
These services are used to determine the antenna configuration. Antenna radiation pattern, antenna gain,
antenna direction, sector configuration, polarization, frequency range, etc. are some factors to be considered in
the Antenna Management services.
NOTE: Antenna Management services depend on the configurability of the antenna.
ETSI
11 ETSI EN 303 146-2 V1.2.1 (2016-06)
• Tx/Rx Chain Control services
These services are used to provide parameters related to real-time control of the RF transceiver chain.
Parameters to be controlled using the Tx/Rx Chain Control services include (but are not limited to) Tx
start/stop time, Rx start/stop time, spectrum- and/or power-related values.
• RVM Protection services
These services are used to provide parameters related to the selection of RVM protection class. Parameters to
be controlled using the RVM Protection services include (but are not limited to) selection and/or request of RF
protection class as well as, RF Front-end indication of input data signals modification.
The clauses 5.2 to 5.4 describe the components/entities shown in figure 5.1.
5.2 URA
RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework
(depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD
perspective, those RAs are called URAs [i.8].
5.3 RF Transceiver
RF Transceiver, which includes transceiver chain(s), is part of the radio platform in RC that transforms, in Tx mode, the
baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal.
5.4 RF Interfaces
The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between
SM
base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRF specification defining the
interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a mobile device. RRFI defined in the present
document complements such RF interfaces by defining services which are required for reconfigurable MDs.
5.5 Radio Computer RF System Requirement Mapping
The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and
described in clause 6.5 of ETSI EN 302 969 [1].
NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 302 969 [1] are not
related to the RF Interface defined in the present document and therefore do not appear in table 5.2.
Table 5.2: Mapping of RC Components to the system requirements described in ETSI EN 302 969 [1]
Entity/Component/Unit System Requirements [1] Comments
Unified Radio Applications R-FUNC-RFT-02 Radio Application selects a suitable number of
antenna inputs/outputs. The requirement is
described in clause 6.5.2 of ETSI EN 302 969 [1].
RF Transceiver R-FUNC-RFT-03 The reconfigurable MD supports multiple Radio
Applications using distinct frequency bands. The
requirement is described in clause 6.5.3 of ETSI
EN 302 969 [1].
R-FUNC-RFT-04 RF transceiver manages input/output signals
from/to one or several Radio Applications. The
requirement is described in clause 6.5.4 of ETSI
EN 302 969 [1].
Reconfigurable RF Interface R-FUNC-RFT-01, The RRFI provides a suitable interface for RF
R-FUNC-RFT-07 transceiver configuration. The requirement is
described in clauses 6.5.1 and 6.5.7 of ETSI
EN 302 969 [1].
R-FUNC-RFT-09 The RRFI supports a suitable selection of an RF
protection class. The requirement is described in
clause 6.5.9 of ETSI EN 302 969 [1].
ETSI
12 ETSI EN 303 146-2 V1.2.1 (2016-06)
6 Notational Tools
6.1 Notational Tool for Information Model Classes
Table 6.1 shows a template for defining information model classes [i.4]. 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.
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.
ETSI
13 ETSI EN 303 146-2 V1.2.1 (2016-06)
6.2 Notational Tool for Interface Classes
Table 6.2 shows a template for defining interface classes for RRFI. Each interface class for RRFI will be defined in
clause 8.7 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:
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 RC classes related to RRFI which are required to support Software
Reconfiguration.
ETSI
14 ETSI EN 303 146-2 V1.2.1 (2016-06)
<>
RCProf ile
IRRF I
- RCID: Name Type
RadioComput er
RCMeas urements
RCCap abilit ies
-listOfActiveMeasurements:
1 -listOfSupportedOptions: RCOptions
ActiveMeasurementsList
-listOfSupportedRadioInterfaces:
RadioInterfaces
-listOfSupportedChannels: ChannelIDs
-hardwareProfile: HardwareInfo
-softwareProfile: SoftwareInfo
RCConfi gur ation
Channe l
0.*
Channe lP ro f ile
Link
-channelID: NameType
0.*
-channelFrequecyRange:
FrequencyRange
-radioInterface:
RadioInterface
RF Conf igurat ion -cellID: NameType
LinkP r of il e
-linkID: NameType
-cellID: NameType
-associatedChannelID:
Channe lMeasur ements
TxP ath
OptiaonlObjectName
-listOfChannelMeasurements:
-linkDirection : Direction
-txStartTime: TxStartTime
0,1
ChannelMeasurementsList
-CarrierFrequecy: Frequency
-txStopTime: TxStopTime
-nominalRFPower: -appliedMeasurementConfiguration:
C onfi gu ra ti o nM esur ements
AnaloguePower
-samplingRate: SamplingRate
RxPath
-bandwidth: Bandwidth
-rxStartTime: RxStartTime
1 Antenna
-rxStopTime: RxStopTime
1.*
LinkMe asure me nts
-receiveBLER: RxBLER
-trasmitPower: TxPower AntennaPr ofi le
-receiveSINR: RxSINR
-antennaID:
-transmittedBits: TxBits
NameType
Figure 7.1: UML class diagram for RC classes related to RRFI
The RC classes related to RRFI are defined as follows:
• 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.
ETSI
15 ETSI EN 303 146-2 V1.2.1 (2016-06)
• RCCapabilities
This class contains information about RC 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, centre 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 Link 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 RC. 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 class as members (0.*). 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 Identification (ID),
serving cell ID, channel used, etc. Each instance of Link class shall have only one instance of LinkProfile class
as a member.
• LinkMeasurements
This class contains current measurements (instantaneous measurement data and related metadata) 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 shall have only one instance of LinkMeasurements class as
a member.
• RFConfiguration
This class contains information about the configuration of the RF transceiver. Each instance of Link class shall
have only one instance of RFConfiguration class as a member.
ETSI
16 ETSI EN 303 146-2 V1.2.1 (2016-06)
• TxPath
This class contains information about one transmit path. Each instance of RFConfiguration class has zero or
one instance of TxPath class as a member (0,1).
• RxPath
This class contains information about one receive path. Each instance of RFConfiguration class shall have only
one instance of RxPath class as a member.
• RCMeasurements
This class contains current measurements (instantaneous measurement data and related metadata) related to
reconfigurable MD such as battery capacity, user mobility, MD location determination, and connection history
information. Each instance of RadioComputer class shall have only one instance of RCMeasurements class as
a member.
• 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.
NOTE: The Channel Class is separate from the Link Class, but the Channel Measurements may be based on any
MD configuration which may or may not be used for the final Link Configuration.
7.2 Class Definitions for Information Model
Each class of RC can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of
figure 7.1 which specifies the relations among all the classes of RC. RC classes defined in this way are shown in
tables 7.1 to 7.16.
Table 7.1: RadioComputer Class
Class RadioComputer
This class contains all URA related information about resources and interactions related to hardware
and software of a reconfigurable MD.
DERIVED FROM
ATTRIBUTES
CONTAINED IN
RCCapabilities [1], RCConfiguration [1], RCMeasurements [1],
CONTAINS
Channel [0.*]
SUPPORTED EVENTS
ETSI
17 ETSI EN 303 146-2 V1.2.1 (2016-06)
Table 7.2: RCCapabilities Class
Class RCCapabilities
This class contains information about RC capabilities including hardware, software, transmission and
measurement capabilities.
DERIVED FROM
ATTRIBUTES
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 this RC.
Value type: Possible access: Default value:
listOfSupportedChannels
ChannelIDsList Read-Write Not specified
This attributes describes frequency channels supported by this RC.
Value type: Possible access: Default value:
hardwareProfile
HardwareInfo Read-Write Not specified
This attributes describes hardware capabilities of this RC.
Value type: Possible access: Default value:
softwareProfile
SoftwareInfo Read-Write Not specified
This attributes describes software capabilities of this RC.
CONTAINED IN RadioComputer
CONTAINS
SUPPORTED EVENTS
Table 7.3: Channel Class
Class Channel
This class describes one frequency channel that may or may not have active connections on it.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RadioComputer
CONTAINS ChannelProfile [1], ChannelMeasurements [1], Antenna [1.*]
SUPPORTED EVENTS
Table 7.4: ChannelProfile Class
Class ChannelProfile
This class contains general information about this frequency channel.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
channelID
NameType Read Not specified
This attribute describes ID of channel.
Value type: Possible access: Default value:
channelFrequencyRange
FrequencyRange Read Not specified
This attribute describes a value of channel frequency range.
Value type: Possible access: Default value:
radioInterface
RadioInterface Read Not specified
This attribute describes a radio interface.
Value type: Possible access: Default value:
cellID
NameType Read Not specified
This attribute describes ID of connected cell.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
ETSI
18 ETSI EN 303 146-2 V1.2.1 (2016-06)
Table 7.5: ChannelMeasurements Class
Class ChannelMeasurements
This class contains current measurements related to this frequency channel.
DERIVED FROM
ATTRIBUTES
Default
Value type: Possible access:
listOfChannelMeasurements value:
ChannelMeasurementsList Read
Not specified
This attribute describes a list of channel measurements.
Default
Value type: Possible access:
appliedMeasurementsConfiguration value:
ConfigurationMeasurements Read
Not specified
This attribute describes configuration option of the MD, e.g. which Antenna(s) have been used, which
RF front-end(s) have been used, etc.
CONTAINED IN Channel
CONTAINS
SUPPORTED EVENTS
Table 7.6: Antenna Class
Class Antenna
This class contains information about antenna selection.
DERIVED FROM
ATTRIBUTES
CONTAINED IN Channel
AntennaProfile [1]
CONTAINS
SUPPORTED EVENTS
Table 7.7: AntennaProfileClass
Class AntennaProfile
This class contains general information about this antenna.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
antennaID
NameType Read Not specified
This attribute describes ID of antenna.
CONTAINED IN Antenna
CONTAINS
SUPPORTED EVENTS
Table 7.8: RCConfigurationClass
Class RCConfiguration
This class contains information about the current configuration of RC.
DERIVED FROM
ATTRIBUTES
RadioComputer
CONTAINED IN
CONTAINS Link [0.*]
SUPPORTED EVENTS
ETSI
19 ETSI EN 303 146-2 V1.2.1 (2016-06)
Table 7.9: LinkClass
Class Link
This class contains information about one active Radio Application and corresponding connection
between Reconfigurable Radio terminal and RANs.
DERIVED FROM
ATTRIBUTES
CONTAINED IN RCConfiguration
CONTAINS LinkProfile [1], LinkMeasurements [1], RFConfiguration [1]
SUPPORTED EVENTS
Table 7.10: LinkProfileClass
Class LinkProfile
This class contains general information about this active connection.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
linkID
NameType Read Not specified
This attribute describes ID of link about activated connection.
Value type: Possible access: Default value:
cellID
NameType Read-Write Not specified
This attribute describes ID connected cell.
Value type: Possible access: Default value:
associatedChannelID
OptionalObjectName Read-Add-Remove Not specified
This attribute describes ID of associated channel.
Value type: Possible access: Default value:
linkDirection
Direction Read Not specified
This attribute describes a direction of link.
Value type: Possible access: Default value:
carrierFrequency
FrequencyRange Read-Write Not specified
This attribute describes a value of carrier frequency.
Value type: Possible access: Default value:
nominalRFPower
AnaloguePower Read Not specified
This attribute describes a value of nominal power.
Value type: Possible access: Default value:
samplingRate
SamplingRate Read-Write Not specified
This attribute describes a value of sampling rate.
Value type: Possible access: Default value:
bandwidth
Bandwidth Read-Write Not specified
This attribute describes a value of bandwidth.
CONTAINED IN Link
CONTAINS
SUPPORTED EVENTS
ETSI
20 ETSI EN 303 146-2 V1.2.1 (2016-06)
Table 7.11: LinkMeasurementsClass
Class LinkMeasurements
This class contains current measurements related to this active connection.
DERIVED FROM
ATTRIBUTES
Value type: Possible access: Default value:
receiveBLER
RxBLER Read-Write Not specified
This attribute describes a value of BLER for received data.
Value type: Possible access: Default value:
transmitPower
TxPower Read-Write Not specified
This attribute describes a power of transmit signal.
Value type: Possible access: Default value:
receiveSINR
RxSINR Read-Write Not specified
This attribute describes a value of SINR for received data.
Value type: Possible access: Default value:
transmittedBits
Tx
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Reconfigurable Radio Systems (RRS) - Mobile Device Information Models and Protocols - Part 2: Reconfigurable Radio Frequency Interface (RRFI)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-2 V1.2.1 (2016-06)SIST EN 303 146-2 V1.2.1:2016en01-september-2016SIST EN 303 146-2 V1.2.1:2016SLOVENSKI
STANDARD
EUROPEAN STANDARD SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 2
Reference REN/RRS-0246 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.
© European Telecommunications Standards Institute 2016. All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM 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. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-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 . 8 5 System Identification . 9 5.1 Radio Computer Structure . 9 5.2 URA . 11 5.3 RF Transceiver . 11 5.4 RF Interfaces . 11 5.5 Radio Computer RF System Requirement Mapping . 11 6 Notational Tools . 12 6.1 Notational Tool for Information Model Classes . 12 6.2 Notational Tool for Interface Classes . 13 7 Information Model for Radio Computer . 13 7.1 Radio Computer . 13 7.2 Class Definitions for Information Model . 16 8 Interface Definition . 21 8.1 Interface Overview . 21 8.2 Spectrum Control Services . 24 8.2.1 Overview on Spectrum Control Services . 24 8.2.2 Messages for Spectrum Control Services . 24 8.3 Power Control Services . 25 8.3.1 Overview on Power Control Services . 25 8.3.2 Messages for Power Control Services . 25 8.4 Antenna Management Services . 25 8.4.1 Overview on Antenna Management Services . 25 8.4.2 Messages for Antenna Management Services. 26 8.5 Tx/Rx Chain Control Services. 26 8.5.1 Overview on Tx/Rx Chain Control Services . 26 8.5.2 Messages for Tx/Rx Chain Control Services . 26 8.6 RVM Protection Services . 27 8.6.1 Overview on RVM Protection Services . 27 8.6.2 Messages for RVM Protection Services . 28 8.7 Class Definitions for Interface . 28 Annex A (informative): Abstract Data Definitions . 31 Annex B (informative): RRFI Qualification Methods for Validation . 34 History . 35
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 4 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 (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. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS). The present document is part 2 of a multi-part deliverable covering the Mobile Device (MD) information models and protocols, as identified below: ETSI EN 303 146-1:
"Multiradio Interface (MURI)"; ETSI EN 303 146-2: "Reconfigurable Radio Frequency Interface (RRFI)"; ETSI EN 303 146-3:
"Unified Radio Application Interface (URAI)"; ETSI TS 103 146-4:
"Radio Programming Interface (RPI)".
National transposition dates Date of adoption of this EN: 30 May 2016 Date of latest announcement of this EN (doa): 31 August 2016 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
28 February 2017 Date of withdrawal of any conflicting National Standard (dow): 28 February 2017
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 ETSI EN 303 146-2 V1.2.1 (2016-06) 5 1 Scope The present document defines an information model and protocol for reconfigurable radio frequency interface for reconfigurable MDs. 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.8]. 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 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. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 969 (V1.2.1): "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] Recommendation ITU-T Q.1290: "Glossary of Terms used in the Definition of Intelligent Networks". [i.3] ETSI TR 102 839: "Reconfigurable Radio Systems (RRS); Multiradio Interface for Software Defined Radio (SDR) Mobile Device Architecture and Services". [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] ETSI EN 303 146-1: "Reconfigurable Radio Systems (RRS); Mobile Device Information Models and Protocols; Part 1: Multiradio Interface (MURI)". [i.6] DigRFSM Working Group: "MIPI® Alliance Specification for DigRFSM v4". [i.7] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 6 [i.8] ETSI EN 303 095 (V1.2.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Architecture for Mobile Devices". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Application Processor (AP): part of mobile device hardware working under OS control and on which User Applications, among others, are executed 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 Recommendation ITU-T Q.1290 [i.2]. Communication Services Layer (CSL): 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 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 (RC): 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), Multiradio Controller (MRC) and Resource Manager (RM) which is typically part of OS. Radio Frequency (RF) transceiver: part of radio platform converting, for transmission, baseband signals into radio signals, and, for reception, radio signals into baseband signals Radio Operating System (ROS): any appropriate OS empowered by RCF NOTE: ROS provides RCF capabilities as well as traditional management capabilities related to management of RP such as resource management, file system support, unified access to hardware resources, etc. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 7 radio platform: part of mobile device hardware which relates to radio processing capability, including programmable components, hardware accelerators, RF transceiver, and antenna(s) NOTE: A Radio Platform is a piece of hardware capable of generating RF signals or receiving RF signals. By nature, it is heterogeneous hardware including different processing elements such as fixed accelerators, e.g. Application-Specific Integrated Circuit (ASIC), or reconfigurable accelerators, e.g. FPGAs, etc. Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions NOTE: An RVM may be implemented as a controlled execution environment which allows the selection of a trade-off between flexibility of base band code development and required (re-)certification efforts.
reconfigurable Mobile Device (MD): 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. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement ACKM ACKnowledgement with Modification AP Application Processor ASIC Application-Specific Integrated Circuit ASN.1 Abstract Syntax Notation One BBIC Base-Band Integrated Circuit BLER Block Error Rate CSL Communication Services Layer EU European Union MD Mobile Device MDRC Mobile Device Reconfiguration Class MIMO Multiple Input Multiple Output MPM Mobility Policy Manager MURI MUltiRadio Interface NACK Negative ACKnowledgement OOB Out Of Band OS Operating System RA Radio Application RAN Radio Access Network RAP Radio Application Package RAT Radio Access Technology RC Radio Computer RCF Radio Control Framework RF Radio Frequency RFIC Radio Frequency Integrated Circuit ROS Radio Operating System RPI Radio Programming Interface RRFI Reconfigurable Radio Frequency Interface RVM Radio Virtual Machine RX Reception SINR Signal to Interference plus Noise Ratio TR Technical Report UML Unified Modeling Language URA Unified Radio Applications URAI Unified Radio Applications Interface SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 8 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 [1]. 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.
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.5]. • RRFI for interfacing URA and RF Transceiver, which is the scope of the present document. • URAI for interfacing URA and RCF [i.3]. • RPI for allowing an independent and uniform production of RAs [i.3]. The present document defines RRFI. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 9 RadioComputer<>IMURI<>IRRFI<>IRPI<>IURAI Figure 4.2: UML class diagram for RC interfaces Figure 4.2 illustrates UML class diagram for RC interfaces. The reconfigurable MD may be seen as a RC where individual URAs are engineered as software entities [i.8]. 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 RC; and • clause 8 describes the interface definition. While UML is used for defining the information model and protocol related to RRFI, other modelling languages could be used as well. 5 System Identification 5.1 Radio Computer Structure Figure 5.1 illustrates how URA and RF Transceiver interacts with each other using RRFI. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 10
Figure 5.1: Interconnection between URA and RF Transceiver
using RRFI for reconfigurable MD As shown in figure 5.1, RRFI can support up to 5 kinds of services depending on the applicable MDRC [1].
A Reconfigurable MD shall support all the services as required by the corresponding MDRC as shown in table 5.1 and fully detailed in clause 8 of the present document. In case that a reconfigurable MD supports multiple MDRCs, the concerned reconfigurable MD shall support all the services as defined in table 5.1. Table 5.1: Required services of RRFI according to each MDRC Mobile Device Reconfiguration Class Spectrum Control services Power Control services Antenna Management services Tx/Rx Chain Control services RVM Protection services MDRC-0 No No No No No MDRC-1 Yes Yes No No Yes MDRC-2, MDRC-5 Yes Yes Yes Yes (see note) Yes MDRC-3, MDRC-6 Yes Yes Yes Yes Yes MDRC-4, MDRC-7 Yes Yes Yes Yes Yes NOTE: Among the various Tx/Rx Chain Control services, only the service related with Tx/Rx timing is required in this case.
A corresponding summary of the services is given below. • Spectrum Control services These services are used to set up spectrum-related parameters such as carrier frequency, bandwidth, sampling frequency, etc. that will be determined according to the URAs they are related to. • Power Control services These services are used to set up RF power-related parameters such as maximum transmit (Tx) power level, Tx power level per antenna, receive (Rx) gain, etc. Specific power schemes which have to be controlled according to the communication circumstance around the reconfigurable MD are also included in the Power Control services. • Antenna Management services These services are used to determine the antenna configuration. Antenna radiation pattern, antenna gain, antenna direction, sector configuration, polarization, frequency range, etc. are some factors to be considered in the Antenna Management services.
NOTE: Antenna Management services depend on the configurability of the antenna. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 11 • Tx/Rx Chain Control services These services are used to provide parameters related to real-time control of the RF transceiver chain. Parameters to be controlled using the Tx/Rx Chain Control services include (but are not limited to) Tx start/stop time, Rx start/stop time, spectrum- and/or power-related values.
• RVM Protection services These services are used to provide parameters related to the selection of RVM protection class. Parameters to be controlled using the RVM Protection services include (but are not limited to) selection and/or request of RF protection class as well as, RF Front-end indication of input data signals modification. The clauses 5.2 to 5.4 describe the components/entities shown in figure 5.1. 5.2 URA RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework (depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD perspective, those RAs are called URAs [i.8]. 5.3 RF Transceiver RF Transceiver, which includes transceiver chain(s), is part of the radio platform in RC that transforms, in Tx mode, the baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal. 5.4 RF Interfaces The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRFSM specification defining the interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a mobile device. RRFI defined in the present document complements such RF interfaces by defining services which are required for reconfigurable MDs. 5.5 Radio Computer RF System Requirement Mapping The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and described in clause 6.5 of ETSI EN 302 969 [1].
NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 302 969 [1] are not related to the RF Interface defined in the present document and therefore do not appear in table 5.2. Table 5.2: Mapping of RC Components to the system requirements described in ETSI EN 302 969 [1] Entity/Component/Unit System Requirements [1] Comments Unified Radio Applications R-FUNC-RFT-02 Radio Application selects a suitable number of antenna inputs/outputs. The requirement is described in clause 6.5.2 of ETSI EN 302 969 [1]. RF Transceiver R-FUNC-RFT-03 The reconfigurable MD supports multiple Radio Applications using distinct frequency bands. The requirement is described in clause 6.5.3 of ETSI EN 302 969 [1]. R-FUNC-RFT-04 RF transceiver manages input/output signals from/to one or several Radio Applications. The requirement is described in clause 6.5.4 of ETSI EN 302 969 [1]. Reconfigurable RF Interface R-FUNC-RFT-01, R-FUNC-RFT-07 The RRFI provides a suitable interface for RF transceiver configuration. The requirement is described in clauses 6.5.1 and 6.5.7 of ETSI EN 302 969 [1]. R-FUNC-RFT-09 The RRFI supports a suitable selection of an RF protection class. The requirement is described in clause 6.5.9 of ETSI EN 302 969 [1]. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 12 6 Notational Tools 6.1 Notational Tool for Information Model Classes Table 6.1 shows a template for defining information model classes [i.4]. 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.
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. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 13 6.2 Notational Tool for Interface Classes Table 6.2 shows a template for defining interface classes for RRFI. Each interface class for RRFI will be defined in clause 8.7 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:
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 RC classes related to RRFI which are required to support Software Reconfiguration.
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 14 <>IRRFIRadioComputerRCMeasurements-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: Name Type1 Figure 7.1: UML class diagram for RC classes related to RRFI The RC classes related to RRFI are defined as follows: • 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. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 15 • RCCapabilities
This class contains information about RC 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, centre 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 Link 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 RC. 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 class as members (0.*). 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 Identification (ID), serving cell ID, channel used, etc. Each instance of Link class shall have only one instance of LinkProfile class as a member. • LinkMeasurements
This class contains current measurements (instantaneous measurement data and related metadata) 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 shall have only one instance of LinkMeasurements class as a member. • RFConfiguration
This class contains information about the configuration of the RF transceiver. Each instance of Link class shall have only one instance of RFConfiguration class as a member. SIST EN 303 146-2 V1.2.1:2016
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 16 • TxPath
This class contains information about one transmit path. Each instance of RFConfiguration class has zero or one instance of TxPath class as a member (0,1). • RxPath
This class contains information about one receive path. Each instance of RFConfiguration class shall have only one instance of RxPath class as a member. • RCMeasurements
This class contains current measurements (instantaneous measurement data and related metadata) related to reconfigurable MD such as battery capacity, user mobility, MD location determination, and connection history information. Each instance of RadioComputer class shall have only one instance of RCMeasurements class as a member. • 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. NOTE: The Channel Class is separate from the Link Class, but the Channel Measurements may be based on any MD configuration which may or may not be used for the final Link Configuration. 7.2 Class Definitions for Information Model Each class of RC can be defined using the template presented in clause 6.1 and in accordance with the UML diagram of figure 7.1 which specifies the relations among all the classes of RC. RC classes defined in this way are shown in tables 7.1 to 7.16. Table 7.1: RadioComputer Class Class RadioComputer This class contains all URA related information about resources and interactions related to hardware and software of a reconfigurable MD. DERIVED FROM
ATTRIBUTES CONTAINED IN
CONTAINS RCCapabilities [1], RCConfiguration [1], RCMeasurements [1], Channel [0.*]
SUPPORTED EVENTS
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 17 Table 7.2: RCCapabilities Class Class RCCapabilities This class contains information about RC capabilities including hardware, software, transmission and measurement capabilities. DERIVED FROM
ATTRIBUTES listOfSupportedOptions Value type: RCOptionsList Possible access: Read-Write Default value: Not specified This attribute describes a list of supported options. listOfSupportedRadioInterfaces Value type: RadioInterfacesList Possible access: Read-Write Default value: Not specified This attribute describes radio interfaces supported by this RC. listOfSupportedChannels Value type: ChannelIDsList Possible access: Read-Write Default value: Not specified This attributes describes frequency channels supported by this RC. hardwareProfile Value type: HardwareInfo Possible access: Read-Write Default value: Not specified This attributes describes hardware capabilities of this RC. softwareProfile Value type: SoftwareInfo Possible access: Read-Write Default value: Not specified This attributes describes software capabilities of this RC. CONTAINED IN RadioComputer CONTAINS
SUPPORTED EVENTS
Table 7.3: Channel Class Class Channel This class describes one frequency channel that may or may not have active connections on it. DERIVED FROM
ATTRIBUTES CONTAINED IN RadioComputer CONTAINS ChannelProfile [1], ChannelMeasurements [1], Antenna [1.*] SUPPORTED EVENTS
Table 7.4: ChannelProfile Class Class ChannelProfile This class contains general information about this frequency channel. DERIVED FROM
ATTRIBUTES channelID Value type: NameType Possible access: Read Default value: Not specified This attribute describes ID of channel. channelFrequencyRange Value type: FrequencyRange Possible access: Read Default value: Not specified This attribute describes a value of channel frequency range. radioInterface Value type: RadioInterface Possible access: Read Default value: Not specified This attribute describes a radio interface. cellID Value type: NameType Possible access: Read Default value: Not specified This attribute describes ID of connected cell. CONTAINED IN Channel CONTAINS
SUPPORTED EVENTS
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 18 Table 7.5: ChannelMeasurements Class Class ChannelMeasurements This class contains current measurements related to this frequency channel. DERIVED FROM
ATTRIBUTES listOfChannelMeasurements Value type: ChannelMeasurementsList Possible access: Read Default value: Not specified This attribute describes a list of channel measurements. appliedMeasurementsConfiguration Value type: ConfigurationMeasurements Possible access: Read Default value: Not specified This attribute describes configuration option of the MD, e.g. which Antenna(s) have been used, which RF front-end(s) have been used, etc. CONTAINED IN Channel CONTAINS
SUPPORTED EVENTS
Table 7.6: Antenna Class Class Antenna This class contains information about antenna selection. DERIVED FROM
ATTRIBUTES CONTAINED IN Channel CONTAINS AntennaProfile [1] SUPPORTED EVENTS
Table 7.7: AntennaProfileClass Class AntennaProfile This class contains general information about this antenna. DERIVED FROM
ATTRIBUTES antennaID Value type: NameType Possible access: Read Default value: Not specified This attribute describes ID of antenna. CONTAINED IN Antenna CONTAINS
SUPPORTED EVENTS
Table 7.8: RCConfigurationClass Class RCConfiguration This class contains information about the current configuration of RC. DERIVED FROM
ATTRIBUTES CONTAINED IN RadioComputer CONTAINS Link [0.*] SUPPORTED EVENTS
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 19 Table 7.9: LinkClass Class Link This class contains information about one active Radio Application and corresponding connection between Reconfigurable Radio terminal and RANs. DERIVED FROM
ATTRIBUTES CONTAINED IN RCConfiguration CONTAINS LinkProfile [1], LinkMeasurements [1], RFConfiguration [1] SUPPORTED EVENTS
Table 7.10: LinkProfileClass Class LinkProfile This class contains general information about this active connection. DERIVED FROM
ATTRIBUTES linkID Value type: NameType Possible access: Read Default value: Not specified This attribute describes ID of link about activated connection. cellID Value type: NameType Possible access: Read-Write Default value: Not specified This attribute describes ID connected cell. associatedChannelID Value type: OptionalObjectName Possible access: Read-Add-Remove Default value: Not specified This attribute describes ID of associated channel. linkDirection Value type: Direction Possible access: Read Default value: Not specified This attribute describes a direction of link. carrierFrequency Value type: FrequencyRange Possible access: Read-Write Default value: Not specified
This attribute describes a value of carrier frequency.
nominalRFPower Value type: AnaloguePower Possible access: Read Default value: Not specified This attribute describes a value of nominal power. samplingRate Value type: SamplingRate Possible access: Read-Write Default value: Not specified This attribute describes a value of sampling rate. bandwidth Value type: Bandwidth Possible access: Read-Write Default value: Not specified This attribute describes a value of bandwidth. CONTAINED IN Link CONTAINS
SUPPORTED EVENTS
ETSI ETSI EN 303 146-2 V1.2.1 (2016-06) 20 Table 7.11: LinkMeasurementsClass Class LinkMeasurements This class contains current measurements related to this active connection. DERIVED FROM
ATTRIBUTES receiveBLER Value type: RxBLER Possible access: Read-Write Default value: Not specified This attribute describes a value of BLER for received data. transmitPower Value type: TxPower Possible access: Read-Write Default value: Not specified This attribute describes a power of transmit signal. receiveSINR Value type: RxSINR Possible access: Read-Write Default value: Not specified This attribute describes a value of SINR for received data. transmittedBits Value type: TxBits Possible access: Read-Write Default value: Not specified This attribute describes transmitted bits. CONTAINED IN Link CONTAINS
SUPPORTED EVENTS
Table 7.12: RFConfigurationClass Class RFConfiguration This class contains information about the configuration of RF transceiver. DERIVED FROM
ATTRIBUTES CONTAINED IN Link CONTAINS TxPath [0,1], RxPath [1] SUPPORTED EVENTS
Table 7.13: TxPathClass Class TxPath This class describes one transmit path. DERIVED FROM DERIVED FROM ATTRIBUTES txStartTime Value type: TxStartTime Possible access: Read-Write Default value: Not specified This attribute defines the time when the transceiver start transmission. txStopTime Value type: TxStopTime Possible access: Read-Write Default value: Not specified This attribute defines the time when the transceiver stop transmission. CONTAINED IN RFConfiguration CONTAINS
SUPPORTED EVENTS
SIST EN 303 146-2 V1.2.1:201
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...