The table below lists URNs registered by 3GPP. Applications for new entries must be made via email to the TSG CT WG1 Secretary. Applications must contain:
Namespace Specific Strings (NSS) for the Namespace Identifier (NID) equal to
3gpp as described in
RFC 5279.
| 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. | |
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
draft-drage-sipping-service-identification-01.
| 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:urn-xxx:3gpp-service.ims.icsi.mmtel NOTE 2 |
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 |
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
draft-drage-sipping-service-identification-01.
| 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:urn-xxx:3gpp-application.ims.iari.gsma-is NOTE 2 |
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 | ||
|
urn:urn-xxx:3gpp-application.ims.iari.gsma-vs NOTE 2
|
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: specifications TBD.
|
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: The complete NID will be determined when draft-drage-sipping-service-identification is completed and appropriate IANA registration is performed.
(Background information for the decision to create and maintain this page can be found in C1-071726 and C1-082533.)
page last updated:
2008-08-22: Link to RFC 5279 replaces link to
draft-monrad-sipping-3gpp-urn-namespace-03 .
2008-07-04: Adds reference to C1-082533.
2008-06-26: Additional explanatory text added (source: C1 Chairman)
2008-02-20: First two IARI entries
2007-09-14: vocabulary corrections
2007-09-07: Correction of typo
2007-09-06: Modifications agreed in CT1 email discussions.
2007-08-28 (first created)