TEL-URL

Telephone Uniform Resource Locator

Identifier
Introduced in Rel-6
A URI scheme for identifying telephone numbers, standardized as 'tel:' in 3GPP. It provides a uniform way to encode and address telephone numbers within network protocols and services, enabling consistent call routing and service invocation across different systems.

Description

The Telephone Uniform Resource Locator (TEL-URL) is a Uniform Resource Identifier (URI) scheme defined by the IETF and adopted within 3GPP specifications, primarily for use in IP Multimedia Subsystem (IMS) and other telecommunication services. Its syntax follows the pattern 'tel:[telephone-subscriber]', where the telephone-subscriber part can be a global number (e.g., +1-555-123-4567) or a local number, optionally including visual separators like hyphens or parentheses for human readability, though these are typically removed during processing. The scheme supports additional parameters for extensions, such as 'phone-context' to define a local dialing plan, and 'isub' for an ISDN subaddress, allowing it to represent a wide range of telephony addressing scenarios beyond simple E.164 numbers.

Within the 3GPP architecture, TEL-URL is a fundamental identifier used in signaling protocols, most notably the Session Initiation Protocol (SIP) employed by the IMS. When a user initiates a voice or video call, a SIP INVITE message may contain a Request-URI formatted as a TEL-URL, specifying the destination's telephone number. This URI is then used by Call Session Control Functions (CSCFs) and other network elements to perform number normalization, routing decisions, and service triggering. For instance, the Serving-CSCF (S-CSCF) can match a TEL-URL against iFC (initial Filter Criteria) to invoke specific application servers, enabling services like number translation, call forwarding, or integration with legacy circuit-switched networks via the MGCF (Media Gateway Control Function).

Its role extends beyond basic call setup to presence services, messaging, and supplementary services. In presence, a watcher's subscription may use a TEL-URL to identify the presentity (the entity being watched). In messaging, it can be used as an address for SMS over IP or multimedia messages. The TEL-URL's design ensures interoperability between IP-based services and traditional telephony networks by providing a clear, standardized mapping between telephone numbers and URI-based addressing, which is essential for the convergence of fixed, mobile, and VoIP services. Its specification in 3GPP TS 23.271 (Functional stage 2 description of LCS) also highlights its use in Location Services, where it can identify a target for location requests.

Purpose & Motivation

The TEL-URL was created to address the need for a standardized, uniform method to represent telephone numbers within the context of Internet protocols and next-generation networks. Prior to its adoption, telephone numbers were often handled in an ad-hoc manner within different applications and protocols, leading to interoperability issues, especially as networks evolved towards all-IP architectures like IMS. The 'tel:' URI scheme provides a consistent syntax that separates the logical telephone number from the physical network or service, enabling seamless integration between circuit-switched telephony and packet-switched services.

Its introduction was motivated by the convergence of telecommunications and the Internet, where traditional E.164 numbering needed to be incorporated into IP-based signaling frameworks such as SIP. Without a standard like TEL-URL, embedding phone numbers in SIP messages would be ambiguous, complicating routing, service invocation, and number portability. By defining a clear URI scheme, 3GPP ensured that telephone numbers could be natively supported in IMS and other IP-centric services, facilitating features like VoIP calling, unified messaging, and ENUM (Telephone Number Mapping) lookups that translate TEL-URLs into SIP URIs or other records.

Furthermore, TEL-URL solves the problem of representing local numbers and private numbering plans within a global context. The 'phone-context' parameter allows a number to be interpreted correctly within a specific domain or geographic area, which is crucial for enterprise networks or national dialing plans that don't use full international format. This flexibility supports the migration from legacy systems and enables advanced services that rely on precise number identification, such as lawful interception, emergency calling (e.g., mapping to PSAPs), and customized call routing based on number analysis, thereby future-proofing telephony addressing in evolving networks.

Key Features

  • Standardized URI scheme ('tel:') for telephone number representation
  • Supports global E.164 numbers (e.g., +[country code][subscriber number])
  • Accommodates local numbers with 'phone-context' parameter for dialing plan context
  • Includes optional ISDN subaddress ('isub') for additional addressing information
  • Enables interoperability between IP-based signaling (e.g., SIP) and legacy telephony networks
  • Used for routing, service triggering, and identification in IMS and other 3GPP services

Evolution Across Releases

Rel-6 Initial

Introduced TEL-URL within 3GPP specifications, primarily in TS 23.271 for Location Services and adopted for IMS-based call control. Established its use as a standard identifier for telephone numbers in SIP signaling, enabling basic call setup and routing between IP multimedia networks and circuit-switched domains.

Defining Specifications

SpecificationTitle
TS 23.271 3GPP TS 23.271