CEN/TC278 WG16 DT2 PT1601 Liaison report to ETSI TC ITS April 2013 PT1601 liaison report to ETSI TC ITS1

PT1601 April 2013PT1601 liaison report to ETSI TC ITS2 PT1601 is a project team at CEN TC278 WG16 funded by the European Commission under mandate M/453. See Contact us:

PT1601 standards April 2013PT1601 liaison report to ETSI TC ITS3 PT1601 is drafting two CEN/ISO Technical Specifications: TS "Co-operative systems — Classification and management of ITS applications in a global context“ TS "Co-operative systems - ITS application requirements for selection of communication profiles" which will be upgraded to EN/ISO standards.

PT1601 work plan April 2013PT1601 liaison report to ETSI TC ITS4 July 2012:Kick-off meeting December 2012:First draft documents distributed. Interim report to EC January 2013:ETSI TC ITS joint WG meeting February 2013:Compilation of first comments. Milestone 1 versions of deliverables for CEN TC commenting / ISO CD comment only ballot April 2013:ETSI TC ITS joint WG meeting May 2013:Compilation of comments July 2013:Final stable drafts for approval.

ITS-S architecture (ISO 21217) April 2013PT1601 liaison report to ETSI TC ITS5 The ITS-S is defined as a B ounded S ecured M anaged D omain. There are many other stations used in ITS already today, which are not following the principles of BSMD. Nevertheless communications between ITS-SUs = BSME and other ITS station units has to be possible.

TS Scope April 2013PT1601 liaison report to ETSI TC ITS6 This Technical Specification specifies requirements and objectives for communications presented by ITS-S application process to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit (ITS-SU) specified in ISO 21217, specifies related optional procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level.

Simplified architecture (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS7 All entities (applications) using communications services from "Simplified communications" are referred to as "ITS-S application processes": (ISO 21217) ITS-S applications (ISO 21217) ITS-S facility applications (ISO 21217) CAM generator (ETSI TC IST WG1) ITS-S management applications (ISO 21217) IICP (ISO ) FSAP (ISO ) Remote management (ISO ) ITS-S security applications (ISO 21217) Other applications

Classification April 2013PT1601 liaison report to ETSI TC ITS8 ITS-S application processes: certified for BSMD and identified by an ITS-AID ITS-S application, ITS-S facilities application, ITS-S management application, ITS-S security application authorized (=mandatory or conditional) permitted (=optional ) not certified for BSMD and without ITS-AID Other application A single ITS application certified for BSMD and identified by a value of ITS-AID might result in N ITS-S application processes of which each may be implemented by M software developers. Each implementation of each such ITS-S application process refers to the same ITS-AID, but gets its own certificate!

Comm. profile selection (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS9 ITS-S application processes reside in the ITS-S applications entity, the ITS-S management entity, the IST-S facilities layer and the ITS-S management entity.

Other applications April 2013PT1601 liaison report to ETSI TC ITS10 A gateway functionality allows other applications to have restricted access to the ITS-S services of an ITS-SU.

Comm. requirements (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS11

Comm. requirements (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS12

Comm. requirements (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS13

Comm. requirements (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS14

Comm. requirements (TS 17423) April 2013PT1601 liaison report to ETSI TC ITS15 The following procedures related to data elements identified in this Technical Specification for the purpose of mapping applications to ITS-S communication profiles are identified: Presentation of requirements and objectives by ITS-S application processes. Monitoring of capabilities of communications. Monitoring of change in regulations and policies. Selection of ITS-S communication profiles. Provision of additional rules and policies by user of ITS- SUs. ITS-S communication profile assignment for applications which are not certified to be installed in an ITS-SU.

TS Scope April 2013PT1601 liaison report to ETSI TC ITS16 This Technical Specification illustrates and specifies "Global Classification and Management of ITS Applications" (GCMA). It describes and specifies globally unique addresses and identifiers (ITS- S object identifiers) which are both internal and external to ITS stations and are used for ITS station management, describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes, describes how ITS-S object identifiers are used in the ITS communication protocol stack, introduces an organizational framework for registration and management of ITS-S objects, defines and specifies management procedures, focuses on international applicability, is based on the ITS communication architecture described in ISO

Entities and their roles (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS17 ITS-S object Entity used in ITS related to ITS-S management that may require a globally unique identifier. Examples are ITS application objects, ITS message sets, ITS-S communication protocols, ITS-S units, ITS-S communication units. ITS-S object owner Entity which is responsible for the specification (design), maintenance and registration of ITS-S objects, often a standards development organization or an industry special interest group such as the "Society of Automotive Engineers" (SAE). Examples are ITS application object owners, ITS message sets owners, ITS-S communication protocol owners.

Entities and their roles (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS18 ITS application object Entity that provides an ITS service to the user as specified in ISO Examples are ITS applications and ITS application classes. ITS message set Set of ITS messages designed for an ITS-related purpose as specified in ISO ITS-S communication protocol Protocol used in a communication protocol stack of an ITS-S

Entities and their roles (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS19 ITS-S unit (ITS-SU) Physical instantiation of an ITS station specified in ISO An ITS-SU may consist of one single ITS-SCU, or several ITS-SCUs interconnected via an ITS station internal network. An ITS-SU is also referred to as "Bounded Secured Managed Entity" as specified in ISO ITS-S communication unit (ITS-SCU) Physical instantiation of a part of an ITS-SU as specified in ISO

Entities and their roles (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS20 ITS equipment manufacturer Manufacturer of ITS-SUs and ITS-SCUs. ITS-S application process developer Developer (manufacturer) of ITS-S application processes for usage in ITS- SUs.

Identifiers and addresses (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS21 ITS-AID An ITS application identifier is used to uniquely identify an ITS application or an ITS application class. It is used to advertise services, and for secure installation and real-time operation of ITS-S application processes in an ITS-SU. All ITS-S applications shall have an ITS-AID assigned to them prior to installation in an ITS-SU. ITS-AOOID An ITS application object owner identifier is used to uniquely identify an owner of specifications of ITS application objects. ITS-EMID An ITS equipment manufacturer identifier is used to uniquely identify a manufacturer of ITS equipment.

Identifiers and addresses (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS22 ITS-FlowTypeID An ITS-FlowTypeID is used to uniquely identify an ITS flow type. It is used in the communication profile selection process specified in CEN/ISO TS An ITS flow type is a set of communication requirements and objectives specified in CEN/ISO TS and used by the ITS-S management to select an optimum ITS-S communication profile. An ITS flow type may be identified by a globally unique well-known ITS flow type identifier (ITS- FlowTypeID). ITS-LCHID An ITS logical channel identifier is used to uniquely identify an ITS logical channel in the ITS-S communication profile selection process specified in CEN/ISO TS

Identifiers and addresses (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS23 ITS-MsgSetID An ITS message set identifier is used to uniquely identify an ITS message set. ITS-S applications may construct PDUs using messages from any registered ITS message set, and may also consume such messages through publish/subscribe mechanisms in ITS-SUs. ITS-MSOID An ITS message set owner identifier is used to uniquely identify an owner of specifications of ITS message sets.

Identifiers and addresses (TS 17419) April 2013PT1601 liaison report to ETSI TC ITS24 ITS-PN An ITS port number is used in an ITS-SCU to uniquely identify for a given transport protocol, e.g. FNTP, an entity or protocol in the ITS-S facilities layer. Globally unique, registered well-known port numbers and local dynamically assigned port numbers are used. ITS-PRID An ITS policy region identifier is used to uniquely identify an ITS policy region (ITS-PR) in the ITS-S communication profile selection process specified in CEN/ISO TS Different types of policy regions may be distinguished.

ITS-AID registry (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS25 ITS-AID: ITS application ID  registry ITS-AOOID: ITS Application Object Owner ID (designer)  registry

ITS-MsgSet-ID registry (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS26 ITS-MsgSet-ID: ITS message set ID  registry ITS-MSOID: ITS Message Set Owner ID (designer)  registry

ITS-SCU registry (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS27 ITS-EMID: ITS equipment manufacturer ID  registry ITS-SCUID: Serial number of ITS-SCU  registry

ITS-S application process (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS28 ITS-APDID: ITS application process developer ID  registry

ITS-SCU credentials (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS29

Communications (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS30

ITS-S application process provisioner (TS 17419) functional description April 2013PT1601 liaison report to ETSI TC ITS31

ESF GmbH Hans-Joachim Fischer Fichtenweg 9 D Blaubeuren Germany phone: fax: LECIT Consulting SrL Fausto Caneschi Via Santa Maria Pisa Italy phone: SRA, Inc. Richard Roy 3351 Shady Spring Ln Mountain View, CA USA phone: Members of PT1601 April 2013PT1601 liaison report to ETSI TC ITS32