Uniform Resource Identifier (URI) List

Uniform Resource Name values maintained by 3GPP:

The tables below list URIs registered by 3GPP. Applications for new entries must be made via email to the TSG CT WG1 Secretary. Applications must contain:

• a proposal for the URN value;
• a brief description of its functionality;
• a reference to the specification or other publicly available document (if any) containing the definition;
• the name and email address of the person making the application; and
• any supplementary information considered necessary to support the application.

Namespace Specific Strings (NSS) for the Namespace Identifier (NID) equal to 3gpp as described in RFC 5279:

Communication services (ICSI values) registered by 3GPP:

These URNs are associated with the top level identifier "3gpp-service" of the Namespace Specific Strings (NSSs) as described in RFC 6050.

Applications (IARI values) registered by 3GPP:

These URNs are associated with the top level identifier "3gpp-application" of the Namespace Specific Strings (NSSs) as described in
RFC 6050.

XML Namespace Registry for the Namespace Identifier (NID) equal to 3gpp as described in RFC 5279:
The XML namespace has a NID set to 3gpp. It is recommended that domain segregation of the namespace can follow: the URNs identifying namespaces are in the class "ns". Subsequent tags can follow.
The model follows the following grammar:

urn:3gpp:ns:{UniqueIdentifier}:{OptionalSchemaSpecificTags}

URN	Description	Reference	Contact	Remarks
URN-value (Note 1)	Brief overview of the functionality associated with this NSS.	Related specification(s) if appropriate	Person requesting the URN assignment.
urn:3gpp:ns:extRegExp:1.0	namespace of XML schema of the reg event package extension for wildcarded identity transport	TS 24.229	Mr Keith DRAGE	.
urn:3gpp:ns:extRegInfo:1.0	namespace of XML schema of the reg event package extension for policy transport	TS 24.229	Mr Keith DRAGE	.
.

 

XML URI Registry for URIs used in a 3GPP TS, identifying a resource, and having a Namespace Identifier (NID) not equal to 3gpp (see RFC 5279). This registry does not register URIs used in 3GPP protocol specifications that have been assigned by other authorities, e.g. URIs already used in ETSI publications relating to core functions of the IP Multimedia Subsystem (IMS) used by the Next Generation Network standardized within ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) (see ETSI TR 183 050 for a registry of assigned protocol numbers and names used in TISPAN protocol specifications).

URI	Description	Reference	Contact	Remarks
URI-value (Note 1)	Brief overview of the functionality associated with this NSS.	Related specification(s) if appropriate	Person requesting the URI assignment.
.

 

NOTE 1: A combination of lower and upper case letters can appear in the URN. This may be useful for reading by humans, but note that parsers do not distinguish between upper and lower case letters within URNs.

NOTE 2: Registration of subtype ...

• When the value of the column is "Yes" any organisation can register subtypes of this value on this registration page.
• When the value of the column is "No", subtypes, if any, are controlled by the registering organisation.
• Neither a "Yes" or "No" value presumes that subtypes have been defined, but merely indicates, if subtype values are defined, where the appropriate registrations could be found.
• Multiple levels of subtypes are allowed as defined by RFC 6050; each level, and value in the level, has to have an independent registration according to these rules.

(Background information for the decision to create and maintain this page can be found in C1-071726, C1-082533, C1-092017, C1-092976, C1-124619 and C1-130795.)