hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.3 Link layer | |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.3.1 5,9 GHz / 802.11p link | No mechanisms suitable for link-layer confidentiality over an ITS G5A link have been defined. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.3.2 2G/3G/LTE | Confidentiality services for 2G/3G/LTE communications shall be provided by the mechanisms specified in TS 133 102 [1]. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.3.3 Other link layer protocols | Confidentiality mechanisms for communications over a link layer other than the link layers specified above shall provide at least 128 bits of cryptographic security. ETSI ETSI TS 102 943 V1.1.1 (2012-06) 8 Annex A (informative): Bibliography IEEE 802.11p: "IEEE Standard for Information technology - Local and metropolit... |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 1 Scope | The present document is the baseline for the definition of the Release 2 Access Control. |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 2 References | |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 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... |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 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... |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 3 Definition of terms, symbols and abbreviations | |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 942 [1] apply. |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 3.2 Symbols | Void. |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 942 [1] apply. ETSI ETSI TS 102 942 V2.0.0 (2022-11) 6 4 Use of references and numbering in Release 2 specifications TC ITS specifications are developed in Releases and each Release needs to be self-consistent. The following rules apply: •... |
2f974b64661f4e4ece9fa82d35635c3f | 102 942 | 5 Normative provisions | ETSI TS 102 942 [1] shall apply altogether. ETSI ETSI TS 102 942 V2.0.0 (2022-11) 7 History Document history V1.1.1 June 2012 Publication V2.0.0 November 2022 Publication |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 1 Scope | The present document specifies the trust and privacy management for Intelligent Transport System (ITS) communications. Based upon the security services defined in TS 102 731 [1] and the security architecture define in TS 102 940 [5], it identifies the trust establishment and privacy management required to support secur... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 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... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 731: "Intelligent Transport Systems (ITS); Security; Security Services and Architecture". [2] ETSI EN 302 665: "Intelligent Transport Systems (ITS); Communications Architecture". [3] ETSI TS 102 867: "Intellige... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 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] ISO/IEC 15408-2: "Information technology - Security techniques - Evaluation criteria for IT security; Part 2: Security functional components". [i.2] E... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 3 Definitions and abbreviations | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: anonymity: ability of a user to use a resource or service without disclosing the user's identity authorization authority: authority that provides an ITS-S with permission to invoke ITS applications and services canonical identifier: st... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Authorization Authority CA Certification Authority CAM Cooperative Awareness Message CRL Certificate Revocation List CSR Certificate Signing Request DENM Decentralized Environmental Notification Message EA Enrolment Authority ETSI ETSI TS 1... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4 ITS authority hierarchy | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4.1 Overview | Trust and privacy management requires secure distribution and maintenance (including revocation when applicable) of trust relationships, which may be enabled by specific security parameters that include 3rd party certificates of proof of identity or other attributes such as pseudonym certificates. Public key certificat... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4.2 ITS authorities | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4.2.1 Enrolment Authority | The EA issues a proof of identity authenticating the canonical identifier issued to the ITS-S. The proof of identity does not reveal the canonical identifier to a 3rd party and may be used by the ITS-S to request authorization of services from an AA. The functions provided by the EA are as follows: • the authentication... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4.2.2 Authorization Authority | An ITS-S that has enrolled with, and been authenticated by, an EA may apply to an AA for specific permissions within the enrolment authority's domain and the AA's authorization context. These privileges are denoted by means of authorization credentials in the form of IEEE 1609.2 [8] authorisation certificates. Each aut... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 4.2.3 Root CA | Each CA hierarchy (for EA or AA) has at its summit a Root Certificate, which is the ultimate root of trust for all certificates within that hierarchy. In order to trust an incoming message, an ITS-S must have access at least to the root certificate at the summit of the hierarchy for the authorization certificate attach... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 5 Privacy in ITS | ISO/IEC 15408-2 [i.1] identifies 4 key attributes that relate to privacy: • anonymity; • pseudonymity; • unlinkability; and • unobservability. ETSI ETSI TS 102 941 V1.1.1 (2012-06) 9 Anonymity alone is insufficient for protection of an ITS user's privacy and unsuitable as a solution for ITS, as one of the main requirem... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6 Trust and privacy management | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.1 ITS-S Security Lifecycle | The ITS-S Security Lifecycle includes the following stages: • manufacture; • enrolment; • authorization; • maintenance. |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.1.1 Manufacture | As part of the ITS-S manufacturing process, the following information elements associated with the identity of the station shall be established within the ITS-S itself and within the Enrolment Authority (EA). • in the ITS-S, the following information elements shall be established using a physically secure process. The ... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.1.2 Enrolment | The ITS-S requests its enrolment certificate from the EA (see clause 6.2.2.2). |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.1.3 Authorization | Having received the enrolment credentials, the ITS-S requests its authorization certificate(s) from the AA (see clause 6.2.2.3). |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.1.4 Maintenance | If an EA or AA is added to or removed from the system, the associated authority (not defined by the present document) should inform enrolled ITS-Ss of this change. The process for achieving this is beyond the scope of the present document but possible methods include: • sending a certificate revocation list as specifie... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2 Public Key Infrastructure | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2.1 Assumption and requirements | The present document assumes the ITS security reference model that is described in TS 102 940 [5]. |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2.2 Message Sequences | |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2.2.1 Introduction | The message sequences specified in clauses 6.2.2.2 and 6.2.2.3 for ITS-S enrolment and authorization are based on the protocol messages defined in TS 102 867 [3] and IEEE 1609.2 [8]. Each of the messages shall be encoded into a 1609Dot2Data (see clause 6 in IEEE 1609.2 [8]) with the appropriate enumeration set into its... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2.2.2 Enrolment Request | The Enrolment Request message shall be sent by an ITS-S to the Enrolment Authority (EA) across the interface at reference point S3 (see Figure 7 in TS 102 940 [5]) to request an enrolment certificate to be used in a subsequent authorization request. Figure 2 shows an example of a message sequence for a successful or un... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 6.2.2.3 Authorization Request | The Authorization Request message shall be sent by an ITS-S to the Authorization Authority (AA) across the interface at reference point S2 (see Figure 7 in [5]) to request an authorization certificate to be used in a subsequent ITS communications. Figure 3 shows an example of a message sequence for a successful or unsu... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 7.1 Broadcast SAs | Broadcast applications such as CAM and DENM require authentication, authorisation and integrity but not confidentiality. Senders of CAM and DENM shall obtain this service by signing with an authorization certificate using the mechanisms of IEEE 1609.2 [8] (see clause 6.2.2.3 and Table 5, as well as TS 102 867 [3]). Fig... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 7.2 Multicast SAs | Multicast applications such as public transport information and Point of Interest notification services require secure group communications with message authentication, authorisation and encryption depending on that group's particular security policy. An ITS-S may join a multicast group using an authorisation certifica... |
51b2f3995552a5ee1b4a77d9f69bb691 | 102 941 | 7.3 Unicast SAs | Unicast applications such as automatic access control, parking management and media downloading services require secure unicast communications with message authentication, authorisation and encryption. An ITS-S may join such services using its authorisation certificate (see clause 6.2.2.3 and Table 5) followed, possibl... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 1 Scope | The present document describes a proposal of requirements for a Network Termination (NT) device in Next Generation Access Networks. |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] CENELEC EN 50173-1 (2007): "Information technology - ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] Council Directive 89/336/EEC of 3 May 1989 on th... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADSL Asymmetric Digital Subscriber Line AES Advanced Encryption Standard AN Access Network ANP Access Network Provider ATM Asynchronous Transfer Mode BER Bit Error Rate BSP Broadband Service Provider CBR Constant Bit Rate CO Central Office CoS... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 4 General requirements | |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 4.1 Hardware and case characteristics | Specific requirements: 1) Customized case (the case will be customized by each operator) with small form factor, also allowing wall-mount. Specific recommended dimensions, in case of xDSL WAN-side technology, are 5 × 5 × 2 cm. In case of optical WAN-side technology, no specific dimensions are defined (mainly determined... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 4.2 Powering characteristic | Specific requirements: 10) The power supply MUST be external, in switching (not linear) technology and connected to the device using a connector. 11) The contra-connector on the NT-housing MUST contain a pull relief mechanism that prevents accidental removal of the power supply connector. ETSI ETSI TS 102 973 V1.1.1 (2... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5 WAN physical interfaces | The following different and alternative options for the NT WAN interface are addressed by these requirements, in order to support specific WAN technologies: • ADSL2+ only. • VDSL2 only. • VDSL2 and ADSL2+. • GPON. • Point-to-point FTTH based on 100Base-BX technology. A specific different NT device is foreseen to suppor... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.1 xDSL physical connector | 21) xDSL WAN interface with RJ-45 connector [1] and [2] with specific color coding (DSL Forum TR-068 [4] requirement I - 37). As an alternative, depending on regional specific requirements, RJ-11 connector may be used. In order to facilitate compatibility with regional specific requirements, it is recommended to adopt ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.2 ADSL2+ specific characteristics | 22) The NT must conform to ITU-T Recommendation G.992.1 [i.14], (ADSL) annex A, ITU-T Recommendation G.992.3 [i.15], (ADSL2) annex A and ITU-T Recommendation G.992.5 [i.16], (ADSL2plus) annex A. 23) The NT must be able to guarantee, in the interworking with the DSLAM platforms, at least the same ADSL1 performances as r... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.3 VDSL2-only specific characteristics | 27) Compliancy with ITU-T Recommendation G.993.2 [i.19]; moreover the VDSL2 line system must be compliant with ITU-T Recommendation G.993.2 [i.19], Corrigendum 1 and Amendment 1. 28) Compliancy with the international standards of the ITU-T: - ITU-T Recommendation G.997.1 [i.17], Physical layer management for digital su... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.4 VDSL2 and ADSL2+ specific characteristics | The following additional requirements apply in case of VDSL2 NT with ADSL2+ backward compatibility: 41) ADSL/ADSL2+ (ATM encapsulation) backward compatibility with full auto-sensing, in terms that no action on the device is needed (i.e. no reboot) during or after the switch from ADSL2+ to VDSL2 and vice-versa (seamless... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.5 GPON-specific characteristics | In the current clause, the GPON NT is referred as ONT. 45) The GPON interface must be compliant with ITU-T Recommendation G.984 (all parts) [i.10]. 46) Single fiber transmission is used for optical transmission (both in the upstream and downstream direction) and bidirectional transmission is accomplished by use of a WD... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 5.6 Point-to-point FTTH specific characteristics | 73) The fiber Point-to Point WAN interface MUST be 100base-BX (single mode fibre/bidirectional on a single fibre with diplex mode). 74) 100base-LX (single mode fibre, dual simplex fibres) MAY be used as fiber Point-to Point WAN instead of 73). ETSI ETSI TS 102 973 V1.1.1 (2008-09) 18 75) 1000base-BX (single mode fibre/... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 6 WAN interfaces logical framing | |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 6.1 L2 ATM features | These requirements apply only in case of ADSL2+ only NT and VDSL2/ADSL2+ NT. 77) The ATM/ADSL network interface UNI must conform with ATM Forum UNI 4.0. 78) The ATM functionalities must be compliant with ITU-T Recommendation I.361 [i.20]. 79) The AAL5 adaptation protocol must be compliant with ITU-T Recommendation I.36... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 6.2 L2 Ethernet features | These requirements apply in case of xDSL interfaces operating in PTM mode, GPON and point-to-point FTTH. 86) The NT shall at least support 1 534 bytes Ethernet Frame Size (1 500 bytes data size + PPPoE header 8 bytes, Ethernet header 18 bytes, and two VLAN tags 2x4 bytes). 87) VLAN support with 802.1q tagged frames con... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 6.3 Performances | 91) All interfaces shall support line rates data (for GPON, Fast Ethernet and Gigabit Ethernet interfaces). 92) [xDSL and P2P] The processing power should be sufficient to support maximum WAN-technology specific line speeds (at least 100 Mbps full-duplex, for Fast Ethernet WAN) with all VLAN and QoS features active, fo... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 7 LAN interfaces | |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 7.1 Single LAN port | The following specific requirements apply for any NT option, and basically in case of single LAN Ethernet port. 94) One Ethernet 10/100BaseT ports, according to ISO/IEC 8802-3 [i.8] standard, autosensing (10/100) and with MDIX functionalities. 95) Gigabit Ethernet must be supported in case of GPON WAN interface. Option... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 7.2 Multiple LAN ports | These additional requirements, with respect to clause 7.1 Single LAN port, apply in case of multiple LAN Ethernet ports. 100) Four Ethernet 10/100BaseT ports, according to ISO/IEC 8802-3 [i.8] standard, autosensing (10/100) and with MDIX functionalities. 101) Gigabit Ethernet must be supported on the LAN interfaces in ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 8 IP functionalities | 8.1 IP traffic generated inside the NT for communication with the network These functionalities are for the support of IP traffic between NT (applies to xDSL and PtP FTTH NTs only - not required for a pure GPON NT which is fully be managed by OMCI) and network, for Remote Management communication between NT and remote ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 8.2 IP traffic between LAN and WAN | 118) The NT must be fully transparent to IP traffic coming from the LAN. 119) It must be possible to enable the p-bit tagging based on the DSCP bits of the IP ToS byte for untagged ingress traffic, according to the following rules: ETSI ETSI TS 102 973 V1.1.1 (2008-09) 21 DSCP 802.1p 0x00 0 0x08 1 0x10 2 0x18 3 0x20 4 ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 9 LAN-WAN QoS functionalities | This applies to the upstream data flow because the QoS policies of the downstream traffic are applied in the first access network element that forwards the IP traffic. 120) Traffic classification on the aggregated LAN ingress traffic based on the following physical/L2 parameters: - VLAN-ID (for VLAN tagged traffic only... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 10 Security | 133) [GPON] AES encryption as defined in ITU-T Recommendation G.984.3 [i.10] is required for the unicast services in the downstream direction. 134) [GPON] The ONT must be able to filter upstream IGMP requests based on white and black lists of multicast groups (defined by both source and destination IP address and place... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11 Management | If the remote management option is included in the required set of functionalities, this may be implemented either using a full-feature TCP/IP based solution, as specified in clause 11.3 TCP/IP based remote management and applicable to xDSL, or an access-specific OAM solution, as specified in clause 12.1 for all access... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.1 Remote physical layer monitoring capabilities | 135) [GPON]The NT WAN interface must provide physical loopback capability, that are activated on remote action by the LT and enable the operator to differentiate a physical media outage from an NT failure. On WAN interfaces two loopback points can be identified, one at the transceiver end, the other on the ONT backplan... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.2 Local management and configuration | 141) No external Console port must be present. 142) [xDSL and PtoP] It must not be possible to access locally the NT using any management interface over LAN ports (i.e. web-based GUI, SSH, telnet, etc.). [GPON] Because GPON is a shared media, a means is needed to configure through each ONT a password called hereafter "... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.3 TCP/IP based remote management | The following requirements apply in case remote management option is required and based on a TCP/IP solution; in any case these do not apply to GPON NT which is fully managed by OMCI. 155) Remote management, using DSL Forum CWMP protocol (TR-069 [i.29]). 156) For ensuring a secure CWMP communication between the NT and ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.4 Alternative management solution for Point-to-Point FTTH | This clause describes the requirements for an alternative management solution that for configuration and fault management tasks does not rely on communications with a remote management system. This solution ensures robust, trouble free and secure operation of the NT and does not require integration with the OSS layer. ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.5 Remote management in optical networks (GPON) | OMCI (ONT Management and Control Interface) is the management protocol used for optical network management in GPON technologies. 165) ONTs/ONUs complies with the applicable sections of ITU-T Recommendation G.984.4 [i.10] and referenced documents. All applicable managed entities in table 1 of ITU-T Recommendation G.984.... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 11.6 Physical alarms | Physical alarms for all networks 167) The system is able to support dry loop to report power alarm (dying gasp). 168) The system is able to support dry loop to report intrusion alarm. Physical alarms in optical networks (GPON) 169) ONTs/ONUs complies with the applicable sections of ITU-T Recommendation.G.984.3 [i.10]. ... |
278839146805a1a273ac1ce2e5ff7d7a | 102 973 | 13 Factory default configuration | Only generic statements have to be reported in this clause, letting every Operator define the localized factory default configuration. 175) Flexibility do define a default setting of parameters in compliance with the needs of the specific operator is required. ETSI ETSI TS 102 973 V1.1.1 (2008-09) 28 Annex A (informati... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 1 Scope | The present document specifies a security architecture for Intelligent Transport System (ITS) communications. Based upon the security services defined in ETSI TS 102 731 [4], it identifies the functional entities required to support security in an ITS environment and the relationships that exist between the entities th... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 2 References | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 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... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 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... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 3 Definitions and abbreviations | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 102 731 [4], IETF RFC 4949 [i.6] and the following apply: identifier: attribute or a set of attributes of an entity which uniquely identifies the entity within a certain context security management: operations that support acquiring or... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI EN 302 665 [1], ETSI TS 103 301 [9] and the following apply: AA Authorization Authority CA Co-operative Awareness CAM Co-operative Awareness Message CN Co-operative Navigation CRL Certificate Revocation List CS Communities Services CSM Co-operati... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4 ITS reference architecture | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.1 Background | ETSI EN 302 665 [1] describes an ITS station architecture based upon four processing layers identified as follows: • Access Layer; • Networking & Transport Layer; • Facilities Layer; and • Applications Layer. These horizontal layers are bounded on each side by a vertical Management layer and a Security layer (figure 1)... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2 ITS applications groups | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.1 ITS applications groups and their communication characteristics | ETSI TR 102 638 [i.1] defines the basic set of ITS applications which it divides into groups according to the functionality provided. Based on this a further analysis in ETSI TR 102 863 [i.2] takes into account some additional sources. The resulting list of functional groupings from this analysis is shown in table 1. A... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.2 Cooperative awareness | The purpose of cooperative awareness messages is to allow ITS users to provide other users with information regarding their status and environment in order to improve road safety. They can be categorized as follows: • broadcast; • single-hop; • time-critical; • having low data content; • transmitted frequently; • vehic... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.3 Static local hazard warning | Static local hazard warning messages are broadcast by fixed roadside ITS stations usually to provide continuous information regarding a specific static condition which is relevant to road users. They can be categorized as follows: • broadcast only from a roadside ITS-S; • single-hop; • time-critical; • having low data ... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.4 Interactive local hazard warning | Interactive local hazard warning messages are broadcast followed by a unicast session to provide direct cooperation in specific hazardous situations. The basic model for these applications is that station A receives a cooperative awareness message from station B and then returns a message to station B requesting that i... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.5 Area hazard warning | Area hazard warning messages are broadcast and then forwarded by the receiving stations to form a geocast. They are sent event-driven to inform about a specific event or a specific condition to improve road safety. They can be categorized as follows: • broadcast; • multi-hop with geocasting; • time-critical; • low data... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.6 Advertised services | Advertised services refer to services where a provider unit sends out a message of a particular type advertising that the service is being offered and an ITS-S with the corresponding user application connects to the service. This description is based on WAVE Service Announcements (WSAs) as described in IEEE 1609.3 [i.3... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.7 Local high-speed unicast service | Local high-speed unicast services are provided directly to vehicles that may be moving at a high speed. They can be categorized as: • unicast; • single-hop; • time critical; • medium data content; • frequently advertised then used as needed; • local sessions. EXAMPLE: Traffic information and recommended itinerary (serv... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.8 Local multicast service | Local multicast services are similar to local unicast service but using multicast communication. They can therefore be categorized as: • multicast; • single-hop; • time critical; • medium data content; • frequently advertised then used as needed; • local sessions. EXAMPLES: Traffic information and recommended itinerary... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.9 Low-speed unicast service | Low-speed unicast services are non time-critical services consumed at low (vehicle) speeds. They can be categorized as: • unicast; • single-hop; • low time-criticality; • medium to large data content; • low frequency; • restricted local or remote session. EXAMPLES: ITS local electronic commerce, Media downloading, Insu... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.10 Distributed (networked) service | Distributed services are non-time critical subscription services that are intended to be consumed by the user over long periods such as the duration of a journey or even the lifetime of a vehicle: They can be categorized as: • unicast; • single-hop; • low time-criticality; • medium to large data content; • low frequenc... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.2.11 Multiple Applications | An ITS-S may run multiple applications. Each application will have its own security requirements as described above. However, the combination of applications may introduce additional threats to the communications security, such as: • Privacy - the combination of applications that an ITS-S runs may act as an identifier.... |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3 Security requirements of ITS application groups | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.1 Security requirements of cooperative awareness | |
79491d3f4dfdee6749c7487774681445 | 102 940 | 4.3.1.1 Authentication and Authorization | Cooperative awareness applications are used to enhance traffic safety. In addition to authenticity and integrity, authorization is required in order to restrict access to legitimate users. Different levels of authentication may be needed depending on the application and the requirements for participation. Consequently,... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.