Standard Architecture, Related Interfaces, and ... · Standard Architecture, Related Interfaces,...

Standard Architecture, Related Interfaces, and Standard Architecture, Related Interfaces, and Reconfiguration Process for MultiReconfiguration Process for Multi--radio Mobile Devicesradio Mobile Devices

11/32/32

Seungwon Choi, Vladimir Ivanov, and Markus Seungwon Choi, Vladimir Ivanov, and Markus MueckMueckChairman of TC RRS WG2,

Director of HY-MC Research Center,Hanyang University, Seoul, Korea

ETSI Workshop on Reconfigurable Radio Systems- Status and novel Standards

4 December 2014

ContentsContentsContentsContents

Architecture and InterfacesArchitecture and InterfacesII.II.

Introduction Introduction I.I.

22/32/32http://dsplab.hanyang.ac.kr, [email protected] Tel : 82-2-2220-0366 Fax : 82-2-2299-6263

©All rights reserved by Prof. S. Choi

Reconfiguration ProcessReconfiguration ProcessIII.III.

ConclusionConclusionIV.IV.

I. IntroductionI. Introduction



I. Introduction

ETSI TC RRS (Reconfigurable Radio Systems)

ETSI TC RRSETSI TC RRS

Markus Mueck (Intel)

WG1:WG1:

RRS System AspectsRRS System Aspects

WG2:WG2:Reconfigurable Radio Reconfigurable Radio

Equipment ArchitectureEquipment Architecture

WG3:WG3:Cognitive Management Cognitive Management

and Controland Control

WG4:WG4:

RRS Public SafetyRRS Public Safety




Michael Gundlach(Nokia Network)

Seungwon Choi(Hanyang Univ.)

Markus Mueck(Intel)

Markus Mueck(Intel)

ETSI TC RRS WG2• WG2 focuses on SDR technology with a particular interest in radio equipment architecture

and proposes common reference architectures for SDR/CR radio equipment (mobile handsetdevices, radio base stations, etc.), related interfaces, and so on

• Supporting Company

� Intel Corporation (UK) Ltd., LG Electronics, Samsung Electronics,Hanyang University, ETRI, University of Bradford, SK Telecom, and KT Cooperation

I. Introduction

Documents Released by ETSI TC RRS WG2

� ETSI TS/TR

� TR 102 680 SDR Reference Architecture for Mobile Device (2009.03)

� TR 102 681 Radio Base Station (RBS) SDR status, implementations and costs aspects, including future possibilities (2009.06)

� TR 102 944 Use Cases for Baseband Interfaces for Unified Radio Applications of Mobile Device (2011.07)

� TR 102 839 Multiradio Interface for SDR Mobile Device Architecture and Services (2011.04)




� TR 102 839 Multiradio Interface for SDR Mobile Device Architecture and Services (2011.04)

� TS 102 969 Radio Reconfiguration related Requirements for Mobile Devices (2012.03)

� TS 103 095 Radio Reconfiguration related Architecture for Mobile Devices (2013.01)

� TS 103 146-1 Mobile Device Information Models and Protocols (Part 1): MURI (2013.10)

� European Standard (EN)

� EN 302 969 Radio Reconfiguration related Requirements for Mobile Devices (2014.12)

I. Introduction

Why should RRS be standardized?� With Standard Architecture and Standard Interfaces, RadioApplication Code and HW

Platform can be separated.� Radio Application Code can be developed independently of Hardware Platform.

WiMAXWiMAXWiMAXWiMAXWiMAXWiMAXWiMAXWiMAX




Wireless Mic

Wireless-PhoneWalkie-Talkie

RFID

WiMAXWiMAXWiMAXWiMAXWiMAXWiMAXWiMAXWiMAX

Long Term EvolutionHanyang Univ.

Mobile WiMAXWiMAX Forum

Wireless MicrophoneYJ Software House

Walkie TalkieRadio Software Inc.

DECT TelephoneVATEL Software.

<Radio Apps Store> <Reconfigurable MD>We are decoupled!We are decoupled!

Hardware Hardware PlatformPlatform

RadioRadioApplicationApplication

CodeCode

HW is compliant with Standard

Interfaces

SW is made up with Standard

Interfaces

StandardStandardInterfacesInterfaces

II. Architecture and InterfacesII. Architecture and Interfaces



IIII--1. Architecture Components 1. Architecture Components

IIII--3. Architecture Reference Model for 3. Architecture Reference Model for Multiradio ApplicationsMultiradio Applications

IIII--4. Radio Computer 4. Radio Computer

IIII--2. Related Interfaces2. Related Interfaces

II-1. Architecture ComponentsWhat is being standardized?

�Administrator entity

include at least functions to request installation installation or uninstallation of URAor uninstallation of URA, and creating or creating or deleting instances of URAdeleting instances of URA. It shall also provide information about the URA and their status.

�Mobility Policy Manager (MPM) entity




<Reconfigurable Radio System>

include at least functions for monitoring of the monitoring of the radio environments and MD capabilitiesradio environments and MD capabilities, to request activation or deactivation of URAactivation or deactivation of URA, and to provide information about the URA list.

�Networking Stack entity

include at least functions for sending and sending and receiving of user datareceiving of user data.

�Monitor entity

include at least functions to transfer information transfer information from URA to user or proper destination entity from URA to user or proper destination entity in MD

II-1. Architecture ComponentsWhat is being standardized?

� Configuration Manager (CM) entity

include at least functions for installing/ uninstalling and installing/ uninstalling and creating/deleting instances of URA creating/deleting instances of URA as well as management management of and access to the radio parameters of the URAof and access to the radio parameters of the URA.

� Radio Connection Manager (RCM) entity

include at least functions for activating/deactivating URA for activating/deactivating URA according to user requests, and to management of user data management of user data flowsflows, which can also be switched from one RA to another.





flowsflows, which can also be switched from one RA to another.

� Flow Controller (FC) entity

include at least functions for sending and receiving of user for sending and receiving of user data packetsdata packetsand controlling the flow of signalling packetscontrolling the flow of signalling packets.

� Multiradio Controller (MRC) entity

include at least functions to schedule the requests for radio schedule the requests for radio resourcesresourcesissued by concurrently executing URA, and to detect and manage the interoperability problems detect and manage the interoperability problems among the concurrently executed URA.

� Resource Manager (RM) entity

include at least functions to manage the computational manage the computational resourcesresources, to share them among simultaneously active URAshare them among simultaneously active URA, and to guarantee their real-time execution.

II-2. Related InterfacesWhat is being standardized?

� Multiradio Interface (MURI) between CSL and RCF

� ETSI TS 103 146-1 Reconfigurable Radio Systems(RRS); Mobile Device Information Models andProtocols; Part 1:Multiradio Interface (MURI)

� Published at Oct. 2013

� Reconfigurable Radio Frequency Interface (RRFI)betweenURA andRFTransceiver





betweenURA andRFTransceiver

� ETSI TS 103 146-2 Reconfigurable Radio Systems(RRS); Mobile Device Information Models andProtocols; Part2: Reconfigurable Radio FrequencyInterface (RRFI)

� In draft

� Unified Radio Application Interface (URAI) betweenRCF and URA

� ETSI TS 103 146-3 Reconfigurable Radio Systems(RRS); Mobile Device Information Models andProtocols; Part2: Unified Radio ApplicationInterface (URAI)

II-3. Architecture Reference Model for Multiradio Applications

Driver OS App 1

App 2

App 3

App M•••

UserApplication

Application Processor

CommunicationServices Layer

MURI are interfaces between component of Communication services layer and that of RCF.

All radio applications are calledUnified Radio Applications (URA), since they exhibit a

common behaviour from the radio computer perspective.Radio Controller

Function Block

URAI are interfaces between URA and component of RCF.

MURI

URAI

•••


RA.1

RA.2

RA.3

RA.N



Radio OS

Radio Platform Driver

Radio Platform

ProgrammableHardware

DedicatedHardware

AntennaRF transceiver

Radio Spectrum

Radio Control Framework

RadioComputer

Radio OSis real time OS for multiradio

operation. Radio Control Framework (RCF) is part of Radio OS including :• Configuration Manager (CM)• Radio Connection Manager (RCM)• Flow Controller (FC)• Multiradio Controller (MRC)• Resource Manager (RM)

RA is software which enforces particular radio platform to generate the transmit user data or received user data of given

radio waves.

Function Block•••

RA.1

RA.2

RA.3

RA.N

II-4. Radio Computer

Radio

Storage

Multi Radio Interface (MURI)

Radio Librarynormative description Radio Apps

configcode

Unified Radio

Application

Interface (URAI)

Radio Control Framework

Radio Apps

Source code

Front-end

Compiler

System architecture for Radio Computer

� Case 1: Radio Library and BE compiler are included within theRadio Computer




Radio Programming Interface

configcode

RVMimplementation

Radio Librarynative implementation

Radio OS

Radio Apps

Store

Radio Computer

BECompiler

HW Radio Platform

RF part

upload

configcode

Radio Apps

package

단추Shadow

Radio Platform

II-4. Radio ComputerSystem architecture for Radio Computer

� Case 2: Radio Library and BE compiler are provided at a cloud outside the Radio Computer




III. Reconfiguration ProcessIII. Reconfiguration Process



IIIIII--1. Generation of Radio Application Package1. Generation of Radio Application Package

IIIIII--2. Distribution and Installation of RAP2. Distribution and Installation of RAP

IIIIII--3. Operational Structure of URA3. Operational Structure of URA

IIIIII--4. Implementation of Standard Functional Blocks4. Implementation of Standard Functional Blocks

III-1. Generation of Radio Application PackageWhat should be included in a RAP?


� Platform-specific executable code� Platform-independent source code� Platform-independent IR*

� RAP consists of URA Configuration codes (Configcodes), Metadata, and Radio Controller.



<RA provider>

<URA Configcodes>

IR: Intermediate Representation

<Metadata for compilation>

<Radio Controller>

III-2. Distribution and Installation of RAPConceptual diagram for adopting platform-specific executable code

� URA Configcodes are executable codes� Functional Blocks are compiled for each target platform during the design time


RadioApp Store

RadioApplication

PackageRadio

Application PackageRadio

Application

System Information

RadioApplication

Package

Par

t of

Mob

ile

Dev

ice

rela

ted

to r

econ

figu

rab

le R

adio



Operating System

Loader

Radio Operating System

Loader

StorageApplication Processor

Radio Computer

Functional Blocks (SFBs & UDFBs) Executable Codes

RC Executable Codes

Ra

dio

Ap

plica

tion

Radio Controller

Code

Design Time Installation Time Run Time

Standard Radio

LibraryHeader

Standard & User Defined Functional

Blocks

Compiler C

Compiler BAP

Compiler

Application Package

Compiler A

Installer

RadioController

Par

t of

Mob

ile

Dev

ice

rela

ted

to r

econ

figu

rab

le R

adio

Configcodes

RadioApp StoreMetadata

for Pipeline Configuration

Radio

III-2. Distribution and Installation of RAPConceptual diagram for adopting platform-independent source code

� URA Configcodes are source codes� Functional Blocks are compiled during the installation time

� Compilation process could be performed within the MD� Compilation process could be performed in the cloud

� In the case of dynamic linking, Radio Library Native Implementation should be providedwithin MD

Radio Library for static linkstatic link




Operating System


RCExecutable Code

Radio Computer

Application ProcessorStorage

Loader

LoaderFunctional Blocks (SFBs & UDFBs)Executable Code

Radio A

pplication

RadioLibrary

Encryptor(optional)

APCompiler

RadioApplication

Package

Standard Radio

LibraryHeader

Radio Controller

Code


User Defined Functional Blocks

Decryptor(optional) Installer

RadioController

RadioApplication

Package

Configcodes

Metadata for Pipeline

Configuration

RadioLibrary

Executable Code

Compiler

Radio Library for dynamic linkdynamic link


ConfigurationRadioApp Store

Radio

III-2. Distribution and Installation of RAPConceptual diagram for adopting platform-independent IR

� URA Configcodes are IR� Functional Blocks are front-end/back-end compiled duringthe design/installation time

� Back-end Compilation process could be performed within the MD� Back-end Compilation process could be performed in the cloud

� In the case of dynamic linking, Radio Library Native Implementation should be providedwithin MD

Radio Library for static linkstatic link




Standard Radio

LibraryHeader

Radio Controller

Code


User Defined Functional Blocks

APCompiler

RadioApplication

Package

Front-End Compiler

Installer

RadioController

RadioApplication

Package

Configcodes


Configuration

RadioLibrary

Executable Code

Back-EndCompiler

Operating System


RCExecutable Code

Radio Computer

Application ProcessorStorage

Loader, Dispatcher,

etc.

Loader, Dispatcher,

etc.

Functional Blocks (SFBs & UDFBs)Executable Code

Radio A

pplication

RadioLibrary

Radio Library for dynamic linkdynamic link

III-3. Operational Structure of URAURA Configcodes are executable on a given MD

� All Functional Blocks (SFBs & UDFBs) are already bound in theexecutable Configcodes ofURA




Operational structure of URA when URA configcodes are executable on a target platform

III-3. Operational Structure of URAURA Configcodes are platform-independent source codes/IR

� Only User Defined Functional Blocks are included in the URA Configcodes� Standard Functional Blocks are prepared in a given MD� Function calls of Standard Functional Blocks are provided in the Metadata




Operational structure of URA when URA configcodes are source codes or IR to be compiled

III-3. Operational Structure of URAURA Configcodes consists of executable codes and IR codes

� Operational procedure for the executable codes is equivalent to that of the first case� IR part shall be processed in the RVM




Operational structure of URA when URA configcodes are combined (executable & IR)

III-3. Operational Structure of URARF & RVM Protection Class

� URA choose one RVM Protection Class for code to be executed onthe RVM� An RVM controls RF Transceiver chain, in particular for selection of an RF Protection Class




A typical radio equipment architecture comprising an RVM Software Component selecting RF and/or RVM protection class(es)

III-4. Implementation of Standard Functional Blocks

Implementation of functional blocks libraries on Radio Computer

Radio Library

Exe codes for SFB#3

Exe codes for SFB#M1

Exe

codes

for SFB

#2

Hardware

Accelerator

for

SFB#(M1+M2)

Radio

• Processor dependent

� SFBs typically include all those functional blocks which are commonly used in URA

� SFBs can be implemented in software or




Radio HAL

UDFB

Exe

codes

for S

FB#1

Hardware

Accelerator

for

SFB#(M1+4)

Hardware

Accelerator

for SFB#(M1+1)

Hardware

Accelerator

for SFB#(M1+2)

Hardware

Accelerator

for SFB#(M1+3)

Radio Processor

• Processor & peripheral dependent• Hardware Acceleration

� SFBs can be implemented in software or hardware

�Programmable components

�Dedicated hardware

� The portion of software and hardware will be determined by chip vendor

IV. ConclusionIV. Conclusion



Vision of Reconfigurable MD

with ETSI-Standard Architectures

• The future MD is expected to allow for advanced reconfiguration, enabling usersto acquire and install “Radio Application” software components.

GPS InformationRequest for LTE RA

Radio

IV. ConclusionIV. Conclusion



Long Term EvolutionHanyang Univ.

Mobile WiMAXWiMAX Forum

Wireless MicrophoneJune’s Software House

Walkie TalkieRadio Software Inc.

DECT TelephoneVATEL Software.

Available Carriers

Carrier Selection

SK Telecomm

KT

LG U+

Subscription

1 month

6 months

1 Year

Downloading & Install

Your carrier will be changed in a few minute

Download LTE RA

Radio App Store

Server

<Radio App Store>

Standard Architecture, Related Interfaces, and ... · Standard Architecture, Related Interfaces,...

Documents

Transcript of Standard Architecture, Related Interfaces, and ... · Standard Architecture, Related Interfaces,...