1 / 25

STF 404 "ITS Application ID" Report 1

Dr. Hans-Joachim Fischer Fichtenweg 9 89143 Blaubeuren Germany +49 7344 175340 HJFischer@fischer-tech.info. STF 404 "ITS Application ID" Report 1. Dr. Maria Grazia Verardi 292, chemin du Valbosquet 06600 Antibes France +33 6 3797 1473 mg.verardi@ylum.eu. Introduction.

raquel
Download Presentation

STF 404 "ITS Application ID" Report 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dr. Hans-Joachim Fischer Fichtenweg 9 89143 Blaubeuren Germany +49 7344 175340 HJFischer@fischer-tech.info STF 404 "ITS Application ID" Report 1 Dr. Maria Grazia Verardi 292, chemin du Valbosquet 06600 Antibes France +33 6 3797 1473 mg.verardi@ylum.eu

  2. ITS application identifier Introduction Real time handling of ITS applications is based on unique identifiers (ID). Uniqueness of these identifiers can be ensured e.g. by a registration authority, assigning values of IDs. In order to keep the payload in the narrow wireless channels small, small numbers used as IDs are preferable. CEN TC278 WG9 together with ISO TC204 WG15 jointly defined the DSRCApplicationEntityID and assigned numbers for groups of applications. DSRCApplicationEntityID is presented in an element with minimum 6 bits length: INTEGER (0..31,...) IEEE maintains a registry, assigning numbers to individual applications, rather than to application classes. These IDs are referred to as PSID (Provider Service Identifier) in IEEE 1609. However the IEEE registry also uses the small numbers from CEN TC278 WG9 / ISO TC204 WG15 with the same meaning. PSID is presented in a 4 octets element: INTEGER(0..232-1). ISO defined a serviceID presented in an element with minimum 1 octet length: INTEGER (0..127,...), taking into account the developments at CEN and IEEE. ETSI started to develop standards for ITS where such an ID is needed.

  3. ITS application identifier Objectives • For global applicability, the ITS community needs a number scheme for IDs compliant to DSRCApplicationEntityID and to PSID, taking also into account the developments at ISO TC204 WG16 / WG18 and CEN TC278 WG16. • STF 404 shall develop: • A common ASN.1 format for applicationID. • A specification on the global / local usage of this identifier. • An explanation on how the specified approach considers the various existent definitions at IEEE, ISO and CEN. • A proposal for a framework (registration / standardization) on who and how to assign values of applicationID to specific ITS applications.

  4. ITS application identifier CEN / ISO In the 90ths of the last century CEN TC278 and ISO TC204 started to develop jointly standards for Road Transport and Traffic Telematics (RTTT) / Intelligent Transport Systems (ITS). TC278 WG9 published EN 12834. It specified the identifier DSRCApplicationEntityID used to uniquely identify classes of RTTT / ITS applications and assigned initial values (0 - 16). TC204 WG15 published ISO 15628. It confirms the specification of DSRCApplicationEntityID done in EN 12834 and identified usage of some remaining value ranges (17 - 19).

  5. ITS application identifier DSRCApplicationEntityID ISO 15628

  6. ITS application identifier IEEE Starting in ISO TC204 WG15, US experts developed the US version of DSRC, which later on lead to the set of IEEE 1609 WAVE standards. WAVE defines a Provider Service Identifier (PSID) which is an extension of CEN/ISO DSRCApplicationEntityID. WAVE adds further application classes and changes the number presentation to the ASN.1 type ENUMERATED equal to a four octet unsigned Integer. In a second step, the ENUMERATED type is replaced by INTEGER(0 .. 232-1). Recently, WAVE works on a further modification towards a presentation with variable length. IEEE created a registration authority for PSID.

  7. ITS application identifier WAVE service advertisement

  8. ITS application identifier WAVE short message

  9. ITS application identifier Provider Service Identifier (PSID) Provider Service Identifier is 4 octets long and identifies the service being offered. https://standards.ieee.org/regauth/PSID/PSID_Main.html

  10. ITS application identifier PSID The original specification of PSID is: INTEGER(0..232-1). 0: system, 1: automatic-fee-collection, 2: freight-fleet-management, 3: public-transport, 4: traffic-traveler-information, 5: traffic-control6: parking-management, 7: geographic-road-database, 8: medium-range-preinformation, 9: man-machine-interface, 10: intersystem-interface, 11: automatic-vehicle-identification, 12: emergency-warning, 13: private, 14: multi-purpose-payment, 15: dsrc-resource-manager, 16: after-theft-systems, 17: cruise-assist- highway-system, 18: multi-purpose-information system,19: public-safety, 20: vehicle-safety, 21: general-purpose-internet-access,22: onboard diagnostics, 23: security manager, 24: signed WSA, 25:ACI conflict with ISO 15628 Complements ISO 15628

  11. PSID Latest developments at IEEE indicate a modification towards a presentation scheme with variable length using a non-standardized coding scheme: ITS application identifier

  12. ITS application identifier ISO TC204 WG16 - CALM Around the year 2000, ISO TC204 WG16 started to develop a basic set of communication standards under the name of CALM (Communications Access for Land Mobiles), aiming on integration and harmonization of developments done so far at CEN, ISO and IEEE. In the context of FAST service advertisement, an application identifier serviceID was specified in ISO 24102. The ASN.1 type is INTEGER(0..127,...). This approach continues to provide the functionality of all existing designs.

  13. ITS application identifier FAST NPDU

  14. ITS application identifier Example FAST Service Advertisement Frame (SAF)

  15. ITS application identifier FAST serviceID ISO 24102 specifies the element serviceID: INTEGER(0..127,...). Extension method: 0xxx xxxx: One octet Integer 0 - 127 0xxx xxxx 1xxx xxxx: Two octet Integer 127 - 16.383 0xxx xxxx 1xxx xxxx 1xxx xxxx: Three octet Integer 16.384 - 2.097.151 0xxx xxxx 1xxx xxxx 1xxx xxxx 1xxx xxxx: Four octet Integer 2.097.152 - 268.435.455 LSB is on right hand side, Least significant octet is on right hand side.

  16. FAST serviceID ITS application identifier

  17. ETSI In 2007, ETSI TC ITS was founded by members of ISO TC204 WG16. The purpose was twofold, i.e. to establish a close relation between the base standard development at ISO and the development of abstract test suites. ETSI also started to develop regional standards for ITS, which complement work done at ISO TC204 WG16. Major focus is on ITS facilities for road safety and traffic efficiency applications. An already published standard specifies the Cooperative Awareness Message (CAM). An early draft works on the Service Announcement Message (SAM). Further work is on the Decentralized Environmental Notification Message (DENM). The application classes behind these messages need to be identified by a unique application identifier. The needs of ETSI can be fulfilled with either the DSRCApplicationEntityID, the PSID or the serviceID. Note: The approach at ETSI so far neither refers to DSRCApplicationEntityID, nor to PSID, nor to serviceID. This STF 404, of which the parent body is TC ITS WG2, shall develop a harmonized scheme to be used at ETSI. ITS application identifier

  18. ITS application identifier ETSI - CAM

  19. ITS application identifier ETSI - SAM

  20. CEN TC278 WG16 / ISO TC204 WG18 These two working groups aim on joint development of applications for cooperative ITS. They have an active work item on development of an application identifier for ITS having in mind the They are aware of STF 404 and support an approach in line with the needs of IEEE WAVE and ISO CALM. ITS application identifier

  21. Evaluation DSRCApplicationEntityID is in use in Europe in large scale for Electronic Fee Collection (EFC). CEN DSRC will continue to use this identifier with the given format (presentation in 6 bits). WAVE continued to support the DSRCApplicationEntityID values presented in a new four octet scheme. No problems are known so far, thus this approach is considered to be viable and meaningful, except a single conflict with double usage of a number for two different application groups. STF 404 does not know whether this conflict still exists in reality, or whether this is just a "conflict on paper" visible in the copies of two standards. ISO CALM has improved the approach from IEEE WAVE with respect of efficiency in the radio link - by introducing a variable length presentation of the numbers. This actually reduces the total number range to be presented with four octets. However this is acceptable, as still the maximum number of values is extremely large, and as a further extension to five or more octets is always possible. Recently IEEE, as part of the harmonization of WAVE with FAST, started to prepare a migration of the presentation of PSID from fixed length to variable length, which promotes the approach at ISO. The needs of ETSI are fulfilled by the approach of ISO CALM. ITS application identifier

  22. Conclusion The global ITS application identifier shall be presented in a field of variable length with either: 7 bits 14 bits 21 bits 28 bits, or alternatively a higher integer multiple of 7 bits payload contained in the field. The number presentation needs to be further harmonized. ITS application identifier

  23. ITS application identifier ITS application identifier

  24. IAID next steps • Details of the format, usage and management of itsApplicationID need to be discussed with experts from IEEE, ISO, CEN and ETSI. Topics are: • Who is responsible for assigning values. Maybe dependent on number range: CEN (1 octet), ISO (2 and 3 octets), IEEE (4 octets) - or EC? • Assignment (by standards or) by a registration body. • Is priority of the application to be considered / assigned simultaneously. • How to consider single applications owned by private persons / for public usage, and application groups, • CommunityID (draft TS 102 890-2) implicitly linked to itsApplicationID. No need for an explicit parameter. • Possibility to map a communication profile to a itsApplicationID - maybe dependent on the region. Not needed in the general case, but should be possible for some applications. An extension of this approach would be a list of acceptable communication profiles. • Cost of registration - cost model (private / public / ...). Same cost model for all registration bodies! ITS application identifier

  25. ITS application identifier ITS consultant Ylum Consulting SARL Dr. Maria Grazia Verardi 292, chemin du Valbosquet 06600 Antibes France mg.verardi@ylum.eu http://www.ylum.eu phone: +33 6 3797 1473 fax: +33 4 9333 0543 ESF GmbH Hans-Joachim Fischer Fichtenweg 9 D-89143 Blaubeuren Germany HJFischer@fischer-tech.info http://www.fischer-tech.info phone: +49 7344 175 340 fax: +49 7344 919 123

More Related