hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7 GBLS Architecture (Level 3) | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.1 Level 3 detailed architecture | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.1.1 Generic GBLS | Figure 7-1 shows the detailed (Level 3) architecture, which is derived from the Level 2 architecture in clause 6.1. Target Positioning Module Data Exchange with external Service Provider I/F 8 Central Facility Data Exchange with external Service Provider Position Calculation Module Mandatory Optional Sensor Management ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2 Functional Block Definitions | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.1 List of functional blocks | The following clauses define the functions that shall be provided by each block of Figure 7-1. ETSI ETSI TS 103 246-2 V1.3.1 (2020-10) 24 The architecture in Figure 7-1 comprises the following functional blocks: • GNSS sensor; • Telecommunication module; • Inertial Sensor; • Magnetometer; • Odometer/tachometer; • Beam ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.2 GNSS Sensor | The GNSS sensor is a mandatory component of the GBLS architecture, and shall be on-board the Positioning module of the location target. It determines the position of the location target by processing signals transmitted from space-based GNSS satellites at precisely known locations. Specific GNSS authentication function... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.3 Telecommunication Module | The Telecommunication module is an optional component of the Positioning module of the GBLS architecture. It determines the position of the location target by processing signals transmitted from terrestrial radio beacons (i.e. anchor nodes such as bases stations or WIFI access point) at fixed and precisely known locati... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.4 Inertial Sensor | The Inertial Measurement Unit (IMU) is an optional component of the Positioning module of the GBLS architecture. It contains a set of as many as three orthogonally-installed accelerometers and/or as many as three orthogonally-installed gyroscopes to provide measurements of the acceleration and the angular change on thr... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.5 Magnetometer | The Magnetometer is an optional component of the Positioning module of the GBLS architecture. It is used to measure the magnetic flux on as many as three axes that may be used to estimate the horizontal and vertical orientation of the location target. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.6 Odometer | The Odometer is an optional component of the Positioning module of the GBLS architecture. It is used to measure the distance travelled by the location target in a predefined time window. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.7 Beam Forming Antenna | The Beam Forming Antenna is an optional component of the Positioning module of the GBLS architecture. It includes signal-processing techniques able to combine streams of samples from n different elements of an antenna array. The Beam Forming Antenna is used to steer the antenna beam pattern to the transmitting sources ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.8 EMI Mitigation | The EMI mitigation algorithm (EMA) is an optional component of the GBLS architecture. It is in charge of detecting and mitigating RF interfering signals that can be present over bandwidths allocated to GNSS. The EMI mitigation algorithm includes an interference detector that enables the mitigation functions. The EMI mi... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.9 EMI Location | The Electro Magnetic Interference (EMI) location algorithm is an optional component of the GBLS architecture. The presence of interfering sources (whether intentional or not) can degrade the GBLS performance. The EMI location algorithm is responsible for determining the location-related data of RF interfering sources, ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.10 Location Hybridization Algorithm | The Location Hybridization Algorithm (LHA) is an optional component of the GBLS architecture. It is one of the algorithms responsible for determining the location-related data of a location target. It is specifically in charge of the processing required in the case that the location targets are not interference sources... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.11 Integrity Building Algorithm | The Integrity Building Algorithm (IBA) is an optional component of the GBLS architecture. It is one of the algorithms in charge of executing the processing required to determine the location-related data of a location target. It is specifically in charge of the processing required in case a reliable quality of service ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.12 PPP Module | The PPP Module is an optional component of the GBLS architecture. It provides precise estimates of the PVT by implementing algorithms able to mitigate most of the errors affecting GNSS positioning These errors include: • The space segment (i.e. receiver clock offset, satellite antenna phase centre offsets). • The signa... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.13 D-GNSS/RTK processing module | The RTK/D-GNSS is an optional component of the GBLS architecture. This component includes algorithms in charge of: • Applying differential corrections on sets of measurements (i.e. pseudoranges) generated by the GNSS sensor. Differential corrections sent by different augmentation systems can be received through the App... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.14 Location Authentication | The Location Authentication is an optional component of the GBLS architecture. It includes algorithms in charge of authenticating the position computed by the location target. The authentication may be based on specific processing of the received GNSS signals and involves the detection, and possibly the mitigation, of ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.15 Security Provisioning | Security Provisioning is an optional block within the system architecture. It is provided to allow devices to register their credentials to act as measurement or reference sources. The provisioning process allows for later security verification. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.16 Security Verification | Security Verification is an optional block within the system architecture. It is used to establish that the measurement source is a trusted, secure source. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.17 Privacy Provisioning | Privacy provisioning is an optional block within the system architecture. It is provided to allow a location target to register its privacy profile. This privacy profile will be consulted by the Application to direct the location process. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.18 Privacy Test | The privacy test is an optional block within the system architecture. It consults the provisioning data of the location target to determine if the requesting entity should be granted access to the location of the target. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.19 Application Interface Module | This is the interface that external applications use to exchange location requests and responses with the positioning system. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.20 Reference Receivers | The Reference Receivers are optional components of the GBLS architecture. They are GNSS sensors in charge of processing GNSS signals at the Central Facility, in a fixed and precisely known location. Reference Receivers provide measurements post correlation (e.g. code and carrier phase measurements, Doppler, C/No estima... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.21 Assistance server | The Assistance server is an optional component of the Central Facility of the GBLS architecture. It implements at least one of the following functions: • Provision of A-GNSS data (assistance data as defined in ETSI TS 103 246-4 [i.2]). • Provision of multi-lateration/Triangulation assistance data. This is applicable in... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.22 Map database | The Map database (MD) is an optional component of GBLS architecture. It contains the digital map database with the graphical representation of all the spatial information required for route guidance. It is based on: • single-line-road-network representing the centreline of the road; and a detailed description of the ro... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.23 Real Time Clock (RTC) | The Real time Clock (RTC) is an optional component of the GBLS architecture. It is essentially a crystal-oscillator clock with a backup battery allowing the propagation of current time even if the GBLS is switched off. Some authentication algorithms need an independent time source providing loose time synchronization t... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 7.2.24 Key Storage and Management (KSM) | The Key Storage is an optional component of the GBLS architecture. It is essentially a non volatile memory with key storage and, optionally, management capabilities. Depending on the type of application, it can require secure storage, tamper-proof and automatic wiping functions (in case physical tampering is detected).... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for conformance test specifications for the IPv6 transition technology NAT64 as defined in ETSI TS 101 569-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-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. Refe... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 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 in... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 3 Definitions and abbreviations | |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [1], ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [3] apply. In particular, the following terms given in ISO/IEC 9646-1 [2] apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or sy... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ALG Application Layer Gateway ATS Abstract Test Suite FTP File Transfer Protocol GRT Global Routing Table GW Gateway ICMP Internet Control Message Protocol IP Internet Protocol IPv4 IP version 4 IPv6 IP version 6 IUT Implementation Under Test ... |
f03901aa825c85a1813c6a1d19df71a4 | 103 238-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and ordering of the proforma items. An ICS which conforms to the present document shall be a ... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for 6rd technology as defined in RFC 5969 [1] and RFC 5569 [2] which address specific cable industry requirements as defined in ETSI TS 101 569-1 [10] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 2 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 ar... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 5969: "IPv6 Rapid Deployment on IPv4 infrastructures - 6rd - Protocol Specification". [2] IETF RFC 5569: "IPv6 Rapid Deployment on IPv4 infrastructures - 6rd". [3] ISO/IEC 9646-1 (1994): "Information technology - ... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 2.2 Informative references | 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 EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 3 Definitions and abbreviations | |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [10], ISO/IEC 9646-1 [3] and ISO/IEC 9646-7 [6] apply. |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply. 3GPP Third Generation Partnership Project 6rd IPv6 Rapid Deployment ALG Application Layer Gateway ASP Abstract Service Primitives ATM Abstract Test Method ATS Abstract Test Suite BR Border Router CE Customer Edge router CPE Customer Premises E... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4 Abstract test method | This clause describes the ATM used to test the 6rd technology. |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.1 Abstract protocol tester | An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation of communication which is equivalent to real operation between real devi... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.2 Test configurations | The test suite for 6rd uses two test configurations to cover the different test scenarios. Distinction between the two configurations is given by the two main components in 6rd, which are the Customer Edge router (CE), also referred to as a Customer Premises Equipment (CPE) and Border Relay router (BR). |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.2.1 CF01: CPE as IUT | In this configuration, the CPE is the IUT and the test system simulates a 6rd BR in one side and a IPv6 host in the other side. CPE - IUT Test system (TTCN-3) IPv6 Host - Simulated 6rd BR - Simulated Figure 3: CF01, CPE device is the IUT ETSI ETSI TS 103 243-3 V1.1.1 (2014-12) 10 |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.2.2 CF02: BR as IUT | In this configuration, the BR is the IUT and the test system simulates a 6rd CPE in one side and a IPv6 server in the other side. BR - IUT Test system (TTCN-3) IPv6 server - Simulated 6rd CPE - Simulated Figure 4: CF01, BR device is the IUT |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.3 TTCN-3 Test architecture | In general, a conformance test system architecture based on TTCN-3 is as figure 5 shows. 6rd Test System Test control 6rd Abstract Test Suite Codec Test adaptor Upper tester transport 6rd lower Layers SUT Upper tester application 6rd IUT 6rd lower Layers Upper tester transport Upper tester transport link Lower layer tr... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.4.1 TTCN-3 ports | The 6rd Test Suite implements the following ports: • Ipv6Port, to send and receive IPv6 packets. • Ipv4Port, to send and receive IPv4 packets. • Dhcpv6Port, to send and receive DHCPv6 messages. • HttpPort, to trigger the following HTTP actions: data sending (both IPv4 and IPv6). It can monitor incoming traffic. • UtPor... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 4.4.2 Abstract Service Primitives | Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain behaviour or to obtain information about the IUT state. The list of ASP used in the 6rd ATS is shown in table 1. Table 1: 6rd Abstract Service Primitives TTCN-3 text Action/Command Description Is Gateway... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 5 Implemented Test Purposes | Table 2 shows the test purposes from [9] which have been implemented and included in the present document. Table 2: Implemented Test Purposes TP Identifier TC Identifier Group Subgroup PICS Unt esta ble Implemented TP/6RD/CPE/GWA/BV/01 TC_6RD_CPE_GWA_BV_01 CPE Gateway Assignment PICS_ROLE_IS_CPE Yes TP/6RD/ CPE/BF/BV/0... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6 ATS conventions | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.1 Naming conventions | This test suite follows the naming convention guidelines provided in [7] and [i.1]. |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.1.1 General guidelines | The naming convention is based on the following underlying principles: • Identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents. • Suffixes should not be used except in those specific cases identified in table 3. • Prefixes and suffixes s... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.1.2 6rd specific TTCN-3 naming conventions | In addition to such general naming conventions, table 4 shows specific naming conventions that apply to the 6rd technology TTCN-3 test suite. Table 4: 6rd specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier 6rd Module Use upper-case initial letter Ats6RD_ Ats6RD_ Module conta... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.1.3 Usage of Log statements | All TTCN-3 log statements use the following format: • Three asterisks followed by a blank character. • The TTCN-3 test case or function identifier in which the log statement is defined followed by a colon and a blank character. • One of the log categories: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT followed by a... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.1.4 Test Case (TC) identifier | The identifier of the TC is built according to table 5 as recommended in [7]. Table 5: TC naming convention for 6rd TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root 6RD 6rd <gr> = group CPE CPE as IUT BR BR as IUT <sgr> = sub-group GWA Gateway Assignment BF Basic Function FRAG Fragmentation ALG Application Layer Gateway MSS... |
9fa6ce79a3332483dbf89ada8226c56d | 103 243-3 | 6.2 On line documentation | Using the T3D tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in table 6. Table 6: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 2 References | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 ar... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 in... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 3 Definitions and abbreviations | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd 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 Controll... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 4 Architecture Model | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 ETSI TS 103 235 V1.1.1 (2015-10) 8 Figure... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 Control... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 4.3 Reference Points | LSA1: Reference point between LR and LC. LSA2: Reference point for Administration/NRA interaction with the LR. Some of the functionality associated with this reference point is described in annex B. LSA3: Reference point for Incumbent interaction with the LR. Some of the functionality associated with this reference poi... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 4.4 High Level Functions | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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]. |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 operati... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 dat... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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. |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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. |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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. Fa... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 ETSI TS 103 235 V1.1.1 (2015-10) 10 System management is separate for LR and LC since these logical entities belong to... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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. 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 ... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5 LSA1 Functional Description and Information Flows | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.1 Introduction | This clause describes procedures, procedural flows and additional functional aspects related to the interface between LR and LC (LSA1 interface). The LSA1 interface provides support for the exchange of LSA Spectrum Resource Availability Information (LSRAI, clause 5.4.2) and respective acknowledgement information betwee... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.2 Protocol Stacks | The LSA1 application layer protocol shall ensure the application part, in LR and LC, conforms to the regulatory 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. ... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.3 LSA1 Interface Management Functions | The LSA1 Interface shall provide Management functions and corresponding procedures to ensure means for a defined start of interface operation and means to identify application or protocol failure. Information Mapping LSA Repository Information Processing LSA Information Exchange Reporting Information Entry LC System Ma... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.4 LSA1 Protocol Elements | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.4.1 Identities | The following defines identities that shall be employed by the LSA System in general, and particularly over the LSA1 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 uni... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 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 stores relevant associated information such as status of LC ... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5 High Level Procedures | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.1 Introduction | This clause specifies high level procedures which describe the interaction between LR and LC in normal operation. Some procedures imply the reconfiguration of the LSA Licensee's network through the interaction between the LSA System and the MFCN. These procedures, how they apply and the related lead, latency and respon... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.2 Registration Procedure | The purpose of the registration procedure is to register an LC with an LR. This is the first procedure executed on the LSA1 interface. After successful completion of this procedure, the LC is able to initiate requests or receive notifications on spectrum resource availability information. Figure 5.1: Registration Proce... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.3 Deregistration Procedure | The purpose of the LC-initiated Deregistration procedure is to allow an LC to deregister with an LR. After successful completion of this procedure, the LC can close its connectivity with LR. To re-establish the dialogue with LR, LC shall proceed with a Registration Procedure (clause 5.5.2). Figure 5.2: Deregistration P... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.4 LSRAI Request Procedure | The purpose of the LSRAI Request procedure is to enable the LC to request LSA spectrum resource availability information. The procedure is used to synchronize LSRAI between LR and LC. Figure 5.3: LSRAI Request Procedure 1) The LC sends an LSRAI Request message to the LR. 2) The LR checks the consistency of the LC's req... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.5 LSRAI Notification Procedure | The purpose of the LSRAI Notification procedure is to enable the LR to send LSA spectrum resource availability information to the LC. It can be used to send either specific immediate notifications or periodic updates to the LC. Figure 5.4: LSRAI Notification Procedure 1) The LR sends an LSRAI Notification message to th... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.6 LSRAI Confirmation Procedure | The purpose of the LSRAI Confirmation Procedure is for the LC to notify the LR once the necessary configuration changes in the MFCN have been applied according to the LSA spectrum resource availability information provided by the LR. Figure 5.5: LSRAI Confirmation Procedure 1) The LC sends a LSRAI Confirmation Request ... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.5.8 Connectivity Check Request Procedure | The LC-initiated Connectivity Check procedure allows the LC to test the connectivity with the LR. The procedure can be invoked at any time after Registration Procedure and throughout the lifetime of the LC registration, and on specific events and/or on periodic basis. However the LC may take into account previous succe... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.6 Procedure Flows | |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.6.1 Introduction | This clause describes procedure flows that shall be supported by the LSA1 application protocol. Each flow may be composed of several procedures, and provides support for a particular operational activity (e.g. LC start-up). Additional flows (and respective operational activities) may be supported by the protocol. The p... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.6.2 LC Operation Start-up | This message flow shall be used during LC start-up, and provides the LSA1 support for the use case A.3 (see annex A). At the end of the flow, the LC has the necessary LSRAI, and the LR will have received confirmation that relevant changes have been executed. ETSI ETSI TS 103 235 V1.1.1 (2015-10) 16 Figure 5.8: LC Opera... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.6.3 LR Notification of new LSRAI | When the LR becomes aware of new LSRAI, it may decide to notify immediately the LC using this procedure flow. This flow may happen at any time following completion of the Registration procedure. Figure 5.9: LR Notification of new LSRAI procedure flow 1) The LR initiates the LSRAI Notification procedure, to inform the L... |
8789abb2c1e018137f99c7c5f13445c3 | 103 235 | 5.6.4 LSRAI Synchronization | This procedure flow is used to synchronize the LSRAI of LR and LC. Either LC or LR may consider the possibility that the LSRAI is no longer synchronized. To solve or avoid loss of synchronization, LC or LR can initiate LSRAI synchronization at any time. At the end of the flow, the LC has the necessary LSRAI, and the LR... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.