OID repository - 0.4.0.0.1.3.110 = {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) cap-IMS-object-identifiers(110)}

itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3)
`cap-IMS-object-identifiers(110)` [other identifier: `cap-u-abort-data`] child OIDs: version1(0) version3(2) version4(3) version5(4) version8(7)

OID description

OID:	{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) modules(3) cap-IMS-object-identifiers(110)}	(ASN.1 notation)
	0.4.0.0.1.3.110	(dot notation)
	/ITU-T/Identified-Organization/0/0/1/3/110	(OID-IRI notation)

Description: ASN.1 module named CAP-IMS-object-identifiers

Information: Defined in 3GPP TS 29.278.

This OID is also (very likely wrongly) named cap-u-abort-data to reference the ASN.1 module named CAP-U-ABORT-Data in ETSI TS 129 078 v6.4.0 (2004-12).
----------
From: John M Meredith
To: Kimmo Kymalainen
Date: 13 Sep 2005
Observations have highlighted an error in the ASN.1 of 29.078 and/or 29.278: in 29.078, OID "cap-IMS-object-identifiers" is allocated both the value 100 and 110. See:
{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-IMS-object-identifiers(100)} and
{itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-IMS-object-identifiers(110)}
Meanwhile 29.078 assigns {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-u-abort-data(110)}.
That is, the node "cap-u-abort-data" has a value which conflicts with one of the values of "cap-IMS-object-identifiers".
The obvious conclusion is that the error lies in 29.278, where the 110 should be changed to 100 (in at least two places). But it is not so quite straightforward, since 29.278 also assigns the value 100 to "cAP-object-identifiers", in {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-object-identifiers(100)}.
Please could you bring this to the attention of "3GPP CT4" with a view to raising appropriate Change Requests (CRs).
----------

Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024

Webmaster

26 Jan 2021