8 Information storage

3GPP43.073Release 17Stage 2Support of Localised Service Area (SoLSA)TS

8.1 Information managed per subscriber

8.1.1 Stored in the HLR

The following mandatory information shall be stored in the HLR for each service subscriber:

– a list of all the LSA Ids for the service subscriber;

– the priority for each LSA;

– the preferential access indicator for each LSA;

– the LSA only access indicator.

The following optional information may be stored in the HLR for each service subscriber:

– LSA only access indication text (text to be displayed when out of LSA).

The following optional information may also be stored for each subscribed LSA:

– LSA name (A text string describing area and/or service. For example "ETSI BUILDING");

– LSA indication for idle mode (flag to activate/deactivate LSA indication in idle mode);

– LSA indication for active mode (flag to activate/deactivate LSA indication in active mode);

– idle mode support (flag to activate/deactivate idle mode support in LSA);

– active mode support (flag to activate/deactivate active mode support in LSA).

The LSA Ids are defined in subclause 9.1.1.

A service subscriber shall not be provided with more than 20 LSAs per PLMN (including universal LSA’s).

8.1.2 Stored in the VLR

The following mandatory information, which is relevant in the VPLMN, shall be stored in the VLR for each service subscriber:

– a list of all the LSA Ids for the service subscriber;

– the priority for each LSA;

– the preferential access indicator for each LSA;

– the LSA only access indicator.

The following optional information may also be stored for each subscribed LSA:

– LSA indication for active mode (flag to activate/deactivate LSA indication in active mode);

– active mode support (flag to activate/deactivate active mode support in LSA).

This information shall be brought forward to the VLR at the same time as other subscriber information is copied form HLR. VLR entries shall be modified when corresponding HLR records are changed.

8.1.3 Stored in the SIM

The following mandatory information shall be stored in the SIM for each service subscriber:

– a list of all the LSA Ids for the service subscriber;

– the priority for each LSA;

– the LSA only access indicator.

The following optional information may be stored in the SIM for each service subscriber:

– LSA only access indication text (text to be displayed when out of LSA).

The following optional information may also be stored for each subscribed LSA:

– a list of all the cell identities for the subscribed LSA;

– LSA name (A text string describing area and / or service. For example "ETSI BUILDING");

– LSA indication for idle mode (flag to activate/deactivate LSA indication in idle mode);

– idle mode support (flag to activate/deactivate idle mode support in LSA);

The information shall be modified when corresponding HLR and BSS records are changed.

8.1.4 Stored in the SGSN

The following mandatory information, which is relevant in the VPLMN, shall be stored in the SGSN for each service subscriber:

– a list of all the LSA Ids for the service subscriber;

– the priority for each LSA;

– the preferential access indicator for each LSA;

– the LSA only access indicator.

The following optional information may also be stored for each subscribed LSA:

– LSA indication for active mode (flag to activate/deactivate LSA indication in active mode);

– active mode support (flag to activate/deactivate active mode support in LSA).

This information shall be brought forward to the SGSN at the same time as other subscriber information is copied form HLR. SGSN entries shall be modified when corresponding HLR records are changed.

8.2 Information managed per LSA

The LSA is defined as a list of cells inside the network. The cells shall be defined by their cell identification consisting of the Location Area Code and the Cell Identity as defined in 3GPP TS 48.008 and are therefore uniquely identified in the network.

8.2.1 Stored in the MSC

The information stored in the MSC (network option) is the network specific service configuration of each LSA defined by the network operator and relevant for the MSC.

The network specific configuration of each LSA may also include specific rules for e.g. the priority handling and the mapping between LSA information for the subscriber (VLR data) and the LSA information sent to BSS and when to notify MS about a service area change.

NOTE: For the handling of call establishment, it is out of scope of the present document to describe how the network shall perform e.g. mapping between LSA information for the subscriber (VLR data) and the LSA information sent to BSS. The network specific service configuration information shall only be seen as an example.

8.2.2 Stored in the BSS

The information stored in the BSS is the network specific service configuration of each LSA defined by the network operator and relevant for the BSS.

For each LSA relevant for the BSS in case of internal and external handover support, the LSA ID and the cells belonging to the LSA shall be stored. The BSS must also have knowledge about in which LSA cells that the exclusive access shall be indicated.

The network specific configuration of each LSA may also include rules for e.g. handover and resource allocation.