hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.1.2 Confidentiality | As CAMs are broadcasts to any possible receiver there are no confidentiality requirements. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.1.3 Privacy | CAMs are sent periodically up to several times a second by every ITS-S. They contain substantial status information (e.g. location) relating to the sending ITS-S. Consequently, it is necessary to ensure that the data cannot be linked to any individual so that no personally identifying information is leaked by the CAM s... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.2 Security requirements of static local hazard warnings | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.2.1 Authentication and Authorization | Static local hazard warnings have very similar properties than the CAM service with the exemption that they are sent by RSUs. For Authentication and Authorization similar requirements as for CAM apply with the addition, that authorization should be limited to the specific purpose, functionality, and location of the res... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.2.2 Confidentiality and Privacy | As the nature of the service is broadcast and the sender is a static RSU, no confidentiality or privacy requirements apply. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.3 Security requirements of interactive local hazard warnings | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.3.1 Authentication and Authorization | In general the requirements for Authorization and Authentication are similar to CAM. In the subsequent unicast session the local policies of the participating partners may require additional authorization and/or authentication. These additional requirements are out of the scope of the present document. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.3.2 Confidentiality and Privacy | The requirements for Confidentiality and Privacy depend heavily on the specific application and the information to be exchanged. The unicast session may contain more privacy related and personally identifying information so that confidentiality may be an issue but this is likely to be solved within the application or b... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.4 Security requirements of area hazard warnings | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.4.1 Authentication and Authorization | Authorization for area hazard warnings (Decentralized Environment Notification Message, DENM) could be granted on several levels depending on sensor equipment, sensor quality and algorithmic and processing capabilities of the ITS-S. Apart from that, similar requirements as for CAM apply. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.4.2 Confidentiality and Privacy | As the service is event-driven and, therefore, sporadic and as neither the properties of the sender nor its identity are important for the reported area warning, the privacy issues are reduced compared with the CAM service. Consequently, no confidentiality services are required. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.5 Security requirements of advertised services | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.5.1 Authentication and Authorization | The Service Advertisement message (SAM/WSA) is used by a service provider unit to inform ITS stations about available local services or about services that can be accessed on a remote server. To minimize the risk of threats to ITS stations such as attacks from a fake or malicious service provider unit or an impersonati... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.5.2 Confidentiality and Privacy | As the nature of service is broadcast to any possible receivers and the sender is a static RSU or a mobile vehicle which accepts to play a distinguishable role (e.g. leader vehicle in a platoon), no confidentiality or privacy requirements apply. |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.6 Security requirements of other services | Special authorization may be needed for commercial services. The authorization model depends on the specific service provided and the local legal conditions which may vary between countries. Authorization may include fees. Local services such as multimedia download may need confidentiality in addition depending on the ... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.7 Security requirements of multiple applications | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.7.1 Authentication and Authorization | In general, Authentication and Authorization are handled separately for each individual application. Nevertheless, some combinations of applications may require special treatment or authorization due to additional privacy issues. This needs to be dealt with in security policies associated with the authorization or duri... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.7.2 Confidentiality and Privacy | It is assumed that each ITS application uses its own identifiers that cannot be linked to each other. In particular, DENM and CAM originating from the same vehicle should not be linkable. ETSI ETSI TS 102 940 V1.2.1 (2016-11) 20 |
79491d3f4dfdee6749c7487774681445 | 102 940 | 5 ITS communications security architecture | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 5.1 ITS station communications security architecture | ETSI EN 302 665 [1] shows Security as a vertical layer adjacent to each of the ITS layers but, in fact, security services are provided on a layer-by-layer basis so that the security layer can be considered to be subdivided into the four basic ITS processing layers as shown in figure 4. Security services are provided on... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 5.2 Security services | ETSI TS 102 731 [4] identifies a range of security services which may be supported by an ITS station in order to provide communications security between itself and other stations. Table 3 provides the list and a short description of these services. Table 3: ITS Communication Security Services Service category Security ... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 5.3 ITS security functional model | Communications security services require, by definition, more than one element within their functional model. The principle functional elements and reference points between them can be determined by considering a simple ITS communications scenario such as that shown in figure 7. This shows an ITS-enabled vehicle which ... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6 ITS station security management | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.1 Basic principles | The purpose of the present document is to describe an architecture for the communication security of ITS. However, it is also necessary for an ITS-S to provide secure access to common resources such as services, information and protocols. These security requirements can be separated into two parts: 1) external security... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.2 Guidelines for establishing enrolment trust requirements | The following recommendations are specified as guidance in ensuring that an ITS-S is able to establish a trust relationship with an enrolment authority: • all cryptographic key material should be stored in a secure memory that is protected against tampering, altering and unauthorized reading and should only be accessib... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.3 Trust and privacy management | The enrolment and authorization services (table 4) provide the following services to support the establishment of trust and the protection of privacy: • trust: - the provision of certificates allowing an ITS station to assert: their permission to use the ITS system as a whole; and their permission to use specific I... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.4 Access control | Before an ITS station can make full use of the ITS applications, services and capabilities that are available to it, it is required to obtain specific credentials from the Authorization Authority. These credentials, in the form of cryptographically signed certificates, are used to assure any receiving ITS-S that the st... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.5 Identity management | For privacy reasons, the Authorization Authority provides an ITS station with multiple pseudonyms and the related authorization tickets (or pseudonym certificates) to be used in the ITS communication. Privacy protection is provided by changing frequently the ITS-S pseudonym and its related certificate. Identity managem... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 6.6 Confidentiality | Many of the applications and services described in ETSI TR 102 638 [i.1] and summarized in table 2 are based on the transmission of broadcast messages which are intended to be viewed and processed by all recipients. Consequently, there are no confidentiality requirements associated with these messages other than the pr... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 1 Scope | The scope of the present document is to define the system requirements for Reconfigurable Radio Systems operating in GSM and IMT bands for intra-operator scenarios. These requirements are derived from the use cases described in ETSI TR 103 063 [i.1]. The present document considers the system requirements only for intra... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 2 References | |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 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... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 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... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 3 Definitions and abbreviations | |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: cognitive radio system: radio system employing technology that allows the system to obtain knowledge of its operational and geographical environment, established policies and its internal state; to dynamically and autonomously adjust i... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: DSP Digital Signal Processor FPGA Field Programmable Gate Array HPR Hardware Processing Resource IMT International Mobile Telecommunications MD Mobile Device QoS Quality of Service RAT Radio Access Technology RBS Reconfigurable Base Station RF... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 4 Requirement Organization and Format | |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 4.1 Requirement Organization | The present document is structured such that a level 2 section is dedicated to the requirements associated with a single category. The overall structure is shown in figure 4.1. ETSI ETSI TS 102 968 V1.1.1 (2016-11) 7 Figure 4.1: Overall requirements structure |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 4.2 Requirement Format | 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 PERF Performance aspects • <GROUP>: Requirement group identifier. A letter code will be us... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 5 Working assumptions | ETSI TR 103 063 [i.1] describes how Reconfigurable Radio Systems can be exploited in IMT bands and GSM bands (i.e. licensed spectrums allocated to IMT and GSM systems) to increase the efficiency of the radio resource management in the intra-operator scenarios for which the spectrum resources are assigned to and managed... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6 Functional Requirements | 6.1 Radio and Hardware Processing Resources Reconfiguration Requirements |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.1.1 R-FUNC-RHR-01: Reconfiguration for each RAT | The system shall support the reconfiguration of both the Hardware Processing Resources (HPRs) and the Radio Resources (RRs) for each supported RAT. Explanation: The system should be able to perform resource reconfiguration of both the hardware processing resources and the radio resources for each supported RAT. The rad... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.1.2 R-FUNC-RHR-02: Reconfiguration between RATs | The system shall support reconfiguration of both HPRs and RRs between different RATs. Explanation: The system can re-configure multiple RATs with flexibility in terms of the percentage of HPRs and RRs between different RATs according to the status of the network. |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2 Requirements for functions supporting reconfiguration | |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.1 R-FUNC-REC-01: Gathering and processing function | The system shall support a gathering and processing function to gather and process certain radio related metrics and parameters. Explanation: After having gathered radio related metrics and parameters, the gathering and processing function may process them to make decisions on reconfiguration in order to optimize radio... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration | The system shall support trigger events for reconfiguration. Explanation: Trigger events are described by certain parameters (e.g. thresholds, hysteresis, etc.) in order to define the condition under which an event is happening. When one or more events occur, the system starts to evaluate the need for a possible reconf... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.3 R-FUNC-REC-03: Support for reconfiguration function | The system shall support a reconfiguration function to make decisions for radio resource reconfiguration and inform RBSs to perform the reconfiguration e.g. triggered by events in clause 6.2.2. Explanation: The reconfiguration function shall make radio resource reconfiguration decisions such as, reconfiguration time, r... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.4 R-FUNC-REC-04: Support for execution function | The system shall support the execution function in order to perform the reconfiguration. Explanation: The system devices (e.g. RBS, MDs, etc.) should support mechanisms in order to be reconfigured according to the reconfiguration decision of the reconfiguration function. |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.5 R-FUNC-REC-05: Support of learning function | The system shall support a learning function to improve and optimize the reconfiguration decisions. Explanation: For example, the learning capability may consist in monitoring the performance of the system after each reconfiguration and verifying whether the decisions meet or not the reconfiguration target. Another pos... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.2.6 R-FUNC-REC-06: Support of information provisioning function | The system shall support an information provisioning function to provide updated network configuration information to the appropriate system devices. Explanation: After a reconfiguration, the information related to the new network configuration and policies, are expected to be efficiently provided to the system devices... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.3 MDs mobility and connectivity management requirements | |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.3.1 R-FUNC-MOB-01: Mobility management of the MDs | The system shall guarantee the mobility management of the MDs. Explanation: Network reconfiguration (e.g. change of RAT in currently used band or starting operations in a new band using a RAT already deployed or a new RAT) may imply the change of radio parameters, such as neighbour cells relation information (e.g. the ... |
1fd01e3659f8669c8c87458cf36aa0da | 102 968 | 6.3.2 R-FUNC-MOB-02: Connectivity management of the MDs | The system shall manage the connectivity of the MDs during the reconfiguration. Explanations: When a MD is in connected mode on a RAT operating on radio resources that may be reconfigured, an appropriate decision has to be evaluated by the system in order to maintain the connectivity of the involved MDs. In the followi... |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 1 Scope | The present document: • provides a hyperlink to a template to request a new entry in the list; • lists the assigned ITS-AID values for ETSI-ITS. |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 2 References | |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 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... |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 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... |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 3 Definition of terms, symbols and abbreviations | |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 3.1 Terms | For the purposes of the present document, the terms given in ISO 17419 [1] apply. |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 3.2 Symbols | Void. |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AVM Automated Vehicle Marshalling CA Cooperative Awareness CP Collective Perception DEN Decentralized Environmental Notification GN GeoNetworking GN-MGMT GeoNetworking Management Communications GPC GNSS Positioning Service IMZ Interference Man... |
2699a667026e9b8ef06515c95a8e0736 | 102 965 | 4 ITS-AID registration list | The assigned ITS-AID values for ETSI-ITS are provided in Annex A. In order to request assignment of an ITS-AID the applicant shall use the template given in ISO 17419 [1]. ETSI ETSI TS 102 965 V2.4.1 (2025-11) 8 Annex A (normative): ITS-AID assigned for ETSI ITS ETSI Cooperative ITS shall use the assigned ITS-AIDs prov... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 1 Scope | The present document specifies the eCall applicable tests required to ensure eCall NAD conformance when accessing Digital cellular telecommunications system (Phase 2+) and Universal Telecommunication System (UMTS) mobile networks. The present document includes references to existing ETSI technical specifications includ... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Service principles (3GPP TS 22.101)". [2] ETSI TS 126 269: "Digital cellular telecommunications system (Phase 2+); Universal Mobile... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 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 TR 102 937: "Mobile systems; Guidelines on applicability of GSM and UMTS mobile station harmonized standards to eCall Network Access Device (NAD)... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 3 Definitions and abbreviations | |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: eCall: manually or automatically initiated emergency call, (TS12) from a vehicle, supplemented with a minimum set of emergency related data (MSD), as defined under the EU Commission's eSafety initiative Minimum Set of Data (MSD): data ... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AIeC Automatically Initiated eCall CC Call Control CEN Commission Européen de Normalisation EFFDN Elementary File Fixed Dialling Numbers EFSDN Elementary File Service Dialling Numbers GNSS Global Navigation Satellite System ICS Implementation ... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 4 General aspects of eCall conformance testing | The eCall service is based on the pan-European harmonised 112 emergency service supplemented by accident related data. An eCall is initiated automatically when a collision of sufficient severity occurs, or manually by the vehicle occupants. Once initiated the eCall proceeds automatically without the need for any user i... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 4.1 Types of eCall capable UE - Unrestricted and Restricted | In order to avoid the generation of large volumes of unnecessary mobility management (MM) signaling, when not engaged in an eCall, test or reconfiguration call, additional network access restrictions apply to certain 'eCall only' devices in accordance with TS 122 101 [1]. eCall capable UEs are divided into two types, u... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 4.2 Establishment of eCalls by the UE under test | A Manually Initiated eCall (MIeC) or an Automatically Initiated eCall (AIeC) shall be initiated in accordance with the information provided by the manufacturer in the Implementation Conformance Statement (ICS) proforma [4]. The eCall capable UE is expected to provide a call set-up MMI that enables the user to manually ... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5 UMTS network access eCall NAD conformance tests | The terminal type and eCall applicable tests required to ensure eCall NAD conformance when accessing a Universal Telecommunication System (UMTS) mobile network are specified, by reference, in the following clauses. eCall NAD conformance testing shall be carried out in accordance with the tests and test procedures speci... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1 eCall Emergency Call Procedures | Reference TS 134 123-1 [3], clause 13.3. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1 eCall with USIM | Reference TS 134 123-1 [3], clause 13.3.1. ETSI ETSI TS 102 936-1 V1.1.1 (2011-04) 9 |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1.1 Void | |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1.2 Test call using eCall capable UE with 'eCall only' subscription on USIM | Reference TS 134 123-1 [3], clause 13.3.1.2. 5.1.1.3 Manually initiated eCall using eCall capable UE with 'eCall only' subscription on USIM Reference TS 134 123-1 [3], clause 13.3.1.3. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1.4 Reconfiguration call using eCall capable UE with 'eCall only' subscription | Reference TS 134 123-1 [3], clause 13.3.1.4. 5.1.1.5 Manually initiated eCall using eCall capable UE with eCall and non eCall subscription on USIM Reference TS 134 123-1 [3], clause 13.3.1.5. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1.6 eCall Inactivity State after T3242 expires | Reference TS 134 123-1 [3], clause 13.3.1.6. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.1.1.7 Automatically initiated eCall | Reference TS 134 123-1 [3], clause 13.3.1.7. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 5.2 Applicability of eCall NAD tests for UMTS network access | Table 5.1: Applicability of tests (TS 134 123-2 [4]) Clause Title Release Comments 13.3 eCall Emergency Call Procedures 13.3.1 eCall with USIM 13.3.1.2 Test call using eCall capable UE with 'eCall only' subscription on USIM Rel-8 UEs supporting 'eCall only' subscription and capable of triggering a test eCall 13.3.1.3 M... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6 GSM network access eCall NAD conformance tests | The terminal type and eCall applicable tests required to ensure eCall NAD conformance when accessing a Digital cellular telecommunications system (Phase 2+) mobile network are specified, by reference, in the following clauses. eCall NAD conformance testing shall be carried out in accordance with the tests and test proc... |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1 eCall Emergency Call Procedures | Reference TS 151 010-1 [6], clause 26.9.6a. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1 eCall with USIM | Reference TS 151 010-1 [6], clause 26.9.6a.1. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.1 Void | |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.2 Test call using eCall capable MS with 'eCall only' subscription on USIM | Reference TS 151 010-1 [6], clause 26.9.6a.1.2. 6.1.1.3 Manually initiated eCall using eCall capable MS with 'eCall only' subscription on USIM Reference TS 151 010-1 [6], clause 26.9.6a.1.3. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.4 Manually initiated eCall using eCall capable MS with eCall capable USIM | Reference TS 151 010-1 [6], clause 26.9.6a.1.4. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.5 eCall Inactivity State after T3242 expires | Reference TS 151 010-1 [6], clause 26.9.6a.1.5. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.6 Automatically initiated eCall | Reference TS 151 010-1 [6], clause 26.9.6a.1.6. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.1.1.7 Reconfiguration call using eCall capable MS with 'eCall only' subscription | Reference TS 151 010-1 [6], clause 26.9.6a.1.7. |
37f49a81ad1b4f4c3c00b85c6174f90c | 102 936-1 | 6.2 Applicability of eCall NAD tests for GSM network access | Table 6.1: Applicability of tests (TS 151 010-2 [7]) Clause Title Release Comments 26.9.6a Structured Calls / eCall 26.9.6a.1 eCall with USIM 26.9.6a.1.2 Test call using eCall capable MS with 'eCall only' subscription on USIM Rel-8 MS supporting 'eCall only' subscription and capable of triggering a test eCall 26.9.6a.1... |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 1 Scope | The present document specifies Interoperability Test Descriptions (TDs) for OCCI and CDMI standards. The Test Descriptions cover the OCCI and CDMI protocol specifications where relevant and more specifically: 1) OCCI interoperability testing, to prove that end-to-end functionality is as required by the standard. 2) CDM... |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] OGF GFD.183: "Open Cloud Computing Interface - Core". [2] OGF GFD.184: "Open Cloud Computing Interface - Infrastructure". [3] OGF GFD.185: "Open Cloud Computing Interface - RESTful HTTP Rendering". [4] ISO/IEC 17826: "Info... |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 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] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". [i.2] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1". |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in GFD.183 [1], GFD.184 [2], GFD.185 [3], ISO/IEC 17826 [4] and the following apply: SUT System Under Test ETSI ETSI TS 103 142 V1.1.1 (2013-04) 9 |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 4 Conventions | |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 4.1 Interoperability test process | |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 4.1.1 Introduction | The goal of interoperability testing is to check that services implemented according to protocol specifications are able to interwork and to provide at least the mandatory features specified in the protocol specification. In addition, optional features may be checked when all services involved in a test support them. D... |
0aa3fbee0abc0f4062b2c8be0e70b9cc | 103 142 | 4.1.2 Test description proforma | The test descriptions are provided in proforma tables. The test description header specifies a unique test identifier, the test objective, the test configuration to be used and references to the protocol specification(s). The pre-condition row defines conditions that need to apply before starting the test. The followin... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.