9 Information storage

23.1713GPPFunctional descriptionLocation Services (LCS)Release 1999Stage 2 (UMTS)TS

This clause describes information storage structures that are mandatory (M), conditional (C) or optional (O) for LCS, and the recovery and restoration procedures needed to maintain service if inconsistencies in databases occur and for lost or invalid database information. Information storage in SRNC and LMU is specified in UTRAN Stage 2, reference [1].

9.1 HLR

The HLR holds LCS data for both UE subscribers and LMUs.

9.1.1 LCS Data in the HLR for an UE Subscriber

The IMSI is the primary key for LCS UE subscription data in the HLR. This subscription data may be stored in a Multiple Subscriber Profile (MSP), with the HLR able to hold a number of MSPs per IMSI.

LCS UE subscription data includes a privacy exception list containing the privacy classes for which location of the target UE is permitted. Each privacy class is treated as a distinct supplementary service with its own supplementary service code. The following logical states are applicable to each privacy class (refer to GSM 23.011 for an explanation of the notation):

Table 9.1: Logical States for each LCS Privacy Class

Provisioning State

Registration State

Activation State

HLR Induction State

(Not Provisioned,

Not Applicable,

Not Active,

Not Induced)

(Provisioned,

Not Applicable,

Active and Operative,

Not Induced)

For each LCS privacy class, the HLR shall store the logical state of the class on a per-subscriber (or per subscriber MSP) basis. In addition, the permanent data indicated below shall be stored on a per subscriber (or per subscriber MSP) basis when the logical provisioning state of the associated LCS privacy class is "provisioned". For the meaning of each LCS privacy class, refer to clause 8 and to TS 22.071.

Table 9.2: LCS data stored in the HLR privacy exception list for an UE Subscriber (or UE Subscriber MSP)

LCS Privacy Class

Status

Additional HLR Data when Class is provisioned

Universal Class

No additional data

Call Related Class

M

Indication of one of the following mutually exclusive options:

  • Location allowed without notification (default case)
  • Location allowed with notification
  • Location with notification and privacy verification; location allowed if no response
  • Location with notification and privacy verification; location restricted if no response

Call Unrelated Class

M

O

C

O

C

Indication of one of the following mutually exclusive options for any LCS client not in the external LCS client list:

  • Location not allowed (default case)
  • Location allowed with notification
  • Location with notification and privacy verification; location allowed if no response
  • Location with notification and privacy verification; location restricted if no response

External LCS client list: a list of zero or more LCS clients, with the following data stored for each LCS client in the list:

  • International E.164 address identifying a single LCS client or a single group of LCS clients that are permitted to locate this target UE
  • Restriction on the GMLC. Possible values are:
  • identified GMLCs only
  • Any GMLC in the home country
  • Indication of one of the following mutually exclusive options:
  • Location allowed without notification (default case)
  • Location allowed with notification
  • Location with notification and privacy verification; location allowed if no response
  • Location with notification and privacy verification; location restricted if no response

PLMN Operator Class

O

LCS client list: a list of one or more generic classes of LCS client that are allowed to locate the particular UE. The following classes are distinguished:

  • LCS client broadcasting location related information
  • O&M LCS client in the HPLMN
  • O&M LCS client in the VPLMN
  • LCS client recording anonymous location information
  • LCS Client supporting a bearer service, teleservice or supplementary service to the target UE

LCS UE subscription data may include a mobile originating list containing the LCS mobile originating classes that an UE is permitted to request. Each LCS mobile originating class is treated as a distinct supplementary service with its own supplementary service code. The following logical states are applicable to each mobile originating class (refer to TS23.011 for an explanation of the notation):

Table 9.3: Logical States for each Mobile Originating LCS Class

Provisioning State

Registration State

Activation State

HLR Induction State

(Not Provisioned,

Not Applicable,

Not Active,

Not Induced)

(Provisioned,

Not Applicable,

Active and Operative,

Not Induced)

For each LCS Mobile Originating class, the HLR shall store the logical state of the class on a per-subscriber (or per subscriber MSP) basis. In this version of LCS, there is no additional permanent data in the HLR. The table below shows the defined mobile originating classes. For the meaning of each LCS mobile originating class, refer to clause 8 and to GSM 22.071.

Table 9.4: Data stored in the HLR for the LCS Mobile Originating List for an UE (or UE Subscriber MSP)

LCS Mobile Originating Class

Status

Additional HLR Data when Class is provisioned

Basic Self Location

No additional data

Autonomous Self Location

No additional data

Transfer to Third Party

No additional data

In addition to the privacy exception list, the following other data iteUE may be stored in the UE subscription profile in the HLR to support LCS:

Table 9.5: Temporary LCS data in the HLR

Other Data in the HLR

Status

Description

GMLC List

O

List of one or more E.164 addresses of the GMLCs from which a location request for an MT-LR is allowed, The addresses are only relevant to an LCS client that is restricted (in the UE privacy exception list) to making call unrelated location requests.

9.2 VLR

The VLR contains the same LCS permanent data for each registered UE subscriber, as does the HLR. This data is downloaded to the VLR as part of the location update procedure between the VLR and HLR for an UE subscriber.

9.3 GMLC

The GMLC holds data for a set of external LCS clients that may make call related or non-call related MT-LR requests to this GMLC. The permanent data administered for each LCS client is as follows.

Table 9.6: GMLC Permanent Data for a LCS Client

LCS Client data in GMLC

Status

Description

LCS Client Type

M

Identifies the type LCS client from among the following:

  • Emergency Services
  • Value Added Services
  • PLMN Operator Services
  • – Lawful Intercept Services

External identity

M

A list of one or more identifiers used to identify an external LCS client when making an MT-LR – the nature and content of the identifier(s) is outside the scope of the present document

Authentication data

M

Data employed to authenticate the identity of an LCS client – details are outside the scope of the present document

Call related identity

O

A list of one or more international E.164 addresses to identify the client for a call related MT-LR.

In case the LCS client was reached via IN or abbreviated number routing (e.g. toll free number or emergency call routing), the E.164 number(s) stored in the GMLC shall be the number(s) that the UE has to dial to reach the LCS Client. In these cases the E.164 number is not to be in international format. The country in which the national specific number(s) is (are) applicable is (are) also stored (or implied) in this case.

Each call related identity may be associated with a specific external identity

Non-call related identity

O

A list of one ore more international E.164 addresses to identify the client for a non-call related MT-LR.

Each non-call related identity may be associated with a specific external identity

Override capability

O

Indication of whether the LCS client possesses the override capability (not applicable to a value added client)

Authorized UE List

O

A list of MSISDNs or groups of MSISDN for which the LCS client may issue a non-call related MT-LR. Separate lists of MSISDNs and groups of MSISDN may be associated with each distinct external or non-call related client identity.

Priority

M

The priority of the LCS client – to be treated as either the default priority when priority is not negotiated between the LCS server and client or the highest allowed priority when priority is negotiated

QoS parameters

M

The default QoS requirements for the LCS client, comprising:

  • Accuracy
  • Response time

Separate default QoS parameters may be maintained for each distinct LCS client identity (external, non-call related, call related)

Allowed LCS Request Types

M

Indicates which of the following are allowed:

  • Non-call related MT-LR
  • Call related MT-LR
  • Specification or negotiation of priority
  • Specification or negotiation of QoS parameters
  • Request of current location
  • Request of current or last known location

Local Co-ordinate System

O

Definition of the co-ordinate system(s) in which a location estimate shall be provided – details are outside the scope of the present document

Access Barring List(s)

O

List(s) of MSISDNs or groups of MSISDN for which a location request is barred

9.4 Recovery and Restoration Procedures

The LCS recovery and restoration procedures allow temporary data to be recovered or reinitialized following loss or corruption of data, such that normal LCS service is rapidly restored and inconsistency between the data held by different LCS network elements is removed. For a full description, refer to TS 23.007.