OID reference

its

2.28

Description

Intelligent Transport Systems (ITS)

Full description and source information

Identification

Identifier and names

Parent
2 (joint-iso-itu-t, joint-iso-ccitt)
Node code
28
Node name
its
Numeric OID
2.28
URN notation
urn:oid:2.28
Creation date
May 29, 2015
ASN.1, OID-IRI and named path variants
ASN.1 notation

{2 28}

  • {joint-iso-itu-t(2) its(28)}
  • {joint-iso-ccitt(2) its(28)}
OID-IRI notation
  • /2/28
  • /Joint-ISO-ITU-T/ITS
  • /Joint-ISO-ITU-T/28
Named path variants
  • /joint-iso-itu-t/its
  • /joint-iso-ccitt/its

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Intelligent Transport Systems (ITS)
Sources for this description

OID Repository

View at oid-base.com
Subsequent OIDs are defined in ISO 14817-3 "Intelligent transport systems -- ITS data dictionaries -- Part 3: Object identifier assignments for ITS data concepts" or assigned by the Central Intelligent transport systems Data Concept Registry (CIDCR).

Placing all ITS data concepts under a single OID arc will allow for the greatest possible benefit of the RELATIVE OID ASN.1 type. Having this arc directly underneath the joint-iso-itu-t arc will allow for efficient encodings even when the RELATIVE OID format cannot be used.

Placing all ITS data concepts under a single OID arc will also assist in harmonization efforts as developers will have a way to easily become aware of similar efforts, i.e., by going to the CIDCR. Nothing in ISO 14817-3 precludes users from assigning numbers under other arcs to their data. For example, ISO standards may still define their data under {iso(1) standard(0) <standard-number>}; however, by grouping definitions together under this 'its' arc, additional benefits may be achieved, as described above. A specific data concept may be identified by more than one OID. For example, an existing ITS data concept may have an OID assigned to it prior to the publication of this standard. Networks may continue to use that OID for interoperability, while new uses of the data concept may wish to use an OID under this 'its' OID arc in order to achieve the benefits described above.

This arc was assigned on 17 Apr 2015 by ITU-T Study Group 17 and will be endorsed on 29 May 2015 by ISO/IEC JTC 1/SC 6.

Registration

Registration authorities

First Registration Authority

Ken Vaughn

Current Registration Authority (inferred from ancestor 2)

ITU-T SG 17 & ISO/IEC JTC 1/SC 6

Direct children (1)

OIDNameDirect childrenDescendantsDescription
2.28.0 its-misc537 International Transport Systems (ITS) data concepts that do not relate to internationally standardized object classes

Siblings (38)

OIDNameDirect childrenDescendantsDescription
2.0 presentation00 Presentation layer service and protocol
2.1 asn11179 ASN.1 standards:
- Rec. ITU-T X.680 | ISO/IEC 8824 series: Information
Technology - Abstract Syntax Notation One (ASN.1)
;
- Rec…
2.2 association-control416 Association Control Service Element (ACSE), Rec. ITU-T X.227 | ISO/IEC 8650-1
2.3 reliable-transfer33 Reliable transfer service element (Rec. ITU-T X.218 | ISO/IEC 9066-1 and Rec. ITU-T X.228 | ISO/IEC 9066-2)
2.4 remote-operations1328 Remote operations service element (ROSE)
2.5 ds421576 Directory Services
2.6 mhs111505 Message Handling System (MHS), also known as Message Oriented Text Interchange System (MOTIS) in ISO
2.7 ccr, joint-CCR29 Commitment, Concurrency and Recovery (CCR) service and protocol
2.8 oda5110 Open Document Architecture (ODA)
2.9 ms61950 OSI network management, and particularly CMIP (Common Management Information Protocol) and GDMO (Guidelines for the Definition …
2.10 transaction-processing310 Transaction processing
2.11 dor, dorx34 ISO 10031-2 (withdrawn standard): Information technology -- Text and office systems -- Distributed-office-applications model --…
2.12 reference-data-transfer519 Reference data transfer
2.13 network-layer1537 Network layer management
2.14 transport-layer1116 Transport layer management
2.15 datalink-layer198 OSI data link layer management
2.16 country20533195 Joint (ITU-T and ISO/IEC) registration within a country
2.17 registration-procedures5125 ISO/IEC and/or ITU-T activities on registration procedures
2.18 physical-layer141 Physical layer management
2.19 mheg110 Multimedia and Hypermedia information coding Expert Group (MHEG)
2.20 genericULS633 Generic upper layers security (GULS)
2.21 transport-layer-security-protocol12 Transport layer security protocol
2.22 network-layer-security-protocol12 Network layer security protocol
2.23 international-organizations19494 International organizations
2.24 sios15 Security Information Objects (SIOS) for access control
2.25 uuid197245 UUIDs (Universally Unique Identifiers) generated in accordance with Recommendation ITU-T X.667 | ISO/IEC 9834-8
2.26 odp14 Rec. ITU-T X.900 series | ISO/IEC 10746 & 13235 series: Information technology -- Open Distributed Processing (ODP)
2.27 tag-based22 Tag-based identifications (identification mechanisms for which identifiers are stored in a memory-limited area of a tag like an…
2.40 upu312 Universal Postal Union (UPU)
2.41 bip17 Rec. ITU-T X.1083 | ISO/IEC 24708 "BioAPI Interworking Protocol (BIP)"
2.42 telebiometrics, id-telebio54439 Telebiometrics including telehealth and associated physiological quantities and units
2.48 cybersecurity22 Cybersecurity information exchange
2.49 alerting11728 Alerts and alerting agencies according to Recommendation ITU-T X.674
2.50 ors15 Rec. ITU-T X.672 | ISO/IEC 29168-1 "Information technology -- Open Systems Interconnection -- Object Identifier Resolution Syst…
2.51 gs1414 GS1
2.100 id-trader469
2.999 example00 Example
2.16840 1684015 This node IS NOT DESCRIBED YET