The Mobile
Broadband Standard

Uniform Resource Identifier (URI) list

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:

URNDescriptionReferenceContactRemarks
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:metadata:2005:Keyest:UICCKeyRequest defines format for the key request sent from the Terminal to the NAF Key Center requesting a Ks_local key 3GPP TS 33.110 Vesa Lehtovirta  
urn:3GPP:metadata:2005:Keyest:UICCKeyResponse defines a format for the key response sent from the NAF Key Center to the Terminal containing the Ks_local key 3GPP TS 33.110 Vesa Lehtovirta  
urn:3GPP:metadata:2005:Keyest:DeviceKeyRequest defines a format for the key request sent from the Remote Device to the NAF Key Centre requesting a Ks_local_device key 3GPP TS 33.259 Vesa Lehtovirta  
urn:3GPP:metadata:2005:Keyest:DeviceKeyResponse defines a format for the key response sent from the NAF Key Centre to the Remote Device containing the Ks_local_device key 3GPP TS 33.259 Vesa Lehtovirta  
urn:3GPP:metadata:2008:MBMS:Registration namespace of XML schema for MBMS UE user service registration and deregistration 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:FLUTE:FDT namespace of XML schema for 3GPP FDT release 6 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2007:MBMS:FLUTE:FDT namespace of XML schema for 3GPP FDT release 7 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2008:MBMS:FLUTE:FDT_ext namespace of XML schema for 3GPP FDT release 8 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2009:MBMS:FLUTE:FDT_ext namespace of XML schema for 3GPP FDT release 9 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2012:MBMS:FLUTE:FDT namespace of XML schema for 3GPP FDT release 11 extension 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2009:MBMS:schemaVersion namespace of XML schema for defining schemaVersion and delimiter element, used for backward and forward compatibility of the MBMS schemas across 3GPP releases 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2007:MBMS:downloadHeader namespace of XML schema for 3GPP MBMS download delivery method over OMA push bearers 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2005:MBMS:associatedProcedure namespace of XML schema for 3GPP MBMS Associated Delivery Procedures 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2008:MBMS:receptionreport namespace of XML schema for 3GPP MBMS reception reporting request 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2005:MBMS:envelope namespace of XML schema for 3GPP MBMS metadata envelope, for management of MBMS metadata fragments validity time 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:userServiceDescription namespace of XML schema for 3GPP MBMS main User Service Description metadata schema 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2007:MBMS:userServiceDescription namespace of XML schema for 3GPP MBMS User Service Description metadata release 7 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2008:MBMS:userServiceDescription namespace of XML schema for 3GPP MBMS User Service Description metadata release 8 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2009:MBMS:userServiceDescription namespace of XML schema for 3GPP MBMS User Service Description metadata release 9 extension 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2011:MBMS:scheduleDescription namespace of XML schema for 3GPP MBMS schedule fragment metadata 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:metadata:2012:MBMS:scheduleDescription namespace of XML schema for 3GPP MBMS schedule fragment metadata release 11 extension 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:securityDescription namespace of XML schema for 3GPP MBMS security description fragment metadata 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:securityRegistration namespace of XML schema for 3GPP MBMS service protection registration 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:securityDeregistration namespace of XML schema for 3GPP MBMS service protection deregistration 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:mskRequest namespace of XML schema for 3GPP MBMS service protection MSK request 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:securityRegistrationResponse namespace of XML schema for 3GPP MBMS service protection registration and deregistration response 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:mskResponse namespace of XML schema for 3GPP MBMS service protection MSK response 3GPP TS 26.346 Eric Turcotte  
urn:3GPP:PSS:profile:DASH10 profile name for 3GP-DASH release 10 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:PSS:profile:DASH11:MS3D profile name for 3GP-DASH release 11 multiview stereoscopic 3D video 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:PSS:profile:DASH11:FPS3D profile name for 3GP-DASH release 11 frame-packed stereoscopic 3D video 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:ns:DASH:MPD-ext:2011 namespace of XML schema for 3GPP extension of DASH 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:ns:PSS:DASH:QM10 name of the schemeIdURI used for 3GP-DASH quality reporting 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:ns:PSS:AdaptiveHTTPStreaming:2009:qm namespace of XML schema for 3GP-DASH quality reporting 3GPP TS 26.247 Eric Turcotte  
urn:3gpp:metadata:2011:HSD:receptionreport namespace of XML schema for 3GP-DASH report format 3GPP TS 26.247 Eric Turcotte  
urn:3GPP:ns:PSS:AdaptiveHTTPStreamingMPD:2009 namespace of XML schema for release 9 Adaptive HTTP Streaming (AHS) 3GPP TS 26.234 Eric Turcotte  
urn:3gpp:metadata:2009:PSS:receptionreport namespace of XML schema for AHS reception report 3GPP TS 26.234 Eric Turcotte  
urn:3GPP:ns:PSS:Bookmarking:2011 namespace of XML schema for network bookmark 3GPP TS 26.234 Eric Turcotte  
urn:org:3gpp:applications:ims-pss-mbms-service-discovery name of appids parameter for the ua-profile event package for the retrieval of service attachment from the SDF 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:metadata:2009:PSS:receptionreport name of appid used by the recording server to associate an XML body to include in the RTSP ANNOUNCE message 3GPP TS 26.237 Eric Turcotte  
urn:3GPP:metadata:2008:IMS-PSS-MBMS:UECap namespace of XML schema for PSS and MBMS UE Device Capabilities 3GPP TS 26.237 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:bootstrappingTransactionIdentifier namespace of XML schema for SIP based MBMS security parameter - bootstrapping transaction identifier 3GPP TS 26.237 Eric Turcotte  
urn:3GPP:metadata:2005:MBMS:nafKeyInfo namespace of XML schema for SIP based MBMS security parameter - NAF key information 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:bookmark:2012:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS release 11 network bookmark extension 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:bookmark:2012:IMS-PSS-MBMS:schemaVersion namespace of XML schema for IMS-PSS-MBMS release 11 network bookmark schema version 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:bookmark:2009:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS release 11 network bookmark 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:ParentalControl:2010:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS parental control 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:ParentalControlProfile:2010:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS parental control extension 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:npvr:2010:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS network PVR request from UE to SCF 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:contentreferral:2010:IMS-PSS-MBMS namespace of XML schema for IMS-PSS-MBMS Service Provider Initiated Content Referral Service (CRS) 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:metadata:2008:MTSI:qoereport namespace of XML schema for MTSI QoE report 3GPP TS 26.114 Eric Turcotte  
urn:3gpp:metadata:2011:MBMS:filterDescription namespace of XML schema for 3GPP MBMS Filter Description Metadata 3GPP TS 26.346 Eric Turcotte  
urn:3gpp:bookmark:2009:IMS-PSS-MBMS:schemaVersion namespace of XML schema for IMS-PSS-MBMS release 9 and 10 network bookmark schema version 3GPP TS 26.237 Eric Turcotte  
urn:3gpp:metadata:2013:MBMS:userServiceDescription namespace of XML schema for 3GPP MBMS User Service Description metadata release 12 extension 3GPP TS 26.346 Eric Turcotte -
urn:3gpp:metadata:2013:MBMS:scheduleDescription namespace of XML schema for 3GPP MBMS schedule fragment metadata release 12 extension 3GPP TS 26.346 Eric Turcotte  -
urn:3gpp:video-orientation Coordination of video orientation (CVO), see subclause 6.2.3 of TS 26.114 3GPP TS 26.114 Ozgur Oyman -
urn:3gpp:video-orientation:6 Higher granularity (6-bit) coordination of video orientation (CVO), see subclause 6.2.3 of TS 26.114 3GPP TS 26.114 Ozgur Oyman -
urn:3gpp:metadata:2005:MBMS:associatedProcedure-rel-12-extension namespace of XML schema for 3GPP MBMS Associated Delivery Procedures Release 12 Extension 3GPP TS 26.346 Eric Turcotte -
urn:3gpp:metadata:2014:MBMS:consumptionreport namespace of XML schema for 3GPP MBMS Consumption Report 3GPP TS 26.346 Eric Turcotte -
urn:3GPP:ns:ProSe:Discovery:2014 namespace of XML schema for ProSe 3GPP TS 24.334 Lena Chaponniere -
urn:3GPP:ns:ProSe:PC3ch:2014 namespace of XML schema for ProSe PC3ch signalling 3GPP TS 24.334 Lena Chaponniere -
urn:3gpp:roi-sent Signalling of the arbitrary region-of-interest (ROI) information for the sent video, see clause 6.2.3.4 of TS 26.114 3GPP TS 26.114 Ozgur Oyman -
urn:3gpp:predefined-roi-sent Signalling of the predefined region-of-interest (ROI) information for the sent video, see clause 6.2.3.4 of TS 26.114 3GPP TS 26.114 Ozgur Oyman -
urn:3gpp:fe Defines format for a functional entities defined in IMS. This namespace is to be used in the Response-Source header field. 3GPP TS 24.229 Marianne Mohali -
urn:3GPP:sos-anqp Defines format for an emergency call number and any associated emergency types. This format is used in the Emergency Call Number field of the Emergency Call Number ANQP-element specified in IEEE 802.11-2012. 3GPP TS 24.302
John-Luc Bakker -

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.

URNDescriptionReferenceContactRegistration of subtype - Note 2Remarks
URN-value (Note 1) Brief overview of the functionality associated with this NSS. Related specification(s) if appropriate Person requesting the URN assignment. No  
urn:urn-7:3gpp-service.ims.icsi.mmtel This URN indicates that the device supports the IMS Multimedia Telephony Communication Service framework, and specifically indicates that the terminal has the capabilities of multimedia telephony 3GPP TS 24.173 Mr Atle Monrad Yes  
urn:urn-7:3gpp-service.ims.icsi.iptv Extract from TS 183 063 clause 5.6.1: " This URN indicates that the device supports the IMS IPTV Service" ETSI TS 183 063 v2.1.0 Ms Sonia Compans No  
urn:urn-7:3gpp-service.ims.icsi.ra Extract from TS 185 010 (draft only) clause A.3: " This URN indicates that the device supports the IMS Remote Access Service" ETSI TS 185 010 draft file 05019-ngn-r2vxxx.pdf where xxx represents the latest version number Ms Sonia Compans No  
urn:3gpp-service.ims.icsi.omapush This ICSI value is associated with OMA Push services. The OMA Push 2.2 enabler release, which is in Candidate status in the OMA, includes support for SIP Push. SIP Push extends the OMA Push enabler, which is widely deployed and fundamental to many mobile data services, with the ability to operate over SIP-based networks such as 3GPP IMS. The OMA Push ICSI enables SIP transactions that are related to the OMA Push service to be identified, so that messages can be properly handled by the SIP/IP Core Network functions and OMA Push service entities. Support for SIP Push will be fundamental to the evolution of mobile data services in an LTE environment, as OMA Push service entities can provide seamless evolution for OMA service enablers from dependence upon the SMS-based WAP Push transport, transparently delivering the same service-specific data over SIP Push. OMA Push 2.2 Mr Bryan Sullivan No  
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.msg OMA CPM Pager Mode CPM Message : Uniquely identifies in a SIP MESSAGE a Pager Mode CPM Standalone Message. OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.msg" is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg OMA CPM Large Mode CPM Message: Uniquely identifies in SIP INVITE a request for Large Message Mode CPM Standalone Message. OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.largemsg" is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.filetransfer OMA CPM File Transfer: Uniquely identifies in SIP INVITE a request for CPM File Transfer OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.filetransfer" is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.session OMA CPM Chat: Uniquely identifies in SIP INVITE a request for CPM chat. OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.session" is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.deferred OMA CPM Deferred Message OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.deferred" is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.systemmsg OMA CPM System Message: Uniquely identifies in SIP INVITE a request for a CPM System message. OMA CPM TS Conversation v2.0 Mrs. Cristina Badulescu No This value is used in P-Preferred-Service and P-Asserted-Service.
+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.systemmsg” is used in Contact and Accept-Contact headers.
urn:urn-7:3gpp-service.ims.icsi.oma.cab_1.0 Used to identify and route message notifications specific for OMA CAB and OMA S-CAB, such as notifications to a user that he/she was added as a new contact by another user. OMA-TS-CAB-V1_0 OMA-TS-S_CAB-V1_0 Mrs. Cristina Badulescu No  
3gpp-service.ims.icsi.oma.cab_1.1 Used to identify and route contact subscription invitation requests, using a SIP MESSAGE between two network entities (e.g. cross-domain OMA CAB 1.1 Servers) as defined in OMA CAB 1.1. OMA-TS-CAB-V1_1 Suresh Chitturi No  
+g.oma.sip-im IM feature tag used in the Contact header of the SIP REGISTER request to indicate support for OMA SIMPLE IM, and in the Accept-Contact header of:

  • SIP INVITE for SIMPLE IM chat sessions, file transfer, Large Message Mode and deferred delivery of messages, and of
  • SIP MESSAGE containing a SIMPLE IM Pager Mode Message.
OMA-TS-SIMPLE_IM-V2_0 Mrs. Cristina Badulescu No  
+g.oma.sip-im.system-message IM feature tag used in the Contact header of the SIP REGISTER request to indicate that a IM client supports System Message, and in the SIP MESSAGE requests to distinguish system messages from normal user message. OMA-TS-SIMPLE_IM-V2_0 Mrs. Cristina Badulescu No  
+g.oma.sip-im.large-message IM feature tag used in the Contact header of the SIP REGISTER request to indicate that a IM client supports Large Message session, and in SIP INVITE to determine that the request is a Large IM Message. OMA-TS-SIMPLE_IM-V2_0 Mrs. Cristina Badulescu No  
urn:urn-7:3gpp-service.ims.icsi.mcptt This URN indicates that the device has the capabilities to support the mission critical push to talk (MCPTT) service. 3GPP TS 24.379 Mr. Ricky Kaura Yes  

urn:urn-7:3gpp-service.ims.icsi.mcdata

This URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) service.

3GPP TS 24.282 Mr. Ricky Kaura Yes  This URN is included in the "g.3gpp.icsi-ref" media feature tag in the Contact header field of SIP requests (not SIP MESSAGE) and responses, and the Accept-Contact header fields of non-register SIP requests.

This URN can be included by the device in the P-Preferred-Service header field of SIP requests, and is asserted by the network into the P-Asserted-Service header field of SIP Requests.

urn:urn-7:3gpp-service.ims.icsi.mcdata.sds

This URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service.

3GPP TS 24.282 Mr. Ricky Kaura Yes  This URN is included in the "g.3gpp.icsi-ref" media feature tag in the Contact header field of SIP requests (not SIP MESSAGE) and responses, and the Accept-Contact header fields of non-register SIP requests.

This URN can be included by the device in the P-Preferred-Service header field of SIP requests, and is asserted by the network into the P-Asserted-Service header field of SIP Requests.

urn:urn-7:3gpp-service.ims.icsi.mcdata.fd

This URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) File Distribution (FD) IMS communication service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) File Distribution (FD) IMS communication service.

3GPP TS 24.282 Mr. Ricky Kaura Yes  This URN is included in the "g.3gpp.icsi-ref" media feature tag in the Contact header field of SIP requests (not SIP MESSAGE) and responses, and the Accept-Contact header fields of non-register SIP requests.

This URN can be included by the device in the P-Preferred-Service header field of SIP requests, and is asserted by the network into the P-Asserted-Service header field of SIP Requests.

urn:urn-7:3gpp-service.ims.icsi.mcvideo

This URN indicates that the device has the capabilities to support the mission critical video (MCVideo) service.

3GPP TS 24.281 Mr Haitao Wei Yes  

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.

URNDescriptionReferenceContactRegistration of subtype - Note 2Remarks
URN-value (Note 1) Brief overview of the functionality associated with this NSS. Related specification(s) if appropriate Person requesting the URN assignment. No  
urn:urn-7:3gpp-application.ims.iari.gsma-is Image Share service makes use of MSRP to send still images between terminal devices that are IMS registered. It is in some sense a ’Combinational Service’ insofar as there is a requirement for a voice call to be active. However, the implementation of the service means that the interaction between CS domain voice call and the exchange of images is only coupled at the device itself. To exchange images it is a pre-requisite requirement that the Subscribers involved in the exchange are IMS registered. GSMA PRD IR.79 Mr Dan Warren No  
urn:urn-7:3gpp-application.ims.iari.gsma-vs Video Share service use SIP signalling to establish an RTP session for the transport of uni-directional video content from one device to another. It has been defined in two phases. Phase 1: a requirement for a CS domain voice call to be active to enable the Video Share to session to be coupled with. Phase 2: the video session could be coupled with a different service (for example IM), started independent of any service or even a video session sent to a point in the network where it is stored and then retrieved by the intended recipient at a later time. Note that Phase 1 uses Feature Tag as a mechanism to identify the service, whereas Phase 2 will use the IARI including IARI in Feature Tag format. Phase 1: GSMA PRD SE.41 and GSMA PRD IR.74 Phase 2: GSMA PRD IR.84. Mr Dan Warren No  
urn:urn-7:3gpp-application.ims.iari.pnm-controller This URN is used to define the IARI for the PNM controller application and indicates that the device supports the PNM controller application. 3GPP TS 24.259 Mr Atle Monrad No  
urn:urn-7:3gpp-application.ims.iari.ttc-iss Image Sharing with Synchronization of real-time interactions (ISS) provides IMS users functionalities of Image Sharing and manipulating on the shared image, i.e. drawing figures or texts on the shared image, changing its scale, scrolling the shared image and rotating the shared image. The original shared image can be a white board or any other color as a background of drawing. This URN is used for exchanging capabilities or negotiating services for IMS users defined as IARI. TTC Technical Specification Number: TS-1016 "RCSS Phase 3; Stage 2/3 Specification; Content Sharing Enhancement (Image sharing with synchronization of real-time interactions, Video sharing synchronized pause/resume)" version 1.1 April 28 2011 Tetsuo Inoue (editor), Ataru Kobayashi (Chairman of TTC RCSS Sub-working group) No  
urn:urn-7:3gpp-application.ims.iari.rcse.im Used to uniquely identify the RCS Chat service based on either OMA SIMPLE IM or OMA CPM in SIP OPTIONS based capability exchanges. RCS-e 1.2 and RCS 5.0 Mr David Hutton No  
urn:urn-7:3gpp-application.ims.iari.rcse.ft Used to uniquely identify the RCS File Transfer service based on either OMA SIMPLE IM or OMA CPM in SIP OPTIONS based capability exchanges. RCS-e 1.2 and RCS 5.0 Mr David Hutton No  
urn:urn-7:3gpp-application.ims.iari.rcse.sp Used to uniquely identify the capability to share social presence information in SIP OPTIONS based capability exchanges. RCS-e 1.2 and RCS 5.0 Mr David Hutton No  
urn:urn-7:3gpp-application.ims.iari.rcse.dp Used to uniquely identify in SIP OPTIONS based capability exchanges the capability to share capabilities also through OMA SIMPLE Presence. RCS-e 1.2 and RCS 5.0 Mr David Hutton No  
urn:urn-7:3gpp-application.ims.iari.rcs.geopull Used to uniquely identify the capability to handle geolocation pull requests in SIP OPTIONS based capability exchanges. RCS 5.0 Mr David Hutton No  
urn:urn-7:3gpp-application.ims.iari.rcs.geopush Used to uniquely identify the capability to handle geolocation push requests in SIP OPTIONS based capability exchanges as well as to identify the geolocation push request itself. That request bases on either OMA SIMPLE IM or OMA CPM file transfer. RCS 5.0 Mr David Hutton No  

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}

URNDescriptionReferenceContactRemarks
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).

URIDescriptionReferenceContactRemarks
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.)

Search
Events

5g imt image

 

News Feeds