hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
74588378d2df7cfc62503d6045995846 | 103 652-2 | 4.3.7 System Management Functions Group | This includes: • Operation, administration and maintenance tasks in the eLSA System. • Identity management (comprising user identity and authentication management, and user authorization profiles). System management is separate for eLR and eLC since these logical entities belong to different operation domains. The supp... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 4.4 Mapping of High-Level Functions to Logical Elements | Figure 3 shows how the high-level functions and function groups are mapped to the logical entities eLR and eLC. Figure 3: 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 eLSA System. The c... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5 eLSA1 Functional Description and Information Flows | |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.1 Introduction | This clause describes procedures, procedural flows and additional functional aspects related to the interface between eLR and eLC (eLSA1 interface). The eLSA1 interface provides support for the exchange of eLSA Spectrum Resource Availability Information (eLSRAI, clause 5.4.2) and respective acknowledgement information ... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.2 Protocol Stacks | The eLSA1 application layer protocol shall ensure the application part, in eLR and eLC, conforms to the regulatory requirements, thereby the requirements on underlying transport protocols are kept to minimum. Supported network layer protocol is IP. No eLSA specific requirement is set on the transport layer protocol. NO... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.3 eLSA1 Interface Management Functions | The eLSA1 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. The node that initiates a particular procedure is responsible for supervising the overall procedure status and detecting c... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.4 eLSA1 Protocol Elements | |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.4.1 Identities | The following defines identities that shall be employed by the eLSA System in general, and particularly over the eLSA1 interface: • VSP Identity: identifies a specific VSP. • eLR Identity: identifies a specific eLR. • eLC Identity: identifies a specific eLC. VSP Identity, eLR Identity and eLC Identity shall be unique a... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.4.2 eLSA Spectrum Resource Availability Information | The eLSA Spectrum Resource Availability Information (eLSRAI) is conveyed to the eLC in messages originated in the eLR (e.g. eLSRAI Notification message, see clause 5.5.5). ETSI ETSI TS 103 652-2 V1.1.1 (2020-01) 13 Under normal operating conditions, the eLR is aware of the eLSRAI that is known to the eLC, and stores re... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5 High Level Procedures | |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.1 Introduction | This clause specifies high level procedures which describe the interaction between eLR and eLC in normal operation. Some procedures imply the reconfiguration of the VSP's network through the interaction between the eLSA System and the MFCN. These procedures, how they apply, and the related lead, latency and response ti... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.2 Registration Procedure | The purpose of the registration procedure is to register an eLC with an eLR. This is the first procedure executed on the eLSA1 interface. After successful completion of this procedure, the eLC is able to initiate requests or receive notifications on eLSRAI. ETSI ETSI TS 103 652-2 V1.1.1 (2020-01) 14 Figure 4: Registrat... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.3 Deregistration Procedure | The purpose of the eLC-initiated Deregistration procedure is to allow an eLC to deregister with an eLR. After successful completion of this procedure, the eLC can close its connectivity with eLR. To re-establish the dialogue with eLR, eLC shall proceed with a Registration Procedure (see clause 5.5.2). Figure 5: Deregis... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.4 eLSR Grant Procedure | The purpose of the eLSR Grant procedure is to enable the eLC to request a grant for an eLSR. The grant is provided as eLSRAI containing Allowance Zone information. The procedure is used to synchronize eLSRAI between eLR and eLC for the eLSA supported spectrum access schemes. Figure 6: eLSR Grant Procedure 1) The eLC se... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.5 eLSR Grant Relinquishment Procedure | The purpose of the eLSR Grant Relinquishment procedure is to enable the eLC to relinquish grants for eLSR. The procedure is used to release a granted eLSR before the grant time expires. ETSI ETSI TS 103 652-2 V1.1.1 (2020-01) 16 Figure 7: eLSR Grant Relinquishment Request Procedure 1) The eLC sends an eLSR Grant Relinq... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.6 eLSRAI Request Procedure | The purpose of the eLSRAI Request procedure is to enable the eLC to request an eLSRAI. The procedure is used to synchronize eLSRAI between eLR and eLC. Figure 8: eLSRAI Request Procedure 1) The eLC sends an eLSRAI Request message to the eLR. 2) The eLR checks the consistency of the eLC request and builds the relevant e... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.7 eLSRAI Notification Procedure | The purpose of the eLSRAI Notification procedure is to enable the eLR to send eLSRAI to the eLC. It can be used to send either specific immediate notifications or periodic updates to the eLC. Figure 9: eLSRAI Notification Procedure 1) The eLR sends an eLSRAI Notification message to the eLC containing eLSRAI. The eLSRAI... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.8 eLSRAI Confirmation Procedure | The purpose of the eLSRAI Confirmation Procedure is for the eLC to notify the eLR once the necessary configuration changes in the MFCN have been applied according to the eLSRAI provided by the eLR. Figure 10: eLSRAI Confirmation Request Procedure ETSI ETSI TS 103 652-2 V1.1.1 (2020-01) 18 1) The eLC sends an eLSRAI Con... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.9 Connectivity Check Notification Procedure | The eLR-initiated Connectivity Check procedure allows the eLR to test the connectivity with any registered eLC. The procedure can be invoked at any time after Registration Procedure and throughout the lifetime of the eLC registration, and on specific events and/or on periodic basis. However, the eLR may take into accou... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.5.10 Connectivity Check Request Procedure | The eLC-initiated Connectivity Check procedure allows the eLC to test the connectivity with the eLR. The procedure can be invoked at any time after Registration Procedure and throughout the lifetime of the eLC registration, and on specific events and/or on periodic basis. However, the eLC may take into account previous... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6 Procedure Flows | |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.1 Introduction | This clause describes procedure flows that shall be supported by the eLSA1 application protocol. Each flow may be composed of several procedures, and provides support for a particular operational activity (e.g. eLC start-up with dedicated eLSR or variable eLSR). Additional flows (and respective operational activities) ... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.2 eLC Operation Start-up for granted eLSR | This message flow shall be used during eLC start-up when eLSR are dedicated (e.g. eLSA Licensing), and provides the eLSA1 support for the use case A.3 (see annex A). At the end of the flow, the eLC has the necessary eLSRAI, and the eLR will have received confirmation that relevant changes have been executed. ETSI ETSI ... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.3 eLC Operation Start-up for non-granted eLSR | This message flow shall be used during eLC start-up when eLSR needs to be granted before operation per request, and provides the eLSA1 support for the use case A.3 (see annex A). At the end of the flow, the eLC has the necessary eLSRAI, and the eLR will have received confirmation that relevant changes have been execute... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.4 eLR Notification of new eLSRAI | When eLSR is granted and the eLR becomes aware of new eLSRAI, it may decide to notify immediately the eLC using this procedure flow. This flow may happen at any time following completion of the Registration procedure. ETSI ETSI TS 103 652-2 V1.1.1 (2020-01) 22 Figure 15: eLR Notification of new eLSRAI procedure flow 1)... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.5 eLSRAI Synchronization | This procedure flow is used to synchronize the eLSRAI of eLR and eLC. Either eLC or eLR may consider the possibility that the eLSRAI is no longer synchronized. To solve or avoid loss of synchronization, eLC or eLR can initiate eLSRAI synchronization at any time. At the end of the flow, the eLC has the necessary eLSRAI,... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 5.6.6 eLC Request for new eLSRAI with optional eLR Notification | This procedure flow is used when the eLC requests the eLR to send it new eLSRAI. Optionally, the procedure flow enables the eLR to receive an acknowledgement from the eLC upon reception of the new eLSRAI. The acknowledgement may allow informing the Incumbent that the VSP has received the new eLSRAI (e.g. changed protec... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 6 eLSA Failure Management | Failures may originate due to hardware or software problems at the eLC, eLR or eLSA1 interface. The eLSA failure management provides respective functions to guarantee the Incumbent and the VSP protections even in case that eLC, eLR, or eLSA1 interface is out of operation. Failures may occur either during the eLSA syste... |
74588378d2df7cfc62503d6045995846 | 103 652-2 | 7 eLSA Deployment Scenario Rules | eLSA deployments may comprise multiple physical eLSA Repositories and/or eLSA Controllers (motivated by practical requirements such as extended reliability concepts, private repositories at Incumbents side, performance extensions, support of eLC outside of the VSP domain based on business agreements, or the parallel us... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 1 Scope | The objective of evolving the LSA framework towards an eLSA (evolved LSA) system is to support spectrum access to local high-quality wireless networks operated by vertical sector operators, as introduced in ETSI TR 103 588 [i.1]. The present document specifies system requirements for that purpose. ETSI TC RRS work on e... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 2 References | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 3 Definition of terms, symbols and abbreviations | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: allowance zone: geographical area within which an eLSA Licensee is allowed to operate radio transmitters on its assigned spectrum resource NOTE 1: An allowance zone is defined using specific measurement quantities and thresholds, e.g. a maximum field ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 3.2 Symbols | Void. |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CEPT Conférence Européenne des administrations des Postes et des Télécommunications ECC Electronic Communications Committee of the CEPT EIRP Effective Isotropic Radiated Power eLSA evolved LSA IMT International Mobile Telecommunications LSA Li... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 4 Requirement organization and methodology | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 4.1 Requirement organization | This clause contains a description of how the requirements are organized. As shown in Figure 1, the requirements described in the present document belong to the category of functional requirements. This category, in turn, is organized into groups. ETSI ETSI TS 103 652-1 V1.1.1 (2019-02) 10 Figure 1: Organization of fun... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 4.2 Requirement format | This clause describes the format of the requirements. A letter code system is defined which makes a unique identification of each requirement R-<CAT>-<GROUP>-<XX>. It should be constructed as follows: • R-: Standard requirement prefix • <CAT>: Code Category FUNC Functional aspects • <GROUP>: Requirement group identifie... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 4.3 Requirement formulation | A requirement is formulated in such a way that it is uniquely defined. It is built as follows: • Title: <Title Description> • Description: the description of a requirement will be formulated using the ETSI modal verbal terminology |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 4.4 eLSA Roles | Requirements are formulated in regards of the "eLSA System" and make use of generic "eLSA roles". "eLSA roles" are based on "LSA roles" as introduced in ECC Report 205 [i.5]. eLSA Licensee role includes the lease/sub-lease case and extends the scope to vertical sectors stakeholders. Functional requirements category (FU... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5 Working Assumptions | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.1 General Assumptions | The working assumptions described below are based on ETSI TR 103 588 [i.1], and particularly on the three functional use cases described in clause 6.1 and summarized in Table 5 of ETSI TR 103 588 [i.1], as well as on the current ETSI LSA framework [i.2], [i.3], [i.4] and the ECC Report 205 [i.5]. For eLSA, the followin... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.2 Operation of local high-quality wireless networks | Local high-quality wireless networks refer to MFCNs capable of supporting different use cases with following commons: • their operation is confined in a local geographical area: - the definition of a local geographical area is assumed to be based on premises, real estate, address or similar notion. Having a precise are... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.3 Regulatory background | The current ETSI LSA framework [i.2], [i.3], [i.4] provides a solution to enable spectrum access to the 2 300 MHz - 2 400 MHz frequency band for MFCNs acting as MNOs. At this stage, eLSA does not target specific radio bands but aims to provide a general solution for providing spectrum access to local high-quality wirel... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.4 Sharing Framework | The Sharing Framework remains the central piece for the implementation of eLSA at national level. It defines for a given frequency band the spectrum, with corresponding technical and operational conditions, that can be made available for eLSA. For eLSA it is intended to provide technical solutions enabling at least fol... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.5 Spectrum Sharing Arrangement | The spectrum sharing arrangement concept for eLSA is based on the spectrum sharing arrangement concept for LSA in ETSI TS 103 154 [i.2] and will contain additional features to deal with the new aspects for providing spectrum access to local high-quality wireless networks. For example, if the Sharing Framework and the s... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.6 eLSA functional enhancements | For providing spectrum access to local high-quality wireless networks, the current LSA framework needs to be evolve on system level. Table 6 in ETSI TR 103 588 [i.1] lists an overview of identified potential functional enhancements to the current LSA system and the corresponding affected LSA entities. It is assumed tha... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 5.7 eLSA system administration by trusted 3rd parties | It is assumed that the eLSA System or part(s) thereof may be administered by trusted 3rd party user(s) with defined access rights. The new aspect for eLSA is that a eLSA Controller may be operated by a 3rd party user, which acts on behalf of eLSA Licensees operating a local MFCN. |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6 Functional system requirements | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1 General system operation | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.0 Introduction | This clause comprises functional requirements that relate to the general system operation. |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.1 R-FUNC-GEN-01 eLSA spectrum resource sharing | The eLSA system shall support: • spectrum resource sharing in suitable licensed bands between Incumbent(s) and eLSA, according to the applicable Sharing Framework automatic local area licensing of spectrum resources in suitable licensed bands to eLSA Licensees, even if no Incumbent is present in the band; • leasing of ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.2 R-FUNC-GEN-02 Quality of service | The eLSA System shall facilitate the provision of a predictable Quality of Service (QoS) for both Incumbents and eLSA. Licensees, whenever operation by a particular service is allowed by the system. Explanation: The eLSA System supports sharing on a non-interfering basis, meaning that the sharing systems will operate w... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.3 R-FUNC-GEN-03 Information exchange between eLSA roles | The eLSA System shall provide means for the exchange of information between different roles, e.g. between an Incumbent and/or NRA and an eLSA Licensee to enable the eLSA Licensee to be made aware of the eLSA spectrum resource that is available for its use and its possible changes over time. If the Sharing Framework and... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.4 R-FUNC-GEN-04 Multiple eLSA Licensee/Lessee support | The eLSA System shall allow an Incumbent, NRA or lessor to interact with one or more eLSA Licensees/Lessees for spectrum sharing purposes. Explanation: A single Incumbent user may communicate with multiple MFCNs to provide information on the eLSA spectrum resource available to each. For example, an Incumbent may have u... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.5 R-FUNC-GEN-05 Multiple Incumbent user support | The eLSA System shall allow an MFCN to interact with one or more Incumbents, lessors and/or one NRA for spectrum sharing purposes. NOTE: An MFCN should be able to interact directly with the NRA in frequency bands where there is no incumbent. Explanation: A particular MFCN may be authorized as an eLSA Licensee of differ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.6 R-FUNC-GEN-06 Sharing framework support | The eLSA System shall support the use of a Sharing Framework as defined on national level. Explanation: The Sharing Framework is described in the working assumptions (clause 5.4). ETSI ETSI TS 103 652-1 V1.1.1 (2019-02) 15 |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.7 R-FUNC-GEN-07 Confidentiality of spectrum resource information | The eLSA System shall support mechanisms to ensure that, for a particular Sharing Framework, the information on the associated available eLSA spectrum resource may only be accessed by the concerned Incumbent and/or NRA and eLSA Licensee. Information about the frequency allocations of neighbour licenses could be useful ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.8 R-FUNC-GEN-08 Provision of failure indication | The eLSA System shall have means to provide failure indications to both the eLSA Licensee and the Incumbent, following the detection of any critical system failure that may result in harmful interference. Explanation: Under some circumstances, failures may occur which prevent normal operation of the eLSA System. A simp... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.9 R-FUNC-GEN-09 eLSA system data storage function | The eLSA System shall support the entry, storage and modification of information required for eLSA operation. Explanation: The eLSA System supports receiving and maintaining information required for the operation of eLSA, including eLSA spectrum resource definitions, sharing rule definitions (from the Sharing Framework... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.10 R-FUNC-GEN-10 eLSA system reporting function | The eLSA System shall support the capability to generate reports on eLSA operation, covering as a minimum the availability of eLSA spectrum resource through eLSA operation, and the occurrence of critical events such as eLSA spectrum resource evacuation. Such reports may be provided on-demand, or according to a schedule... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.11 R-FUNC-GEN-11 Support of scheduled operation | The eLSA System shall support a scheduled mode of operation for spectrum resource sharing. Explanation: In this mode of operation, the eLSA spectrum resource availability information changes at pre-set times according to a schedule. For example, the schedule may be part of the sharing rules, or it could be entered by t... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.12 R-FUNC-GEN-12 Support of on-demand operation | The eLSA System shall support an on-demand mode of operation for spectrum resource sharing only if the frequency allocation of the license requires such an operation due to incumbent use. In general, an on-demand operation mode is not desired for providing spectrum access to MFCNs as described in ETSI TR 103 588 [i.1].... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.13 R-FUNC-GEN-13 Support of pre-configuration | The eLSA System shall support the pre-configuration of the Incumbent's eLSA spectrum resource usage and protection requirements (and associated eLSA spectrum resource availability information), such that there will be a finite set of possible combinations of such requirements. Such pre-configuration may apply to the en... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.14 R-FUNC-GEN-14 Verification of inputs to the eLSA system | The eLSA System shall support the capability to verify the consistency and validity of its inputs, and in particular, it shall be able to: • reject a requested change in the Incumbent's eLSA spectrum resource usage and protection requirements, if it fails to meet a specific condition (e.g. within the Sharing Framework,... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.15 R-FUNC-GEN-15 eLSA system availability to stakeholders | The eLSA System shall incorporate mechanisms to maintain robustness against failures and malicious attacks such that the spectrum sharing arrangement between an Incumbent and an eLSA Licensee can be fulfilled by the eLSA system with a predictable level of certainty in its availability to stakeholders. Explanation: The ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.1.17 R-FUNC-GEN-17 Support of allowance zones | The eLSA System shall support allowance zones as described in clause 5.6. Explanation: It is assumed that eLSA spectrum resource sharing for vertical sector players is based on geographical sharing, i.e. the individual right of use, the Sharing Framework, and/or a particular spectrum sharing arrangement defines an allo... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.2 Incumbent protection requirements | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.2.0 Introduction | This clause comprises functional requirements that relate to the protection of the Incumbent. |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.2.1 R-FUNC-INC-01 Protection of information of the Incumbent | The eLSA System shall allow the Incumbent to store a description of the eLSA spectrum resource and its availability. This excludes any need to provide details on the network and actual usage of the eLSA spectrum resource not available to the eLSA Licensee. Explanation: Neither network details of the Incumbent (e.g. dep... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.2.2 R-FUNC-INC-02 General protection of the incumbent | The eLSA System shall support mechanisms to ensure that the Incumbent's eLSA spectrum resource usage and protection requirements are met, and in particular it shall provide eLSA spectrum resource availability information to the eLSA Licensee that will be such as to meet these requirements. Explanation: The eLSA System ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.3 Resource grant requirements | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.3.0 Introduction | This clause contains functional requirements that relate to the process of granting the use of eLSA spectrum resource to the eLSA Licensee. Note that the term "grant" refers here to the process of providing information to the Licensee regarding the available eLSA spectrum resource and is different from usage in a regul... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.3.1 R-FUNC-GRA-01 Protection of information of the eLSA Licensee | The eLSA System shall be able to derive and communicate the eLSA spectrum resource availability information to the appropriate eLSA Licensee, without knowledge of the information related to its MFCN, or related to its usage of the eLSA spectrum resource. Explanation: Information related to the MFCN is confidential data... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.3.3 R-FUNC-GRA-03 General protection of the eLSA Licensee | The eLSA System shall support mechanisms to ensure that the eLSA Licensee's protection requirements related to the eLSA spectrum resource are met, when and where the eLSA spectrum resource is available to the eLSA Licensee. Explanation: The eLSA System needs to ensure that the eLSA Licensee will not experience harmful ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.3.4 R-FUNC-GRA-04 Variation of eLSA Licensee's protection | The eLSA System shall support a modification of the eLSA Licensee's eLSA spectrum resource usage and protection requirements following a change in the spectrum sharing arrangement. Explanation: The spectrum sharing arrangement may contain an option to change practical details (e.g. this input is typically used to optim... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4 Security requirements | |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.0 Introduction | This clause contains functional requirements that relate specifically to security aspects of the eLSA System. |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.1 R-FUNC-SEC-01 Data integrity | The eLSA System shall incorporate mechanisms to ensure the integrity of the data stored in the system and the data exchanged between any of the eLSA System, Incumbents, eLSA Licensees and Administration/NRA. The eLSA System shall ensure the availability of the information to the authorized recipients and shall support ... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.2 R-FUNC-SEC-02 Data authenticity | The eLSA System shall incorporate mechanisms to ensure the authenticity of the information stored in the system and exchanged between any of the eLSA System, Incumbents, eLSA Licensees and Administration/NRA. Explanation: In contrast to integrity, which relates to the content of the information, the authenticity is con... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.3 R-FUNC-SEC-03 Data confidentiality | The eLSA System shall incorporate mechanisms to prevent unauthorized disclosure of confidential information that the system maintains and that is exchanged between any of the eLSA System, Incumbents, eLSA Licensees and Administration/NRA. Explanation: An eLSA System may support many Incumbents and eLSA Licensees and ma... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.4 R-FUNC-SEC-04 Identity management and authentication | The eLSA System shall allow to manage identities and authentication of users. This includes configuration, reconfiguration and deletion of identities. Explanation: In order to enforce the limitations of access rights and other security requirements, it is necessary to identify the users who access the system and to pro... |
15d47c62b50017ec5bb5c0958c8682e1 | 103 652-1 | 6.4.5 R-FUNC-SEC-05 Support of authorization profiles | The eLSA System shall distinguish between different authorization profiles assigned to user groups of the eLSA System based on their identification and shall allow the specification and enforcement of applicable access rights. Explanation: Different authorization profiles may be used to differentiate authorizations of ... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 1 Scope | The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Physical layer and interaction between PHY and MAC layer. |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 2 References | |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 3 Definition of terms, symbols and abbreviations | |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 3.1 Terms | Void. ETSI ETSI TS 103 636-3 V2.1.1 (2024-10) 7 Release 2 |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ∀ Mathematical notation for "for all" ⋀ Mathematical notation for "and" ⌊⌋ Mathematical notation for "floor of x" i.e. rounding towards zero ⌈⌉ Mathematical notation for "ceiling of x" i.e. rounding towards infinity Fourier transform scaling fac... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 636-1 [1] and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TS 103 636-1 [1]. ARQ Automatic Repeat reQuest BPSK Binary Phase Shift ... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4 Physical layer principles | |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4.1 General description of Physical layer | Figure 4.1-1: Radio interface protocol architecture around the Physical layer Figure 4.1-1 shows the DECT-2020 NR radio interface protocol architecture around the Physical layer (PHY). The physical layer interfaces the Medium Access Control (MAC) layer. The circles between different layer/sub-layers indicate Service Ac... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4.2 Multiple access | The multiple access scheme for the DECT-2020 NR physical layer is based on Time Division Duplex (TDD) combined with Frequency Division Multiple Access (FDMA) and Time Division Multiple Access (TDMA). The physical layer operates with non-overlapping channels in frequency domain and non-overlapping transmission slots in ... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4.3 Numerologies | In the present document, unless otherwise noted, the size of various fields in the time domain are expressed in terms of basic parameters. Subcarrier spacing is defined by the subcarrier scaling factor , resulting either in 27 kHz, 54 kHz, 108 kHz or 216 kHz OFDM subcarriers spacing Δ . In addition, the Fourier trans... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4.4 Frame structure | The radio frame has a duration of = 10 and consists of = 24 slots with a slot duration of = 0,41667 as depicted in Figure 4.4-1. ETSI ETSI TS 103 636-3 V2.1.1 (2024-10) 11 Release 2 Figure 4.4-1: DECT-2020 NR frame structure Each slot consists of , = 10, 20, 40 or 80 OFDM symbols dep... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 4.5 Physical resources | Physical resources are mapped to resource elements (, , ), where may denote either transmit stream or spatial stream index, denotes the subcarrier index and denotes the OFDM symbol position in the time domain relative to the start of the transmission packet as depicted in Figure 4.5-1. The occupied subcarriers i... |
079ec1062b1e3a23370df289fea6f113 | 103 636-3 | 5 Physical layer transmissions |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.