IEEE 1609.12:2016 pdf free download – IEEE Standard for Wireless Access in Vehicular Environments(WAVE) – ldentifier Allocations
PSIDs have two uses specified in IEEE Std 1609.3TM.First, a service provider indicates offeredidentifies advertised application-service opportunities by the PSID values in WAVE ServiceAdvertisement messages it transmits.Second, the WAVE Short Message Protocol (WSMP) deliversWAVE Short Message content to higher layer entities based on the PSID value set by the sender inthe message header. A third use of the PSID is specified in IEEE Std P1609.2/D16TM. A securitycertificate lists the PSID value(s) that identifying application areas for which a sender is authorizedto include in either a WAVE Service Advertisement or a WAVE-Short Message generate signed,secured protocol data units.
The fixed-length four-octet PSID format and values specified in trial-use IEEE Std 1609.3-2007 aredeprecated, and the registration process described in that document is no longer in effect. None ofthese those values was were fielded for other than experimental purposes. The IEEE RegistrationAuthority assignment procedures specified in that standard are inoperative.
The PSID shares characteristics and its numbering space with the Intelligent Transportation SystemsApplication Identifier (ITS-AID) used in standards from other international standards organizationsinvolved in Intelligent Transportation Systems including ISO,CEN, and ETSI. The specification ofthe ITS-AID and a high-level functional description of its management and assignment procedurescan be found in ISOTS 17419 [B14]3.The intention of the IEEE 1609 Working Group is to encouragethe global uniqueness of the PSID/ITS-AID values by coordinating allocations with the appropriateITS-AID assignment entities.
As a consequence of the length encoding in the first bits of Octet 0 in every p-PSID, only PSIDinteger values from decimal 0 (Ox00-00-00-00) to decimal 270549 119(0x10-20-40-7F) can be encodedin p-encoded PSIDs of length less than five octets.As a further consequence of the length encoding.not all octet strings are valid p-encoded PSID values. While p-encoded PSIDs of a given size aresequential, the transition from one length to the next involves skipping a number of hexadecimalvalues as indicated in ‘Table 1.For example,the p-en-coding of PSID 127 is 0p7F while the p-encoding of PSID 128 is 0p80-00.Consequently, hexadecimal values between 0x80 and Ox7F-FF arenot valid p-PSID values.
The p-encoded PSID format specified is compliant with the ITS-AID format specified in ISo TS17419 [B14]，Annex B gives ASN.1 structures that，when encoded with the Unaligned PackedEncoding Rules of ISO/IEC 8825-2 [B9], produce output that is bitwise compatible with p-encoding.
Note that in IEEE Std 1609.3-2010 and IEEE Std 1609.12-2012,PSID was specified in terms of what isreferred to in this standard as the p-encoded value.
4.2 Object identifier (OID)
In IEEE 1609 standards, OID is used to identify ASN.1 objects, including management informationbases (MIlBs), objects within MIBs, and other data structures.OID format is specified in ISO/IEC8824-1 and ISO/IEC 8825-1.
The values are hierarchically assigned, in this case through I5O and IEEE. The IEEE 1609 WorkingGroup is assigned value 1609 by the IEEE Standards Association3 at the fifth level of the hierarchy asshown below. Both the numeric value (in parentheses) and the text descriptor of each of the fivelevels of OID allocation are shown.
iso(1) iso-identified-organization(3) ieee(111) standards-association-numbered-series-standards(2)wave-stds(1609)