hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.2.10.2 Channel Number | The Channel Number field shall indicate the channel number to which the DCH will switch. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3 Connection Request (C-Req) | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.0 Connection Request Frame Format | Figure 13: Connection Request Frame Format The Connection Request command allows a device to request connection with a hub. This command shall only be sent by an unconnected device that wishes to connect with a hub. All nodes shall be capable of transmitting this command (though not required to be capable of receiving ... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.1 Recipient Address | The Recipient Address Field is set to the EUI-48 of the recipient of the current frame. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.2 Sender Address | The Sender Address Field is set to the EUI-48 of the sender of the current frame. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.3 Enhanced Supplement | The Enhanced Supplement field shall indicate if the node sending the Connection Request has any of the optional Enhanced Supplement modes shown in Table 11 enabled. Table 11: Mapping of Enhanced Supplement field Enhanced Supplement Field Value Support of Enhanced Supplement Multi Use Access mode b0 Enable: 1 None: 0 Hu... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.4 PHY Capability | The PHY capability field indicates the physical layer capability of the node. The mapping of the field is shown in Table 12. Table 12: Mapping of PHY Capability field PHY Capability Field Value Support of PHY Capability FEC Type b0, b1 00 None 01 (127,113) BCH 10 Reserved 11 Reserved Repetition Type b2, b3 00 None 01 2... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.5 PHY Version | The 3bit PHY version field shown in Table 13 shall indicate the version of the SmartBAN PHY specifications that the node supports. Table 13: Mapping of PHY Version field Field Value Node supporting version b0, b1, b2 000 v.1.1.1 001 v.1.2.1 010 Reserved 011 Reserved 100 Reserved 101 Reserved 110 Reserved 111 Reserved |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.6 Requested Wakeup Phase | The Requested Wakeup Phase field is set to the sequence number of the next Inter-Beacon Interval in which the sender node plans to wake up for frame reception and transmission, with the sequence number of a beacon treated as incremented by one modulo 28, from that of the previous beacon period. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.7 Requested Wakeup Period | The Requested Wakeup Period field is set to the length, in units of beacon periods, between the start of successive wakeup beacon periods in which the sender node plans to wake up for reception and transmission, starting from the one indicated in the preceding Requested Wakeup Phase field. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.8 Uplink Allocation Request | The Uplink Allocation Request field shall be structured as an Information Unit as described in clause 5.5. The Information Unit shall consist of 1 or more Information Modules which shall be formatted as in Table 14. Table 14: Information Module Field for Allocation Request Information Unit Type Number of bits Subfields... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.3.9 Downlink Allocation Request | The Downlink Allocation Request field shall be structured in the same way as the Uplink Allocation Request field as described above. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4 Connection Assignment (C-Ass) | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.0 Connection Assignment Frame Format | The Connection Assignment command allows the hub coordinator or coordinator to communicate the results of a connection attempt back to the device requesting a connection. The hub coordinator or coordinator shall only send this command to a device that is currently trying to connect. All devices shall be capable of rece... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.1 Recipient Address | The Recipient Address field is as defined in clause 6.2.3.1. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.2 Node ID | The Node ID is chosen according to Table 5. ETSI ETSI TS 103 325 V1.2.1 (2022-07) 28 |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.3 Assigned Wakeup Phase | The Assigned Wakeup Phase field is set to the sequence number of the next beacon period in which the recipient node needs to wake up for frame reception and transmission. The field in the Connection Assignment frame supersedes the Requested Wakeup Phase field in the Connection Request frame previously exchanged between... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.4 Assigned Wakeup Period | The Assigned Wakeup Period field is set to the length, in units of beacon periods, between the start of successive wakeup beacon periods in which the recipient needs to wake up for reception and transmission, starting from the one indicated in the preceding Assigned Wakeup Phase field. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.5 Assigned Supplement | The Assigned Supplement field shall indicate if the hub assigns the node to operate an optional Enhanced Supplement mode shown in Table 15. Table 15: Mapping of Assigned Supplement field Assigned Supplement Field Value Node Assigned permission Multi Access mode b0 Assigned: 1 Not assigned: 0 Hub to Hub mode b1 Assigned... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.6 Assigned PHY Capability | The PHY capability field shall indicate the physical layer capability of the node. The mapping of the field is shown in Table 16. Table 16: Mapping of Assigned PHY Capability field PHY Capability Field Value Node Assigned capability FEC Type b0, b1 00 None 01 (127,113) BCH 10 Reserved 11 Reserved Repetition Type b2, b3... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.7 Uplink Assignment | The Uplink Assignment field shall be structured as an Information Unit as described in clause 5.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 17. Table 17: Information Module Field for Allocation Assignment Information Unit Type Number of bits Subfields Number of b... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.4.8 Downlink Assignment | The Downlink Assignment field shall be structured in the same way as the Uplink Allocation Assignment field described above. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.5 Slot Reassignment (S-Ras) | The Slot Reassignment frame shall be formatted as an Information Unit as described in clause 5.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 18. Table 18: Information Module Field for Slot Reassignment Information Unit Type Number of bits Subfields Number of bits S... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.6 Disconnection Request (D-Req) | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.6.0 Disconnection Request command | The Disconnection Request command either allows a device to request disconnection from a hub or a hub to terminate the connections of specific nodes. 1) This command is sent by a connected node that wishes to disconnect from a hub. The frame is a null frame. Nodes may be capable of transmitting this command, but are no... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.6.1 Length | The Length field indicates the number of nodes whose links will be terminated. If the Length field is '00000,' it indicates that all nodes will be disconnected, and no Recipient ID fields will follow the Length field. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.6.2 Recipient ID | The Recipient ID field denotes the previously assigned Node ID of the nodes whose links will be terminated. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.2.7 Disconnection Response (D-Res) | The Disconnection Response is either sent by a hub to a node requesting disconnection or a node to a hub requesting disconnection. The D-Res frame shall have a 1 bit MAC Frame Body consisting of a single 'Disconnection Information' field. The field shall be set to '0' if the receiving Hub/node allows disconnection. If ... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.3 Control Frames (C-Frame) | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.3.1 Acknowledgement/Negative Acknowledge Frame (ACK/NACK) | The Acknowledgement and Negative Acknowledgement frames shall have zero length MAC Frame Bodies. The Acknowledgement and Negative Acknowledgement MPDU shall consist only of the MAC Header and the Frame Parity. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 6.4 Data Frames (D-Frame) | The data frame shall be of a maximum of TF,max bits. For data blocks that are greater than TF,max bits, the block shall be fragmented into multiple data frames. The calculation of TF,max can be found in ETSI TS 103 326 [1]. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7 MAC Functions | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.1 General | This clause shall describe the essential operations that are required for the functioning of a SmartBAN. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.2 SmartBAN Creation and Connection Initialization | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.2.1 SmartBAN Creation | A hub shall initiate the creation of a SmartBAN through the following steps: • The hub chooses an 8 bit BAN ID which is not currently in use by neighbouring SmartBANs. Length Bits: 5 Recipient ID 8 Recipient ID … 8 ETSI ETSI TS 103 325 V1.2.1 (2022-07) 31 • The hub chooses a Control Channel (CCH) to transmit C-Beacon. ... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.2.2 Connection Initialization | An unconnected node wishing to make a connection to the hub may follow the following procedure to join the SmartBAN: • The node may monitor the CCHs to acquire a C-Beacon with the Initial State field set to '1'. • The node may acquire the BAN ID, DCH Number, Slot Length, and the number of time slots in each Inter-Beaco... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3 Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1 Scheduled Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1.0 Scheduled Channel Access | A node and a hub by default shall employ Scheduled Channel Access in the Scheduled Access Period. Figure 17: Scheduled Channel Access |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1.1 Starting Scheduled Access | To obtain one or more new scheduled allocation, a node shall send a Connection Request (C-Req) frame in the C/M Period using Slotted Aloha Channel Access to the hub, setting the Requested Wakeup Period field in the frame to 1. To grant scheduled access, requested by the node, a hub shall send a Connection Assignment (C... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1.2 Using Scheduled Access | Upon receiving the C-Ass frame granting it scheduled access intervals, the node may transmit to or receive from the hub depending on the allocation assignment. Scheduled Channel Access shall use the slot structure described in clause 5.2.2.1 and illustrated in Figure 4. The transmitting device shall ensure that the MAC... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1.3 Modifying Scheduled Access | A node may modify the existing allocation assignment by sending another C-Req frame specifying the new requirements for the allocations. A hub may modify allocation assignments of a node by sending the node a Slot Reassignment (S-Ras) frame as described in clause 7.5. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.1.4 Ending Scheduled Access | A node may at any time end Scheduled Channel Access by sending a C-Req frame that contains Allocation Request fields with the corresponding Allocation Length field set to 0. A hub may at any time end any scheduled access of a node by signalling downlink data in the D-Beacon, and sending a C-Ass frame that contains Allo... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.2 Slotted Aloha Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.2.0 Description | A hub or a node may employ Slotted Aloha Channel Access to transmit management frames or data frames when it has not been allocated sufficient time slots in the Scheduled Access Period for its purpose. A node shall maintain a CP to facilitate channel access as described in clause 7.3.2.1. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.2.1 Starting Slotted Aloha Channel Access | A node shall start a Slotted Aloha Channel Access (SACA) session by transmitting in a time slot in the C/M Period with a probability of CP. At the beginning of each time slot in the C/M Period, a device shall choose its CP according to the following rules: • Determine the User Priority of its traffic according to Table... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.2.2 Using Slotted Aloha Channel Access | Slotted Aloha Channel Access shall use the slot structure described in clause 5.2.2.2 and illustrated in Figure 5. The transmitting device shall ensure that the MAC Frame Body has a length of less than or equal to LF,max, such that there will be sufficient time left in the time slot to accommodate the transmission of a... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.2.3 Ending Slotted Aloha Channel Access | Each session of Slotted Aloha Channel Access shall end with the end of each time slot in the C/M Period. A node may start a new session using the procedure in clause 7.3.2.1. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3 Multi-use Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.0 Description | The node and hub may employ Multi-use Channel Access to access the channel if the Multi-use Channel Access bit is set to '1' in the D-Beacon. A flowchart describing the Multi-use Channel Access algorithm is presented in annex A. ETSI ETSI TS 103 325 V1.2.1 (2022-07) 34 |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.1 Starting Multi-use Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.1.0 Description | A device shall start a Multi-use Channel Access (MCA) session by sensing for channel use in a time slot in the Scheduled Access Period or C/M Period. The sensing period, TMUA, is dependent on the type of traffic and the Access Phase that the time slot belongs to, and is listed in Table 2. At the beginning of each trans... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.1.1 Backoff Algorithm | The device may use the following procedure to obtain channel access in MCA mode. At the beginning of each transmission attempt of a new packet, a device shall set its backoff exponent (BE) to BEmin. If BEmin is set to 0, backoff will be disabled during the first transmission attempt. The device shall also maintain a Ba... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.1.2 Re-use Channel Access (RCA) | Re-use Channel Access (RCA) allows the use of an allocated slot in the Scheduled Access Period by other users when the allocated user is not using the slot. For Re-use Channel Access, the device maintains a Re-use Backoff (RBC) counter, which indicates the number of slots for the next transmission attempt. The RBC coun... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.1.3 Priority Channel Access (PCA) | A device may use Priority Channel Access (PCA) to send User Priority 3 packets in both Scheduled Access, and Control and Management Periods. In order to transmit using PCA, a device supporting PCA initializes its BE to 0 for the first transmission attempt of a new User Priority 3 packet. In addition, the device maintai... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.2 Using Multi-use Channel Access | |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.2.0 Description | Multi-use Channel Access shall use the Multi-use Access slot structure described in clause 5.2.2.3 and illustrated in Figure 6. The transmitting device shall ensure that the MAC Frame Body has a length of less than or equal to LF,max, such that there will be sufficient time left in the time slot to accommodate the tran... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.2.1 Scheduled Access Period | In the Scheduled Access Period, three types of transmission may take place. For devices with packets of User Priority 3 to send, the device may use PCA to access the channel if it supports it. For other transmissions, the device senses the channel for activity for a duration of TMUA, which depends on the user type and ... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.2.2 Control and Management Period | In the Control and Management Period, two types of transmissions may take place. For devices with packets of User Priority 3 to send, the device may use PCA to access the channel if it supports it. For other devices, it may use the Backoff Algorithm in clause 7.3.3.1.1 to access the channel. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.3.3.3 Ending Multi-use Channel Access | Each session of MCA shall end with the end of each time slot. A node may start a new session using the procedure in clause 7.3.3.1. |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.4 Supplementary Downlink Data Transmission | A hub may employ supplementary downlink data transmission to transmit data, control or management traffic to a node. Supplementary Downlink Data Transmission is initiated by the following steps: • The hub shall indicate downlink data transmission in the Downlink Data Indicator field of the D-Beacon. • The hub shall als... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.5 Slot Re-assignment | A hub shall inform a node of the new scheduled slot re-assignment through following steps: • A value of '1' in Slot Reassignment field indicates some of the nodes in the BAN will be allocated new slots, and that an accompanying D/SR List will be sent in the same D-Beacon frame. • The hub shall indicate the list of node... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 7.6 Data Channel Migration | A hub may switch the Data Channel (DCH) to a new channel. The hub shall commence the following procedure to switch DCH to a new channel: • Indicate data channel migration through channel migration field in the D-Beacon, with the new channel number and sequence number of the D-Beacon at which the change will occur. • C-... |
0cb2c723b210f3b1b3e12a82e23b9d76 | 103 325 | 8 MAC Parameters | Parameter Value Tc variable Tmin 625 µs Tsch 16 / symbol rate TIFS 150 µs ETSI ETSI TS 103 325 V1.2.1 (2022-07) 39 Annex A (normative): Multi-use Channel Access Figure A.1 describes the operation of Multi-use Channel Access algorithm. Figure A.1: Flowchart of Multi-use Channel Access ETSI ETSI TS 103 325 V1.2.1 (2022-0... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 1 Scope | The present document specifies the CPS. Conceptually, Collective Perception involves sharing safety-relevant information about the current context of the ITS-S's environment. This includes the definition of the syntax and semantics of the CPM and the specification of the data and message handling of the CPM to increase... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 2 References | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 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... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 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... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 3 Definition of terms, symbols and abbreviations | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 3.1 Terms | For the purposes of the present document, the following terms apply: central ITS-S: ITS-S in a backend, e.g. traffic control centre, traffic management centre, or cloud system from road authorities, ITS application suppliers or automotive OEMs classification confidence level: measure related to the certainty, generally... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: IF.CPS Interface between CPS and LDM or ITS applications IF.APP Interface between CPS and ITS applications IF.FAC Interface between CPS and other facilities layer entities IF.MCO Interface between CPS and the MCO facility layer entity IF.Mng Interfa... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ASN.1 Abstract Syntax Notation One CAM Cooperative Awareness Message CP Collective Perception CPM Collective Perception Message CPS Collective Perception Service DCC Decentralized Congestion Control DDP De... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 4 CPS introduction | Collective Perception Messages (CPMs) are transmitted by ITS-Ss in order to share information about perceived objects (such as vehicles, pedestrians, animals and other collision relevant objects) and perception regions (road regions that allow receiving ITS-Ss to determine unoccupied regions) in the local environment. ... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5 CPS functional specification | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.1 CPS in the ITS architecture | The CPS is a facilities layer entity in 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 ITS applications to collect relevant information for CPM generation and for forwarding received CPM content for further processing. Figure 1 depicts t... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.2 CPS functional architecture | For sending and receiving CPMs, the CPS shall provide the following sub-functions: • Encode CPM: This sub-function shall construct the CPM according to the format specified in Annex A. The most recent abstract CP object information, sensor information and perception region information data shall be included in the CPM.... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3 Interfaces of the CPS | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.1 Interface to ITS applications | An ITS application is an application layer functionality that implements the logic for fulfilling one or more ITS use cases. For the provision of received data, the CPS provides the interface IF.CPS to LDM or ITS application as illustrated in Figure 2. |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.2 Interface to data provisioning facilities | For the generation of CPMs, the CPS interacts with other Facilities layer entities to obtain the required data. This set of other facilities is referred to as data provisioning facilities, e.g. the ITS-S's POTI, DDP or LDM. Data is exchanged between the data provisioning facilities and the CP basic service via the inte... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.3 Interface to MCO_FAC | If the ITS-S supports MCO, the CPS shall exchange information with the MCO_FAC via the interface IF.MCO specified in ETSI TS 103 141 [7] and depicted in Figure 2. This interface can be used to configure the default MCO settings for the generated CPMs and can also be used to configure the MCO parameters on a per message... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.4 Interface to the Networking & Transport layer | If the ITS-S does not support MCO, the CPS exchanges information with the ITS Networking & Transport Layer via the interface IF.N&T, as depicted in Figure 2. At the originating ITS-S, the CPS shall provide the CPM embedded in a Facility-layer Service Data Unit (FL-SDU) together with protocol control information (PCI) t... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.6 Interface to the ITS management entity | The CPS of an originating ITS-S obtains configuration parameters and other control information from the Management Information Base (MIB) located in the management entity via the IF.Mng interface, as depicted in Figure 2. ETSI ETSI TS 103 324 V2.1.1 (2023-06) 14 NOTE 1: A list of primitives exchanged with the managemen... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 5.3.7 Interface to the security entity | The CPS may exchange primitives with the Security entity of the ITS-S (see Figure 1) using the IF.SEC interface provided by the Security entity, as depicted in Figure 2. In case the facility layer security is used, for ITS stations that use the trust model according to ETSI TS 102 940 [i.9] and ITS certificates accordi... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6 CPM dissemination | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1 CPM generation | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.1 CPM generation management | The functional scheme of the CPM generation management is illustrated in Figure 3. for single channel operation and in Figure 4. for multi-channel operation. Its different entities related to the CPM data inclusion management and the CPM assembly are specified in clause 6.1.2 and clause 6.1.3, respectively. The CPM Gen... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.2 CPM data inclusion | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.2.1 CPM generation events | CPMs are generated during periodic CPM generation events. The time elapsed between the triggering of consecutive CPM generation events shall be equal to T_GenCpm. T_GenCpm is limited to T_GenCpmMin ≤ T_GenCpm ≤ T_GenCpmMax. During each generation event, the inclusion of the SensorInformationContainer, PerceivedObject, ... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.2.2 Sensor Information Container Inclusion Management | A CPM shall include a SensorInformationContainer in the first generated CPM and whenever the time elapsed since the last time a CPM included a SensorInformationContainer is equal or greater than T_AddSensorInformation.Perception Region Inclusion Management. A CPM shall include a perception region whenever the CPS detec... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.2.3 Perceived Object Inclusion Management | A CPM shall include available information about perceived objects inside the perceivedObjectContainer using one instance of PerceivedObject per object in accordance with their type. The inclusion management depends on the CPS configuration, e.g. as a configuration stored in the MIB and listed in Annex F: • If ObjectInc... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.3 CPM assembly | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.3.1 General | The size of an ASN.1 UPER encoded CPM shall not exceed MTU_CPM, i.e. the MTU_CPM depends on the MTU of the access layer technology (MTU_AL) over which the CPM is transported. If multiple channels are available and, e.g. the ITS-S supports MCO, these restrictions shall apply to each channel individually. MTU_CPM shall b... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.3.2 Object utility function | If the SensorInformationContainer or the PerceptionRegions need to be transmitted, they shall be added to the first CPM generated for transmission on the preferred CPM channel. Perceived objects selected for transmission shall be included in CPMs in a descending priority order following a per- object utility function d... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.1.3.3 Perception region based | In case the SensorInformationContainer also needs to be transmitted, it shall be added to the first CPM transmitted on the preferred CPM channel. In case only one channel is available the preferred CPM channel corresponds to this channel. Every set of overlapping perception region and the objects selected for inclusion... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.2 CPM dissemination constraints | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.2.1 Security constraints | |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.2.1.1 Introduction | Clause 6.2.1 is applicable to ITS stations that use the trust model according to ETSI TS 102 940 [i.9] and ITS certificates according to ETSI TS 103 097 [1]. NOTE: For other scenarios, the trust model and the mechanisms for trust enforcement for inter-connected ITS stations can be agreed among participating actors. The... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.2.1.2 Service Specific Permissions (SSP) | CPMs shall be signed using private keys associated to Authorization Tickets that contain SSPs of type BitmapSsp as specified in ETSI TS 103 097 [1]. The SSP for the CPM shall be of CHOICE BitmapSsp. It is defined by a variable number of octets and shall correspond to the octet scheme illustrated in Figure 6. This octet... |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 6.2.2 General priority constraints | If the GeoNetworking/BTP stack is used, the priority constraint shall be as given by the Traffic Class as specified in ETSI TS 103 836-4-1 [5]. |
3f654b07bdb486ec521536f502b13be0 | 103 324 | 7 CPM Specification |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.