SIST EN 12834:2004

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Cestna transportna in prometna telematika (RTTT) – Posebna komunikacija kratkega dosega (DSRC) –
Aplikacijska plast DSRCStraßenverkehrstelematik - Nahbereichskommunikation Fahrzeug-Bake (DSRC) - AnwendungsschichtTélématique de la circulation et du transport routier - Communication a courte portée - Couche applicativeRoad transport and traffic telematics - Dedicated Short Range Communication (DSRC) - DSRC application layer35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and trade35.100.70Uporabniški slojApplication layerICS:Ta slovenski standard je istoveten z:EN 12834:2003SIST EN 12834:2004en01-maj-2004SIST EN 12834:2004SLOVENSKI
STANDARDSIST ENV 12834:20031DGRPHãþD

EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 12834November 2003ICS 35.100.70; 35.240.60English versionRoad transport and traffic telematics - Dedicated Short RangeCommunication (DSRC) - DSRC application layerTélématique de la circulation et du transport routier -Communication à courte portée - Couche applicativeStraßenverkehrstelematik - NahbereichskommunikationFahrzeug-Bake (DSRC) - AnwendungsschichtThis European Standard was approved by CEN on 4 December 2002.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the Management Centre has the same status as the officialversions.CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and UnitedKingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMITÉ EUROPÉEN DE NORMALISATIONEUROPÄISCHES KOMITEE FÜR NORMUNGManagement Centre: rue de Stassart, 36
B-1050 Brussels© 2003 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 12834:2003 ESIST EN 12834:2004

(normative)
Data structures.36A.1Use of modules.36A.2ASN.1-modules.36Annex B
(normative)
Naming and registration.41B.1General.41B.2Items for registration.41B.3Items defined by application standards.41Annex C
(informative)
Example.42Annex D
(informative)
A-deviations.44SIST EN 12834:2004

rules: Specification of Packed EncodingRules (PER).EN ISO/IEC 7498-1, Information technology - Open Systems Interconnection - Basic Reference Model: TheBasic Model (ISO/IEC 7498-1).EN 12795, Road Transport and Traffic Telematics (RTTT) - Dedicated Short Range Communication (DSRC) -DSRC Data Link Layer: Medium Access and Logical Link Control.prEN 13372, Road Transport and Traffic Telematics (RTTT) - Dedicated Short-Range Communication (DSRC)- DSRC Profiles for RTTT Applications.ENV ISO 14906, Road Transport and Traffic Telematics (RTTT) - Electronic Fee Collection (EFC) -Application interface definition for dedicated short range communications (ISO/TR 14906:1998).ENV ISO 14816, Road Traffic and Transport Telematics - Automatic vehicle and equipment identification -Numbering and data structures (ISO/TR 14816:2000).3 Terms and definitionsFor the purpose of this European Standard, the following terms and definitions apply.3.1applicationuser of the services offered by the DSRC communication stack3.2attributetakes a value, which may have a structure, consisting of a set or sequence of data elementsNOTEThe value of an attribute can be observed or modified by sending a request to GET (read) or SET (write) the value.3.3attribute identifierunambiguously distinguishes an attribute from all other attributes within the same element3.4Beacon service tabledata structure transmitted by the RSU indicating available services3.5broadcast pooldata structure broadcast from the RSU to the OBUsSIST EN 12834:2004

The T-Kernel provides thebasic transportation facilities that can be used by the I-Kernel, by the B-Kernel, and by the applications.Figure 2 — Context and structure of the application layer coreSIST EN 12834:2004

IID of related indication if present, else EID of related indication.optionalThe use of the optional fields is detailed by the underlying ASN.1 standards.=Same as in corresponding request / indicationNot applicableTable 2 — Format of the GET service primitivesParameter namerequest / indicationresponse / confirmASN.1 typeInvoker Identifier (IID)optional=Dsrc-EIDLink Identifier (LID)mandatory=BIT STRINGChainingmandatory=BooleanElement Identifier (EID)mandatoryiid / eidDsrc-EIDAccessCredentialsoptionalOCTET STRINGAttribute Id List (AttrIdList)optionalAttributeIdListFlowControlmandatorymandatoryINTEGERAttribute List (AttrList)optionalAttributeListReturn Code (Ret)optionalReturnStatusTable 3 — Format of the SET service primitivesParameter namerequest / indicationresponse / confirmASN.1 typeInvoker Identifier (IID)optional=Dsrc-EIDLink Identifier (LID)mandatory=BIT STRINGChainingmandatory=BooleanElement Identifier (EID)mandatoryiid / eidDsrc-EIDAccessCredentialsoptionalOCTET STRINGAttribute List (AttrList)mandatoryAttributeListModemandatoryBooleanFlowControlmandatorymandatoryINTEGERReturn Code (Ret)optionalReturnStatusSIST EN 12834:2004

If true, then there shall be a service.response to a service.indication(confirmed mode);— ActionType shall identify an operation of the element which receives an ACTION.indication and which shall beinvoked;— ActionParameter shall be the information needed for the invocation of an operation identified in anACTION.indication;— ResponseParameter may be information resulting from the execution of the operation invoked byACTION.indication;— EventType shall identify the message which shall be delivered to an element which receives an EVENT-REPORT.indication;— EventParameter shall be the additional information needed for the message sent via an EVENT-REPORT.request and EVENT-REPORT.indication, respectively;— Initialisation Parameter shall be the information needed for the initialisation of the communication (i.e. the BSTon the downlink and VST on the uplink) sent via an initialisation service.6.3 BehaviourThe transfer protocol shall consist of the following steps:a) translating SDU to PDU;b) encoding of PDU;c) fragmentation;d) octet alignment;e) multiplexing, concatenation, and access to LLC;f) demultiplexing;g) defragmentation;h) decoding of PDU, deconcatenation and removal of inserted bits;i) translating PDU to SDU and distribution to addressee.NOTE 1It is outside the scope of this European Standard how the above steps are implemented as long as an instantiation ofthe T-Kernel behaves according to the requirements below.NOTE 2The arrows shown in Figures 6 to 17 are indicating the conversion process.SIST EN 12834:2004

If no fragmentation isperformed then the fragment shall be given the fragment counter value 0.6.3.3.6 Two octet fragmentation headerA two octets fragmentation header shall be used for fragments between 4 and 511, bit 0 of the first octet shall beset to 02. Bits 2 and 1 of the first octet and bits 7 to 1 of the second octet shall be interpreted as an unsignedinteger, where the highest significant bit is bit 2 of the first octet and the least significant bit is bit 1 of the secondoctet. Bit 0 of the second octet shall be set to 12. Fragment numbers shall be assigned to the fragment as specifiedin 6.3.3.5.6.3.3.7 Three octet fragmentation headerA three octets fragmentation header shall be used for fragments between 512 and 65535, bit 0 of the first octetshall be set to 02. Bits 2 and 1 of the first octet, bits 7 to 1 of the second octet and bits 7 to 1 of the third octet areinterpreted as unsigned integer, where the highest significant bit is bit 2 of the first octet and the least significant bitis bit 1 of the third octet. Bit 0 of the second octet shall be set to 02 and bit 0 of the third octet shall be set to 12.Fragment numbers shall be assigned to the fragment as specified in 6.3.3.5.Figure 9 — Fragmentation6.3.4 Octet alignmentTh
...