12 Information storage

03.713GPPFunctional descriptionLocation Services (LCS)Release 1999Stage 2TS

This section 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.

12.1 HLR

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

LCS Data in the HLR for an MS Subscriber

The IMSI is the primary key for LCS MS 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 MS subscription data includes a privacy exception list containing the privacy classes for which location of the target MS 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 03.11 for an explanation of the notation):

Table 4: 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 section 7 and to GSM 02.71.

Table 5: LCS data stored in the HLR privacy exception list for an MS Subscriber (or MS 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

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

O

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

C

– International E.164 address identifying a single LCS client or a single group of LCS clients that are permitted to locate this target MS

O

– Restriction on the GMLC. Possible values are:

– identified GMLCs only

– Any GMLC in the home country

C

– 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 Opeator Class

O

LCS client list: a list of one or more generic classes of LCS client that are allowed to locate the particular MS. 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 MS

LCS MS subscription data may include a mobile originating list containing the LCS mobile originating classes that an MS 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 GSM 03.11 for an explanation of the notation):

Table 6: 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 section 7 and to GSM 02.71.

Table 7: Data stored in the HLR for the LCS Mobile Originating List for an MS (or MS 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 items may be stored in the MS subscription profile in the HLR to support LCS:

Table 8: 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 MS privacy exception list) to making call unrelated location requests.

LCS data in the HLR for a Type A LMU with an NSS based SMLC

The IMSI is the primary key to data for a Type A LMU stored in the HLR when the SMLC associated with the LMU is NSS based. Any subscription data that is applicable to an MS subscriber may be held by the HLR for a Type A LMU, since the LMU is treated by the HLR similarly to an MS subscriber. However, a HLR will normally restrict LMU subscription data to just the IMSI, MSISDN, SMS-PP MT (if assigned) and barring of all incoming and possibly outgoing calls. Use of MSPs is also unnecessary for an LMU. A Type A LMU has no HLR subscription when the SMLC associated with the LMU is BSS-based.

An HLR also needs to hold the following additional permanent data for a Type A LMU.

Table 9: Additional permanent data in the HLR for a Type A LMU

Additional LMU Data in HLR

Status

Description

LMU Indicator

M

Distinguishes a Type A LMU from a normal MS Subscriber

12.2 VLR

The VLR contains the same LCS permanent data for each registered MS subscriber and each Type A LMU when the SMLC associated with the LMU is NSS-based, as does the HLR. This data is downloaded to the VLR as part of the location update procedure between the VLR and HLR for either an MS subscriber or LMU. The VLR has no data for Type A LMUs when the SMLC associated with the LMU is BSS-based.

12.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.

Table10: 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 this specification

Authentication data

M

Data employed to authenticate the identity of an LCS client – details are outside the scope of this specification

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 MS 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 MS 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 Coordinate System

O

Definition of the coordinate system(s) in which a location estimate shall be provided – details are outside the scope of this specification

Access Barring List(s)

O

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

12.4 SMLC

Common Data

The following table holds permanent BTS data:

Table 11: Permanent SMLC Data for a BTS

Permanent BTS Data Item

Status

Description

BTS position

M

BTS position (latitude/longitude) of the Serving BTS

CGI

M

Cell global identity.

BSIC

M

Base station identity code.

BCCH

M

Frequency of the broadcast carrier.

The SMLC holds data for its associated LMUs. The main key to LMU data in the SMLC is the IMSI for a Type A LMU and a cell site identifier for a Type B LMU. LMU data provides the location capabilities of the LMU (e.g. which location and assistance measurements are supported). The following permanent data shall be administered for any LMU:

Table 12: Permanent SMLC Data for an LMU

Permanent LMU Data Item

Status

Description

Type of LMU

M

Indicates if LMU is Type A or Type B

IMSI

C

Main key to data for a Type A LMU. Not applicable to a Type B LMU

LAC + CI

C

Cell site identifier to address a Type B LMU. Not applicable to a Type A LMU.

Signaling Access

M

Information regarding signaling access to the LMU including the following:

– address of default serving BSC and/or serving MSC (a BSS based SMLC uses a serving BSC while an NSS based SMLC uses a serving MSC)

– SS7 link set to serving BSC or serving MSC (or to an intermediate STP)

Serving Cell

M

Identity of the cell in which the LMU is physically located

Geographic location

C

Latitude/longitude coordinates

Storage of coordinates is mandatory for TOA or E-OTD if an LMU is not co-located with a BTS

Position measurement functions

O

List of supported position measurements

For each type of position measurement, a list of associated capabilities – details are outside the scope of this specification

Assistance measurement functions

O

List of supported assistance measurements

For each type of assistance measurement, a list of associated capabilities – details are outside the scope of this specification

Diagnostic functions

O

List of supported diagnostic functions – details are outside the scope of this specification

The SMLC also holds the following temporary data for each LMU for which there has been any previous signalling interaction.

Table 13: Temporary SMLC Data for an LMU

Temporary LMU Data Item

Status

Description

Serving MSC

M

Identity of the current or most recent serving MSC (not applicable to a BSS based SMLC)

– SS7 signaling point code

Position Measurements

O

Ongoing and scheduled position measurements ordered in the LMU by the SMLC – details are outside the scope of this specification

Assistance Measurements

O

Ongoing and scheduled assistance measurements ordered by the SMLC – details are outside the scope of this specification

O&M Activities

O

Ongoing and scheduled O&M activities ordered in the LMU by the SMLC – details are outside the scope of this specification

TOA Data

The following data are specific to TOA and shall be administered in the SMLC:

Table 14: Permanent SMLC Data for an LMU

Permanent LMU Data Item

Status

Description

Number of Measurement Devices (Note 1)

M

Number of measurement devices contained in the LMU.

Number of Simultaneous Measurements (Note 2)

M

LMU total measurement capacity.

Data items for each measurement device:

Beamwidth

M

Azimuthal coverage in degrees for each LMU measurement device.

Orientation

M

Main beam pointing angle counter-clockwise looking down with respect to North in degrees for each LMU measurement device.

Gain

O

LMU measurement device antenna gain at foresight in dB.

Number of Simultaneous Measurements

O

Maximum measurement capacity in a single LMU measurement device. (Assume dedicated receivers if this field is not specified.)

NOTE 1: The term "measurement device" is used both to indicate the LMU sector and to avoid confusion with the BTS sectors when LMU sectors are not coincident with BTS sectors.

NOTE 2: A "measurement" refers to the time interval required for an entire TOA measurement. If any portion of the interval overlaps, it is considered simultaneous.

An LMU contains no mandatory data regarding its associated SMLC. An LMU shall contain permanent data regarding its measurement and O&M capabilities and may contain pre-administered data regarding location assistance measurements and O&M activities that the LMU is to perform without the need for any command from the SMLC. The content of such location measurement and O&M related data is outside the scope of this specification.

12.5 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 GSM 03.07.