CLF

Connectivity session Location and repository Function

Core Network →
Introduced in Rel-7 Also in: Core Network

CLF is an IMS network function that stores and provides user equipment location information during connectivity sessions to enable efficient routing and service delivery.

Category
Core Network
Introduced
Rel-7
Where
Services › IMS
Also touches
1 segments
Specifications
5 specs
CLF Description Purpose Related Classification Detected Changes Specifications

Description

The Connectivity session Location and repository Function (CLF) is a critical component within the 3GPP IP Multimedia Subsystem (IMS) architecture, specifically designed to manage and provide location information for user equipment during active connectivity sessions. It operates as a centralized repository that maintains real-time data about the network attachment points and connectivity status of IMS users across various access networks, including both 3GPP and non-3GPP access technologies. The CLF interfaces with multiple network elements to collect and distribute this location information, enabling efficient session routing and service delivery.

Architecturally, the CLF functions as a standalone network element that interacts with several key IMS components. It maintains interfaces with the Interrogating Call Session Control Function (I-CSCF) and Serving Call Session Control Function (S-CSCF) to provide location information during session establishment and routing decisions. The CLF also interfaces with the Home Subscriber Server (HSS) to obtain subscriber profile information and with various access network elements to gather connectivity status updates. This network-centric approach allows the CLF to maintain a comprehensive view of user connectivity across heterogeneous networks.

The CLF operates through a combination of registration, query, and notification mechanisms. When a user equipment establishes connectivity through any access network, the relevant network elements notify the CLF about the user's current location and connectivity status. The CLF stores this information in its repository, associating it with the user's public identity. During session establishment, when an incoming session request arrives, the I-CSCF queries the CLF to determine the user's current connectivity status and location. Based on this information, the CLF provides routing instructions that direct the session to the appropriate S-CSCF serving the user at that location.

Key components of the CLF include the location repository database, which stores real-time connectivity information; the query processing engine, which handles location queries from network elements; and the notification interface, which receives updates from access networks about user connectivity changes. The CLF also includes subscription management capabilities that allow network elements to subscribe to location change notifications for specific users. This proactive notification mechanism enables efficient session routing without requiring repeated queries, reducing signaling overhead and improving session setup times.

The CLF plays a crucial role in enabling seamless mobility and service continuity across different access networks. By maintaining accurate location information, it supports features such as access network selection, session continuity during handovers, and efficient routing of multimedia sessions. The CLF's ability to work with both 3GPP and non-3GPP access technologies makes it essential for converged networks where users may switch between different types of connectivity while maintaining their IMS services.

Purpose & Motivation

The CLF was introduced in 3GPP Release 7 to address the growing complexity of session routing in converged IP Multimedia Subsystem (IMS) networks. As operators began deploying IMS services across multiple access technologies, including both 3GPP cellular networks and non-3GPP access like WiFi, there emerged a need for a centralized mechanism to track user connectivity locations. Previous approaches relied on distributed location information stored in various network elements, leading to inefficient session routing, increased signaling overhead, and difficulties in maintaining service continuity during mobility events.

Before the CLF's introduction, IMS networks faced challenges in efficiently routing sessions to users who could be connected through multiple access points simultaneously or who frequently changed their connectivity points. The traditional approach of querying multiple network elements for location information resulted in increased session setup delays and higher signaling load on the network. The CLF solved these problems by providing a single, authoritative source for user connectivity information, enabling faster session routing decisions and reducing overall network signaling.

The creation of the CLF was motivated by the need to support converged services across heterogeneous networks while maintaining efficient network operation. As operators expanded their service offerings to include fixed-mobile convergence and multi-access connectivity, the ability to accurately track and utilize user location information became critical for service delivery. The CLF enabled operators to optimize their network resources by providing intelligent routing based on current connectivity status, while also supporting regulatory requirements for location-based services and emergency call routing.

Classification

Part ofIMS
Related approachesI-CSCFS-CSCFHSS

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-7, normative work from Rel-15.

Rel-15 3 changes

In Release 15, the CLF function was newly introduced to support emergency sessions over untrusted non-3GPP access in 5GS. This involved updates to domain selection rules for emergency session attempts and corrections to the usage of the emergency service indication and emergency session indication within the signaling. The CLF, as defined, registers the association between the IP address allocated to the UE and related network location information for these sessions.

  • Handling of emergency sessions over untrusted N3GPP access in 5GS TS 23.167CR0321
  • Update on Domain Selection Rules for emergency session attempts TS 23.167CR0331
  • Correcting usage of emergency service indication and emergency session indication TS 23.167CR0339
Rel-16 2 changes

In Release 16, the CLF function was enhanced to support IMS emergency sessions for roaming users in 5GS deployments that lack IMS-level roaming interfaces. This involved specific corrections and support for IMS Emergency Registration and Session Establishment procedures in such roaming scenarios. The updates ensure emergency services are provided by the visited network, aligning with the principle that emergency services shall not be provided by the home network when a UE is roaming.

  • Support of IMS emergency sessions for roaming users in 5GS deployments without IMS-level roaming interfaces TS 23.167CR0350
  • Correction for IMS Emergency Registration and Session Establishment TS 23.167CR0355
Rel-17 1 change

In Release 17, the CLF function was enhanced to support Caller Identity Attestation and Assertion for Emergency sessions. This new capability allows the CLF, which registers the association between a UE's IP address and its network location information, to handle verified identity information specifically for emergency call instances. This update integrates with the existing emergency session framework managed by functions like the LRF and E-CSCF.

  • Support for Caller Identity Attestation and Assertion of Emergency sessions TS 23.167CR0359

Explore further

Broader topics and technologies where CLF plays a role.

Defining Specifications

3GPP specifications that define or reference CLF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.167 vj11 IMS Emergency Sessions Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.819 v1700 IMS Services via Fixed Broadband Access Rel-7
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 33.203 vj10 IMS Security Specification Rel-19