SIST EN 302 969 V1.3.1:2018
(Main)Reconfigurable Radio Systems (RRS) - Radio Reconfiguration related requirements for Mobile Devices
Reconfigurable Radio Systems (RRS) - Radio Reconfiguration related requirements for Mobile Devices
The scope of the present document is to define the high level system requirements for reconfigurable Mobile Devices
enabling the provision of Radio Applications. The work will be based on the Use Cases defined in ETSI
TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na zahteve za mobilne naprave
Področje uporabe tega dokumenta zajema opredelitev sistemskih zahtev za mobilne naprave z možnostjo preoblikovanja na visoki ravni, ki omogočajo zagotovitev radijskih aplikacij. Delo bo temeljilo na primerih uporabe iz dokumentov ETSI TR 103 062 [i.1] in ETSI TR 102 944 [i.2].
General Information
Buy Standard
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Radijski sistemi z možnostjo preoblikovanja (RRS) - Preoblikovanje radia glede na zahteve za mobilne napraveReconfigurable Radio Systems (RRS) - Radio Reconfiguration related requirements for Mobile Devices33.060.01Radijske komunikacije na splošnoRadiocommunications in generalICS:Ta slovenski standard je istoveten z:ETSI EN 302 969 V1.3.1 (2018-05)SIST EN 302 969 V1.3.1:2018en01-september-2018SIST EN 302 969 V1.3.1:2018SLOVENSKI
STANDARD
SIST EN 302 969 V1.3.1:2018
=====bqpf bk mjl sps sk.m.k bljkr-joc oeconfigurable oadio pystems boopc; oadio oeconfiguration related requirements for Mobile aevices
SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc l ===oeference=obkioop-jlko heywords=Copf mobilef pao ETSI poj ooute des iucioles c-jpslk pophia Antipolis Cedex - coAkCb= qel.t emm 4 sl s4 4l jj
caxt emm 4 sm po 4q kp
piret k° m4r plm opl jjjkq - kAc q4l C Association à but non lucratif enregistrée à la pous-mréfecture de drasse bjpc k° qrjmirr
Important notice qhe present document can be downloaded fromt httptiiwww.etsi.orgistandards-search qhe present document may be made available in electronic versions andior in print. qhe content of any electronic andior print versions of the present document shall not be modified without the prior written authorization of bqpf. fn case of any existing or perceived difference in contents between such versions andior in printf the only prevailing document is the print of the mortable aocument cormat bmacc version kept on a specific network drive within bqpf pecretariat. rsers of the present document should be aware that the document may be subject to revision or change of status. fnformation on the current status of this and other bqpf documents is available at httpstiiportal.etsi.orgiqBibqpfaeliverableptatus.aspx ff you find errors in the present documentf please send your comment to one of the following servicest httpstiiportal.etsi.orgimeopleiCommiteepupportptaff.aspx Copyright Notification ko part may be reproduced or utilized in any form or by any meansf electronic or mechanicalf including photocopying and microfilm except as authorized by written permission of bqpf. qhe content of the mac version shall not be modified without the written authorization of bqpf. qhe copyright and the foregoing restriction extend to reproduction in all media.
© bqpf ljkr. All rights reserved.
abCqqjf mirdqbpqpqjf rMqpqj and the bqpf logo are trademarks of bqpf registered for the benefit of its jembers. mdmmqj and iqbqj are trademarks of bqpf registered for the benefit of its jembers and of the mdmm lrganizational martners. oneMlM logo is protected for the benefit of its jembers. dpM® and the dpj logo are trademarks registered and owned by the dpj Association. SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc m Contents fntellectual=mroperty=oights=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=ocoreword=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=ojodal=verbs=terminology=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=ok=pcope=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=pl=oeferences=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=plhk=kormative=references=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=plhl=fnformative=references=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=pm=aefinitions=and=abbreviations=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=pmhk=aefinitions=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=pmhl=Abbreviations=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=rn=oequirement=organization=and=methodology=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=rnhj=deneral=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=rnhk=oequirement=organization=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=rnhl=oequirement=format=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=snhm=oequirement=formulation=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkjo=torking=assumptions=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=kjohk=Assumptions=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkjohkhk=jobile=device=reconfiguration=classes=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkjp=cunctional=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=kmphk=oequirements=on=oAq=link=support=and=management=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkhk=o-crkC-oAq–jk=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkhl=o-crkC-oAq–jl=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkhm=o-crkC-oAq–jm=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkhn=o-crkC-oAq–jn=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkho=o-crkC-oAq–jo=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphkhp=o-crkC-oAq–jp=cunction=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkmphl=oadio=application=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhj=deneral=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhk=o-crkC-oA-jk=oadio=Applications=pupport=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhl=o-crkC-oA-jl=Composition=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhm=o-crkC-oA-jm=Concurrency=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhn=o-crkC-oA-jn=aata=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlho=o-crkC-oA-jo=Context=fnformation=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphlhp=o-crkC-oA-jp=mipelining=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhknphm=oadio=Application=functional=block=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmhk=o-crkC-cB-jk=fmplementation=for=jaoC-l=to=jaoC-qhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmhl=o-crkC-cB-jl=bxecution=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmhm=o-crkC-cB-jm=pide=bffects=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmhn=o-crkC-cB-jn=phared=aata=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmho=o-crkC-cB-jo=Concurrency=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophmhp=o-crkC-cB-jp=bxtendibility=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkophn=jobile=device=reconfiguration=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkpphnhk=o-crkC-jao-jk=mlatform-specific=bxecutable=Code=for=jaoC-lf=jaoC-m=or=jaoC-n=hhhhhhhhhhhhhhhhhhhkpphnhl=o-crkC-jao-jl=mlatform-independent=pource=Code=or=fo=for=jaoC-of=jaoC-p=or=jaoC-q=hhhhhhhhhkpphnhm=o-crkC-jao-jm=oadio=Configuration=of=mlatform=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkpphnhn=o-crkC-jao-jn=oadio=mrogramming=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkpphnho=o-crkC-jao-jo=aynamic=bxecution=for=jaoC-nf=and=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhp=o-crkC-jao-jp=fndependency=on=jemory=jodel=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhq=o-crkC-jao-jq=Code=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhr=o-crkC-jao-jr=fo=cormat=for=jaoC-o=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhs=o-crkC-jao-js=qiming=Constraints=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhkj=o-crkC-jao-kj=mlatform=fndependency=for=jaoC-o=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhkk=o-crkC-jao-kk=oadio=Application=for=jaoC-o=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqSIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc 4 phnhkl=o-crkC-jao-kl=cunction=dranularity=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhkm=o-crkC-jao-km=oadio=sirtual=jachine=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkqphnhkn=o-crkC-jao-kn=oadiosirtual=jachine=ptructure=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhkrphnhko=o-crkC-jao-ko=pelection=of=oadio=sirtual=jachine=mrotection=Class=for=jaoC-l=to=jaoC-q=hhhhhhhhkrpho=oadio=crequencybocc=transceiver=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhksphohj=deneral=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhksphohk=o-crkC-ocq-jk=oc=Configuration=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhksphohl=o-crkC-ocq-jl=bxtendibility=for=multiple-antenna=system=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhksphohm=o-crkC-ocq-jm=Capability=of=multiple=frequency=bands=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphohn=o-crkC-ocq-jn=oeconfigurability=of=oc=qransceiver=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphoho=o-crkC-ocq-jo=fnteroperability=of=radio=resources=for=jaoC-l=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphohp=o-crkC-ocq-jp=qestability=of=radio=equipment=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphohq=o-crkC-ocq-jq=rnified=representation=of=control=information=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhljphohr=o-crkC-ocq-jr=rnified=representation=of=data=payload=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphohs=o-crkC-ocq-js=pelection=of=oc=mrotection=Class=for=jaoC-k=to=jaoC-q=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhljphp=pecurity=requirements=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkphphj=deneral=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkphphk=o-crkC-pbC-jk=obConfmol-oAm-pecurity=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkphphl=o-crkC-pbC-jl=Administration-pecurity=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkphphm=o-crkC-pbC-jm=pecure=janagement=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkphphn=o-crkC-pbC-jn=ooot=of=qrust=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhlkeistory=hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=ll=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc o fntellectual mroperty oights bssential patents fmos=essential=or=potentially=essential=to=normative=deliverables=may=have=been=declared=to=bqpfh=qhe=information=pertaining=to=these=essential=fmosf=if=anyf=is=publicly=available=for=bTpf members and non-membersf=and=can=be=found=in=bqpf=po=jjj=mknt="Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"f=which=is=available=from=the=bqpf=pecretariath=iatest=updates=are=available=on=the=bqpf=teb=server=bhttpstiiiprhetsihorgich=mursuant=to=the=bqpf=fmo=molicyf=no=investigationf=including=fmo=searchesf=has=been=carried=out=by=bqpfh=ko=guarantee=can=be=given=as=to=the=existence=of=other=fmos=not=referenced=in=bqpf=po=jjj=mkn=bor=the=updates=on=the=bqpf=teb=serverc=which=aref=or=may=bef=or=may=becomef=essential=to=the=present=documenth=qrademarks qhe=present=document=may=include=trademarks=andior=tradenames=which=are=asserted=andior=registered=by=their=ownersh=bqpf=claims=no=ownership=of=these=except=for=any=which=are=indicated=as=being=the=property=of=bqpff=and=conveys=no=right=to=use=or=reproduce=any=trademark=andior=tradenameh=jention=of=those=trademarks=in=the=present=document=does=not=constitute=an=endorsement=by=bqpf=of=productsf=services=or=organizations=associated=with=those=trademarksh=coreword qhis=buropean=ptandard=bbkc=has=been=produced=by=bqpf=qechnical=Committee=oeconfigurable=oadio=pystems=boopch==kational transposition dates aate=of=adoption=of=this=bkt=kq=jay=ljkr=aate=of=latest=announcement=of=this=bk=bdoact=mk=August=ljkr=aate=of=latest=publication=of=new=kational=ptandard=or=endorsement=of=this=bk=bdopiect==lr=cebruary=ljks=aate=of=withdrawal=of=any=conflicting=kational=ptandard=bdowct=lr=cebruary=ljks==jodal verbs terminology fn=the=present=document="shall"f="shall not"f="should"f="should not"f="may"f="need not"f="will"f="will not"f="can"=and="cannot"=are=to=be=interpreted=as=described=in=clause=mhl=of=the=bqpf=arafting=oules=bserbal=forms=for=the=expression=of=provisionsch="must"=and="must not"=are=klT=allowed=in=bqpf=deliverables=except=when=used=in=direct=citationh=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc p k pcope qhe=scope=of=the=present=document=is=to=define=the=high=level=system=requirements=for=reconfigurable=jobile=aevices=enabling=the=provision=of=oadio=Applicationsh=qhe=work=will=be=based=on=the=rse=Cases=defined=in=bqpf=qo=kjm=jpl=xihkz=and=bqpf=qo=kjl=snn=xihlzh=l oeferences l.k kormative references oeferences=are=either=specific=bidentified=by=date=of=publication=andior=edition=number=or=version=numberc=or=non-specifich=cor=specific=referencesf=only=the=cited=version=appliesh=cor=non-specific=referencesf=the=latest=version=of=the=referenced=document=bincluding=any=amendmentsc=appliesh=oeferenced=documents=which=are=not=found=to=be=publicly=available=in=the=expected=location=might=be=found=at=httpstiidocboxhetsihorgioeferenceih=klqbt=thile=any=hyperlinks=included=in=this=clause=were=valid=at=the=time=of=publicationf=bqpf=cannot=guarantee=their=long=term=validityh=qhe=following=referenced=documents=are=necessary=for=the=application=of=the=present=documenth=kot=applicableh=l.l fnformative references oeferences=are=either=specific=bidentified=by=date=of=publication=andior=edition=number=or=version=numberc=or=non-specifich=cor=specific=referencesf=only=the=cited=version=appliesh=cor=non-specific=referencesf=the=latest=version=of=the=referenced=document=bincluding=any=amendmentsc=appliesh=klqbt=thile=any=hyperlinks=included=in=this=clause=were=valid=at=the=time=of=publicationf=bqpf=cannot=guarantee=their=long=term=validityh=qhe=following=referenced=documents=are=not=necessary=for=the=application=of=the=present=document=but=they=assist=the=user=with=regard=to=a=particular=subject=areah=xihkz=bqpf=qo=kjm=jplt="oeconfigurable=oadio=pystems=boopcu=rse=Cases=and=pcenarios=for=poftware=aefined=oadio=bpaoc=oeference=Architecture=for=jobile=aevice"h=xihlz=bqpf=qo=kjl=snnt="oeconfigurable=oadio=pystems=boopcu=rse=Cases=for=Baseband=fnterfaces=for=rnified=oadio=Applications=of=jobile=aevice"h=m aefinitions and abbreviations m.k aefinitions cor=the=purposes=of=the=present=documentf=the=following=terms=and=definitions=applyt=cunctional Block bcBc:=function=needed=for=real-time=implementation=of=oadio=Applicationbsc=klqb=kt=A=functional=block=includes=not=only=the=modem=functions=in=iayerk=bikcf=iayerl=bilcf=and=iayer=m=bimc=but=also=all=the=control=functions=that=should=be=processed=in=real-time=for=implementing=given=oadio=Applicationbsch=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc q klqb=lt=cunctional=blocks=are=categorized=into=standard functional blocks and=user defined functional blocksh=fn=more=detailst=kc=Standard functional blocks can=be=shared=by=many=oadio=Applicationsh=cor=examplef=corward=brror=Correction=bcbCcf=cast=courier=qransform=bccqcifnverse=cast=courier=qransform=bfccqcf=bdecinterleaverf=qurbo=codingf=siterbi=codingf=jultiple=fnput=jultiple=lutput=bjfjlcf=Beamformingf=etch=are=the=typical=category=of=standard=functional=blockh=lc=User defined functional blocks include=those=functional=blocks=that=are=dependent=upon=a=specific=oadio=Applicationh=qhey=are=used=to=support=special=functionbsc=required=in=a=specific=oadio=Application=or=to=support=a=special=algorithm=used=for=performance=improvementh=fn=additionf=a=user=defined=functional=block=can=be=used=as=a=baseband=controller=functional=block=which=controls=the=functional=blocks=operating=in=baseband=processor=in=real-time=and=to=control=some=context=information=processed=in=real-timeh=klqb=mt=bach=functional=block=has=its=unique=namef=fnputf=lutput=and=propertiesh=network coding:=technique=in=which=transmitted=data=is=encoded=and=decoded=to=improve=network=performance=oadio Application boAc: software=which=enforces=the=generation=of=the=transmit=oc=signals=or=the=decoding=of=the=receive=oc=signals=klqb=kt=qhe=software=is=executed=on=a=particular=radio=platform=or=an=osj=as=part=of=the=radio=platformh=klqb=lt=oadio=applications=might=have=different=forms=of=representationh=qhey=are=represented=ast= source=codes=including=radio=library=calls=of=radio=library=native=implementation=and=oadio=eAi=callsu= fntermediate=oepresentations=bfosc=including=radio=library=calls=of=radio=library=native=implementation=and=radio=eAi=callsu= bxecutable=codes=for=a=particular=radio=platformh=radio library: library=of=ptandard=cunctional=Blocks=bpcBc=that=is=provided=by=a=platform=vendor=in=a=form=of=platform-specific=executable=code=klqb=kt=pcBs=implement=reference=codes=of=functions=which=are=typical=for=radio=signal=processingh=qhey=are=not=atomic=and=their=source=codes=are=typed=and=visible=for=oadio=Application=developersh=klqb=lt=An=pcB=is=implemented=through=a=oadio=eardware=Abstraction=iayer=beAic=when=the=pcB=is=implemented=on=dedicated=et=acceleratorsh=oadio=eAi=is=part=of=olph=oadio sirtual Machine bosMc: abstract=machine=supporting=reactive=and=concurrent=executions klqbt=A=oadio=sirtual=jachine=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=bre-c=certification=effortsh=reconfigurable mobile device: mobile=device=with=radio=communication=capabilities=providing=support=for=radio=reconfiguration=klqbt=oeconfigurable=mobile=devices=include=but=are=not=limited=tot=smartphonesf=feature=phonesf=tabletsf=laptopsh=resources:=hardware=resources=that=a=oadio=Application=needs=in=active=state=klqb=kt=oesources=are=provided=by=the=reconfigurable=jobile=aevice=bjacf=to=be=used=by=the=oadio=Applications=when=they=are=activeh=oadio=Applications=provide=their=resource=needs=behgh=using=operational=statesc=so=that=the=multiradio=computer=may=judge=whether=these=resources=are=availablef=in=order=to=ensure=non-conflicting=operation=with=other=oadio=Applicationsh=oesources=may=or=may=not=be=shared=in=the=reconfigurable=jah=klqb=lt=oesources=may=include=processorsf=acceleratorsf=memoryf=oadio=crequency=circuitryf=etch=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc r m.l Abbreviations cor=the=purposes=of=the=present=documentf=the=following=abbreviations=applyt=ApfC=Application=ppecific=fntegrated=Circuit=Bbo=Bit=brror=oate=CAq=CAqegory=Co=Cognitive=oadio=cB=cunctional=Block=cbC=corward=brror=Correction=ccq=cast=courier=qransform=eAi=eardware=Abstraction=iayer=fo=fntermediate=oepresentation=iqb=iong=qerm=bvolution=jAC=jedia=Access=Control=ja=jobile=aevice=jaoC=jobile=aevice=oeconfiguration=Class=jfjl=julti-fnput=julti-lutput=jr-jfjl=julti=rser-=julti-fnput=julti-lutput=mbo=macket=brror=oate=mjf=mrecoding=jatrix=fndicator=oA=oadio=Application=oAq=oadio=Access=qechnology=oc=oadio=crequency=of=oank=fndicator=olp=oadio=lperating=pystem=oop=oeconfigurable=oadio=pystems=oppf=oeceived=pignal=ptrength=fndication=osj=oadio=sirtual=jachine=ox=oeceive=pao=poftware=aefined=oadio=pcB=ptandard=cunctional=Block=pfko=pignal=to=fnterference-plus-koise=oatio=pr-jfjl=pingle=rser-=julti-fnput=julti-lutput=qx=qransmit=racB=rser=aefined=cunctional=Block=tici=tireless=cidelity=4 oequirement organization and methodology 4.j deneral qhis=clause=is=containing=the=description=of=how=the=requirements=are=organized=and=the=related=formath=4.k oequirement organization As=shown=in=cigure=kf=all=requirements=described=in=the=present=document=belong=to=one=single=category=bthe=functional=requirements=categorych=oequirements=aref=in=turnf=organized=into=groupsh=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc s
cigure k: lverall requirements structure 4.l oequirement format A=letter=code=system=is=defined=which=makes=a=unique=identification=of=each=requirement=o---h=bach=requirement=is=constructed=as=followst= o-t=ptandard=requirement=prefix= =Code Category crkC cunctional aspects = t=oequirement=group=identifierh=A=letter=code=will=be=used=for=this=identifierh=qhe=three=first=letters=will=give=the=identifier=of=the=group= t=oequirement=identifier=within=requirement=groupu=range=jk==>=ss=buAjmibt=o-crkC-nlp-jkh=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc kM 4.m oequirement formulation A=requirement=is=formulated=in=such=a=way=that=it=is=uniquely=definedh=ft=is=built=as=followst=qitlet== aescriptiont=the=description=of=a=requirement=will=be=formulated=using=one=of=the=following=termst=- "shall"=is=used=to=express=mandatory=requirements=biheh=provisions=that=have=to=be=followedc=- "should"=is=used=to=express=recommendations=bprovisions=that=an=implementation=is=expected=to=follow=unless=there=is=a=strong=reason=for=not=doing=soc=- "jay"=is=used=to=express=permissible=actions=bprovisions=that=an=implementation=is=able=to=follow=or=not=followc=o torking assumptions o.k Assumptions o.k.k jobile device reconfiguration classes As=it=is=expected=that=the=reconfiguration=capabilities=of=a=jobile=aevice=will=evolve=over=timef=jobile=aevice=oeconfiguration=Classes=bjaoCc=are=introducedh=As=shown=in=cigure=lf=q=different=classes=of=reconfigurable=ja=are=introduced=bjaoC-j=corresponds=to=a=non-reconfigurable=devicech= cigure l: aefinition of MaoCs according to reconfiguration capabilities A=reconfigurable=ja=belongs=to=a=defined=class=according=to=the=reconfiguration=capabilitiesf=which=are=determined=by=the=type=of=oesource=requirements=and=the=form=of=the=oadio=Application=mackageh=oeconfigurable=ja=classes=are=defined=as=follows=bsee=also=cigure=lct=kc jaoC-jt=ko=ja=reconfiguration=is=possible=jaoC-j=represents=legacy=radio=implementations=and=do=not=allow=for=ja=reconfiguration=bexcept=for=bug=fixing=and=release-updates=through=firmware=updatesc=or=exploitation=of=Cognitive=oadio=bCoc=featuresh=jaoC-j=represents=legacy=radio=implementations=and=does=not=allow=for=ja=reconfigurationh=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc kk lc jaoC-kt=oadio=Applications=use=different=fixed=oesources=fn=this=scenariof=at=least=some=of=the=radios=are=implemented=with=non-software=defined=radio=bpaoc=technologyf=ehgh=with=dedicated=Application=ppecific=fntegrated=Circuits=bApfCscf=and=are=oesource-wise=independent=of=each=otherh=pimple=Co=functionality=may=be=supported=through=radio=parameter=management=to=the=extent=which=the=radio=implementations=allowh=jaoC-k=implements=multiple=oadio=Applications=with=fixed=oesources=allocation=and=no=oesource=sharingh==qhe=rule=for=oesource=allocation=for=multiple=applications={A1f=A2f=…f=AN}=can=be=formulated=as=followst==Ai==Rif=i{kf=hhhf=N}f=where=Ri=denotes=oesources=allocated=for=application=Ai=and=Ri= Rj====for=i =jh=kote=that=applications=can=be=run=concurrently=in=any=combinationu=a=oesource=allocation=mechanism=within=separate=applications=is=not=specifiedh=mc jaoC-lt=oadio=Applications=use=pre-defined=static=oesources=jaoC-l=implements=multiple=oadio=Applications=but=no=dynamic=oesource=management=is=availableh=qhe=oadio=Applications=for=jaoC-l=come=from=a=single=oadio=Application=mackage=which=is=normally=provided=by=a=reconfigurable=ja=vendor=or=pao=chipset=manufacturerh=fn=this=scenariof=it=is=assumed=that=software=radio=components=in=the=oadio=Application=mackage=are=provided=in=platform-specific=executable=codeh=qhe=rule=for=the=oesource=allocation=related=to=multiple=applications{A1f=A2f=…f=AN}can=be=formulated=as=followst=Ai=Rif=i{kf=hhhf=N}f=where=Ri=denotes=oesources=allocated=for=application=Aif=if= i =j=so=that==Ri= Rj===then=such=applications=cannot=be=run=concurrentlyf=all=other=combinations=are=allowedu=a=oesource=allocation=mechanism=within=separate=applications=is=not=specifiedh=nc jaoC-mt=oadio=Applications=have=static=oesource=requirements=cor=jaoC-mf=a=oesource=budget=is=defined=for=each=oadio=Applicationh=qhis=budget=contains=a=static=oesource=measure=that=represents=the=worst-case=oesource=usage=of=the=applicationf=generated=at=oadio=Application=compile-timeh=ff=an=application=is=being=startedf=the=oesource=manager=installed=in=a=reconfigurable=ja=of=jaoC-m=checks=its=oesource=budget=and=the=sum=of=all=oesource=budgets=of=already=running=applicationsf=and=admits=the=new=application=only=if=the=oesources=can=still=be=guaranteed=for=all=running=applicationsh=fn=this=scenariof=it=is=assumed=that=software=radio=components=in=the=oadio=Application=mackage=are=provided=in=platform-specific=executable=codeh=qhe=rule=for=oesource=allocation=for=multiple=applications{A1f=A2f=…f=AN}can=be=formulated=as=followst==Ai=Aicf=where=o=denotes=total=oesources=to=be=shared=and=obAic=denotes=a=part=of=o=allocated=for=Aiu=if=for=i1f=i2f=hhhf=iM={kf=hhhf=N}f=M==Nf=obAi1c==obAi2c==hhh==obAiMc==o=then=applications=Ai1f=Ai2f=…f=AiM=can=be=run=concurrentlyu=a=oesource=allocation=mechanism=within=separate=applications=is=not=specifiedh=oc jaoC-nt=oadio=Applications=have=dynamic=oesource=requirements=qhis=scenario=assumes=a=similar=oesource=manager=in=a=reconfigurable=ja=as=for=jaoC-mf=but=in=addition=the=oadio=Applications=have=now=varying=oesource=demands=based=on=their=current=type=of=activityh=Applications=have=separate=operational=states=for=different=types=of=activityf=and=a=oesource=budget=is=assigned=to=each=operational=stateh=fn=this=scenariof=it=is=assumed=that=software=radio=components=in=the=oadio=Application=mackage=are=provided=in=platform-specific=executable=codeh=oesource=management=for=jaoC-n=can=be=formulated=as=followsh=jultiple=applications{A1f=A2f=…f=AN}can=be=run=and=each=applicationAiis=divided=into=tasks={t1bAicf=t2bAicf=hhhf=tkbAic}h=oesource=allocation=is=provided=by=the=oesource=manager=in=a=reconfigurable=ja=for=each=task=tjbAic==obtjbAicch=qhe=rule=for=task=running=is=exactly=the=same=as=for=jaoC-m=except=that=each=application=should=be=replaced=by=a=corresponding=taskh=qhereforef=if=for=i1f=i2f=hhhf=iM={kf=hhhf=N}f=M==Nf=obtj1bAi1cc==obtj2bAi2cc==hhh==obtjLbAiMcc==o=then=tasks=tj1bAi1cf=tj2bAi2cf=hhhf=tjLbAiMc=can=be=run=concurrentlyu=a=oesource=allocation=mechanism=within=separate=tasks=is=not=specifiedh=SIST EN 302 969 V1.3.1:2018
ETSI bqpf bk mMl sps sk.m.k blMkr-Moc kl pc jaoC-ot=oadio=Applications=use=pre-defined=static=oesourcesf=on-device=compilation=of=poftware=oadio=Components=qhis=class=corresponds=to=jaoC-l=with=the=difference=that=all=or=part=of=the=software=radio=components=are=provided=in=the=oadio=Application=mackage=as=platform-independent=source=code=or=platform-independent=fntermediate=oepresentation=bfocf=which=is=compiled=on=the=reconfigurable=ja=itselfh=ft=particularly=means=that=the=reconfigu
...
ETSI EN 302 969 V1.3.1 (2018-05)
������������������
Reconfigurable Radio Systems (RRS);
Radio Reconfiguration related requirements
for Mobile Devices
---------------------- Page: 1 ----------------------
2 ETSI EN 302 969 V1.3.1 (2018-05)
Reference
REN/RRS-0215
Keywords
CRS, mobile, SDR
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
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
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI EN 302 969 V1.3.1 (2018-05)
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 . 6�
3.1 Definitions . 6�
3.2 Abbreviations . 8�
4 Requirement organization and methodology . 8�
4.0 General . 8�
4.1 Requirement organization . 8�
4.2 Requirement format . 9�
4.3 Requirement formulation .10�
5 Working assumptions . 10�
5.1 Assumptions .10�
5.1.1 Mobile device reconfiguration classes .10�
6 Functional requirements . 13�
6.1 Requirements on RAT link support and management .13�
6.1.1 R-FUNC-RAT–01 Function for MDRC-1 to MDRC-7 .13�
6.1.2 R-FUNC-RAT–02 Function for MDRC-1 to MDRC-7 .13�
6.1.3 R-FUNC-RAT–03 Function for MDRC-1 to MDRC-7 .13�
6.1.4 R-FUNC-RAT–04 Function for MDRC-1 to MDRC-7 .13�
6.1.5 R-FUNC-RAT–05 Function for MDRC-1 to MDRC-7 .13�
6.1.6 R-FUNC-RAT–06 Function for MDRC-1 to MDRC-7 .13�
6.2 Radio application requirements .14�
6.2.0 General .14�
6.2.1 R-FUNC-RA-01 Radio Applications Support for MDRC-1 to MDRC-7 .14�
6.2.2 R-FUNC-RA-02 Composition for MDRC-1 to MDRC-7 .14�
6.2.3 R-FUNC-RA-03 Concurrency for MDRC-1 to MDRC-7 .14�
6.2.4 R-FUNC-RA-04 Data for MDRC-1 to MDRC-7 .14�
6.2.5 R-FUNC-RA-05 Context Information for MDRC-1 to MDRC-7 .14�
6.2.6 R-FUNC-RA-06 Pipelining for MDRC-2 to MDRC-7 .14�
6.3 Radio Application functional block requirements .15�
6.3.1 R-FUNC-FB-01 Implementation for MDRC-2 to MDRC-7.15�
6.3.2 R-FUNC-FB-02 Execution for MDRC-2 to MDRC-7 .15�
6.3.3 R-FUNC-FB-03 Side Effects for MDRC-2 to MDRC-7 .15�
6.3.4 R-FUNC-FB-04 Shared Data for MDRC-2 to MDRC-7 .15�
6.3.5 R-FUNC-FB-05 Concurrency for MDRC-2 to MDRC-7 .15�
6.3.6 R-FUNC-FB-06 Extendibility for MDRC-2 to MDRC-7 .15�
6.4 Mobile device reconfiguration requirements .16�
6.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 .16�
6.4.2 R-FUNC-MDR-02 Platform-independent Source Code or IR for MDRC-5, MDRC-6 or MDRC-7 .16�
6.4.3 R-FUNC-MDR-03 Radio Configuration of Platform MDRC-1 to MDRC-7 .16�
6.4.4 R-FUNC-MDR-04 Radio Programming for MDRC-1 to MDRC-7 .16�
6.4.5 R-FUNC-MDR-05 Dynamic Execution for MDRC-4, and MDRC-7 .17�
6.4.6 R-FUNC-MDR-06 Independency on Memory Model for MDRC-1 to MDRC-7 .17�
6.4.7 R-FUNC-MDR-07 Code for MDRC-2 to MDRC-7 .17�
6.4.8 R-FUNC-MDR-08 IR Format for MDRC-5 to MDRC-7 .17�
6.4.9 R-FUNC-MDR-09 Timing Constraints for MDRC-1 to MDRC-7 .17�
6.4.10 R-FUNC-MDR-10 Platform Independency for MDRC-5 to MDRC-7 .17�
6.4.11 R-FUNC-MDR-11 Radio Application for MDRC-5 to MDRC-7 .17�
ETSI
---------------------- Page: 3 ----------------------
4 ETSI EN 302 969 V1.3.1 (2018-05)
6.4.12 R-FUNC-MDR-12 Function Granularity for MDRC-1 to MDRC-7 .17�
6.4.13 R-FUNC-MDR-13 Radio Virtual Machine for MDRC-2 to MDRC-7 .17�
6.4.14 R-FUNC-MDR-14 RadioVirtual Machine Structure for MDRC-2 to MDRC-7 .18�
6.4.15 R-FUNC-MDR-15 Selection of Radio Virtual Machine Protection Class for MDRC-2 to MDRC-7 .18�
6.5 Radio Frequency(RF) transceiver requirements .19�
6.5.0 General .19�
6.5.1 R-FUNC-RFT-01 RF Configuration for MDRC-1 to MDRC-7 .19�
6.5.2 R-FUNC-RFT-02 Extendibility for multiple-antenna system for MDRC-1 to MDRC-7 .19�
6.5.3 R-FUNC-RFT-03 Capability of multiple frequency bands for MDRC-1 to MDRC-7 .20�
6.5.4 R-FUNC-RFT-04 Reconfigurability of RF Transceiver for MDRC-1 to MDRC-7 .20�
6.5.5 R-FUNC-RFT-05 Interoperability of radio resources for MDRC-2 to MDRC-7 .20�
6.5.6 R-FUNC-RFT-06 Testability of radio equipment for MDRC-1 to MDRC-7 .20�
6.5.7 R-FUNC-RFT-07 Unified representation of control information for MDRC-1 to MDRC-7 .20�
6.5.8 R-FUNC-RFT-08 Unified representation of data payload for MDRC-1 to MDRC-7 .20�
6.5.9 R-FUNC-RFT-09 Selection of RF Protection Class for MDRC-1 to MDRC-7 .20�
6.6 Security requirements .21�
6.6.0 General .21�
6.6.1 R-FUNC-SEC-01 REConfPol-RAP-Security .21�
6.6.2 R-FUNC-SEC-02 Administration-Security .21�
6.6.3 R-FUNC-SEC-03 Secure Management .21�
6.6.4 R-FUNC-SEC-04 Root of Trust .21�
History . 22�
ETSI
---------------------- Page: 4 ----------------------
5 ETSI EN 302 969 V1.3.1 (2018-05)
Intellectual Property Rights
Essential patents
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
server (https://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.
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.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
National transposition dates
Date of adoption of this EN: 17 May 2018
Date of latest announcement of this EN (doa): 31 August 2018
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2019
Date of withdrawal of any conflicting National Standard (dow): 28 February 2019
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: 5 ----------------------
6 ETSI EN 302 969 V1.3.1 (2018-05)
1 Scope
The scope of the present document is to define the high level system requirements for reconfigurable Mobile Devices
enabling the provision of Radio Applications. The work will be based on the Use Cases defined in ETSI
TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
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.
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
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 TR 103 062: "Reconfigurable Radio Systems (RRS); Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Functional Block (FB): function needed for real-time implementation of Radio Application(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given Radio
Application(s).
ETSI
---------------------- Page: 6 ----------------------
7 ETSI EN 302 969 V1.3.1 (2018-05)
NOTE 2: Functional blocks are categorized into standard functional blocks and user defined functional blocks. In
more details:
1) Standard functional blocks can be shared by many Radio Applications. For example, Forward Error
Correction (FEC), Fast Fourier Transform (FFT)/Inverse Fast Fourier Transform (IFFT),
(de)interleaver, Turbo coding, Viterbi coding, Multiple Input Multiple Output (MIMO),
Beamforming, etc. are the typical category of standard functional block.
2) User defined functional blocks include those functional blocks that are dependent upon a specific
Radio Application. They are used to support special function(s) required in a specific Radio
Application or to support a special algorithm used for performance improvement. In addition, a
user defined functional block can be used as a baseband controller functional block which controls
the functional blocks operating in baseband processor in real-time and to control some context
information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output and properties.
network coding: technique in which transmitted data is encoded and decoded to improve network performance
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: Radio applications 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;
� Intermediate Representations (IRs) including radio library calls of radio library native
implementation and radio HAL calls;
� Executable codes for a particular radio platform.
radio library: library of Standard Functional Blocks (SFB) that is provided by a platform vendor in a form of platform-
specific executable code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for Radio Application developers.
NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on dedicated HW accelerators. Radio HAL is part of ROS.
Radio Virtual Machine (RVM): abstract machine supporting reactive and concurrent executions
NOTE: A Radio Virtual Machine 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.
reconfigurable mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets,
laptops.
resources: hardware resources that a Radio Application needs in active state
NOTE 1: Resources are provided by the reconfigurable Mobile Device (MD), to be used by the Radio Applications
when they are active. Radio Applications provide their resource needs (e.g. using operational states) so
that the multiradio computer may judge whether these resources are available, in order to ensure non-
conflicting operation with other Radio Applications. Resources may or may not be shared in the
reconfigurable MD.
NOTE 2: Resources may include processors, accelerators, memory, Radio Frequency circuitry, etc.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI EN 302 969 V1.3.1 (2018-05)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASIC Application Specific Integrated Circuit
BER Bit Error Rate
CAT CATegory
CR Cognitive Radio
FB Functional Block
FEC Forward Error Correction
FFT Fast Fourier Transform
HAL Hardware Abstraction Layer
IR Intermediate Representation
LTE Long Term Evolution
MAC Media Access Control
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input Multi-Output
MU-MIMO Multi User- Multi-Input Multi-Output
PER Packet Error Rate
PMI Precoding Matrix Indicator
RA Radio Application
RAT Radio Access Technology
RF Radio Frequency
RI Rank Indicator
ROS Radio Operating System
RRS Reconfigurable Radio Systems
RSSI Received Signal Strength Indication
RVM Radio Virtual Machine
Rx Receive
SDR Software Defined Radio
SFB Standard Functional Block
SINR Signal to Interference-plus-Noise Ratio
SU-MIMO Single User- Multi-Input Multi-Output
Tx Transmit
UDFB User Defined Functional Block
WiFi Wireless Fidelity
4 Requirement organization and methodology
4.0 General
This clause is containing the description of how the requirements are organized and the related format.
4.1 Requirement organization
As shown in Figure 1, all requirements described in the present document belong to one single category (the functional
requirements category). Requirements are, in turn, organized into groups.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI EN 302 969 V1.3.1 (2018-05)
Figure 1: Overall requirements structure
4.2 Requirement format
A letter code system is defined which makes a unique identification of each requirement R---.
Each requirement is constructed as follows:
� R-: Standard requirement prefix
�
Code Category
FUNC Functional aspects
� : Requirement group identifier. A letter code will be used for this identifier. The three first letters
will give the identifier of the group
� : Requirement identifier within requirement group; range 01 => 99
EXAMPLE: R-FUNC-QOS-01.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI EN 302 969 V1.3.1 (2018-05)
4.3 Requirement formulation
A requirement is formulated in such a way that it is uniquely defined. It is built as follows:
Title: </br>
� Description: the description of a requirement will be formulated using one of the following terms:</br>
- "shall" is used to express mandatory requirements (i.e. provisions that have to be followed)</br>
- "should" is used to express recommendations (provisions that an implementation is expected to follow</br>
unless there is a strong reason for not doing so)</br>
- "May" is used to express permissible actions (provisions that an implementation is able to follow or not</br>
follow)</br>
5 Working assumptions</br>
5.1 Assumptions</br>
5.1.1 Mobile device reconfiguration classes</br>
As it is expected that the reconfiguration capabilities of a Mobile Device will evolve over time, Mobile Device</br>
Reconfiguration Classes (MDRC) are introduced. As shown in Figure 2, 7 different classes of reconfigurable MD are</br>
introduced (MDRC-0 corresponds to a non-reconfigurable device).</br>
</br>
Figure 2: Definition of MDRCs according to reconfiguration capabilities</br>
A reconfigurable MD belongs to a defined class according to the reconfiguration capabilities, which are determined by</br>
the type of Resource requirements and the form of the Radio Application Package. Reconfigurable MD classes are</br>
defined as follows (see also Figure 2):</br>
1) MDRC-0: No MD reconfiguration is possible</br>
MDRC-0 represents legacy radio implementations and do not allow for MD reconfiguration (except for bug</br>
fixing and release-updates through firmware updates) or exploitation of Cognitive Radio (CR) features.</br>
MDRC-0 represents legacy radio implementations and does not allow for MD reconfiguration.</br>
ETSI</br>
</br>
---------------------- Page: 10 ----------------------</br>
11 ETSI EN 302 969 V1.3.1 (2018-05)</br>
2) MDRC-1: Radio Applications use different fixed Resources</br>
In this scenario, at least some of the radios are implemented with non-software defined radio (SDR)</br>
technology, e.g. with dedicated Application Specific Integrated Circuits (ASICs), and are Resource-wise</br>
independent of each other. Simple CR functionality may be supported through radio parameter management to</br>
the extent which the radio implementations allow.</br>
MDRC-1 implements multiple Radio Applications with fixed Resources allocation and no Resource sharing.</br>
The rule for Resource allocation for multiple applications {A , A , …, A } can be formulated as follows:</br>
1 2 N</br>
A � R , �i�{1, ., N}, where R denotes Resources allocated for application A and R � R = � for �i � j.</br>
i i i i i j</br>
Note that applications can be run concurrently in any combination; a Resource allocation mechanism within</br>
separate applications is not specified.</br>
3) MDRC-2: Radio Applications use pre-defined static Resources</br>
MDRC-2 implements multiple Radio Applications but no dynamic Resource management is available. The</br>
Radio Applications for MDRC-2 come from a single Radio Application Package which is normally provided</br>
by a reconfigurable MD vendor or SDR chipset manufacturer. In this scenario, it is assumed that software</br>
radio components in the Radio Application Package are provided in platform-specific executable code.</br>
The rule for the Resource allocation related to multiple applications�{A , A , …, A }�can be formulated as</br>
1 2 N</br>
follows: A �R , �i�{1, ., N}, where R denotes Resources allocated for application A , if � i � j so that</br>
i i i i</br>
R � R � � then such applications cannot be run concurrently, all other combinations are allowed; a Resource</br>
i j</br>
allocation mechanism within separate applications is not specified.</br>
4) MDRC-3: Radio Applications have static Resource requirements</br>
For MDRC-3, a Resource budget is defined for each Radio Application. This budget contains a static Resource</br>
measure that represents the worst-case Resource usage of the application, generated at Radio Application</br>
compile-time. If an application is being started, the Resource manager installed in a reconfigurable MD of</br>
MDRC-3 checks its Resource budget and the sum of all Resource budgets of already running applications, and</br>
admits the new application only if the Resources can still be guaranteed for all running applications. In this</br>
scenario, it is assumed that software radio components in the Radio Application Package are provided in</br>
platform-specific executable code.</br>
The rule for Resource allocation for multiple applications�{A , A , …, A }�can be formulated as follows:</br>
1 2 N</br>
A ����A ), where R denotes total Resources to be shared and R(A ) denotes a part of R allocated for A ; if for</br>
i i i i</br>
i1, i2, ., iM �{1, ., N}, M � N, R(A ) � R(A ) � . � R(A ) � R then applications A , A , …, A can</br>
i1 i2 iM i1 i2 iM</br>
be run concurrently; a Resource allocation mechanism within separate applications is not specified.</br>
5) MDRC-4: Radio Applications have dynamic Resource requirements</br>
This scenario assumes a similar Resource manager in a reconfigurable MD as for MDRC-3, but in addition the</br>
Radio Applications have now varying Resource demands based on their current type of activity. Applications</br>
have separate operational states for different types of activity, and a Resource budget is assigned to each</br>
operational state. In this scenario, it is assumed that software radio components in the Radio Application</br>
Package are provided in platform-specific executable code.</br>
Resource management for MDRC-4 can be formulated as follows. Multiple applications�{A , A , …, A }�can</br>
1 2 N</br>
be run and each application�A �is divided into tasks {t (A ), t (A ), ., t (A )}. Resource allocation is provided</br>
i 1 i 2 i k i</br>
by the Resource manager in a reconfigurable MD for each task t (A ) � R(t (A )).</br>
j i j i</br>
The rule for task running is exactly the same as for MDRC-3 except that each application should be replaced</br>
by a corresponding task. Therefore, if for i1, i2, ., iM �{1, ., N}, M � N, R(t (A )) � R(t (A )) � . �</br>
j1 i1 j2 i2</br>
R(t (A )) � R then tasks t (A ), t (A ), ., t (A ) can be run concurrently; a Resource allocation</br>
jL iM j1 i1 j2 i2 jL iM</br>
mechanism within separate tasks is not specified.</br>
ETSI</br>
</br>
---------------------- Page: 11 ----------------------</br>
12 ETSI EN 302 969 V1.3.1 (2018-05)</br>
6) MDRC-5: Radio Applications use pre-defined static Resources, on-device compilation of Software Radio</br>
<b>...</b>
Draft ETSI EN 302 969 V1.2.10 (2018-02)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
Radio Reconfiguration related requirements
for Mobile Devices
---------------------- Page: 1 ----------------------
2 Draft ETSI EN 302 969 V1.2.10 (2018-02)
Reference
REN/RRS-0215
Keywords
CRS, mobile, SDR
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
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
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 Draft ETSI EN 302 969 V1.2.10 (2018-02)
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 . 6
3.1 Definitions . 6
3.2 Abbreviations . 8
4 Requirement organization and methodology . 8
4.0 General . 8
4.1 Requirement organization . 8
4.2 Requirement format . 9
4.3 Requirement formulation . 10
5 Working assumptions . 10
5.1 Assumptions . 10
5.1.1 Mobile device reconfiguration classes . 10
6 Functional requirements . 13
6.1 Requirements on RAT link support and management . 13
6.1.1 R-FUNC-RAT–01 Function for MDRC-1 to MDRC-7 . 13
6.1.2 R-FUNC-RAT–02 Function for MDRC-1 to MDRC-7 . 13
6.1.3 R-FUNC-RAT–03 Function for MDRC-1 to MDRC-7 . 13
6.1.4 R-FUNC-RAT–04 Function for MDRC-1 to MDRC-7 . 13
6.1.5 R-FUNC-RAT–05 Function for MDRC-1 to MDRC-7 . 13
6.1.6 R-FUNC-RAT–06 Function for MDRC-1 to MDRC-7 . 13
6.2 Radio application requirements . 14
6.2.0 General . 14
6.2.1 R-FUNC-RA-01 Radio Applications Support for MDRC-1 to MDRC-7 . 14
6.2.2 R-FUNC-RA-02 Composition for MDRC-1 to MDRC-7 . 14
6.2.3 R-FUNC-RA-03 Concurency for MDRC-1 to MDRC-7 . 14
6.2.4 R-FUNC-RA-04 Data for MDRC-1 to MDRC-7 . 14
6.2.5 R-FUNC-RA-05 Context Information for MDRC-1 to MDRC-7 . 14
6.2.6 R-FUNC-RA-06 Pipelining for MDRC-2 to MDRC-7 . 14
6.3 Radio Application functional block requirements . 15
6.3.1 R-FUNC-FB-01 Implementation for MDRC-2 to MDRC-7 . 15
6.3.2 R-FUNC-FB-02 Execution for MDRC-2 to MDRC-7 . 15
6.3.3 R-FUNC-FB-03 Side Effects for MDRC-2 to MDRC-7 . 15
6.3.4 R-FUNC-FB-04 Shared Data for MDRC-2 to MDRC-7 . 15
6.3.5 R-FUNC-FB-05 Concurrency for MDRC-2 to MDRC-7 . 15
6.3.6 R-FUNC-FB-06 Extendability for MDRC-2 to MDRC-7 . 15
6.4 Mobile device reconfiguration requirements . 16
6.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 . 16
6.4.2 R-FUNC-MDR-02 Platform-independent Source Code or IR for MDRC-5, MDRC-6 or MDRC-7 . 16
6.4.3 R-FUNC-MDR-03 Radio Configuration of Platform MDRC-1 to MDRC-7 . 16
6.4.4 R-FUNC-MDR-04 Radio Programming for MDRC-1 to MDRC-7 . 16
6.4.5 R-FUNC-MDR-05 Dynamic Execution for MDRC-4, and MDRC-7 . 17
6.4.6 R-FUNC-MDR-06 Independency on Memory Model for MDRC-1 to MDRC-7 . 17
6.4.7 R-FUNC-MDR-07 Code for MDRC-2 to MDRC-7 . 17
6.4.8 R-FUNC-MDR-08 IR Format for MDRC-5 to MDRC-7 . 17
6.4.9 R-FUNC-MDR-09 Timing Constraints for MDRC-1 to MDRC-7 . 17
6.4.10 R-FUNC-MDR-10 Platform Independency for MDRC-5 to MDRC-7 . 17
6.4.11 R-FUNC-MDR-11 Radio Application for MDRC-5 to MDRC-7 . 17
ETSI
---------------------- Page: 3 ----------------------
4 Draft ETSI EN 302 969 V1.2.10 (2018-02)
6.4.12 R-FUNC-MDR-12 Function Granularity for MDRC-1 to MDRC-7 . 17
6.4.13 R-FUNC-MDR-13 Radio Virtual Machine for MDRC-2 to MDRC-7 . 17
6.4.14 R-FUNC-MDR-14 RadioVirtual Machine Structure for MDRC-2 to MDRC-7 . 18
6.4.15 R-FUNC-MDR-15 Selection of Radio Virtual Machine Protection Class for MDRC-2 to MDRC-7 . 18
6.5 Radio Frequency(RF) transceiver requirements . 19
6.5.0 General . 19
6.5.1 R-FUNC-RFT-01 RF Configuration for MDRC-1 to MDRC-7 . 19
6.5.2 R-FUNC-RFT-02 Extendibility for multiple-antenna system for MDRC-1 to MDRC-7 . 19
6.5.3 R-FUNC-RFT-03 Capability of multiple frequency bands for MDRC-1 to MDRC-7 . 20
6.5.4 R-FUNC-RFT-04 Reconfigurability of RF Transceiver for MDRC-1 to MDRC-7 . 20
6.5.5 R-FUNC-RFT-05 Interoperability of radio resources for MDRC-2 to MDRC-7 . 20
6.5.6 R-FUNC-RFT-06 Testability of radio equipment for MDRC-1 to MDRC-7 . 20
6.5.7 R-FUNC-RFT-07 Unified representation of control information for MDRC-1 to MDRC-7 . 20
6.5.8 R-FUNC-RFT-08 Unified representation of data payload for MDRC-1 to MDRC-7 . 20
6.5.9 R-FUNC-RFT-09 Selection of RF Protection Class for MDRC-1 to MDRC-7 . 20
6.6 Security requirements . 21
6.6.0 General . 21
6.6.1 R-FUNC-SEC-01 REConfPol-RAP-Security . 21
6.6.2 R-FUNC-SEC-02 Administration-Security . 21
6.6.3 R-FUNC-SEC-03 Secure Management . 21
6.6.4 R-FUNC-SEC-04 Root of Trust . 21
History . 22
ETSI
---------------------- Page: 4 ----------------------
5 Draft ETSI EN 302 969 V1.2.10 (2018-02)
Intellectual Property Rights
Essential patents
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
server (https://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.
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.
Foreword
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
Procedure.
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
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: 5 ----------------------
6 Draft ETSI EN 302 969 V1.2.10 (2018-02)
1 Scope
The scope of the present document is to define the high level system requirements for reconfigurable Mobile Devices
enabling the provision of Radio Applications. The work will be based on the Use Cases defined in ETSI
TR 103 062 [i.1] and ETSI TR 102 944 [i.2].
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.
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
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 TR 103 062: "Reconfigurable Radio Systems (RRS); Use Cases and Scenarios for Software
Defined Radio (SDR) Reference Architecture for Mobile Device".
[i.2] ETSI TR 102 944: "Reconfigurable Radio Systems (RRS); Use Cases for Baseband Interfaces for
Unified Radio Applications of Mobile Device".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Functional Block (FB): function needed for real-time implementation of Radio Application(s)
NOTE 1: A functional block includes not only the modem functions in Layer1 (L1), Layer2 (L2), and Layer 3 (L3)
but also all the control functions that should be processed in real-time for implementing given Radio
Application(s).
ETSI
---------------------- Page: 6 ----------------------
7 Draft ETSI EN 302 969 V1.2.10 (2018-02)
NOTE 2: Functional blocks are categorized into standard functional blocks and user defined functional blocks. In
more details:
1) Standard functional blocks can be shared by many Radio Applications. For example, Forward Error
Correction (FEC), Fast Fourier Transform (FFT)/Inverse Fast Fourier Transform (IFFT),
(de)interleaver, Turbo coding, Viterbi coding, Multiple Input Multiple Output (MIMO),
Beamforming, etc. are the typical category of standard functional block.
2) User defined functional blocks include those functional blocks that are dependent upon a specific
Radio Application. They are used to support special function(s) required in a specific Radio
Application or to support a special algorithm used for performance improvement. In addition, a
user defined functional block can be used as a baseband controller functional block which controls
the functional blocks operating in baseband processor in real-time and to control some context
information processed in real-time.
NOTE 3: Each functional block has its unique name, Input, Output and properties.
network coding: technique in which transmitted data is encoded and decoded to improve network performance
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: Radio applications 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;
Intermediate Representations (IRs) including radio library calls of radio library native
implementation and radio HAL calls;
Executable codes for a particular radio platform.
radio library: library of Standard Functional Blocks (SFB) that is provided by a platform vendor in a form of platform-
specific executable code
NOTE 1: SFBs implement reference codes of functions which are typical for radio signal processing. They are not
atomic and their source codes are typed and visible for Radio Application developers.
NOTE 2: An SFB is implemented through a Radio Hardware Abstraction Layer (HAL) when the SFB is
implemented on dedicated HW accelerators. Radio HAL is part of ROS.
Radio Virtual Machine (RVM): abstract machine supporting reactive and concurrent executions
NOTE: A Radio Virtual Machine 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.
reconfigurable mobile device: mobile device with radio communication capabilities providing support for radio
reconfiguration
NOTE: Reconfigurable mobile devices include but are not limited to: smartphones, feature phones, tablets,
laptops.
resources: hardware resources that a Radio Application needs in active state
NOTE 1: Resources are provided by the reconfigurable Mobile Device (MD), to be used by the Radio Applications
when they are active. Radio Applications provide their resource needs (e.g. using operational states) so
that the multiradio computer may judge whether these resources are available, in order to ensure non-
conflicting operation with other Radio Applications. Resources may or may not be shared in the
reconfigurable MD.
NOTE 2: Resources may include processors, accelerators, memory, Radio Frequency circuitry, etc.
ETSI
---------------------- Page: 7 ----------------------
8 Draft ETSI EN 302 969 V1.2.10 (2018-02)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASIC Application Specific Integrated Circuit
BER Bit Error Rate
CAT CATegory
CR Cognitive Radio
DoA Direction of Arrival
FB Functional Block
FEC Forward Error Correction
FFT Fast Fourier Transform
HAL Hardware Abstraction Layer
IR Intermediate Representation
LTE Long Term Evolution
MAC Media Access Control
MD Mobile Device
MDRC Mobile Device Reconfiguration Class
MIMO Multi-Input Multi-Output
MU-MIMO Multi User- Multi-Input Multi-Output
PER Packet Error Rate
PMI Precoding Matrix Indicator
RA Radio Application
RAT Radio Access Technology
RF Radio Frequency
RI Rank Indicator
ROS Radio Operating System
RRS Reconfigurable Radio Systems
RSSI Received Signal Strength Indication
RVM Radio Virtual Machine
Rx Receive
SDR Software Defined Radio
SFB Standard Functional Block
SINR Signal to Interference-plus-Noise Ratio
SU-MIMO Single User- Multi-Input Multi-Output
Tx Transmit
UDFB User Defined Functional Block
WiFi Wireless Fidelity
4 Requirement organization and methodology
4.0 General
This clause is containing the description of how the requirements are organized and the related format.
4.1 Requirement organization
As shown in Figure 1, all requirements described in the present document belong to one single category (the functional
requirements category). Requirements are, in turn, organized into groups.
ETSI
---------------------- Page: 8 ----------------------
9 Draft ETSI EN 302 969 V1.2.10 (2018-02)
Figure 1: Overall requirements structure
4.2 Requirement format
A letter code system is defined which makes a unique identification of each requirement R---.
Each requirement is constructed as follows:
• R-: Standard requirement prefix
•
Code Category
FUNC Functional aspects
• : Requirement group identifier. A letter code will be used for this identifier. The three first letters
will give the identifier of the group.
• : Requirement identifier within requirement group; range 01 => 99.
EXAMPLE: R-FUNC-QOS-01.
ETSI
---------------------- Page: 9 ----------------------
10 Draft ETSI EN 302 969 V1.2.10 (2018-02)
4.3 Requirement formulation
A requirement is formulated in such a way that it is uniquely defined. It is built as follows:
Title: </br>
• Description: the description of a requirement will be formulated using one of the following terms:</br>
- "shall" is used to express mandatory requirements (i.e. provisions that have to be followed)</br>
- "should" is used to express recommendations (provisions that an implementation is expected to follow</br>
unless there is a strong reason for not doing so)</br>
- "May" is used to express permissible actions (provisions that an implementation is able to follow or not</br>
follow)</br>
5 Working assumptions</br>
5.1 Assumptions</br>
5.1.1 Mobile device reconfiguration classes</br>
As it is expected that the reconfiguration capabilities of a Mobile Device will evolve over time, Mobile Device</br>
Reconfiguration Classes (MDRC) are introduced. As shown in Figure 2, 7 different classes of reconfigurable MD are</br>
introduced (MDRC-0 corresponds to a non-reconfigurable device).</br>
</br>
Figure 2: Definition of MDRCs according to reconfiguration capabilities</br>
A reconfigurable MD belongs to a defined class according to the reconfiguration capabilities, which are determined by</br>
the type of Resource requirements and the form of the Radio Application Package. Reconfigurable MD classes are</br>
defined as follows (see also Figure 2):</br>
1) MDRC-0: No MD reconfiguration is possible</br>
MDRC-0 represents legacy radio implementations and do not allow for MD reconfiguration (except for bug</br>
fixing and release-updates through firmware updates) or exploitation of Cognitive Radio (CR) features.</br>
MDRC-0 represents legacy radio implementations and does not allow for MD reconfiguration.</br>
ETSI</br>
</br>
---------------------- Page: 10 ----------------------</br>
11 Draft ETSI EN 302 969 V1.2.10 (2018-02)</br>
2) MDRC-1: Radio Applications use different fixed Resources</br>
In this scenario, at least some of the radios are implemented with non-software defined radio (SDR)</br>
technology, e.g. with dedicated Application Specific Integrated Circuits (ASICs), and are Resource-wise</br>
independent of each other. Simple CR functionality may be supported through radio parameter management to</br>
the extent which the radio implementations allow.</br>
MDRC-1 implements multiple Radio Applications with fixed Resources allocation and no Resource sharing.</br>
The rule for Resource allocation for multiple applications {A , A , …, A } can be formulated as follows:</br>
1 2 N</br>
A → R , ∀i∈{1, ., N}, where R denotes Resources allocated for application A and R ∩ R = ∅ for ∀i ≠ j.</br>
i i i i i j</br>
Note that applications can be run concurrently in any combination; a Resource allocation mechanism within</br>
separate applications is not specified.</br>
3) MDRC-2: Radio Applications use pre-defined static Resources</br>
MDRC-2 implements multiple Radio Applications but no dynamic Resource management is available. The</br>
Radio Applications for MDRC-2 come from a single Radio Application Package which is normally provided</br>
by a reconfigurable MD vendor or SDR chipset manufacturer. In this scenario, it is assumed that software</br>
radio components in the Radio Application Package are provided in platform-specific executable code.</br>
The rule for the Resource allocation related to multiple applications {A , A , …, A } can be formulated as</br>
1 2 N</br>
follows: A →R , ∀i∈{1, ., N}, where R denotes Resources allocated for application A , if ∃ i ≠ j so that</br>
i i i i</br>
R ∩ R ≠ ∅ then such applications cannot be run concurrently, all other combinations are allowed; a Resource</br>
i j</br>
allocation mechanism within separate applications is not specified.</br>
4) MDRC-3: Radio Applications have static Resource requirements</br>
For MDRC-3, a Resource budget is defined for each Radio Application. This budget contains a static Resource</br>
measure that represents the worst-case Resource usage of the application, generated at Radio Application</br>
compile-time. If an application is being started, the Resource manager installed in a reconfigurable MD of</br>
MDRC-3 checks its Resource budget and the sum of all Resource budgets of already running applications, and</br>
admits the new application only if the Resources can still be guaranteed for all running applications. In this</br>
scenario, it is assumed that software radio components in the Radio Application Package are provided in</br>
platform-specific executable code.</br>
The rule for Resource allocation for multiple applications {A , A , …, A } can be formulated as follows:</br>
1 2 N</br>
A → R(A ), where R denotes total Resources to be shared and R(A ) denotes a part of R allocated for A ; if for</br>
i i i i</br>
i1, i2, ., iM ∈{1, ., N}, M ≤ N, R(A ) ∪ R(A ) ∪ . ∪ R(A ) ⊂ R then applications A , A , …, A can be</br>
i1 i2 iM i1 i2 iM</br>
run concurrently; a Resource allocation mechanism within separate applications is not specified.</br>
5) MDRC-4: Radio Applications have dynamic Resource requirements</br>
This scenario assumes a similar Resource manager in a reconfigurable MD as for MDRC-3, but in addition the</br>
Radio Applications have now varying Resource demands based on their current type of activity. Applications</br>
have separate operational states for different types of activity, and a Resource budget is assigned to each</br>
operational state. In this scenario, it is assumed that software radio components in the Radio Application</br>
Package are provided in platform-specific executable code.</br>
Resource management for MDRC-4 can be formulated as follows. Multiple applications {A , A , …, A } can</br>
1 2 N</br>
be run and each application A is divided into tasks {t (A ), t (A ), ., t (A )}. Resource allocation is provided</br>
i 1 i 2 i k i</br>
by the Resource manager in a reconfigurable MD for each task t (A ) → R(t (A )).</br>
j i j i</br>
The rule for task running is exactly the same as for MDRC-3 except that each application should be replaced</br>
by a corresponding task. Therefore, if for i1, i2, ., iM ∈{1, ., N}, M ≤ N, R(t (A )) ∪ R(t (A )) ∪ . ∪</br>
j1 i1 j2 i2</br>
R(t (A )) ⊂ R then tasks t (A ), t (A ), ., t (A ) can be run concurrently; a Resource allocation</br>
jL iM j1 i1</br>
<b>...</b>
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.