hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3.4 Call back | A call back is indicated by the SIP Priority header with value "psap-callback" from the PSAP to the user equipment, as defined in IETF RFC 7090 [18]. Any call back from the emergency service shall be handled by the user equipment and indicated to the user. (AEC-CB-01). The media shall be handled as in any incoming comm... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3.5 Invocation of support services by the user | Users who find themselves in an emergency may not remember that their accessibility needs will be met efficiently if they initiate the emergency communication in the recommended way. This could especially be the case if they are used to calling support services in their daily communication. When a user invokes a suppor... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.4 Other technologies for communication services | If other technologies in addition to IMS and SIP are used for session and media control by the user equipment, the underlying communication service is responsible for performing emergency communication according to the procedures described in clause 8.4 of present document. In that case, the service involves the user e... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8 Originating Service Requirements | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.1 General | The originating service handles the emergency communications with the PSAP as requested by the user equipment. The result is that the emergency communications in the interface between the service and the emergency communications network (ESInet) is aligned with the conventions in that interface as specified in ETSI TS ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2 IMS Based Originating Service | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2.1 General | The IMS multimedia telephony service, where the user equipment (UE) is when the emergency communications is established, handles the emergency communications between the user in emergency and the PSAPs. The result shall be that the emergency communications in the interface between the IMS service and the emergency comm... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2.2 Settings | The IMS service shall enable the user to set accessibility related preferences of importance for emergency communications. The settings are stored in the service. These settings comply but are not limited to the following: • Preference for always including RTT initially in both outgoing and incoming communications. (AE... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2.3 Initiation of emergency communications | The emergency communications shall be initiated according to the procedures specified in ETSI TS 126 114 [9], ETSI TS 122 101 [5], clause 10 except clauses 10.2 and 10.3, and ETSI TS 124 229 [8], clauses 4.7 and 5.1.6 for emergency communications in IMS. The exchange with the PSAP shall be performed as specified in ETS... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2.4 Call back | Any call back from the PSAP shall be handled by the IMS service and conveyed to the user equipment. (AEC-CB-01), (AEC-CB-02), (AEC-CB-03). The IMS service shall convey the SIP Priority header with value "psap-callback" from the PSAP to the user equipment, as defined in IETF RFC 7090 [18]. ETSI ETSI TS 103 919 V1.1.1 (2... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.2.5 Visiting regions and networks | Support for roaming user equipment to have emergency communications shall be provided by the visited service. (AEC-RO-07). That causes specific considerations in roaming conditions, specified in ETSI TS 123 167 [7] and ETSI TS 124 229 [8], clauses 4.7 and 5.1.6 which services and user equipment in roaming conditions sh... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3 SIP Based Originating Service | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3.1 General | Originating services here called "SIP based" use IETF RFC 3261 [10] and IETF RFC 8866 [17] for session and media control, and are not included within the IP multimedia subsystem concept (IMS) ETSI TS 122 228 [i.2]. Real time text (RTT) shall be supported as specified in ETSI TS 103 479 [3], clause 6.6.2.4. (AEC-CM01), ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3.2 Settings | The originating service shall enable the user to set accessibility related preferences of importance for emergency communications. The settings may be stored in the user equipment or in the service as decided by the service provider. These settings comply but are not limited to the following: • Preference for always in... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3.3 Initiation of emergency communications | The emergency communications shall be initiated according to the procedures specified in ETSI TS 103 479 [3], clause 6 except 6.1.3, 6.2, 6.3, 6.4 and 6.8. (AEC-SC-01), (AEC-SC-02). Location information shall be included as specified in ETSI TS 103 479 [3], clauses 6.1.2.2 and 6.1.4. Any media preferences indicated by ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3.4 Call back | Any call back from the PSAP shall be handled by the SIP service and conveyed to the user equipment. (AEC-CB-01), (AEC-CB-02), (AEC-CB-03). The SIP service shall convey the SIP Priority header with value "psap-callback" from the PSAP to the user equipment, as defined in IETF RFC 7090 [18]. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.3.5 Visiting regions and networks | When an emergency communication is initiated from a region other than the home region of the user in emergency, some conditions, which always shall be considered, stand out requiring extra considerations specified in clause 9.8 of the present document. International peering or interconnect of PSAP domains is prerequisi... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4 Other technologies for emergency communication | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.1 General | If other technologies in addition to IMS and SIP are used for session and media control by the user equipment, the underlying communication service is responsible for performing emergency communication according to the procedures described in clause 8.4 of present document. If other technologies in addition to IMS and ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.3.1 General | To IMS and native SIP technologies, another complementary method for establishing emergency communications is by using PEMEA specifications according to ETSI TS 103 478 [i.4]. The PEMEA specification provides standardized interfaces for multimedia emergency communications and emergency context information. Refer to ETS... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.3.2 Initiating emergency communication with PEMEA support | If a user of mobile application initiates emergency communications from a user equipment (UE) as described in ETSI TS 103 478 [i.4], the application should establish the emergency communication according to the procedures defined in ETSI TS 126 114 [9], ETSI TS 122 101 [5], clause 10 except clauses 10.2 and 10.3, and E... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.3.3 Emergency communications by IMS in regions without PEMEA support | If a mobile application discovers that a PEMEA service is not available as described in ETSI TS 103 872 [i.7], and the UE supports IMS emergency sessions as specified in ETSI TS 123 167 [7], it shall immediately establish an emergency communication according to the procedures defined in ETSI TS 126 114 [9], ETSI TS 122... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.3.4 Emergency communications by SIP in regions without PEMEA support | If an application discovers that a PEMEA service is not available as described in ETSI TS 103 872 [i.7], and the UE supports SIP based emergency sessions as specified in clause 8.3.3 of the present document, it should immediately establish an emergency communication according to the procedures defined in clause 8.3.3 o... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.3.5 Accessibility related details in use of PEMEA | The emergencyDataSend information as described in ETSI TS 103 478 [i.4], clause 6.2 includes an identity or address to be used for emergency call back. (AEC-SC-03). To utilize the multimedia capabilities of PEMEA or to enrich emergency communications with additional media capabilities, the media and modality preference... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 8.4.4 Use of ETSI TS 103 479 with future technologies | If future technologies in addition to IMS and SIP are used for emergency communications with full accessibility functions according to clause 5 of the present document (AEC-**-**), then the communication between the communication service provider and the emergency communications network and PSAP in the region of the em... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9 Emergency communications network and PSAP | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.1 General | The emergency communications network and PSAPs shall support the mandatory interfaces listed in clause 4.3 and defined in clause 6 of ETSI TS 103 479 [3] and may support optional interfaces listed in clause 4.4 and defined in clause 6 of ETSI TS 103 479 [3] to provide an interface to the originating communication servi... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.2 Media | The media: video, audio and real time text (RTT) shall be supported as specified in ETSI TS 103 479 [3], clauses 6.6.2.4, 6.6.2.2, and 6.6.2.3. (AEC-CM-01), (AEC-CM-02), (AEC-CM-03), (AEC-CM-04), (AEC-CM-05), (AEC-CM-06), (AEC-UI-04). Total conversation shall be supported. (AEC-CM-11). Audio and RTT shall be supported ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.3 Modality and Language indication | The following indications shall be supported by emergency communications networks and PSAPs and be used to convey the need for support of efficient communication with users with disabilities involving specific modality and language needs with call takers. (AEC-ML-03), (AEC-ML-04), (AEC-ML-05), (AEC-ML-06). IETF RFC 837... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.4 Routing | The emergency communications enter the emergency communications network in an interface where the communication can be routed to a PSAP responsible for handling the communication. Then routing to the most appropriate PSAP shall be performed using location information (AEC-RO-01), any type or subtype of emergency servic... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.5 Bridging | When the PSAP has access to multiparty bridging for audio, the bridge operations shall also include video and RTT when these media are used in the emergency communication. The multiparty bridging shall be used when needed for attended call transfer between call takers where the first call taker can stay as long as need... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.6 Call back | A PSAP shall have the possibility to call back to the equipment of the user in emergency, using the routable uri provided in the original emergency communications and the call control and media control procedures specified in ETSI TS 103 479 [3]. (AEC-SC-03), (AEC-CB-01), (AEC-CB-06). The default action shall be to inc... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.7 Communications handling | ETSI TS 103 479 [3] specifies communications handling for letting incoming emergency communications wait for handling by appropriate call takers. The functional accessibility requirements on the PSAP are specified in clause 5 of the present document. In order to arrange for efficient answering on emergency communicatio... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.8 Considerations for PSAP domains | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.8.1 General | When an emergency communication or an emergency callback communication is initiated, the actions specified in clause 9.8 of the present document shall be taken by the emergency communication networks and PSAPs handing the emergency communication. NOTE: Some of the considerations are of extra importance when the user in... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.8.2 Forest Guide for routing to the responsible PSAP domain | When an emergency communication enters an emergency communication network, from a communication service using SIP, the emergency communication shall request information regarding routing to the region responsible for the location of the emergency from a Forest Guide. (AEC-RO-09). NOTE: For emergency communications from... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.8.3 Spoken or written language competence | For efficient handling of the emergency communication, when the user and the call taker have no spoken or written language competence in common, the PSAP and call taker shall be provided with the ability to transfer the communication to a better matching call taker or to invoke a text relay service or language translat... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 9.8.4 Sign language handling | All PSAPs shall have capability to support video communication for sign language users and invoke proper sign language competence in the emergency communication. (AEC-SS-01), (AEC-SS-02), (AEC-SS-03), (AEC-SS-04), (AEC-SS-05), (AEC-SS-06), (AEC-SS-07). NOTE: The user may have needs to use one specific sign language whi... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 10 Supporting Services | Supporting services include relay services, language translating services and expert services, which may be invoked during emergency communications to support resolving the emergency. The main method to invoke support services in the communication is to include it by automatic or manual means by the PSAP through one mu... |
0c5195871d3d56854d267137a760b496 | 103 918 | 1 Scope | The present document contains specification of interoperability test descriptions to validate implementations of ETSI TS 103 097 [1], ETSI TS 102 941 [i.3] and ETSI TS 103 759 [2]. |
0c5195871d3d56854d267137a760b496 | 103 918 | 2 References | |
0c5195871d3d56854d267137a760b496 | 103 918 | 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... |
0c5195871d3d56854d267137a760b496 | 103 918 | 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... |
0c5195871d3d56854d267137a760b496 | 103 918 | 3 Definition of terms, symbols and abbreviations | |
0c5195871d3d56854d267137a760b496 | 103 918 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 097 [1], ETSI TS 102 940 [i.1], ETSI TS 102 941 [i.3] and ISO/IEC 15408-2 [i.2]. |
0c5195871d3d56854d267137a760b496 | 103 918 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 097 [1], ETSI TS 102 940 [i.1], ETSI TS 102 941 [i.3] and ISO/IEC 15408-2 [i.2] apply. |
0c5195871d3d56854d267137a760b496 | 103 918 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 097 [1], ETSI TS 102 941 [i.3], ETSI TS 102 940 [i.1] and ISO/IEC 15408-2 [i.2] apply. |
0c5195871d3d56854d267137a760b496 | 103 918 | 4 Requirements and configuration | |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.1 Requirements | |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.1.1 Overview | In order to perform the interoperability tests defined in the present document, all EUTs shall implement the generic mandatory requirements defined in clauses 4.1.2 and 4.1.3. NOTE: Interoperability testing between two IUTs cover mandatory requirements and optional requirements supported by the IUTs. |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.1.2 ITS stations | Mandatory requirements: • The ITS-S shall support data communication using security mechanisms described in ETSI TS 103 759 [2]. • The ITS-S shall support algorithms and key length according to the Certificate Policy [3]. • In order to participate in misbehaviour reporting tests, the ITS-S shall be able to send CAMs an... |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.1.3 Misbehaviour Authority | Mandatory requirements: • The Misbehaviour Authority shall support data communication using security mechanisms described in ETSI TS 103 759 [2]. • The Misbehaviour Authority shall support algorithms and key length according to the Certificate Policy [3]. |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.2 Configurations | |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.2.1 Overview | In order to participate in the test with the present configurations, IUTs (participating entities) shall be configured as follows: • All participating ITS-Ss are in the "authorized" state (equipped with valid ATs). • The AT of participating ITS-Ss allows the transmission of CAMs and DENMs in the time and place of UC ex... |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.2.2 CFG_LONG_RANGE communication | This clause describes the configuration used to execute misbehaviour reporting test scenarios. The configuration contains the following entities: • Actor - The virtual ITS-S producing the fault message or behaviour. • Detector - The ITS-Sdetecting the misbehaviour and sending the MR using the long range communication c... |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.2.3 CFG_SHORT_RANGE communication | This clause describes the configuration used to execute misbehaviour reporting test scenarios focused on forwarding between an ITS-S and an RSU. The configuration contains the following entities: • Actor - The virtual ITS-S producing the fault message or behaviour. • Detector - The ITS-S detecting the misbehaviour and ... |
0c5195871d3d56854d267137a760b496 | 103 918 | 4.3 Inconsistent ITS messages generator | A virtual ITS-S device was developed by ETSI. This virtual device generates inconsistent ITS messages according to the different usage required by the Interoperability test descriptions. |
0c5195871d3d56854d267137a760b496 | 103 918 | 5 Requirements to be tested | |
0c5195871d3d56854d267137a760b496 | 103 918 | 5.1 Overview | The clauses below collect and enumerate the requirements that can be tested with the present interoperability test specification. |
0c5195871d3d56854d267137a760b496 | 103 918 | 5.2 ITS-S communication messages | NN Requirement References UCs 1.1. ITS-S may implement a CAM Speed local misbehaviour detection service ETSI TS 103 759 [2], clause 4.2.2 6.2.1, 6.3.3 1.2. ITS-S may implement a CAM Position local misbehaviour detection service ETSI TS 103 759 [2], clause 4.2.2 6.2.2 1.3. ITS-S may implement a CAM Acceleration local mi... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6 Interoperability test descriptions | |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.1 Overview | Interoperability test descriptions consist of two groups: • Misbehaviour Detection service for class 1 as defined in ETSI TS 103 759 [2], clause 6.2. • Misbehaviour Detection service for class 2 as defined in ETSI TS 103 759 [2], clause 6.2. These groups are described in the clauses below. |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.2 Misbehaviour Detection service for class 1 | |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.2.1 CAM speed misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS1_CAM_SPEED_UC1 Objective Verify that CAM speed misbehaviour detector generated a MR Description The "actor" ITS-S is sending secured CAM with inconsistent speed value regarding the type of vehicle. The "detector" ITS-S detects the misbehaviour and generates a MR... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.2.2 CAM position misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS1_CAM_POSITION_UC1 Objective Verify that CAM position misbehaviour detector generated a MR Description The "actor" ITS-S is sending secured CAM with inconsistent position value regarding the position of the receiver and coverage area. The "detector" ITS-S detects... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.2.3 CAM Acceleration misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS1_CAM_LONG_ACC_UC1 Objective Verify that CAM acceleration misbehaviour detector generated a MR Description The "actor" ITS-S is sending secured CAM with inconsistent longitudinal acceleration value regarding the type of vehicle (e.g. 20 m/s/s). The "detector" ITS... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.2.4 CAM Security misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS1_CAM_SECURITY_UC1 Objective Verify that CAM security misbehaviour detector generated a MR - Wrong HeaderInfo PSID Description The "actor" ITS-S is sending secured CAM with HeaderInfo Psid field set to AID_DENM (see ETSI TS 102 965 [4], clause 7.1.1). The "detect... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.3 Misbehaviour Detection service for class 2 | |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.3.1 CAM Beacon misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS2_CAM_STATIC_UC1 Objective Verify that CAM static data misbehaviour detector generated a MR Description The "actor" ITS-S is sending several secured CAMs with a variable frequency between 0,5 to 30 Hz. The MA accepts the MR and send a report to the Device Operato... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.3.2 CAM Static misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS2_CAM_STATIC_UC1 Objective Verify that CAM static data misbehaviour detector generated a MR Description The "actor" ITS-S is sending several secured CAMs with as VehicleRole set to passengerCar. One ITS-S is starting to send several secured CAMs with a different ... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.3.3 CAM speed misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS2_CAM_SPEED_UC1 Objective Verify that CAM speed misbehaviour detector generated a MR Description One ITS-S sends several secured CAM with a valid speed regarding the type of vehicle (e.g. passengerCar with a speed of 50 km/h). The "actor" ITS-S is sending secured... |
0c5195871d3d56854d267137a760b496 | 103 918 | 6.3.4 CAM acceleration misbehaviour detector | Interoperability Test Description Identifier TD_MBR_CLASS2_CAM_LONG_ACC_UC1 Objective Verify that CAM acceleration misbehaviour detector generated a MR Description One ITS-S sends several secured CAM with a valid longitudinal acceleration value regarding the type of vehicle (e.g. a passengerCas with an acceleration of ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 1 Scope | The present document specifies the facility layer service responsible for the generation of dynamic parking availability information in various transport environments (on street, off street, in parking facilities and park & ride stations). The dissemination is intended from a roadside or any other appropriate node, for... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 2 References | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 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... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 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... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 3 Definition of terms, symbols, and abbreviations | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 3.1 Terms | For the purposes of the present document, the terms given in TS 16157-6 [i.1] and the following apply: authority: entity which has the right and ability to perform certain tasks on a subject vehicle NOTE 1: Within the present document, authority can be transferred between the user and the service provider and does not ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 3.2 Symbols | Void. |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 103 300-1 [i.6], ETSI TS 103 300-2 [i.7] and the following apply: AVP Automated Valet Parking AVPS Automated Valet Parking System BTP Basic Transport Protocol CCH Control Channel CDD Common Data Dictionary FCP Functional Configuration Profile ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4 PAS contextual introduction | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.1 Background | Mobility services are users' value-added services which support the mobility of users in their various mobility activities contexts. These services are necessary to maintain the user' mobility system operational (e.g. its vehicle), to facilitate the transition between various transport modalities, and to support the tr... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.2 General information about parking place | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.2.1 Introduction | A parking place can be divided into several elements (sub-place, parking areas, parking identified areas) facilitating users' and vehicles' accesses to relevant parking spaces. Each element of a parking place, a parking sub-place, a parking identified area is constituted of the following facilities: • Vehicular access.... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.2.2 Parking place organizational aspects | The present document considers parking organizations which are represented in Figure 2, respecting the example of place hierarchy as provided in TS 1657-6 [i.1]. ETSI ETSI TS 103 916 V2.1.1 (2024-01) 14 Figure 2: Example of place hierarchy A given parking place may include several parking sub-places, parking areas and ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.2.3 Services provided by the PAS | The Parking Availability Service (PAS) provides real time generic information about the Parking Place, its management, the aggregated status of the parking place, its detailed status (e.g. per space) and Related POIs. Other optional information can be provided according to the parking profile being considered. The prov... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 4.2.4 Related POIs | Related POIs can be part of the parking when restricted to parking users and directly available only after accessing to the parking place. But other Related POIs (outside the parking place), can also be locally, publicly available to a parking place user. It would be complex and inefficient to provide detailed informat... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5 PAS functional description | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.1 Introduction | The Parking Availability Service (PAS) is an ITS-S service which provides static and dynamic real time information about parking spaces such as detailed information for single parking spaces and the availability of parking services (such as vehicle parking, parking space reservation, payment modalities and contacts and... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.2 PAS in the ITS architecture | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.2.0 Overview | Figure 4 presents the main components of the ITS-S architecture that directly impact the PAS operation. ETSI ETSI TS 103 916 V2.1.1 (2024-01) 17 Figure 4: Functional categories Figure 4 shows 4 functional categories: • VRU portable devices. • Vehicles (human driven and automated). • Road Infrastructure. • In the Cloud ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.2.1 Vehicle Parking Information | Vehicle parking information is provided to potential users of the parking either via locally broadcast messages or from a central system (unicast push mode). They are real time information which provide available parking capabilities and associated management information necessary to select a parking space, optionally ... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.2.2 Parking Space Reservation and Payment | After a real time, reception of the parking availability information, the potential user of the main service can initiate a reservation based on received information. If the parking is subject to a payment, the reservation can be secured by a prepayment so authorizing the user to arrive and use the reserved parking spa... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.2.3 Related user' services Reservation and Payment | A limited number of related users' services which are associated to the navigation of vehicles, people and goods inside the parking can be the object of the communication about their availability, payment, and reservation information. For paid services, a reservation can be achieved on basis of communicated information... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.3 PAS functional architecture | The PAS is distributed in ITS-Stations facilities layers which are originating POIMs-PA, and which are receiving POIMs-PA for the supply of the service to customers. Typically, the originating ITS-S is located at the level of a Roadside equipment or at the level of a central system, while the receiving ITS-Ss are locat... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.4 Interfaces of the PAS | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.4.0 Overview | The PAS is managed by the Parking Management Application at the level of the service providers and by a mobility support application at the level of the service users. PAS is a real time information service which provides the availability of parking services and other related mobility services either directly (e.g. val... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.4.2 Interface to the ITS Application (IF-App) | An ITS application is a function of the ITS application layer that implements the application logic of one or more-use cases. The Parking Management application provides data frames and data elements which are used to build the POIMs-PA. Received POIMs-PA contents are provided to the Parking Management application afte... |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.4.3 Interface to the ITS-S networking and transport layer (IF-N&T) | |
dffd2716e833c86a27c24ff378d6f55d | 103 916 | 5.4.3.1 Networking & Transport Layer | If the ITS-S does not support the MCO, the PAS shall exchange information with the ITS Networking & Transport layer via the interface IF.N&T, as depicted in Figure 6. At the originating ITS-S, the PAS shall provide the POIM-PA embedded in a Facility-layer Service Data Unit (FL-SDU) together with Protocol Control Inform... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.