ETSI EN 303 145 V1.2.1 (2015-11)
Reconfigurable Radio Systems (RRS); System Architecture and High Level Procedures for Coordinated and Uncoordinated Use of TV White Spaces
Reconfigurable Radio Systems (RRS); System Architecture and High Level Procedures for Coordinated and Uncoordinated Use of TV White Spaces
REN/RRS-0144
Radijski sistemi z možnostjo preoblikovanja (RRS) - Arhitektura sistema in vrhunski postopki za usklajeno in neusklajeno uporabo belih lis TV
Ta dokument določa arhitekturo sistema za uporabo spektra s strani naprav za kanalske presledke (WSD), zlasti v pasovih UHF TV. Arhitektura izhaja iz dokumenta ETSI TS 102 946 [1]. Obseg tega dokumenta določa arhitekturo sistema, ki omogoča delovanje naprav za kanalske presledke (WSD), ki temeljijo na informacijah, pridobljenih iz geolokacijskih podatkovnih baz. Arhitektura upošteva tako neusklajeno uporabo kanalskih presledkov (kjer ne obstaja poskus upravljanja uporabe kanalov z različnimi napravami za kanalske presledke (WSD)) kot tudi usklajeno uporabo kanalskih presledkov (kjer se za učinkovito uporabo kanalskih presledkov uporablja določena oblika upravljanja kanalov in/ali soobstoječe tehnike).
General Information
Standards Content (Sample)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
System Architecture and High Level Procedures for
Coordinated and Uncoordinated Use of TV White Spaces
2 ETSI EN 303 145 V1.2.1 (2015-11)
Reference
REN/RRS-0144
Keywords
architecture, GLDB, system, white space
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI EN 303 145 V1.2.1 (2015-11)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Functional Architecture . 9
4.1 Overview of Functional Architecture . 9
4.2 Coordinated Usage of White Spaces . 10
4.2.1 Spectrum coordination . 10
4.2.1.1 Overview . 10
4.2.1.2 Information service . 10
4.2.1.3 Management service. 10
4.2.2 High level operation sequence . 10
4.3 Uncoordinated Usage of White Spaces . 11
4.3.1 High level operation sequence . 11
5 Detailed Functional Architecture . 11
5.1 Architecture Description . 11
5.2 Functional Description of Components . 12
5.2.1 Database function . 12
5.2.2 Geo-location function . 12
5.2.3 Spectrum coordination function . 13
5.2.4 Control function . 14
5.2.5 Communication function . 14
5.2.6 Interface function . 14
5.3 Reference Points . 15
5.3.1 Reference point A: Between a GLDB and a CRS . 15
5.3.2 Reference point B: Between a CRS and a SC . 16
5.3.3 Reference point C: Between SCs . 16
5.3.4 Reference point D: Between a SC and a GLDB . 17
5.4 Potential Interaction of Functionality within the spectrum coordination function . 18
6 High Level Procedures . 19
6.1 Procedures for Coordinated Access of White Spaces . 19
6.1.1 Initialization procedures . 19
6.1.2 Coordination service subscription procedures . 19
6.1.2.1 Overview . 19
6.1.2.2 CRS subscription procedure . 19
6.1.2.3 CRS subscription update procedure . 20
6.1.2.4 CRS subscription change procedure . 21
6.1.3 Registration and authentication procedures . 21
6.1.3.1 Overview . 21
6.1.3.2 CRS registration procedure . 22
6.1.3.3 CRS registration update procedure . 22
6.1.3.4 Procedure for CRS deregistration from SC . 23
6.1.3.5 SC authentication and registration procedure . 23
6.1.3.6 SC de-authentication and de-registration procedure . 24
6.1.4 Channel Access Procedures . 25
6.1.4.1 Requesting CRS channel access procedure . 25
6.1.4.2 Requesting SC channel access procedure . 25
6.1.4.3 Providing available channel list procedure . 26
ETSI
4 ETSI EN 303 145 V1.2.1 (2015-11)
6.1.4.4 Procedure of channel usage notification for subject CRS . 27
6.1.4.5 Procedure for GLDB to SC Notification for CRS operational parameters update . 27
6.1.4.6 CRS's operational parameters update request procedure from SC for incumbent protection . 28
6.1.4.7 Basic Channel Access Sequence . 30
6.1.4.8 Channel Access Sequence for Priority-Based Channel Assignment . 31
6.1.5 Information exchange procedures . 32
6.1.5.1 Providing coordination report procedure . 32
6.1.6 Sensing and Measurement Procedures and Operation Sequences . 33
6.1.6.1 Overview . 33
6.1.6.2 Requesting measurements procedure . 33
6.1.6.3 Providing periodic measurements procedure . 33
6.1.6.4 Providing single measurements procedure . 34
6.1.6.5 Non-Periodic measurements sequence . 35
6.1.6.6 Event-Triggered Measurement Sequence . 35
6.1.7 Reconfiguration Procedures and Operation Sequences . 37
6.1.7.1 Reconfiguration request from SC to CRS procedure . 37
6.1.7.2 Reconfiguration request from SC to GLDB procedure . 38
6.1.7.3 General reconfiguration sequence between coordinated CRSs . 38
6.1.7.4 CRS Request-Triggered Operational Parameter Reconfiguration . 40
6.1.7.5 CRS-Measurement Triggered Priority-Based Operational Parameter Reconfiguration . 43
6.1.7.6 General Priority-Based Channel Reconfiguration Sequence . 45
6.1.7.7 Management of uncoordinated CRSs considering priority usage of coordinated CRSs . 46
6.1.7.8 Priority Usage Request Considering Uncoordinated Channel Usage . 47
6.1.7.8.1 Overview . 47
6.1.7.8.2 Implementation Option A . 47
6.1.7.8.3 Implementation Option B . 49
6.1.7.9 Uncoordinated CRS Request Considering Priority Usage Coordinated CRS . 53
6.1.7.9.1 Overview . 53
6.1.7.9.2 Implementation Option A . 54
6.1.7.9.3 Implementation Option B . 54
6.1.7.10 Device parameter reconfiguration request from SC to CRS procedure. 56
6.1.7.11 General sequence of device parameter reconfiguration request from SC to CRS for facilitating
coexistence among CRSs . 57
6.1.8 Inter-SC procedures . 58
6.1.8.1 Reconfiguration request from master SC to CRS registered to slave SC procedure . 58
6.1.8.2 Master/slave SC configuration procedure . 59
6.1.8.3 Obtaining coordination set information from other SCs procedure . 60
6.1.8.4 Procedures for interfering SCs discovery . 61
6.1.8.4.1 Overview . 61
6.1.8.4.2 GLDB-aided potential interfering SCs discovery procedure . 61
6.1.8.4.3 Interfering SCs discovery procedure . 62
6.1.8.5 Negotiation between SCs procedure . 63
6.1.8.6 Operational Sequences for negotiation-based configuration of SCs . 64
6.2 Procedures for Uncoordinated Access of White Spaces . 65
7 Potential Implementation Architectures . 65
7.1 High level flow chart of entities . 65
7.1.1 CRS operation . 65
7.1.1.1 General description . 65
7.1.2 SC operation . 69
7.1.2.1 General description . 69
7.1.3 GLDB operation . 74
7.1.3.1 General description . 74
Annex A (informative): High Level Spectrum Management Algorithms for White Spaces . 77
A.1 Coexistence decision algorithms . 77
A.1.1 Algorithm based on co-channel sharing via CRS network geometry classification . 77
A.1.1.1 Introduction. 77
A.1.1.2 Network geometry classification . 77
A.1.1.3 Algorithm description . 81
A.1.2 Control of spectrum utilization based on the number of CRSs . 82
A.1.2.1 Introduction. 82
ETSI
5 ETSI EN 303 145 V1.2.1 (2015-11)
A.1.2.2 Flowchart of the algorithm . 83
A.1.3 Control of coordinated CRSs for reduced transmit power fluctuation . 85
A.1.3.1 Introduction. 85
A.1.3.2 Flowchart of the algorithm . 85
A.1.4 Spectrum rearrangement among CRSs . 86
A.1.4.1 Introduction. 86
A.1.4.2 Flowchart of the algorithm . 87
A.1.5 Resource allocation based on channel ranking . 88
A.1.5.1 Introduction. 88
A.1.5.2 Flowchart of the algorithm . 89
A.2 Priority access management algorithms . 90
A.2.1 Control of non-priority access CRSs for CRS with priority access . 90
A.2.1.1 Introduction. 90
A.2.1.2 Flowchart of the algorithm . 91
Annex B (informative): Possible Physical implementation examples of logical functions in
coordinated usage of white spaces . 92
B.1 Possible Physical implementation examples . 92
B.1.1 Third party database management . 92
B.1.2 GLDB with spectrum coordination function . 92
B.1.3 CRS with spectrum coordination function . 93
B.1.4 Spectrum coordination for Multi-operators . 94
History . 95
ETSI
6 ETSI EN 303 145 V1.2.1 (2015-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
National transposition dates
Date of adoption of this EN: 6 November 2015
Date of latest announcement of this EN (doa): 29 February 2016
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 August 2016
Date of withdrawal of any conflicting National Standard (dow): 31 August 2016
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
7 ETSI EN 303 145 V1.2.1 (2015-11)
1 Scope
The present document defines the system architecture for the use of spectrum by White Space Devices (WSDs),
specifically in the UHF TV Bands. The architecture stems from ETSI TS 102 946 [1]. The scope of the present
document is to define the architecture of a system which can allow operation of WSDs based on information obtained
from Geo-location databases. The architecture will consider both uncoordinated use of White Space (where there is no
attempt to manage the usage of channels by different WSDs) as well as coordinated use of White Space (where some
form of channel management and/or coexistence techniques are employed to efficiently use the White Space).
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 102 946: "Reconfigurable Radio Systems (RRS); System requirements for Operation in
UHF TV Band White Spaces".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 067: "Reconfigurable Radio Systems (RRS); Feasibility study on Radio Frequency
(RF) performance for Cognitive Radio Systems operating in UHF TV band White Spaces".
[i.2] ECC Report 186: "Technical and operational requirements for the operation of white space devices
under geo-location approach".
™
[i.3] IEEE 802.22: "Cognitive Radio Wireless Regional Area Networks (WRAN) Medium Access
Control (MAC) and Physical Layer (PHY) Specifications: Policies and Procedures for Operation
in the Bands that Allow Spectrum Sharing where the Communications Devices may
Opportunistically Operate in the Spectrum of the Primary Service".
™
[i.4] IEEE 802.11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[i.5] ETSI EN 301 598 (V1.1.1): "White Space Devices (WSD);Wireless Access Systems operating in
the 470 MHz to 790 MHz TV broadcast band; Harmonized EN covering the essential requirements
of article 3.2 of the R&TTE Directive".
ETSI
8 ETSI EN 303 145 V1.2.1 (2015-11)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
coexistence: situation in which one radio system operates in an environment where another radio system having
potentially different characteristics (e.g. RAT) may be using the same or different channels, and both radio systems are
able to operate with some tolerable impact to each other
coordinated use of white spaces: case when each CRS uses available white space resources obtained with the help of
the geo-location database and with additional knowledge of spectrum usage by its neighbour CRSs by the SC
NOTE: The case in which the SC assigns directly channels to the CRSs is also part of the coordinated use of
white spaces.
coordination: ability of managing two or more CRSs to allow them to follow pre-determined operation policies such as
coexistence among coordinated CRSs
coordination report: information to the CRS to make coordination decisions on its operational parameters in the
information service
NOTE: This includes channel usage information, output power level, channel availability time, sensing
information, as well as some initial ranking of the available channels.
coordination set: set of CRSs which may affect the performance of the CRS they are associated to
Geo-Location Database (GLDB): database approved by the relevant national regulatory authority which can
communicate with WSDs and provide information on TVWS channel availability
NOTE 1: Information provided by a GLDB will include the available frequencies and associated maximum EIRP
values that the WSD is permitted to use which allow for protection of the incumbent service and are
derived from information provided by the WSD and the minimum required ACLR of the WSD.
NOTE 2: The GLDB consists of database and geo-location functions.
priority-based channel assignment: assignment of a channel by the SC to a CRS in such a way that the CRS can
operate alone in such channel for a specific reservation period and in a specific area based on particular minimum
protection requirements of the CRS
NOTE: CRSs assigned such channels with therefore have priority over other CRSs.
Spectrum Coordinator (SC): entity that coordinates spectrum usage of CRS based on the information obtained from
geo-location database as well as supplemental spectrum usage data from different CRSs using its service
uncoordinated use of white spaces: case when each CRS independently uses available white space resources obtained
with the help of the geo-location database without any help from the spectrum coordination function to coordinate
spectrum usage with its neighbour CRSs
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACLR Adjacent Channel Leakage Ratio
BC Branch Condition
Com-SAP Communication Service Access Point
CR Cognitive Radio
CRS Cogitative Radio System
C-SAP Control Service Access Point
CSMA Carrier Sense Multiple Access
DB-SAP DataBase-Service Access Point
DS Decision Status
DTV Digital TV
ETSI
9 ETSI EN 303 145 V1.2.1 (2015-11)
EIRP Effective Isotropic Radiated Power
GLDB Geo-Location Database
GL-SAP GeoLocation-Service Access Point
NAV Network Allocation Vector
NRA National Regulatory Authority
QoS Quality of Service
RAT Radio Access Technology
SAP Service Access Point
SC Spectrum Coordinator
SC-SAP Spectrum Coordinator Service Access Point
SINR Signal to Interference plus Noise Ratio
TV TeleVision
TVWS TV White Space
UHF Ultra High Frequency
WSD White Space Device
4 Functional Architecture
4.1 Overview of Functional Architecture
Figure 4.1 shows the high level functional architecture of a white space system. All the system requirements specified
in ETSI TS 102 946 [1] shall be supported.
Figure 4.1: Overview of TV white spaces system
The TV white space system has three entities:
• Cognitive Radio System (CRS);
• Spectrum Coordinator (SC);
• Geolocation Database (GLDB);
and four reference points (A, B, C, and D), as shown in figure 4.1.
Each entity is defined by its functional roles and reference points with other entities.
The cognitive radio system (CRS) represents a white spaces device (WSD) or network of WSDs (i.e. a master WSD and
some slave WSDs). The CRS uses available white space resources obtained with the help of geo-location database
(GLDB) and/or with additional knowledge of spectrum usage by its neighbour CRSs provided by the spectrum
coordinator (SC).
The GLDB provides a WSD in a CRS with location specific information on the available frequencies and associated
maximum EIRP values that the WSD is permitted to use. This will allow for protection of the incumbent service and is
derived from information provided by the WSD and the minimum required Adjacent Channel Leakage Ratio (ACLR)
of the WSD itself.
ETSI
10 ETSI EN 303 145 V1.2.1 (2015-11)
The SC is responsible for coordinating spectrum usage of CRSs based on the information obtained from GLDB as well
as additional spectrum usage data from different CRSs using its service. Different SCs are capable of communicating
with each other.
The reference point A that is related to the uncoordinated usage of White Spaces is described in ETSI EN 301 598 [i.5].
4.2 Coordinated Usage of White Spaces
4.2.1 Spectrum coordination
4.2.1.1 Overview
Spectrum coordination is the mechanism with which an SC serves CRSs so that they can operate efficiently in available
spectrum resources of white spaces. The SC coordinates how to manage radio resources among a set of CRSs that are
potentially interfering with each other (coexistence) and allows for channel assignment requested by a CRS that wishes
to operate alone on a channel and with priority over other CRSs (priority-based channel assignment). The priority-based
channel assignment is managed by the SC based on some minimum protection requirements requested by the CRS,
which includes minimum bandwidth, minimum SINR (or maximum allowable interference) and some guaranteed
minimum availability time. The SC translates these requirements into protection criteria, which are used by the GLDB
to ensure that the priority-based channel assignment is maintained in the presence of other WSDs not using the SC. The
algorithms to enable coexistence and/or priority-based channel assignment are described in Annex A. From the
perspective of the CRSs, coexistence and priority-based channel assignment are provided as a set of two available SC
services: the information service (for coexistence only) and the management service (for both coexistence and
priority-based channel assignment). Each SC shall provide at least the information service or the management service
for CRSs but can also provide both of them. The information service and the management service are described in
clauses 4.2.1.2 and 4.2.1.3.
4.2.1.2 Information service
For CRSs that are subscribed to the information service, an SC provides information about useful operational
parameters (e.g. the operational parameters of other CRS in the available spectrum resources). In the information
service, an SC does not make decision on the operational parameters to be used by those CRSs, but rather, all decisions
are made by the CRS itself. However, the SC may process information about the current usage of spectrum to provide
to the CRS in a manner which may facilitate the CRS decision (such as ranking the potential operational parameters
according to the resulting expected performance).
4.2.1.3 Management service
For CRSs that are subscribed to the management service, a SC provides the operational parameters to be used by a CRS
based on its requests and, potentially, certain QoS and usage time requirements. A CRS does not make any decision for
its operational parameters (e.g. channel and transmit power) but they are determined by the SC itself.
4.2.2 High level operation sequence
An overview of coordinated usage of white spaces is shown in figure 4.2.
Figure 4.2: Overview of coordinated usage of white spaces system
ETSI
11 ETSI EN 303 145 V1.2.1 (2015-11)
A CRS consists of a master WSD and one or more slave WSDs. The master WSD sends device parameters to a GLDB
via the SC. The SC shall act as relay and can also store the device parameters of the master WSD. The SC, during the
process, maintains additional data about spectrum usage of the different CRSs using its service. This additional data
contains information that reflects the current state of spectrum usage, including spectrum measurement data from
WSDs, and usage maps or areas of occupancy of the different CRSs. It also contains parameters specific to the Radio
Access Technology of each CRS that facilitates coexistence. A GLDB shall receive information from the master WSD
about the characteristics of that WSD in order to generate operational parameters for that WSD. The GLDB provides
specific operational parameters to the master WSD via the SC. During this process, the SC determines the operational
parameters using the information obtained from the GLDB as well as the additional data about spectrum usage of the
different CRSs, and sends these operational parameters to the master WSD in response to the request for white space
access. The operational parameters determined by the SC shall not violate the protection criteria of the incumbent, and
are therefore compliant with the information obtained from the GLDB. The master WSD then sends the selected
channel usage parameter to the GLDB via the SC [i.2]. The SC will also update its additional spectrum usage data based
on information sent by the WSD. At any time in the process of assigning channels to the CRSs, the SC could
reconfigure the channel usage of the CRSs to ensure an efficient use of spectrum, such as reducing fragmentation in the
available spectrum. The GLDB can use channel usage parameters sent by the SC to ensure that WSDs can operate in the
presence of other WSDs not using the SC.
4.3 Uncoordinated Usage of White Spaces
4.3.1 High level operation sequence
An overview of uncoordinated usage of white spaces is shown in figure 4.3.
Figure 4.3: Overview of uncoordinated usage of white spaces system
A CRS consists of a master WSD and one or more slave WSDs. The master WSD shall communicate with a GLDB to
obtain its operational parameters in white spaces. A GLDB shall receive information from a WSD about the
characteristics of that WSD in order to generate operational parameter for that WSD. A GLDB shall maintain a record
of the actual usage of the white spaces. This information could be used to enable WSDs to be readily identified if
interference to incumbent users were to occur, and to allow the GLDB to know the extent to which available white
spaces are being used.
5 Detailed Functional Architecture
5.1 Architecture Description
The overall system reference model is shown in figure 5.1.
ETSI
12 ETSI EN 303 145 V1.2.1 (2015-11)
Figure 5.1: Overall system reference model
There are six logical functions for operating white space system: control function, spectrum coordination function,
database function and geo-location function are the 4 key components for the system. Two additional functions (the
interface function and the communication function) are general components for the system. Physical implementation
examples of the overall system reference model are shown in annex B. Clause 5.2 describes in more detail the six
identified logical functions.
5.2 Functional Description of Components
5.2.1 Database function
A database function is a software/hardware module that stores necessary information provided by regulators for
calculating the available spectrum that a WSD in a CRS can operate on (with protection to incumbent services) as well
as registration of the WSDs under regulatory requirements and for the purposes of protecting incumbent services. The
reference model of database function is shown in figure 5.2.
Figure 5.2: Reference model of a database function
The database function service access point (SAP) is the database SAP (DB-SAP). The DB-SAP is used by the interface
function to access the services provided by the database function such as registration of CRS and provision of
incumbent information.
5.2.2 Geo-location function
A geo-location function is a software/hardware module that supports the following functions:
• To calculate location specific available frequency band and associated maximum EIRP that a WSD in a CRS
can use based on the information on incumbents stored in database function.
• To Interact with the SC for management of uncoordinated CRSs when considering priority usage coordinated
CRSs.
ETSI
13 ETSI EN 303 145 V1.2.1 (2015-11)
The reference model of the geo-location function is shown in figure 5.3.
Figure 5.3: Reference model of a geo-location function
The geo-location function service access point (SAP) is the geo-location SAP (GL-SAP). GL-SAP is used by the
interface function to access the services provided by the geo-location function such as calculation of location specific
EIRP of a frequency band and that a WSD in a CRS can use.
5.2.3 Spectrum coordination function
A spectrum coordination function is a software/hardware module that coordinates spectrum usage of CRSs based on the
information obtained from geo-location database and additional data about the spectrum usage of the different CRSs
using the services of the SC. The reference model of spectrum coordination function is shown in figure 5.4. Depending
on the implementation and location of the spectrum coordination function in the system (see annex B for examples) the
spectrum coordination function will have one or more of the following functionalities:
Coexistence functionality: This functionality assures proper operation between different WSDs that utilize the white
space, and avoidance of harmful interference between different CRSs using the same and/or adjacent channels.
Sensing and measurement functionality: The sensing functionality is responsible for the configuration of sensing in
the CRS as well as the collection and combined processing of the sensing results and the measurements specific of the
RAT that the CRS is using.
Priority-Based Channel assignment and negotiation functionality: This functionality allows certain CRSs or other
spectrum coordination functions to assign channels and provides the necessary means for negotiation between different
CRSs which may request a priority-based channel assignment for periods of time.
Figure 5.4: Reference model of spectrum coordination function
The spectrum coordination function service access point is the spectrum coordination SAP (SC-SAP). The coexistence
functionality, sensing functionality, and priority usage and negotiation functionality all communicate with functions
outside of the spectrum coordination function using the same SC-SAP. SC-SAP is used by the interface function to
access the services provided by the spectrum function such as calculation of coordination parameters based on
coexistence algorithms, priority-based channel assignment algorithms, etc. that a WSD in a CRS can use.
ETSI
14 ETSI EN 303 145 V1.2.1 (2015-11)
5.2.4 Control function
A control function is a hardware/software module that controls operation of a CRS in white space such as sending
device parameters to GLDB/SC, receiving operational parameters from GLDB/SC, sending operational parameters
and/or channel assignment to CRSs, sending channel usage parameters to GLDB/SC, sending requests to SC, and
receiving responses from SC. The reference model of the control function is shown in figure 5.5.
Figure 5.5: Reference model of spectrum coordination function
The control function service access point is the control SAP (C-SAP). C-SAP is used by applications to access
information and parameters of GLDB and/or SC. It defines a set of generic primitives and data structures to control the
CRSs and/or to obtain the information and parameters of GLDB and/or SC for application purposes. A CRS utilizing
the C-SAP takes the role of an information consumer and of control application.
5.2.5 Communication function
A communication function is a hardware/software module that provides the communications protocol stack, and other
communica
...
Draft ETSI EN 303 145 V1.1.5 (2015-07)
EUROPEAN STANDARD
Reconfigurable Radio Systems (RRS);
System Architecture and High Level Procedures for
Coordinated and Uncoordinated Use of TV White Spaces
2 Draft ETSI EN 303 145 V1.1.5 (2015-07)
Reference
REN/RRS-0144
Keywords
architecture, GLDB, system, white space
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Draft ETSI EN 303 145 V1.1.5 (2015-07)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Functional Architecture . 9
4.1 Overview of Functional Architecture . 9
4.2 Coordinated Usage of White Spaces . 10
4.2.1 Spectrum coordination . 10
4.2.1.1 Overview . 10
4.2.1.2 Information service . 10
4.2.1.3 Management service. 10
4.2.2 High level operation sequence . 10
4.3 Uncoordinated Usage of White Spaces . 11
4.3.1 High level operation sequence . 11
5 Detailed Functional Architecture . 11
5.1 Architecture Description . 11
5.2 Functional Description of Components . 12
5.2.1 Database function . 12
5.2.2 Geo-location function . 12
5.2.3 Spectrum coordination function . 13
5.2.4 Control function . 14
5.2.5 Communication function . 14
5.2.6 Interface function . 14
5.3 Reference Points . 15
5.3.1 Reference point A: Between a GLDB and a CRS . 15
5.3.2 Reference point B: Between a CRS and a SC . 16
5.3.3 Reference point C: Between SCs . 16
5.3.4 Reference point D: Between a SC and a GLDB . 17
5.4 Potential Interaction of Functionality within the spectrum coordination function . 18
6 High Level Procedures . 19
6.1 Procedures for Coordinated Access of White Spaces . 19
6.1.1 Initialization procedures . 19
6.1.2 Coordination service subscription procedures . 19
6.1.2.1 Overview . 19
6.1.2.2 CRS subscription procedure . 19
6.1.2.3 CRS subscription update procedure . 20
6.1.2.4 CRS subscription change procedure . 21
6.1.3 Registration and authentication procedures . 21
6.1.3.1 Overview . 21
6.1.3.2 CRS registration procedure . 22
6.1.3.3 CRS registration update procedure . 22
6.1.3.4 Procedure for CRS deregistration from SC . 23
6.1.3.5 SC authentication and registration procedure . 23
6.1.3.6 SC de-authentication and de-registration procedure . 24
6.1.4 Channel Access Procedures . 25
6.1.4.1 Requesting CRS channel access procedure . 25
6.1.4.2 Requesting SC channel access procedure . 25
6.1.4.3 Providing available channel list procedure . 26
ETSI
4 Draft ETSI EN 303 145 V1.1.5 (2015-07)
6.1.4.4 Procedure of channel usage notification for subject CRS . 27
6.1.4.5 Procedure for GLDB to SC Notification for CRS operational parameters update . 27
6.1.4.6 CRS's operational parameters update request procedure from SC for incumbent protection . 28
6.1.4.7 Basic Channel Access Sequence . 30
6.1.4.8 Channel Access Sequence for Priority-Based Channel Assignment . 31
6.1.5 Information exchange procedures . 32
6.1.5.1 Providing coordination report procedure . 32
6.1.6 Sensing and Measurement Procedures and Operation Sequences . 33
6.1.6.1 Overview . 33
6.1.6.2 Requesting measurements procedure . 33
6.1.6.3 Providing periodic measurements procedure . 33
6.1.6.4 Providing single measurements procedure . 34
6.1.6.5 Non-Periodic measurements sequence . 35
6.1.6.6 Event-Triggered Measurement Sequence . 35
6.1.7 Reconfiguration Procedures and Operation Sequences . 37
6.1.7.1 Reconfiguration request from SC to CRS procedure . 37
6.1.7.2 Reconfiguration request from SC to GLDB procedure . 38
6.1.7.3 General reconfiguration sequence between coordinated CRSs . 38
6.1.7.4 CRS Request-Triggered Operational Parameter Reconfiguration . 40
6.1.7.5 CRS-Measurement Triggered Priority-Based Operational Parameter Reconfiguration . 43
6.1.7.6 General Priority-Based Channel Reconfiguration Sequence . 45
6.1.7.7 Management of uncoordinated CRSs considering priority usage of coordinated CRSs . 46
6.1.7.8 Priority Usage Request Considering Uncoordinated Channel Usage . 47
6.1.7.8.1 Overview . 47
6.1.7.8.2 Implementation Option A . 47
6.1.7.8.3 Implementation Option B . 49
6.1.7.9 Uncoordinated CRS Request Considering Priority Usage Coordinated CRS . 53
6.1.7.9.1 Overview . 53
6.1.7.9.2 Implementation Option A . 54
6.1.7.9.3 Implementation Option B . 54
6.1.7.10 Device parameter reconfiguration request from SC to CRS procedure. 56
6.1.7.11 General sequence of device parameter reconfiguration request from SC to CRS for facilitating
coexistence among CRSs . 57
6.1.8 Inter-SC procedures . 58
6.1.8.1 Reconfiguration request from master SC to CRS registered to slave SC procedure . 58
6.1.8.2 Master/slave SC configuration procedure . 59
6.1.8.3 Obtaining coordination set information from other SCs procedure . 60
6.1.8.4 Procedures for interfering SCs discovery . 61
6.1.8.4.1 Overview . 61
6.1.8.4.2 GLDB-aided potential interfering SCs discovery procedure . 61
6.1.8.4.3 Interfering SCs discovery procedure . 62
6.1.8.5 Negotiation between SCs procedure . 63
6.1.8.6 Operational Sequences for negotiation-based configuration of SCs . 64
6.2 Procedures for Uncoordinated Access of White Spaces . 65
7 Potential Implementation Architectures . 65
7.1 High level flow chart of entities . 65
7.1.1 CRS operation . 65
7.1.1.1 General description . 65
7.1.2 SC operation . 69
7.1.2.1 General description . 69
7.1.3 GLDB operation . 74
7.1.3.1 General description . 74
Annex A (informative): High Level Spectrum Management Algorithms for White Spaces . 77
A.1 Coexistence decision algorithms . 77
A.1.1 Algorithm based on co-channel sharing via CRS network geometry classification . 77
A.1.1.1 Introduction. 77
A.1.1.2 Network geometry classification . 77
A.1.1.3 Algorithm description . 81
A.1.2 Control of spectrum utilization based on the number of CRSs . 82
A.1.2.1 Introduction. 82
ETSI
5 Draft ETSI EN 303 145 V1.1.5 (2015-07)
A.1.2.2 Flowchart of the algorithm . 83
A.1.3 Control of coordinated CRSs for reduced transmit power fluctuation . 85
A.1.3.1 Introduction. 85
A.1.3.2 Flowchart of the algorithm . 85
A.1.4 Spectrum rearrangement among CRSs . 86
A.1.4.1 Introduction. 86
A.1.4.2 Flowchart of the algorithm . 87
A.1.5 Resource allocation based on channel ranking . 88
A.1.5.1 Introduction. 88
A.1.5.2 Flowchart of the algorithm . 89
A.2 Priority access management algorithms . 90
A.2.1 Control of non-priority access CRSs for CRS with priority access . 90
A.2.1.1 Introduction. 90
A.2.1.2 Flowchart of the algorithm . 91
Annex B (informative): Possible Physical implementation examples of logical functions in
coordinated usage of white spaces . 92
B.1 Possible Physical implementation examples . 92
B.1.1 Third party database management . 92
B.1.2 GLDB with spectrum coordination function . 92
B.1.3 CRS with spectrum coordination function . 93
B.1.4 Spectrum coordination for Multi-operators . 94
History . 95
ETSI
6 Draft ETSI EN 303 145 V1.1.5 (2015-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This 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
7 Draft ETSI EN 303 145 V1.1.5 (2015-07)
1 Scope
The present document defines the system architecture for the use of spectrum by White Space Devices (WSDs),
specifically in the UHF TV Bands. The architecture stems from ETSI TS 102 946 [1]. The scope of the present
document is to define the architecture of a system which can allow operation of WSDs based on information obtained
from Geo-location databases. The architecture will consider both uncoordinated use of White Space (where there is no
attempt to manage the usage of channels by different WSDs) as well as coordinated use of White Space (where some
form of channel management and/or coexistence techniques are employed to efficiently use the White Space).
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 102 946: "Reconfigurable Radio Systems (RRS); System requirements for Operation in
UHF TV Band White Spaces".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 067: "Reconfigurable Radio Systems (RRS); Feasibility study on Radio Frequency
(RF) performance for Cognitive Radio Systems operating in UHF TV band White Spaces".
[i.2] ECC Report 186: "Technical and operational requirements for the operation of white space devices
under geo-location approach".
™
[i.3] IEEE 802.22: "Cognitive Radio Wireless Regional Area Networks (WRAN) Medium Access
Control (MAC) and Physical Layer (PHY) Specifications: Policies and Procedures for Operation
in the Bands that Allow Spectrum Sharing where the Communications Devices may
Opportunistically Operate in the Spectrum of the Primary Service".
™
[i.4] IEEE 802.11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[i.5] ETSI EN 301 598 (V1.1.1): "White Space Devices (WSD);Wireless Access Systems operating in
the 470 MHz to 790 MHz TV broadcast band; Harmonized EN covering the essential requirements
of article 3.2 of the R&TTE Directive".
ETSI
8 Draft ETSI EN 303 145 V1.1.5 (2015-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
coexistence: situation in which one radio system operates in an environment where another radio system having
potentially different characteristics (e.g. RAT) may be using the same or different channels, and both radio systems are
able to operate with some tolerable impact to each other
coordinated use of white spaces: case when each CRS uses available white space resources obtained with the help of
the geo-location database and with additional knowledge of spectrum usage by its neighbour CRSs by the SC
NOTE: The case in which the SC assigns directly channels to the CRSs is also part of the coordinated use of
white spaces.
coordination: ability of managing two or more CRSs to allow them to follow pre-determined operation policies such as
coexistence among coordinated CRSs
coordination report: information to the CRS to make coordination decisions on its operational parameters in the
information service
NOTE: This includes channel usage information, output power level, channel availability time, sensing
information, as well as some initial ranking of the available channels.
coordination set: set of CRSs which may affect the performance of the CRS they are associated to
Geo-Location Database (GLDB): database approved by the relevant national regulatory authority which can
communicate with WSDs and provide information on TVWS channel availability
NOTE 1: Information provided by a GLDB will include the available frequencies and associated maximum EIRP
values that the WSD is permitted to use which allow for protection of the incumbent service and are
derived from information provided by the WSD and the minimum required ACLR of the WSD.
NOTE 2: The GLDB consists of database and geo-location functions.
priority-based channel assignment: assignment of a channel by the SC to a CRS in such a way that the CRS can
operate alone in such channel for a specific reservation period and in a specific area based on particular minimum
protection requirements of the CRS
NOTE: CRSs assigned such channels with therefore have priority over other CRSs.
Spectrum Coordinator (SC): entity that coordinates spectrum usage of CRS based on the information obtained from
geo-location database as well as supplemental spectrum usage data from different CRSs using its service
uncoordinated use of white spaces: case when each CRS independently uses available white space resources obtained
with the help of the geo-location database without any help from the spectrum coordination function to coordinate
spectrum usage with its neighbour CRSs
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACLR Adjacent Channel Leakage Ratio
BC Branch Condition
Com-SAP Communication Service Access Point
CR Cognitive Radio
CRS Cogitative Radio System
C-SAP Control Service Access Point
CSMA Carrier Sense Multiple Access
DB-SAP DataBase-Service Access Point
DS Decision Status
DTV Digital TV
ETSI
9 Draft ETSI EN 303 145 V1.1.5 (2015-07)
EIRP Effective Isotropic Radiated Power
GLDB Geo-Location Database
GL-SAP GeoLocation-Service Access Point
NAV Network Allocation Vector
NRA National Regulatory Authority
QoS Quality of Service
RAT Radio Access Technology
SAP Service Access Point
SC Spectrum Coordinator
SC-SAP Spectrum Coordinator Service Access Point
SINR Signal to Interference plus Noise Ratio
TV TeleVision
TVWS TV White Space
UHF Ultra High Frequency
WSD White Space Device
4 Functional Architecture
4.1 Overview of Functional Architecture
Figure 4.1 shows the high level functional architecture of a white space system. All the system requirements specified
in ETSI TS 102 946 [1] shall be supported.
Figure 4.1: Overview of TV white spaces system
The TV white space system has three entities:
• Cognitive Radio System (CRS);
• Spectrum Coordinator (SC);
• Geolocation Database (GLDB);
and four reference points (A, B, C, and D), as shown in figure 4.1.
Each entity is defined by its functional roles and reference points with other entities.
The cognitive radio system (CRS) represents a white spaces device (WSD) or network of WSDs (i.e. a master WSD and
some slave WSDs). The CRS uses available white space resources obtained with the help of geo-location database
(GLDB) and/or with additional knowledge of spectrum usage by its neighbour CRSs provided by the spectrum
coordinator (SC).
ETSI
10 Draft ETSI EN 303 145 V1.1.5 (2015-07)
The GLDB provides a WSD in a CRS with location specific information on the available frequencies and associated
maximum EIRP values that the WSD is permitted to use. This will allow for protection of the incumbent service and is
derived from information provided by the WSD and the minimum required Adjacent Channel Leakage Ratio (ACLR)
of the WSD itself.
The SC is responsible for coordinating spectrum usage of CRSs based on the information obtained from GLDB as well
as additional spectrum usage data from different CRSs using its service. Different SCs are capable of communicating
with each other.
The reference point A that is related to the uncoordinated usage of White Spaces is described in ETSI EN 301 598 [i.5].
4.2 Coordinated Usage of White Spaces
4.2.1 Spectrum coordination
4.2.1.1 Overview
Spectrum coordination is the mechanism with which an SC serves CRSs so that they can operate efficiently in available
spectrum resources of white spaces. The SC coordinates how to manage radio resources among a set of CRSs that are
potentially interfering with each other (coexistence) and allows for channel assignment requested by a CRS that wishes
to operate alone on a channel and with priority over other CRSs (priority-based channel assignment). The priority-based
channel assignment is managed by the SC based on some minimum protection requirements requested by the CRS,
which includes minimum bandwidth, minimum SINR (or maximum allowable interference) and some guaranteed
minimum availability time. The SC translates these requirements into protection criteria, which are used by the GLDB
to ensure that the priority-based channel assignment is maintained in the presence of other WSDs not using the SC. The
algorithms to enable coexistence and/or priority-based channel assignment are described in Annex A. From the
perspective of the CRSs, coexistence and priority-based channel assignment are provided as a set of two available SC
services: the information service (for coexistence only) and the management service (for both coexistence and
priority-based channel assignment). Each SC shall provide at least the information service or the management service
for CRSs but can also provide both of them. The information service and the management service are described in
clauses 4.2.1.2 and 4.2.1.3.
4.2.1.2 Information service
For CRSs that are subscribed to the information service, an SC provides information about useful operational
parameters (e.g. the operational parameters of other CRS in the available spectrum resources). In the information
service, an SC does not make decision on the operational parameters to be used by those CRSs, but rather, all decisions
are made by the CRS itself. However, the SC may process information about the current usage of spectrum to provide
to the CRS in a manner which may facilitate the CRS decision (such as ranking the potential operational parameters
according to the resulting expected performance).
4.2.1.3 Management service
For CRSs that are subscribed to the management service, a SC provides the operational parameters to be used by a CRS
based on its requests and, potentially, certain QoS and usage time requirements. A CRS does not make any decision for
its operational parameters (e.g. channel and transmit power) but they are determined by the SC itself.
4.2.2 High level operation sequence
An overview of coordinated usage of white spaces is shown in figure 4.2.
Figure 4.2: Overview of coordinated usage of white spaces system
ETSI
11 Draft ETSI EN 303 145 V1.1.5 (2015-07)
A CRS consists of a master WSD and one or more slave WSDs. The master WSD sends device parameters to a GLDB
via the SC. The SC shall act as relay and can also store the device parameters of the master WSD. The SC, during the
process, maintains additional data about spectrum usage of the different CRSs using its service. This additional data
contains information that reflects the current state of spectrum usage, including spectrum measurement data from
WSDs, and usage maps or areas of occupancy of the different CRSs. It also contains parameters specific to the Radio
Access Technology of each CRS that facilitates coexistence. A GLDB shall receive information from the master WSD
about the characteristics of that WSD in order to generate operational parameters for that WSD. The GLDB provides
specific operational parameters to the master WSD via the SC. During this process, the SC determines the operational
parameters using the information obtained from the GLDB as well as the additional data about spectrum usage of the
different CRSs, and sends these operational parameters to the master WSD in response to the request for white space
access. The operational parameters determined by the SC shall not violate the protection criteria of the incumbent, and
are therefore compliant with the information obtained from the GLDB. The master WSD then sends the selected
channel usage parameter to the GLDB via the SC [i.2]. The SC will also update its additional spectrum usage data based
on information sent by the WSD. At any time in the process of assigning channels to the CRSs, the SC could
reconfigure the channel usage of the CRSs to ensure an efficient use of spectrum, such as reducing fragmentation in the
available spectrum. The GLDB can use channel usage parameters sent by the SC to ensure that WSDs can operate in the
presence of other WSDs not using the SC.
4.3 Uncoordinated Usage of White Spaces
4.3.1 High level operation sequence
An overview of uncoordinated usage of white spaces is shown in figure 4.3.
Figure 4.3: Overview of uncoordinated usage of white spaces system
A CRS consists of a master WSD and one or more slave WSDs. The master WSD shall communicate with a GLDB to
obtain its operational parameters in white spaces. A GLDB shall receive information from a WSD about the
characteristics of that WSD in order to generate operational parameter for that WSD. A GLDB shall maintain a record
of the actual usage of the white spaces. This information could be used to enable WSDs to be readily identified if
interference to incumbent users were to occur, and to allow the GLDB to know the extent to which available white
spaces are being used.
5 Detailed Functional Architecture
5.1 Architecture Description
The overall system reference model is shown in figure 5.1.
ETSI
12 Draft ETSI EN 303 145 V1.1.5 (2015-07)
Figure 5.1: Overall system reference model
There are six logical functions for operating white space system: control function, spectrum coordination function,
database function and geo-location function are the 4 key components for the system. Two additional functions (the
interface function and the communication function) are general components for the system. Physical implementation
examples of the overall system reference model are shown in annex B. Clause 5.2 describes in more detail the six
identified logical functions.
5.2 Functional Description of Components
5.2.1 Database function
A database function is a software/hardware module that stores necessary information provided by regulators for
calculating the available spectrum that a WSD in a CRS can operate on (with protection to incumbent services) as well
as registration of the WSDs under regulatory requirements and for the purposes of protecting incumbent services. The
reference model of database function is shown in figure 5.2.
Figure 5.2: Reference model of a database function
The database function service access point (SAP) is the database SAP (DB-SAP). The DB-SAP is used by the interface
function to access the services provided by the database function such as registration of CRS and provision of
incumbent information.
5.2.2 Geo-location function
A geo-location function is a software/hardware module that supports the following functions:
• To calculate location specific available frequency band and associated maximum EIRP that a WSD in a CRS
can use based on the information on incumbents stored in database function.
• To Interact with the SC for management of uncoordinated CRSs when considering priority usage coordinated
CRSs.
ETSI
13 Draft ETSI EN 303 145 V1.1.5 (2015-07)
The reference model of the geo-location function is shown in figure 5.3.
Figure 5.3: Reference model of a geo-location function
The geo-location function service access point (SAP) is the geo-location SAP (GL-SAP). GL-SAP is used by the
interface function to access the services provided by the geo-location function such as calculation of location specific
EIRP of a frequency band and that a WSD in a CRS can use.
5.2.3 Spectrum coordination function
A spectrum coordination function is a software/hardware module that coordinates spectrum usage of CRSs based on the
information obtained from geo-location database and additional data about the spectrum usage of the different CRSs
using the services of the SC. The reference model of spectrum coordination function is shown in figure 5.4. Depending
on the implementation and location of the spectrum coordination function in the system (see annex B for examples) the
spectrum coordination function will have one or more of the following functionalities:
Coexistence functionality: This functionality assures proper operation between different WSDs that utilize the white
space, and avoidance of harmful interference between different CRSs using the same and/or adjacent channels.
Sensing and measurement functionality: The sensing functionality is responsible for the configuration of sensing in
the CRS as well as the collection and combined processing of the sensing results and the measurements specific of the
RAT that the CRS is using.
Priority-Based Channel assignment and negotiation functionality: This functionality allows certain CRSs or other
spectrum coordination functions to assign channels and provides the necessary means for negotiation between different
CRSs which may request a priority-based channel assignment for periods of time.
Figure 5.4: Reference model of spectrum coordination function
The spectrum coordination function service access point is the spectrum coordination SAP (SC-SAP). The coexistence
functionality, sensing functionality, and priority usage and negotiation functionality all communicate with functions
outside of the spectrum coordination function using the same SC-SAP. SC-SAP is used by the interface function to
access the services provided by the spectrum function such as calculation of coordination parameters based on
coexistence algorithms, priority-based channel assignment algorithms, etc. that a WSD in a CRS can use.
ETSI
14 Draft ETSI EN 303 145 V1.1.5 (2015-07)
5.2.4 Control function
A control function is a hardware/software module that controls operation of a CRS in white space such as sending
device parameters to GLDB/SC, receiving operational parameters from GLDB/SC, sending operational parameters
and/or channel assignment to CRSs, sending channel usage parameters to GLDB/SC, sending requests to SC, and
receiving responses from SC. The reference model of the control function is shown in figure 5.5.
Figure 5.5: Reference model of spectrum coordination function
The control function service access point is the control SAP (C-SAP). C-SAP is used by applications to access
information and parameters of GLDB and/or SC. It defines a set of generic primitives and data structures to control the
CRSs and/or to obtain the information and parameters of GLDB and/or SC for application purposes. A CRS utilizing
the C-SAP takes the role of an informatio
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Radijski sistemi z možnostjo preoblikovanja (RRS) - Arhitektura sistema in vrhunski postopki za usklajeno in neusklajeno uporabo belih lis TVReconfigurable Radio Systems (RRS) - System Architecture and High Level Procedures for Coordinated and Uncoordinated Use of TV White Spaces33.060.01Radijske komunikacije na splošnoRadiocommunications in generalICS:Ta slovenski standard je istoveten z:EN 303 145 V1.2.1SIST EN 303 145 V1.2.1:2016en01-marec-2016SIST EN 303 145 V1.2.1:2016SLOVENSKI
STANDARD
EUROPEAN STANDARD SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 2
Reference REN/RRS-0144 Keywords architecture, GLDB, system, white space ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88
Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2015. All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 3 Contents Intellectual Property Rights . 6 Foreword . 6 Modal verbs terminology . 6 1 Scope . 7 2 References . 7 2.1 Normative references . 7 2.2 Informative references . 7 3 Definitions and abbreviations . 8 3.1 Definitions . 8 3.2 Abbreviations . 8 4 Functional Architecture . 9 4.1 Overview of Functional Architecture . 9 4.2 Coordinated Usage of White Spaces . 10 4.2.1 Spectrum coordination . 10 4.2.1.1 Overview . 10 4.2.1.2 Information service . 10 4.2.1.3 Management service. 10 4.2.2 High level operation sequence . 10 4.3 Uncoordinated Usage of White Spaces . 11 4.3.1 High level operation sequence . 11 5 Detailed Functional Architecture . 11 5.1 Architecture Description . 11 5.2 Functional Description of Components . 12 5.2.1 Database function . 12 5.2.2 Geo-location function . 12 5.2.3 Spectrum coordination function . 13 5.2.4 Control function . 14 5.2.5 Communication function . 14 5.2.6 Interface function . 14 5.3 Reference Points . 15 5.3.1 Reference point A: Between a GLDB and a CRS . 15 5.3.2 Reference point B: Between a CRS and a SC . 16 5.3.3 Reference point C: Between SCs . 16 5.3.4 Reference point D: Between a SC and a GLDB . 17 5.4 Potential Interaction of Functionality within the spectrum coordination function . 18 6 High Level Procedures . 19 6.1 Procedures for Coordinated Access of White Spaces . 19 6.1.1 Initialization procedures . 19 6.1.2 Coordination service subscription procedures . 19 6.1.2.1 Overview . 19 6.1.2.2 CRS subscription procedure . 19 6.1.2.3 CRS subscription update procedure . 20 6.1.2.4 CRS subscription change procedure . 21 6.1.3 Registration and authentication procedures . 21 6.1.3.1 Overview . 21 6.1.3.2 CRS registration procedure . 22 6.1.3.3 CRS registration update procedure . 22 6.1.3.4 Procedure for CRS deregistration from SC . 23 6.1.3.5 SC authentication and registration procedure . 23 6.1.3.6 SC de-authentication and de-registration procedure . 24 6.1.4 Channel Access Procedures . 25 6.1.4.1 Requesting CRS channel access procedure . 25 6.1.4.2 Requesting SC channel access procedure . 25 6.1.4.3 Providing available channel list procedure . 26 SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 4 6.1.4.4 Procedure of channel usage notification for subject CRS . 27 6.1.4.5 Procedure for GLDB to SC Notification for CRS operational parameters update . 27 6.1.4.6 CRS's operational parameters update request procedure from SC for incumbent protection . 28 6.1.4.7 Basic Channel Access Sequence . 30 6.1.4.8 Channel Access Sequence for Priority-Based Channel Assignment . 31 6.1.5 Information exchange procedures . 32 6.1.5.1 Providing coordination report procedure . 32 6.1.6 Sensing and Measurement Procedures and Operation Sequences . 33 6.1.6.1 Overview . 33 6.1.6.2 Requesting measurements procedure . 33 6.1.6.3 Providing periodic measurements procedure . 33 6.1.6.4 Providing single measurements procedure . 34 6.1.6.5 Non-Periodic measurements sequence . 35 6.1.6.6 Event-Triggered Measurement Sequence . 35 6.1.7 Reconfiguration Procedures and Operation Sequences . 37 6.1.7.1 Reconfiguration request from SC to CRS procedure . 37 6.1.7.2 Reconfiguration request from SC to GLDB procedure . 38 6.1.7.3 General reconfiguration sequence between coordinated CRSs . 38 6.1.7.4 CRS Request-Triggered Operational Parameter Reconfiguration . 40 6.1.7.5 CRS-Measurement Triggered Priority-Based Operational Parameter Reconfiguration . 43 6.1.7.6 General Priority-Based Channel Reconfiguration Sequence . 45 6.1.7.7 Management of uncoordinated CRSs considering priority usage of coordinated CRSs . 46 6.1.7.8 Priority Usage Request Considering Uncoordinated Channel Usage . 47 6.1.7.8.1 Overview . 47 6.1.7.8.2 Implementation Option A . 47 6.1.7.8.3 Implementation Option B . 49 6.1.7.9 Uncoordinated CRS Request Considering Priority Usage Coordinated CRS . 53 6.1.7.9.1 Overview . 53 6.1.7.9.2 Implementation Option A . 54 6.1.7.9.3 Implementation Option B . 54 6.1.7.10 Device parameter reconfiguration request from SC to CRS procedure. 56 6.1.7.11 General sequence of device parameter reconfiguration request from SC to CRS for facilitating coexistence among CRSs . 57 6.1.8 Inter-SC procedures . 58 6.1.8.1 Reconfiguration request from master SC to CRS registered to slave SC procedure . 58 6.1.8.2 Master/slave SC configuration procedure . 59 6.1.8.3 Obtaining coordination set information from other SCs procedure . 60 6.1.8.4 Procedures for interfering SCs discovery . 61 6.1.8.4.1 Overview . 61 6.1.8.4.2 GLDB-aided potential interfering SCs discovery procedure . 61 6.1.8.4.3 Interfering SCs discovery procedure . 62 6.1.8.5 Negotiation between SCs procedure . 63 6.1.8.6 Operational Sequences for negotiation-based configuration of SCs . 64 6.2 Procedures for Uncoordinated Access of White Spaces . 65 7 Potential Implementation Architectures . 65 7.1 High level flow chart of entities . 65 7.1.1 CRS operation . 65 7.1.1.1 General description . 65 7.1.2 SC operation . 69 7.1.2.1 General description . 69 7.1.3 GLDB operation . 74 7.1.3.1 General description . 74 Annex A (informative): High Level Spectrum Management Algorithms for White Spaces . 77 A.1 Coexistence decision algorithms . 77 A.1.1 Algorithm based on co-channel sharing via CRS network geometry classification . 77 A.1.1.1 Introduction. 77 A.1.1.2 Network geometry classification . 77 A.1.1.3 Algorithm description . 81 A.1.2 Control of spectrum utilization based on the number of CRSs . 82 A.1.2.1 Introduction. 82 SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 5 A.1.2.2 Flowchart of the algorithm . 83 A.1.3 Control of coordinated CRSs for reduced transmit power fluctuation . 85 A.1.3.1 Introduction. 85 A.1.3.2 Flowchart of the algorithm . 85 A.1.4 Spectrum rearrangement among CRSs . 86 A.1.4.1 Introduction. 86 A.1.4.2 Flowchart of the algorithm . 87 A.1.5 Resource allocation based on channel ranking . 88 A.1.5.1 Introduction. 88 A.1.5.2 Flowchart of the algorithm . 89 A.2 Priority access management algorithms . 90 A.2.1 Control of non-priority access CRSs for CRS with priority access . 90 A.2.1.1 Introduction. 90 A.2.1.2 Flowchart of the algorithm . 91 Annex B (informative): Possible Physical implementation examples of logical functions in coordinated usage of white spaces . 92 B.1 Possible Physical implementation examples . 92 B.1.1 Third party database management . 92 B.1.2 GLDB with spectrum coordination function . 92 B.1.3 CRS with spectrum coordination function . 93 B.1.4 Spectrum coordination for Multi-operators . 94 History . 95
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Reconfigurable Radio Systems (RRS).
National transposition dates Date of adoption of this EN: 6 November 2015 Date of latest announcement of this EN (doa): 29 February 2016 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
31 August 2016 Date of withdrawal of any conflicting National Standard (dow): 31 August 2016
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 ETSI EN 303 145 V1.2.1 (2015-11) 7 1 Scope The present document defines the system architecture for the use of spectrum by White Space Devices (WSDs), specifically in the UHF TV Bands. The architecture stems from ETSI TS 102 946 [1]. The scope of the present document is to define the architecture of a system which can allow operation of WSDs based on information obtained from Geo-location databases. The architecture will consider both uncoordinated use of White Space (where there is no attempt to manage the usage of channels by different WSDs) as well as coordinated use of White Space (where some form of channel management and/or coexistence techniques are employed to efficiently use the White Space). 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 946: "Reconfigurable Radio Systems (RRS); System requirements for Operation in UHF TV Band White Spaces". 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 103 067: "Reconfigurable Radio Systems (RRS); Feasibility study on Radio Frequency (RF) performance for Cognitive Radio Systems operating in UHF TV band White Spaces". [i.2] ECC Report 186: "Technical and operational requirements for the operation of white space devices under geo-location approach". [i.3] IEEE™ 802.22: "Cognitive Radio Wireless Regional Area Networks (WRAN) Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Policies and Procedures for Operation in the Bands that Allow Spectrum Sharing where the Communications Devices may Opportunistically Operate in the Spectrum of the Primary Service". [i.4] IEEE™ 802.11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". [i.5] ETSI EN 301 598 (V1.1.1): "White Space Devices (WSD);Wireless Access Systems operating in the 470 MHz to 790 MHz TV broadcast band; Harmonized EN covering the essential requirements of article 3.2 of the R&TTE Directive". SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 8 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: coexistence: situation in which one radio system operates in an environment where another radio system having potentially different characteristics (e.g. RAT) may be using the same or different channels, and both radio systems are able to operate with some tolerable impact to each other coordinated use of white spaces: case when each CRS uses available white space resources obtained with the help of the geo-location database and with additional knowledge of spectrum usage by its neighbour CRSs by the SC NOTE: The case in which the SC assigns directly channels to the CRSs is also part of the coordinated use of white spaces. coordination: ability of managing two or more CRSs to allow them to follow pre-determined operation policies such as coexistence among coordinated CRSs coordination report: information to the CRS to make coordination decisions on its operational parameters in the information service NOTE: This includes channel usage information, output power level, channel availability time, sensing information, as well as some initial ranking of the available channels. coordination set: set of CRSs which may affect the performance of the CRS they are associated to Geo-Location Database (GLDB): database approved by the relevant national regulatory authority which can communicate with WSDs and provide information on TVWS channel availability NOTE 1: Information provided by a GLDB will include the available frequencies and associated maximum EIRP values that the WSD is permitted to use which allow for protection of the incumbent service and are derived from information provided by the WSD and the minimum required ACLR of the WSD. NOTE 2: The GLDB consists of database and geo-location functions. priority-based channel assignment: assignment of a channel by the SC to a CRS in such a way that the CRS can operate alone in such channel for a specific reservation period and in a specific area based on particular minimum protection requirements of the CRS NOTE: CRSs assigned such channels with therefore have priority over other CRSs. Spectrum Coordinator (SC): entity that coordinates spectrum usage of CRS based on the information obtained from geo-location database as well as supplemental spectrum usage data from different CRSs using its service uncoordinated use of white spaces: case when each CRS independently uses available white space resources obtained with the help of the geo-location database without any help from the spectrum coordination function to coordinate spectrum usage with its neighbour CRSs 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ACLR Adjacent Channel Leakage Ratio BC Branch Condition Com-SAP Communication Service Access Point CR Cognitive Radio CRS Cogitative Radio System C-SAP Control Service Access Point CSMA Carrier Sense Multiple Access DB-SAP DataBase-Service Access Point DS Decision Status DTV Digital TV SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 9 EIRP Effective Isotropic Radiated Power GLDB Geo-Location Database GL-SAP GeoLocation-Service Access Point NAV Network Allocation Vector NRA National Regulatory Authority QoS Quality of Service RAT Radio Access Technology SAP Service Access Point SC Spectrum Coordinator SC-SAP Spectrum Coordinator Service Access Point SINR Signal to Interference plus Noise Ratio TV TeleVision TVWS TV White Space UHF Ultra High Frequency WSD White Space Device 4 Functional Architecture 4.1 Overview of Functional Architecture Figure 4.1 shows the high level functional architecture of a white space system. All the system requirements specified in ETSI TS 102 946 [1] shall be supported.
Figure 4.1: Overview of TV white spaces system The TV white space system has three entities: • Cognitive Radio System (CRS); • Spectrum Coordinator (SC); • Geolocation Database (GLDB); and four reference points (A, B, C, and D), as shown in figure 4.1. Each entity is defined by its functional roles and reference points with other entities. The cognitive radio system (CRS) represents a white spaces device (WSD) or network of WSDs (i.e. a master WSD and some slave WSDs). The CRS uses available white space resources obtained with the help of geo-location database (GLDB) and/or with additional knowledge of spectrum usage by its neighbour CRSs provided by the spectrum coordinator (SC). The GLDB provides a WSD in a CRS with location specific information on the available frequencies and associated maximum EIRP values that the WSD is permitted to use. This will allow for protection of the incumbent service and is derived from information provided by the WSD and the minimum required Adjacent Channel Leakage Ratio (ACLR) of the WSD itself. SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 10 The SC is responsible for coordinating spectrum usage of CRSs based on the information obtained from GLDB as well as additional spectrum usage data from different CRSs using its service. Different SCs are capable of communicating with each other. The reference point A that is related to the uncoordinated usage of White Spaces is described in ETSI EN 301 598 [i.5]. 4.2 Coordinated Usage of White Spaces 4.2.1 Spectrum coordination 4.2.1.1 Overview Spectrum coordination is the mechanism with which an SC serves CRSs so that they can operate efficiently in available spectrum resources of white spaces. The SC coordinates how to manage radio resources among a set of CRSs that are potentially interfering with each other (coexistence) and allows for channel assignment requested by a CRS that wishes to operate alone on a channel and with priority over other CRSs (priority-based channel assignment). The priority-based channel assignment is managed by the SC based on some minimum protection requirements requested by the CRS, which includes minimum bandwidth, minimum SINR (or maximum allowable interference) and some guaranteed minimum availability time. The SC translates these requirements into protection criteria, which are used by the GLDB to ensure that the priority-based channel assignment is maintained in the presence of other WSDs not using the SC. The algorithms to enable coexistence and/or priority-based channel assignment are described in Annex A. From the perspective of the CRSs, coexistence and priority-based channel assignment are provided as a set of two available SC services: the information service (for coexistence only) and the management service (for both coexistence and priority-based channel assignment). Each SC shall provide at least the information service or the management service for CRSs but can also provide both of them. The information service and the management service are described in clauses 4.2.1.2 and 4.2.1.3. 4.2.1.2 Information service For CRSs that are subscribed to the information service, an SC provides information about useful operational parameters (e.g. the operational parameters of other CRS in the available spectrum resources). In the information service, an SC does not make decision on the operational parameters to be used by those CRSs, but rather, all decisions are made by the CRS itself. However, the SC may process information about the current usage of spectrum to provide to the CRS in a manner which may facilitate the CRS decision (such as ranking the potential operational parameters according to the resulting expected performance). 4.2.1.3 Management service For CRSs that are subscribed to the management service, a SC provides the operational parameters to be used by a CRS based on its requests and, potentially, certain QoS and usage time requirements. A CRS does not make any decision for its operational parameters (e.g. channel and transmit power) but they are determined by the SC itself. 4.2.2 High level operation sequence An overview of coordinated usage of white spaces is shown in figure 4.2.
Figure 4.2: Overview of coordinated usage of white spaces system SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 11 A CRS consists of a master WSD and one or more slave WSDs. The master WSD sends device parameters to a GLDB via the SC. The SC shall act as relay and can also store the device parameters of the master WSD. The SC, during the process, maintains additional data about spectrum usage of the different CRSs using its service. This additional data contains information that reflects the current state of spectrum usage, including spectrum measurement data from WSDs, and usage maps or areas of occupancy of the different CRSs. It also contains parameters specific to the Radio Access Technology of each CRS that facilitates coexistence. A GLDB shall receive information from the master WSD about the characteristics of that WSD in order to generate operational parameters for that WSD. The GLDB provides specific operational parameters to the master WSD via the SC. During this process, the SC determines the operational parameters using the information obtained from the GLDB as well as the additional data about spectrum usage of the different CRSs, and sends these operational parameters to the master WSD in response to the request for white space access. The operational parameters determined by the SC shall not violate the protection criteria of the incumbent, and are therefore compliant with the information obtained from the GLDB. The master WSD then sends the selected channel usage parameter to the GLDB via the SC [i.2]. The SC will also update its additional spectrum usage data based on information sent by the WSD. At any time in the process of assigning channels to the CRSs, the SC could reconfigure the channel usage of the CRSs to ensure an efficient use of spectrum, such as reducing fragmentation in the available spectrum. The GLDB can use channel usage parameters sent by the SC to ensure that WSDs can operate in the presence of other WSDs not using the SC. 4.3 Uncoordinated Usage of White Spaces 4.3.1 High level operation sequence An overview of uncoordinated usage of white spaces is shown in figure 4.3.
Figure 4.3: Overview of uncoordinated usage of white spaces system A CRS consists of a master WSD and one or more slave WSDs. The master WSD shall communicate with a GLDB to obtain its operational parameters in white spaces. A GLDB shall receive information from a WSD about the characteristics of that WSD in order to generate operational parameter for that WSD. A GLDB shall maintain a record of the actual usage of the white spaces. This information could be used to enable WSDs to be readily identified if interference to incumbent users were to occur, and to allow the GLDB to know the extent to which available white spaces are being used. 5 Detailed Functional Architecture 5.1 Architecture Description The overall system reference model is shown in figure 5.1. SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 12
Figure 5.1: Overall system reference model There are six logical functions for operating white space system: control function, spectrum coordination function, database function and geo-location function are the 4 key components for the system. Two additional functions (the interface function and the communication function) are general components for the system. Physical implementation examples of the overall system reference model are shown in annex B. Clause 5.2 describes in more detail the six identified logical functions. 5.2 Functional Description of Components 5.2.1 Database function A database function is a software/hardware module that stores necessary information provided by regulators for calculating the available spectrum that a WSD in a CRS can operate on (with protection to incumbent services) as well as registration of the WSDs under regulatory requirements and for the purposes of protecting incumbent services. The reference model of database function is shown in figure 5.2.
Figure 5.2: Reference model of a database function The database function service access point (SAP) is the database SAP (DB-SAP). The DB-SAP is used by the interface function to access the services provided by the database function such as registration of CRS and provision of incumbent information. 5.2.2 Geo-location function A geo-location function is a software/hardware module that supports the following functions: • To calculate location specific available frequency band and associated maximum EIRP that a WSD in a CRS can use based on the information on incumbents stored in database function. • To Interact with the SC for management of uncoordinated CRSs when considering priority usage coordinated CRSs. SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 13 The reference model of the geo-location function is shown in figure 5.3.
Figure 5.3: Reference model of a geo-location function The geo-location function service access point (SAP) is the geo-location SAP (GL-SAP). GL-SAP is used by the interface function to access the services provided by the geo-location function such as calculation of location specific EIRP of a frequency band and that a WSD in a CRS can use. 5.2.3 Spectrum coordination function A spectrum coordination function is a software/hardware module that coordinates spectrum usage of CRSs based on the information obtained from geo-location database and additional data about the spectrum usage of the different CRSs using the services of the SC. The reference model of spectrum coordination function is shown in figure 5.4. Depending on the implementation and location of the spectrum coordination function in the system (see annex B for examples) the spectrum coordination function will have one or more of the following functionalities: Coexistence functionality: This functionality assures proper operation between different WSDs that utilize the white space, and avoidance of harmful interference between different CRSs using the same and/or adjacent channels. Sensing and measurement functionality: The sensing functionality is responsible for the configuration of sensing in the CRS as well as the collection and combined processing of the sensing results and the measurements specific of the RAT that the CRS is using. Priority-Based Channel assignment and negotiation functionality: This functionality allows certain CRSs or other spectrum coordination functions to assign channels and provides the necessary means for negotiation between different CRSs which may request a priority-based channel assignment for periods of time.
Figure 5.4: Reference model of spectrum coordination function The spectrum coordination function service access point is the spectrum coordination SAP (SC-SAP). The coexistence functionality, sensing functionality, and priority usage and negotiation functionality all communicate with functions outside of the spectrum coordination function using the same SC-SAP. SC-SAP is used by the interface function to access the services provided by the spectrum function such as calculation of coordination parameters based on coexistence algorithms, priority-based channel assignment algorithms, etc. that a WSD in a CRS can use. SIST EN 303 145 V1.2.1:2016
ETSI ETSI EN 303 145 V1.2.1 (2015-11) 14 5.2.4 Control function A control function is a hardware/software module that controls operation of a CRS in white space such as sending device parameters to GLDB/SC, receiving operational parameters from GLDB/SC, sending operational parameters and/or channel assignment to CRSs, sending channel usage parameters to GLDB/SC, sending requests to SC, and receiving responses from SC. The reference model of the control function is shown in figure 5.5.
Figure 5.5: Reference model of spectrum coordination function The control function service access point is the control SAP (C-SAP). C-SAP is used by applications to access information and parameters of GLDB and/or SC. It defines a set of generic primitives and data structures to control the CRSs and/or to obtain the information and parameters of GLDB and/or SC for application purposes. A CRS utilizing the C-SAP takes the role of an information consumer and of control application. 5.2.5 Communication function A communication function is a hardware/software module that provides the communications protocol stack, and other communication services required by the interfaces between logical entities. The reference model of the communication function is shown in figure 5.6.
Figure 5.6: Reference model of a communication function The communication function service access p
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...