ETSI TS 103 850 V1.1.1 (2022-10)

Reconfigurable Radio Systems (RRS); Definition of Radio Application Package

DTS/RRS-0133

General Information

• Status: Not Published
• Technical Committee: RRS 1 - RRS System Aspects & Cognitive functionalities
• Current Stage: 12 - Completion
• Due Date: 14-Oct-2022
• Completion Date: 06-Oct-2022

Standards Content (Sample)

ETSI TS 103 850 V1.1.1 (2022-10)






TECHNICAL SPECIFICATION
Reconfigurable Radio Systems (RRS);
Definition of Radio Application Package

---------------------- Page: 1 ----------------------
2 ETSI TS 103 850 V1.1.1 (2022-10)

Reference
DTS/RRS-0133
Keywords
radio, RAP, RRS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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 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
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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 850 V1.1.1 (2022-10)
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 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Usage of Radio Application Packages . 7
4.1 Context . 7
4.2 Reconfiguration Classes . 8
5 Definition of Radio Application Packages . 9
5.1 Content . 9
5.2 Tree Structure . 10
5.2.1 Introduction. 10
5.2.2 Top Level . 11
5.2.3 Tree - Header Section . 11
5.2.4 Tree - Security Section . 12
5.2.5 Tree - Unified Radio Application (URA) Code Section . 13
5.2.6 Tree - Manufacturer Information Section . 15
5.2.7 Tree - Initial Profile Section . 15
5.3 Internal Structure . 15
5.3.1 Introduction and conventions . 15
5.3.2 Radio Application Package (RAP) Header . 17
5.3.3 Security Section . 17
5.3.4 Unified Radio Application (URA) Code Section. 18
5.3.5 Manufacturer Information Section . 19
5.3.6 Initial Profile Section . 20
5.4 Format . 20
History . 23

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 850 V1.1.1 (2022-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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 of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio
Systems (RRS).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 850 V1.1.1 (2022-10)
1 Scope
This Technical Specification details the format of a Radio Application Package (RAP).
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 436 (V1.2.1): "Reconfigurable Radio Systems (RRS); Security requirements for
reconfigurable radios".
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 EN 303 641 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
reconfiguration requirements".
[i.2] ETSI EN 303 648 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
reconfiguration architecture".
[i.3] ETSI EN 303 681-1 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
information models and protocols for generalized software reconfiguration architecture; Part 1:
generalized Multiradio Interface (gMURI)".
[i.4] ETSI EN 303 681-2 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
information models and protocols for generalized software reconfiguration architecture;
Part 2: generalized Reconfigurable Radio Frequency Interface (gRRFI)".
[i.5] ETSI EN 303 681-3 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
information models and protocols for generalized software reconfiguration architecture;
Part 3: generalized Unified Radio Application Interface (gURAI)".
[i.6] ETSI EN 303 681-4 (V1.1.2): "Reconfigurable Radio Systems (RRS); Radio Equipment (RE)
information models and protocols for generalized software reconfiguration architecture;
Part 4: generalized Radio Programming Interface (gRPI)".
[i.7] ETSI EN 302 969 (V1.3.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related
Requirements for Mobile Devices".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 850 V1.1.1 (2022-10)
[i.8] ETSI EN 303 095 (V1.3.1): "Reconfigurable Radio Systems (RRS); Radio reconfiguration related
architecture for Mobile Devices (MD)".
[i.9] ETSI EN 303 146-1 (V1.3.1): "Reconfigurable Radio Systems (RRS); Mobile Device (MD)
information models and protocols; Part 1: Multiradio Interface (MURI)".
[i.10] ETSI EN 303 146-2 (V1.2.1): "Reconfigurable Radio Systems (RRS); Mobile Device (MD)
information models and protocols; Part 2: Reconfigurable Radio Frequency Interface (RRFI)".
[i.11] ETSI EN 303 146-3 (V1.3.1): "Reconfigurable Radio Systems (RRS); Mobile Device (MD)
information models and protocols; Part 3: Unified Radio Application Interface (URAI)".
[i.12] ETSI EN 303 146-4 (V1.1.2): "Reconfigurable Radio Systems (RRS); Mobile Device (MD)
information models and protocols; Part 4: Radio Programming Interface (RPI)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
administrative RAP metadata: information to help manage a resource, like resource type, permissions, and when and
how it was created
descriptive RAP metadata: descriptive information about a resource, such as a target reconfiguration platform, a
compiler, etc. used for discovery and identification and including elements such as title, abstract, author and keywords
NOTE: A Radio Application Package (RAP) contains metadata itself.
legal RAP metadata: information about the creator, copyright holder, and public licensing, if provided
metadata: data about the data, which can be structural or descriptive
NOTE: In the present document Metadata related to Descriptive RAP metadata, Structural RAP metadata,
Administrative RAP metadata, Legal RAP metadata or a combination of some or all.
Radio Application (RA): software which enforces the generation of the transmit RF signals or the decoding of the
receive RF signals
NOTE 1: The Software is executed on a particular radio platform or an RVM as part of the radio platform.
NOTE 2: RAs might have different forms of representation. They are represented as:
 Source codes including Radio Library calls of Radio Library native implementation and Radio
HAL calls.
 IRs including Radio Library calls of Radio Library native implementation and radio HAL calls.
 Executable codes for a particular radio platform.
radio computer: part of Radio Equipment working under ROS control and on which RAs are executed
NOTE 1: A radio computer typically includes programmable processors, hardware accelerators, peripherals,
software, etc. RF part is considered to be part of peripherals.
NOTE 2: The Radio Platform is the hardware part of the radio computer.
radio reconfiguration: reconfiguration of parameters related to air interface
Radio Virtual Machine (RVM): abstract machine which supports reactive and concurrent executions
NOTE: A 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.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 850 V1.1.1 (2022-10)
reconfigurable equipment: part of a reconfigurable radio system
NOTE: The Reconfigurable Equipment is capable of being dynamically reconfigured to adapt to a wide range of
communications conditions. Such reconfiguration may include the band of operation, the radio access
technology, the associated networks and the services accessed. The reconfiguration may occur after initial
sale deployment and operation.
Reconfigurable Radio System (RRS): radio systems encompassing Software Defined and/or Cognitive Radio Systems
structural RAP metadata: metadata about Radio Application Package structure, indicating how compound objects are
put together, for example, where to find information fields related to Code, Security, etc. and describing the types,
versions, relationships and other characteristics of digital materials
user: user of the Reconfigurable Radio System or the Reconfigurable Equipment
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BE Back End
HAL Hardware Abstraction Layer
HW HardWare
IR Intermediate Representation
MDRC Mobile Device Reconfiguration Class
OS Operating System
RA Radio Application
RAP Radio Application Package
RC Radio Controller
RE Reconfigurable Equipment
RERC Radio Equipment Reconfiguration Class
RF Radio Frequency
ROS Radio Operating System
RRS Reconfigurable Radio System
RVM Radio Virtual Machine
SFB Standard Functional Block
UDFB User Defined Functional Block
URA Unified Radio Application
4 Usage of Radio Application Packages
4.1 Context
A Radio Application Package (RAP) is being used in order to provide new Radio Applications to a target radio
equipment. As detailed in ETSI EN 303 648 [i.2] for radio equipment in general and in ETSI EN 303 095 [i.8] for the
specific case of mobile devices, the RAP is used for distribution and installation of RA codes on the target
reconfigurable REs. During the design time, the RA codes provider will generate a Radio Application Package (RAP)
that includes metadata and RA codes. Note that the Radio Computer (RC) codes are part of the RA codes. In case that
RC codes are executed in the non-real-time environment, they are compiled to be executed in a given Computational
Resources before they are included in the RAP.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 850 V1.1.1 (2022-10)
During the installation time, the RAP will be downloaded from a RadioApp Store and installed in the reconfigurable
RE. The RA codes, including RC codes, and metadata included in the RAP are installed in the reconfigurable RE. Note
that the RC codes are installed in the Computational Resources for operations that do not have to be executed in real
time processing such as context information processing, while the Functional Block (SFBs & UDFBs) codes shall be
installed in the radio computers to be processed in real-time.
The full chain is illustrated in Figure 1 for the case of general radio equipment as defined in ETSI EN 303 648 [i.2]:
generalized Multi Radio Interface (gMURI) generalized Multi Radio Interface (gMURI)
generalized Multi Radio Interface (gMURI)
Radio Control Framework
Radio Control Framework
Radio Control Framework
Radio Apps
generalized
generalized
Source code generalized
Radio
Radio
Radio
Unified Radio
Unified Radio Unified Radio Storage
Storage
Storage
Application
Application Application
Radio Apps
Radio Apps
Radio Apps Interface
Interface Interface
configcode
configcode
configcode
(gURAI)
(gURAI) (gURAI)
Front-end
Radio Library
Compiler normative description Radio Library
... RVM BE
RVM Radio Library BE
Radio Library
RVM BE
implementation native implementation Compiler
implementation native implementation Compiler
implementation native implementation Compiler
Radio OS
Radio OS
Radio OS
Shadow
configcode
단추
Radio Platform
HW Radio Platform
HW Radio Platform
HW Radio Platform
RF part
RF part
RF part
Generalized Radio
Programming Interface
Radio Computer #N
Radio Computer #1
Radio Computer #2
Radio Apps
package
upload
Radio Apps
Store

Figure 1: System architecture for radio computers where Radio Library and Back End (BE)
compiler are included within the radio computers
The present document will define the structure of a RAP that shall be used for the software reconfiguration framework
defined in [i.1] to [i.12].
4.2 Reconfiguration Classes
The information to be provided in a Radio Application Package (RAP) is dependent on the level of reprogrammability
of the concerned platform. In the present document, it is thus referred to the Mobile Device Reconfiguration Classes
(MDRC) as defined in ETSI EN 302 969 [i.7] for reconfigurable Mobile Devices and Radio Equipment Reconfiguration
Classes (RERC) as defined in ETSI EN 303 641 [i.1] for any other reconfigurable equipment. A related summary is
provided in Figures 2 and 3.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 850 V1.1.1 (2022-10)

Figure 2: Definition of Radio Equipment Reconfiguration Classes (RERCs)
according to reconfiguration capabilities [i.1]

Figure 3: Definition of Mobile Device Reconfiguration Classes (MDRCs)
according to reconfiguration capabilities [i.7]
5 Definition of Radio Application Packages
5.1 Content
In the present clause, the format of the RAP container is described on a high level. In order to keep the approach
flexible, each of the information elements will be combined with a length indication (number of octets) such that
manufacturers can adapt the size of any information element as required. The high-level RAP container format shall be
defined as indicated in Figure 4.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 850 V1.1.1 (2022-10)
Radio Application
Package (RAP) container
Header
Security Section
URA Code (any representation)
Manufacturer Information Section
Initial Profile Section
Reserved for future use (optional, as
indicated in Header)

Figure 4: High level Radio Application Package container format
5.2 Tree Structure
5.2.1 Introduction
The RAP is a complex hierarchical bit field which is represented as a graph with specific properties. The RAP bit field
is a sequence of bits. Therefore, the graph properties shall insure the only way for the RAP writing operation when the
RAP is created as well as the RAP reading operation during which all RAP elements are decoded.
The RAP graph consists of nodes and edges between them. Each node of the RAP graph represents some bit field. Two
nodes are connected by the edge if and only if one of them is a part of another one assuming that the one bit field is a
part of another bit field. The RAP graph is a tree. It means that there is the only path between any pair of graph nodes.
All the RAP graph elements are ordered in the following way:
• From the top to the bottom, the RAP graph is structured by layers. Nodes from the upper layer are connected
with nodes from the adjusted lower layer. There are no edges between nodes from the same layer. If there is an
edge between the upper layer node and the lower layer node it means that the bit field represented by the lower
layer node is a part of the bit field represented by the upper layer node.
• From the left-hand to the right-hand, nodes from the same layer have fixed layer positions. It defines a position
of the RAP element in the RAP bit field sequence: the left-hand elements are placed before the right-hand
RAP element.
Below the RAP graph nodes are denoted by circles and edges by lines. Some of the RAP elements can be optional. In
such case corresponding nodes can be omitted in the RAP graph structure and related edges are drawn as dotted lines.
They also will be labelled by the letter "o" ("optional") or by a particular condition defining the related option. All other
edges are drawn by the solid lines.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 850 V1.1.1 (2022-10)
5.2.2 Top Level
RAP
Reserve
URACodeList
Manufacturer Profile
Header Security

Figure 5: Top Level Tree Structure
The highest layer of the RAP graph consists of the only one the RAP node which represents the whole RAP bit field as
it is pointed out in Figure 5 The lower layer consists of the following nodes representing particular RAP sections from
Figure 4.
Table 1: Top Level Tree Structure Bit Fields
N Node name Node type Bit field
1 Header mandatory The RAP header
2 Security mandatory The Security section
mandatory URA codes (any representation). The URA code list consisting of code
3 URACodeList
sections for a few Radio Applications
4 Manufacturer optional The Manufacturer Information section
5 Profile optional The Initial Profile section
6 Reserve optional Reserved for the future use

5.2.3 Tree - Header Section
RAP \Header
Descriptor
Structure TargetPlatform
RadioLib Reserve
ManufacturerFlag
ReconfigurationClass
ID Version Version
Date Producer Date ID
(RC)
InitialProfileFlag
RAPReserveFlag
HeaderReserveFlag
ManufacturerReserveFlag
SecurityReserveFlag
ReserveFlag

Figure 6: Tree - Header Section
The RAP Header subtree is depicted in Figure 6 Elements of the RAP Header are described in Table 2.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 850 V1.1.1 (2022-10)
Table 2: Header Section Bit Fields
Node
N Node name Bit field
type
1 Descriptor mandatory The RAP header descriptor
2 Descriptor\ID mandatory The RAP ID
3 Descriptor\Version mandatory The RAP version
4 Descriptor\Date mandatory The RAP day issue
5 Descriptor\Producer mandatory The RAP producer
6 Structure mandatory The bit field for the RAP structure description
Structure\ManufacturerFlag mandatory ManufacturerFlag = 1 than Manufacturer is a part of the RAP and
7
otherwise if ManufacturerFlag = 0
Structure\InitialProfileFlag mandatory InitialProfileFlag = 1 than Profile is a part of the RAP and
8
otherwise if InitialProfileFlag = 0
Structure\RAPReserveFlag mandatory RAPReserveFlag = 1 than Reserve is a part of the RAP and
9
otherwise if RAPReserveFlag = 0
Structure\HeaderReserveFlag mandatory HeaderReserveFlag = 1 than Header\Reserve is a part of the
10
RAP and otherwise if HeaderReserveFlag = 0
Structure\ManufacturerReserveFlag mandatory ManufacturerReserveFlag = 1 than Manufacturer\Reserve is a
11
part of the RAP and otherwise if ManufacturerReserveFlag = 0
Structure\SecurityReserveFlag mandatory SecurityReserveFlag = 1 than Security\Reserve is a part of the
12
RAP and otherwise if SecurityReserveFlag = 0
Structure\ReserveFlag mandatory ReserveFlag = 1 than Reserve is a part of the RAP and
13
otherwise if ReserveFlag = 0
14 RadioLib mandatory The Radio Lib description
15 RadioLib\Version mandatory The Radio Lib version
16 RadioLib\Date mandatory The Radio Lib day issue
17 TargetPlatform mandatory The target platform description
18 TargetPlatform\ID mandatory The target platform ID
19 TargetPlatform\ReconfigurationClass mandatory The target platform Reconfiguration Class (see Figures 2 and 3)
20 Reserve mandatory The RAP reserved bit field

5.2.4 Tree - Security Section
RAP\Security
Reserve
Origin
Integrity
Profile

Figure 7: Tree - Security Section
The Security section subtree is depicted in Figure 7. Elements of the Security section are described in Table 3.
Table 3: Security Section Bit Fields
N Node name Node type Bit field
mandatory Description of security profile. Indication of the security features implemented
1 Profile for the specific case (taken out of the identified list of options available in the
RRS security study ETSI TS 103 436 [1])
2 Integrity mandatory Parameterization for Integrity Protection: Hash Algorithm, Hash size, etc.
mandatory Parameterization for Proof of Origin: Digital signature algorithm, digital
3 Origin
signature size, etc.
4 Reserve optional Reserved for the future use

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 850 V1.1.1 (2022-10)
5.2.5 Tree - Unified Radio Application (URA) Code Section
RAP\URACodeList
URACode[2]
...
URACode[1]
URAComponentList
URADescriptor
URAComponent[2]
...
URAComponent[1]
ID
...