hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, Table 7 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 7: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsMbr_ Module containing types ... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** TC_MRS_S... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.3.5 Test Case (TC) identifier | Table 8 shows the test case naming convention, which follows the same naming convention as the test purposes. Table 8: TC naming convention Identifier TP_<root>_<tgt>_<gr>_<sub-gr> <sn>_<x> Sub-Group Category <root> = root MRS <tgt> = target ITSS IUT is an OBU RSU IUT is an RSU MA General behaviour <gr> = group SEC Sec... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.4 On line documentation | The T3D [i.10] tool enables providing on-line documentation browser in HTML, by tagging TTCN-3 comments. These tags are defined in Table 9. Table 9: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece o... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 1 Scope | The present document specifies the media-dependent functionalities for GeoNetworking defined in ETSI TS 103 836-4-1 [i.1] over ITS-G5 defined in ETSI EN 303 797 [i.2] as a network protocol for ad hoc routing in vehicular environments. |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 2 References | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-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... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-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... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 3 Definition of terms, symbols and abbreviations | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-4-1 [i.1], ETSI EN 303 797 [i.2] and the following apply: 1-hop channel busy ratio: highest local channel busy ratio that the ego ITS station has received from its 1-hop neighbourhood over a certain time 2-hop channel busy ratio: highest 1-hop... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 836-4-1 [i.1], ETSI EN 303 797 [i.2] and the following apply: CBR_L_0_Hop Local channel busy ratio for a specific frequency channel for ego ITS station CBR_L_1_Hop Highest received value of CBR_R_0_Hop CBR_L_2_Hop Highest received value of CBR_R... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 836-4-1 [i.1], ETSI EN 303 797 [i.2] and the following apply: LocTEX Location Table Entry eXtension |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 4 Overview | The present document specifies the media-dependent functionalities necessary to run the GeoNetworking protocol defined in ETSI TS 103 836-4-1 [i.1] over the ITS-G5 access technology defined in ETSI EN 303 797 [i.2]. The functionalities are: • Decentralized Congestion Control (DCC) at the networking & transport layer fo... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 5.1 General | An ITS-S operating the ITS-G5 access technology supports Decentralized Congestion Control (DCC) to ensure that the radio channel is not congested by too many transmissions within a certain geographical range. The DCC functionality is distributed among the entities DCC_FAC, DCC_NET, DCC_ACC and DCC_CROSS at the differen... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 5.2 Maintenance of DCC variables | If DCC_NET is present, it shall maintain the following DCC variables: • CBR_L_0_Hop; • CBR_L_1_Hop; • CBR_L_2_Hop; • CBR_R_0_Hop; ETSI ETSI TS 103 836-4-2 V2.1.1 (2025-04) 10 • CBR_R_1_Hop; • CBR_G; and • CBR_Target. The CBR variables are described in detail in table 1. Table 1: Description of DCC variables in DCC_NET ... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 5.3 Calculation of the global channel busy ratio CBR_G | To calculate CBR_G, the following steps shall be executed at every T_Trig: The value of T_Trig equals the GeoNetworking protocol constant itsGNCBRGTriggerInterval. Within the trigger interval T_Trig, all ITS-S shall start with a random time offset. The values of CBR_L_1_Hop(0) and CBR_L_2_Hop(0) shall be initialized to... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 5.4 DCC_NET | If GeoNetworking over ITS-G5 is used, a DCC_NET entity shall be present. The DCC_NET entity shall process the local CBR value, the CBR target value, and optionally the TX power level upper limit of each individual used radio channel. The service primitives and parameters for the interface between DCC_NET and the DCC_CR... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.1 GeoNetworking address | As specified in ETSI TS 103 836-4-1 [i.1], clause 6, every GeoAdhoc router shall have a unique GeoNetworking address and use the format in figure 5. ETSI ETSI TS 103 836-4-2 V2.1.1 (2025-04) 12 0 1 2 3 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 M ST Reserved MID MID Figure 5: GeoNetworking address ... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.2 Location table extensions for ITS-G5 | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.2.1 General | This clause specifies media-dependent extension to the Location Table Entry (LocTE) for GN over ITS-G5, following the structure specified in ETSI TS 103 836-4-1 [i.1], clause 8.1. |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.2.2 Definition of additional data elements for the location table entry | If DCC_NET (see clause 5) is present, the location table of the GeoAdhoc router shall include the extensions - named Location Table Entry Extension for ITS-G5 (LocTEX-G5) - for GN neighbours on ITS-G5 interfaces, as follows: • Timestamp (local to ego station) of the last update of the LocTEX-G5, TST_G5(GN_ADDR). • Time... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.2.3 Maintenance of additional data elements for the location table entry | The data elements in the LocTEX-G5 shall be updated as specified in ETSI TS 103 836-4-1 [i.1], clause 7.1 and the following additions: • The data elements in the LocTEX-G5 shall only be updated for received GeoNetworking SHB packets as specified in ETSI TS 103 836-4-1 [i.1], clause 8.8.4. • The data elements in the Loc... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.3 Field settings in the GeoNetworking header | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.3.1 General | The present clause specifies setting and encoding of GN header fields specific for ITS-G5 access technology, i.e.: • Traffic Class (TC) field in the Common Header (clause 6.3.2); • DCC-MCO field in the Extended Header of the SHB packet (clause 6.3.3). |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.3.2 Field settings in the Common Header | As specified in ETSI TS 103 836-4-1 [i.1], the Common Header consists of the fields shown in figure 6. The Traffic Class Identifier (TC ID) is transmitted in the TC field. 0 1 2 3 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 NH Reserved HT HST TC Flags PL MHL Reserved Figure 6: Common Header format a... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.3.3 Field settings in the Extended Header of the SHB packet | As specified in ETSI TS 103 836-4-1 [i.1], clause 9.8.4, the SHB packet header carries a 4-byte, reserved field for media-dependent functionality (figure 7). 0 1 2 3 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Basic Header Common Header SO PV Reserved by ETSI TS 103 836-4-1 [i.1] and specified in th... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 6.4 EtherType | The GeoNetworking protocol over ITS-G5 access technology as specified in ETSI TS 103 836-4-1 [i.1] and in the present document shall use the EtherType 0x8947. NOTE: According to ETSI EN 303 797 [i.2] clause 4.5, for ITS-G5 the Subnetwork Access Protocol (SNAP) and the EtherType Protocol Discrimination (EPD) are used. E... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 7 Extensions of packet handling algorithms for ITS-G5 | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 7.1 General | ETSI TS 103 836-4-1 [i.1], clause 10.3 "Packet handling" defines the behaviour of the GN protocol for handling of packets. The present clause specifies extensions for the packet handling of SHB packets for the transmission of ITS-G5 access technology. NOTE: For other packet types than SHB, packet handling extensions ar... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 7.2 Extensions of SHB packet handling | |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 7.2.1 Extensions for source operations | If DCC_NET is present, on reception of a service primitive GN DATA.request with a Packet transport type parameter set to SHB, the source shall execute the following operation in step 5b) of ETSI TS 103 836-4-1 [i.1], clause 10.3.10.2 "Source operations"): • Set the DCC-MCO field, more specifically: - CBR_L_0_Hop; - CBR... |
8ebc27e6b57d9c167f706fb4f9a26e63 | 103 836-4-2 | 7.2.2 Extensions for receiver operations | If DCC_NET is present, on reception of a SHB packet, the GeoAdhoc router shall execute the following operations between step 6) and step 7) of ETSI TS 103 836-4-1 [i.1], clause 10.3.10.3 "Receiver operations": • Update the LocTEX-G5, more specifically: - TST_G5(GN_ADDR); - TST_SO_PV_G5 (GN_ADDR); - TX_POWER_G5(GN_ADDR)... |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specifications for ITS Misbehaviour Reporting service as specified in ETSI TS 103 759 [1] and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 406 [i.3]. |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 2 References | |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 3 Definition of terms, symbols and abbreviations | |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 759 [1] and ISO/IEC 9646-1 [i.1] apply. |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 3.2 Symbols | Void. |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 097 [2], ETSI TS 103 759 [1] and the following apply: PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement |
b93469e4221c144fa737e276edb76112 | 103 868-1 | 4 Conformance | A PICS pro forma which conforms to this PICS pro forma specification shall be technically equivalent to annex A of the present document and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to the present document shall: a) describe an implementation which claims to conform to ETS... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 1 Scope | The present document specifies a network architecture of communications in Cooperative Intelligent Transportation Systems (C-ITS). The network architecture is focused on, but not limited to, vehicular communication. The architecture enables a wide range of ITS applications for road safety, traffic efficiency as well as... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 2 References | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 3 Definition of terms, symbols and abbreviations | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 7498-1 [i.1] and the following apply: access network gateway: router at the edge of a network that connects an ITS station-internal network to the ITS access network, the public access network, and the private access network access router: IPv6 router... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 3.2 Symbols | Void. |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 3.3 Abbreviations | AU Application Unit AU Application Unit CAN Controller Area Network CCU Communication and Control Unit DCC Decentralized Congestion Control IP Internet Protocol ITS-S ITS-Station NEMO Network Mobility PDCP Packet Data Convergence Protocol SAP Service access points SCTP Stream Control Transfer Protocol TCP Transmission ... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 4 Network architecture for ITS stations | The network architecture comprises external and internal networks. External networks interconnect ITS stations among each other or connect ITS stations to other network entities. The following external networks are identified: • ITS ad hoc network. • Access network (ITS access network, public access network, private ac... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 6 Components of the network architecture | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 6.1 General | Main component of the network architecture is the ITS station in different instantiations, i.e.: • vehicle ITS station; • personal ITS station; • roadside ITS station; • central ITS station. ETSI ETSI TS 103 836-3 V2.1.1 (2025-08) 12 In addition to these instantiations, the ITS-S Border Router interconnects networks in... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7 ITS station protocol architecture | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.1 Protocol stack overview | The protocol stack of an ITS station (Figure 8) basically follows the ISO/OSI reference model defined in ISO/IEC 7498-1 [i.1] and defines three horizontal protocol layers, two vertical protocol entities and the ITS applications on top. This clause gives an overview of the protocol stack and focuses on networking aspect... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.2 Protocols of the ITS networking & transport layer | The ITS networking & transport layer comprises several networking and transport protocols (Figure 9). In detail, an ITS station can execute the following protocols at the ITS networking & transport layer: • GeoNetworking protocol. For usage of the GeoNetworking over different ITS access technologies, the specification ... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.3.1 Overview | For protocol stacks involving the GeoNetworking protocol and IPv6 protocols shall be assembled in one of the following ways described in clause 7.3.2, clause 7.3.3 and clause 7.3.4. The protocol stacks for other network protocols are described in clause 7.3.5. For the GeoNetworking protocol, the underlying ITS access t... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.3.2 GeoNetworking protocol stack | The GeoNetworking protocol stack may be assembled with the GeoNetworking protocol and ITS-specific transport protocols as envisaged in ETSI TS 103 636-5-1 [4] at the top of the GeoNetworking protocol as depicted in Figure 10. Figure 10: GeoNetworking protocol stack in an ITS station |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.3.3 IPv6 stack | The IPv6 stack may be assembled with the IPv6 protocol and related transport protocols UDP defined in IETF RFC 768 [10], TCP defined in IETF RFC 793 [11] and others as depicted in Figure 11. Figure 11: IPv6 stack in an ITS station ETSI ETSI TS 103 836-3 V2.1.1 (2025-08) 16 |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.3.4 Combination of the GeoNetworking protocol and IPv6 | This protocol stack combines the stacks in clause 7.3.2 and clause 7.3.3. In this protocol stack (Figure 12), IP shall run at the top of the GeoNetworking protocol as specified in ETSI TS 103 636-6-1 [5] or directly at the top of the ITS access technologies. Figure 12: Combined GeoNetworking and IPv6 stack in an ITS st... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 7.3.5 Protocol stacks for other network protocols | Further protocol stacks can be defined for other network protocols. In order to meet application and system requirements, the usage of other network protocols in parallel to the protocol stacks defined in clause 7.3.2, clause 7.3.3 and clause 7.3.4 can be restricted. |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 8 Interfaces and service access points | The ITS networking & transport layer provides services to the ITS Facility layer. In order to provide its service, the ITS networking & transport layer uses services from other layers and entities, namely the ITS access technology layer, ITS management entity and ITS security entity. In an ITS station, the following fo... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9 Framework for networking and transport protocols | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.0 General | This clause defines high-level logical functions to be considered in the design of ITS networking and transport protocols. |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1 GeoNetworking functional requirements | |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.1 Ad hoc networking | GeoNetworking shall provide ad hoc networking based on geographical addressing and geographical routing between ITS stations using short-range wireless technology. It shall allow the addressing of ITS stations based on their individual network addresses and also facilitate the addressing of geographical areas. For rout... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.2 Addressing | For packet transport, the network protocol of an ITS-Station should be addressed by a network address. The address type is protocol-specific and should include GeoNetworking addresses, IPv6 addresses and IPv4 addresses. GeoNetworking shall apply a particular concept of geographical addressing, i.e. it shall allow for c... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.3 Resource management and decentralized data congestion control | ITS applications, in particular safety-related applications, have high requirements on the reliability and the delay of the data transmission. Considering the limitations of the ITS-related frequency bands, the data load on the wireless channels can exceed the available network resources and capacity in some situations... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.4 Integration of GeoNetworking and IPv6 | The ITS ad hoc network shall provide the transport of IPv6 packets enhanced by GeoNetworking for communication among ITS stations. The delivery of IPv6 packets shall be achieved by IPv6 in GeoNetworking header tunnelling, i.e. encapsulation of IPv6 packets (header and payload) into GeoNetworking packet headers and rout... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.5 Backward compatibility to IPv4 | In principle, the communication using the Internet protocol in ITS is based on IP version 6. Backward compatibility from IPv6 to IPv4 is needed as required for legacy Internet applications that require IPv4, and Public Access Networks that are capable of IPv4 only. In order to achieve the backward compatibility, standa... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.6 Usage of multiple ITS access technologies | GeoNetworking shall be capable for routing of packets over different types of short-range wireless technologies. In case an ITS station is equipped with multiple communication interfaces of different technologies, the GeoNetworking protocol should provide mechanisms to choose the communication interface based on polici... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.1.7 Security and privacy protection | In order to provide secure communication, including authentication, authorization, integrity and non-repudiation, the GeoNetworking protocol shall support cryptographic protection based on digital signatures and certificates. Additionally, the networking operations shall be protected by plausibility checks, rate limita... |
07381f8c461e379274ba9845b0e1e86d | 103 836-3 | 9.2 Other protocol stacks | Other protocol stacks are out of scope of the present document. ETSI ETSI TS 103 836-3 V2.1.1 (2025-08) 20 History Document history V2.0.0 July 2022 Publication V2.1.1 August 2025 Publication |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 1 Scope | The present document classifies and specifies all communication scenarios that are supported by GeoNetworking. |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 2 References | |
68705b3b7dc187503fe83746808d13e5 | 103 836-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... |
68705b3b7dc187503fe83746808d13e5 | 103 836-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... |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 3 Definition of terms, symbols and abbreviations | |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-3 [i.2] apply. |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 3.2 Symbols | Void. ETSI ETSI TS 103 836-2 V2.1.1 (2024-07) 6 |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: R2R Roadside-to-Roadside R2V Roadside-to-Vehicle V2R Vehicle-to-Roadside V2V Vehicle-to-Vehicle |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 4 Classification of communication scenarios | This clause specifies the basic communication scenarios for GeoNetworking. The communication scenarios for GeoNetworking can be classified in two ways: • by connection multiplicity and addressing mode (address or location); • by direct or indirect usage of the GeoNetworking protocol. The GeoNetworking standard series i... |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5 Communication scenarios | |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5.1 General | Clauses 5.2 to 5.5 specify communication scenarios for GeoNetworking. The scenarios may be combined with each other to create more advanced communication scenarios. An example of such a communication scenario is illustrated in annex A. NOTE: The example of the advanced communication scenario does not limit the implemen... |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5.2 Point-to-Point | Communication starts at a single ITS station and ends at one ITS station. This scenario is applicable to V2V, V2R and R2V communication. Figure 1 illustrates the point-to-point communication scenario for V2V. Figure 1: An example of V2V only point-to-point communication |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5.3 Point-to-Multipoint | Communication starts at a single ITS station and ends at multiple ITS stations. This scenario is applicable to V2V, V2R and R2V communication. Figure 2 illustrates the point-to-multipoint communication scenario for V2V. NOTE: This scenario is also applicable to combinations of V2V, V2R and R2V, e.g. V2R/V and R2R/V. Fi... |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5.4 GeoAnycast | Communication starts from a single ITS station and ends at an arbitrary vehicle ITS station within a geographical area. This scenario is applicable to V2V, V2R and R2V communication. Figure 3 illustrates the GeoAnycast communication scenario for V2V, where the source of the GeoNetworking packet is located outside of th... |
68705b3b7dc187503fe83746808d13e5 | 103 836-2 | 5.5 GeoBroadcast | Communication starts from a single vehicle ITS station and ends at multiple vehicle ITS stations within a geographical area. This scenario is applicable to V2V, V2R and R2V communication. Figure 4 illustrates the GeoBroadcast communication scenario for V2V, where the source of the GeoNetworking packet is located outsid... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 1 Scope | The present document contains specifications of interoperability test descriptions to validate implementations of ETSI TS 103 324 [1]. |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 2 References | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 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... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 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... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 3 Definition of terms, symbols and abbreviations | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 324 [1] apply. |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 324 [1] apply. ETSI ETSI TS 103 926 V2.1.1 (2024-11) 6 |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 324 [1] and the following apply: EUT Equipment Under Test QE Qualified Equipment UC Use Case |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4 Requirements and configuration | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.1 Requirements | |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.1.1 Overview | The clauses 4.1.2, 4.1.3 and 4.1.4 define mandatory and optional requirements for the implementation of the ITS-S in the role of the Equipment Under Test (EUT) and in the role of the Qualified Equipment (QE) and the network sniffer. |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.1.2 Equipment under test | The EUT in the CPS interoperability tests is an ITS-S with the following mandatory requirements: • The EUT shall be able to send and receive CPMs as defined in ETSI TS 103 324 [1]. • The EUT's parameters as defined in ETSI TS 103 324 [1] shall be configurable by the test operator. The EUT shall be checked if it behaves... |
9101aaa9223d901102e3c87bbcb433e1 | 103 926 | 4.1.3 Qualified equipment | The QE in the CPS interoperability tests is an ITS-S with the following mandatory requirements: • The QE shall be able to send and receive CPMs as defined in ETSI TS 103 324 [1]. • The QE is verified to fulfil the interoperability test specification. • The QE's parameters as defined in ETSI TS 103 324 [1] shall be conf... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.