SIP Uniform Resource Identifier

Description

A SIP Uniform Resource Identifier (URI) is the fundamental addressing scheme used within networks that employ the Session Initiation Protocol (SIP), including the 3GPP IP Multimedia Subsystem (IMS). Defined syntactically by RFC 3261 and profiled within 3GPP specifications, it follows the standard URI format: `sip:user@domain`. The 'user' part can be a telephone number (in which case it is often formatted as a 'tel-URI' or as a numeric user part) or an alphanumeric identifier (like 'john.doe'), while the 'domain' part specifies the host or domain responsible for routing the request, such as an operator's network (`operator.com`) or a specific proxy server. SIP-URIs can also include parameters (separated by semicolons) for conveying additional session information, such as the transport protocol (`;transport=tcp`), and headers (introduced by `?`) for passing specific SIP header fields to the proxy.

Within the 3GPP IMS architecture, the SIP-URI is the primary public user identity for a subscriber. When a user registers with the IMS, they register one or more SIP-URIs (and potentially tel-URIs) with the network. The Serving-Call Session Control Function (S-CSCF) uses this URI to identify the user and apply the appropriate service logic. When a call is placed, the originating User Equipment (UE) or Application Server populates the SIP INVITE's Request-URI and the To header field with the SIP-URI of the intended recipient. The IMS routing machinery, including the Interrogating-CSCF (I-CSCF) and S-CSCF, then uses DNS procedures (like NAPTR and SRV records) to resolve the domain part of the URI to the appropriate SIP server in the recipient's home network to deliver the request.

The SIP-URI is more than just an address; it is a key element in subscriber identification, authentication, and service triggering. It is stored in the Home Subscriber Server (HSS) as part of the user's profile. The URI can also be used in conjunction with privacy mechanisms and asserted identity services. Furthermore, for interworking with non-IMS SIP networks or the Internet, the SIP-URI provides a globally routable, standardized format that enables seamless communication across administrative boundaries. Its flexibility allows it to represent not only end-users but also services (e.g., `sip:[email protected]`) and applications, forming the cornerstone of SIP-based session management and routing.

Purpose & Motivation

The SIP-URI was created to provide a universal, flexible, and text-based addressing scheme for SIP sessions, solving the problem of how to uniquely identify communication endpoints in an IP-based multimedia world. Prior to SIP and its URI, telephony used E.164 numbers exclusively, which are tied to a specific geographical or service hierarchy and are not natively compatible with Internet host-based routing. The development of SIP as a protocol for initiating interactive sessions required an address format that could integrate with Internet infrastructure (like DNS), support user-friendly aliases, and work alongside traditional telephone numbers.

The motivation stemmed from the vision of converged communications where users could be reached via an email-like address (`sip:[email protected]`) as well as a phone number. The SIP-URI standard, established in IETF RFC 2543 and later refined in RFC 3261, provided this capability. 3GPP adopted and profiled the SIP-URI for IMS starting in Release 5 to serve as the foundational subscriber identity, enabling the IMS to be a true Internet-protocol-based system. It addressed the limitation of circuit-switched identifiers by allowing for dynamic user assignment, easy integration with email and web services, and enabling rich presence and messaging applications that rely on a persistent, personal online identity rather than a device-centric number.

Key Features

• Standardized text format: `sip:[userinfo]@hostport[;parameters][?headers]`
• Supports both numeric (telephone-number) and alphanumeric user parts for flexible addressing
• Enables DNS-based routing of SIP requests through resolution of the domain part
• Can carry session-specific parameters (e.g., `;user=phone`, `;transport`) to influence signaling behavior
• Serves as the primary Public User Identity in 3GPP IMS for registration, authentication, and service invocation
• Globally unique and routable across different SIP/IMS network domains and the Internet

Evolution Across Releases

Defining Specifications