hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2481a464970b9169f540027dd8035ec8 | 103 256 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CSS3 Third revision of the Cascading Style Sheets standard DB Data Base HTML Hyper Text Markup Language HTML5 Fifth revision of the HTML standard JS Javascript JSON JavaScript Object Notation PHP Hypertext Preprocessor QoE Quality of Experienc... |
2481a464970b9169f540027dd8035ec8 | 103 256 | 4 General aspects of a reference web page | Quality of web experience represents an important topic for service or content providers. Measurement of such services at the end-user side is not a trivial task and various factors are influencing the overall QoE perception. In order to suppress the influence of the content a standardized web page is necessary. The mo... |
2481a464970b9169f540027dd8035ec8 | 103 256 | 4.1 Web QoE reference page composition | After successful recording of the articles from the RSS feeds, all content of the web page is stored locally in the database, which allows perfect control over page loading times. Interactive content such as the news articles is updated on a daily basis, with the possibility to update the database also manually from th... |
2481a464970b9169f540027dd8035ec8 | 103 256 | 4.3 Composition rules for a Web QoE reference page | Design and composition of the page was developed by taking into account the recommendations for the development of reference web pages from W3C® and general concepts of various existing news pages on the Internet (Spiegel.de®, Guardian.com®). Therefore, the following features are essential. • Responsive design, such th... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 1 Scope | The present document provides specifications of infrastructure related ITS services to support communication between infrastructure ITS equipment and traffic participants using ITS equipment (e.g. vehicles, pedestrians). It defines services in the Facilities layer for communication between the infrastructure and traffi... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 2 References | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 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... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 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... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 3 Definitions and abbreviations | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: destination area: geographic area in which a message is disseminated NOTE: The definition is compliant to ETSI EN 302 637-3 [13]. driver awareness zone: area in which the driver will be informed about upcoming situations NOTE: The defi... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AC Access Category AC_BE Access Category Best Effort AC_BK Access Category Background AC_VI Access Category Video AC_VO Access Category Voice ADU Application Data Unit AID Action IDentifier ASN Anstract ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.1 Naming convention | Within the scope of the present document, the term "message" refers to the Facilities layer PDU; the term "payload" refers to the applications layer ADU. The payload is generated by the application and provided to the corresponding service of the Facilities layer. The Facilities service merges the ItsPduHeader with the... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.3 Infrastructure services in the ITS organizational architecture | Within the role "System Operation" as defined in ISO/TS 17427 [10], the following sub roles are relevant for the infrastructure services: • "Content Provision" is responsible for generating the information that is conveyed in the message. This task is included in any application providing information to the application... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.4 Interfaces of the infrastructure services | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.4.1 Interface between Application layer and Facilities layer | The infrastructure services within the Facilities layer provide APIs to applications for the processing of the payload at the transmitting ITS-S and the receiving ITS-S. An application may execute requests to the infrastructure services in the Facilities layer to trigger, update or terminate transmission of a message. ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.4.2 Interface between Facilities layer and Management entity | The infrastructure services may exchange information with the Management entity. This includes the default service communication parameters specified in clauses 5 to 8. The interface MF-SAP may be realized as the MF-SAP ETSI TS 102 723-5 [i.5]. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.4.3 Interface between Facilities layer and Security entity | The infrastructure service may exchange information with the Security entity. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.4.4 Interface between Facilities layer and the N&T layer | The infrastructure services deliver the message as payload to the ITS Networking & Transport Layer for dissemination via the NF-SAP. The ITS Networking & Transport Layer indicates the reception of an ITS message to the infrastructure services. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.5 Common protocol requirements for infrastructure services | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.5.1 Security for messages used by infrastructure | The security mechanisms for messages used by the infrastructure service as specified in the present document shall use the message authentication with signatures to be verified at the receiving ITS-S with public keys contained in certificates. A certificate indicates its holder's permissions, i.e. what statements the h... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.5.2 Message payload encapsulation | The ItsPduHeader header as defined in ETSI TS 102 894-2 [2] shall be used to encapsulate the payload in order to construct messages. The ITS PDU header includes the following elements: • protocolVersion: Version of the ITS payload contained in the message as defined for the specific infrastructure service. • messageID:... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.5.3 Message encoding scheme | Unless specified otherwise, the Unaligned PER encoding scheme as specified in Recommendation ITU-T X.691 [11] shall be used for the encoding of the messages specified in the present document. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.6 Protocol version | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.6.1 Protocol version definition | The value of the protocol version for the messages SPATEM, MAPEM, IVIM, SREM, SSEM, RTCMEM is individual and independent of each other. It is defined in the ItsPduHeader for each message and identified by the protocolVersion data element (see clauses 5 to 8). |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 4.6.2 Protocol version handling | If the ASN.1 definition of the protocol is extended without compromising the backwards compatibility, the data element protocolVersion will not be increased. This allows the receiving ITS-S to process the message correctly (except the extensions) without the need for immediate update. An update for protocol interoperab... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5 Traffic Light Maneuver (TLM) service | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.1 TLM service overview | The TLM service is one instantiation of the infrastructure services to manage the generation, transmission and reception of SPATEM messages. The TLM service includes safety-related information for supporting traffic participants (vehicles, pedestrians, etc.) to execute safe maneuvers in an intersection area. The goal i... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.2 TLM service | The TLM service instantiated in an ITS-Station shall provide the communication services defined in clause 4.2. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.3 TLM service message and version | The TLM service uses the message SPATEM as defined in Annex A. The header of SPATEM shall be as specified in the data dictionary ETSI TS 102 894-2 [2]. The data elements of SPATEM payload shall be as specified in CEN ISO/TS 19091 [8]. The protocolVersion (defined in the header) of SPATEM message based on the present do... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4 TLM service dissemination | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4.1 TLM service identification | The TLM service provides real-time information of the traffic light signal phase and timing of an intersection or parts of an intersection identified by the intersection reference identifier. The timestamp indicates the order of messages within the given time system as defined in CEN ISO/TS 19091 [8]. There is no addit... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4.2 TLM service trigger, update, repetition and termination | The application triggers the TLM service for the transmission of SPATEM. The application provides all data content included in a SPATEM payload. The TLM service constructs a SPATEM and delivers it to the ITS Networking & Transport Layer for dissemination. The SPATEM is not repeated. The TLM service shall be terminated,... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4.3 TLM service communication requirements | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4.3.1 TLM service communication overview | The TLM service uses SPATEM to disseminate the status of the traffic light controller, traffic lights and intersection traffic information. It transmits continuously in real-time the information relevant for all maneuvers in the area of an intersection. The goal is to address all traffic participants using the intersec... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 5.4.3.3 TLM service communication requirements for long range communication | This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2]. Table 7: TLM service communication requirements for long range access technologies Requirement Value Comment Operational communication service parameters CSP_LogicalChan... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6 Road and Lane Topology (RLT) service | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.1 RLT service overview | The RLT service is one instantiation of the infrastructure services to manage the generation, transmission and reception of a digital topological map, which defines the topology of an infrastructure area. It includes the lane topology for e.g. vehicles, bicycles, parking, public transportation and the paths for pedestr... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.2 RLT service | The Road and Lane Topology service instantiated in an ITS-Station shall provide either the transmission or the reception service defined in clause 4.2. Additionally the Road and lane Topology service supports the following functionality: • Continuous transmission for infinity of the MAPEM. As the MAPEM message is not c... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.3 RLT service message and version | The RLT service uses the message MAPEM as defined in Annex B. The header of MAPEM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of MAPEM payload are defined in CEN ISO/TS 19091 [8], Annex G. The protocolVersion (defined in header) of MAPEM message based on the present document is set to val... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4 RLT service dissemination | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4.1 RLT service identification | The RLT service uses MAPEM which represents the topology/geometry of a set of lanes. E.g. considering an intersection MAPEM defines the topology of the lanes or parts of the topology of the lanes identified by the intersection reference identifier. The MAPEM does not change very often in time. The same MAPEM is retrans... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4.2 RLT service trigger, update, repetition and termination | The application triggers the Road and lane Topology service for the transmission of the MAPEM. The application provides all data content included in the MAPEM payload. The RLT service constructs a MAPEM and delivers it to the ITS Networking & Transport Layer for dissemination. As the MAPEM content is only changed, e.g.... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4.3 RLT service communication requirements | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4.3.1 RLT service communication overview | The RLT service uses MAPEM to define all the road topological details. It uses the lane "connection" (between ingress and egress lanes) which includes the signal-group identifier which is the link to SPATEM signalling information. MAPEM shall be transmitted continuously together with the SPATEM to inform the traffic pa... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 6.4.3.3 RLT service dissemination parameters for long range communication | This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2]. Table 12: RLT service communication requirements for long range access technologies Requirement Value Comment Operational communication service parameters CSP_LogicalCha... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7 Infrastructure to Vehicle Information (IVI) service | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.1 IVI service overview | IVI service is one instantiation of the infrastructure services to manage the generation, transmission and reception of the IVIM messages. An IVIM supports mandatory and advisory road signage such as contextual speeds and road works warnings. IVIM either provides information of physical road signs such as static or var... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.2 IVI service | The IVI service instantiated in an ITS-Station shall provide either the transmission or the reception service defined in clause 4.2. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.3 IVI service message and version | The IVI service uses the IVIM as defined in Annex C. The header of the IVIM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of the IVIM message payload are defined in CEN ISO/TS 19321 [7]. The protocolVersion (defined in the header) of IVIM message based on the present document is set to valu... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4 IVI service dissemination | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4.1 IVI service identification | The IVIM identification is enabled by the parameter {IVIM.ivi.mandatory.iviIdentificationNumber}. Each time a new IVIM is generated upon an application request, a new iviIdentificationNumber (as defined in CEN ISO/TS 19321 [7]) value shall be assigned by the IVI service. When a iviIdentificationNumber is set, it shall ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4.2 IVI service trigger, update, repetition and termination | IVI service trigger refers to the process of the generation and transmission of an IVIM when the IVI service of the sending ITS-S receives an application request. The IVI service shall then generate a new message with status {IVIM.ivi.mandatory.iviStatus} set to "new". An IVIM content is updated e.g. by the service pro... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4.3 IVI service communication requirements | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4.3.1 IVI service communication parameters for short-range communication | An IVIM shall be transmitted if applicable, e.g. when it is applicable in time (e.g. a speed limitation only valid between 8:00 and 20:00) and due to the context as determined by the sending ITS-S (e.g. a speed limitation applicable in case of fog). An IVIM shall be disseminated to reach as many ITS-S as possible, loca... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 7.4.3.2 IVI service dissemination parameters for long-range communication | This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2]. Table 16: IVI service communication requirements for long range access technologies Requirement Value Comment Operational parameters CSP_LogicalChannelType SCH Safety ch... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8 Traffic Light Control (TLC) service | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.1 TLC service overview | The Traffic Light Control service is one instantiation of the infrastructure services to manage the generation, transmission of SREM messages and SSEM messages. The TLC service supports prioritization of public transport and public safety vehicles (ambulance, fire brigade, etc.) to traverse a signalized road infrastruc... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.2 TLC service | The TLC service shall provide the communication service defined in clause 4.2 and support additionally the following functionality: • Generation of SREM with a single request or sequence of signal requests (e.g. related to several signalized intersections). • Generation of SSEM with a signal status response. • Single o... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.3 TLC service message and version | The Signal Control service uses the SREM as defined in Annex D and the SSEM as defined in Annex E. The header of the SREM and the SSEM are defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of the SREM and the SSEM payload are defined in CEN ISO/TS 19091 [8]. The protocolVersion (defined in the hea... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4 TLC service dissemination | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.1 TLC service identification | The SREM is identified by a request identification which is unique. Additionally a sequence number identifies a sequence of requests. If the request or one of the requests with the same request identification has changed, the sequence number will be incremented. For having a clear relation between an SREM request and t... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.2 TLC service trigger, update, repetition and termination | SREM The SREM is transmitted based on the needs of the vehicle operator and triggered by applications. The application provides all data included in SREM. The traffic light control service shall construct a SREM payload and deliver it to the N&T (Networking and Transport) layer for dissemination. The SREM may be repeat... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.3 TLC service communication parameters | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.3.1 TLC service communication overview | The SREM is transmitted on demand (e.g. bus driver) or automatically by an application (e.g. in the bus) based on external conditions (e.g. position, reception of a specific SPATEM, etc.) It is transmitted once or continuously depending on the needs of the implementation. The SSEM is sent as response to a SREM. Both me... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.3.2 TLC service communication parameters for short range access technologies | Table 17 provides the requirements for the broadcast communication. The structure of the requirements is in accordance with ISO/TS 17423 [i.2]. ETSI ETSI TS 103 301 V1.2.1 (2018-08) 29 The ITS station management uses the communication requirements to select suitable ITS-S communication protocol stacks. Some examples of... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 8.4.3.3 TLC service communication parameters for long range communication | This clause provides the communication requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2]. Table 22: TLC service communication profile for long range access technologies Requirement Value Comment Operational parameters CSP_LogicalChannelType SFCH... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9 GNSS positioning correction (GPC) service | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.1 GPC service overview | The GPS service uses positioning correction message for GNSS as defined by the RTCM (Radio Technical Commission For Maritime Services - www.rtcm.org) . The RTCMEM message enables several types of position corrections (e.g. GPS, GLONAS, RTK). The RTCM correction data is generated by road side equipment (stationary GNSS ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.2 GPC service | The GNSS positioning correction service instantiated in an ITS-Station shall provide the communication services defined in clause 4.2. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.3 GPC service message and version | The GPC service uses the message RTCMEM defined in Annex F. The header of RTCMEM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of RTCMEM payload are defined in the Annex F of the present document. The protocolVersion (defined in the header) of RTCMEM based on the present document is set to ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4 GPC service dissemination | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4.1 GPC service identification | The GPC service provides real-time information for GNSS positioning correction data, There is no additional identifier needed to distinguish a RTCMEM from a previous one. |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4.2 GPC service trigger, update, repetition and termination | The application triggers the GPC service for the transmission of the RTCMEM. The application provides all data content included in the RTCMEM payload. The GPC service constructs a RTCMEM and delivers it to the ITS Networking & Transport Layer for dissemination. The RTCMEM is not repeated. The RTCMEM transmission may be... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4.3 GPC service communication requirements | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4.3.1 GPC service communication overview | The GPC service uses RTCMEM to disseminate the GNSS correction data. It transmits continuously in real-time the information relevant for enabling accurate positioning to the surrounding moving ITS stations. The goal is to support all traffic participants to execute safely location based maneuvers (e.g. for safe executi... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 9.4.3.3 GPC service dissemination parameters for long range communication | This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2]. Table 26: GPC service communication requirements for long range access technologies Requirement Value Comment Operational communication service parameters CSP_LogicalCha... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 10 Basic services running on ITS infrastructure devices | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 10.1 Basic service overview | Infrastructure ITS devices (e.g. road side unit) will communicate to vehicles/pedestrians and are on the other side connected to traffic controllers, traffic control centers (urban, interurban) or work in a standalone operation mode. From the application point of view, they use the same services like all other ITS stat... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 10.2 DEN service on ITS infrastructure devices | Infrastructure ITS devices shall be able to transmit and to receive DENMs and provide the DEN (Decentralized Environmental Notification) service as defined in ETSI EN 302 637-3 [13]. Due to the role of the infrastructure device additional applications may run using the DEN basic service: • Generation and transmission o... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 10.3 CA service on ITS infrastructure devices | Infrastructure ITS devices shall be able to transmit CAM's and provide the CA (Common Awareness) service as defined in ETSI EN 302 637-2 [12]. Due to the role of the infrastructure device additional applications may run using the CA basic service: • Generation of CAM's for notification of protected communication zones ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11 Communication Profiles | |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.1 Introduction | The messages for infrastructure services as specified in the present document shall use one of the following communication profiles: • CPS_001 Transmission of ADU over ITS-G5 • CPS_002 Transmission of ADU over WLAN 2.4 GHz in infrastructure mode • CPS_003 Transmission of ADU over WLAN 5.8 GHz in infrastructure mode • C... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.2 Basic communication profile settings | The communication profiles defines in the following clauses 11.3 to 11.7 use different communication access but shall all use the mandatory Geonetwork Protocol (ETSI EN 302 636-4-1 [3]) and the Basic Transport Protocol (ETSI EN 302 636-5-1 [4]). This assures interoperability, application security and authorization mech... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.3 CPS_001 | This profile defines the communication parameter settings for dissemination of an ADU using GeoNetworking/BTP over ITS G5. The ITS station shall implement the following protocols: • Basic Transport Protocol (ETSI EN 302 636-5-1 [4]) using parameter as defined in clause 11.2. • GeoNetworking protocol (ETSI EN 302 636-4-... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.4 CPS_002 | This profile defines the communication settings for dissemination of an ADU using GeoNetworking/BTP over WLAN in infrastructure mode in the 2,4 GHz frequency band (ISM). The ITS station shall implement the following protocols: • Basic Transport Protocol (ETSI EN 302 636-5-1 [4]) using parameter as defined in clause 11.... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.5 CPS_003 | This profile defines the communication settings for dissemination of an ADU using GeoNetworking/BTP over WLAN in infrastructure mode in the 5,8 GHz frequency band (ISM). The ITS station shall implement the following protocols: • Basic Transport Protocol (ETSI EN 302 636-5-1 [4]) using parameter as defined in clause 11.... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.6 CPS_004 | This profile defines the communication parameter settings for dissemination of an ADU using GeoNetworking/BTP over LTE-V2X sidelink. The ITS station shall implement the following protocols: • Basic Transport Protocol (ETSI EN 302 636-5-1 [4]) using parameter as defined in clause 11.2. • GeoNetworking protocol (ETSI EN ... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 11.7 CPS_005 | This profile defines the communication settings for dissemination of an ADU using BTP/GeoNetworking encapsulated within UDP-IP/TCP-IP based data services (e.g. using cellular communication) interface. It applies tunnelling of GeoNetworking packets through UDP-IP/TCP-IP version 4/version 6. The ITS station shall impleme... |
57d49adcd71876144b7a5a6dfc3f1ce2 | 103 301 | 12 Security Profile | The Generic security profile as defined in ETSI TS 103 097 [6] shall be applied to messages used by the TLM, RLT, IVI, TLC, GPC services. Additional HeaderField types are not allowed. ETSI ETSI TS 103 301 V1.2.1 (2018-08) 39 Annex A (informative): ASN.1 specification of SPATEM This annex provides the ASN.1 specificatio... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 1 Scope | The present document presents an overview of the architecture for a generic mission critical service for use by a Critical Communications Application in network and terminal over a broadband IP bearer, with specific focus for LTE. The architecture is part of the overall Critical Communications Architecture Reference Mo... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 2 References | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 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... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 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... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 3 Definitions and abbreviations | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 5-tuple: set of five values required to specify a TCP or UDP connection, comprising a protocol identifier (TCP or UDP), a source IP address, a source port number, a destination IP address and a destination port number Access Point Name... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AGNSS Assisted Global Navigation Satellite System AL Ambience Listening APN Access Point Name ASCII American Standard Code for Information Interchange ASSI Alias Short Subscriber Identity AVL Automatic V... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4 Architecture overview | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.1 Architecture reference | The Critical Communications Architecture Reference model is detailed in ETSI TR 103 269-1 [i.11]. The architecture and interfaces are shown in figure 1. ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 16 Figure 1: CCS Reference Model The present document describes the architecture of interface 4 in the reference model shown in... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.2 Configurations | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.2.0 Functional Architecture | The functional architecture covered in the present document is presented in the following clauses. ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 17 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.