Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

CLF

Connectivity session Location and repository Function

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.

Introduced
Rel-7
Where
Services › IMS
Specifications
5 specs
Also in
Core Network
CLF Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define CLF. Each summary describes the whole specification, not only this term.

TS 23.167Rel-17 → Rel-18

Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.

Full comparison in TS 23.167 →
TS 24.229Rel-18 → Rel-19

Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.

Full comparison in TS 24.229 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Initial introduction of CLF with basic location repository functionality for IMS networks. The architecture included interfaces to I-CSCF for session routing queries and support for tracking user connectivity across different access networks. Initial capabilities focused on storing and providing location information for session establishment and basic mobility scenarios.

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 vk10 IMS Emergency Services Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read