ETSI TR 102 967 V1.2.1 (2015-11)

TECHNICAL REPORT
Reconfigurable Radio Systems (RRS) ;
Use cases for dynamic equipment reconfiguration

2 ETSI TR 102 967 V1.2.1 (2015-11)

Reference
RTR/RRS-0343
Keywords
conformance, radio, use case
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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
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 2015.
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 TR 102 967 V1.2.1 (2015-11)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Principles and Objectives for Reconfigurable Equipment . 8
5 Stakeholders and Interrelations . 10
5.0 Introduction . 10
5.1 Stakeholders, Entities and Statements of Conformity . 10
6 Reconfiguration generic Use Cases . 12
6.0 Introduction . 12
6.1 OEM Establishing Initial Conformity of RE Platform . 12
6.2 DoC/StoC Verification of reconfigurable equipment . 13
6.3 OEM Upgrade (individual or en-masse) . 13
6.4 Third Party reconfiguration (individual or en-masse) . 14
6.5 Configuration enforcement of reconfigurable equipment . 15
7 Responsibility . 15
7.1 Overview . 15
7.2 Vertical Market model . 16
7.3 Horizontal Market model . 17
7.4 Hybrid Model - Horizontal Market model with a single Contact Point. 18
7.4.0 Introduction. 18
7.4.1 Hybrid Model - Horizontal Market model with an independent single Contact Point and the OEM
involved in the reconfiguration . 18
7.4.2 Hybrid Model - Horizontal Market with OEM as single Contact Point . 18
8 Declaration of Conformity in the context of Software Reconfiguration in Europe . 20
9 Further Details on Use Cases . 20
9.0 Introduction . 20
9.1 Overview . 20
9.2 Detailed Description of Use Cases . 20
9.2.1 Use Case "OEM Establishing Initial Conformity of RE Platform" . 20
9.2.1.1 General Use Case Description. 20
9.2.1.2 Stakeholders . 20
9.2.1.3 Use Case Description . 21
9.2.1.4 Information Flow . 21
9.2.1.5 Derived potential system requirements . 21
9.2.2 Use Case "DoC/StoC Verification of reconfigurable equipment" . 21
9.2.2.1 General Use Case Description. 21
9.2.2.2 Stakeholders . 22
9.2.2.3 Use Case Description . 22
9.2.2.4 Information Flow . 22
9.2.2.5 Derived potential system requirements . 22
9.2.3 Void . 23
9.2.4 Use Case "OEM Upgrade (individual or en-masse)" . 23
9.2.4.1 General Use Case Description. 23
9.2.4.2 Stakeholders . 23
9.2.4.3 Use Case Description . 23
ETSI
4 ETSI TR 102 967 V1.2.1 (2015-11)
9.2.4.4 Information Flow . 24
9.2.4.5 Derived potential system requirements . 24
9.2.5 Use Case "Third Party reconfiguration (individual or en-masse)" . 25
9.2.5.1 General Use Case Description. 25
9.2.5.2 Stakeholders . 25
9.2.5.3 Use Case Description . 25
9.2.5.4 Information Flow . 25
9.2.5.5 Derived potential system requirements . 26
9.2.6 Use Case "Configuration enforcement of reconfigurable equipment" . 26
9.2.6.1 General Use Case Description. 26
9.2.6.2 Stakeholders . 27
9.2.6.3 Use Case Description . 27
9.2.6.4 Information Flow . 27
9.2.6.5 Derived potential system requirements . 28
10 Technical Challenges . 28
11 Conclusion . 28
History . 29

ETSI
5 ETSI TR 102 967 V1.2.1 (2015-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) 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
6 ETSI TR 102 967 V1.2.1 (2015-11)
1 Scope
The present document outlines the Use Cases which are related to the introduction of mechanisms to enable, for
reconfigurable radio systems, the dynamic reconfiguration of equipment and its continuing conformity with the
applicable legislation. These Use Cases involve the dynamic reconfiguration of reconfigurable radio equipment after its
initial Declaration of Conformity and deployment. Such post-deployment reconfiguration will ensure the continued
conformity in the new configuration to the applicable legislation. In some Use Cases, new mechanisms that enable
reconfigurable devices to have their Declaration of Conformity dynamically verified may be introduced.
Note that the term "Declaration of Conformity" is typically used in conjunction with the European Radio Equipment
Directive. In other regulation domains, other terminology may be employed. While the Use Cases presented in the
present document are designed to support the novel radio reconfiguration features of the Radio Equipment Directive
[i.3] that is applicable in Europe, the principles and the Use Cases outlined here are not limited to Europe and may also
be appropriate for other regions.
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
reference 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.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference 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] Report Recommendation ITU-R SM.2152: "Definitions of Software Defined Radio (SDR) and
Cognitive Radio System (CRS"), 2009.
[i.2] Void.
[i.3] 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
radio equipment and repealing Directive 1999/5/EC.
ETSI
7 ETSI TR 102 967 V1.2.1 (2015-11)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Cognitive Radio System (CRS): Radio system employing technology that allows the system: to obtain knowledge of
its operational and geographical environment, established policies and its internal state; to dynamically and
autonomously adjust its operational parameters and protocols according to its obtained knowledge in order to achieve
predefined objectives; and to learn from the results obtained.
NOTE: This is the current definition as given in Report Recommendation ITU-R SM.2152 [i.1].
RadioApp (RA): software component to be installed and operated on reconfigurable Mobile Devices
NOTE: The operation of the software component impacts the conformity of the reconfigurable equipment to the
applicable legislation.
Reconfigurable Equipment (RE): 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): generic term for radio systems encompassing Software Defined and/or
Cognitive Radio Systems
Software Defined Radio (SDR): radio transmitter and/or receiver employing a technology that allows the RF operating
parameters including, but not limited to, frequency range, modulation type, or output power to be set or altered by
software, excluding changes to operating parameters which occur during the normal pre-installed and predetermined
operation of a radio according to a system specification or standard
NOTE: This is the current definition as given in Report Recommendation ITU-R SM.2152 [i.1].
user: user of the Reconfigurable Radio System or the Reconfigurable Equipment
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CRS Cognitive Radio System
DoC Declaration of Conformity
EC European Commission
GSM Global System for Mobile Communications
HW HardWare
NRA National Regulatory Authority
OEM Original Equipment Manufacturer
PAMR Public Access Mobile Radio
PMR Professional Mobile Radio
PPDR Public Protection and Disaster Relief
RAT Radio Access Technology
RE Reconfigurable Equipment
RMP Reconfiguration Market Platform
RRS Reconfigurable Radio System
RVM Radio Virtual Machine
SDR Software Defined Radio
SM Software Manufacturer
SP Service Provider
StoC Statement of conformity
SW SoftWare
TCAM Telecommunication Conformity Assessment and Market Surveillance Committee
ETSI
8 ETSI TR 102 967 V1.2.1 (2015-11)
4 Principles and Objectives for Reconfigurable
Equipment
The present document focuses on the Use Cases and the related procedures applicable to equipment to be placed on the
market that is able to be dynamically reconfigured. This includes, for instance, a piece of equipment for which the radio
part can be reconfigured after deployment with new software remotely. Very often such a reconfiguration may occur
"over-the-air" while the reconfigurable equipment is attached to a network. In the framework of the present document, it
is assumed that equipment reconfiguration may include software provided by third party software suppliers. A
corresponding legal framework is available in Europe under the Radio Equipment Directive (RED) [i.3]. Other regions
may have their specific legal frameworks for placing such reconfigurable equipment on the market and/or putting it into
service.
Herein, it is assumed that methods and processes traditionally used in the context of the assessment of conformity to
applicable legislation may continue to be applied.
The extensions and standards for dynamically reconfigurable equipment may take into consideration the following
principles and objectives:
i) One single entity, typically but not necessarily the Original Equipment Manufacturer, will ensure and declare
that the resulting combination of (third party) software and hardware is in conformity to the applicable
requirements.
ii) The entity responsible for the joint operation of hardware and software will provide all relevant technical
documentation on request for market surveillance (including all background information used for the DoC).
iii) A mechanism may be developed to ensure that reconfigurable equipment will only allow compliant software
to be installed and to ensure the externally verifiable integrity of the software. A mechanism may be used to
indicate that a Declaration of Conformity has been issued for the combination of the software and hardware
equipment in question.
iv) Third party software may be installed as long as the resulting combination of software and hardware is in
conformity with the appropriate applicable legislation.
v) A history file should be kept inside the dynamically reconfigurable equipment for storing information on
previous reconfigurations. This may enable the equipment to go back to a previous (stable) configuration in
case of unexpected operation (e.g. creation of interference to other users or systems) and/or to identify which
software modifications have been installed onto the equipment (so as to facilitate ex-post equipment
monitoring).
vi) Typically, a Declaration of Conformity may be issued for software and hardware components which are
available at the time of the Declaration ("Scenario 1"); additionally, depending on the applicable legislation, a
Declaration of Conformity may be issued for hardware components in combination with available software
components which can be extended for inclusion of software components to be developed in the future
("Scenario 2"). In the latter case, a future software component is typically made available together with a
"Statement of Conformity", indicating that the combination of concerned hardware and software complies with
the appropriate requirements. In Scenario 2, the Declaration of Conformity together with the appropriate
Statement of Conformity is expected to be equivalent to Scenario 1.
Scenario 2 is expected to reduce the administrative overhead for the responsible entity (typically the Original
Equipment Manufacturer), while the legal result would be the same as in Scenario 1. It still needs to be
verified whether:
i) Scenario 2 is finally meeting its objectives; and
ii) be acceptable from a legal perspective.
ETSI
9 ETSI TR 102 967 V1.2.1 (2015-11)
Figure 1 positions the application of Scenario 1 and Scenario 2 with respect to the verification needs of an equipment
after Software Reconfiguration. Scenario 2 is an alternative to Scenario 1, especially in the case of a very limited access
to radio parameters for (third party) software developers - the latter can be addressed by an Radio Virtual Machine
(RVM) approach enabling the management of various levels of access to Radio Parameters by Software Components.
Finally, together with the limited effort required for verification (i.e. only those test-cases need to be executed which are
affected by the reconfiguration), a less complex assessment procedure might be possible.

Figure 1: Scenario 1 and Scenario 2 Declaration of Conformity.
Figure 2 highlights that both Scenario 1 and Scenario 2 based Declaration of Conformity lead to an identical situation,
i.e. the Declaration of Conformity is finally covering the concerned combination of hardware and software after the
Reconfiguration process.
Figure 2: Identical situation for Scenario 1 and Scenario 2 Declaration of Conformity.
ETSI
10 ETSI TR 102 967 V1.2.1 (2015-11)
5 Stakeholders and Interrelations
5.0 Introduction
The ability to dynamically reconfigure equipment throughout its lifetime is important to enable the rapid and
economical upgrading of equipment after initial deployment while at the same time assuring the continued conformity
to all the applicable rules and the applicable legislation. It is through providing a climate of dynamic re-configurability
that the economic benefits of Cognitive Radio Systems technology and rapid deployment of new innovative
reconfigurable radio systems will be fostered. Such re-configurability will enable systems to be designed for the future
and to take advantage of new technology and regulatory developments.
However, while it is important that the dynamic reconfiguration process does not hinder the development of new
systems, the process should accommodate a wide variety of equipment, be sustainable over decades of regulatory
control, be legally sound and be proof against both innocent misuse and malevolent perversion. In some cases, the new
Declaration of Conformity may cover regulations that were not in effect at the time of original Declaration of
Conformity or involve service aspects that are new capabilities. The reconfiguration may also be performed in a
regulatory domain that is different from the initial Declaration of Conformity domain and the reconfiguration may
affect features that may be regulated differently in different regulatory domains. It can be anticipated, for example, that
in a first phase reconfiguration features are likely to be used only within a single regulatory domain. At a later time, the
features could be extended to multiple regulatory domains as needed.
It should be understood that the Use Cases discussed in the present document are not about the conformity testing or
"Declaration of Conformity" of equipment that has been upgraded with new software. All upgrades should first be
verified by their developers using testing processes that are already established within the industry that conform to the
applicable legislation. The reconfiguration Use Cases that are the subject of the present document address the process of
assuring that new configurations for reconfigurable equipment are properly and appropriately loaded. The software and
equipment design for the new configuration may be tested for conformity through the appropriate entities. Once the
conformity testing of the new configuration is successful and a new Declaration of Conformity for the new
configuration is issued, the reconfiguration process that is the subject of the Use Cases in the present document may be
used to dynamically reconfigure the equipment.
Reconfigurations may involve many layers of software or hardware, and some reconfigurations may rely on presumed
operation of previously established configurations. Also, due to the large volumes of deployments of consumer devices,
the reconfiguration process should be scalable to accommodate (literally) billions of deployed devices and a similar
number of possible new configurations.
This introductory clause outlines key stakeholders and key concepts for dynamically reconfiguring equipment while
ensuring its continued conformity/compliance to/with applicable legislation and standards. One of the purposes of the
present document is to enumerate some of the practical and technical Use Cases that should be accommodated by the
dynamic reconfiguration process. For example, due to the equipment long life-cycles, the configuration process requires
care and caution in its design to prevent failures or malevolent perversion. Furthermore, security requirements for the
reconfigurable equipment should be considered to ensure trustworthy operation.
5.1 Stakeholders, Entities and Statements of Conformity
This clause lists and briefly describes the Stakeholders ([S]) and Entities ([E]) involved in the illustrated reconfiguration
Use Cases as well as the "Statement of Conformity"([StoC]).
Note that the requirement for some or all of the below mentioned entities depends on the implementation of the
reconfiguration framework. In particular a first implementation of the software reconfiguration framework is expected
to limit itself to the most essential features only.
Not all of the listed stakeholders are involved at the same time.
ETSI
11 ETSI TR 102 967 V1.2.1 (2015-11)
• Reconfigurable Equipment (RE) [E]: Equipment that is dynamically reconfigurable through software
reconfigurations affecting radio parameters. The Software may be acquired from a Reconfiguration Market
Platform (for instance an SP, see below). This reconfiguration may occur after the initial sale, deployment and
operation of the equipment. In some situations, the reconfigurable equipment may be physically fixed in
location and linked to a communications network (Mobile network base stations are an example of such
equipment). In other situations, the reconfigurable equipment may be mobile or in no specific location and
linked to communications networks through temporary means such as radio links (User mobile equipment are
an example of such equipment). The reconfiguration of fixed and mobile RE may adopt different procedures
for dynamic changes. In some cases the RE may be reconfigured using procedures that have previously been
used which may, for example, involve human interaction.
• Reconfigurable Equipment User [S]: User making use of Reconfigurable Equipment to access services from
an SP or to otherwise communicate with equipment that is compliant with the applicable legislation.
NOTE 1: In some cases RE Users may select reconfiguration software components to alter the capabilities and
services of their RE.
NOTE 2: Such other communication may include, for example, a private network or a local individual
communication.
• Service Provider [S]: An SP delivers radio access and network services using equipment including RE. The
SP may, for example, be a network operator using licensed spectrum, but may also be a personal or local area
network manager. There may be multiple SPs associated with mobile RE through roaming or other
commercial arrangements. The SP network may be a public service or a user restricted one (e.g. PMR, PAMR,
PPDR network). The SP may require a subscription, for mobile RE to access its network and services. The SP
may perform reconfiguration of its network RE, perhaps in concert with the RE's OEM. The SP may also
provide the RE User with information on available reconfiguration software (i.e. the SP may also be a
'Reconfiguration' Market Platform provider).
• 'Reconfiguration' Market Platform [E]: RMP is a Platform where reconfiguration software is advertised and
can be downloaded by RE Users in a trustworthy way. The 'Reconfiguration' Market Platform may also inform
the RE Users of new, updated or discontinued (no longer supported) software configurations. There may be
multiple 'Reconfiguration' Market Platforms which may, or may not, be associated with an equipment or a
software provider or an SP. In this context, reconfiguration software refers to software that affects the
conformity of the RE to radio or service regulations or to the Service Provider's network. The RE may be
reconfigured with software from multiple 'Reconfiguration' Market Platforms. In the present document, the
RMP is considered to be generic and covers all relevant market channels (such as the SP, a RadioApp store,
etc.).
• Declaration of Conformity [C]: The Declaration of Conformity may be made such that the stated version of
software in combination with equipment is in conformity with the applicable legislation and standards.
• Statement of Conformity [C]: In case of Scenario 2 Declaration of Conformity (Declaration of Conformity
may be issued for available hardware components in combination with software components to be developed
in the future), a "Statement of conformity" (StoC) is provided after successful completion of testing that proves
the conformity of the RE to the applicable legislation and standards. The StoC is the proof that the RE or its
reconfiguration is in conformity with all the applicable legislation and it is the basis for the continued
operation of the device.
A new StoC is required anytime a new configuration, including a new firmware release, affects, or may affect,
the conformity of the RE to the applicable legislation.
• Original Equipment Manufacturer [S]: OEM develops Reconfigurable Equipment platforms based on user
preferences, service requirements, applicable technical regulations or the facilities of the SP. The platform may
consist of only hardware, but may also be a combination of hardware and associated software. Note that if the
reconfigurable equipment is not operational without appropriate SW, then it cannot be tested for conformity as
such testing requires operational equipment including both hardware and software components.
• Software Manufacturer [S]: An SM develops Reconfiguration Software or software components to be used
on Reconfigurable Radio System platforms. The software may be distributed to users through the
'Reconfiguration' Market Platform or other relevant channels (such as the SP, or direct to the RE User, or
bundling with HW equipment, etc.).
ETSI
12 ETSI TR 102 967 V1.2.1 (2015-11)
• National Regulatory Authority [S]: NRA is a national body, or other designated authority, responsible for
administering and assuring that the RE can be put into service and conforms to the applicable legislation.
6 Reconfiguration generic Use Cases
6.0 Introduction
There are a number of possible generic Use Cases for the initial Declaration of Conformity and subsequent
reconfiguration of reconfigurable equipment after its initial Declaration of Conformity and deployment. In case of
Scenario 1 Declaration of Conformity (Declaration of Conformity may be issued for software and hardware components
which are available at the time of the Declaration), a Declaration of Conformity is provided including the combination
of the concerned hardware and software components. In case of Scenario 2 Declaration of Conformity (Declaration of
Conformity may be issued for available hardware components in combination with software components to be
developed in the future), the initial Declaration of Conformity Use Cases follows closely the procedures for non-
reconfigurable equipment with the addition of the concept of a dynamic Statement of Conformity. The reconfiguration
Use Cases typically involve changes in software for the equipment or databases associated with the reconfigurable
equipment. To assure that the equipment remains in conformity with the applicable legislation a form of dynamic
conformity declaration may be required. There are 5 basic Use Cases:
1) OEM establishing initial conformity of reconfigurable equipment platform.
2) DoC/StoC verification of reconfigurable equipment.
3) OEM upgrade of reconfigurable equipment (individual or en-masse).
4) Third party upgrade of reconfigurable equipment (individual or en-masse).
5) Configuration enforcement of reconfigurable equipment.
These Use Cases are discussed generically in this clause. Further details are provided in clause 9.
6.1 OEM Establishing Initial Conformity of RE Platform
The establishment of the initial conformity and Declaration of Conformity of the reconfigurable equipment platform by
the OEM is illustrated in figure 3. This Use Case is very similar to the conformity testing and Declaration of
Conformity that is currently used for non-reconfigurable equipment. As shown in figure 3 the following steps can be
identified:
1) The OEM designs and develops the RE platform.
2) The RE is then tested, for example, by the OEM and the SP for conformity to applicable legislation and
standards and a Declaration of Conformity is made.
3) In case of Scenario 2 Declaration of Conformity (Declaration of Conformity may be issued for available
hardware components in combination with software components to be developed in the future, if available in
the concerned legal framework), the OEM includes the coverage of software components in the Declaration of
Conformity for which a Statement of Conformity is issued. The concerned RE may then be placed on the
market.
Figure 3: Use Case in which OEM develops, certifies conformity and deploys an RE platform
ETSI
13 ETSI TR 102 967 V1.2.1 (2015-11)
6.2 DoC/StoC Verification of reconfigurable equipment
The Use Case for the verification of conformity of a given deployed reconfigurable equipment is illustrated in figure 4.
The following steps can be identified:
1) To verify the conformity of the equipment deployed, the inquiring party queries the RE to provide information
on its Declaration of Conformity.
2) The RE replies to the requestor with its current Declaration of Conformity - and in case Scenario 2 Declaration
of Conformity, any available Statement(s) of Conformity are provided.
3) The requestor receives the Declaration of Conformity (directly or by pointing to a relevant storage, for
example a web-site) - and in case of Scenario 2 Declaration of Conformity, any available Statement(s) of
Conformity. The requestor verifies the authenticity of the RE's Declaration of Conformity (in combination
with available Statement(s) of Conformity in case of Scenario 2 Declaration of Conformity) to assure the
conformity of the RE.
Figure 4 shows the NRA as the source of the query for Declaration of Conformity verification but a similar request for
verification could come from other stakeholders as well. For example, the OEM or the software manufacturer could
query the RE's Declaration of Conformity (in combination with available Statement(s) of Conformity in case of
Scenario 2 Declaration of Conformity) to determine the current configuration of the RE before deploying new
reconfiguration software or to ascertain the RE's capabilities.

Figure 4: Use Case in which an NRA verifies Declaration of Conformity (in combination with available
Statement(s) of Conformity in case of a-priori Declaration of Conformity) for RE
6.3 OEM Upgrade (individual or en-masse)
6.3.1 Introduction
In some Use Cases, the reconfiguration components (e.g. software) may be developed by a team that includes the
original equipment manufacturer under which the equipment was initially marketed. This Use Case may include, for
example "bug fixing", SW Upgrades, new features and enablement of new technologies such as new radio access
technologies or new frequency bands of operation.
The Use Case in figure 5 considers the case when multiple REs are loaded with a new software by the OEM. The
following steps can be identified:
1) The OEM team develops the new SW for the reconfigurable equipment.
2) The new SW is tested for conformity and for compatibility with the intended RE platforms and software
configuration.
ETSI
14 ETSI TR 102 967 V1.2.1 (2015-11)
3) In case of Scenario 1 Declaration of Conformity (Declaration of Conformity may be issued for software and
hardware components which are available at the time of the Declaration), the entity responsible for the
combination of hardware and software updates the existing Declaration(s) of Conformity (directly or in a
relevant storage, for example a web-site to which the concerned device is pointing) for some or all RE
platforms. Alternatively, in case of Scenario 2 Declaration of Conformity (Declaration of Conformity may be
issued for available hardware components in combination with software components to be developed in the
future), , (a) new Statement(s) of Conformity are issued indicating that (a) new software component(s) is/are
covered by the existing Declaration(s) of Conformity. In the latter case, the existing Declaration(s) of
Conformity is/are maintained.
In case that the concerned software component is not compatible with a given RE configuration, corresponding
usage conditions are included in the Declaration(s) of Conformity and/or Statement(s) of Conformity.

Figure 5: Use Case in which OEM team upgrades applicable reconfigurable equipment en masse
6.4 Third Party reconfiguration (individual or en-masse)
In some Use Cases the reconfiguration components (e.g. software updates) may be provided by a team that is not
associated with the original equipment manufacturing team that was responsible for the original Declaration of
Conformity. The reconfiguration (new features, SW upgrade, new RAT, operation in a new frequency band, etc.) may
be directed to all the REs, a sub-set of REs or to an individual RE. It is therefore necessary to establish and verify the
compatibility of the new configuration with the RE's current configuration.
Figure 6 considers the case when an individual RE is reconfigured "on request". The following steps can be identified:
1) The user requests a new SW for the reconfigurable platform.
2) The current Declaration(s) of Conformity and (in case of Scenario 2) Statement(s) of Conformity are used in
order to identify whether the concerned software components are compatible with the RE platform.
3) If the new reconfiguration is not compatible with the RE's current configuration, the new configuration is not
loaded by the RE.
4) If the new reconfiguration is compatible with the RE's current configuration following the current
Declaration(s) of Conformity and (if available) Statement(s) of Conformity, the software component(s) may be
loaded by the RE for its use and the RE operates with the new SW.
ETSI
15 ETSI TR 102 967 V1.2.1 (2015-11)

Figure 6: Use Case in which user upgrades SW RE Platform
6.5 Configuration enforcement of reconfigurable equipment
The Use Case for configuration enforcement of reconfigurable equipment (for example to halt an improper operation) is
illustrated in figure 7. The following steps can be identified:
1) The NRA (or another appropriate body) becomes aware of improper operation of an RE. The NRA may be
informed of improper operation by, for example, the SP, the OEM, other RE users or other system users.
2) The NRA (or another appropriate body) requests through appropriate channels the RE to cease its operations.
3) The RE receives the instructions to cease the current operating mode.
4) The RE ceases its improper functions. This may take place, for example, through a complete switch-off or
through a reversion to a previous configuration.

Figure 7: Use Case for enforcement in the event of improper operation of reconfigurable equipment
7 Responsibility
7.1 Overview
From a National Regulatory Authority (NRA)'s perspective, a key requirement for reconfigurable radio systems relates
to the issue of Responsibility. In the event that an RE does not operate within the regulatory framework, the
...