SIST EN 303 681-3 V1.1.2:2020

SLOVENSKI STANDARD
oSIST prEN 303 681-3 V1.1.2:2020
01-julij-2020
Radijski sistemi z možnostjo preoblikovanja (RRS) - Informacijski modeli in
protokoli za radijsko opremo (RE) za splošno arhitekturo preoblikovanja
programske opreme - 3. del: Splošni enotni radijski aplikacijski vmesnik (gURAI)
Reconfigurable Radio Systems (RRS) - Radio Equipment (RE) information models and

protocols for generalized software reconfiguration architecture - Part 3: generalized

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

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 prevailing version of an ETSI

deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.

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

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

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

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

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

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

oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and

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 Definition of terms, symbols and abbreviations ....................................................................................... 6

3.1 Terms .................................................................................................................................................................. 6

3.2 Symbols .............................................................................................................................................................. 7

3.3 Abbreviations ..................................................................................................................................................... 7

4 Introduction .............................................................................................................................................. 8

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

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

5.2 gURAI System Requirement Mapping............................................................................................................. 10

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

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

6.2 Notational Tool for Interface Classes ............................................................................................................... 11

7 Information Model for Radio Computer ................................................................................................ 12

7.1 Radio Computer ............................................................................................................................................... 12

7.2 Class Definitions for Information Model ......................................................................................................... 15

8 Interface Definition ................................................................................................................................ 21

8.1 Interface Overview ........................................................................................................................................... 21

8.2 Radio Application Management Services ........................................................................................................ 22

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

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

8.3 User Data Flow Services .................................................................................................................................. 23

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

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

8.4 Multiradio Control Services ............................................................................................................................. 24

8.4.1 Overview on Multiradio Control Services .................................................................................................. 24

8.4.2 Messages for Multiradio Control Services .................................................................................................. 25

8.5 Class Definitions for Interface .......................................................................................................................... 25

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

Annex B (informative): gURAI Qualification Methods for Validation ............................................. 31

History .............................................................................................................................................................. 32

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

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

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

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

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

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

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

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

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

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

(RRS), and is now submitted for the combined Public Enquiry and Vote phase of the ETSI standards EN Approval

The present document is part 3 of a multi-part deliverable covering the Radio Equipment (RE) information models and

Date of withdrawal of any conflicting National Standard (dow): 6 months after doa

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

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

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

for radio equipment reconfiguration except for reconfigurable mobile devices which are covered in [i.6] to [i.11]. The

work is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI

EN 303 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI

The present document will be based on ETSI EN 303 146-3 [i.10] and provide a generalized interface definition for the

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 documents which are not found to be publicly available in the expected location might be found at

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

[1] ETSI EN 303 641: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration

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

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

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

[i.1] ETSI TR 103 585: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration

[i.2] ETSI EN 303 648: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration

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

Device Distributed Decision Making for Optimized Radio Resource Usage in Heterogeneous

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

[i.5] Directive 2014/53/EU of the European Parliament and of the Council of 16 April 2014 on the

harmonisation of the laws of the Member States relating to the making available on the market of

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

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

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

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

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

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

[i.12] ETSI EN 303 681-1: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information

models and protocols for generalized software reconfiguration architecture; Part 1: generalized

[i.13] ETSI EN 303 681-2: "Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information

models and protocols for generalized software reconfiguration architecture; Part 3: generalized

[i.14] ETSI EN 303 681-4: "Reconfigurable Radio Systems (RRS); adio Equipment (RE) information

models and protocols for generalized software reconfiguration architecture; Part 4: generalized

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

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

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

NOTE 2: Peer equipment is any communication counterpart of a reconfigurable Radio Equipment. It can be

reached by establishing a logical communication link (i.e. an association) between the reconfigurable

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

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

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

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

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

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

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

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

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

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

Radio Equipment (RE): "an electrical or electronic product, which intentionally emits and/or receives radio waves for

the purpose of radio communication and/or radiodetermination, or an electrical or electronic product which must be

completed with an accessory, such as antenna, so as to intentionally emit and/or receive radio waves for the purpose of

NOTE: The definition above is as defined in the Radio Equipment Directive, Article 2(1)(1) [i.5].

reconfigurable mobile device: mobile device with radio communication capabilities providing support for radio

NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets, and

reconfigurable Radio Equipment: Radio Equipment with radio communication capabilities providing support for

NOTE: Reconfigurable Radio Equipment includes Smartphones, Feature phones, Tablets, Laptops, Connected

Unified Radio Application (URA): Radio Application which complies with the reconfigurable RE framework defined

ITU-T International Telecommunication Union Telecommunication Standardization Sector

A reconfigurable RE is capable of running multiple radios simultaneously, changing the set of radios by loading new

Radio Application Packages (RAP) and setting their parameters. All Radio Applications (RAs) are called Unified Radio

Applications (URAs) when they exhibit a common behaviour from the reconfigurable RE's point of view in ETSI

EN 303 648 [i.2]. In order to run multiple URAs, the reconfigurable RE will include Communication Services Layer

(CSL), Radio Control Frameworks (RCFs), Radio Platforms and 4 sets of interfaces for their interconnection.

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

• gRPI for allowing an independent and uniform production of RAs (in ETSI EN 303 681-4 [i.14]).

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

multiple Radio Computers where individual URAs are engineered as software entities in ETSI EN 303 648 [i.2].

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

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

Figure 5.1: Interconnection between RCF and URA using gURAI for Reconfigurable RE

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

URA functions such as reporting of discovered Peer Equipment's, creating/terminating association with

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

URA, or used by URA to transmit received user data to FC. These services also include management of

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

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

Flow Controller R-FUNC-RAT-05 The requirement is described in clause 6.1.5 of [1].

Multiradio Controller R-FUNC-RAT-01 The requirement is described in clause 6.1.1 of [1].

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

In the present document, information model classes are used as defined in annex B.1 of IEEE 1900.4 -2009 [i.3].

Table 6.1 shows a template for defining interface classes for gURAI. Each interface class for gURAI will be defined in

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

• 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

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

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

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