Location Services

LoCation Services (LCS) on the MME and SGSN is a 3GPP standards-compliant feature that enables the system (MME or SGSN) to collect and use or share location (geographical position) information for connected UEs in support of a variety of location services.

Location Services - Feature Description

The Location Services (LCS) feature enables the EPC MME and the GPRS/UMTS SGSN to use the SLg (MME) or Lg (SGSN) interface which provides the mechanisms to support specialized mobile location services for operators, subscribers, and third party service providers. Use of this feature and the SLg/Lg interface is license controlled.

The location information is reported in standard geographical co-ordinates (longitude and latitude) together with the time-of-day and the estimated errors (uncertainty) of the location of the UE. For external use, the location information may be requested by and reported to a client application associated with the UE, or a client within or attached to the core network. For internal use, the location information can be utilized by the SGSN for functions such as location assisted handover or to support other features.

Location information is intended to be used for

  • location-based charging (e.g., home-location billing, roaming-location billing),
  • location-based services (e.g., lawful interception, emergency calls),
  • positioning services offered to the subscribers (e.g., mobile yellow pages, navigation applications on mobiles), and
  • by the operator for service provider services such as network planning and enhanced call routing.

How Location Services Works

The MME LCS responsibilities are to manage LCS positioning requests. The LCS functions of the MME are related to LCS co-ordination, location requests, and operation of the LCS services.

The operation begins with a LCS Client requesting location information for a UE from the LCS server. The LCS server will pass the request to the MME in the core network. The MME in the core network then:

  1. verifies that the LCS Client is authorized to request the location of the UE or subscriber;
  2. verifies that location services are supported by the UE;
  3. establishes whether it (the MME) is allowed to locate the UE or subscriber, for privacy or other reasons;
  4. requests the access network (via S1 interface) to provide location information for an identified UE, with indicated QoS;
  5. receives information about the location of the UE from the Access Network and forward it to the Client;

Architecture

The MME is accessible to the Gateway Mobile Location Center (GMLC) via the SLg interface.

The SGSN is accessible to the GMLC via the Lg interface.


Figure 1. LCS Architecture

The MME informs the HLR/HSS about a UE's location services capabilities for an EPC network.

Supported Functionality

The MME supports the following LCS functions:

  • Immediate Mobile-Terminating Location Requests (MT-LI) [TS 3GPP 23.271].
  • MT-LR procedures from the GMLC with client types of: Emergency Services, Value Added Services, PLMN Operator Services, and Lawful Intercept Services.
  • Network Induced (NI-LR) procedures for Emergency PDN Connect and Emergency Attach, and Inbound relocation with emergency PDN (through TAU or SRNS).
  • Circuit Switch Fallback (CSFB): When a UE is combined attached to the MME, and the CSFB registration is not for SMS-only services, the MME shall page UE on receipt of an SGs page with LCS Client identity.

Limitations

Currently, MME support is limited to:

  • A single location request at a time for the target UE. Concurrent location requests are not supported.
  • Location reporting granularity is at the E-UTRAN Cell Global Identifier (EGCI) level only.

Flows

Mobile Terminated Location Requests


Figure 2. 4G LCS - MT-LR Call Flow - Connected Mode
  1. The MME receives a Provide Location Request from the GMLC. The UE is in Connected mode.
  2. The MME sends Location Report Control message with request-type as 'Direct'.
  3. The eNodeB (ENB) sends the current location of the UE (ECGI) in the Location report message.
  4. The MME sends Provide Location Answer to GMLC with ECGI received in the location Report Message

Figure 3. 4G LCS - MT-LR Call Flow - Idle Mode
  1. The MME receives a Provide Location Request from the GMLC. The UE is in idle mode.
  2. The MME pages the UE.
  3. If the UE does not respond to the page, the MME responds with the last known location and sets the age of location report accordingly if the Location Type requested by the GMLC was “current or last known location”.
  4. If paging is successful, the UE responds with Service request/TAU request.
  5. The MME uses the ECGI in the S1 message and sends Provide Location Answer message to the GMLC.

Network Induced Location Requests


Figure 4. 4G LCS - NI-LR Call Flow
  1. The UE establishes Emergency bearers with MME. This could be a Emergency Attach or establishment of an Emergency PDN. Handover of an Emergency call from one MME to the other is also possible.
  2. If the MME is configured to support Location service for emergency calls, the latest ECGI is sent in the Subscriber Location Report message to the configured GMLC.
  3. The GMLC, on processing the Subscriber location report, sends the Subscriber location ACK. Note: A Negative ACK will not have any effect.

Standards Compliance

The Location Services feature complies with the following standards:

  • TS 3GPP 23.271, v10.4.0
  • TS 3GPP 23.272, v10.9.0
  • TS 3GPP 24.080, v10.0.0
  • TS 3GPP 24.171, v9.0.0
  • TS 3GPP 29.172, v10.1.0

Configuring Location Services (LCS)

This section provides a high-level series of steps and the associated configuration examples to configure Location Services on the MME.

The commands could be issued in a different order, but we recommend that you follow the outlined order for an initial LCS configuration. All listed configuration steps are mandatory unless otherwise indicated.

IMPORTANT:

For all the required configuration commands to be available and to implement the configuration, the MME must have loaded the license for the Lg interface.

  1. Create a location service configuration on the MME.
  2. Associate the location service with the appropriate Diameter endpoint.
  3. Associate the MME service with this location service.
  4. Associate the LTE Emergency Policy with this location service.
  5. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide.
  6. Verify the configuration for each component by following the instructions provided in the Verifying the Feature Configuration section.

Creating and Configuring a Location Service

A location service must be created within a context. Up to 16 separate location services can be created.

IMPORTANT:

The Origin host configured in the endpoint for SLg interface must match the origin host configured in the endpoint for S6a interface.

config
   context <context_name> -noconfirm
      location-service  <location_svc_name> -noconfirm
      associate
diameter endpoint <endpoint>
      end

Notes:

  • This series of commands creates a Location service and associates the service with a diameter endpoint.

Associate the MME Service with the Location Service

Once the location service is created and configured, the MME service must be associated with it. The steps below assume the MME service has already been created.

config
   context <context_name> -noconfirm
      mme-service  <mme_svc_name>
      associate
location-service <location_svc_name>
      end

Notes:

  • This series of commands associates an MME service with the new location service.

Associate the LTE Emergency Profile with the Location Service

Once the location service is created and configured, the LTE Emergency Profile must be associated with it. The steps below assume the LTE Emergency Profile has already been created.

This procedure enables the MME to provide location information of an emergency call to the GMLC.

config
   lte-policy
      lte-emergency-profile  <profile_name>
      associate
location-service <location_svc_name>
      end

Notes:

  • This series of commands associates the LTE Emergency Profile with the new location service.

Verifying the LCS Configuration

The following command displays configuration information for all Location services configured on the MME.

show location-service
service all

The following command displays the location service to which each MME service is associated.

show mme-service
all 

The following command displays the location service to which the specified LTE Emergency Profile is associated.

show lte-policy
lte-emergency-profile  profile_name 

The following command displays a list of all services configured on the system, including location services (listed as Type: lcs).

show services all 

Monitoring Location Services (LCS)

This section lists the bulk statistics and show commands that display operational statistics relating to Location services.

LCS Bulk Statistics

LCS service related bulk statistics are provided within the LCS schema.

Use the following command to display a list of all variables available within this schema:

show bulkstats variables
lcs 

For more information about these statistics, refer to the LCS Schema chapter of the Statistics and Counters Reference.

LCS Show Commands

The following command displays statistics for all LCS activity on the MME.

show location-service
statistics all

Use the following command to clear the LCS statistics for a specific Location service.

clear location-service
statistics service location_svc_name

The following command displays LCS statistics for a specific MME service.

show mme-service
statistics service mme-service mme_svc_name

Use the following command to clear MME service statistics for a specific MME service.

clear mme-service
statistics mme-service mme_svc_name