hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.3 Ego Position Vector | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.3.1 General | A GeoAdhoc router shall maintain a local data structure that holds position-related information for the local GeoAdhoc router, i.e. the ego position vector EPV. The data elements of a EPV are specified in clause 8.3.2 and the maintenance of the location table in clause 8.3.3. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.3.2 Minimum data elements | The EPV shall contain at least the following data elements: 1) Geographical position POS_EPV. 2) Speed S_EPV. 3) Heading H_EPV. 4) Timestamp TST_EPV indicating when the geographical position POS_EPV was generated. 5) Accuracy of the geographical position PAI_EPV. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.3.3 Maintenance | At start-up, all data elements of the EPV shall be initialized with 0 to indicate an unknown value. The EPV shall be updated with a frequency of the GN protocol constant itsGnMinUpdateFrequencyEPV or higher. In case of a stationary ITS-S, the timestamp of the EPV shall be updated with a frequency of the GN protocol con... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.4 Sequence number | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.4.1 General | Each GeoAdhoc router shall maintain a local sequence number per GAGH that determines the Sequence Number (SN) field of the next GeoNetworking packet to be transmitted. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.4.2 Maintenance | For a GAGH, the SN shall be initialized to 0. For every GeoNetworking packet P, the sequence number SN(P) shall be incremented as follows: ( ) MAX SN P SN P SN _ mod 1 ) ( ) ( + = with SN(P) being the sequence number of the GeoNetworking packet and SN_MAX the largest possible sequence number. The resulting sequence num... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.5 Location service packet buffer | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.5.1 General | Upon invocation of the LS (clause 10.2.4) by a GAGH, a GeoAdhoc router shall queue a GeoNetworking packet in a LS packet buffer for the sought destination until the LS is completed. Subsequent GeoNetworking packets, which are processed while the LS is in progress, shall also be buffered (see clause 10.2.4). |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.5.2 Buffer size | The LS packet buffer shall have a minimum size of the value stored in the GN protocol constant itsGnLocationServicePacketBufferSize. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.5.3 Maintenance | The LS packet buffer shall work as follows: 1) GeoNetworking packets arriving at the LS packet buffer for a destination (GN_ADDR of a certain ITS-S) shall be queued at the tail of the queue. 2) When a new GeoNetworking packet arrives at the LS packet buffer and exceeds the buffer capacity (buffer overflow), GeoNetworki... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.6 Forwarding packet buffer | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.6.1 General | A GeoAdhoc router shall use forwarding packet buffers to temporarily keep packets in a GeoAdhoc router during the forwarding process. A GeoAdhoc router shall maintain the following forwarding packet buffers: 1) UC forwarding packet buffer to buffer GUC packets per GN_ADDR per GAGH. 2) BC forwarding packet buffer to buf... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.6.2 Buffer size | The UC forwarding packet buffer shall have a minimum size given by the value of the GN protocol constant itsGnUcForwardingPacketBufferSize. The BC forwarding packet buffer shall have a minimum size given by the value of the GN protocol constant itsGnBcForwardingPacketBufferSize. The CBF packet buffer shall have a minim... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 8.6.3 Maintenance | The UC forwarding packet buffer and the BC forwarding packet buffer shall work as follows: 1) GeoNetworking packets arriving at the forwarding packet buffer shall be queued at the tail of the queue. 2) When a new GeoNetworking packet arrives at the forwarding packet buffer and exceeds the buffer capacity, GeoNetworking... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9 GeoNetworking packet structure and formats | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.1 Overview | This clause specifies the structure and the format of the GeoNetworking packet. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.2 Packet structure | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.2.1 General | As specified in ETSI TS 103 836-3 [i.1], the GeoNetworking protocol is either used in the GeoNetworking protocol stack or in the protocol stack that combines the GeoNetworking protocol and IPv6. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.2.2 Overall packet structure | A GeoNetworking packet is part of the overall frame/packet structure depicted in figure 4 (without security) and figure 6 (with security), respectively: 1) The Access layer header is the header of the specific technology at the Access layer with which the packet is transmitted. NOTE 1: The Access layer header is not sp... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.2.3 Maximum Transmit Unit | The Maximum Transmit Unit (MTU), which the GeoNetworking protocol supports via the TRANSP_CORE interface, i.e. the MTU_GN depends on the MTU of the Access layer technology (MTU_ALI) over which the GeoNetworking packet is transported. In particular, MTU_GN shall be less or equal to MTU_ALI reduced by the size of the lar... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.3 GeoNetworking header structure | The GeoNetworking header shall be comprised of a Basic Header, Common Header and an optional Extended Header (figure 5). Basic Header Common Header Extended Header (optional) Figure 5: GeoNetworking header structure Basic Header, Common Header and Extended Header are specified in clause 9.6, clause 10.3.6 and clause 9.... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.4 GeoNetworking Secured Packet | The overall packet structure may be protected by security services, by digital signatures, certificates, and by encryption.With enabled security (GN protocol constant itsGnSecurity is set to ENABLED), the overall packet structure is depicted in figure 6. Security operations are executed by the security entity via the G... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5 Position vectors | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.1 Overview | For simplicity, a set of position-related fields of the GeoNetworking header are subsumed to a Position Vector (PV). Two types of PV are defined: 1) Long position vector as specified in clause 9.5.2. 2) Short position vector as specified in clause 9.5.3. ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 23 |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.2 Long Position Vector | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.2.1 Structure | The Long Position Vector (LPV) shall consist of the fields specified in 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 GN_ADDR TST Lat Long PAI S H Figure 7: Long Position Vector |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.2.2 Fields | The Long Position Vector (LPV) shall consist of the fields as specified in table 2. Table 2: Fields of Long Position Vector Field # Field name Octet/bit position Type Unit Description First Last 1 GN_ADDR Octet 0 Octet 7 64 bit address n/a Network address for the GeoAdhoc router entity in the ITS-S 2 TST Octet 8 Octet ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.3 Short Position Vector | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.3.1 Structure | The Short Position Vector (SPV) shall consist of the fields specified in figure 8. 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 GN_ADDR TST Lat Long Figure 8: Short Position Vector |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.5.3.2 Fields | The Short Position Vector (SPV) shall consist of the fields as specified in table 3. Table 3: Fields of Short Position Vector Field # Field name Octet/bit position Type Unit Description First Last 1 GN_ADDR Octet 0 Octet 7 64 bit address n/a GN_ADDR field as specified in table 2 2 TST Octet 8 Octet 11 32 bit unsigned i... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.6 Basic Header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.6.1 Composition of the Basic Header | The Basic Header shall be present in every GeoNetworking packet and consists of the fields as depicted in figure 9. 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 Version NH Reserved LT RHL Figure 9: Basic Header format ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 25 |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.6.2 Fields of the Basic Header | The Basic Header shall carry the fields as specified in table 4. Table 4: Fields of the Basic Header Field # Field name Octet/bit position Type Unit Description First Last 1 Version Octet 0 Bit 0 Octet 0 Bit 3 4 bit unsigned integer n/a Identifies the version of the GeoNetworking protocol 2 NH Octet 0 Bit 4 Octet 0 Bit... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.6.3 Encoding of the NH field in the Basic Header | For the Next Header (NH) field in the Basic Header the values as specified in table 5 shall be used. Table 5: Next Header (NH) field in the GeoNetworking Basic Header Next Header (NH) Encoding Description ANY 0 Unspecified Common Header 1 GeoNetworking Common Header as specified in clause 10.3.6 Secured Packet 2 GeoNet... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.6.4 Encoding of the LT field | The Lifetime (LT) field shall indicate the maximum tolerable time a packet may be buffered until it reaches its destination. NOTE 1: This parameter is relevant for safety and traffic efficiency information that do not have strict real-time requirements. In sparse network scenarios, this lifetime may also be used to avo... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7 Common Header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7.1 Composition of the Common Header | The Common Header shall be present in every GeoNetworking packet and consists of the fields as depicted in figure 11. 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 11: Common Header format |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7.2 Fields of the Common Header | The Common Header shall carry the fields as specified in table 7. Table 7: Fields of the Common Header Field # Field name Octet/bit position Type Unit Description First Last 1 NH Octet 0 Bit 0 Octet 0 Bit 3 4 bit unsigned integer n/a Identifies the type of header immediately following the GeoNetworking headers as speci... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7.3 Encoding of the NH field in the Common Header | For the Next Header (NH) field in the Common Header the values as specified in table 8 shall be used. Table 8: Next Header (NH) field in the GeoNetworking Common Header Next Header (NH) Encoding Description ANY 0 Unspecified BTP-A 1 Transport protocol (BTP-A for interactive packet transport), see ETSI TS 103 836-5-1 [3... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7.4 Encoding of the HT and HST fields | For the Header Type (HT) and the Header Sub-Type (HST) fields in the Common Header the values as specified in table 9 shall be used. Table 9: GeoNetworking Header Types and Header Sub-Types Header Type (HT) Header Sub-Type (HST) Encoding Description ANY 0 Unspecified UNSPECIFIED 0 Unspecified BEACON 1 Beacon UNSPECIFIE... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.7.5 Encoding of the TC field | The TC field shall consist of the fields as depicted in figure 12. 0 1 2 3 4 5 6 7 SCF Reserved TC ID Figure 12: Traffic Class (TC) field composition Table 10: TC field in the GeoNetworking Common Header Field # Field name Octet/bit position Type Unit Description First Last 1 SCF Bit 0 Bit 0 Bit n/a Indicates whether t... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8 GeoNetworking packet header types | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.1 Overview | The following GeoNetworking packet header types are defined: 1) GUC packet header (clause 9.8.2). 2) TSB packet header (clause 9.8.3). 3) SHB packet header (clause 9.8.4). 4) GBC and GAC packet headers (clause 9.8.5). 5) BEACON packet header (clause 9.8.6). 6) LS Request and LS Reply packet headers (clause 9.8.7 and cl... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.2 GUC packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.2.1 Composition of the GUC packet header | The GUC header shall be comprised of the Basic Header, the Common Header and the Extended Header as shown in figure 13. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. ETSI ETSI TS 103 836-4-1 V2.1.1 (2022-11) 29 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... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.2.2 Fields of the GUC packet header | The GUC packet header shall consist of the fields as specified in table 11. Table 11: Fields of the GUC packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header Octet 4 Oc... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.3 TSB packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.3.1 Composition of the TSB packet header | The TSB header shall be comprised of the Basic Header, the Common Header and the Extended Header as shown in figure 14. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. 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 SN Rese... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.3.2 Fields of the TSB packet header | The TSB packet header shall consist of the fields as specified in table 12. Table 12: Fields of the TSB packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header Octet 4 Oc... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.4 SHB packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.4.1 Composition of the SHB packet header | The SHB header shall consist of the Basic Header, the Common Header and the Extended Header as shown in figure 15. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. 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 Reserv... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.4.2 Fields of the SHB packet header | The SHB packet header shall consist of the fields as specified in table 13. Table 13: Fields of the SHB packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header Octet 4 Oc... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.5 GBC/GAC packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.5.1 Composition of the GBC/GAC packet header | The GBC and GAC packets shall have the same header structure. They are distinguished by the HT field in the Common Header. The header shall be comprised of the Basic Header, the Common Header and the Extended Header as shown in figure 16. NOTE: The Extended Header comprises all fields except the Basic Header and the Co... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.5.2 Fields of the GBC/GAC packet header | The GBC/GAC packet header shall consist of the fields as specified in table 14. Table 14: Fields of the GBC/GAC packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header Oc... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.6 BEACON packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.6.1 Composition of the BEACON packet header | A BEACON packet shall consist of the Basic Header, the Common Header, and the Extended Header as shown in figure 17. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. 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 Figu... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.6.2 Fields of the BEACON packet header | The BEACON shall consist of the fields of the Basic Header, the Common Header and the Extended Header as specified in table 15. Table 15: Fields of the BEACON packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.7 LS Request packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.7.1 Composition of the LS Request packet header | The LS Request packet header shall be comprised of the Common Header and the Extended Header as shown in figure 18. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. 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 SN Reserved... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.7.2 Fields of the LS Request packet header | The LS Request packet header shall carry the fields as specified in table 16. Table 16: Fields of the LS Request packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header O... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.8 LS Reply packet header | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.8.1 Composition of the LS Reply packet header | The LS Reply packet header shall be comprised of the Basic Header, the Common Header and the Extended Header as shown in figure 19. NOTE: The Extended Header comprises all fields except the Basic Header and the Common Header. 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 He... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 9.8.8.2 Fields of the LS Reply packet header | The LS Reply packet header shall carry the fields as specified in table 17. Table 17: Fields of the LS Reply packet header Field # Field name Octet/bit position Type Unit Description First Last 1 Basic Header Octet 0 Octet 3 Basic Header n/a Basic Header as specified in clause 9.6 Length: 4 octets 2 Common Header Octet... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10 Protocol operation | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.1 General | This clause specifies the media-independent operations of the GeoNetworking protocol. The operations include: 1) Network management: - Address configuration (clause 10.2.1); - Local position vector and time update (clause 10.2.2); - Beaconing (clause 10.2.3); - Location service (clause 10.2.4). 2) Packet handling: - GU... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2 Network management | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.0 Overview | In the Management plane of the Networking & Transport layer, network management for the GeoNetworking protocol is handled by the GN Core and the GAGHs as depicted in figure 20. The GN Core provides the GeoNetworking address and current local position and time information upon request from a GAGH as specified in clause ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1 Address configuration | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.1 General | When initialized, the GN Core shall have a self-assigned initial GeoNetworking address with the format specified in clause 6. GeoNetworking defines three methods for the configuration of the local GN_ADDR: 1) Auto-address configuration (clause 10.2.1.2); 2) Managed address configuration (clause 10.2.1.3); 3) Anonymous ... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.2 Auto-address configuration | The auto-address configuration method shall be used if the GN protocol constant itsGnLocalAddrConfMethod is set to AUTO (0). When activated, a GAGH shall assign the MID field of the local GN_ADDR from the GN protocol constant itsGnLocalGnAddr. NOTE: The setting of the GN protocol constant itsGnLocalGnAddr is implementa... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.3 Managed address configuration | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.3.1 General Requirements | The managed address configuration method shall be used if the GN protocol constant itsGnLocalAddrConfMethod is set to MANAGED (1). With managed address configuration, the GN Core is responsible for providing the MID field of the GN_ADDR. |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.3.2 Initial address configuration | At startup, a GAGH shall request an MID field for the GN_ADDR from the GN Core (see clause K.2, service primitive CORE_GAGH.request). The GN Core is responsible for generating the appropriate GeoNetworking address (see clause K.3 using the service primitive CORE_GAGH.response). |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.3.3 Address update | The update of the MID field of the local GN_ADDR may be triggered by the GN Core using an unsolicited CORE_GAGH.response to the active GAGHs. Upon reception of the CORE_GAGH.response, a GAGH shall update its local GN_ADDR. NOTE 1: For privacy reasons, the GN_ADDR may be derived from the current authorization ticket. Th... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.4 Anonymous address configuration | The anonymous address configuration method shall be used if the GN protocol constant itsGnLocalAddrConfMethod is set to ANONYMOUS (2). This method allows for configuration of anonymous addresses controlled by the security entity. The services are provided via the CORE_SEC interface. In this method, the GN Core subscrib... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.1.5 Duplicate address detection | In order to achieve uniqueness of the GeoNetworking address configuration with the auto-address configuration method, i.e. if the GN protocol constant itsGnLocalAddrConfMethod is set to AUTO (0), each GAGH shall execute the following operations for DAD: 1) Upon reception of a GeoNetworking packet, a GAGH compares: a) i... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.2 Ego position vector and time update | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.2.1 Overview | Ego position vector and time are set by the GN Core for the GAGH via the CORE_GAGH interface (clause K.3). |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.2.2 Ego Position Vector update | For position update, the GN Core shall send an unsolicited CORE_GAGH.response with the Ego position vector parameter (clause K.3) to the GAGHs. Upon reception of the CORE_GAGH.response with the Ego position vector parameter, the GeoAdhoc router updates its EPV (clause 8.3). As specified in clause 8.3.3, the EPV shall b... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.2.3 Time update | For time update, the GN_CORE entity sends an unsolicited CORE_GAGH.response with the Time parameter (clause K.3) to the GeoAdhoc router. Upon reception of the CORE_GAGH.response with the Time parameter, the GeoAdhoc router should set its local system time at a reasonable time interval. ETSI ETSI TS 103 836-4-1 V2.1.1 (... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.3 Beaconing | Beaconing is used to periodically advertise a GeoAdhoc router's position vector to its neighbours. Each active GAGH shall send a BEACON periodically unless the GAGH dissiminated another GeoNetworking packet that carries the GeoAdhoc router's EPV. At startup a GeoAdhoc router shall send an initial beacon to announce its... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.2.4 Location service | The location service is used if a GeoAdhoc router needs to determine the position of another GeoAdhoc router using one of its GAGH. This is the case if a GeoAdhoc router is in the process to send a T/GN6-SDU as a GUC packet to another GeoAdhoc router, i.e. from the source to the destination, and does not have the posit... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3 Packet handling | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.1 Overview | This clause defines the behaviour of the protocol in the source, forwarder and destination. Packet handling includes the procedures to determine the destination (GeoAdhoc router, geographical area) of the GeoNetworking packet, execute security functions, execute functions that are specific to the packet type and the as... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.2 Basic Header field settings | For all GeoNetworking packets, the fields of the Basic Header shall be set as specified in table 18. Table 18: Field settings for the Basic Header Field name Field setting Description Version GN protocol constant itsGnProtocolVersion Version of the GeoNetworking protocol NH 1 (Common Header) if TRANSP_CORE.request para... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.3 Basic Header processing | When a GAGH in a forwarder, receiver or destination GeoAdhoc router processes a Basic Header, the GAGH shall execute the following operations upon reception of a GeoNetworking packet: 1) check the Version field of the Basic Header: a) if the value of the Version field equals the GN protocol constant itsGnProtocolVersio... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.4 Common Header field settings | For all GeoNetworking packets, the fields of the Common Header shall be set as specified in table 20. Table 20: Field settings for the Common Header Field name Field setting Description NH 0 (ANY) if Header type HT = 1 (BEACON) 1 (BTP-A) if TRANSP_CORE.request parameter Upper protocol entity is BTP-A 2 (BTP-B) if TRANS... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.5 Common Header processing | When a GAGH (forwarder, receiver, destination) processes a Common Header, the GAGH shall execute the following operations upon reception of a GeoNetworking packet: 1) check the MHL field of the Common Header: a) compare MHL with the value of the RHL field of the Basic Header; if MHL < RHL discard the packet and omit th... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.6 Beacon packet handling | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.6.1 General | Beaconing is used to periodically advertise a GeoAdhoc router's position vector to its neighbours. A BEACON packet shall be sent periodically by each active GAGH unless the GAGH sends another GeoNetworking packet that carries the EPV. NOTE: In one possible implementation a timer is reset upon transmission of a SHB pack... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.6.2 Source operations | Upon activation, a GAGH shall execute the following operations: 1) create a GN-PDU with a Beacon packet header (clause 9.8.6): a) set the fields of the Basic Header (clause 10.3.2); b) set the fields of the Common Header (clause 10.3.4); c) set the fields of the Beacon Extended Header (table 21); Table 21: Field settin... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.6.3 Receiver operations | Receiver operations of Beacon packets are identical to the handling procedures of the SHB packet (clause 10.3.10.3) except step 8 (pass the payload of the GN-PDU to the upper protocol entity). |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7 Location service packet handling | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.1 Source operations | |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.1.1 Overview | Three cases are distinguished for the source operations: 1) source operation for initial LS Request (clause 10.3.7.1.2); 2) source operation for LS Request re-transmission (clause 10.3.7.1.3); 3) source operation for LS Reply (clause 10.3.7.1.4). |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.1.2 Operation for initial LS Request | When a source has a T/GN6-SDU to send and has no position vector information for the destination address, the source shall invoke the location service and shall execute the following operations: 1) check whether a LS for the sought GN_ADDR is in progress, i.e. the flag LS_pending is set TRUE: a) if LS_pending is TRUE f... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.1.3 Operation for LS Request re-transmission | If the timer TLS, GN_ADDR for the GN_ADDR expires, the source shall execute the following operations: 1) check the retransmit counter RTCLS, GN_ADDR: a) if the retransmit counter is less than the maximum number of LS retransmissions set by the GN protocol constant itsGnLocationServiceMaxRetrans, i.e. RTCLS, GN_ADDR < i... |
9f86761ce8ee8d8ab46b9be0c3bae757 | 103 836-4-1 | 10.3.7.1.4 Operation for LS Reply | If the source receives a LS Reply packet for the sought GN_ADDR, the source shall execute the following operations: 1) Basic Header processing (clause 10.3.3); 2) Common Header processing (clause 10.3.5); 3) execute DPD as specified in clause A.2; if the LS Reply packet is a duplicate, discard the packet and omit the e... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.