Universal Resource Identifier

Description

A Universal Resource Identifier (URI) in 3GPP is a compact sequence of characters that identifies an abstract or physical resource, adhering to IETF RFC 3986 and related standards. It is used extensively across 3GPP specifications for naming, addressing, and identifying entities such as users, services, applications, and network nodes. URIs serve as a common syntax for resource identifiers, enabling interoperability between 3GPP networks and the broader internet ecosystem. In architectures like the IP Multimedia Subsystem (IMS), URIs are crucial for user identities (e.g., SIP URIs like sip:[email protected]), service identifiers, and routing information, forming the basis for session establishment and service invocation.

URIs work by providing a structured format that includes a scheme (e.g., sip, tel, http), authority, path, query, and fragment components. In 3GPP, specific URI schemes are standardized for various purposes. For example, SIP URIs are used for IMS user identities and routing, tel URIs for telephone numbers, and HTTP URIs for web-based services. When a UE or network element needs to reference a resource, it constructs or parses a URI according to these rules. During IMS registration, a UE provides a SIP URI as its public user identity, which the Home Subscriber Server (HSS) stores and uses for authentication and service provisioning. Routing engines in Call Session Control Functions (CSCFs) then use these URIs to direct signaling messages to the correct endpoints.

Key components in 3GPP involving URIs include the IMS core, where URIs are embedded in SIP headers like From, To, and Contact; service layer applications that use URIs for service discovery via Uniform Resource Names (URNs); and management systems where URIs identify managed objects. The URI syntax allows for extensibility, supporting parameters that convey additional information such as transport protocols or user preferences. In messaging services like SMS over IP (SMSoIP) or multimedia messaging, URIs can specify destination addresses or content locations. The parsing and validation of URIs are handled by protocol stacks in UEs and network functions, ensuring consistent interpretation across different implementations.

URI's role in 3GPP networks is multifaceted: it enables user identification and routing in IMS, facilitates service exposure through APIs (e.g., using URIs in RESTful interfaces), and supports resource location in management protocols like OMA DM or 3GPP management services. By adopting internet standards, 3GPP ensures that mobile networks can seamlessly integrate with web services and applications. URIs also underpin numbering and addressing evolution, supporting the transition from E.164 numbers to IP-based identifiers. This universality makes URIs a cornerstone for All-IP networks, supporting everything from voice over LTE (VoLTE) to IoT service layer communications.

Purpose & Motivation

The Universal Resource Identifier (URI) was incorporated into 3GPP to address the need for standardized, flexible resource identification in evolving mobile networks. Prior to its adoption, telecom systems relied heavily on E.164 numbers and proprietary addressing schemes, which were insufficient for IP-based multimedia services and internet interoperability. As 3GPP moved towards All-IP architectures with IMS in Release 5, there was a requirement for a universal naming system that could identify diverse resources—users, services, content—across heterogeneous networks. URIs, as established by IETF, provided a well-defined syntax that could unify addressing across telecom and internet domains.

URI solves problems of fragmentation and incompatibility in resource referencing. It enables seamless service discovery, session initiation, and messaging between mobile devices and internet servers. For example, in IMS, SIP URIs allow users to be identified independently of their devices or locations, supporting rich communication services. Without URIs, integrating web technologies like HTTP, email, or instant messaging into mobile networks would be cumbersome. URIs also future-proof addressing by accommodating new schemes and parameters as services evolve, such as for IoT device identifiers or API endpoints.

Historically, URI adoption in 3GPP was motivated by the convergence of telecom and IT, driven by the rise of multimedia and data services. Release 2 saw early use in messaging, but it was with IMS that URIs became central. They addressed limitations of traditional telecom identifiers by supporting alphanumeric formats, domain-based routing, and extensibility. This allowed 3GPP networks to offer innovative services like presence, video calling, and web integration, competing with OTT providers. URIs continue to be essential for 5G service-based architectures and network slicing, where resources need unique, scalable identifiers.

Key Features

• Standardized syntax per IETF RFC 3986 for consistent parsing
• Supports multiple schemes (e.g., sip, tel, http, urn) for diverse resources
• Enables user and service identification in IMS and beyond
• Facilitates interoperability with internet protocols and services
• Extensible with parameters for additional context or routing info
• Used for addressing in messaging, management, and APIs

Evolution Across Releases

Defining Specifications