hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.2.2 Central Coordination Point | The CCP is a centralized coordination device or system. The tasks for CCP are incumbent services and applications sensing, provide mechanism to incumbent service and application protection and establish an automatic coexistence management between multiple WIA systems and WIA devices. The CCP shall establish a wired or ... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.3 Local Industrial Environment Resource Database | The LRDB contains information about a WIA device within a CCP controlled WIA system, CCP controlled WIA devices and WIA system with per device spectrum access mechanism with location specific information and radio specific information. The LRDB shall provide this information to the SM. The radio specific information is... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4 Spectrum Manager | |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4.1 Overview | The spectrum manager (SM) within a CCP shall be responsible for maintaining the requirements of automation application, maintaining spectrum availability information, channel selection, channel management, scheduling spectrum sensing operation, access to the database, regulatory domain policies and enabling intra-syste... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4.2 Incumbent Service Database | The incumbent service/application is allowed to dynamically use its spectrum band or parts of it during the WIA operation. The incumbent service/application database (ISDB) contains regulatory information about incumbent service/application and information how the WIA network or system will react in case of an incumben... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4.3 Spectrum Resource Engine | The Spectrum Resource Engine (SRE) makes use of the radio regulation specifications, since radio regulations specify important coexistence parameters such as frequency band, output power and mitigation techniques. These specifications shall be taken into account within the spectrum management process. Furthermore, WIA ... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4.4 Radio System and Device Registration and Management | The RRM manages all WIA systems and devices. Therefore, all these WIA systems and devices shall be registered at RRM before operation starts. |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.4.5 Automation Application Resource Management | The Automatic Application Resource Management (AARM) contains information about the application traffic, and time and error requirements of automation applications. Resources can be provided to the AARM by the controlled devices or by a tool. Resources can be static or dynamic. |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.5 Spectrum Sensing Unit | The Spectrum Sensing Unit (SSU) is necessary for the implementation of a CCP controlled WIA system. The SSU observes the available RF spectrum to determine its occurrence of incumbent services/applications and occupancy of other WIA systems. This process is called sensing and takes into account parameters of the radio ... |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.6 Functions | |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.6.1 Mitigation techniques | |
c96657948d5044969d3c53893fe9eef7 | 103 329 | 5.6.1.1 General | The CCP shall implement the needed mitigation techniques for example Dynamic Frequency Selection (DFS), Detect and avoid (DAA) and Adaptive Frequency Agility (AFA). ETSI ETSI TS 103 329 V1.1.1 (2016-06) 18 History Document history V1.1.1 June 2016 Publication |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 1 Scope | The present document defines the communication protocols, message format, semantics and syntax as well as key interfaces and protocol operation for the VRU awareness service, hereafter named the VRU Basic Service (VBS). |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 2 References | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 3 Definition of terms, symbols and abbreviations | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 300-1 [i.1], ETSI TS 103 300-2 [1] and the following apply: cluster VAM: Vulnerable Road User (VRU) Awareness Message (VAM) including information about a cluster of VRUs farm animal: animal living under the supervision of an owner ETSI ETSI TS 103... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 3.2 Symbols | Void. |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 103 300-1 [i.1], ETSI TS 103 300-2 [1] and the following apply: BTP Basic Transport Protocol CA Cooperative Awareness (basic service) CAM Cooperative Awareness Message CDD Common Data Dictionary CPM Collective Perception Message CPS Collective... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 4 VRU basic service introduction | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 4.1 Background | ETSI TS 103 300-2 [1] specifies the requirements for the C-ITS service related to VRU protection, as well as the VRU system architecture. The present document further elaborates on the details of the VRU basic service and the transmission of the Vulnerable Road User Awareness Messages (VAM). VAMs are messages transmitt... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 4.2 Services provided by VRU basic service | The VRU basic service is a facilities layer entity that operates the VAM protocol. It provides three main services: handling the VRU role, sending and receiving of VAMs. The VRU basic service uses the services provided by the protocol entities of the ITS networking & transport layer to disseminate the VAM. Handling VRU... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5 VRU basic service functional description | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.1 VRU basic service in the ITS architecture | Figure 1 presents the main components of the ITS-S architecture that directly impact the VRU system operation. The VRU basic service (VBS) shall be a facilities layer entity of the ITS-S architecture as defined in ETSI EN 302 665 [2]. Functions other than those shown in the figure may be present as defined in ETSI TS 1... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.2 VRU basic service functional architecture | This clause provides a summary of the VRU basic service. The VRU basic service functions are represented in Figure 2. This clause introduces these VBS functions, which are further detailed in the next clauses of the present document. Figure 2: VRU basic service functions NOTES: • The VAM reception management and the VA... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3 Interfaces of the VRU basic service | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.1 VRU basic service interfaces in the facilities layer (IF.OFa) | 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 2. Table 2: VRU basic service interfaces (IF.OFa) Interfaced functionality Parameters Po... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.2 Interface to the ITS applications (IF.FA) | An ITS application is a function of the ITS application layer that implements the application logic of one or more use cases. The VRU basic service provides the interfaces to the ITS-S applications for the VAM protocol operation of the originator ITS-S and receiver ITS-S. ETSI ETSI TS 103 300-3 V2.1.1 (2020-11) 20 NOTE... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.3 Interface to the ITS-S networking and transport layer (IF.NF) | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.3.1 General requirements | The VRU basic service exchanges information with ITS networking & transport layer via the interface NF in Figure 2. A specification of the interface IF.NF as NF-SAP in Figure 1 is provided in ETSI TS 102 723-11 [i.5]. At the originating ITS-S, the VRU basic service shall provide the VAM embedded in a facilities-layer S... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.3.2 Interface to the GeoNetworking/BTP stack | The VRU basic service may rely on services provided by the GeoNetworking/BTP stack to disseminate a VAM to a geographic destination area. PCI being passed from VRU basic service to the GeoNetworking/BTP stack shall comply with Table 3 and Table 4. ETSI ETSI TS 103 300-3 V2.1.1 (2020-11) 21 Table 4: Data passed from VRU... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.3.3 Interface to the IPv6 stack and the combined IPv6/GeoNetworking stack | A VAM may use the IPv6 stack or the combined IPv6/GeoNetworking stack for VAM dissemination as specified in ETSI EN 302 636-3 [i.3]. NOTE: When the VAM dissemination makes use of the combined IPv6/GeoNetworking stack, the interface between the VRU basic service and the combined IPv6/GeoNetworking stack may be identical... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.4 Interface to the ITS-S management entity (IF.MF) | The VRU basic service may exchange primitives with Management entity of the ITS-S via the MF-SAP interface depicted in Figure 1. The VRU basic service gets information for congestion control from the management entity. The VRU basic service shall be able to receive unsolicited notifications from the ITS-S management en... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.3.5 Interface to the ITS-S security entity (IF.SF) | The VRU basic service may exchange primitives with the Security entity of the ITS-S via the SF-SAP interface in Figure 1 using the SF interface (IF.SF) provided by the Security entity in Figure 2. The SF-SAP interface is provisioned in ETSI EN 302 665 [2] but not yet specified as of V1.1.1 of the present document. Acco... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4 VRU cluster specification | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.1 VRU clustering functional overview | The clustering operation as part of the VRU basic service is intended to optimize the resource usage in the ITS system. These resources are mainly spectrum resources and processing resources. A huge number of VRUs in a certain area (pedestrian crossing in urban environment, large squares in urban environment, special e... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2 VRU cluster operation | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.1 VBS clustering states | Depending on its context, the VRU basic service (VBS) shall be in one of the cluster states specified in Table 5. Table 5: Possible states of the VRU basic service related to cluster operation VBS State Specification Valid VRU profiles Valid VRU types Additional explanation VRU-IDLE The device user is not considered as... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.2 Events triggering a transition between VBS clustering states | In addition to the normal VAM triggering conditions defined in clause 6, the following events shall trigger a VBS state transition related to cluster operation. Parameters that control these events are summarized in clause 8, Table 14 and Table 15. • Entering VRU role: VRU-IDLE When the VBS in VRU-IDLE determines that ... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.3 Events not triggering a transition between VBS clustering states | The following actions do not trigger a state transition but shall cause an update of information. • Extending or shrinking a VRU cluster: State: VRU-ACTIVE-CLUSTER-LEADER A VAM indicating that a VRU is joining the cluster allows the VRU cluster leader to determine whether the cluster is homogeneous or heterogeneous, it... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.4 Conditions for clustering operations | Conditions to determine whether to create a cluster: a VRU device with a VBS in VRU-ACTIVE-STANDALONE can create a cluster if all these conditions are met: • It has sufficient processing power (indicated in the VRU configuration received from the VRU profile management function). • It has been configured with VRU equip... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.5 State diagram related to VRU cluster operation | Figure 3 illustrates the state diagram related to VRU cluster operation. Figure 3: VBS state diagram related to VRU cluster operation |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.2.6 Application to the specific case of a combined VRU | A combined VRU groups the device of at least one VRU from VRU Profile 1 (e.g. a pedestrian) and the device located in a VRU vehicle from VRU Profile 2 or VRU Profile 3 (e.g. motorcycle, bicycle, wheel chair, mounted animal), as described in ETSI TS 103 300-2 [1]. As a pre-requisite to the creation of a combined VRU, th... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 5.4.3 Cluster information parameters | A VRU cluster is considered as a single entity in the overall VRU communication system. If a cluster exists, cluster members shall not transmit VAMs, and only the cluster leader shall transmit cluster VAMs that describe the entire cluster. The parameters included in a cluster VAM shall be as in Table 6. Table 6: Cluste... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6 VAM dissemination | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.1 VAM transmission method | Point-to-multipoint communication shall be used for transmitting VAMs, as specified in ETSI TS 103 300-2 [1]. NOTE: Point-to-multipoint communication is specified in ETSI EN 302 636-4-1 [i.2] and ETSI EN 302 636-3 [i.3]. |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.2 Frequency/Periodicity range of VAMs | NOTE: The values of the parameters in clause 6.2 are provided in clause 8, Table 16. A VAM generation event results in the generation of one VAM. The minimum time elapsed between the start of consecutive VAM generation events shall be equal to or larger than T_GenVam. T_GenVam is limited to T_GenVamMin ≤ T_GenVam ≤T_Ge... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.3 Transmitting VAMs | VRU ITS-S in VRU-ACTIVE-STANDALONE state shall send "individual VAMs", while VRU ITS-S in VRU-ACTIVE-CLUSTERLEADER VBS state shall transmit "cluster VAMs" on behalf of the VRU cluster. Cluster member VRU ITS-S in VRU-PASSIVE VBS state shall send individual VAMs containing VruClusterOperationContainer while leaving the ... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4 Triggering conditions | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.1 Individual VAM transmission management by VBS at VRU ITS-S | NOTE: The values of the parameters in clause 6.4 are provided in Table 17. The first time individual VAM shall be generated immediately after VBS activation. The VAM shall also be generated at the earliest time instant for transmission if any of the following conditions are satisfied and the individual VAM transmission... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.2 Cluster VAM transmission management by VBS at VRU ITS-S | The first time VRU cluster VAM shall be generated immediately after VBS activation. The VAM shall also be generated at the earliest time instant for transmission if any of the following conditions are satisfied and the VRU cluster VAM transmission is not subject to redundancy mitigation techniques: 1) A VRU in VRU-ACTI... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.3 VAM Redundancy Mitigation | A balance between frequency of VAM generation at facilities layer and communication overhead at access layer needs to be considered without impacting VRU safety and VRU awareness in the proximity. VAM transmission at a VAM generation event shall be subject to the following redundancy mitigation techniques: • An origina... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.4 VAM time requirement | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.4.1 VAM generation time | Besides the VAM generation frequency, the time required for the VAM generation and the timeliness of the data taken for the message construction are decisive for the applicability of data in the receiving ITS-Ss. In order to ensure proper interpretation of received VAMs, each VAM shall be time-stamped. NOTE: An accepta... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.4.4.2 VAM timestamp | The following requirements shall apply: • The reference timestamp provided in a VAM disseminated by an ITS-S shall correspond to the time at which the reference position provided in BasicContainer DF is determined by the originating ITS-S. The format and range of the timestamp is defined in clause B.1.3. • The differen... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.5 Security constraints | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.5.1 Introduction | VAMs that are transmitted over links that do not provide trust services shall be signed using ITS certificates as specified in ETSI TS 103 097 [8]. In particular, VAMs that are transmitted over BTP with the GeoNetworking protocol shall be signed at the GeoNetworking layer. In general, within the certificate the permiss... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.5.2 Service Specific Permissions (SSP) | The VAM-SSP octet scheme allows the SSP format to accommodate current and future versions of the present document. The octet scheme is constructed of a single octet taking the value 1, indicating version V1.1.1 of the present document. The SSP shall be a BitmapSsp as specified in ETSI TS 103 097 [8]. NOTE: The use of a... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.5.3 Certificate attachment policy | The baseline behaviour for attaching certificates to a signed individual VAM is to attach the certificate once a second or if a new vehicle has been observed. Specifically, when the VBS generates an individual VAM and requests it to be signed: 1) If it is one second or more since a certificate was last attached to a VA... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.5.4 Privacy considerations | The decision whether to participate in sending VAMs creates a trade-off between personal safety, which is enhanced by the VAM, and privacy, which is reduced by the VAM. From the privacy perspective, sending the VAM creates the risk that if an eavesdropper has an interest in tracking an individual person who is a VRU, t... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.6 Methods to prevent false warnings (false positives) | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.6.1 General Considerations | The false warnings could create dangerous situations for VRUs, and other road users. False warning and reactions to those warnings may create network congestion in some scenarios. To prevent the false warnings the following techniques may be used depending on specific applications and implementations: • Ruling out fals... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.6.2 Roadworks safety | False warnings regarding roadworks are filtered out more confidently if DENM and VAM are used together for vehicles or VRUs. If there is a DENM to indicate that there is a road work area ahead, plus VAMs sent by the road workers, any ITS-S that receives both types of messages can be aware of the road worker VRUs confid... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.6.3 Weather condition | The TTC (time to collision) can be estimated by the VRU ITS-S receiving the safety messages from other ITS-Ss. The dynamic motion properties (i.e. velocity, acceleration, heading, etc.) of VRU ITS-S or vehicle ITS-S are influenced by external conditions such as weather, road conditions. For example, if it rains, the ro... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 6.7 Methods to prevent false negatives | The false negative situation arises when no warning message is transmitted during a dangerous situation. A false negative could be more critical for the safety of VRUs, and other road users than a false positive. To prevent the false negatives, the following techniques may be used depending on specific applications and... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7 VAM Format Specification | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.1 General Structure of a VAM PDU | A VAM is composed of: • a common ITS PDU header • a generation time • a basic container • a VRU high frequency container with dynamic properties of the VRU (motion, acceleration, etc.) • a VRU low frequency container with physical properties of the VRU (conditional mandatory, e.g. with higher periodicity, see clause 7.... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.2 ITS PDU header | The ITS PDU header shall be as specified in ETSI TS 102 894-2 [7]. Detailed data presentation rules of the ITS PDU header in the context of VAM shall be as specified in annex B. The StationId field in the ITS PDU Header shall change when the signing pseudonym certificate changes, or when the VRU starts to transmit indi... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3 Other containers | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.1 Basic container | The basic container provides basic information of the originating ITS-S: • Type of the originating ITS-S; this DE somehow overlaps with the VRU profile, even though they do not fully match (e.g. moped(3) and motorcycle(4) both correspond to a VRU profile 3). To enable a future possibility to have the VAM transmitted by... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.2 VRU specific containers | All VAMs generated by a VRU ITS-S shall include at least a VRU high frequency (VRU HF) container. The VRU HF container contains potentially fast-changing status information of the VRU ITS-S such as heading or speed. NOTE: As the VAM is not used by VRUs from profile 3 (motorcyclist), none of these containers apply to VR... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.3 VAM VRU HF container | The VRU HF container of the VAM contains potentially fast-changing status information of the VRU ITS-S. It shall include the parameters listed in clause B.3.1. Part of the information in this container do not make sense for some VRU profiles. Accordingly, they are indicated as optional, but recommended to specific VRU ... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.4 VAM VRU LF container | The VRU LF container of the VAM contains potential slow-changing information of the VRU ITS-S. It shall include the parameters listed in clause B.4.1. Some elements are mandatory, others are optional or conditional mandatory. The VRU LF container shall be included into the VAM with a parametrizable frequency as specifi... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.5 VAM VRU cluster containers | The VRU cluster containers of the VAM contain the cluster information and/or operations related to the VRU clusters of the VRU ITS-S. The VRU cluster containers are made of two types of cluster containers according to the characteristics of the included data/parameters. • A VRU cluster information container shall be ad... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.3.6 VAM VRU Motion Prediction container | The VRU Motion Prediction Container carries the past and future motion state information of the VRU. The VRU Motion Prediction Container of type VruMotionPredictionContainer shall contain information about the past locations of the VRU of type PathHistory, predicted future locations of the VRU (formatted as SequenceOfV... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.4 Special container for VRU Profile 3 (motorcyclist) | ITS stations in VRUs profile 3 devices (motorcyclist) already transmit the CAM. Accordingly, as specified in ETSI TS 103 300-2 [1] and in clause 5, they shall not transmit the full VAM but may transmit a VRU special vehicle container in the CAM that they already transmit. When relevant, this requirement also applies in... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.5 VAM format and coding rules | |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.5.1 Common data dictionary | The VAM format shall make use of the common data dictionary (CDD) as defined in ETSI TS 102 894-2 [7]. Where applicable, DEs and DFs that are not defined in the present document shall be imported from the CDD as specified in ETSI TS 102 894-2 [7]. NOTE 1: Detailed descriptions of all DEs and DFs in the context of VAM a... |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 7.5.2 VAM data presentation | The VAM format is presented in ASN.1. Unaligned packed encoding rules (PER) as defined in Recommendation ITU-T X.691/ISO/IEC 8825-2 [16] shall be used for VAM encoding and decoding. The ASN.1 representation of VAM shall be as specified in annex A of the present document. |
86590683f9aec49d24cd520688b6dc36 | 103 300-3 | 8 Parameters values | The present clause provides the values to be used for the parameters defined in clauses 5 to 7. The parameters in Table 14 govern the VRU decision to create, join or leave a cluster. The parameters may be set on individual devices or system wide and may depend on external conditions or be independent of them. Table 14:... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 1 Scope | The present document describes and specifies the high level infrastructure, its building blocks and associated APIs providing interoperability management solutions for SmartBAN. The architecture described in the present document also enables generic interaction and access to BAN data and entities, and thus paves the wa... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 2 References | |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 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... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 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... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 3 Definition of terms, symbols and abbreviations | |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 3.1 Terms | Void. |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: bpm beats per minute bps bit per second s second ETSI ETSI TS 103 327 V1.1.1 (2019-04) 10 |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledgement (e.g. ACK message) AE Application Entity AIOTI Alliance for Internet of Things Innovation API Application Programming Interface ASTM American Standards for Testing and Materials AT ATtention (e.g. AT Command) BAN Body Area ... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 4 Ambit and induced constraints | The scope of the present clause is to briefly investigate the initial TC SmartBAN use case requirements in order to point out their impact on High level specifications and designs of the present document. The initial additional requirements induced by scenario addressed within the present document are also listed. Wire... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.0 Introduction | Actually, almost all SmartBAN services are presented as close solutions where the users adopts a low-level sensor network configuration, and use a specific application coupled with this implemented network configuration. This application prohibits the possibility to benefit from collected data among different solutions... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1 SmartBAN reference model and architecture | |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.0 Introduction | To improve the maintainability and the flexibility, the proposed SmartBAN reference model and architecture is designed as a multi-agent IoT architecture. The SmartBAN reference model shall also fully rely on BAN semantic data, service model, corresponding ontologies (as already standardized in [1]), and shall also addr... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.1 SmartBAN reference model High Level Architecture (HLA) | The SmartBAN reference architecture follows a multi-layer model where all layers: • are communicating to each other; • can be implemented independently in a device depending on the device capabilities and the needs, thus allowing for constraint devices to include just the required functionality. It consists of four lay... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.5 SmartBAN reference architecture: agents definitions | The architecture is built of various software agents in order to provide granularity, flexibility and the ability to adapt to pervasive environment such as BANs. An software agent is a piece of software that functions as an agent for a user or another program, and working autonomy and continuously in a particular envir... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.6 SmartBAN reference architecture: Process and data flows | |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.6.0 Introduction | The aim of clause 5.1.6 of the present document is to describe the overall process and interaction of different components/agents of the SmartBAN Reference Architecture already defined within clause 5.1.5 of the present document, starting from the Setup phase, passing to the sensor enablement phase, service discovery p... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.6.1 Set up phase | The first step in any software application is the Set up phase, where the users provide the adequate information to the proposed architecture. It may be done using a mobile application or a website or any other solution enabling the users to enter data. If a simple architecture is retained, the main players shall be: t... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.6.2 Node Discovery Phase | One of the most complex issues for the integration of SmartBAN in the WoT is the automatic node discovery, which includes the node discovery, service discovery and the effect of the node on the overall SmartBAN network. This step shall be conceived with minimum user's interactions. Figure 16 depicts the node discovery ... |
0501906322d59d0b9af5ed9b13e45aa2 | 103 327 | 5.1.6.3 Measurement Collection Phase | The measurement collection phase consists of collecting raw sensed values in order to add it to the Measurement class in the MyOntoSensProcess ontology. The collection can be periodic, on event triggering or on request. If it is periodic, the DS (Data Scanner agents) shall periodically retrieve the value by invoking th... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.