hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.3 JOIN message | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.3.1 Message overview | The JOIN message is the message sent from the participant to the RTT-session room when the user wants to join the session. This may be the AP, the PSAP-CPE or another trusted user. The JOIN message is resent if for some reason the connection between the entity and the RTT-session room is lost but the RTT session is not... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.3.2 Examples | The JOIN message is also used to reconnect to the RTT-session room in the case that the connection terminated, AP or RTT server restarted. In this case, the AP will set the since value to be the time that the AP knew it last had a connection to the RTT-session room, often this will be last received message from the RTT... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.4 ERROR message | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.4.1 Message overview | The ERROR message is sent by the RTT-session room in response to a JOIN request containing a uniqueId already in use by an active/ONLINE user in the session. The message is not intended to be visible to the end-user since either the AP or call-taker CPE will generate the uniqueId automatically. Refer to clause 7.3.4 fo... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.4.2 Error message example | { "type":"ERROR", "room":"ttRRkzORz", "reasonCode":"idInUse", "reason":"uniqueId sh4786793384881h32jh already in use", "timestamp":1574092280231 } |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.5 USER_LIST message | The USER_LIST message is sent to all participants in the RTT session whenever a user enters and leaves the RTT session. Table 10: USER_LIST message fields and description Element Name Description type "USER_LIST" The message being sent by the RTT-session room to the participants. room String identifying the RTT-session... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.6 TEXT_MESSAGE message | The text message is used by a RTT session participant to contribute to send real-time written text to other participants in the RTT session. Every message has an identifier associated with RTT-session room so that it can be uniquely identified. After the RTT-session room server receives a TEXT_MESSAGE message from a us... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 9 RTT PEMEA message and type definitions | The RTT-session room is responsible for all session logging. It shall log all messages into and out of the room. This ensures that in the event of an audit there is a trail showing that the messages were sent to a specific room participant. Message logging shall include all characters sent by a user, including backspac... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 1 Scope | The present document specifies NR-V2X PC5 and LTE-V2X PC5 specific GeoNetworking requirements, including: • fields of the GeoNetworking address; • overall packet structure for NR-V2X PC5 and LTE-V2X PC5 access layer technology; • packet handling. |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 2 References | |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-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... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-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... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 3 Definition of terms, symbols and abbreviations | |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-4-1 [1] and ETSI EN 303 798 [2] apply. |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 836-4-1 [1] apply. |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 836-4-1 [1], ETSI EN 303 798 [2] and the following apply: C-V2X Cellular Vehicle-to-Everything (or Cellular-V2X) GN GeoNetworking ITS-S ITS Station LTE-V2X Long Term Evolution based Vehicle-to-Everything MAC Medium Access Control MIB Manag... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 4 Overview | The present document specifies the media-dependent functionalities necessary to run the GeoNetworking protocol defined in ETSI TS 103 836-4-1 [1] over the LTE-V2X and NR-V2X access technologies defined in ETSI EN 303 798 [2]. The functionalities are: • Addressing, data structure extensions and field settings in the Geo... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.1 General | The Networking Services implementation using LTE-V2X and NR-V2X shall use access layer functionality for sidelink communication as defined in ETSI EN 303 798 [2]. |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.2 GeoNetworking address | As specified in ETSI TS 103 836-4-1 [1], clause 6, every GeoAdhoc router shall have a unique GeoNetworking address and use the format in Figure 1. 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 1: GeoNetworking address format as specified in ETSI TS 103 836-4-1 [1] ... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.3 Field settings in the GeoNetworking header | |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.3.1 General | The present clause specifies setting and encoding of GN header fields specific for LTE-V2X and NR-V2X access technology, i.e.: • Traffic Class (TC) field in the Common Header (clause 5.3.2). • Timing advance and position for improved synchronization. |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.3.2 Field settings in the Common Header | As specified in ETSI TS 103 836-4-1 [1], clause 9.7, the Common Header consists of the fields shown in Figure 2. 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 2: Common Header format as specified in ETSI TS 103 836-4-1 [1] As specified in ETSI... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.3.3 Field settings in the Extended Header of the SHB packet | As specified in ETSI TS 103 836-4-1 [1], clause 9.8.4, the SHB header consists of the fields shown in Figure 3. 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 [1] and specified in the present document Figure 3: The SHB packet head... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 5.3.4 Timing synchronization extension | Timing synchronization confidence shall be added to the GN messages as shown in Table 4 and Table 5. 3GPP Specifications define three synchronization sources for C-V2X: • GNSS. • Serving cell/PCell (eNB DL timing). • SyncRef UE (SLSS/PSBCH). The timing synchronization extension is used to improve synchronization qualit... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 6 General Requirements | |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 6.1 Processing on transmit | For transmission of a GN packet, the SDU Type field of the PDCP header as defined in ETSI TS 136 323 [5] and ETSI TS 138 323 [6] shall be set to 0b011 (i.e. Non-IP), and the Non-IP Type field indicates the V2X message family as defined in ETSI TS 124 386 [7] and shall be set to value 0b00000011 for the ETSI-ITS stack. ... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 6.2 Processing on receive | Processing on receive for MAC, RLC, and PDCP layers is in accordance with the corresponding protocol specification and with ETSI TS 124 386 [7]. NOTE: An ITS Station may selective process or discard (i.e. filter) MAC PDUs received via C-V2X based on the value of the DST field of the MAC header. Subsequent to successful... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 7 Security and Privacy requirements | The security entity shall have the ability to trigger SPS resource reselection. This enables the security entity to coordinate SPS resource selection with pseudonym change. Since the selected SPS resources act as a short-lived identifier, it is useful to change the SPS resource at the same time as carrying out pseudony... |
07071a8c71cbe9af18552e3a55fd5caf | 103 836-4-3 | 8 Forwarding algorithms | The following applies to NR-V2X and LTE-V2X. GeoNetworking forwarding algorithm selection procedure, Non-area forwarding algorithms and Area forwarding algorithms specified in Annex D, Annex E and Annex F respectively in ETSI TS 103 836-4-1 [1] shall be applied in the present document. Greedy Forwarding (GF) and Simple... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 1 Scope | The present document provides the specification of the Release 2 Cooperative Awareness (CA) service. This includes definition of the syntax and semantics of the Cooperative Awareness Message (CAM) and detailed specifications on the message handling. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 2 References | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 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... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 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... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 3 Definition of terms, symbols and abbreviations | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 898 [i.2], LDM given in ETSI TS 103 938 [i.7] and the following apply: basic set of applications: group of applications, supported by vehicular communication system NOTE: The basic set of applications is defined in ETSI TR 102 638 [i.1]. Cooperati... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: IF.CAM Interface between CAM service and LDM or ITS application IF.FAC Interface between CAM service and other facilities layer entities IF.N&T Interface between CAM service and ITS networking & transport layer IF.SEC Interface between CAM service a... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ASN.1 Abstract Syntax Notation 1 BSA Basic Set of Applications BTP Basic Transport Protocol C2C-CC Car to Car Communication Consortium CA Cooperative Awareness CAM Cooperative Awareness Message DCC Decentr... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 4 CA service introduction | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 4.1 Background | Cooperative Awareness Messages (CAMs) are messages exchanged in the ITS network between ITS-Ss to create and maintain awareness of each other and to support cooperative performance of vehicles using the road network. A CAM contains status and attribute information of the originating ITS-S. The content varies depending ... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 4.2 Services provided by CA service | The CA service is a facilities layer entity that operates the CAM protocol. It provides two services: sending and receiving of CAMs. The CA service uses the services provided by the protocol entities of the ITS networking & transport layer to disseminate the CAM. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 4.3 Sending CAMs | The sending of CAMs comprises the generation and transmission of CAMs. In the course of CAM generation the originating ITS-S composes the CAM, which is then delivered to the ITS networking & transport layer for dissemination. The dissemination of CAMs may vary depending on the applied communication system. CAMs may be ... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 4.4 Receiving CAMs | Upon receiving a CAM, the CA service makes the content of the CAM available to the ITS applications and/or to other facilities within the receiving ITS-S, such as a Local Dynamic Map (LDM) [i.7]. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5 CA service functional specification | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.1 CA service in the ITS architecture | The CA service is a facilities layer entity of the ITS-S architecture as defined in ETSI TS 103 898 [i.2]. It may interface with other entities of the facilities layer and with the ITS application layer in order to collect relevant information for CAM generation and to forward the received CAM content for further proce... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.2 CA service functional architecture | The CA service is part of the Application support domain of the facilities layer according to ETSI TS 102 894-1 [i.9]. Figure 2 shows the functional block diagram with the functional blocks of the CA service and interfaces to other facilities and layers, which are detailed in the following. The interfaces to other enti... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3 Interfaces of the CA service | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.1 Interface to ITS application layer | An ITS application is an application layer entity that implements the logic for fulfilling one or more ITS use cases. Example ITS applications are defined in the C2C-CC Basic System Profile [i.3], the C-Roads Release [i.4] and the C2C-CC Roadmap [i.5]. For the provision of received data the CA service provides the inte... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.2 Interface to data provisioning facilities | For the generation of CAMs, the CA service interacts with other facilities layer entities in order to obtain the required data. This set of facilities that provides data for CAM generation is referred to as data provisioning facilities. Data is exchanged between the data provisioning facilities and the CA service via t... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.3 Interface to the Networking & Transport layer | The CA service exchanges information with ITS networking & transport layer via the interface IF.N&T as depicted in Figure 2. At the originating ITS-S, the CA service shall provide the CAM embedded in a Facility-Layer Service Data Unit (FL-SDU) together with Protocol Control Information (PCI) to the ITS networking & tra... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.4 Interfaces protocol stacks of the networking & transport layer | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.4.1 Interface to the GeoNetworking/BTP stack | A CAM may rely on the services provided by the GeoNetworking/BTP stack. If this stack is used, the GN packet transport type Single-Hop Broadcasting (SHB) shall be used. In this scenario only nodes in direct communication range may receive the CAM. PCI being passed from CA service to the GeoNetworking/BTP stack shall co... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.4.2 Interface to the IPv6 stack and the combined IPv6/GeoNetworking stack | A CAM may use the IPv6 stack or the combined IPv6/GeoNetworking stack for CAM dissemination as specified in ETSI TS 103 836-3 [i.15]. NOTE: When the CAM dissemination makes use of the combined IPv6/GeoNetworking stack, the interface between the CA service and the combined IPv6/GeoNetworking stack may be identical to th... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.5 Interface to the ITS management entity | The CA service may exchange primitives with management entity of the ITS-S via the IF.Mng interface as depicted in Figure 1. In case of the ITS-G5 access layer, an originating ITS-S the CA service gets information for setting the T_GenCam_DCC from the management entity defined in clause 6.1.3 via the IF.Mng interface, ... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 5.3.6 Interface to the ITS security entity | The CA service may exchange primitives with the security entity of the ITS-S via the IF.Sec interface as depicted in Figure 1 using the IF.Sec interface provided by the security entity as depicted in Figure 2. NOTE: Specifications of the IF.Sec and the corresponding protocol are out of the scope of the present document... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6 CAM dissemination | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1 CAM dissemination concept | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.1 CAM dissemination requirements | Point-to-multipoint communication, specified in ETSI TS 103 836-3 [i.15], is used for CAMs dissemination. The CAM shall be disseminated only from the originating ITS-S in a single hop to the receiving ITS-Ss located in the direct communication range of the originating ITS-S. A received CAM shall not be forwarded to oth... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.2 CA service activation and termination | CA service activation may vary for different types of ITS-S, e.g. vehicle ITS-S, road side ITS-S, personal ITS-S. As long as the CA service is active, the CAM generation shall be triggered and managed by the CA service. For vehicle ITS-S, the CA service shall be activated with the ITS-S activation. The CA service shall... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.3 CAM generation frequency management for vehicle ITS-Ss | The CAM generation frequency is managed by the CA service; it defines the time interval between two consecutive CAM generations. The upper and lower limits of the transmission interval are set as follows: • The CAM generation interval shall not be less than T_GenCamMin = 100 ms. This corresponds to the CAM generation r... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.4 CAM generation frequency management for RSU ITS-Ss | The CAM generation frequency for RSU ITS-Ss defined by the time interval between two consecutive CAM generations shall be set in such a way, that at least one CAM is transmitted while a vehicle is in the communication zone of the RSU ITS-S and that an inlineP2pcdRequest for an unknown authorization authority certificat... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.5 CAM time requirement | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.5.1 CAM generation time | Besides the CAM generation frequency the time required for the CAM generation and the timeliness of the data taken for the message construction are decisive for the applicability of data in the receiving ITS-Ss. In order to ensure proper interpretation of received CAMs, each CAM shall be time-stamped. NOTE: An acceptab... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.1.5.2 CAM Time stamp | The following requirements shall apply: • The time stamp given in the vehicle ITS-S CAM shall correspond to the time at which the reference position of the originating ITS-S given in this CAM was determined. The format and range of the time stamp is defined in ETSI TS 102 894-2 [1]. • The time stamp given in the RSU IT... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2 CAM dissemination constraints | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2.1 General Confidence Constraints | Several data elements of the CAM may vary with regard to accuracy or confidence. These confidence constraints are presented in the data element and data frame definitions as specified in annex A of the present document and in ETSI TS 102 894-2 [1]. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2.2 Security constraints | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2.2.1 Introduction | Clause 6.2.2 is applicable to ITS stations that use the trust model according to ETSI TS 102 940 [i.16] and ITS certificates according to ETSI TS 103 097 [3]. NOTE: For other scenarios, the trust model and the mechanisms for trust enforcement for inter-connected ITS stations can agreed among participating actors. The s... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2.2.2 Service Specific Permissions (SSP) | CAMs shall be signed using private keys associated to Authorization Tickets that contain SSPs of type BitmapSsp as specified in ETSI TS 103 097 [3]. The CAM-SSP octet scheme allows the SSP format to accommodate current and future versions of the present document. The octet scheme is constructed out of three octets as i... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 6.2.3 General priority constraints | If the GeoNetworking / BTP stack is used, the priority constraint is given by the Traffic Class as specified in ETSI TS 103 836-4-1 [4]. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7 CAM Format Specification | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.1 General structure of a CAM PDU | A CAM is composed of one common ITS PDU header and multiple containers, which together constitute a CAM. The ITS PDU header is a common header that includes the information of the protocol version, the message type and the ITS-S ID of the originating ITS-S. For vehicle ITS-Ss a CAM shall comprise one basic container an... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.2 ITS PDU header | The ITS PDU header shall be as specified in ETSI TS 102 894-2 [1]. Detailed data presentation rules of the ITS PDU header in the context of CAM shall be as specified in annex A. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.3 Basic container | The basic container provides basic information of the originating ITS-S: • type of the originating ITS-S; • the latest geographic position of the originating ITS-S as obtained by the CA service at the CAM generation. The basic container shall be present for CAM generated by all ITS-Ss implementing the CA service. Detai... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.4 Vehicle ITS-S containers | All CAMs generated by a vehicle ITS-S shall include at least a High Frequency vehicle (Vehicle HF) container, and optionally a Low Frequency vehicle (Vehicle LF) container. The Vehicle HF container contains all fast-changing (dynamic) status information of the vehicle ITS-S such as heading or speed. The Vehicle LF cont... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.5 RSU ITS-S containers | RSU ITS-S CAMs shall provide at least one HF container. Additional LF containers may be added. |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.6 CAM format and coding rules | |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.6.1 Common data dictionary | The CAM format makes use of the common data dictionary as defined in ETSI TS 102 894-2 [1]. Where applicable, DEs and DFs that are not defined in the present document shall be imported from the common data dictionary as specified in ETSI TS 102 894-2 [1]. NOTE: Detailed descriptions of all DEs and DFs in the context of... |
8f9a862c261b9147c4d1cc239edecb76 | 103 900 | 7.6.2 CAM data presentation | The CAM format is presented in ASN.1. Unaligned Packed Encoding Rules (UPER) as defined in Recommendation ITU-T X.691/ISO/IEC 8825-2 [2] shall be used for CAM encoding and decoding. The ASN.1 representation of CAM shall be as specified in annex A of the present document. ETSI ETSI TS 103 900 V2.2.1 (2025-02) 23 Annex A... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 1 Scope | The present document specifies the Release 2 of the GeoNetworking protocol. Compared to the Release 1 specification, Release 2 primarily adds support for multi-channel operation. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 2 References | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-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... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-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... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 3 Definition of terms, symbols and abbreviations | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-3 [i.1], ETSI TS 103 697 [i.2] and the following apply: destination: receiver that processes a packet and delivers it to upper protocol entities, but does not relay the packet to other GeoAdhoc routers forwarder: GeoAdhoc router that processes... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 697 [i.2] and the following apply: ALI_ADDR Address of the Access Layer instance that identifies the ITS-S at the link layer protocol entity in the Access Layer GEO_MAX Maximum size of the GeoNetworking packet header H(GN_ADDR) Heading of the IT... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 836-3 [i.1], ETSI TS 103 697 [i.2] and the following apply: ALI Access Layer Instance AliID Access layer instance Identifier ARH ALI Request Handler ASN Abstract Syntax Notation BC BroadCast BTP Basic Transport Protocol CBF Contention-Base... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 4 Services provided by the GeoNetworking protocol | The GeoNetworking protocol is a network protocol that resides in the Networking & Transport layer. Requirements on the GeoNetworking protocol are specified in ETSI TS 103 836-3 [i.1]. It is executed in the ad hoc router, specifically in the GeoAdhoc router. It provides the transport of packets in the ITS ad hoc network... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 5 Format convention | The basic convention for the specification of packet formats is illustrated in figure 2. The bits are grouped into octets. The bits of an octet are always shown horizontally and are numbered from 0 to 7. Up to 4 octets are shown horizontally; multiple sets of 4 octets are grouped vertically. Octets are numbered from 0 ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 6 GeoNetworking address | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 6.1 General | Every GeoAdhoc router, irrespective of the number of GAGHs, shall have a unique GeoNetworking address. This address shall be used in the header of a GeoNetworking packet and identify the communicating GeoNetworking entities. In order to ensure the uniqueness of the GeoNetworking address, duplicate detection as specifie... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 6.2 GeoNetworking address format | The format of the GeoNetworking address shall be as described in figure 3. 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 3: GeoNetworking address format ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 16 |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 6.3 Fields of the GeoNetworking address | The GeoNetworking address shall be comprised of the fields specified in table 1. Table 1: Fields of the GeoNetworking address Field # Field name Octet/bit position Type Description First Last 1 M Octet 0 Bit 0 Octet 0 Bit 0 1 bit unsigned integer This bit allows distinguishing between manually configured network addres... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 7 Security and privacy | The GeoNetworking protocol may exchange information with the security entity via the CORE_SEC and GAGH_SEC (see figure 1) interfaces when required. ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 17 |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8 Data structures | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.1 General | A GeoAdhoc router shall maintain different types of local data structures per GAGH, i.e.: • location table (clause 8.2); • sequence number (clause 8.4); • location service packet buffer (clause 8.5); • forwarding packet buffer (clause 8.6). A GeoAdhoc router shall also maintain a data structure for the ego position vec... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.2 Location table | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.2.1 General | A GeoAdhoc router shall maintain a local data structure, referred to as Location Table (LocT). This data structure holds information about other ITS-Ss received by the same GAGH that execute the GeoNetworking protocol. The data elements of a location table entry are specified in clause 8.2.2 and the maintenance of the ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.2.2 Minimum data elements of a Location Table Entry | A Location Table Entry (LocTE) shall contain at least the following data elements: • GeoNetwork address of the ITS-S GN_ADDR. • Link layer address of the ITS-S. • Type of the ITS-S (e.g. vehicle ITS-S, roadside ITS-S). • Version of the GeoNetworking protocol used by the ITS-S. • Position vector PV, i.e. Long Position V... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.2.3 Maintenance of the Location Table | The entries in the location table shall be soft-state, i.e. entries are added with a lifetime T(LocTE) set to the value of the GN protocol constant itsGnLifetimeLocTE and shall be removed when the lifetimes expire. The flag LS_PENDING(GN_ADDR) shall be soft-state, i.e. it shall be unset when the flag is not renewed wit... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.