ETSI TS 103 235 V1.1.1 (2015-10)

Reconfigurable Radio Systems (RRS); System architecture and high level procedures for operation of Licensed Shared Access (LSA) in the 2 300 MHz - 2 400 MHz band

DTS/RRS-0141

General Information

• Status: Published
• Publication Date: 15-Oct-2015
• Technical Committee: RRS 1 - RRS System Aspects & Cognitive functionalities
• Current Stage: 12 - Completion
• Due Date: 02-Nov-2015
• Completion Date: 16-Oct-2015
• Mandate: M/512

Standards Content (Sample)

ETSI TS 103 235 V1.1.1 (2015-10)






TECHNICAL SPECIFICATION
Reconfigurable Radio Systems (RRS);
System architecture and high level procedures
for operation of Licensed Shared Access (LSA)
in the 2 300 MHz - 2 400 MHz band

---------------------- Page: 1 ----------------------
2 ETSI TS 103 235 V1.1.1 (2015-10)



Reference
DTS/RRS-0141
Keywords
architecture, BWA, radio
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

---------------------- Page: 2 ----------------------
3 ETSI TS 103 235 V1.1.1 (2015-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Architecture Model. 7
4.1 Architecture Reference Model . 7
4.2 Logical Elements . 8
4.3 Reference Points . 8
4.4 High Level Functions . 8
4.4.0 Introduction. 8
4.4.1 Information Entry Function . 8
4.4.2 Information Processing Function . 9
4.4.3 Information Mapping Function . 9
4.4.4 Reporting Function . 9
4.4.5 LSA Information Exchange Function . 9
4.4.6 System Support Functions Group . 9
4.4.7 System Management Functions Group . 9
4.5 Mapping of High Level Functions to Logical Elements. 10
5 LSA Functional Description and Information Flows . 10
1
5.1 Introduction . 10
5.2 Protocol Stacks . 10
5.3 LSA Interface Management Functions . 10
1
5.4 LSA Protocol Elements . 11
1
5.4.1 Identities . 11
5.4.2 LSA Spectrum Resource Availability Information . 11
5.5 High Level Procedures . 11
5.5.1 Introduction. 11
5.5.2 Registration Procedure . 12
5.5.3 Deregistration Procedure . 12
5.5.4 LSRAI Request Procedure . 13
5.5.5 LSRAI Notification Procedure . 13
5.5.6 LSRAI Confirmation Procedure . 14
5.5.7 Connectivity Check Notification Procedure . 14
5.5.8 Connectivity Check Request Procedure . 15
5.6 Procedure Flows . 15
5.6.1 Introduction. 15
5.6.2 LC Operation Start-up . 15
5.6.3 LR Notification of new LSRAI. 16
5.6.4 LSRAI Synchronization . 17
5.6.5 LC Request for new LSRAI with optional LR Notification . 17
6 LSA Failure Management . 18
7 LSA Deployment Scenario Rules . 19
Annex A (informative): LSA Operational Use Cases . 20
A.0 Introduction . 20
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 235 V1.1.1 (2015-10)
A.1 Input of the Sharing Framework, Sharing Arrangement and LSA License information to the LSA
Repository . 20
A.2 Input of Incumbent's usage and protection requirements . 20
A.3 LSA Licensee activates LSA support operation . 21
A.4 LSA Licensee starts to operate in the available LSA spectrum resources . 21
A.5 Updates of the incumbent's usage and protection requirements . 22
Annex B (informative): Guidance for LSA and LSA . 23
2 3
B.0 Introduction . 23
B.1 NRA-Related Guidance (LSA ) . 23
2
B.2 Incumbent-related Guidance (LSA ) . 23
3
Annex C (informative): Deployment Architecture Examples . 25
C.1 Introduction . 25
C.2 Examples . 25
C.2.1 LR and single LC . 25
C.2.2 LR and multiple LCs . 25
C.2.3 LR and "proxy LC" . 26
Annex D (informative): Example for possible LC fall-back measures if LSRAI consistency
cannot be guaranteed on both ends of LSA . 27
1
History . 28

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 235 V1.1.1 (2015-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Reconfigurable Radio Systems
(RRS).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 235 V1.1.1 (2015-10)
1 Scope
The present document specifies the system architecture for operation of mobile broadband service in the
2 300 MHz - 2 400 MHz band under Licensed Shared Access (LSA) [i.2] and [i.3], aimed at enabling access for
mobile/fixed communication networks (MFCNs) in those CEPT countries where access to the band is foreseen but
cannot be provided without restrictions due to Incumbent usage, as documented in ETSI TR 103 113 [i.1]. Application
to other bands is not precluded and depends on future regulatory decisions.
The documented system architecture includes definition of the logical elements, reference points and functions
supported by the architecture, and the definition of the procedures and procedure flows. The present document has been
developed following, and in accordance with, the System Requirements for LSA as documented in ETSI
TS 103 154 [1].
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 103 154: "Reconfigurable Radio Systems (RRS); System requirements for operation of
Mobile Broadband Systems in the 2 300 MHz - 2 400 MHz band under Licensed Shared Access
(LSA)".
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 113 (V1.1.1): "Electromagnetic compatibility and Radio spectrum Matters (ERM);
System Reference document (SRdoc); Mobile broadband services in the 2 300 MHz - 2 400 MHz
frequency band under Licensed Shared Access regime".
[i.2] ECC Report 205: "Licensed Shared Access (LSA)", February 2014.
[i.3] RSPG Opinion on Licensed Shared Access, RSPG13-538, November 2013.
[i.4] IETF RFC 791: "Internet Protocol (IP)", September 1981.
[i.5] ECC Recommendation (15)04: "Guidance for the implementation of a sharing framework between
MFCN and PMSE within 2300-2400 MHz", July 2015.
[i.6] CEPT Report 58: "Technical sharing solutions for the shared use of the 2300-2400 MHz band for
WBB and PMSE", July 2015.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 235 V1.1.1 (2015-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
LSA licensee: entity operating a MFCN, which holds individual rights of use to an LSA spectrum resource
LSA spectrum resource: spectrum resource which is to be shared between an Incumbent and a LSA Licensee on a
static or dynamic basis according to the Sharing Framework defined by the Administration/NRA
LSA spectrum resource availability information: information provided to a Licensee, which conveys the LSA
spectrum resource that may be used by the Licensee, and the respective operational conditions
sharing arrangement: set of practical details for sharing an LSA spectrum resource
sharing framework: set of sharing rules or sharing conditions that will materialize the change, if any, in the spectrum
rights of the Incumbent(s) and define the spectrum, with corresponding technical and operational conditions, that can be
made available for alternative usage under LSA
spectrum resource: resource or set of resources defined in time, space and frequency domains
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
DTLS Datagram Transport Layer Security
ECC Electronic Communications Committee of the CEPT
IP Internet Protocol
IPsec Internet Protocol security
ITU International Telecommunications Union
LC LSA Controller
LR LSA Repository
LSA Licensed Shared Access
LSRAI LSA Spectrum Resource Availability Information
LTE Long Term Evolution
MFCN Mobile/Fixed Communications Network
NRA National Regulatory Authority
OAM Operation, Administration and Maintenance
RSPG Radio Spectrum Policy Group
TCP Transmission Control Protocol
TLS Transport Layer Security
UDP User Datagram Protocol
4 Architecture Model
4.1 Architecture Reference Model
The LSA Architecture reference model is shown in figure 4.1. Reference points shown in dashed format indicate that
the respective interfaces and corresponding interface functions will not be defined in the present document, although
some guidance is provided (see annex B).
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 235 V1.1.1 (2015-10)

Figure 4.1: LSA Architecture Reference Model
4.2 Logical Elements
LSA Repository (LR): The LR supports the entry and storage of information describing Incumbent's usage and
protection requirements [1]. It is able to convey the related availability information to authorized LSA Controllers, and
is also able to receive and store acknowledgement information received from the LSA Controllers. The LR also
provides means for the NRA to monitor the operation of the LSA System [1], and to provide the LSA System with
information on the Sharing Framework and the LSA Licensees. The LR ensures that the LSA system operates in
conformance with the Sharing Framework [i.2] and the licensing regime, and may in addition realize any non-
regulatory details of the Sharing Arrangement [1].
LSA Controller (LC): The LC is located within the LSA Licensee's domain, and enables the LSA Licensee [1] to
obtain LSA spectrum resource availability information from the LR, and to provide acknowledgment information to the
LR. The LC interacts with the Licensee's MFCN in order to support the mapping of availability information into
appropriate radio transmitter configurations, and receive the respective confirmations from the MFCN.
4.3 Reference Points
LSA : Reference point between LR and LC.
1
LSA : Reference point for Administration/NRA interaction with the LR. Some of the functionality
2
associated with this reference point is described in annex B.
LSA : Reference point for Incumbent interaction with the LR. Some of the functionality associated with
3
this reference point is described in annex B.
4.4 High Level Functions
4.4.0 Introduction
This clause lists and describes the high level functions performed by the LSA System. The high level functions cover
the aspects of LSA System operation in line with requirements of ETSI TS 103 154 [1].
4.4.1 Information Entry Function
Allows the entry and storage of information that is needed for the operation of the LSA System, including the
following:
• Sharing Framework information (set of sharing rules or sharing conditions for the band, information on
spectrum that can be made available for shared use and the corresponding technical and operational conditions
for its use, identification of incumbents).
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 235 V1.1.1 (2015-10)
• LSA License information (Licensee identity and related information).
• Sharing Arrangement information for each Incumbent and Licensee (set of practical details for sharing an LSA
spectrum resource, whereby LSA spectrum resource may be used by Incumbent or LSA Licensee).
• Incumbent's LSA spectrum resource usage and protection requirements.
The function also supports the verification of inputs (consistency with Sharing Framework/Arrangement).
4.4.2 Information Processing Function
This function supports the derivation of LSA spectrum resource availability information for each Licensee, to be
provided to the Information Exchange function for forwarding to the respective Information Mapping function of the
LSA Licensee. The LSA spectrum resource availability information is derived based on the data collected by the
Information Entry Function. The function further supports the processing of Licensee acknowledgment information.
The above functionality also includes support for multiple Incumbents and multiple LSA Licensees, scheduled and on-
demand modes of operation, and logging of processing information.
4.4.3 Information Mapping Function
The information mapping function receives LSA spectrum resource availability information, confirms reception and
initiates respective operations in the MFCN. It also sends acknowledgements to the information exchange function (for
forwarding to the information processing function) when changes in the MFCN are processed.
NOTE: The respective interaction with the MFCN is out of scope of the present document.
4.4.4 Reporting Function
The reporting function is responsible to create and provide reports regarding the LSA System operation to
Administration/NRA, Incumbent(s), and/or LSA Licensee(s) on an on-demand or scheduled basis.
4.4.5 LSA Information Exchange Function
The information exchange function supports communication mechanisms, internal to the LSA System, to exchange
LSA spectrum resource availability information, and related acknowledgement information.
4.4.6 System Support Functions Group
The system support functions comprise:
Security Support Function: support of authentication and authorization as well as services to support integrity and
confidentiality of data.
Robustness and Reliability Function: support of mechanisms to maintain robustness and reliability against failures
and malicious attacks.
Fault Management Function: support of:
• failure detection in the LSA System;
• subsequent generation and delivery of respective failure notification(s) to LSA Licensee(s) and Incumbent(s);
• initiation of respective operations in the LSA System.
4.4.7 System Management Functions Group
This includes:
• Operation, administration and maintenance tasks in the LSA System.
• Identity management (comprising user identity and authentication management, and user authorization
profiles).
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 235 V1.1.1 (2015-10)
System management is separate for LR and LC since these logical entities belong to different operation domains. The
supported functionality may also be different in the two entities. Identity management applies to the LR only.
4.5 Mapping of High Level Functions to Logical Elements
Figure 4.2 shows how the high level functions and function groups are mapped to the logical entities LR and LC.
LSA Repository LSA Controller
Reporting
Information LSA Information Information
Information Entry
Processing
Exchange Mapping
System Support (Security Support, Robustness and Reliability, Fault Management)
LR System LC System
Management Management
(OAM, Identity Management)
(OAM)

Figure 4.2: Mapping of high level functions and function groups to logical elements
The System Support functions group may be considered to map across all elements and reference points of the LSA
System.
The corresponding functionality at the LSA reference point is covered by the LSA Information Exchange function and
1
the System Support functions group.
5 LSA Functional Description and Information Flows
1
5.1 Introduction
This clause describes procedures, procedural flows and additional functional aspects related to the interface between LR
and LC (LSA interface).
1
The LSA interface provides support for the exchange of LSA Spectrum Resource Availability Information (LSRAI,
1
clause 5.4.2) and respective acknowledgement information between LR and LC, and for maintaining and recovering
synchronization of such information between LR and LC.
5.2 Protocol Stacks
The LSA application layer protocol shall ensure the application part, in LR and LC, conforms to the regulatory
1
requirements, thereby the requirements on underlying transport protocols are kept to minimum. Supported network
layer protocol is IP [i.4]. No LSA specific requirement is set on the transport layer protocol.
NOTE: Supported Transport layer mechanisms include TCP and UDP. Depending on the security requirements,
use of IPsec, TLS or DTLS may be applicable.
5.3 LSA Interface Management Functions
1
The LSA Interface shall provide Management functions and corresponding procedures to ensure means for a defined
1
start of interface operation and means to identify application or protocol failure.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 235 V1.1.1 (2015-10)
The node that initiates a particular procedure is responsible for supervising the overall procedure status and detecting
corresponding failures. In case of failure (e.g. the respective response message is not received, or the response message
is not valid), the action taken is unspecified and left for implementation. A typical behaviour would be to re-initiate the
procedure a number of times, before further recovery action is invoked.
If failures occur during procedures concerned with exchange of LSRAI, the supervising node may consider that LSRAI
synchronization has been lost between LC and LR, and should initiate actions to restore LSRAI synchronization. The
protocol should ensure that LSRAI is consistent in both nodes.
5.4 LSA Protocol Elements
1
5.4.1 Identities
The following defines identities that shall be employed by the LSA System in general, and particularly over the LSA
1
interface:
Licensee Identity: identifies a specific LSA Licensee.
LR Identity: identifies a specific LR.
LC Identity: identifies a specific LC.
Licensee Identity, LR Identity and LC Identity shall be unique and unambiguous within a particular set of
interconnected LSA network elements (for example, multiple LCs of the same or different LSA Licensee(s) connected
to one LR).
Transaction Identity: identifies a specific instance of a procedure, and all messages within the same procedure
instance shall include the same Transaction Identity. The node initiating the procedure shall assign a Transaction
Identity which is not currently used by any other procedure initiated by the same node.
5.4.2 LSA Spectrum Resource Availability Information
The LSA Spectrum Resource Availability Information (LSRAI) is conveyed to the LC in messages originated in the LR
(e.g. LSRAI Notification message, see clause 5.5.5).
Under normal operating conditions, the LR is aware of the LSRAI that is known to the LC, and
...