VORNORM
`0NORM
`ENV ISO 14906
`
`Ausgabe: 1999-03-01
`
`Normengruppe V
`
`ldent (IDT) mit ENV ISO 14906:1998
`ldent (IDT) mit ISO/TR 14906:1998
`
`ICS 03.220.20;
`35.240.60
`
`Road Transport and Traffic Telematics (RTTT)
`Electronic Fee Collection (EFC)
`Application interface definition for dedicated short range
`communications
`(ISOfTR 14906: 1998)
`
`Die Europaische Vornorm ENV ISO 14906 hat den Status einer Osterreichi(cid:173)
`schen Vornorm.
`
`Die ONORM Vornorm ENV ISO 14906 besteht aus
`•
`diesem nationalen Deckblatt sowie
`•
`der offiziellen englischsprachigen Fassung der ENV ISO 14906:1998.
`
`Fortsetzung
`ONORM ENV ISO 14906 Seite 2 und
`ENV ISO 14906 Seiten 1 bis 69 (nicht im Abo)
`
`Medieninhaber und Hersteller: Osterreichisches Normungsinstitut, A-1021 Wien
`Copyright© ON - 1999. Aile Rechte vorbehalten;
`Nachdruck oder Vervielfaltigung, Aufnahme auf oder in sonstige Medien oder Datentrager
`nur mit Zustimmung des ON gestattet!
`Verkauf von in- und auslandischen Normen und technischen Regelwerken durch:
`ON Osterreichisches Normungsinstitut, HeinestraBe 38, Postfach 130, A-1021 Wien
`Tel.: (+43 1) 213 00-805, Fax: (+43 1) 213 00-818, E-Mail: sales@on-norm.at,
`Internet: http://www.on-norm.at
`
`Fachnormenausschuss220
`Telematik fUr StraBenverkehr
`und -transport
`
`Preisgruppe 37
`
`Kapsch-1006
`
`Page 1 of 72
`
`

`
`Seite 2
`ONORM ENV ISO 14906
`
`Nationales Vorwort
`
`Diese ONORM wurde als Vornorm herausgegeben, weil die europaische Entwicklung auf diesem Fachgebiet noch in
`Fluss ist und weitere praktische Erfahrungen abgewartet werden sollen. Es wird gebeten, Erfahrungen und Vorschlage
`schriftlich dem 6sterreichischen Normungsinstitut mitzuteilen.
`
`Europaische Vornormen sind bereits in das nationale Normenwerk zu Obernehmen, wenn sie in einer der offiziellen
`Sprachfassungen von CEN/CENELEC vorliegen.
`
`Die derzeit nur in englischer Sprache vorliegende ONORM Vornorm ENV ISO 14906 wurde daher bereits jetzt in das
`6sterreichische Normenwerk Obernommen und damit allen Normanwendern verfOgbar gemacht. Diese konnen das er(cid:173)
`wahnte Dokument beim 6sterreichischen Normungsinstitut beziehen bzw. in den Text Einsicht nehmen.
`
`Nach Vorliegen einer deutschsprachigen Fassung wird diese parallel zur englischen Sprachfassung herausgegeben und
`als Bestandteil des (der) einschlagigen Normenabonnements entsprechend verbreitet werden.
`
`Kapsch-1006
`
`Page 2 of 72
`
`

`
`EUROPEANPRESTANDARD
`PRENORMEEUROPEENNE
`EUROPAISCHE VORNORM
`
`ICS 03.220.00; 03.240
`
`ENV ISO 14906
`
`December 1998
`
`Descriptors:
`
`teleprocessing, traffic, road transport, information interchange, messages, interfaces, application layer
`
`English version
`
`Road Transport and Traffic Telematics (RTTT) - Electronic Fee
`Collection (EFC) - Application interface definition for dedicated
`short range communications (ISO/TR 14906:1 998)
`
`This European Prestandard (ENV) was approved by CEN on 9 October 1998 as a prospective standard for provisional application.
`
`The period of validity of this ENV is limited initially to three years. After two years the members of CEN will be requested to submit their
`comments, particularly on the question whether the ENV can be converted into a European Standard.
`
`CEN members are required to announce the existence of this ENV in the same way as for an EN and to make the ENV available promptly
`at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the ENV) until the final
`decision about the possible conversion of the ENV into an EN is reached.
`
`CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,
`Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom.
`
`EUROPEAN COMMriTEE FOR STANDARDIZATION
`CO MITE EUROPEEN DE NORMALISATION
`EUROPAISCHES KOMITEE FUR NORMUNG
`
`Central Secretariat: rue de Stassart, 36 B-1050 Brussels
`
`© 1998 CEN All rights of exploitation in any form and by any means reserved
`worldwide for CEN national Members.
`
`Ref. No. ENV ISO 14906:1998 E
`
`Kapsch-1006
`
`Page 3 of 72
`
`

`
`Page2
`ENV ISO 14906:1998
`
`CONTENTS
`Foreword ...................•.•.....•....................•.•.................•..•••.•....•....•....••.•..•.....•......•....••••.••......•..••.••••••••.•.••••.•.•...•.•......•. 4
`
`Introduction ....................................................................•........•...........•................•.....••.............•...•.•••...•..•........•...•...••. 4
`
`1 Scope .................................................••.........................•.......••..•..••••.••.•.•...............•...•.•...........•..••.•••.....••••....••....••..... 5
`
`2 Normative references .................................................•.•..•••..•.•..•.................•••.•.....•....••.•..••.••........•....•........•........•.... 6
`
`3 Definitions ..•..................•..............................•...•........••.....•.•...........••••..........•..................•......•.......••••••......•..........••... 7
`
`4 Abbreviations ...•••..•..........•••.......•.......•.•.....•..•.•...•...•.•.••....•••.•......•...•••...••...••.•..•......•...••.••••••••.••...••..••.....•....•.••••••.... 9
`
`5 EFC application interface architecture ...•.........•.•.•.••••.•••••••••••••••••.••••....•••••••.•..•.••......••.....•.•.....••.••.....•.•......••..•.• lO
`
`5.1 Relation to the DSRC communication architecture ............................................................................................... 1 0
`5.2 Usage of DSRC application layer by the EFC application interface ...................................................................... 11
`5.3 Addressing of EFC attributes ................................................................................................................................. 11
`5.3.1 Basic mechanism ............................................................................................................................................ 11
`5.3.2 Role ofthe EID ............................................................................................................................................... l2
`5.3.3 Multiple Instances of Attributes ...................................................................................................................... l2
`5.4 Addressing of components ..................................................................................................................................... l3
`
`6 EFC Transaction Model ................................................................••••.•.......•...............••••...•.....•.••.••......•.••..•..•••••...• 14
`
`6.1 Initialisation Phase ................................................................................................................................................. 14
`6.1.1 Overview ......................................................................................................................................................... l4
`6.1.2 EFC application-specific contents ofthe BST ................................................................................................ J5
`6.1.3 EFC application-specific contents of the VST ................................................................................................ l5
`6.2 Transaction phase .................................................................................................................................................. 16
`
`7 EFC Functions .............................................•...............•..•.•......•.•..........•.•...............•.....••••.........•••..••....•.••••••....•••... 18
`
`7.1 Overview and general concepts ............................................................................................................................. 18
`7.1.1 EFC functions and service primitives ............................................................................................................. 18
`7.1.2 Overview of EFCfunctions ............................................................................................................................. J9
`7.1.3 Handling of multiple instances ....................................................................................................................... 20
`7.1.4 Security .......................................................................................................................................................... 21
`7.2 EFC functions ........................................................................................................................................................ 21
`7.2.1 GET_STAMPED ............................................................................................................................................. 22
`7.2.2 SET_STAMPED .............................................................................................................................................. 23
`7.2.3 GET_SECURE ................................................................................................................................................ 24
`7.2.4 SET_SECURE ................................................................................................................................................. 25
`7.2.5 GET _INSTANCE ............................................................................................................................................ 26
`7.2.6 SET_INSTANCE ............................................................................................................................................. 27
`7.2.7 GET_NONCE .................................................................................................................................................. 28
`7.2.8 SET_NONCE .................................................................................................................................................. 29
`7.2.9 TRANSFER_ CHANNEL ................................................................................................................................. 30
`7.2.10 COPY ............................................................................................................................................................ 31
`7.2.11 SET_MMI ...................................................................................................................................................... 32
`7.2.12 SUBTRACT ................................................................................................................................................... 33
`7.2.13 ADD .............................................................................................................................................................. 34
`7.2.14 DEBIT ........................................................................................................................................................... 35
`7.2.15 CREDIT ........................................................................................................................................................ 36
`7.2.16 ECHO ........................................................................................................................................................... 37
`
`8 EFC Attributes ........................................................................................................................................................ 38
`
`8.1 Data group CONTRACT ....................................................................................................................................... 39
`8.2 Data group RECEIPT ............................................................................................................................................ 40
`8.3 Data group VEHICLE ........................................................................................................................................... 42
`8.4 Data group EQUIPMENT ..................................................................................................................................... 43
`
`Kapsch-1006
`
`Page 4 of 72
`
`

`
`Page 3
`ENV ISO 14906:1998
`
`8.5 Data group DRIVER .............................................................................................................................................. 43
`8.6 Data group PAYMENT ......................................................................................................................................... 44
`
`ANNEX A (normative) EFC data type specitications ....•.•....•••••.•...••.•••.•.••...•..............................•.......•................•. 45
`
`Annex B (informative) An excerpt from DSRC application layer .......................................................•.............•... 52
`
`B.l Format of service primitives .................................................................................................................................. 52
`B.2 Generic DSRC application layer functions ............................................................................................................ 53
`B.2.1 GET ................................................................................................................................................................ 53
`B.2.2 SET ................................................................................................................................................................. 54
`B.3 Container.ASN.l type definition ........................................................................................................................... 55
`
`Annex C (informative) Examples of EFC transactions using the EFC application interface ....••..........•..••....•.•. 56
`
`C.l Example of an EFC transaction - Example ! ......................................................................................................... 56
`C.2 Example of an EFC transaction - Example 2 ......................................................................................................... 57
`C.3 Example of an EFC transaction- Example 3 ......................................................................................................... 58
`C.4 Example of an EFC transaction- Example 4 ......................................................................................................... 59
`C.5 Example of an EFC transaction- Example 5 ......................................................................................................... 62
`
`ANNEX D (informative) Functional requirements ...•.•...•••.....••....•.•...•......•........•........••..........•..•..........•.••.....•••••... 66
`
`Kapsch-1006
`
`Page 5 of 72
`
`

`
`Page4
`ENV ISO 14906:1998
`
`Foreword
`
`This European Prestandard has been prepared by Technical Committee CEN/TC 278 "Road transport
`and traffic telematics", the secretariat of which is held by NNI, in collaboration with Technical Committee
`ISO/TC 204 'Transport information and control systems".
`
`According to the CEN/CENELEC Internal Regulations, the national standards organizations of the
`following countries are bound to announce this European Prestandard: Austria, Belgium, Czech Republic,
`Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway,
`Portugal, Spain, Sweden, Switzerland and the United Kingdom.
`
`Introduction
`
`This European Pre-Standard specifies an application interface for Electronic Fee Collection (EFC)
`systems, which are based on the Dedicated Short-Range Communication (DSRC), enabling
`interoperability between open EFC systems (i.e. between different EFC system operators) on an EFC(cid:173)
`DSRC application interface level.
`
`The European Pre-Standard provides specifications for the EFC transaction model, EFC data elements
`(referred to as attributes) and functions, from which an EFC transaction can be built. The EFC transaction
`model provides a mechanism that allows handling of different versions of EFC transactions and
`associated contracts. A certain EFC transaction supports a certain set of EFC attributes and EFC
`functions as defined in this European Pre-Standard. It is not envisaged that the complete set of EFC
`attributes and functions is present in each piece of EFC equipment, be OBE or RSE.
`
`This European Pre-Standard provides the basis for agreements between operators, which are needed to
`achieve interoperability. Based on the tools specified in this European Pre-Standard, interoperability can
`be reached by operators recognising each others EFC transactions (including the exchange of security
`algorithms and keys) and implementing the EFC transactions in each others RSE, or they may reach an
`agreement to define a new transaction (and contract) that is common to both. Considerations also have to
`be made by each operator that the RSE has sufficient resources to implement such additional EFC
`transactions.
`
`In order to achieve interoperability, operators have to agree on issues like:
`• which optional features are actually being implemented and used;
`• security policy (including encryption algorithms and key management, if applicable);
`• operational issues, such as how many receipts may be stored for privacy reasons, how many receipts
`are necessary for operational reasons (e.g. as entry tickets or as proof of payment);
`the agreements needed between operators in order to regulate the handling of different EFC
`transactions.
`
`•
`
`This European Pre-Standard has the following structure. In the first four clauses the scope, normative
`references, definitions of terms and abbreviations are accounted for. Next, in clause 5, the EFC
`Application interface architecture is described in terms of its relation to the DSRC communication
`architecture, including the addressing of data attributes and of components. In the following clause 6, the
`EFC transaction model is introduced, defining the common steps of each EFC transaction, in particular
`the initialisation phase. Clauses 7 and 8 are dedicated to the detailed specification of the EFC application
`functions and of the EFC data attributes, respectively. Four annexes provide
`-
`the normative ASN.1 specifications of the used data types (EFC action parameters and
`attributes);
`an informative excerpt from DSRC application layer (ENV 12834), and its service
`primitives, parameters and functions;
`informative examples of EFC transactions using the specified EFC attributes and
`functions;
`an informative listing of functional requirements, which can be satisfied by using the
`tools provided by this European Pre-standard.
`
`-
`
`-
`
`-
`
`Kapsch-1006
`
`Page 6 of 72
`
`

`
`Page 5
`ENV ISO 14906:1998
`
`1
`
`Scope
`
`This European Pre-Standard specifies the application interface in the context of Electronic Fee Collection
`(EFC) systems using the Dedicated Short-Range Communications (DSRC).
`
`The EFC application interface is the EFC application process interface to the DSRC Application Layer, as
`can be seen in figure 1 below. The scope of this European Pre-Standard comprises specifications of:
`
`• EFC attributes (i.e. EFC application information);
`
`•
`
`the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI);
`
`• EFC application functions, i.e. further qualification of actions by definitions of the concerned services,
`assignment of associated Action Type values and content and meaning of action parameters;
`
`•
`
`•
`
`the EFC transaction model, which defines the common elements and steps of any EFC transaction;
`
`the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface
`level.
`
`RSE
`
`OBE
`
`·-· ---------------------· ---------------
`
`Application Process
`
`ADU
`
`Attributes (e.g. Payment Means,
`VehicleDimensions, .. )
`
`Scope of this 1
`European
`Pre-standard
`
`1
`
`1
`
`Application Process
`
`Attributes (e.g. PaymentsMeans,
`VehicleDimensions, .. )
`ActionType (e.g. debit, set_MMI,
`transfer_channel, etc.)
`
`I
`
`I
`
`I
`
`I
`
`1
`
`ACTION.cf
`SET.cf
`GET.cf
`
`i I Notify Application
`
`~ Beacon
`
`V
`
`Ready Application
`(De-)register App
`Beacon
`
`ACTION.rq
`SET.rq
`GET.rq
`,...--- T-ASDU
`
`DSRC
`Application
`Layer
`
`ActionType (e.g. debit, set_MMI,
`transfer _channel, etc.)
`
`ACTION.rs
`SET.rs
`GET.rs
`
`ACTION.ind
`SET ind
`GET.ind
`
`/
`
`~
`
`(De)-
`RegAppVehicle
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`T-APDU
`
`DSRC
`Application
`
`T-KE
`
`I J Notify App Vehicle
`T-ASDU l I I-KE
`l Layer
`I
`KE
`
`I I-KE I
`j
`1
`~~ ___ T-K_E __ ~I~----~--~ I
`KE
`
`Figure 1: The EFC application interface
`
`This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (ISO/IEC
`7498-1), and it is as such not concerned with the implementation choices to be realised at either side of
`the interface.
`
`This European Pre-Standard provides security-specific functionality as place holders (data and functions)
`to enable the implementation of secure EFC transactions. Yet the specification of the security policy
`(including specific security algorithms and key management) remains at the discretion and under the
`control of the EFC operator, and hence is outside the scope of this European Pre-Standard.
`
`Kapsch-1006
`
`Page 7 of 72
`
`

`
`Page6
`ENV ISO 14906:1998
`
`2
`
`Normative references
`
`This European Pre-Standard incorporates by dated or undated reference, provisions from other
`publications.
`
`These normative references are cited at the appropriate places in the text and the publications are
`listed hereafter.
`
`For dated references, subsequent amendments to or revisions of any of these publications apply to
`this European Pre-Standard only when incorporated in it by amendment or revision. For undated
`references the latest edition of the publication referred to applies.
`
`ISO 612:
`ISO 1176:
`ISO 3166:
`ISO 3779:
`
`ISO 3780:
`ISO 4217:
`ISO 7498-1:
`
`ISO/IEC 8824-1:
`
`ISO/IEC 8825-2:
`
`ENV 1545-1
`
`ENV 1545-2
`
`prENV ISO 14816:
`
`ENV 12834:
`
`Vehicle Measurement Definition
`Vehicle Weight Definitions
`Codes for the representation of names of countries
`Road Vehicles- Vehicle Identification Number (VIN)
`Content and Structure
`Road Vehicles World manufacturer identification code (WMI)
`Codes for the representation of currencies and funds
`Information Processing Systems - Open Systems
`Interconnection - Basic Reference model
`Information processing systems- Open Systems
`Interconnection- Specification of abstract syntax notation one
`(ASN.1)
`Information processing systems- Open Systems
`Interconnection - ASN.1 encoding rules: Specification of
`Packed encoding rules
`Identification card systems- Surface transport applications(cid:173)
`Part 1 : General data elements
`Identification card systems - Surface transport applications -
`Part 2 : Transport payment related data elements
`Road Traffic and Transport Telematics (RTTT), Automatic
`Vehicle and Equipment Identification - Numbering and Data
`Structures (ISO/DTR 14816: 1998)
`Road Traffic and Transport Telematics {RTTT), Dedicated
`Short-Range Communication {DSRC) -Application Layer
`
`1983
`
`1983
`
`1994
`
`1995
`
`1996
`
`1998
`
`1998
`
`1998
`
`1997
`
`Kapsch-1006
`
`Page 8 of 72
`
`

`
`Page 7
`ENV ISO 14906:1998
`
`3
`
`Definitions
`
`For the purposes of this European Pre-Standard, the following definitions apply:
`
`3.1
`
`access credentials
`
`Data that is transferred to On-Board Equipment, in order to establish
`the claimed identity of an RSE application process entity.
`
`3.2
`
`action
`
`3.3
`
`attribute
`
`3.4
`
`authenticator
`
`NOTE· The access credentials carries information needed to fulfil
`access conditions in order to perform the operation on the addressed
`element in the OBE The access credentials can carry passwords as
`well as cryptographic based information such as authenticators.
`
`that an application process resident at the Roadside
`Function
`Equipment can invoke in order to make the On-Board Equipment
`execute a specific operation during the Transaction.
`
`Application information formed by one or by a sequence of data
`elements, and
`is managed by different actions used
`for
`implementation of a transaction.
`
`Data appended to, or a cryptographic transformation (see
`cryptography) of, a data unit that allows a recipient of the data unit to
`prove the source and/or the integrity of the data unit and protect
`against forgery.
`
`3.5
`
`channel
`
`An information transfer path [ISO/IEC 7498-2].
`
`3.6
`
`component
`
`Logical and physical entity composing an On-Board Equipment,
`supporting a specific functionality.
`
`3. 7
`
`contract
`
`Expression of an agreement between two or more parties concerning
`the use of the road infrastructure.
`
`3.8
`
`cryptography
`
`The discipline which embodies principles, means, and methods for the
`transformation of data in order to hide its information content, prevent
`its undetected modification or/and prevent its unauthorised use
`[ISO/IEC 7498-2].
`
`3.9
`
`data group
`
`A collection of closely related EFC data attributes which together
`describe a distinct part of an Electronic Fee Collection transaction.
`
`3.1 0 data integrity
`
`The property that data has not been altered or destroyed in an
`unauthorised manner [ISO 7 498-2].
`
`3.11 element
`
`In the context of DSRC, a directory containing application information
`in form of Attnbutes.
`
`3.12 on-board equipment Equipment located within the vehicle and supporting the information
`exchange with the Road Side Equipment It is composed of the On(cid:173)
`Board Unit and other sub-units whose presence have to be considered
`optional for the execution of a Transaction.
`
`3.13 on-board unit
`
`Minimum component of an On-Board Equipment, whose functionality
`always includes at least the support of the DSRC interface.
`
`3.14
`
`roadside equipment Equipment located at a fixed position along the road transport network,
`for the purpose of communication and data exchanges with the On(cid:173)
`Board Equipment of passing vehicles.
`
`Kapsch-1006
`
`Page 9 of 72
`
`

`
`PageS
`ENV ISO 14906:1998
`
`3.15 service (EFC)
`
`Road transport related facility provided by a Service Provider. Normally
`a type of infrastructure, the use of which is offered to the User for
`which the User may be requested to pay.
`
`3.16 service primitive
`(communication)
`
`Elementary communication service provided by the Application layer
`protocol to the application processes.
`
`NOTE· The invocation of a service primitive by an application process
`implicitly calls upon and uses services offered by the lower protocol
`layers.
`
`3.17 service provider
`(EFC)
`
`The operator that accepts the user•s payment means and in return
`provides a road-use service to the user.
`
`3.18 session
`
`3.19
`
`transaction
`
`The complete exchange of information and interaction occurring at a
`specific Electronic Fee Collection station between the Roadside
`Equipment and the user/vehicle.
`
`The whole of the exchange of information between the Roadside
`Equipment and
`the On-Board Equipment necessary
`for
`the
`completion of an Electronic Fee Collection operation over the DSRC.
`
`NOTE· A transaction may require more than one session in order to
`be achieved, e.g. an entry session and an exit session.
`
`3.20
`
`transaction model
`
`Functional model describing the general structure of Electronic Fee
`Collection transactions.
`
`3.21 user
`
`The entity that uses transport services provided by the Service
`Provider according to the terms of a Contract
`
`Kapsch-1006
`
`Page 10 of 72
`
`

`
`4
`
`Abbreviations
`
`For the purpose of this European Pre-Standard, the following abbreviations apply throughout the
`document unless otherwise specified:
`
`Page 9
`ENV ISO 14906:1998
`
`ADU
`APDU
`AP
`ASN.1
`BST
`DSRC
`EID
`EFC
`GPS
`ICC
`I-KE
`liD
`LID
`MMI
`OBE
`OBU
`PDU
`PER
`RSE
`RTTT
`SAM
`T-APDU
`T-ASDU
`T-KE
`VST
`
`Application Data Unit
`Application Protocol Data Unit
`Application Process
`Abstract Syntax Notation One
`Beacon Service Table (DSRC Application Layer)
`Dedicated Short-Range Communications
`Element ID
`Electronic Fee Collection
`Global Positioning System
`Integrated Circuit{s) Card
`Initialisation Kernel Element {DSRC Application Layer)
`Invoker ID
`Link ID
`Man-Machine Interface
`On-Board Equipment
`On-Board Unit
`Protocol Data Unit
`Packed Encoding Rules
`Road-Side Equipment
`Road Traffic and Transport Telematics
`Secure Application Module
`Transport-Application Protocol Data Unit {DSRC Application Layer)
`Transport-Application Service Data Unit (DSRC Application Layer)
`Transport Kernel Element (DSRC Application Layer)
`Vehicle Service Table {DSRC Application Layer)
`
`Kapsch-1006
`
`Page 11 of 72
`
`

`
`Page 10
`ENV ISO 14906:1998
`
`5
`
`EFC application interface architecture
`
`Relation to the DSRC communication architecture
`5.1
`The DSRC services are provided to an application process by means of the DSRC Application Layer
`service primitives, which are abstract implementation interactions between a communication service user
`and provider. The services are offered by the DSRC communication entities by means of its DSRC
`Application Layer (ENV 12834).
`
`RSE
`
`AP
`
`ADU
`
`GET.ra
`SET.ra
`
`(EVENT-AT rq}
`
`,
`
`Notify Applic ation
`Beacon
`~ Ready Applic
`ation
`App Beacon
`(De-)register
`
`OBE
`
`AP
`
`J
`1
`
`GET.rs
`SET.rs
`ACTION.rs
`(EVENT-RT.rs}
`
`GET.ind
`SET.ind
`ACTION.ind
`(EVENT-AT
`
`I H No
`
`tify Application
`hicle
`Ve
`
`j (De-) RegAppVehicle
`
`i~d
`
`I
`T-ASDU l
`
`GET.cf
`SET.cf
`ACTION.cf
`(EVENT·RT.cf)
`
`, ...............
`~ 8-KE
`":+""":"
`n.a. for EFC
`,
`
`DSRC
`-L71.
`
`ACTION.ra .-
`I I-KE I
`l
`
`T-KE
`
`I
`I
`KE
`
`, ............ ,.
`.
`.
`: 8-KE
`"':""".6:'
`n.a. for EFC
`
`T-APDU
`
`;,
`
`.I
`
`I
`
`..
`T-KE
`
`I I-KE I
`l
`I D
`SAC -L7
`I
`
`KE
`
`I
`LPDU
`LLC sublayer ~
`-L2 ·······································
`DSRC
`I
`MAC sublayer
`
`~
`
`I
`LLC sublayer
`-----+
`....................................... DSR C-L2
`I
`MAC sublayer
`~
`
`I
`
`DS~C-L 1 Physical layer
`
`PHY
`PDU
`
`..
`I
`Physical layer DSR C-L1
`I
`
`Additional abbreviations used only in this figure (for all other abbreviations see clause 4.}
`B-KE
`Broadcast-Kernel Element
`LLC
`Logical Link Control
`LPDU
`Link Protocol Data Unit
`MAC
`Medium Access Control
`PHY-PDU
`Physical Link Protocol Data Unit
`reqlind/rs/cf
`request/indication/response/confirm
`EVENT-AT
`EVENT-REPORT
`not applicable
`n.a.
`Figure 2: The EFC application process on top of the DSRC communication stack
`
`The Transfer Kernel Element (T-KE) of DSRC Application Layer offers the following services to application
`processes (see also figure 2 above):
`
`• GET: The invocation of a GET service request results in retrieval (i.e. a reading) of application
`information (i.e. Attributes) from the peer service user (i.e. the OBE application process), a reply is
`always expected.
`
`• SET: The invocation of a SET service request results in modification (i.e. writing) of application
`information (i.e. Attributes) of the peer service user (i.e. the OBE application process). This service
`may be requested in confirmed or non-confirmed mode, a reply is only expected in the former case.
`
`• ACTION: The invocation of an ACTION service request results in a performance of an action by the
`peer service user (i.e. the OBE application process). An action is further qualified (see clause 7.4) by
`
`Kapsch-1006
`
`Page 12 of 72
`
`

`
`Page 11
`ENV ISO 14906:1998
`
`the value of the Action Type. This service may be requested in confirmed or non-confirmed mode, a
`reply is only expected in the former case.
`
`• EVENT·REPORT: The invocation of an EVENT-REPORT service request forwards a notification of an
`event to the peer service user.
`
`•
`
`INITIALISATION: The invocation of an initialisation service request by RSE results in an attempt to
`initialise communication between a RSE and each OBE that has not yet established communication
`with the concerned RSE. The Initialisation service is only used by the I-KE as defined in ENV 12834,
`which in its tum is configured by the application(s) wishing to execute applications over the DSRC link.
`
`Usage of DSRC application layer by the EFC application interface
`5.2
`EFC uses the following services offered by DSRC Application Layer (as defined in ENV 12834):
`
`• The INITIALISATION services:
`(at RSE)
`•
`(De-)Register Application RSE
`• Notify Application Beacon
`(at RSE)
`• Ready Application
`(at RSE)
`•
`(at OBE)
`(De-)Register Application OBE
`(at OBE)
`• Notify Application Vehicle
`are used to realise the EFC-specific initialisation mechanism (see clause 6)
`
`• The GET service is used to retrieve EFC attributes (see annex 8.2.1. For attribute specifications
`see clause 8)
`
`• The SET-service is used to set EFC attributes (see annex 8.2.2)
`
`• The ACTION-se