reconfigurable mobile devices and ......• draft en 303 095 on reconfigurable mobile device system...

RECONFIGURABLE MOBILE DEVICES AND CERTIFICATION

IN THE CONTEXT OF THE NEW RED DIRECTIVE ETSI Workshop on Reconfigurable Radio Systems – Sophia Antipolis,

December 3rd, 2014

© ETSI 2011. All rights reserved

Dr. Markus Mueck, Chairman ETSI TC RRS & INTEL

RED Directive

Reconfigurability Vision for Mobile Devices

2 © ETSI 2011. All rights reserved


Status of TC RRS Activities

Next Steps & Conclusion

Radio Equipment Directive (RED)

33//1717

I. I. Radio Equipment Directive (RED)Radio Equipment Directive (RED)


44//1717

• In 2014 the revision of the R&TTE Directive has been published in the Official Journal ofthe European Union;

• A key novelty relates to the support for combinations of radio equipment and software ;

• ETSI TC RRS activities provide corresponding solutions for enabling usage of 3rd PartySoftware. The current activities comprise

• Mobile Device Reconfiguration Use Cases, Requirements, Architecture and Interfacesolutions (ETSI TC RRS WG2);

• Novel Certification and Responsibility solutions (ETSI TC RRS WG3).

Article 3(3)(i):

3. Radio equipment within certain categories or classes shall be so constructed that it complies

with the following essential requirements:

(i) radio equipment supports certain features in order to ensure that software can only

be loaded into the radio equipment where the compliance of the combination of the

radio equipment and software has been demonstrated.

Article 4: Provision of information on the compliance of combinations of radio equipment and


5

Article 4: Provision of information on the compliance of combinations of radio equipment and

software

1. Manufacturers of radio equipment and of software allowing radio equipment to be used as

intended shall provide the Member States and the Commission with information on the

compliance of intended combinations of radio equipment and software with the essential

requirements set out in Article 3. Such information shall result from a conformity assessment

carried out in accordance with Article 17, and shall be given in the form of a statement of

compliance which includes the elements set out in Annex VI. Depending on the specific

combinations of radio equipment and software, the information shall precisely identify the

radio equipment and the software which have been assessed, and it shall be continuously

updated.

2. The Commission shall be empowered to adopt delegated acts in accordance with Article 44

specifying which categories or classes of radio equipment are concerned by the requirement set

out in paragraph 1 of this Article .


66//1717

II. II. ReconfigurabilityReconfigurability Vision for Mobile DevicesVision for Mobile Devices

General principles of TC RRS activities on MD Recon figurability –

Employing a close linkage between Certification & R econfiguration Solutions


77//1717

Employing a close linkage between Certification & R econfiguration Solutions

• Previously, MD Reconfiguration was rather addressed from a „Computer Architecture“perspective: TC RRS activities addresses the topic „from the other end“, i.e. it is assumedthat „Mobile Device Apps“ are smoothly evolving towards „Mobile Device RadioApps“ witha controlled level of access to radio parameters.

• TC RRS MD Reconfiguration activities assume the execution of „RadioApps“ in acontrolled environment called „Radio Virtual Machine“ - vs full access to the platform.

• TC RRS MD Reconfiguration activities provide solutions for provisioning of SW code toMDs using a Library for vendor specific access to HW blocks/accelerators – compared toother solutions, no „open“ Middleware (or similar) is defined which is considered to beinefficient for the Mobile Device market needs.

• TC RRS MD Reconfiguration activities closely address Technological and Certificationsolutions. A „joint“ responsibility solution is required for both HW and SW.


88//1717

Example Applications of „ RadioApps“

• Example 1: Provision of a novel Radio Access Technology to a Mobile Device.

• Example 2: Optimization of Radio Access Technologies to specific usage scenarios,typically not requiring RX modifications, e.g. implementation of a novel intelligent antennaselection approach.

• Example 3: Addition of tailor made (vendor specific), non standard-compliant extensions ofan existing Radio Access Technology, e.g. addition of novel multi-cast, broad-cast, mesh-and/or device-to-device communication features for Civil Security applications, etc.

Responsibility Approach as defined in ETSI TR 102 9 67


99//1717

Radio

Storage

Radio Apps

Source code

Front-end

Compiler

Multi Radio Interface (MURI)

configcode

Radio Librarynormative description

Radio Apps

configcode

Unified Radio

Application

Interface (URAI)

Radio Control Framework

단추Shadow

Radio Platform

Radio Virtual Machine (RVM) approach as defined in Draft ETSI EN 303 095


1010//1717

Radio Programming Interface

configcode

Radio Platform

configcode

RVMimplementation

Radio Librarynative implementation

Radio OS

Radio Apps

package

Radio Apps

Store

Radio Computer

BECompiler

단추Radio Platform

10


1111//1717

III. Status of TC RRS Activities (Certification)III. Status of TC RRS Activities (Certification)

• Draft TS 103 094: Dynamic Certification related System Requ irements

• TR 102 967 (under revision): Use Cases for Dynamic Equipment Reconfiguration

Status of TC RRS Activities - Certification

The following 7 basic Use Cases are defined in TS 103 094:

• OEM establishing initial conformity of reconfigurable equ ipment platform:

1212//1717

• Certificate verification of reconfigurable equipment:


• Establishing conformity of reconfiguration software:

1313//1717

• OEM upgrade of reconfigurable equipment (individual or en- masse):


• Third party upgrade of reconfigurable equipment (individu al or en-masse):

1414//1717

• Configuration enforcement of reconfigurable equipment:


• RE discovery of databases:

• Declaration of Conformity is proposed to be managed by two possible approaches :

1515//1717

• Declaration of Conformity is proposed to be managed by two possible approaches :

a) Through a dynamic update of the DoC as for example foreseen in Annex VII ofthe new RED;

b) With a SINGLE DoC that antipates conformity for Equipment to be modified inthe future – under the condition that a „Certificate“ (or „To ken“) is issued bythe responsible entity ensuring that the equipment is cover ed by the relevantDoC.


1616//1717

• Reconfiguration Database : RD is a centralized or distributed database which containsinformation that may be used by reconfigurable equipment in the process ofreconfiguration and which may affect the conformity of the reconfigurable equipment to theapplicable legislation. .

• Operational Database : OD is a centralized or distributed database which containsinformation that may be used by reconfigurable equipment for its operation and which mayaffect the conformity of the reconfigurable equipment to the applicable legislation;

• Regulatory Certificate Platform : RCP dynamically receives and verifies certificates forREs that may be upgrading their software;

• Reconfiguration Market Platform : RMP is a Platform where reconfiguration software isadvertised and can be downloaded by RE Users in a trustworthy way.


• RVM / RF Protection Classes for managing several levels of Re -Certification (DraftEN 303 095):

Analog-to-

Digital-

Converter

RF Front-End /

RF transceiver

chain

Application

Processor /

MAC (Layer 2)

and Higher

Base-Band Processing

Hard-wired (ASIC

type) of Base band

Implementation

A RVM

Software

component

selects RF &

RVM protection

classes

Indication of RF protection class

chosen by RVM SW component

1717//1717

Digital-to-

Analog-

Converter

chainLayer

Processing

Radio Virtual

Machine (RVM)

Implementationclasses

The RVM enables a Radio Application to choose one among multiple available protection classes for code to be executed on the RVM as well as a protection class for the RF front-end. Depending on the combination of chosen RF & RVM pro tection classes, the required re-certification process of the software reconfigur able radio platform will be more or less complex.


1818//1717

III. Status of TC RRS Activities (Reconfigurable MD)III. Status of TC RRS Activities (Reconfigurable MD)

• A detailed introduction will be given in the „ Tutorial 1 - Reconfigurable MobileDevices Architecture and Interfaces and related Declarati on of Conformity “ by Prof.Seungwon Choi (Hanyang University, Korea) on 4-December-2014

Available (Draft) Deliverables:

• TR 103 062: Definition of refined Scenarios and Use Cases for Software DefinedRadio (SDR) Reference Architecture for Mobile Device

• TR 102 839: Multiradio Interface for SDR Mobile Device Archi tecture and Services

• TR 102 944: Use Cases for baseband interfaces for unified radio applications of

Status of TC RRS Activities – MD Reconfiguration

1919//1717

• TR 102 944: Use Cases for baseband interfaces for unified radio applications ofmobile device

• TS 102 969: Radio Reconfiguration related Requirements for Mobile Devices

• TS 103 095: Radio Reconfiguration related Architecture for Mobile Devices

• TS 103 146-1: Mobile Device Information Models and Protocol s; Part1:MultiradioInterface (MURI)

• EN 302 969: Radio Reconfiguration related Requirements for Mobile Devices

• Draft EN 303 095: Radio Reconfiguration related Architectu re for Mobile Devices

• Draft EN 303 146-1: Mobile Device Information Models and Pro tocols;Part1:Multiradio Interface (MURI)

• Draft TS 103 146-2: Mobile Device Information Models and Pro tocols; Part2:RRFI

• Scope of standardization activities


• Use Cases, Requirements & FunctionalSystem Architecture

• A Multiradio Interface (MURI) provides auniform way to access all radioapplications in the Reconfigure MDequipment.

• A Reconfigurable RF Interface (RFFI)supports multiple radio applications and

2020//1717

supports multiple radio applications andsharing of the same circuitry amongsimultaneously active radio applications.

• A Radio Programming Interface (RPI)enables an independent and uniformproduction of radio applications assoftware entities.

• A Unified Radio Application Interface(URAI) is used to adapt and align all kindsof radio applications under the commonreconfiguration, multiradio execution andresource sharing framework.

• Capabilities of Reconfigurable Mobile Devices are address ed through „MobileDevice Reconfiguration Classes“ (TS 102 969)


2121//1717

• Distribution and Installation of Radio Application Packag es – Example (Draft EN 303 095)


Operating SystemAP

RadioApp StoreMetadata

for Pipeline Configuration

Radio

Application

Package

Radio

Application

Package

Radio

LibraryFront-End

Compiler ab

le R

ad

io

2222//1717

• Different approaches are defined for Source Code / Platform Independent/IRCode and Executable Code as well as Static / Dynamic Linking

Radio Operating System

RC

Executable Code

Radio Computer

Application Processor

AP

Compiler

Installer

Radio

Controller

Standard

Radio

Library

Header

Radio Controller

Code

Configcodes

Metadata for Pipeline

Configuration

Library

Storage

Loader,

Dispatcher,

etc.

Loader,

Dispatcher,

etc.

Design Time Installation Time Run Time

User Defined Functional Blocks

Executable

Code

Functional Blocks

(SFBs & UDFBs)

Executable Code

Back-End

Compiler

Compiler

Ra

dio

Ap

plica

tion

Pa

rt o

f M

ob

ile

Dev

ice

rela

ted

to

rec

on

fig

ura

Next Steps & Conclusions

2323//1717

IV. Next Steps & ConclusionsIV. Next Steps & Conclusions


• ETSI RRS WG2 will finalize

• Draft EN 303 095 on Reconfigurable Mobile Device System Architecturesolutions,

• Draft EN 303 146-1: on Mobile Device Information Models and Protocols;Part1:Multiradio Interface (MURI) and

• Draft TS 103 146-2 on Mobile Device Information Models and Protocols;Part2:RRFI (planned to be evolved towards an EN)

2424//1717

• Further RRS WG2 work is required on

• A Radio Programming Interface (RPI) anabling an independent and uniformproduction of radio applications as software entities;

• A Unified Radio Application Interface (URAI) to adapt and align all kinds ofradio applications under the common reconfiguration, multiradio executionand resource sharing framework.

• ETSI RRS WG3 will

• finalize Draft TS 103 094: Dynamic Certification related SystemRequirements and

• Revise TR 102 967 (under revision): Use Cases for Dynamic EquipmentReconfiguration.


• ETSI RRS WG2 / WG3 would furthermore be the ideal groups to address apotential future EC mandate as indicated in „Preliminary draft of the annualUnion work programme on European standardisation“:

2.3.12. Wireless communications

• The development and updating of harmonised standards is essential. The Commissionmay prepare new mandates on:

2525//1717

may prepare new mandates on:

• …

• (4) enforcement of systems designed to guarantee that software supporting certainfeatures can only be loaded into the radio equipment where the compliance of thecombination of software and the radio equipment has been demonstrated;

• ….

reconfigurable mobile devices and ......• draft en 303 095 on reconfigurable mobile device system...

Documents