1 / 15

IEEE P1609.12™ Provider Service Identifier (PSID) Allocations

IEEE P1609.12™ Provider Service Identifier (PSID) Allocations. November, 2010 Justin McNew, Kapsch TrafficCom Inc. justin.mcnew@kapsch.net T. M. Kurihara, Chair, IEEE 1609 WG tkstds@mindspring.com. IEEE Standards.

nuru
Télécharger la présentation

IEEE P1609.12™ Provider Service Identifier (PSID) Allocations

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. IEEE P1609.12™Provider Service Identifier (PSID) Allocations November, 2010 Justin McNew, Kapsch TrafficCom Inc. justin.mcnew@kapsch.net T. M. Kurihara, Chair, IEEE 1609 WG tkstds@mindspring.com

  2. IEEE Standards • Describes the Wireless Access in Vehicular Environments (WAVE/DSRC) architecture and services necessary for multi-channel DSRC/WAVE devices in mobile vehicular environment. • The family of IEEE 1609™ standards: • IEEE 1609.1™-2006, Resource Manager (revision title change to Remote Management Services changes scope to include over-the-air management of classes of devices) planned approval 2011 • IEEE Std 1609.2™-2006, Security Services for Applications and Management Messages (in development, planned approval 2011) • IEEE Std 1609.3™-2010, Networking Services • IEEE Std 1609.4™-2010, Multi-Channel Operation • IEEE Std 1609.11™-2010, Over-the-air Interface for Electronic Funds Collection (EFC) • Projects in development: • IEEE P1609.0™, WAVE - Architecture • IEEE P1609.12™, WAVE - Provider Service Identifier Allocation • Note: Includes legacy specification, ASTM E2213-03 - 2003, Standard Specification for Telecommunications and Information Exchange Between Roadside and Vehicle Systems – 5.9GHz Band Dedicated Short Range Communications (DSRC) Medium Access Control (MAC) and Physical Layer (PHY) Specifications 1

  3. IEEE 802.11p, Amendment to IEEE Standard 802.11™-2007 Title: Draft Standard for Information Technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications Amendment 6: Wireless Access in Vehicular Environments Status Approved as an amendment in 2010 WAVE Amendment is being included in the revision to IEEE Std 802.11™-2007; IEEE project designation is IEEE P802.11mb™, Revision of IEEE Std 802.11™-2007 as amended by: IEEE Std 802.11k™-2008 IEEE Std 802.11r™-2008 IEEE Std 802.11y™-2008 IEEE Std 802.11w™-2009 IEEE Std 802.11n™-2009 In P802.11mb™ initial IEEE sponsor ballot, scheduled for approval of the 2400+ page document in 2011 Caution. Note that changes in clause numbers and wording are being made to the published amendments in the process of including the WAVE amendment and five other amendments into revised P802.11mb™draft. 2

  4. P1609.12™ Objectives • “The purpose of this standard is to record PSID allocation decisions.” • Will include normative requirements on PSID allocations • Describes the PSID decisions in the IEEE 1609™ family of standards, agreement with SAE J2735 Technical Committee, and existing registration authority • Document values identified in source standards and in operational use • May be affected and is adaptable to deployment and operational determinations for a global ITS

  5. PSID defined • Provider Service Identifier (PSID): “An octet string that identifies a service provided by a higher layer entity.” • Defined, specified in IEEE Std 1609.3™-2010: • Carried in the WAVE Service Advertisement to indicate what services are locally available • Carried in the WAVE Short Message Protocol (WSMP) header to allow routing of data to interested recipient higher layer entities

  6. PSID specified • Ref: Table 4, IEEE Standard 1609.3™-2010, Network Services • It has been shown that PSID encoding is compliant with and can be expressed using ASN.1 notation and unaligned packed encoding rules Number of values 128 16k 2M 268M

  7. PSID examples

  8. PSID Background • Was (IEEE Trial Use Standard 1609.3™-2007) • Fixed, flat 4-octet size • Values assigned by IEEE Registration Authority Committee (RAC) • ($1000 fee; no values registered to date, process on hold) • ~30 legacy values honored • Some values not provided to IEEE RAC for assignment • For testing purposes • For temporary assignments for demonstrations • Now (IEEE Standard P1609.12™D0.2, October 2010) • Variable size • Values assigned for registration - TBD • Intend to share numbering space with other ITS standardization activities • ~30 (1-octet) ISO AID legacy values honored • Some values reserved/allocated as covered in existing standards IEEE 1609™/SAE J2735/ISO TC204/ETSI, for testing, and for future use (proposed allocation on following charts)

  9. PSID Proposal • IEEE 1609™ Working Group proposes the following based on discussion in meetings previous to this meeting: • Align with the existing AID values allocated (values 0 through 31) • SAE J2735 has identified 32 values in 1-octet space in J2735, DSRC Message Sets and Data Dictionary • Approved in joint session by IEEE 1609™ and SAE J2735 groups • 32 values for IEEE 1609™ and ISO/ETSI for future use • SAE J2735 has identified 256 values in 2-octet space in J2735 revision • Approved in joint session by IEEE 1609 and SAE J2735 groups • 256 values for IEEE 1609™ and ISO/ETSI for future use in 2-octet space • Remainder of 2-octet space available for allocation by an appropriate number assignment authority (to be determined)

  10. PSID Proposal (cont’d) • IEEE 1609™ Working Group proposes the following: • 3-octet and 4-octet spaces to be administered by an appropriate number assignment authority (to be determined and expect to include allocations identified in operational use and standards documents) • ≥ 5-octets spaces are reserved for future allocation, as needed

  11. IEEE 1609.12™ Allocation Table (preliminary)(modified based on discussion October 25, 2010) *When identified, numbers not allocated for legacy use, assigned by interim experts group, or reserved will revert to a formally constituted number authority.

  12. Proposed Way Forward • IEEE RAC Assignment Process on hold until P1609.12™, WAVE PSID Allocation, is completed and ITS number authority is formally constituted • Interim interested experts group to be constituted to administer PSIDs (and AIDs) pending an ITS number authority identification and operation • Interim experts group may provide suggestions for the operation of an ITS number authority taking into consideration global requirements • Interim experts group may suggest what is needed to reconcile various views of use of PSIDs and AIDs • Numbers not set aside for standards developing organizations use, testing, and other uses, are available for allocation by a global ITS number authority 11

  13. View in the Rear View Mirror Application Context Identifier (ACID) Provider Service Identifier (PSID) Application Identifier (AID) Application Entity Identifier (AEID) For the future consideration by the IEEE 1609 working Group: ServiceID ITS-msg-set-ID ITS-msg-ID 12

  14. Current Practice – IEEE Registration Authority Committee (RAC) and NEN • Describes the flat fixed four-octet size number space as described in IEEE Trial Use Standard 1609.3™-2007 with registration requirement http://standards.ieee.org/regauth/rac.html • Superceded by IEEE Standard 1609.3™-2010, identifies 1- and 2-octet space value identified in IEEE P1609.12™, PSID Allocation, 3-and 4-octet space for assignment by a TBD “number authority,” and ≥5-octet space, reserved • No assignments by the RAC have been made and on hold pending outcome of global agreements • Manufacturer ID (identified in approved standard, operational, administered by a national standardization body, NEN) 13

  15. Global ITS View • Global “number authority” for ITS operations • Number authority as part of a larger global entities, such as, a global ITS industry consortia charter (e.g., WiFi Alliance) or a Global ITS Alliance, TBD) • Consolidate in global ITS entity, role and responsibility for administering identifiers and other ITS artifacts for global interconnection, harmonization, interoperability, sustainability, and safety 14

More Related