hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.1 Architecture Description | The overall system reference model is shown in figure 5.1. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 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 com... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.2 Functional Description of Components | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 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 protectin... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 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 u... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 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 sh... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 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... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 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 ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.2.6 Interface function | An interface function is an abstraction of the totality of those functional blocks realizing the reference points between a CRS and an SC, between an SC and a GLDB, between a CRS and a GLDB and between SCs. The reference model of the interface function is shown in figure 5.7. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 15 Fi... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.3 Reference Points | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.3.1 Reference point A: Between a GLDB and a CRS | Figure 5.8: Reference point A Reference point A is shown in figure 5.8. Reference point A between a GLDB and a CRS is used to send the following from a CRS to a GLDB: • CRS registration information; • CRS device parameters; • CRS channel usage parameters. Reference point A between a GLDB and a CRS is used to send the f... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.3.2 Reference point B: Between a CRS and a SC | Figure 5.9: Reference point B Reference point B is shown in figure 5.9. Reference point B between a CRS and a SC is used to send the following from a CRS to a SC: • CRS registration information; • Sensing and/or Measurement results; • Currently used RAT-specific parameters; • Reconfiguration results (notification of sp... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.3.3 Reference point C: Between SCs | Figure 5.10: Reference point C Reference point C is shown in figure 5.10. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 17 Reference point C between SCs is a reference point and it is used to send the following: • Information required for coordination between SCs; • Information used for assistance in CRS operational parameter ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 5.3.4 Reference point D: Between a SC and a GLDB | Figure 5.11: Reference point D Reference point D is shown in figure 5.11. Reference point D between a SC and a GLDB is used to send the following from a SC to a GLDB: • Available spectrum resources requests; • Request for the information required for output power level management; • Request for channel assignment; • Pr... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6 High Level Procedures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1 Procedures for Coordinated Access of White Spaces | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.1 Initialization procedures | A CRS shall perform the initialization procedure for the CRS to provide capability information to the SC whenever the CRS powers up or initiates communication with the SC. The capability information includes radio capability information (supported RAT, supported frequencies, supported data rates, and supported services... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.2 Coordination service subscription procedures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.2.1 Overview | These procedures deal with aspects of CRS coordination service subscription of the entities as defined in the functional architecture. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 20 |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.2.2 CRS subscription procedure | A CRS shall perform the CRS subscription procedure when it needs to subscribe to the services of the SC. The CRS shall subscribe to either information service or management service. Figure 6.2: CRS Subscription Procedure The procedure is shown in figure 6.2 and shall be as follows: 1. After a CRS has received a request... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.2.3 CRS subscription update procedure | A CRS shall perform the CRS subscription update procedure when the CRS wants to change the type of coordination service provided by the SC or to stop its operation. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 21 Figure 6.3: CRS Subscription Update Procedure The procedure is shown in figure 6.3 and shall be as follows: 1. Whe... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.2.4 CRS subscription change procedure | A SC shall perform the CRS subscription change procedure when the SC wants to ask a CRS to change the type of coordination service provided by the SC. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 22 Figure 6.4: CRS Subscription Change Procedure The procedure is shown in figure 6.4 and shall be as follows: 1. When a SC wants t... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3 Registration and authentication procedures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.1 Overview | These procedures deal with aspects of registration and authentication of the entities as defined in the functional architecture. In order to use the services of the SC, a CRS shall first register with the SC. Likewise, an SC shall authenticate with a GLDB in order to make use of the advanced services provided by the GL... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.2 CRS registration procedure | A CRS shall perform the CRS registration procedure when it has successfully finished the CRS subscription procedure. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 23 Figure 6.5: CRS Registration Procedure The procedure is shown in figure 6.5 and shall be as follows: 1. When the CRS registers to the SC, the CRS generates a Netw... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.3 CRS registration update procedure | A CRS shall perform the CRS registration update procedure when it needs to change its registration information. The CRS may also use the update procedure to de-register from the SC. Figure 6.6: CRS Registration Update Procedure ETSI ETSI TS 103 145 V1.1.1 (2015-01) 24 The procedure is shown in figure 6.6 and shall be a... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.4 Procedure for CRS deregistration from SC | A SC shall perform the CRS deregistration procedure when the SC needs to deregister the CRS from the SC. Figure 6.7: CRS De-Registration Procedure The procedure is shown in figure 6.7 and shall be as follows: 1. When a SC wants to deregister the CRS served by this SC, the SC generates a Network_Deregistration_Request m... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.5 SC authentication and registration procedure | A SC shall perform the SC authentication and registration procedure in order to register and authenticate to the GLDB. This allows the SC to obtain additional information on TVWS channels and to support use of channels with specific QoS guarantees. When registering to the GLDB, the SC first provides some rough informat... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.3.6 SC de-authentication and de-registration procedure | A SC shall perform the SC de-authentication and de-registration procedure when it needs to de-authenticate and de-register from the GLDB. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 26 Figure 6.9: SC De-Authentication and De-Registration Procedure The procedure is shown in figure 6.9 and shall be as follows: 1. Before the SC... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4 Channel Access Procedures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.1 Requesting CRS channel access procedure | A CRS shall perform the requesting CRS channel access procedure when the CRS wants to obtain the channel access information. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 27 Figure 6.10: Requesting CRS Channel Access Procedure The procedure is shown in figure 6.10 and shall be as follows: 1. When a CRS wants to obtain the chan... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.2 Requesting SC channel access procedure | A SC shall perform the requesting SC channel access procedure when the SC wants to obtain the channel access information. Figure 6.11: Requesting SC Channel Access Procedure ETSI ETSI TS 103 145 V1.1.1 (2015-01) 28 The procedure is shown in figure 6.11 and shall be as follows: 1. When the SC wants to obtain the channel... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.3 Providing available channel list procedure | A SC shall perform the providing available channel list procedure when the SC wants to provide the available channel list for the CRS served by the SC. Figure 6.12: Providing Available Channel List Procedure The procedure is shown in figure 6.12 and shall be as follows: 1. When a SC wants to provide the available chann... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.4 Procedure of channel usage notification for subject CRS | A SC shall perform the procedure of channel usage notification for subject CRS when it has received channel usage parameters from the subject CRS. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 29 Figure 6.13: Channel Usage Notification for Subject CRS Procedure The procedure is shown in figure 6.13 and shall be as follows: 1. ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.7 Basic Channel Access Sequence | Figure 6.16: Basic Channel Access Sequence The procedure is shown in figure 6.16 and shall be as follows: 1. The CRS makes a channel request to the SC. The request will contain the userID, device parameters, and basic requirements for the usage parameters (amount of spectrum, transmit power, antenna locations/coverage ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.4.8 Channel Access Sequence for Priority-Based Channel Assignment | Figure 6.17: Channel Access Sequence for Priority-Based Channel Assignment The procedure is shown in figure 6.17 and shall be as follows: 1. The CRS makes a channel request to the SC for priority-based channel assignment. The request will contain the basic device parameters of the CRS and specific performance requireme... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.5 Information exchange procedures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.5.1 Providing coordination report procedure | A SC shall perform the providing coordination report procedure when the coordination information has been changed for one or several CRSs subscribed to the information service and served by this SC. Figure 6.18: Providing Coordination Report Procedure ETSI ETSI TS 103 145 V1.1.1 (2015-01) 35 The procedure is shown in f... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6 Sensing and Measurement Procedures and Operation Sequences | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.1 Overview | The SC can configure sensing and measurements in the CRS in order to aid the SC to ensure coexistence between different CRSs, as well as to ensure a CRS can coexist despite interference from incumbents (e.g. adjacent channel interference from a strong DTV broadcast in TVWS). Sensing would consist of specific algorithms... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.2 Requesting measurements procedure | An SC shall perform the requesting measurements procedure to request the CRS served by this SC to perform measurements and to request the CRS to provide measurement reports. The SC requests the CRS to perform measurements and the CRS to provide measurement reports either once per request or on scheduled basis. Figure 6... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.3 Providing periodic measurements procedure | A CRS may be configured to perform periodic measurements and report them to the SC. A CRS shall perform the providing periodic measurement reports procedure when the SC has requested periodic measurement reports from the CRS. CRS SC 1. Measurement_Response 2. Measurement_Confirm N. Measurement_Response N+1. Measurement... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.4 Providing single measurements procedure | A CRS may be configured to perform single (non-periodic) measurements and report them to the SC. A CRS shall perform the providing single measurement reports procedure when the SC has requested single measurement reports from the CRS. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 37 CRS SC 1. Measurement_Response 2. Measuremen... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.5 Non-Periodic measurements sequence | Figure 6.22: Non-Periodic Measurements Sequence The procedure is shown in figure 6.22 and shall be as follows: 1. The SC performs the requesting measurements procedure by requesting the CRS to perform immediate non- periodic sensing and/or measurements. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 38 2. The CRS performs the m... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.6.6 Event-Triggered Measurement Sequence | Non-periodic sensing can be triggered by an event created by a CRS (any slave in the CRS, or a master WSD, for instance). The event will detect some form of change in the environment on the channel(s) being used by the CRS, which will result in the SC requesting the CRS to perform sensing to detect the actual cause for... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7 Reconfiguration Procedures and Operation Sequences | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.1 Reconfiguration request from SC to CRS procedure | The SC shall be able to reconfigure the operational parameters of a CRS through a reconfiguration request procedure. In addition, the SC shall be able to request reconfiguration of certain coexistence parameters in a CRS (assuming the CRS can support such parameters) based on changes in the usage of channels managed by... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.2 Reconfiguration request from SC to GLDB procedure | A SC shall perform the sending resource reconfiguration request from the SC to the GLDB which serves the SC when the SC requires resource for reconfiguration of a CRS. Figure 6.25: Reconfiguration Request from SC to GLDB Procedure The procedure is shown in figure 6.25 and shall be as follows: 1. When an SC requires res... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.3 General reconfiguration sequence between coordinated CRSs | The SC, based on interaction with a coordinated CRS (CRS2), determines that there is a need for reconfiguration of another coordinated CRS (CRS1). For instance, this may occur when CRS1 and CRS2 use overlapping adjacent channels that incur interface to each other. The reassignment of channel usage can resolve this coex... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.4 CRS Request-Triggered Operational Parameter Reconfiguration | Operational parameters can be reconfigured by the SC from a request made by a CRS. For example, the SC could realize that a CRS requiring two contiguous channels would be able to obtain them only if another CRS changes its operating channels, which would require a reconfiguration ETSI ETSI TS 103 145 V1.1.1 (2015-01) 4... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.6 General Priority-Based Channel Reconfiguration Sequence | Figure 6.29: General Priority-Based Channel Reconfiguration Sequence The procedure is shown in figure 6.29 and shall be as follows: 1. The SC, based on interaction with a priority access CRS (CRS2), determines that there is a need for reconfiguration of other non-priority CRSs (CRS1). For instance, this may occur when ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.8 Priority Usage Request Considering Uncoordinated Channel Usage | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.8.1 Overview | A priority usage coordinated CRS, upon requesting available channels from the GLDB, can provide requirements on its channel quality. In some scenarios, providing channels to the priority usage CRSs requires changes to the current usage of the uncoordinated CRSs. Such changes of the uncoordinated CRS channel usage will ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.8.2 Implementation Option A | In the first implementation option, the SC reserves channels with the GLDB in preparation for the expiry of the validity time of the channels used by the uncoordinated systems. Upon the expiry of the validity time, the priority usage CRSs can start using these channels. The GLDB, in storing the protection criteria of t... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.8.3 Implementation Option B | This implementation option relies on the use of two additional procedures which are required only for this implementation option: 1) the Priority Usage Checking procedure; and 2) providing Uncoordinated CRS information procedure. Priority usage checking procedure A GLDB shall perform the priority usage checking procedu... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.9 Uncoordinated CRS Request Considering Priority Usage Coordinated CRS | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.9.1 Overview | This procedure is performed when an uncoordinated CRS requests channels from the GLDB over reference point A, when there is a potential for causing interference with a priority usage CRS operating in the same area. It is assumed that the signalling between the uncoordinated CRS and the GLDB is consistent with clause 6.... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.9.2 Implementation Option A | Figure 6.35: Implementation Option A The procedure is shown in figure 6.35 and shall be as follows: 1. An un-coordinated CRS requests available channels from the GLDB. 2. The GLDB verifies the protection criteria of any priority usage CRS currently utilizing the white spaces. This protection criteria was obtained and s... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.9.3 Implementation Option B | This implementation option relies on the use of the following procedures above described: • the Priority Usage Checking procedure; • providing Uncoordinated CRS information procedure. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 57 Un- coordinated CRS SC GLDB Check whether the channel usage of the un-Coordinated CRS will infl... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.7.10 Device parameter reconfiguration request from SC to CRS procedure | The SC may be able to reconfigure certain device parameters of a CRS through a device parameter reconfiguration request procedure. When the SC has made a coordination decision which would require device parameter reconfiguration of the CRS, it may perform the sending of device parameter reconfiguration request from the... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8 Inter-SC procedures | 6.1.8.1 Reconfiguration request from master SC to CRS registered to slave SC procedure A SC shall perform the procedure for reconfiguration request from master SC to slave SC when the master SC has made a coordination decision that requires reconfiguration of a CRS registered to the slave SC. ETSI ETSI TS 103 145 V1.1.... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.2 Master/slave SC configuration procedure | A SC shall perform the master/slave SC configuration procedure when the master SC needs to change its role from master SC to slave SC in centralized decision making. The method for initially selecting the master SC is defined by the specific implementation of the system. When there are many SCs in the system, the syste... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.3 Obtaining coordination set information from other SCs procedure | A SC shall perform the procedure when the SC needs to obtain coordination set information from other SCs. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 63 Figure 6.41: Obtaining coordination set information from other SCs procedure The procedure is shown in figure 6.41 and shall be as follows: 1. When SC A needs to obtain the ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.4 Procedures for interfering SCs discovery | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.4.1 Overview | In coordinated usage of TVWS, the SC ensures coexistence of different CRSs to avoid harmful interference between CRSs under the same SC. However, depending on system implementation, it is possible that CRSs under different SCs could interfere with each depending on the areas managed by each SC. We refer to such SCs as ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.4.2 GLDB-aided potential interfering SCs discovery procedure | In the SC authentication/registration procedure, the SC provides information such as the planned location and channel usage of the CRSs which it supports. This information can be used by the GLDB to determine the potential interfering SCs for a given SC. Every SC could acquire knowledge of the potential interfering SCs... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.4.3 Interfering SCs discovery procedure | Before providing operational parameters to a CRS, the SC shall check whether the use of such operational parameters by the CRS causes interference to the CRS managed by other SCs. Such a check with proposed operational parameters should be done with every SC from the potential interfering SC list. ETSI ETSI TS 103 145 ... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.5 Negotiation between SCs procedure | The SC needs to negotiate with SCs in its coordination set about the channel usage/configuration of CRSs under its management. ETSI ETSI TS 103 145 V1.1.1 (2015-01) 66 SC A SC B 1. Negotiation_Request 2. Negotiation_Response Figure 6.44: Negotiation Between SCs The procedure is shown in figure 6.44 and shall be as foll... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.1.8.6 Operational Sequences for negotiation-based configuration of SCs | SC A SC B 1. Obtaining coordination set information between SCs procedure 2. Propose Channel usage/ configuration 3. Configuration negotiation Among SCs procedure Figure 6.45: Operation Sequence for Negotiation-based Configuration The procedure related to the full operational sequence for negotiation-based configuratio... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 6.2 Procedures for Uncoordinated Access of White Spaces | Figure 6.46: Operation procedure for uncoordinated access of white spaces The Operation sequence between entities is shown in figure 6.46. The sequence between GLDB, mater WSD and slave WSD is shall be as follows: 1. A master WSD sends device parameter to the GLDB. 2. The GLDB generates its specific operational paramet... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7 Potential Implementation Architectures | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1 High level flow chart of entities | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.1 CRS operation | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.1.1 General description | A CRS shall support the following procedures. • Initialization • CRS subscription • CRS subscription update • CRS subscription change • CRS registration • CRS registration update • Requesting CRS channel access • Providing available channel list • Reconfiguration request from SC to CRS • Device parameter reconfiguratio... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.2 SC operation | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.2.1 General description | A SC shall support the following procedures. • Initialization • CRS subscription • CRS subscription update • CRS subscription change • CRS registration • CRS registration update • SC authentication and registration • SC de-authentication and de-registration • Requesting SC channel access • Providing available channel l... |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.3 GLDB operation | |
9e15b7676569b64d8a45258be2eed974 | 103 145 | 7.1.3.1 General description | A GLDB shall support the following procedures. • SC authentication and registration • SC de-registration and de-registration • Channel usage notification • Priority usage checking • Providing uncoordinated CRS information • Procedure for GLDB to SC Notification for CRS operational parameters update A high level flow ch... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for Security as defined in ETSI TS 103 097 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well ... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 2 References | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 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... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 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... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 3 Definition of terms, symbols and abbreviations | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 097 [1], ETSI TS 102 965 [i.2], ISO/IEC 9646-6 [i.5] and ISO/IEC 9646-7 [i.6] apply. |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 3.2 Symbols | Void. |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Authorization Authority AID Application Identifier AID_CAM ITS Application Identifier for CAM AID_DENM Application Identifier for DENM AID_GN Application Identifier for general GeoNetworking messages AT Authorization Ticket ATS Abstract Tes... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 4 Test Suite Structure (TSS) | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 4.1 Structure for Security tests | Table 1 shows the Security Test Suite Structure (TSS) defined for conformance testing. Table 1: TSS for Security Root Group Category Security ITS-S data transfer Valid ITS-S - AA authorization Valid ITS-S - EA enrolment Valid Sending behaviour Valid Receiving behaviour Valid and Invalid Generic messages Valid CAM testi... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5 Test Purposes (TP) | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1 Introduction | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1.1 TP definition conventions | The TP definition is built according to ETSI EG 202 798 [i.1]. |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1.2 TP Identifier naming conventions | The identifier of the TP is built according to table 2. Table 2: TP naming convention Identifier TP_<root>_<tgt>_<gr>_<sgr>_<rn>_<sn>_<x>[_<v>] <root> = root SEC <tgt> = target ITSS ITS-S data transfer CA Certificate Authority tests AA ITS-S - AA authorization EA ITS-S - EA enrolment <gr> = group SND Sending behaviour ... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1.3 Rules for the behaviour description | The description of the TP is built according to ETSI EG 202 798 [i.1]. ETSI TS 103 097 [1] does not use the finite state machine concept. As a consequence, the test purposes use a generic "Initial State" that corresponds to a state where the IUT is ready for starting the test execution. Furthermore, the IUT shall be le... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1.4 Sources of TP definitions | All TPs have been specified according to ETSI TS 103 097 [1] and IEEE Std 1609.2 [2]. |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 5.1.5 Mnemonics for PICS reference | To avoid an update of all TPs when the PICS document is changed, table 3 introduces mnemonics name and the correspondence with the real PICS item number. The 'PICS item' as defined in IEEE Std 1609.2 [2], ETSI TS 103 096-1 [3] and ETSI TS 102 871-1 [4] shall be used to determine the test applicability. Table 3: Mnemoni... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6 ITS-S Security | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6.1 Overview | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6.1.1 Certificates content | |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6.1.1.1 Root Certificate Authorities certificates | RCA certificate Content To be installed on the IUT CERT_IUT_A_RCA - self-signed - name "ETSI Test RCA A certificate" - application permissions: o CRL with SSP 0x01 o CTL with SSP 0x0138 - certificate issuing permissions: o CAM with all possible SPP (0x01FFFC / 0xFF0003) o DENM with all possible SSP (0x01FFFFFF / 0xFF00... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6.1.1.2 Authorization Authorities certificates | AA certificate Content To be installed on the IUT CERT_IUT_A_AA - signer digest of the CERT_IUT_A_RCA - application permissions: o CRT_REQ with SSP 0x0132 - certificate issuing permissions: o CAM with all possible SPP (0x01FFFC / 0xFF0003) o DENM with all possible SSP (0x01FFFFFF / 0xFF000000) o SPATEM with all possibl... |
178192f851c1df4ccb17504392f1e490 | 103 096-2 | 6.1.1.3 Authorization Tickets | Authorization ticket Content To be installed on the IUT CERT_IUT_A_AT - Explicit certificate - signer digest of the CERT_IUT_A_AA; - application permissions: o CAM with all SPP (0x01FFFC); o DENM with all SSP (0x01FFFFFF); o GN-MGMT; - validation time for 1 year; - no region restriction; - assurance level 3; - verifica... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.