hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.6 UC-B4: Emergency Electronic Brake Light (EEBL) | Table 8: Risk analysis: UC-B4: Emergency electronic brake light Use case: Emergency Electronic Brake Light (EEBL) Actors: Braking ITS-S, Receiving ITS-S Information flow Entity activities Description Impact IB4-1 Exchange messages EB4-1.1 Braking ITS-S → Receiving ITS-S Broadcast of information about brake event C: Non... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.8 UC-C1: Signalling VRU hidden by an obstacle | Table 10: Risk analysis: UC-C1: Signalling VRU hidden by an obstacle Use case: Signalling VRU hidden by an obstacle Actors: VRU, Sensor-equipped vehicle, Receiving vehicle Information flow Entity activities Description Impact IC1-1 Detect EC1-1.1 Sensor-equipped vehicle detecting VRU Sensor activity to detect VRU C: No... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.9 UC-D1: Signalled few VRUs in a protected area | Table 11: Risk analysis: UC-D1: Signalled few VRUs in a protected area Use case: Signalled few VRUs in a protected area Actors: VRU, RSE, Approaching vehicle Information flow Entity activities Description Impact ID1-1 Detect ED1-1.1 Approaching vehicle → RSE Broadcast of dynamic and other information about vehicle used... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.10 UC-D2: Non equipped VRUs crossing a road | Table 12: Risk analysis: UC-D2: Non equipped VRUs crossing a road Use case: Non equipped VRUs crossing a road Actors: Notifying ITS-S, Receiving vehicle Information flow Entity activities Description Impact ID2-1 Warn ED2-1.1 RSE → Approaching vehicle Broadcast of warning information of VRUs in road C: None - broadcast... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.11 UC-D3: VRUs crossing at a zebra protected by a traffic light | Table 13: Risk Analysis: UC-D3: VRUs crossing at a zebra protected by a traffic light Use case: VRUs crossing at a zebra protected by a traffic light in the presence of a priority vehicle Actors: Priority vehicle, RSE, VRU Information flow Entity activities Description Impact ID3-1 Request priority ED3-1.1 Priority veh... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.12 UC-D4: Scooter/bicyclist safety with turning vehicle | Table 14: Risk analysis: UC-D4: Scooter/bicyclist safety with turning vehicle Use case: Scoots/bicyclist safety with turning vehicle Actors: VRU, RSE, vehicle Information flow Entity activities Description Impact ID4-1 Detect ED4-1.1 Sensor-equipped RSE detecting VRU Sensor activity to detect VRU C: None - VRU is detec... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.13 UC-E1: Network assisted vulnerable pedestrian protection | Table 15: Risk analysis: UC-E1: Network assisted vulnerable pedestrian protection Use case: Network assisted vulnerable pedestrian protection Actors: VRU, vehicle, third party in cloud Information flow Entity activities Description Impact IE1-1 Detect EE1-1.1 VRU → Third party in cloud Position report C: None - VRU is ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.14 UC-E2: Detection of an animal or pedestrian on a highway | Table 16: Risk analysis: UC-E2: Detection of an animal or pedestrian on a highway Use case: Detection of an animal or pedestrian on a highway Actors: Roadside Sensor, vehicle, third party in cloud, VRU Information flow Entity activities Description Impact IE2-1 Detect EE2-1.1 Roadside Sensor → Control centre VRU report... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.15 UC-E3: VRU protection via a central system | Table 17: Risk analysis: UC-E3: VRU protection via a central system Use case: VRU protection via a central system Actors: Roadside Sensor, VRU, vehicle, third party in cloud Information flow Entity activities Description Impact IE3-1 Detect EE3-1.1 VRUs, vehicles → Third party in cloud Position report C: Low - Unicast ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.16 UC-F1: Signalled many VRUs in a protected area | Table 18: Risk analysis: UC-F1: Signalled many VRUs in a protected area Use case: Signalled many VRUs in a protected area Actors: Equipped VRUs, RSE, Approaching vehicle Information flow Entity activities Description Impact IF1-1 Detect EF1-1.1 Approaching vehicle → RSE Broadcast of dynamic and other information about ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 4.5.17 UC-F2: Intelligent traffic lights for all | Table 19: Risk analysis: UC-F2: Intelligent traffic lights for all Use case: Intelligent traffic lights for all Actors: Privileged VRU, RSE, Vehicle Information flow Entity activities Description Impact IF2-1 Detect EF2-1.1 Equipped VRU → RSE Awareness message of (a) presence of VRU (b) fact that VRU is privileged (c) ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5 VRU related requirements | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.1 Introduction | This clause specifies the requirements on the VRU-related components in the C-ITS. These requirements are derived from the use cases and related analysis described in clause 6 and in clause 7 of ETSI TR 103 300-1 [i.1]. The requirements are classified into two categories: functional requirements, which will have an imp... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.2 Functional requirements | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.2.1 System requirements | System functional requirements identify the ITS functions necessary to support the VRU services. Table 20: Functional system requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] FSYS01 An element of the VRU system shall use an ITS-S (either personal, vehicle, roadside or central) f... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.2.2 Communication requirements | Table 21: Functional communication requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] FCOM01 A VRU system shall operate effectively when up to 5 000 number of users are within the same communications zone, i.e. within a circle of radius up to 300 m (see ETSI TS 101 539-1 [i.27]) ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.2.3 Security requirements | Table 22: Functional security requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] FSEC01 All transmissions to support VRU use cases shall come from an ITS-S and all ITS-S shall ensure that inputs used to form messages are from trustworthy sources. FSEC02 Messages within the VRU sy... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.3 Operational requirements | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.3.1 System requirements | Operational system requirements which characterize the system performances and other operational aspects related to the identified functions are described in Table 23. Table 23: Operational system requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] OSYS01 Positioning capabilities ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.3.2 Communication requirements | Table 24: Operational communication requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] OCOM01 The communication range of a VRU system shall depend on the specific application. Specific values are defined in sub-requirements OCOM01.1 to OCOM01.5. Here, "communication range" means ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.3.3 Security requirements | Table 25: Operational security requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] OSEC01 The security processes shall support generating messages at a rate of 10 Hz, receiving messages at a rate of 2 KHz, latency of 300 ms end-to- end and an average sent packet size over 1 s of 3... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 5.4 Additional recommendations | Table 26: Additional recommendations Rec-Id Recommendation text Explanation UC reference from ETSI TR 103 300-1 [i.1] REC01 A VRU ITS-S should be able to perform collision risk assessment if sufficient battery and processing power are available in the VRU device. The VRU may not have sufficient processing power or batt... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6 Functional architecture of the VRU system | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.1 VRU profile specification | In this clause four basic VRU profiles are specified. These profiles are the basis for the further definition of the VRU functional architecture. The profiles are derived from the use cases and from the analysis in clause 7.2 of ETSI TR 103 300-1 [i.1]. A VRU can only be a living being. This living being is considered ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.2 VRU cluster definition | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.2.1 VRU cluster concept | NOTE: The present clause defines the notion of VRU cluster. Its detailed specification is part of the VRU basic service standard (ETSI TS 103 300-3 [i.11]). The number of VRUs operating in a given area can get very high (up to 500, see UC-B2, VRU crossing a road, and clause 7.4.1 in ETSI TR 103 300-1 [i.1]) or the VRU ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.2.2 VRU cluster requirements | Table 31: VRU cluster requirements Req-Id Requirement text Explanation UC reference from ETSI TR 103 300-1 [i.1] RCL01 A VRU device (with VRU profile 1, 2 or 4) shall be able to determine whether it should be acting as a clustered or individual VRU. See also RCL02. RCL02 Only the VRU-St device type (see clause 4.1) sha... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.2.3 VRU cluster reference position | A VRU cluster is considered as a single entity in the overall VRU communication. Only a single cluster VAM is generated per cluster containing the relevant information/parameter of the cluster. These parameters are (more details can be found in ETSI TS 103 300-3 [i.11]): • Cluster ID (in case several clusters are collo... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.2.4 VRU cluster approach | Clustering of VRUs is one of the possible solutions for prevention and reduction of the number of transmitted messages (see requirement FCOM03 for all possible solutions identified). A VRU device is able to determine whether it should be acting as a clustered or individual VRU (see note 2 below). If a VRU is part of a ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.3 VRU system functional architecture | The present document specifies the VRU-related functional entities residing in the facilities and application layers of an ITS Station, as defined in ETSI TS 103 898 [i.12] (ITS station reference architecture) and ETSI TS 102 894-1 [i.14] (Facilities layer specification) that are relevant for the operation of the VRU s... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.4 VRU-related functions in the ITS station architecture | Figure 5 zooms in the ITS-S element of Figure 4 and shows the main components of the ITS-S architecture specified in ETSI TS 103 898 [i.12] that directly impact the VRU system operation. It introduces a new functional entity described in more details in ETSI TS 103 300-3 [i.11], the VRU Basic Service. Other functions a... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5 Function descriptions | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.1 General overview | Clause 6.5 describes the functions illustrated in Figure 4 and Figure 5. The proposed functional descriptions are conceptual models which can be implemented in different ways. The specification of exposed interfaces would contribute to make the ITS functionally testable and measurable in terms of minimum performances r... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.2 Sensor system - IoT platform | The VRU sensor system is at least composed of the PoTi data provider present in each ITS-S of the system. The PoTi entity provides the global time common to all VRU system elements and the real time position of the mobile elements of the VRU system. Local sensors may also be embedded in the mobile elements as well as i... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.3 Local Sensor data fusion and actuator (including AI) | The sensor data fusion function is the fusion of local perception data obtained from different local sensors. Sensor data fusion relies on the consistency of its inputs and on their timestamping which needs to correspond to one common given time. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.4 Local perception | The local perception function is provided by the local processing of information collected by local sensor(s) associated to the system element (VRU device, vehicle, RSE, central systems) considered. Its main purpose is to detect and characterize objects (static and mobile) which are likely to cross the trajectory of th... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.5 Motion dynamic prediction | The motion dynamic prediction function is related to the behaviour prediction of the considered moving objects. Motion dynamic includes the moving object trajectory resulting from evolution of the successive mobile positions. A change of the moving object trajectory or of the moving object velocity (acceleration/decele... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.6 Vehicle motion control | The vehicle motion control is a function under the responsibility of the human driver or of the vehicle if it is able to drive in automated mode. It is capable to act on the trajectory of the vehicle or on its speed. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.7 Human - Machine Interface (HMI) | The Human Machine Interface (HMI) is not mandatory, but, when present, it enables: • The configuration of initial data (parameters) in the management entities (e.g. VRU profile management) and in other functions (e.g. VRU basic service management). • The communication to the device owner of external events related to t... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.8 Connected System/Information System | The VRU system is a connected system made of up to 4 different levels of equipment as represented in Figure 4. It is also an information system which collects in real time information resulting from events, processes the collected information and stores them together with processed results. At each level of the VRU sys... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.9 Traffic Management System | Traffic Management System (TMS) collects data from interconnected system elements, then processes them and provides traffic information to road users. The processing of collected data is performed for well-defined services and supporting applications. In the case of VRU protection, a TMS allows to collect data and diss... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10 ITS Station Application Layer | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.1 Global overview | The functions described below are proposed to be located at the application layer level. However, if there is a generic and justified need to share them between several applications, part of these functions may be moved to the facilities layer. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.2 Device role setting | A VRU can be equipped with a portable device which needs to be initially configured and may evolve during its operation following context changes which need to be specified. This is particularly true for the setting-up of the VRU profile and sub-profile which can be achieved automatically at power on or via an HMI. The... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.3 Remote sensor data fusion and actuator (including AI) | The local perception obtained by the computation of data collected by local sensors may be augmented by remote data collected by elements of the VRU system (vehicles, RSE) via the ITS-S. These remote data are transferred using standard services such as the CPS. In such case it is necessary to fuse these data. The data ... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.4 Cooperative Perception | As shown in Figure 6, the perception chain can be the fusion of the results of several perception functions at predefined times: • The local perception is provided by the collection of information from the environment of the considered ITS element (VRU device, vehicle, infrastructure). This information collection is pe... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.5 Collision risk analysis | The collision risk analysis function analyses the motion dynamic prediction of the considered moving objects associated to their respective levels of confidence (reliability). The objective is to estimate the likelihood of a collision and then to identify as precisely as possible the Time To Collision (TTC) if the resu... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.6 Collision risk avoidance | The collision risk avoidance includes the collision avoidance strategy to be selected according to the TTC value. In the case of an autonomous vehicle, it may consist in the identification of manoeuvre coordination/vehicle motion control to achieve the collision avoidance as per the likelihood of VRU trajectory interce... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.7 Event detection | The event detection function assists the VRU basic service during its operation when transiting from one state to another. The main events to be considered are: • Change of a VRU role when a road user becomes vulnerable (activation) or when a road user is not any more vulnerable (de-activation). • Change of a VRU profi... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.8 Infrastructure services | Existing infrastructure services can be used in the context of the VRU system: • The broadcast of the SPaT (Signal Phase and Timing) & MAP (SPaT relevance delimited area) is already standardized and used by vehicles at intersection level. In principle they protect VRUs crossing. However, signal violation warnings may e... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.10.9 Manoeuvre coordination | This function executes the collision avoidance actions which are associated to the collision avoidance strategy that has been decided. This function should be present at the vehicle level, depending also on the vehicle level of automation (i.e. not present in non-automated vehicles), and may be present at the VRU devic... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11 ITS Station Facilities Layer | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11.1 VRU basic service | The VRU basic service is supported by the set of functions illustrated in Figure 8: • VRU basic service management. • VRU Cluster management. • VAM Reception management. • VAM Transmission management. • VAM Encoding. • VAM Decoding. These functions are described with more details in ETSI TS 103 300-3 [i.11]. The VRU ba... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11.2 Local Dynamic Map (LDM) | The Local Dynamic Map (LDM) is the repository of all the dynamic data elements related to the functions supporting the VRU basic service. The LDM content should be accessible directly from dedicated VRU and vehicle facilities layer functions via an exposed interface (FA SAP: Facilities - Application Service Access Poin... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11.3 PoTI | Position and Time Management (PoTi) is specified in ETSI EN 302 890-2 [3]. The PoTi function is present in vehicles' ITS-S and VRU ITS-S. It may also be present in an infrastructure ITS-S and be used to develop a positioning augmentation service. Position accuracy and confidence level are key performance indicators whi... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11.4 Other Application Support Facilities: CA, DEN, CPS, MCS, SPaT, etc. | Other application support facilities functions are responsible to trigger the transmission of their related messages and forward the messages received to the relevant applications. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.11.5 Channel Congestion Control (DCC-FAC) | The channel congestion control function acts to optimize the use of the available channel bandwidth during peak traffic, thus avoiding its congestion. ETSI ETSI TS 103 300-2 V2.3.1 (2024-08) 57 For this purpose, according to current and anticipated channel load, the channel congestion control cooperates with the VRU Ba... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.12 ITS Station Management Entity | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.5.12.1 VRU profile management | The VRU profile management function is an important support element for the VRU basic service as it manages the VRU profile during a VRU active session. The profile management is part of the ITS-S configuration management and is initialized with necessary typical parameters' values to be able to fulfil its operation. T... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6 Security | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.1 Security mechanisms by information flow | Information flows below are identified by the alphanumeric identifiers used in clause 4.5. In the electronic version of the present document, each information flow identifier is a clickable link that links to the security analysis in the relevant part of clause 4.5. The following information flows/entity activities are... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.2 Roles | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.2.1 Overall roles | A "role" is an identifier corresponding to a set of activities such that any actor with that role may carry out any of the activities in the set. One goal of the security analysis is to identify natural roles in the system from a security perspective, i.e. collections of activities (as an example: if an actor can do on... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.2.2 Entitlement to roles | The identification of roles creates two design requirements: • The design shall provide a mechanism for participants in use cases to determine that counterparties are entitled to act in the appropriate role. ETSI ETSI TS 103 300-2 V2.3.1 (2024-08) 59 • The design shall provide a mechanism for credential issuance system... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.3 Pseudonymity | As noted in the security analysis, actors acting in the VRU and Vehicle role require pseudonymity (see also ETSI TS 103 300-3 [i.11]). For actors in both of these cases, for all broadcast information flows, pseudonymity is provided by having multiple certificates. For actors in the Vehicle role, the messages that are s... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.6.4 Misbehaviour Detection | A VRU device that causes false alerts, or a VRU device that creates messages that are physically inconsistent with each other, should be considered for reporting and blacklisting. |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.7 Impact of the deployment and automation level roadmap | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.7.1 Introduction | The C-ITS platform final report [i.5] has defined a set of C-ITS services for Day 1 and Day 1.5 deployments. The protection of VRUs (pedestrian and cyclists) is considered in the list of Day 1.5 services. In parallel, OEMs are enhancing the vehicle security by increased ADAS capabilities, with a higher level of automat... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.7.2 Functional architecture of VRU system with Day 1 services | Services for Day 1 deployment - assumptions These services target vehicle safety in motorway and urban use cases. They are based on awareness messages (CAM, MAP, SPaT), notifications (DENM) and in-vehicle information. The C-ITS communication is essentially V2V or I2V. The level of vehicle automation is expected to be a... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.7.3 Functional architecture of VRU system with Day 1.5 services | Services for Day 1.5 deployment - assumptions The roadmap of service deployment is incremental. Accordingly, the Day 1 services are present in this phase. Additional services of interest are the CPS and the VRU basic service. New messages are available to the ITS stations: CPM and VAM. The C-ITS communications addition... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.8 Interfaces between entities | |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.8.1 Introduction | The interfaces between different ITS stations of different levels of the architecture, i.e. external interfaces, and those between different functional components of each level, i.e. internal interfaces, are illustrated in Figure 4. The interfaces between the VRU Basic Service and other facilities layer entities in the... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.8.2 External interfaces | Parameters of the external interfaces shall include the descriptive, physical and dynamic state information of a VRU so that the collision risk can be estimated and warned, and the strategy for collision avoidance can be deduced. The parameters may also include additional information of a VRU cluster for efficient netw... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.8.3 Internal interfaces | Data exchanged via the internal interfaces of the VRU system are used to generate the parameters to be sent via the external interfaces. They are also used to estimate/predict the collision risk and avoid the predicted collision based on the parameters received via the external interfaces. Table 33 describes the intern... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.8.4 VRU Basic Service interfaces | The interactions between the VRU Basic Service and other facilities layer entities in the ITS-S architecture are used to obtain information for the generation of the VAM. The interfaces for these interactions are described in Table 37 and in ETSI TS 103 300-3 [i.11]. Table 37: VRU Basic Service interfaces Interfaced fu... |
43ae532e6551f735fab5f793f0b2091c | 103 300-2 | 6.9 Vulnerable Road User Awareness Message, VAM | The message specified for the VRUs awareness (VAM) shall be harmonized in the largest extent with the existing Cooperative Awareness Messages (CAM) defined in ETSI TS 103 900 [1]. The transmission of the VAM shall be limited to the VRU profiles specified in clause 6.1. The Vulnerable Road User Awareness Message (VAM) s... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 1 Scope | The present document specifies the ultra-low power physical layer (PHY) SmartBAN. The present document applies to short range, wireless communication between wearable sensors devices and the hub coordinator. The present document specifies the PHY for transmitting on the medium. The present document describes: • packet ... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 2 References | |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 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... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 3 Definition of terms, symbols and abbreviations | |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 3.1 Terms | Void. ETSI ETSI TS 103 326 V1.2.1 (2021-07) 6 |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: D Delay ⊕ eXclusive OR (XOR) |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BAN Body Area Network BCH Bose–Chaudhuri–Hocquenghem CCA Clear Channel Assessment CRC Cyclic Redundancy Check ED Energy Detection FEC Forward Error Correction GFSK Gaussian Frequency Shift Keying IFS Inter-Frame Spacing ISM Industrial, Scienti... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 4 Introduction and Background | Modern medical and health monitoring equipment are moving towards the trend of wireless connectivity between the data collection or control centre and the medical devices or sensors. Therefore, the need for a standardized communication interface and protocol between the actors are required. This network of actors perfo... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 5 General PHY Framework | |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 5.0 Introduction | This clause provides the basic PHY framework for the nodes and hubs. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 5.1 Frequency Spectrum | The frequency of operation shall fall within 2 401 - 2 481 MHz. The channels shall be arranged in blocks of 2 MHz with centre frequencies: fc = 2 402 + 2 × n MHz, for n = 0 to 39 (1) where n is the channel number. Table 1 shows the mapping of the channel number to data channel number and control channel number. ETSI ET... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6 Packet Formats | |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1 PPDU | 6.1.0 PPDU Structure Figure 1 shows the PPDU structure. The PPDU consists of Preamble, Synchronization (Sync.), PLCP Header, PSDU and Frame Parity. Figure 1: PPDU Structure |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.1 Preamble | PPDUs have a sixteen-bit preamble used for frequency synchronization, timing synchronization, and automatic gain control. The preamble for all PPDUs shall be 1010101010101010. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.2 Sync. | The Sync. field indicates the synchronization pattern that shall be 10000111101100101000011110110010. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3 PLCP Header | |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3.0 PLCP Header Structure | The PLCP Header is structured as illustrated in Figure 2. The PLCP header consists of the Packet Length, PHY Scheme, Reserved, BCH Parity Bits, and the Header Parity fields. The PLCP header may be scrambled by the procedure described in clause 7.4. Preamble PLCP Header PSDU Bits: 16 LPSDU 40 Sync. 32 Frame Parity 16 ET... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3.1 Packet Length | The packet length field indicates the length of the PSDU. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3.2 PHY Scheme | The PHY Scheme field describes the Forward Error Control (FEC) type and the repetition type the PPDU employs. The mapping of the field bits is as described in Table 2. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3.3 BCH Parity Bits | The BCH Parity Bits field is generated using a BCH (36, 22, t = 2) code defined in clause 7.3.3 to protect the Packet Length, PHY Scheme, and Reserved fields. |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.3.4 Header Parity | The Header Parity field is generated by the CRC polynomial 1 + x + x4 on the Packet Length, PHY Scheme, Reserved, and BCH Parity Bits fields. Table 2: PHY Scheme field bit mapping Field Value b0 b1 FEC Type Field Value b2 b3 Repetition Type 00 None 00 None 01 BCH (127, 113, 2) 01 2 10 Reserved 10 4 11 Reserved 11 Reser... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.4 PSDU | The Physical Layer Service Data Unit (PSDU) is either an encoded or uncoded MAC Protocol Data Unit (MPDU) as defined in clause 6.1 of ETSI TS 103 325 [1]. The MPDU may be encoded using a BCH (127, 113, t = 2) code. The encoding procedure is described in clause 7.3. The PSDU may be scrambled using the procedure describe... |
f4556ad722d8b9d7a0282eb7d9f58ada | 103 326 | 6.1.5 Frame Parity | The Frame Parity field shall contain a 16 bit CRC sequence of the PSDU generated using the generator polynomial: x16 + x12 + x5 + 1 (2) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.