Discovery Service

Description

The Discovery Service (DS) is a functional element and associated procedures within the 3GPP Location Services (LCS) architecture. Its primary role is to act as a directory or registry that provides discovery information to LCS Clients. An LCS Client is an application or network entity that requests the location of a target UE. Before it can make a location request, the client needs to know *which* network node (the Location Server, such as a Gateway Mobile Location Centre (GMLC) in the core network or a Location Management Function (LMF) in 5GC) is responsible for or can serve the target UE. The DS provides this routing and capability information.

Architecturally, the DS can be implemented as a standalone network node or integrated into an existing node like a GMLC. It maintains a database or has access to provisioning data that maps key identifiers (like the target UE's Mobile Subscriber ISDN Number (MSISDN), International Mobile Subscriber Identity (IMSI), or Serving Network identity) to the address (e.g., IP address, Diameter hostname) of the appropriate Location Server. The procedure typically involves the LCS Client sending a Discovery Request message to a known DS entry point. This request contains the target identifier. The DS processes this request, performs any necessary lookups or inter-network routing resolution (e.g., using the LCS Roaming Exchange (LRX) for inter-PLMN cases), and returns a Discovery Response with the address of the relevant Location Server and potentially its supported capabilities (e.g., positioning methods, privacy protocols).

The DS is crucial for scalable and interoperable LCS deployments, especially in multi-vendor environments, roaming scenarios, and networks with multiple, geographically distributed Location Servers. It decouples the service logic of LCS Clients from the underlying network topology. Without a DS, each LCS Client would need to be statically configured with the addresses of all possible Location Servers, an impractical approach for large, evolving, or interconnected networks. The service is defined across multiple 3GPP specifications covering architecture, protocols (like Diameter-based LCS Application Protocol), and interworking, ensuring that both network-based and external application clients can reliably discover location service endpoints.

Purpose & Motivation

The Discovery Service was created to solve the fundamental bootstrapping problem in location service provisioning: 'How does a client find the right server?' In early LCS implementations, clients often used pre-configured or hard-coded addresses for GMLCs. This approach was inflexible, difficult to manage in large networks, and broke down completely in roaming scenarios where the client in the home network needed to find the GMLC in the visited network. The DS provides a dynamic, standardized lookup mechanism, which was essential for the commercial rollout of interoperable location-based services across multiple operator networks.

Its creation was motivated by the need for scalability and automation in LCS. As the number of LCS Clients (e.g., for emergency services, lawful intercept, fleet management, and consumer apps) grew, manual configuration became a major operational burden and a source of errors. The DS abstracts the network complexity, allowing new Location Servers to be added or old ones retired without requiring updates to every client. Furthermore, it enables advanced features like load balancing between servers and discovery based on the client's own identity or requested service level. By providing a centralized discovery point, it facilitates inter-PLMN location services, which are critical for emergency call routing (E911, eCall) and international roaming services, ensuring that a location request can be correctly routed to the network currently serving the target subscriber.

Key Features

• Provides addressing information (e.g., hostname, IP) of the appropriate Location Server (GMLC/LMF) for a target UE.
• Supports discovery based on various target identifiers including MSISDN, IMSI, and IP address.
• Enables inter-PLMN discovery through interaction with the LCS Roaming Exchange (LRX) or H-GMLC.
• May return server capabilities, such as supported positioning methods and LCS protocols.
• Decouples LCS Clients from the physical network topology of Location Servers.
• Uses standardized protocols, primarily based on Diameter for the LCS Application Protocol (LCS-AP).

Evolution Across Releases

Defining Specifications