8 Mobility services

29.0023GPPMobile Application Part (MAP) specificationRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.1 Location management services

8.1.1 Void

8.1.1.1 Void

8.1.1.2 Void

8.1.1.3 Void

8.1.2 MAP_UPDATE_LOCATION service

8.1.2.1 Definition

This service is used by the VLR to update the location information stored in the HLR.

This service is also used by an IWF that registers an MME as MSC for MT-SMS.

The MAP_UPDATE_LOCATION service is a confirmed service using the service primitives given in table 8.1/2.

8.1.2.2 Service primitives

Table 8.1/2: MAP_UPDATE_LOCATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
MSC Address	M	M(=)
VLR number	M	M(=)
LMSI	U	C(=)
Supported CAMEL Phases	C	C(=)
SoLSA Support Indicator	C	C(=)
IST Support Indicator	C	C(=)
Super-Charger Supported in Serving Network Entity	C	C(=)
Long FTN Supported	C	C(=)
Supported LCS Capability Sets	C	C(=)
Offered CAMEL 4 CSIs	C	C(=)
Inform Previous Network Entity	C	C(=)
CS LCS Not Supported by UE	C	C(=)
V-GMLC Address	U	C(=)
IMEISV	C	C(=)
Skip Subscriber Data Update	U	C(=)
Supported RAT Types Indicator	U	C(=)
Paging Area	U	C(=)
Restoration Indicator	U	C(=)
MTRF Supported	U	C(=)
Equivalent PLMN List	C	C(=)
MSISDN-less Operation Supported	C	C(=)
MME-Diameter-Address-For MT-SMS	C	C(=)
Reset-IDs Supported	C	C(=)
ADD Capability			U	C(=)
Paging Area Capability			U	C(=)
HLR number			C	C(=)
User error			C	C(=)
Provider error				O

8.1.2.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

MSC Address

See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each incoming call set-up attempt the MSRN will be requested from the VLR.

VLR number

See definition in clause 7.6.2.

LMSI

See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR to support the LMSI handling procedures.

Supported CAMEL Phases

This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from phase 1 is supported. Otherwise may be absent.

HLR number

See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating.

SoLSA Support Indicator

This parameter is used by the VLR to indicate to the HLR in the Update Location indication that SoLSA is supported. If this parameter is not included in the Update Location indication and the Subscriber is marked as only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the VLR that roaming is not allowed to that Subscriber in the VLR.

This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted.

IST Support Indicator

This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Update Location indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available.

This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Update Location indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.

Long FTN Supported

This parameter indicates that the VLR supports Long Forwarded-to Numbers.

Super-Charger Supported in Serving Network Entity

This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required.

If this parameter is absent then the VLR does not support the Super-Charger functionality.

Supported LCS Capability Sets

This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no capability set is marked as supported then the VLR does not support LCS at all.

If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 version.

Offered CAMEL 4 CSIs

This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D).

Inform Previous Network Entity

This parameter is used by the VLR to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used if Super-Charger is supported in the network and either the serving network entity has not been able to inform the previous network entity that MS has moved (i.e. if it has not sent Send Identification to the previous serving entity) or the MTRF Supported flag is set in the MAP_UPDATE LOCATION request.

CS LCS Not Supported by UE

See definition in clause 7.6.11.

V-GMLC address

See definition in clause 7.6.2.

IMEISV

For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.012. IMEISV shall be present if ADD function is supported and a new IMEISV is to be notified to the HLR (The functional requirements for the presence of IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4).

Skip Subscriber Data Update

The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR about change of IMEISV or Paging Area. The parameter is used to optimise signalling load during Location Update procedure.

Supported RAT Types Indicator

This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the MSC/VLR (see clause 7.6.3)

Paging Area

This parameter indicates, if present, the paging area where the MS is currently located (see clause 7.6.5.18)

Restoration Indicator

This parameter indicates, if present, that the HLR shall send in the MAP-INSERT-SUBSCRIBER-DATA the MME Name if the subscriber is registered to EPS, or the SGSN Number if available and if the subscriber is registered to GPRS. The VLR may set this indicator during a CSFB mobile originated call if the VLR performs an implicit location update (see 3GPP TS 23.272 [143]).

MTRF Supported

See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

Equivalent PLMN List

This parameter indicates the equivalent PLMN list of which the VLR requests the corresponding CSG Subscription data.

MSISDN-less Operation Supported

See clause 3.6.1.5 of 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

MME-Diameter-Address-For-MT-SMS

This parameter may be sent by an IWF that registers an MME for MT-SMS. The MME-Diameter-Address-For-MT-SMS may be stored in the HLR and may be sent in SMS interrogation responses to SMS-GMSCs.

Reset-IDs Supported

This parameter indicates, if present, the support of Reset-IDs by the MSC.

ADD Capability

This parameter indicates, if present, the support of ADD function by the HLR.

Paging Area Capability

This parameter indicates, if present, the support of Paging Area function by the HLR. The HLR shall report the same capability for all subscribers.

User error

In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in clause 7.6.1 may be used, depending on the nature of the fault:

– unknown subscriber;

– roaming not allowed;

This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the VLR number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed", "Supported RAT Types Not Allowed" or "Operator Determined Barring". If no qualification is received (HLR with MAP Version 1), "PLMN Not Allowed" is taken as default.

This cause shall be used when the HLR rejects a MAP Update Location request received for an MSISDN-less subscription from a VLR not supporting MSISDN-less operation (see clause 3.6.1.5 of 3GPP TS 23.012 [23]).

– system failure;

– unexpected data value.

Provider error

For definition of provider errors see clause 7.6.1.

8.1.3 MAP_CANCEL_LOCATION service

8.1.3.1 Definition

This service is used between HLR and VLR to delete a subscriber record from the VLR. It may be invoked automatically when an MS moves from one VLR area to another, to remove the subscriber record from the old VLR, or by the HLR operator to enforce a location updating from the VLR to the HLR, e.g. on withdrawal of a subscription.

Also this service is used between HLR and SGSN to delete a subscriber record from the SGSN. It may be invoked automatically when an MS moves from one SGSN area to another, to remove the subscriber record from the old SGSN, or by the HLR operator to enforce a location updating from the SGSN to the HLR. This service is also used to request the SGSN to indicate to the MS to initiate an immediate re-attach procedure.

In an EPS this service is used between HSS and IWF and between IWF and IWF to delete the subscriber record from the MME or SGSN or to release bearer resources without deleting the subscriber record. This service is also used to request the MME or SGSN to indicate to the UE to initiate an immediate re-attach procedure.

The MAP_CANCEL_LOCATION service is a confirmed service using the primitives defined in table 8.1/3.

8.1.3.2 Service primitives

Table 8.1/3: MAP_CANCEL_LOCATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
LMSI	C	C(=)
Cancellation Type	C	C(=)
MTRF Supported And Authorized	U	C(=)
MTRF Supported And Not Authorized	U	C(=)
New MSC Number	U	C(=)
New VLR Number	U	C(=)
New LMSI	U	C(=)
Reattach Required	U	C(=)
User error			C	C(=)
Provider error				O

8.1.3.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

LMSI

See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable between SGSN and HLR.

Value 0000 0000 can be used to indicate that the LMSI is not in use.

Cancellation Type

See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the SGSN or IWF. The parameter may also be sent during an inter-VLR location update If the VLR receives this parameter and does not understand it the VLR shall ignore it and should by default assume an Update procedure. If the SGSN receives this parameter indicating initial attach procedure, the SGSN shall do as specified in 3GPP TS 23.060 [104], and shall not delete the subscription data.

MTRF Supported And Authorized

See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

MTRF Supported And Not Authorized

See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

New MSC Number

This parameter refers to the E.164 address of the new VMSC. The use and conditions of presence of this parameter are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This parameter shall be present if the MTRF Supported And Authorized flag is present.

New VLR Number

This parameter contains the new VLR Number. See definition in clause 7.6.2. The use and conditions of presence of this parameter are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This parameter shall be present if the MTRF Supported And Authorized flag is present.

New LMSI

See definition in clause 7.6.2 for LMSI. This parameter shall be present if the MTRF Supported And Authorized flag is present and the HLR has received the LMSI in Update Location from the new VLR.

Reattach Required

When present and when the Cancellation Type indicates a subscription withdraw, this parameter indicates that the MME (informed via the IWF) or the SGSN shall delete the subscription data and request the UE or MS to initiate an immediate re-attach procedure as described in 3GPP TS 23.401 [145] and in 3GPP TS 23.060 [12].

User error

If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN or IWF. One of the following error causes defined in clause 7.6.1 shall be used:

– unexpected data value;

– data missing.

Provider error

For definition of provider errors see clause 7.6.1.

8.1.4 MAP_SEND_IDENTIFICATION service

8.1.4.1 Definition

The MAP_SEND_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and authentication data for a subscriber registering afresh in that VLR.

It may also be used to send the MSC number from a VLR to a previous VLR.

The MAP_SEND_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4.

8.1.4.2 Service primitives

Table 8.1/4: MAP_SEND_IDENTIFICATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
TMSI	M	M(=)
Number of requested vectors	M	M(=)
Segmentation prohibited indicator	C	C(=)
MSC Number	U	C(=)
Previous Location Area Id	U	C(=)
Hop Counter	U	C (=)
MTRF Supported	U	C(=)
VLR Number	U	C(=)
New LMSI	U	C(=)
IMSI			C	C(=)
Authentication set			U	C(=)
Current Security Context			U	C(=)
MT call pending flag			U	C(=)
Last used LTE PLMN ID			U	C(=)
User error			C	C(=)
Provider error				O

8.1.4.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

TMSI

See definition in clause 7.6.2.

If multiple service requests are present in a dialogue then this parameter shall be present in every service request.

Number of requested vectors

A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not return more vectors than indicated by this parameter.

This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other than the first one

Segmentation prohibited indicator

This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level.

This parameter may be present only in the first request of the dialogue.

IMSI

See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds.

If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in any service response other than the first one

MSC Number

This is the ISDN number assigned to the MSC currently serving the MS. This parameter shall be present if the MTRF Supported flag is present.

Previous Location Area Id

See definition in clause 7.6.2. Together with the TMSI the Previous Location Area Id can be used to derive the IMSI.

Authentication set

See definition in clause 7.6.7. If the service succeeds a list of up to five authentication sets is returned, if there are any available.

Current Security Context

See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be returned.

This parameter shall not be included if the Key Status associated to the current security context indicates this is a new keyset that has not been used yet. If this parameter is present in the message, the new VLR shall consider that the keyset has already been used (i.e. the key status is "old").

MT call pending flag

This flag indicates by its presence that there is a Mobile Terminating call pending in the old MSC/VLR. See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence.

Hop Counter

For the use of this parameter see 3GPP TS 23.012 [23].

MTRF Supported

See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence.

VLR Number

This is the ISDN number assigned to the VLR currently serving the MS. See definition in clause 7.6.2. The use and conditions of presence of this parameter are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23]. This parameter shall be present if the MTRF Supported flag is present.

New LMSI

See definition in clause 7.6.2 for LMSI. This parameter may be present if the MTRF Supported flag is present.

Last used LTE PLMN ID

See 3GPP TS 23.272 [143] for the use of this parameter and the conditions for its presence.

User error

This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, depending on the nature of the fault:

– unidentified subscriber.

Provider error

For definition of provider errors see clause 7.6.1.

8.1.5 Void

8.1.5.1 Void

8.1.5.2 Void

8.1.5.3 Void

8.1.6 MAP_PURGE_MS service

8.1.6.1 Definition

This service is used between the VLR and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated call or a mobile terminated short message will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This service shall not be used if both the VLR and HLR support the Super-Charger functionality.

Also this service is used between the SGSN and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated short message or a network requested PDP-context activation will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This service shall not be used if both the SGSN and HLR support the Super-Charger functionality.

In an EPS this service is used between IWF and IWF and between IWF and HSS.

The MAP_PURGE_MS service is a confirmed service using the primitives defined in table 8.1/6.

8.1.6.2 Service primitives

Table 8.1/6: MAP_PURGE_MS

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
VLR number	C	C(=)
Freeze TMSI			C	C(=)
Freeze P-TMSI			C	C(=)
Freeze M-TMSI			C	C(=)
SGSN number	C	C(=)
Last known location	C	C(=)
User error			C	C(=)
Provider error				O

8.1.6.3 Parameter definitions and use

Invoke ID

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

VLR number

Shall be present if the sender is VLR. See definition in clause 7.6.2.

SGSN number

Shall be present if the sender is SGSN. See definition in clause 7.6.2.

In an EPS, this parameter may contain the IWF number.

Freeze TMSI

This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR number matches the stored VLR number.

Freeze P-TMSI

This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received SGSN number matches the stored SGSN number.

Freeze M-TMSI

This parameter is sent to the IWF to indicate that the M-TMSI has to be frozen. It shall be present if the received node number matches the stored IWF number.

Last known location

This parameter contains the last known location of the purged UE.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Data Missing;

– Unexpected Data Value;

– Unknown Subscriber.

Provider error

See definition of provider errors in clause 7.6.1.

8.1.7 MAP_UPDATE_GPRS_LOCATION service

8.1.7.1 Definition

This service is used by the SGSN to update the location information stored in the HLR.

In an EPS, this service is used between IWF and IWF and between IWF and HSS.

The MAP_UPDATE_GPRS_LOCATION service is a confirmed service using the service primitives given in table 8.1/7.

8.1.7.2 Service primitives

Table 8.1/7: MAP_UPDATE_GPRS_LOCATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
SGSN number	M	M(=)
SGSN address	M	M(=)
Supported CAMEL Phases	C	C(=)
SoLSA Support Indicator	C	C(=)
Super-Charger Supported in Serving Network Entity	C	C(=)
GPRS enhancements support indicator	C	C(=)
Supported LCS Capability Sets	C	C(=)
Offered CAMEL 4 CSIs	C	C(=)
Inform Previous Network Entity	C	C(=)
PS LCS Not Supported by UE	C	C(=)
V-GMLC Address	U	C(=)
Call barring support indicator	C	C(=)
IMEISV	C	C(=)
Skip Subscriber Data Update	U	C(=)
Supported RAT Types Indicator	U	C(=)
EPS Info	C	C(=)
Serving Node Type Indicator	C	C(=)
Supported Features	U	C(=)
Used RAT Type	U	C(=)
GPRS Subscription Data not needed Indicator	C	C(=)
EPS Subscription Data Not Needed Indicator	C	C(=)
Node-Type-Indicator	U	C(=)
Area Restricted Indicator	C	C(=)
UE Reachable Indicator	C	C(=)
T-ADS Data Retrieval Support Indicator	C	C(=)
Homogeneous Support Of IMS Voice Over PS Sessions	C	C(=)
Update of Homogeneous Support Of IMS Voice Over PS Sessions	C	C(=)
UE SRVCC Capability	C	C(=)
Equivalent PLMN List	C	C(=)
MME Number for MT SMS	C	C(=)
SMS-Only	C	C(=)
SMS Register Request	C	C(=)
Removal of MME Registration for SMS	C	C(=)
MSISDN-less Operation Supported	C	C(=)
SGSN Name	C	C(=)
SGSN Realm	C	C(=)
Lgd Support Indicator	C	C(=)
Adjacent-PLMNs	C	C(=)
Reset-IDs Supported	C	C(=)
ADD Capability			U	C(=)
SGSN-MME Separation Support Indicator			C	C(=)
HLR number			C	C(=)
MME Registered for SMS			C	C(=)
User error			C	C(=)
Provider error				O

8.1.7.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

SGSN number

See definition in clause 7.6.2.

In an EPS, this parameter is populated with an IWF number if received from an IWF.

SGSN address

See definition in clause 7.6.2.

In an EPS, this parameter is populated with an IWF address if received from an IWF.

Supported CAMEL Phases

This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or greater.

SoLSA Support Indicator

This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that SoLSA is supported. If this parameter is not included in the Update GPRS Location indication and the Subscriber is marked as only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the SGSN that roaming is not allowed to that Subscriber in the SGSN.

This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted.

Super-Charger Supported in Serving Network Entity

This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required.

If this parameter is absent then the SGSN does not support the Super-Charger functionality.

GPRS enhancements support indicator

This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that GPRS enhancements are supported. If this parameter is included in the Update GPRS Location indication the HLR may send the extension QoS parameter in the PDP contexts to the SGSN. The HLR may send the extension-2 QoS, the extension-3 QoS and the extension-4 QoS parameters with the extension QoS parameter.

HLR number

See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating.

Supported LCS Capability Sets

This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no capability set is marked as supported then the SGSN does not support LCS at all.

The SGSN is not allowed to indicate support for LCS capability set 1.

If this parameter is absent then the SGSN does not support LCS at all.

Offered CAMEL 4 CSIs

This parameter indicates the CAMEL phase 4 CSIs offered in the SGSN (see clause 7.6.3.36D).

Inform Previous Network Entity

This parameter is used by the SGSN to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the network and the serving network entity has not been able to inform the previous network entity that MS has moved, that is if it has not sent SGSN Context Request to the previous serving entity.

PS LCS Not Supported by UE

See definition in clause 7.6.11.

V-GMLC address

See definition in clause 7.6.2.

Call Barring support indicator

See definition in clause 7.6.3.92.

IMEISV

For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.060. IMEISV shall be present if ADD function is supported and the IMEISV is new in SGSN (The functional requirements for the presence of IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4).

Skip Subscriber Data Update

The presence of the parameter is optional and if present it indicates that subscriber data download during the updateGprsLocation procedure may be skipped by the HLR e.g. because the service is solely used to inform the HLR about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure.

Supported RAT Types Indicator

This parameter indicates, if present, which access technologies (e.g. GERAN and/or UTRAN and/or E-UTRAN) are served by the SGSN or MME (see clause 7.6.3)

EPS Info

This parameter may indicate that the MME or SGSN has selected a new PDN GW for an APN. If so, the HSS shall skip subscriber data update (insert subscriber data) and only note the new PDN GW.

Otherwise this parameter may indicate the appropriate instruction to be performed by the HSS which is one or more of

a) Update Location; i.e. send CancelLocation to the old MME and replace the stored MME id (if Serving Node Type Indicator is present and the stored MME id is different from the received MME id), or send CancelLocation to the old SGSN and replace the stored SGSN id (if Serving Node Type Indicator is absent and the stored SGSN id is different from the received SGSN id);

b) Cancel SGSN; i.e. send CancelLocation to the SGSN and delete the stored SGSN id.

c) Initial Attach; i.e. send CancelLocation to the MME (if Serving Node Type Indicator is absent) or to the SGSN (if Serving Node Type Indicator is present) with cancellation type set to "initial attach procedure"

Serving Node Type Indicator

This parameter indicates by its presence that the subscriber’s serving node is an MME (which is either stand alone or combined with an SGSN) and it indicates by its absence that the subscriber’s serving node is an SGSN (which is either stand alone or combined with an MME).

Supported Features

This parameter shall be used by an IWF to forward feature support indications as received from the MME or SGSN via S6a/S6d. It shall also be used by the SGSN to indicate support of the Dedicated Core Network functionality to the HLR.

Used RAT Type

This parameter may indicate the RAT type currently used by the serving node.

GPRS Subscription Data not needed Indicator

This parameter indicates by its presence that the SGSN (or MME/IWF) does not request GPRS Subscription Data in addition to EPS Subscription Data.

EPS Subscription Data Not Needed Indicator

This parameter indicates by its presence that the SGSN does not request EPS Subscription Data in addition to GPRS Subscription Data.

NOTE: The indicator is only applicable to an SGSN which only supports Gn and Gp interfaces and does not support S4 interface.

Node-Type Indicator

This parameter indicates by its presence that the requesting node is a combined MME/SGSN. Absence of this Indicator indicates that the requesting node is a single MME or SGSN.

When Node-Type Indicator is absent and Serving Node Type Indicator is present, the HSS may skip checking SMS/LCS supported features and skip the download of SMS/LCS-related subscription data to a standalone MME.

Area Restricted Indicator

This parameter indicates by its presence that the network node area is restricted due to regional subscription. This parameter is used by the IWF only.

UE-Reachable Indicator

This parameter indicates by its presence that the UE is reachable.

NOTE: In general any UpdateGPRS-Location request message (with or without UE-Reachable Indicator) implicitly conveys the information that the UE is now reachable.

This explicit indicator shall be set only when UpdateGPRS-Location is used for the only and no other purpose than indicating UE reachability. The HLR shall skip subscriber data downloading and any mobility management functionality other than reporting the UE’s reachability to relevant core network entities.

T-ADS Data Retrieval Support Indicator

This parameter indicates by its presence that the SGSN supports retrieval of T-ADS data with the Provide-Subscriber-Info service.

Homogeneous Support Of IMS Voice Over PS Sessions

This parameter when present indicates that IMS voice over PS sessions is homogeneously supported in the complete SGSN area or that IMS voice over PS sessions is homogeneously not supported in the complete SGSN area.

Update of Homogeneous Support Of IMS Voice Over PS Sessions

This parameter when present indicates that Homogeneous Support of IMS Voice Over PS Sessions is updated. If the Homogeneous Support of IMS Voice Over PS Session is not present, the value of the Homogeneous Support of IMS Voice Over PS Sessions shall be updated as unknown to the serving node.

UE SRVCC Capability

See definition in clause 7.6.3.99.

Equivalent PLMN List

This parameter indicates the equivalent PLMN list of which the MME/SGSN requests the corresponding CSG Subscription data.

MME Number for MT SMS

This parameter contains the ISDN number of the MME allocated for MT SMS (see 3GPP TS 23.003 [17]). It is present when the MME requests to be registered for SMS.

SMS-Only

This parameter indicates to the HSS that the UE needs only PS domain services and SMS services.

SMS Register Request

This parameter indicates to the HSS that if the MME (via IWF) needs to be registered for SMS, prefers not to be registered for SMS or has no preference to be registered for SMS, see 3GPP TS 23.272 [143].

This parameter indicates to the HSS that if the SGSN needs to be registered for SMS, prefers not to be registered for SMS or has no preference to be registered for SMS, see 3GPP TS 23.060 [104].

Removal of MME Registration for SMS

This parameter indicates by its presence that the MME requests to remove its registration for SMS.

MSISDN-less Operation Supported

This parameter indicates by its presence that the SGSN supports MSISDN-less operation (see clause 5.3.17 of 3GPP TS 23.060 [23]). An SGSN which supports MSISDN-less operation shall set this parameter.

SGSN Name

See definition in clause 7.6.2. This parameter is provided in a request when the serving node is an SGSN and the SGSN supports Lgd interface for LCS and/or Gdd interface for SMS.

SGSN Realm

See definition in clause 7.6.2. This parameter is provided in a request when the serving node is an SGSN and the SGSN supports Lgd interface for LCS and/or Gdd interface for SMS.

Lgd Support Indicator

This parameter, by its presence, indicates to the HSS that the SGSN supports Lgd interface for LCS. When absent the SGSN supports only Lg interface for LCS, if LCS is supported.

Adjacent PLMNs

This parameter indicates the list of PLMNs where an UE served by the SGSN is likely to make a handover from the PLMN where the SGSN is located. This list is statically configured by the operator in the SGSN, according to the geographical disposition of the different PLMNs in that area, the roaming agreements, etc…

Reset-IDs Supported

This parameter indicates, if present, the support of Reset-IDs by the SGSN.

ADD Capability

This parameter indicates, if present, the support of ADD function by the HLR.

SGSN-MME Separation Support Indicator

This parameter indicates by its presence that the HSS separately stores SGSN Id and MME Id. A combined MME/SGSN shall not send Update-GPRS-Location at intra node inter RAT routing area update if a Separation Indicator was not received previously.

MME Registered for SMS

This parameter indicates by its presence that the HSS has registered the MME for SMS.

User error

In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in clause 7.6.1 may be used, depending on the nature of the fault:

– unknown subscriber;

– roaming not allowed.

This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the SGSN number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed", "Supported RAT Types Not Allowed" or "Operator Determined Barring".

This cause shall be used when the HLR rejects a MAP Update Gprs Location request received for an MSISDN-less subscription from a SGSN not supporting MSISDN-less operation.

– system failure;

– unexpected data value.

The diagnostic in the Unknown Subscriber may indicate "Imsi Unknown" or "Gprs or EPS Subscription Unknown".

Provider error

For definition of provider errors see clause 7.6.1.

8.1.8 MAP-NOTE-MM-EVENT

8.1.8.1 Definition

This service is used between the VLR and the gsmSCF or between the SGSN and the gsmSCF when a mobility management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG-CSI and the relevant mobility management event is marked for reporting.

This service is also used between the VLR and the Presence Network Agent or between the SGSN and the Presence Network Agent to notify the Presence Network Agent when a mobility management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG-CSI and the relevant mobility management event is marked for reporting (see 3GPP TS 23.141 [128]).

8.1.8.2 Service primitives

The service primitives are shown in table 8.1/8.

Table 8.1/8: MAP_NOTE_MM_EVENT parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
Event Met	M	M(=)
Service Key	M	M(=)
IMSI	M	M(=)
Basic MSISDN	M	M(=)
Location Information for GPRS	C	C(=)
Location Information	C	C(=)
LSA Identity	C	C(=)
Supported CAMEL Phases	M	M(=)
Offered CAMEL 4 Functionalities	C	C(=)
User error			C	C(=)
Provider error				O

8.1.8.3 Parameter use

Event Met
This parameter indicates the mobility management event that has lead to the notification. It shall have one of the following values for a mobility management event reported by the VLR:

– Location update in the same VLR service area;

– Location update to another VLR service area;

– IMSI attach;

– MS initiated IMSI detach (explicit detach);

– Network initiated IMSI detach (implicit detach).

It shall have one of the following values for a mobility management event reported by the SGSN:

– Routeing area update in the same SGSN service area;

– Routeing area update to another SGSN service area;

– GPRS attach;

– MS initiated GPRS detach;

– Network initiated GPRS detach;

– Network initiated transfer to the "not reachable for paging" state.

Service Key

See clause 7.6.x.

IMSI

See clause 7.6.x.

Basic MSISDN

See clause 7.6.x.

Location Information

See clause 7.6.2.30. This information shall be sent when the event is reported by a VLR, if available. If the event is reported as part of an SGs location update procedure, this information shall include the LAI and the Location Information for EPS if available.

Location Information for GPRS

See clause 7.6.2.30a. This information shall be sent when the event is reported by an SGSN, if available.

LSA Identity

See clause 7.6.x. This information shall be sent, if available.

Supported CAMEL Phases

See clause 7.6.x. This information shall always be sent.

Offered CAMEL 4 Functionalities

This parameter indicates the CAMEL phase 4 functionalities offered by the sending entity, VMSC/VLR or SGSN (see clause 7.6.3.36G).

User error

This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values:

– Data Missing;

– Unexpected Data Value;

– Unknown Subscriber;

– MM-EventNotSupported.

Provider error

This is defined in clause 7.6.1.

8.1.9 MAP_UPDATE_VCSG_LOCATION service

8.1.9.1 Definition

This procedure is used by the VLR or SGSN to register the MS in the CSS when

– the VPLMN supports Autonomous CSG Roaming

– and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN

– and the MS has requested an initial attach or a location area procedure or a routing area procedure to a CSG cell

– and the VLR or SGSN has not yet registered the MS in the CSS.

The MAP_UPDATE_VCSG_LOCATION service is a confirmed service using the service primitives given in table 8.1/9.

8.1.9.2 Service primitives

Table 8.1/9: MAP_UPDATE_VCSG_LOCATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
VLR number	C	C(=)
SGSN number	C	C(=)
MSISDN	C	C(=)
Temporary Empty CSG Subscription data Indicator			C	C(=)
User error			C	C(=)
Provider error				O

8.1.9.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

VLR number

See definition in clause 7.6.2. The presence of this parameter is mandatory when the service is used by the VLR.

SGSN number

See definition in clause 7.6.2. The presence of this parameter is mandatory when the service is used by the SGSN.

MSISDN

See definition in clause 7.6.2. Shall be present if this parameter is available.

Temporary Empty CSG Subscription data Indicator

See definition in clause 7.6.3.100. This parameter shall be present if the CSS accepts the request and there is no CSG Subscription data (empty CSG-ID list) for the roaming MS in the CSS.

User error

The following error causes defined in clause 7.6.1 may be used:

– unknown subscriber;

– system failure;

– unexpected data value.

Provider error

For definition of provider errors see clause 7.6.1

8.1.10 MAP_ CANCEL_VCSG_LOCATION service

8.1.10.1 Definition

This service is used between CSS and VLR to delete a roaming user record including the CSG subscription data and the CSS number from the VLR. The service is also used between CSS and SGSN to delete a roaming user record including the CSG subscription data and the CSS number from the SGSN. It may be invoked when there is removal of the CSG subscription data in CSS and of the MS registration including the case where a MS was registered in CSS but without CSG data.

The MAP_CANCEL_VCSG_LOCATION service is a confirmed service using the primitives defined in table 8.1/10.

8.1.10.2 Service primitives

Table 8.1/10: MAP_CANCEL_VCSG_LOCATION

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
User error			C	C(=)
Provider error				O

8.1.10.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

User error

If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes defined in clause 7.6.1 shall be used:

– unexpected data value;

– data missing.

Provider error

For definition of provider errors see clause 7.6.1.

8.2 Paging and search

8.2.1 MAP_PAGE service

8.2.1.1 Definition

This service is used between VLR and MSC to initiate paging of an MS for mobile terminated short message or unstructured SS notification.

The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.

8.2.1.2 Service primitives

Table 8.2/1: MAP_PAGE

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
Stored location area Id	M	M(=)
TMSI	U	C(=)
User error			C	C(=)
Provider error				O

8.2.1.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on the radio path uses the IMSI as an identifier.

Stored location area Id

See definition in clause 7.6.2.

TMSI

See definition in clause 7.6.2. The TMSI is included if paging on the radio channel is to use the TMSI as an identifier.

User error

The following error causes defined in clause 7.6.1 may be sent by the user in case of a paging error, depending on the failure reason:

– absent subscriber;

– unknown location area;

– busy subscriber;

– system failure;

– this corresponds to the case where there is no call associated with the MAP_PAGE service, i.e. if the call has been released but the dialogue to the VLR has not been aborted;

– unexpected data value.

Provider error

See definition in clause 7.6.1.

8.2.2 MAP_SEARCH_FOR_MS service

8.2.2.1 Definition

This service is used between VLR and MSC to initiate paging of an MS in all location areas of that VLR. It is used if the VLR does not hold location area information confirmed by radio contact.

The MAP_SEARCH_FOR_MS service is a confirmed service using the primitives from table 8.2/2.

8.2.2.2 Service primitives

Table 8.2/2: MAP_SEARCH_FOR_MS

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
Current location area Id			C	C(=)
User error			C	C(=)
Provider error				O

8.2.2.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path.

Current location area Id

See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the Location Area Id of the area in which the MS responded is given in the response.

User error

The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on the failure reason:

– absent subscriber;

this error cause is returned by the MSC if the MS does not respond to the paging request;

– system failure;

– this corresponds to the case where there is no call associated with the MAP_SEARCH_FOR_MS service, i.e. if the call has been released but the dialogue to the VLR has not been aborted;

– busy subscriber;

– unexpected data value.

Provider error

See definition in clause 7.6.1.

8.3 Access management services

8.3.1 MAP_PROCESS_ACCESS_REQUEST service

8.3.1.1 Definition

This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. for mobile originated short message submission or after being paged by the network.

The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.

8.3.1.2 Service primitives

Table 8.3/1: MAP_PROCESS_ACCESS_REQUEST

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
CM service type	M	M(=)
Access connection status	M	M(=)
Current Location Area Id	M	M(=)
Serving cell Id	M	M(=)
TMSI	C	C(=)
Cksn	C	C(=)
IMSI	C	C(=)	C	C(=)
IMEI	C	C(=)	C	C(=)
MSISDN			U	C(=)
User error			C	C(=)
Provider error				O

8.3.1.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

CM service type

See definition in clause 7.6.9.

Access connection status

See definition in clause 7.6.9.

Current Location Area Id

See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure.

Serving cell Id

See definition in clause 7.6.2.

TMSI

See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI.

Cksn

See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present.

IMSI

In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM Service Type "Emergency Call Establishment", IMEI may replace IMSI.

IMEI

See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment".

MSISDN

See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding.

User error

One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending on the failure reason:

– unidentified subscriber;

– illegal subscriber;

this error is sent if a correlated authentication procedure has not authenticated the subscriber;

– illegal equipment;

this error is sent if an IMEI check failed, i.e. the IMEI is prohibited-listed or not permitted-listed;

– roaming not allowed;

– this cause is used after VLR restart if the subscriber has no subscription for the current location area, e.g. due to regional subscription. The cause will be qualified by "location area not allowed" or "national roaming not allowed", respectively;

– unknown location area;

– system failure;

– unexpected data value.

Provider error

For definition of provider errors see clause 7.6.1.

8.4 Handover services

It should be noted that the handover services used on the B-interface have not been updated for Release 99. The B-interface is not fully operational specified. It is strongly recommended not to implement the B-interface as an external interface.

8.4.1 MAP_PREPARE_HANDOVER service

8.4.1.1 Definition

This service is used between MSC-A and MSC-B (E-interface) when a call is to be handed over or relocated from MSC‑A to MSC‑B.

The MAP_PREPARE_HANDOVER service is a confirmed service using the primitives from table 8.4/1.

8.4.1.2 Service primitives

Table 8.4/1: MAP_PREPARE_HANDOVER

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
Target Cell Id	C	C(=)
Target RNC Id	C	C(=)
HO-NumberNotRequired	C	C(=)
IMSI	C	C(=)
Integrity Protection Information	C	C(=)
Encryption Information	C	C(=)
Radio Resource Information	C	C(=)
AN-APDU	C	C(=)	C	C(=)
Allowed GSM Algorithms	C	C(=)
Allowed UMTS Algorithms	C	C(=)
Radio Resource List	C	C(=)
RAB ID	C	C(=)
GERAN Classmark	C	C(=)
BSSMAP Service Handover	C	C(=)
BSSMAP Service Handover List	C	C(=)
RANAP Service Handover	C	C(=)
Iu-Currently Used Codec	C	C(=)
Iu-Supported Codecs List	C	C(=)
RAB Configuration Indicator	C	C(=)
ASCI Call Reference	C	C(=)
UESBI-Iu	C	C(=)
IMEISV	C	C(=)
Alternative Channel Type	C	C(=)
Trace_Propagation_List	C	C(=)
AoIP-Supported Codecs List Anchor	C	C(=)
Regional Subscription Data	U	(C=)
CSG Subscription Data	U	(C=)
LCLS Global Call Reference	C	C(=)
LCLS-Negotiation	C	C(=)
LCLS-Configuration-Preference	C	C(=)
Multiple Bearer Requested	C	C(=)
Handover Number			C	C(=)
Relocation Number List			C	C(=)
Multicall Bearer Information			C	C(=)
Multiple Bearer Not Supported			C	C(=)
Selected UMTS Algorithms			C	C(=)
Chosen Radio Resource Information			C	C(=)
Iu-Selected Codec			C	C(=)
Iu-Available Codecs List			C	C(=)
AoIP-Selected Codec Target			C	C(=)
AoIP-Available Codecs List Map			C	C(=)
User error			C	C(=)
Provider error				O

8.4.1.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

Target Cell Id

For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009.

Target RNC Id

For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter-MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009.

HO-Number Not Required

For definition of this parameter see clause 7.6.6.

IMSI

For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if:

– available and

– if the access network protocol is BSSAP and

– there is an indication that the MS also supports UMTS.

Integrity Protection Information

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access network protocol is BSSAP.

Encryption Information

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access network protocol is BSSAP.

Radio Resource Information

For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the parameter Radio Resource Information shall not be sent.

AN-APDU

For definition of this parameter see clause 7.6.9.

Allowed GSM Algorithms

For definition of this parameter see clause 7.6.6. This parameters includes allowed GSM algorithms. This GSM parameter shall be included if:

– the service is a part of the Inter-MSC SRNS Relocation procedure and

– Ciphering or Security Mode Setting procedure has been performed.and

– there is an indication that the UE also supports GSM.

Allowed UMTS Algorithms

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following conditions apply:

– access network protocol is BSSAP and

– Integrity Protection Information and Encryption Information are not available and

– Ciphering or Security Mode Setting procedure has been performed.

Radio Resource List

For definition of this parameter see clause 7.6.6. This parameter shall be included if the access network protocol is RANAP and there is an indication that the UE also supports GSM. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter Radio Resource Information is sent , the parameter Radio Resource List shall not be sent.

RAB ID

For definition of this parameter see clause 7.6.2. This parameter shall be included when MSC-A supports multiple bearers and access network protocol is BSSAP and the RAB ID has a value other than 1.

GERAN Classmark

For definition of this parameter see clause 7.6.6 This parameter shall be included if available.

BSSMAP Service Handover

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not be sent.

BSSMAP Service Handover List

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent.

RANAP Service Handover

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is BSSAP.

Iu-Currently Used Codec

For definition of this parameter see clause 7.6.6. This parameter shall be included if the handover is requested for a speech bearer and the MS is in UMTS or GERAN Iu-mode access. This parameter shall not be included if the Iu-Supported Codecs List is not included.

Iu-Supported Codecs List

For definition of this parameter see clause 7.6.6. This parameter shall be included by MSC-A, if the handover is requested for a speech bearer.

RAB Configuration Indicator

For definition of this parameter see clause 7.6.6. This parameter may be included if the handover is requested for a speech bearer and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu-Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported Codecs List is not included.

ASCI Call Reference

This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49].

UESBI-Iu

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is BSSAP.

IMEISV

For definition of the parameter see clause 7.6.2. This parameter shall be present, if available. This is used e.g. for Management based Trace Activation (see 3GPP TS 32.422).

Alternative Channel Type

For definition of this parameter see clause 7.6.6 It shall be present for a SCUDIF call if the access network protocol is BSSAP.

Trace Propagation List

See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation.

AoIP-Supported Codecs List Anchor

For definition of this parameter see clause 7.6.6. This parameter may be included by MSC-A, if the handover is requested for a speech bearer and mobile terminal supports GSM codec types.

Regional Subscription Data

The list of subscribed Zone Codes as received from the HLR may be included by MSC-A at intra PLMN inter MSC handover and may be stored at MSC-B for use at subsequent intra MSC handover.

CSG Subscription Data

The subscribed CSG Subscription Information as received from the HLR may be included by MSC-A at intra PLMN inter MSC handover and at inter PLMN inter MSC handover when the target PLMN is an ePLMN, and may be stored at MSC-B for use at subsequent intra MSC handover.

LCLS Global Call Reference

For definition of this parameter see clause 7.6.5.21. This parameter shall be included when MSC-A supports LCLS.

LCLS-Negotiation

For definition of this parameter see clause 7.6.5.22. This parameter shall be included when MSC-A supports LCLS.

LCLS-Configurations-Preference

For definition of this parameter see clause 7.6.5.23. This parameter shall be included when MSC-A supports LCLS.

Multiple Bearer Requested

For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B.

Handover Number

For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List shall not be returned.

Relocation Number List

For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number shall not be returned.

Multicall Bearer Information

For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B supports multiple bearers.

Multiple Bearer Not Supported

For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives Multiple Bearer Requested parameter and MSC-B does not support multiple bearers.

Selected UMTS Algorithms

For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the service is a part of the inter MSC inter system handover from GSM to UMTS.

Chosen Radio Resource Information

For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU is RANAP RAB Assignment Response and MS is in GSM access.

Iu-Selected Codec

For definition of this parameter see clause 7.6.6. This parameter shall be included if an Iu-Supported Codecs List was received in the service request and MSC-B supports the selection of codec based on the Iu-Supported Codecs List and the target radio access network is connected to MSC-B via the Iu interface, even if the Iu-Selected Codec is equal to the Iu-Currently Used Codec received in the service request. This parameter shall not be included if the Iu-Supported Codecs List was not received in the service request.

Iu-Available Codecs List

For definition of this parameter see clause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO, if the Iu-Supported Codecs List was included by MSC-A and the target radio access is UMTS or GERAN Iu-mode.

AoIP-Selected Codec Target

For definition of this parameter see clause 7.6.6. This parameter may be included by an MSC-B supporting TrFO, if the AoIP-Supported Codecs List Anchor was included by MSC-A and if AoIP is used on the target A interface with transcoder inserted in the MGW.

AoIP-Available Codecs List Map

User error

For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault:

– No handover number available.

– Target cell outside group call area;

– System failure.

– Unexpected data value.

– Data Missing.

Provider error

See definition of provider errors in clause 7.6.1.

8.4.2 MAP_SEND_END_SIGNAL service

8.4.2.1 Definition

This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by MSC-B to the MS. MSC-A retains then the main control of the call until it clears.

The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either because the call has been released in MSC-A or because the call has been successfully handed over or relocated from MSC-B to another MSC.

The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.

8.4.2.2 Service primitives

Table 8.4/2: MAP_SEND_END_SIGNAL

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
AN-APDU	M	M(=)
Provider error				O

8.4.2.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

AN-APDU

For definition of this parameter see clause 7.6.9.

Provider error

For definition of this parameter see clause 7.6.1.

8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service

8.4.3.1 Definition

This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A‑interface or Iu-interface in MSC‑B to MSC‑A.

The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from table 8.4/3.

8.4.3.2 Service primitives

Table 8.4/3: MAP_PROCESS_ACCESS_SIGNALLING

Parameter name	Request	Indication
Invoke Id	M	M(=)
AN-APDU	M	M(=)
Selected GSM Algorithm	C	C(=)
Selected UMTS Algorithms	C	C(=)
Chosen Radio Resource Information	C	C(=)
Selected RAB id	C	C(=)
Iu-Selected Codec	C	C(=)
Iu-Available Codecs List	C	C(=)
AoIP-Selected Codec Target	C	C(=)
AoIP-Available Codecs List Map	C	C(=)

8.4.3.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

AN-APDU

For definition of this parameter see clause 7.6.9.

Selected GSM algorithm

For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security Mode Complete and MS is in GSM access.

Selected UMTS Algorithms

For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the encapsulated PDU is BSSMAP Cipher Mode Complete and the MS is in UMTS, or an interystem handover to UMTS is performed in MSC-B, or in the case of intra MSC-B intra UMTS relocation.

Chosen Radio Resource Information

For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB Assignment Response and MS is in GSM access.

Selected RAB ID

The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple bearers were used.

Iu-Selected Codec

For definition of this parameter see clause 7.6.6. This parameter shall be included

– if MSC-B changes the selected codec and the MS is in UMTS or GERAN Iu-mode access;

– if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or

– if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the MS is in UMTS or GERAN Iu-mode access.

This parameter shall not be included if the Iu-Supported Codecs List was not received either in the Prepare Handover service request or in the Forward Access Signalling service request.

Iu-Available Codecs List

For definition of this parameter see clause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO

– if the Iu-Available Codecs List has changed in MSC-B;

– if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or

– if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the MS is in UMTS or GERAN Iu-mode access.

AoIP-Selected Codec Target

For definition of this parameter see clause 7.6.6. This parameter may be included

– if A interface codec is changed in MSC-B; or

– if intersystem handover to AoIP capable BSC is performed in MSC-B and if AoIP is used on the target A interface with transcoder inserted in the MGW; or

– if MSC-B received a Forward Access Signalling service request including an AoIP-Supported Codecs List and the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder inserted in the MGW.

This parameter shall not be included if the AoIP-Supported Codecs List Anchor was not received either in the Prepare Handover service request or in the Forward Access Signalling service request.

AoIP-Available Codecs List Map

For definition of this parameter see clause 7.6.6. This parameter may be included by an MSC-B supporting TrFO

– if the AoIP-Available Codecs List has changed in MSC-B; or

– if intersystem handover to AoIP capable BSC is performed in MSC-B where AoIP is used on the target A interface with transcoder inserted in the MGW; or

– if MSC-B received a Forward Access Signalling service request including an AoIP-Supported Codecs List Anchor and the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder inserted in the MGW.

8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service

8.4.4.1 Definition

This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface or Iu-interface of MSC-B.

The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from table 8.4/4.

8.4.4.2 Service primitives

Table 8.4/4: MAP_FORWARD_ACCESS_SIGNALLING

Parameter name	Request	Indication
Invoke Id	M	M(=)
Integrity Protection Information	C	C(=)
Encryption Information	C	C(=)
Key Status	C	C(=)
AN-APDU	M	M(=)
Allowed GSM Algorithms	C	C(=)
Allowed UMTS Algorithms	C	C(=)
Radio Resource Information	C	C(=)
Radio Resource List	C	C(=)
BSSMAP Service Handover	C	C(=)
BSSMAP Service Handover List	C	C(=)
RANAP Service Handover	C	C(=)
Iu-Currently Used Codec	C	C(=)
Iu-Supported Codecs List	C	C(=)
RAB Configuration Indicator	C	C(=)
Iu-Selected Codec	C	C(=)
Alternative Channel Type	C	C(=)
Trace Propagation List	C	C(=)
AoIP-Supported Codecs List Anchor	C	C(=)
AoIP-Selected Codec Target	C	C(=)
UESBI-Iu	C	C(=)
IMEISV	C	C(=)

8.4.4.3 Parameter use

For the definition and use of all parameters and errors, see clause 7.6.1.

Invoke Id

For definition of this parameter see clause 7.6.1.

Integrity Protection Information

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the encapsulated PDU is BSSMAP Cipher Mode Command.

Encryption Information

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the encapsulated PDU is BSSMAP Cipher Mode Command.

Key Status

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the encapsulated PDU is BSSMAP Cipher Mode Command.

AN-APDU

For definition of this parameter see clause 7.6.9.

Allowed GSM Algorithms

This parameters includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is RANAP Security Mode Command and there is an indication that the UE also supports GSM.

Allowed UMTS Algorithms

For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode Command.

Radio Resource Information

For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not be sent.

Radio Resource List

For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource Information is sent, the parameter Radio Resource List shall not be sent.

BSSMAP Service Handover

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not be sent.

BSSMAP Service Handover List

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent.

RANAP Service Handover

For definition of this parameter see clause 7.6.6.. It shall be present if it is available and the encapsulated PDU is BSSMAP Assignment Request.

Iu-Currently Used Codec

For definition of this parameter see clause 7.6.6. This parameter shall be included if the encapsulated PDU is a RANAP RAB Assignment Request or BSSMAP Assignment Request for a speech bearer and the MS is in UMTS or GERAN Iu-mode access. This parameter shall not be included if the Iu-Supported Codecs List is not included.

Iu-Supported Codecs List

For definition of this parameter see clause 7.6.6. This parameter shall be included if the encapsulated PDU is a RANAP RAB Assignment Request or BSSMAP Assignment Request and

– a new bearer is allocated for speech;

– an existing bearer is modified from data to speech; or

– for an existing speech bearer the order of priority in the Iu-Supported Codecs List needs to be modified.

This parameter shall not be included if the Iu-Selected Codec is included.

RAB Configuration Indicator

For definition of this parameter see clause 7.6.6. This parameter may be included if the encapsulated PDU is a RANAP RAB Assignment Request for a speech bearer, and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu-Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported Codecs List is not included.

Iu-Selected Codec

For definition of this parameter see clause 7.6.6. This parameter shall be included if

– the encapsulated PDU is a RANAP RAB Assignment Request or BSSMAP Assignment Request for an existing speech bearer; and

– the MS is in UMTS or GERAN Iu-mode access; and

– an Iu-Available Codecs List was received by MSC-A for this speech bearer before, either in the Prepare Handover service response or in the Process Access Signalling service request.

This parameter shall not be included if the Iu-Supported Codecs List is included.

Alternative Channel Type

For definition of this parameter see clause 7.6.6. This parameter shall be present for a SCUDIF call if the encapsulated PDU is BSSMAP Assignment Request.

Trace Propagation List

See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation.

AoIP-Supported Codecs List Anchor

For definition of this parameter see clause 7.6.6. This parameter may be included if the encapsulated PDU is a BSSMAP Assignment Request and

– a new bearer is allocated for speech;

– an existing bearer is modified from data to speech; or

– for an existing speech bearer the order of priority in the AoIP-Supported Codecs List needs to be modified.

This parameter shall not be included if the AoIP-Selected Codec Target is included.

AoIP-Selected Codec Target

For definition of this parameter see clause 7.6.6. This parameter may be included if

– the encapsulated PDU is a BSSMAP Assignment Request for an existing speech bearer; and

– the MS is in AoIP capable GSM access where AoIP is used on the target A interface with transcoder inserted in the MGW; and

– an AoIP-Available Codecs List was received by MSC-A for this speech bearer before, either in the Prepare Handover service response or in the Process Access Signalling service request.

This parameter shall not be included if the AoIP-Supported Codecs List Anchor is included.

UESBI-Iu

For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is BSSAP and the parameter has not already been sent to the target MSC.

IMEISV

For definition of the parameter see clause 7.6.2. This parameter shall be present if available and if not already sent to the target MSC. This is used e.g. for Management based Trace Activation (see 3GPP TS 32.422).

8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service

8.4.5.1 Definition

This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a handover or relocation to either MSC-A or a third MSC (MSC-B’) is required.

The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from table 8.4/5.

8.4.5.2 Service primitives

Table 8.4/5: MAP_PREPARE_SUBSEQUENT_HANDOVER

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
Target Cell Id	C	C(=)
Target RNC Id	C	C(=)
Target MSC Number	M	M(=)
Selected RAB ID	C	C(=)
GERAN Classmark	C	C(=)
RAB Configuration Indicator	C	C(=)
AN-APDU	M	M(=)	C	C(=)
User error			C	C(=)
Provider error				O

8.4.5.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

Target Cell Id

For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009.

Target RNC Id

Target MSC Number

For definition of this parameter see clause 7.6.2.

Selected RAB ID

For definition of this parameter see clause 7.6.2.

GERAN Classmark

For definition of this parameter see clause 7.6.6 This parameter shall be included if available.

RAB Configuration Indicator

For definition of this parameter see clause 7.6.6. This parameter may be included if the call is a speech call and MSC-B knows by means of configuration information that MSC-B’ (and MSC-A) supports the use of the Iu-Supported Codecs List parameter.

AN-APDU

For definition of this parameter see clause 7.6.9.

User error

For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, depending on the nature of the fault:

– Unknown MSC;

– Subsequent handover failure;

– Unexpected data value;

– Data Missing.

Provider error

For definition of this parameter see clause 7.6.1.

8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service

8.4.6.1 Definition

This service is used between MSC and VLR (B-interface) to request a handover number.

The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.

8.4.6.2 Service primitives

Table 8.4/6: MAP_ALLOCATE_HANDOVER_NUMBER

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
User error			C	C(=)
Provider error				O

8.4.6.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

User error

For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault:

– No handover number available.

Provider error

For definition of this parameter see clause 7.6.1.

8.4.7 MAP_SEND_HANDOVER_REPORT service

8.4.7.1 Definition

This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and used by MSC-A.

The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.

8.4.7.2 Service primitives

Table 8.4/7: MAP_SEND_HANDOVER_REPORT

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
Handover Number	M	M(=)
Linked Id	M	M(=)
Provider error				O

8.4.7.3 Parameter use

Invoke Id

For definition of this parameter see clause 7.6.1.

Handover Number

For definition of this parameter see clause 7.6.2.

Linked Id

For definition of this parameter see clause 7.6.1. This service is linked with MAP_ALLOCATE_HANDOVER_NUMBER.

Provider error

For definition of this parameter see clause 7.6.1.

8.5 Authentication management services

8.5.1 MAP_AUTHENTICATE service

The MAP_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. It is strongly recommended not to implement the B-interface as an external interface.

8.5.1.1 Definition

This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to initiate authentication.

The service is a confirmed service and consists of four service primitives.

8.5.1.2 Service primitives

The service primitives are shown in table 8.5/1.

Table 8.5/1: MAP_AUTHENTICATE parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
RAND	M	M(=)
CKSN	M	M(=)
SRES			M	M(=)
Provider error				O

8.5.1.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

RAND

See clause 7.6.7 for the use of this parameter.

CKSN

See clause 7.6.7 for the use of this parameter.

SRES

See clause 7.6.7 for the use of this parameter.

Provider error

See clause 7.6.1 for the use of this parameter.

8.5.2 MAP_SEND_AUTHENTICATION_INFO service

8.5.2.1 Definition

This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. The VLR requests up to five authentication vectors.

Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information and/or UE Usage Type from the HLR. The SGSN requests up to five authentication vectors.

Also this service is used between the BSF and the HLR for the BSF to retrieve authentication information from the HLR. The BSF shall only request one authentication vector at a time.

In an EPS, this service is used between IWF and IWF and between IWF and HSS.

If the requesting node type is different from "MME" and the user is a UMTS subscriber, the HLR shall return authentication quintuplets. If the requesting node type is different from MME and the user is a GSM subscriber, the HLR shall return authentication triplets.

If the requesting node type is "MME", the HSS shall return EPS authentication vectors.

If the requesting node type is a combined MME/SGSN, the HSS shall return requested authentication vectors for the actual RAT and may return additional authentication vectors for the other RAT.

If the HLR cannot provide the VLR, the SGSN or the BSF with triplets, an empty response is returned. The VLR, the SGSN, or the BSF may then re-use old authentication triplets, except where this is forbidden under the conditions specified in 3GPP TS 43.020 [24].

If the HLR cannot provide the VLR, the SGSN or the BSF with quintuplets, an empty response is returned. The VLR, the SGSN or the BSF shall not re-use old authentication quintuplets.

If the HSS cannot provide the IWF with EPS authentication vectors, an empty response is returned.

If the VLR or SGSN or IWF or BSF receives a MAP_SEND_AUTHENTICATION_INFO response containing a User Error parameter as part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN or MME or BSF shall fail.

Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200.

The service is a confirmed service and consists of four service primitives.

8.5.2.2 Service primitives

The service primitives are shown in table 8.5/2.

Table 8.5/2: MAP_SEND_AUTHENTICATION_INFO parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
IMSI	C	C(=)
Number of requested vectors	C	C(=)
Requesting node type	C	C(=)
Re-synchronisation Info	C	C(=)
Segmentation prohibited indicator	C	C (=)
Immediate response preferred indicator	U	C (=)
Requesting PLMN ID	C	C(=)
Number of additional requested vectors	C	C(=)
Additional requested Vectors are for EPS	C	C(=)
UE Usage Type Request Indication	C	C(=)
AuthenticationSetList			C	C(=)
UE Usage Type			C	C(=)
User error			C	C(=)
Provider error				O

8.5.2.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

IMSI

See clause 7.6.2 for the use of this parameter.

Number of requested vectors

A number indicating how many authentication vectors the VLR, the SGSN, the MME or the BSF is prepared to receive. The HLR shall not return more vectors than indicated by this parameter.

Requesting node type

The type of the requesting node (SGSN, MME, combined MME/SGSN, VLR, or BSF).

Re-synchronisation Info

For definition and use of this parameter see 3GPP TS 33.200.

If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other than the first one..

Segmentation prohibited indicator

This parameter indicates if the VLR, the SGSN or the IWF allows segmentation of the response at MAP user level.

This parameter may be present only in the first request of the dialogue.

Immediate response preferred indicator

This parameter indicates that one of the requested authentication vectors is requested for immediate use in the VLR, the SGSN, the MME or the BSF. It may be used by the HLR together with the number of requested vectors and the number of vectors stored in the HLR to determine the number of vectors to be obtained from the AuC. It shall be ignored if the number of available vectors is greater than the number of requested vectors.

If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other than the first one.

Requesting PLMN ID

The PLMN-ID of the requesting node. See3GPP TS 23.003.

Number of additional requested vectors

A number indicating how many additional authentication vectors the combined MME/SGSN or IWF is prepared to receive. The HLR shall not return more vectors than indicated by this parameter. This parameter shall be present only if the requesting node type is a combined MME/SGSN. A combined MME/SGSN that wants to request only EPS-Vectors (only non-EPS-Vectors) shall set the requesting node type to "MME" ("SGSN").

Additional vectors are for EPS

This parameter shall be absent if Number of additional vectors is absent. The parameter indicates by its presence that additional vectors (i.e. not for immediate use) are for EPS.

UE Usage Type Request Indication

This parameter indicates by its presence that the HLR (if it supports the Dedicated Core Network functionality) shall include the UE Usage Type in the response to the SGSN. This parameter is not applicable for VLRs.

AuthenticationSetList

A set of one to five authentication vectors are transferred from the HLR to the VLR, from the HLR to the SGSN or IWF or from the HLR to the BSF, if the outcome of the service was successful.

UE Usage Type

This parameter shall be present if UE Usage Type Request Indication was present in the request and the HLR supports the Dedicated Core Networks functionality (see 3GPP TS 23.060 [104]) and a UE Usage Type is available in the subscription data of the user. In this case, if the Immediate Response Preferred parameter is not set, the HLR may return no authentication vectors in the response.

User error

One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of the service, depending on the respective failure reason:

– unknown subscriber;

– unexpected data value;

– system failure;

– data missing.

Provider error

See clause 7.6.1 for the use of this parameter.

8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service

8.5.3.1 Definition

This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication failures.

8.5.3.2 Service primitives

The service primitives are shown in table 8.5/3.

Table 8.5/3: MAP_AUTHENTICATION_FAILURE_REPORT parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
Failure cause	M	M(=)
Re-attempt	M	M(=)
Access Type	M	M(=)
Rand	M	M(=)
VLR number	C	C(=)
SGSN number	C	C(=)
User error			C	C(=)
Provider error				O

8.5.3.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

IMSI

See clause 7.6.2 for the use of this parameter.

Failure Cause

See clause 7.6.7 for use of this parameter.

Re-attempt

See clause 7.6.7 for use of this parameter.

Access Type

See clause 7.6.7 for use of this parameter.

Rand

This parameter identifies the specific AV that failed authentication.

See clause 7.6.7 for use of this parameter.

VLR number

Shall be present if the sender is VLR. See definition in clause 7.6.2.

SGSN number

Shall be present if the sender is SGSN. See definition in clause 7.6.2.

User error

This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in clause 7.6.1:

– Unknown Subscriber;

– System Failure;

– Unexpected Data Value.

Provider error

These are defined in clause 7.6.

8.6 Security management services

8.6.1 MAP_SET_CIPHERING_MODE service

8.6.1.1 Definitions

This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is called when another service requires that information is to be sent on the radio path in encrypted form.

The service is a non-confirmed service and consists of two service primitives.

8.6.1.2 Service primitives

The service primitives are shown in table 8.6/1.

Table 8.6/1: MAP_SET_CIPHERING_MODE parameters

Parameter name	Request	Indication
Invoke id	M	M(=)
Ciphering mode	M	M(=)
Kc	C	C(=)

8.6.1.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

Ciphering mode

See clause 7.6.7 for the use of this parameter.

The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.

8.7 International mobile equipment identities management services

8.7.1 MAP_CHECK_IMEI service

8.7.1.1 Definition

This service is used between the VLR and the MSC, between the MSC and the EIR, between the SGSN and EIR, and between IWF and EIR to request check of IMEI. If the IMEI is not available in the MSC or in the SGSN, it is requested from the MS and transferred to the EIR in the service request.

This service may also be used to request the BMUEF from the EIR.

The service is a confirmed service and consists of four service primitives.

8.7.1.2 Service primitives

The service primitives are shown in table 8.7/1.

Table 8.7/1: MAP_CHECK_IMEI parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
IMEI	C	C(=)	C	C(=)
IMEISV	C	C(=)	C(=)	C(=)
Requested Equipment Info	M	M(=)
Equipment status			C	C(=)
BMUEF			C	C(=)
User error			C	C(=)
Provider error				O

8.7.1.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

Requested Equipment Info

This parameter indicates whether Equipment Status or BMUEF or both is requested.

IMEI

See clause 7.6.2 for the use of this parameter. The parameter shall not be included in the service request between the VLR and the MSC, but one of IMEI and IMEISV is mandatory in the service request from the MSC to the EIR, from the SGSN to the EIR and from the IWF to the EIR. It is not included in the service response from the EIR to the MSC, the SGSN or the IWF, but one of IMEI and IMEISV is mandatory in the service response from the MSC to the VLR on successful outcome.

IMEISV

See clause 7.6.2 for the use of this parameter. IMEISV shall be present if BMUEF is requested.

Equipment status

See clause 7.6.3 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of the service if Equipment status was requested.

BMUEF

See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of the service if BMUEF was requested.

User error

One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of the service, depending on the respective failure reason:

– unknown equipment;

this error is returned by the responder when the IMEI is not known in the EIR;

– system failure;

– data missing.

Provider error

See clause 7.6.1 for the use of this parameter.

8.7.2 MAP_OBTAIN_IMEI service

8.7.2.1 Definition

This service is used between the VLR and the MSC to request the IMEI. If the IMEI is not available in the MSC, it is requested from the MS.

The service is a confirmed service and consists of four service primitives.

8.7.2.2 Service primitives

The service primitives are shown in table 8.7/2.

Table 8.7/2: MAP_OBTAIN_IMEI parameters

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
IMEI			C	C(=)
User error			C	C(=)
Provider error				O

8.7.2.3 Parameter use

Invoke id

See clause 7.6.1 for the use of this parameter.

IMEI

See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the VLR on successful outcome of the service.

User error

If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC.

Provider error

See clause 7.6.1 for the use of this parameter.

8.8 Subscriber management services

8.8.1 MAP-INSERT-SUBSCRIBER-DATA service

8.8.1.1 Definition

This service is used by an HLR to update a VLR with certain subscriber data in the following occasions:

– the operator has changed the subscription of one or more supplementary services, basic services or data of a subscriber. Note that in case of withdrawal of a Basic or Supplementary service this primitive shall not be used;

– the operator has applied, changed or removed Operator Determined Barring;

– the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure;

– the HLR provides the VLR with subscriber parameters at location updating of a subscriber or at restoration. In this case, this service is used to indicate explicitly that a supplementary service is not provisioned, if the supplementary service specification requires it. The only supplementary services which have this requirement are the CLIR and COLR services. Network access mode is provided only in restoration. If the Super-Charger functionality is supported the HLR may not need to provide the VLR with subscriber parameters at location updating of a subscriber. See TS 23.116.

Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions:

– if the GPRS subscription has changed;

– if the network access mode is changed;

– the operator has applied, changed or removed Operator Determined Barring;

– the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure;

– the HLR provides the SGSN with subscriber parameters at GPRS location updating of a subscriber. If the Super‑Charger functionality is supported the HLR may not need to provide the SGSN with subscriber parameters. See 3GPP TS 23.116.

Also this service is used by a CSS to update an SGSN or a VLR with VPLMN-CSG-Subscription data in the following occasions:

– if the VPLMN-CSG subscription data has changed;

– the CSS provides the VLR or SGSN with VPLMN-CSG subscription data at VCSG location updating of a subscriber.

In an EPS, this service is used by an HSS to update an MME via IWF with certain subscriber data in the following occasions:

– the EPS subscription has changed;

– the operator has applied, changed or removed Operator Determined Barring;

– the HSS provides the MME via IWF(MME) with subscriber parameters at EPS location updating of a subscriber unless an explicit indication to skip subscriber data update has been received.

In an EPS, this service is used by an IWF to indicate to the MME via IWF that the HSS has requested to be notified when the UE has become reachable.

It is a confirmed service and consists of the primitives shown in table 8.8/1.

8.8.1.2 Service primitives

Table 8.8/1: MAP-INSERT-SUBSCRIBER-DATA

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	C	C(=)
MSISDN	C	C(=)
Additional MSISDN	C	C(=)
Category	C	C(=)
Subscriber Status	C	C(=)
Bearer service List	C	C(=)	C	C(=)
Teleservice List	C	C(=)	C	C(=)
Forwarding information List	C	C(=)
Call barring information List	C	C(=)
CUG information List	C	C(=)
SS-Data List	C	C(=)
eMLPP Subscription Data	C	C(=)
MC-Subscription Data	C	C(=)
Operator Determined Barring General data	C	C(=)	C	C(=)
Operator Determined Barring HPLMN data	C	C(=)
Roaming Restriction Due To Unsupported Feature	C	C(=)
Regional Subscription Data	C	C(=)
VLR CAMEL Subscription Info	C	C(=)
Voice Broadcast Data	C	C(=)
Voice Group Call Data	C	C(=)
Network access mode	C	C(=)
GPRS Subscription Data	C	C(=)
EPS Subscription Data	C	C(=)
VPLMN LIPA Allowed	C	C(=)
Roaming Restricted In SGSN/MME Due To Unsupported Feature	C	C(=)
North American Equal Access preferred Carrier Id List	U	C(=)
SGSN CAMEL Subscription Info	C	C(=)
LSA Information	C	C(=)
IST Alert Timer	C	C(=)
SS-Code List			C	C(=)
LMU Identifier	C	C(=)
LCS Information	C	C(=)
CS Allocation/Retention priority	C	C(=)
Super-Charger Supported In HLR	C	C(=)
Subscribed Charging Characteristics	C	C(=)
Access Restriction Data	C	C(=)
ICS Indicator	U	C(=)
CSG Subscription Data	C	C(=)
VPLMN CSG Subscription Data	C	C(=)
UE Reachability Request Indicator	C	C(=)
SGSN Number	C	C(=)
MME-Name	C	C(=)
Subscribed Periodic RAU-TAU Timer	C	C(=)
Subscribed Periodic LAU Timer	C	C(=)
MDT User Consent	C	C(=)
PS and SMS-Only Service Provision	C	C(=)
SMS in SGSN Allowed	C	C(=)
CS-to-PS-SRVCC-Allowed-Indicator	C	C(=)
P-CSCF Restoration Request	C	C(=)
Adjacent Access Restriction Data	C	C(=)
IMSI-Group-Id List	C	C(=)
UE Usage Type	C	C(=)
User Plane Integrity Protection Indicator	C	C(=)
DL-Buffering Suggested Packet Count	C	C(=)
Reset-IDs	C	C(=)
eDRX-Cycle-Length List	C	C(=)
IAB-Operation-Allowed-Indicator	C	C(==)
Regional Subscription Response			C	C(=)
Supported CAMEL Phases			C	C (=)
Offered CAMEL 4 CSIs			C	C (=)
Supported Features			U	C (=)
User error			U	C(=)
Provider error				O

8.8.1.3 Parameter use

All parameters are described in clause 7.6. The following clarifications are applicable:

Network access mode

This parameter defines if the subscriber has access to MSC/VLR and/or to SGSN/MME. This parameter is used by SGSN/MME and MSC/VLR. In VLR, the parameter is used only as part of Restore Data Procedure and the parameter is not stored in the VLR. This parameter shall always be sent to the SGSN and viaIWF to the MME as part of the GPRS subscriber data at GPRS/MME location updating. It shall be sent to the SGSN and via IWF to the MME if it is changed as a result of administrative action.

This parameter shall not be used by the CSS.

IMSI

It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by the VLR and the SGSN and IWF.

MSISDN

For subscriptions with MSISDN:
It is included at location updating and when it is changed. The MSISDN sent shall be the basic MSISDN. This parameter is used by the VLR and the SGSN and IWF.

For a subscription without MSISDN:
The HLR shall not populate this parameter if the VLR or SGSN explicitly indicated support of MSISDN-less operation.

NOTE 1: See clauses 8.1.2.3 and 8.1.7.3 for the case where the VLR or SGSN does not support MSISDN-less operation.

Additional MSISDN

If subscribed, the Additional MSISDN is included at location updating and when it is changed. This parameter is used by the SGSN and IWF. This parameter shall be ignored by the VLR if received.

If the SGSN does not indicate support of the feature the HSS shall not send the parameter.

Category

It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

Subscriber Status

It is included either at location updating or when it is changed.

To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB HPLMN Specific Data shall also be present.

To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This parameter is used by the VLR and the SGSN and IWF.

This parameter shall not be used by the CSS.

Bearer service List

A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer service parameter must be the code for an individual Bearer service, except in the cases described below.

The codes for the Bearer service groups "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair. The codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair.

If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location updating or at restoration) or only the ones added (at subscriber data modification).

If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no error is sent back), except in the cases described below.

If the VLR receives the codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" and supports one or more of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, it shall accept the bearer service codes, and not return them in the response to the HLR. If the VLR does not support any of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, and receives the pair of codes for "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" or the pair of codes for "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS", it shall reject the pair of codes by returning them in the response to the HLR. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Teleservice List

A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice parameter must be the code for an individual Teleservice.

If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant to the node at which the message is received should be included in the Teleservice List.

If the VLR or the SGSN or the IWF receives an Indication containing any Extensible Teleservice parameters which it does not support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no error is sent back). This parameter is used by the VLR and the SGSN and the IWF.

This parameter shall not be used by the CSS.

Forwarding information List

A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It includes Call Forwarding services either at location updating or at restoration or when they are changed. Each Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive.

The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible Forwarding Feature is defined in clause 7.6).

The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according to the rules in clause 8.8.1.4.

The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter.

If the Extensible SS-Status indicates that call forwarding is registered then (except for call forwarding unconditional) the Extensible Forwarding Feature shall contain a number to define the forwarded-to destination and, if available, the forwarded-to subaddress. In other states the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. For call forwarding unconditional the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a forwarded-to subaddress has not been registered.

The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding options shall be ignored by the VLR, and may be set to any value by the HLR.

For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply condition timer shall not be included.

For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not contain a no reply condition timer.

If the VLR receives an Indication containing any Call Forwarding service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Call Forwarding service codes (no error is sent back). This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Call barring information List

A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible Call barring information parameter shall be treated independently of all other parameters in the primitive.

The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call Barring Feature is defined in clause 7.6).

The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted according to the rules in clause 8.8.1.4.

The Extensible Call Barring Feature shall contain an extensible SS-Status parameter.

If the VLR or the SGSN or the IWF receives an Indication containing any Extensible Call Barring service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Extensible Call Barring service codes (no error is sent back).

This parameter shall not be used by the CSS.

CUG information List

A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information either at location updating or at restoration or when it is changed.

At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete CUG‑SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If there are not options per extensible basic service group the CUG-FeatureList shall not be included.

In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty CUG-SubscriptionList.

When the VLR receives CUG data it shall replace the stored CUG data with the received data set.

If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no preferential CUG exists.

If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies.

If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value.

Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR.

If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

SS-Data List

A list of Extensible SS-Data parameters (Extensible SS-Data is defined in clause 7.6). It is sent for any other supplementary service than Call Forwarding, Call Barring, CUG and eMLPP either at location updating or at restoration or when they are changed. Each SS-Data parameter shall be treated independently of all other parameters in the primitive.

The Extensible SS-Data shall include the SS-Code for an individual supplementary service.

The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are applicable to the service defined by the SS-Code.

The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4.

If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received (no error is sent back).

This parameter is used by the SGSN only for LCS. If the SGSN receives an Indication containing any LCS related supplementary service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received (no error is sent back). SS-codes not related to the supported LCS capability set shall be discarded.

If the IWF receives an Indication containing any LCS related supplementary service codes, it returns them to the HSS in the parameter SS-Code List and therefore discards the service codes received (no error is sent back). SS-codes not related to the supported LCS capability set shall be discarded.

This parameter shall not be used by the CSS.

Operator Determined Barring General data

If it is included in a Request/Indication, it includes all the Operator Determined Barring categories that may be applied to a subscriber registered in any PLMN. This parameter is only included in a Request/Indication when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all General Operator Determined Barring Categories shall be set to their actual status.

If the VLR or the SGSN or IWF receives an Indication containing Operator Determined Barring General Data which shows that the subscriber is subject to barring not supported / not allocated by the VLR or by the SGSN, it returns Operator Determined Barring General Data in the response to the HLR to show the barring categories which are not supported / not allocated by the VLR or by the SGSN. This parameter is used by the VLR and the SGSN and IWF.

This parameter shall not be used by the CSS.

Operator Determined Barring HPLMN data

It includes all the Operator Determined Barring categories that may be applied only to a subscriber registered in the HPLMN. Therefore, it shall only be transferred to the VLR or to the SGSN or IWF when the subscriber is roaming into the HPLMN and when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all HPLMN Operator Determined Barring Categories shall be set to their actual status.

If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data is present then the VLR or the SGSN or IWF shall not apply any HPLMN specific ODB services to the subscriber. This parameter is used by the VLR and the SGSN and IWF.

This parameter shall not be used by the CSS.

eMLPP Subscription Data

If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a call (as defined in clause 7.6). It contains both subparameters of eMLPP.

If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and therefore discards the received information (no error is sent back).

eMLPP subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new eMLPP subscription data received in a MAP_INSERT_SUBSCRIBER_DATA during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

MC Subscription Data

If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in clause 7.6.

If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore discards the received information (no error is sent back).

MC subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new MC subscription data received in a MAP_INSERT_SUBSCRIBER_DATA during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Roaming Restriction Due To Unsupported Feature

The HLR may decide to include this parameter in the request if certain services or features are indicated as not supported by the MSC/VLR (e.g. Advice of Charge Charging Level).

If this parameter is sent to the VLR the MSC area is restricted by the HLR and the VLR. This parameter is used only by the VLR and if the SGSN or the IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Regional Subscription Data

If included in the Insert Subscriber Data request this parameter defines the subscriber’s subscription area for the addressed VLR, for the addressed SGSN or for the addressed MME (as defined in clause 7.6). It contains the complete list of up to 10 Zone Codes that apply to a subscriber in the currently visited PLMN. The HLR shall send only those Zone Codes which are stored against the CC and NDC of the VLR, the SGSN or the MME to be updated.

NOTE 2: Support of this parameter is a network operator option and it will not be sent to networks which do not support Regional Subscription.

Regional subscription data that have been stored previously in a subscriber data record in the VLR, in the SGSN or in the MME are completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure.

After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional Subscription Response.

The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has been detected in one of the following cases:

– Too Many Zone Codes: more than 10 Zone Codes are to be stored in the VLR or in the SGSN.

– Regional Subscription Not Supported by the VLR or the SGSN.

– Zone Codes Conflict: the VLR or the SGSN detects that the zone codes indicate conflicting service permission for a location area.

Zone codes which have no mapping to location areas shall be ignored.

If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with the error Unexpected Data Value.

If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no restriction of roaming due to Regional Subscription. This parameter is used by the VLR, the SGSN and the IWF.

This parameter shall not be used by the CSS.

Voice Broadcast Data

This parameter contains a list of group id’s a user might have subscribed to; (VBS-Data is defined in clause 7.6). It includes VBS information either at location updating or at restoration or when it is changed.

At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data.

When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All subsequent VBS-data received within this dialogue shall be interpreted as add-on data.

If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data.

If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN or the IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Voice Group Call Data

This parameter contains a list of group id’s a user might have subscribed to; see clause 7.6.

At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete VGCS‑Data.

When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. All VGCS-Data received within this dialogue shall be interpreted as add-on data.

If VBCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data.

This parameter shall not be used by the CSS.

North American Equal Access preferred Carrier Id List

A list of the preferred carrier identity codes that are subscribed to.

When the VLR receives this parameter from the HLR, it shall replace the previously stored preferred carrier identity codes with the received ones. It is not possible to delete all the preferred carrier identity codes from the VLR using this service. To delete all the preferred carrier identity codes from the VLR, the HLR shall use the MAP_CANCEL_LOCATION service.

This parameter shall not be used by the CSS.

LSA Information

If included in the ISD request, this parameter contains a list of localised service area identities a user might have subscribed to together with the priority, the preferential access indicator, the active mode support indicator and active mode indication of each localised service area; see clause 7.6. The access right outside these localised service areas is also indicated. In all cases mentioned below, the LSA information shall only include LSA Data applicable to the VPLMN where the Subscriber is located. The VLR number, received in the MAP-UPDATE_LOCATION primitive, or the SGSN number, received in the MAP_UPDATE_GPRS_LOCATION primitive, can be used, alongside data stored in the HLR, to determine the LSA Data applicable to the VPLMN.

At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA Information.

When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data.

When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access indicator.

When the SGSN or the VLR receives LSA information within a dialogue it shall check if the received data has to be considered as the entire LSA information. If so, it shall replace the stored LSA information with the received data set, otherwise it shall replace the data only for the modified LSA data (if any) and/or access right, and add the new LSA data (if any) to the stored LSA Information.

If the entire LSA information is received, it shall always include the LSA only access indicator value together with the LSA data applicable for the PLMN (if any).

If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously stored LSA Information.

If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used by the VLR and the SGSN, and if the IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

IST Alert Timer

This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber performs.

At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall include the IST Alert timer.

This parameter shall not be used by the CSS.

LMU Identifier

This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if received by an SGSN or an IWF.

This parameter shall not be used by the CSS.

LCS Information

This parameter provides the following LCS related information for an MS subscriber:

– list of GMLCs in the HPLMN;

– privacy exception list;

– MO-LR list.

At restoration and location updating, the HLR shall include the complete LCS data of the subscriber.

When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS data that is not modified need not be included.

The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data operation.

If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the SS‑Data List, then the VLR shall not interpret this as overlapping data. This parameter is used by the VLR and the SGSN and the IWF.

This parameter shall not be used by the CSS.

Super-Charger Supported In HLR

This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it shall include an indication of the age of the subscription data stored in the HLR.

If this parameter is absent then the HLR does not support the Super-Charger functionality.

This parameter shall not be used by the CSS.

SS-Code List

The list of SS-Code parameters for the services that are provided to a subscriber but are not supported/allocated by the VLR/SGSN/IWF (SS-Code is defined in clause 7.6). The list can only include individual SS-Codes that were sent in the service request. For the VLR, this list can also include SS-Codes for the eMLPP and/or CUG services if the above mentioned conditions, as described in eMLPP Subscription Data and/or CUG information List, are met (that is, eMLPP Subscription Data and/or CUG information List are received).

This parameter shall not be used by the CSS.

ICS-Indicator

This optional flag indicates to the MSC Server enhanced for ICS (see 3GPP TS 23.292 [135]) whether the MSC Server shall attempt the IMS registration.

This parameter is used by the VLR and the SGSN.

This parameter shall not be used by the CSS.

CSG-Subscription Data

This parameter contains a list of CSG-Ids, the associated expiration dates (see 3GPP TS 22.011 [138]) and a list of corresponding APNs (see 3GPP TS 29.272 [144]. When the VLR or SGSN or MME receives CSG-Subscription Data from the HLR/HSS it shall replace the stored CSG-Subscription Data from the HLR/HSS (if any) with the received data. This parameter is used by the VLR and the SGSN and IWF, except the list of corresponding APNs is not applicable to the VLR, and the VLR shall ignore this list if it is received.

This parameter shall not be used by the CSS.

VPLMN CSG Subscription Data

This parameter contains a list of CSG-Ids, the associated expiration dates (see 3GPP TS 22.011 [138]). When the VLR or SGSN or MME receives VPLMN CSG Subscription Data from the CSS, it shall replace the stored VPLMN-CSG Subscription Data from the CSS (if any) with the received VPLMN CSG Subscription data. This parameter is used by the VLR, the SGSN and MME.

This parameter is not applicable for the HLR/HSS, and the VLR or SGSN or IWF shall ignore this parameter if it is received from the HLR/HSS.

CSG Subscription Data from the HLR/HSS and VPLMN CSG Subscription Data from the CSS are managed independently in the VLR or SGSN or MME. If the same CSG Id exists in both CSG subscription data from the CSS and CSG subscription data from the HLR/HSS, the CSG subscription data from the HLR/HSS shall take precedence over the CSG subscription data from the CSS in further use.

UE Reachability Request Indicator

This parameter indicates by its presence that the HSS is awaiting a Notification of UE Reachability. This parameter is used by the IWF only.

This parameter shall not be used by the CSS.

MME Name

This parameter contains the MME identity used over the SGs interface (see 3GPP TS 23.003 [17] clause 19.4.2.4) when stored in the HSS. Otherwise this parameter contains the Diameter Identity of the MME (see 3GPP TS 23.003 [17]). If the subscriber is registered to EPS and the length of the MME Name does not exceed 55 octets, the HLR shall send the MME Name to the VLR during the data restoration procedure if the ‘Restoration Indicator’ is set in the MAP_RESTORE_DATA request, and during an Update Location procedure if the ‘Restoration Indicator’ is set in the MAP_UPDATE_LOCATION request. This parameter may be used by the MSC/VLR, e.g. to page the UE via SGs.

This parameter shall not be used by the CSS.

Subscribed Periodic RAU-TAU Timer

This parameter contains the subscribed periodic RAU/TAU timer (see 3GPP TS 23.401 [145] and 3GPP TS 23.060 [104]) and is used by the SGSN and MME (via IWF). The SGSN and MME shall handle the Subscribed Periodic RAU-TAU Timer as specified in clause 5.2.1.1.2 of 3GPP TS 29.272 [144].

If the VLR receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Subscribed Periodic LAU Timer

This parameter contains the subscribed periodic LAU timer value (see 3GPP TS 23.012 [23]) and is used by the MSC/VLR. The MSC/VLR shall handle the Subscribed Periodic LAU Timer as specified in clause 3.7.3 of 3GPP TS 23.012 [23].

If the SGSN receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

SGSN Number

This parameter contains the Identity of the SGSN (see 3GPP TS 23.003 [17]). If the subscriber is registered to GPRS, the HLR shall send the SGSN Number if available to the VLR during the data restoration procedure if the ‘Restoration Indicator’ is set in the MAP_RESTORE_DATA request, and during an Update Location procedure if the ‘Restoration Indicator’ is set in the MAP_UPDATE_LOCATION request. This parameter may be used by the MSC/VLR, e.g. to page the UE via Gs.

This parameter shall not be used by the CSS.

MDT User Consent

This parameter indicates the user consent availability for MDT activation, see 3GPP TS 32.422 [132]. This parameter is used by the VLR, the SGSN and the IWF.

This parameter shall not be used by the CSS.

PS and SMS-only Service Provision

This parameter indicates whether the subscription is for PS Only and permits CS service access only for SMS.

SMS in SGSN Allowed

This parameter indicates whether the HSS allows SMS to be provided by SGSN over NAS.

User Plane Integrity Protection Indicator

This parameter indicates by its presence that the SGSN may decide to activate integrity protection of the user plane when GERAN is used (see 3GPP TS 43.020 [24]).

If the VLR receives this parameter it shall ignore it.

DL-Buffering Suggested Packet Count

This parameter indicates a suggested DL-Buffering Packet Count. The MME (via IWF) and SGSN may take it into account in addition to local policies, to determine whether to invoke extended buffering of downlink packets at the SGW for High Latency Communication. Otherwise, the MME or SGSN shall make this determination based on local policies only (see 3GPP TS 29.272 [144]).

If the VLR receives this parameter it shall ignore it.

Reset-IDs

This parameter contains a list of subscribed Reset-IDs.

eDRX-Cycle-Length List

This list shall contain the subscribed eDRX cycle length, along with the RAT type to which it is applicable.

IAB-Operation-Allowed-Indicator

This parameter indicates by its presence that IAB operation is authorized for the UE. See 3GPP TS 401 [145].

Regional Subscription Response

If included in the response this parameter indicates one of:

– Network Node Area Restricted entirely because of regional subscription;

– Too Many Zone Codes to be inserted;

– Zone Codes Conflict;

– Regional Subscription not Supported by the VLR or by the SGSN or MME.

If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted is not sent. The HLR shall check whether the current MSC area is no longer restricted.

If the SGSN determines after insertion of Regional Subscription Data that the entire SGSN area is restricted, the SGSN shall respond with a Regional Subscription Response indicating SGSN Area Restricted. Otherwise SGSN Area Restricted is not sent. The HLR shall check whether the current SGSN area is no longer restricted. This parameter is used by the VLR, the SGSN and the IWF.

This parameter shall not be used by the CSS.

VLR CAMEL Subscription Info

This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC.

– In CAMEL phase 1, this parameter contains only the O-CSI.

– In CAMEL Phase 2, this parameter may contain O-CSI, SS-CSI and TIF-CSI. In CAMEL Phase 2 and onwards, TDP-Criteria for O-CSI may be associated with O-CSI.

– In CAMEL Phase 3, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, M-CSI and TIF-CSI. In CAMEL Phase 3 and onwards, TDP-Criteria for VT-CSI may be associated with VT-CSI.

– In CAMEL Phase 4, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, MT-SMS-CSI, M-CSI and TIF-CSI. In CAMEL Phase 4, TDP-Criteria for MT-SMS-CSI may be associated with MT-SMS-CSI.

The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL Subscription Info in the HLR has been changed.

At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue.

When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then:

– for CAMEL Phase 1 and CAMEL Phase 2, the complete set of VLR CAMEL Subscription Info is sent in one dialogue;

– for CAMEL Phase 3 or higher, one or more specific elements of VLR CAMEL Subscription Info are sent in one dialogue.

When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber.

For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of:

– O-CSI (irrespective of the value of the "CAMEL Capability Handling" inside O-CSI),TDP-Criteria for O-CSI,SS-CSI and TIF-CSI.

(The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.)

From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are:

O-CSI (irrespective of the value of the "CAMEL Capability Handling" inside O-CSI), TDP criteria for O-CSI, SS-CSI and TIF-CSI;

(The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.)

– D-CSI;

– VT-CSI;

– TDP-Criteria for VT-CSI;

– MO-SMS-CSI;

– MT-SMS-CSI;

– TDP-Criteria for MT-SMS-CSI;

– M-CSI.

If the VLR CAMEL Subscription Info is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and higher. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence.

This parameter shall not be used by the CSS.

Supported CAMEL Phases

The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used by the VLR and SGSN.

A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. An IWF shall omit this parameter.

This parameter shall not be used by the CSS.

GPRS Subscription Data

This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6.

At GPRS location updating the HLR shall include the complete GPRS Subscription Data.

When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts.

When the SGSN receives GPRS Subscription Data within a dialogue it shall check if the received data has to be considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS Subscription Data with the received data set, otherwise it shall replace the data only for the modified PDP contexts (if any) and add the new PDP contexts (if any) to the stored GPRS Subscription Data.

If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored GPRS Subscription Data.

If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.

The SGSN shall handle the SIPTO-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the SIPTO-Local-Network-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the LIPA Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the Restoration-Priority information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

This parameter shall not be used by the CSS.

EPS Subscription Data

This parameter contains:

– the UE level APN-OI Replacement (see 3GPP TS 23.401 [145]), and

– the Subscriber Profile ID for RAT/Frequency Priority (RFSP-ID) (see 3GPP TS 23.401 [145], 3GPP TS 36.413 [147] and 3GPP TS 23.060 [104]), and

– the AMBR (see 3GPP TS 23.401 [145] and 3GPP TS 23.060 [104]), and

– a list of APN Configurations,

– a session transfer number for SRVCC (STN-SR) (see 3GPP TS 23.003 [17]).

– MPS CS Priority, which by its presence indicates the UE is subscribed to the eMLPP in the CS domain.

– MPS EPS Priority, which by its presence indicates the UE is subscribed to the MPS in the EPS domain.

– Subscribed vSRVCC (see 3GPP 29.272 [144]).

This parameter is used only by the MME via IWF and SGSN. If the VLR receives this parameter it shall ignore it.

The MPS CS Priority and MPS EPS Priority inside the parameter are used only by the MME via IWF. If the SGSN receives them it shall ignore them.

The SGSN shall handle the SIPTO-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the SIPTO-Local-Network-Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the LIPA Permission information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the Restoration-Priority information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

The SGSN shall handle the WLAN-offloadability information as specified in 3GPP TS 29.272 [144] clause 5.2.1.1.2.

This parameter shall not be used by the CSS.

VPLMN LIPA Allowed

This parameter by its presence indicates that the UE is allowed to use LIPA in the PLMN where the UE is attached (see 3GPP TS 23.401 [145] and 3GPP TS 23.060 [104]).

This parameter is used only by the IWF and SGSN. If the VLR receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

SGSN CAMEL Subscription Info

The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable SGSN CAMEL Subscription Info in the HLR has been changed.

– In CAMEL Phase 3, this parameter may contain one or both of GPRS-CSI and MO-SMS-CSI.

– In CAMEL Phase 4, this parameter may contain GPRS-CSI, MO-SMS-CSI and MT-SMS-CSI and TDP-Criteria for MT-SMS-CSI.

At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent.

When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue.

When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber.

The specific elements of SGSN CAMEL Subscription Info which may be sent are:

– MO-SMS-CSI;

– MT-SMS-CSI;

– TDP-Criteria for MT-SMS-CSI;

– GPRS-CSI;

– MC-CSI.

This parameter is used only by the SGSN and if the VLR or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Roaming Restricted In SGSN/MME Due To Unsupported Feature

The HSS/HLR may decide to include this parameter in the request if certain services or features are indicated as not supported by the SGSN/IWF. This parameter is used only by the SGSN and IWFand if the VLR receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

CS Allocation/Retention priority

The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Offered CAMEL 4 CSIs

This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR or SGSN (see clause 7.6.3.36D). An IWF shall omit this parameter.

This parameter shall not be used by the CSS.

Subscribed Charging Characteristics

This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.251.

For a detailed description of the use of the parameter, see 3GPP TS 32.251.

This parameter is used only by the SGSN and IWF and if the VLR receives this parameter it shall ignore it.

This parameter shall not be used by the CSS.

Access Restriction Data

This parameter indicates the allowed RAT for the PLMN where the UE is attached according to subscription data. (see clause 7.6.3.97)

If the VLR/SGSN/MME supports the Access Restriction feature but does not receive the Access Restriction Data parameter from the HSS/HLR at location updating or restoration, the VLR/SGSN/MME shall assume that the subscriber’s profile does not have any restrictions enabled.

For a detailed description of the use of the parameter, see 3GPP TS 23.012 [23] for the CS domain and 3GPP TS 23.060[104], 3GPP TS 29.060 [105] clause 7.5.3 and 3GPP TS 29.274 [149] clause 7.3.6 for the PS domain.

This parameter shall not be used by the CSS.

Supported Features

This parameter shall be used by an IWF to forward feature support indications as received from the MME or SGSN via S6a/S6d.

This parameter shall not be used by the CSS.

CS-to-PS-SRVCC-Allowed-Indicator

This parameter indicates by its presence to the MSC Server enhanced for ICS (see 3GPP TS 23.292 [135]) that CS to PS SRVCC is subscribed.

This parameter is used by the VLR.

P-CSCF Restoration Request

This parameter indicates by its presence that the HSS requests to the SGSN or the MME (via the IWF) the execution of the HSS-based P-CSCF restoration procedures, as described in 3GPP TS 23.380 [150], clause 5.4.

This parameter shall not be used by the CSS.

Adjacent Access Restriction Data

This parameter indicates the allowed RAT in each one of the indicated PLMN IDs, according to subscription data.

This parameter shall not be used by the CSS.

IMSI-Group-Id List

A list of IMSI-Group-Id parameters each of which identifies an IMSI-Group the subscriber belongs to.

UE Usage Type

This parameter indicates the usage characteristics of the UE that enables the selection of a specific Dedicated Core Network . It shall not be sent to VLRs and shall not be sent to SGSNs that did not indicate support of the Dedicated Core Network functionality within GPRS-Location Update. When the Insert-Subscriber-Data operation is used within an Update-GPRS-Location Dialogue, the HLR shall include this parameter if the SGSN indicated support of the Dedicated Core Network functionality and a UE Usage Type is available in the subscription data of the user. Outside the Update-Gprs-Location Dialogue the HLR shall include this parameter towards the SGSN that supports the Dedicated Core Network functionality if the value changed.

User error

Only one of the following values is applicable:

– Unidentified subscriber;

– Data missing;

– Unexpected data value.

8.8.1.4 Basic service information related to supplementary services

A number of parameters that relate to supplementary services can be qualified by a Basic Service Group (or a Basic Service Group List). This clause explains how this information is to be interpreted. Supplementary service parameters to which this clause is applicable only apply to the basic service groups described in this clause, and only those basic service groups shall be overwritten at the VLR or the SGSN.

The Basic Service Group (or Basic Service Group List) is optional.

If present the Basic Service Group (or each element of the Basic Service Group List) shall be one of:

– an Elementary Basic Service Group for which the supplementary service is applicable to at least one basic service in the group and for which the subscriber has a subscription to at least one basic service in the group;

– the group "All Teleservices" provided that the service is applicable to at least one teleservice and that the subscriber has a subscription to at least one teleservice which is in the same Elementary Basic Service Group as a teleservice to which the service is applicable;

– the group "All Bearer Services" provided that the service is applicable to at least one bearer service and that the subscriber has a subscription to at least one bearer service which is in the same Elementary Basic Service Group as a basic service to which the service is applicable.

If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic Service Groups.

If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as applying individually to all the Elementary Basic Service Groups for which:

– the supplementary service is applicable to at least one basic service in the Basic Service Group; and

– the subscriber has a subscription to at least one basic service in the Basic Service Group.

The VLR and the SGSN are not required to store supplementary services data for Basic Service Groups which are not supported at the VLR or the SGSN respectively.

8.8.2 MAP-DELETE-SUBSCRIBER-DATA service

8.8.2.1 Definition

This service is used by an HLR to remove certain subscriber data from a VLR or SGSN if the subscription of one or more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or deactivation of supplementary services.

This service is also used by an HLR to remove GPRS subscription data from an SGSN.

This service is also used by an HSS via IWF to remove EPS subscription data from an MME.

This service is also used by a CSS to remove the CSG subscription data from an MME via IWF or a VLR/SGSN.

It is a confirmed service and consists of the primitives shown in table 8.8/2.

8.8.2.2 Service primitives

Table 8.8/2: MAP-DELETE-SUBSCRIBER-DATA

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
Basic service List	C	C(=)
SS-Code List	C	C(=)
Roaming Restriction Due To
Unsupported Feature	C	C(=)
Camel Subscription Info Withdraw	C	C(=)
Specific CSI Withdraw	C	C(=)
Regional Subscription Data	C	C(=)
VBS Group Indication	C	C(=)
VGCS Group Indication	C	C(=)
GPRS Subscription Data Withdraw	C	C(=)
EPS Subscription Data Withdraw	C	C(=)
Roaming Restricted In SGSN/MME Due To Unsupported Feature	C	C(=)
LSA Information Withdraw	C	C(=)
IST Information Withdraw	C	C(=)
Regional Subscription Response			C	C(=)
GMLC List Withdraw	C	C(=)
Subscribed Charging Characteristics Withdraw	C	C(=)
CSG Information Deleted	C	C(=)
VPLMN CSG Information Deleted	C	C(=)
APN-OI-Replacement Withdraw	C	C(=)
STN-SR Withdraw	C	C(=)
Subscribed vSRVCC Withdraw	C	C(=)
Subscribed Periodic RAU-TAU Timer Withdraw	C	C(=)
Subscribed Periodic LAU Timer Withdraw	C	C(=)
Additional MSISDN Withdraw	C	C(=)
CS-to-PS-SRVCC Withdraw	C	C(=)
User Plane Integrity Protection Withdraw	C	C(=)
DL-Buffering Suggested Packet Count Withdraw	C	C(=)
UE-Usage-Type Withdraw	C	C(=)
Reset-IDs Withdraw	C	C(=)
IAB-Operation-Withdraw	C	C(=)
User error			C	C(=)
Provider error				O

8.8.2.3 Parameter use

All parameters are described in clause 7.6. The following clarifications are applicable:

Basic service List

A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 7.6). It is used when one, several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by the SGSN; if the IWF receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

SS-Code List

A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services are to be withdrawn from the subscriber.

There are three possible options:

– deletion of basic service(s);

The parameter Basic service List is only included.

– deletion of supplementary service(s);

The parameter SS-Code List is only included.

– deletion of basic and supplementary services;

Both Basic service List and SS-Code List are included.

This parameter is used by the VLR and SGSN and IWF for Call Barring and LCS. Otherwise, this parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Roaming Restriction Due To Unsupported Feature

This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This may occur if unsupported features or services are removed from the subscriber data in the HLR.

If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is used only by the VLR and if the SGSN or IWF receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

CAMEL Subscription Info Withdraw

This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. This parameter should not be sent in the same message as the Specific CSI Withdraw parameter; if the IWF receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Specific CSI Withdraw

This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from the VLR or from the SGSN.

The specific elements of CAMEL Subscription Info which may be withdrawn are:

– O-CSI with TDP criteria for O-CSI;

– SS-CSI;

– TIF-CSI;

– D-CSI;

– VT-CSI with TDP criteria for VT-CSI;

– MO-SMS-CSI;

– MT-SMS-CSI with TDP-Criteria for MT-SMS-CSI;

– M-CSI;

– MG-CSI;

– GPRS-CSI.

This parameter is used by the VLR and by the SGSN; if the IWF receices this parameter it shall ignore it. It shall not be sent to VLRs that do not support CAMEL phase 3 or higher. This parameter should not be sent in the same message as the CAMEL Subscription Info Withdraw parameter.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Regional Subscription Identifier

Contains one single Zone Code (as defined in clause 7.6) and is used if all Zone Codes shall be deleted from the subscriber data. When all the Zone Codes are deleted, the VLR, the SGSN or the MME shall check for its location areas whether they are allowed or not. If the whole Network Node area is restricted, the VLR, the SGSN or the MME (via the IWF) will report it to HLR by returning the Regional Subscription Response "Network Node Area Restricted".

The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the VLR, the SGSN or the MME.

Note that support of this parameter is a network operator option and it shall not be sent to networks which do not support Regional Subscription.

If Regional Subscription is not supported by the VLR, the SGSN or the MME, the request for deletion of Zone Codes is refused by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR.

If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR, the SGSN and the MME.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

VBS Group Indication

Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice Broadcast teleservice.

If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN or the IWF receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

VGCS Group Indication

Contains an indication (flag) which is used if all Group Id’s shall be deleted from the subscriber data for the Voice Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the request for deletion of all Group Ids shall be ignored.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

GPRS Subscription Data Withdraw

This parameter is used to indicate whether all GPRS Subscription Data for the subscriber shall be deleted or if only a subset of the stored GPRS Subscription Data for the subscriber shall be deleted. In the latter case only those PDP contexts whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

EPS Subscription Data Withdraw

This parameter is used to indicate whether all EPS Subscription Data for the subscriber shall be deleted or if only a subset of the stored EPS Subscription Data for the subscriber shall be deleted. In the latter case, only those APN Configurations whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used only by the SGSN and the MME and if the VLR receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Roaming Restricted In SGSN/MME Due To Unsupported Feature

This parameter is used if Roaming Restricted In SGSN/MME Due To Unsupported Feature is deleted from the GPRS/EPS subscriber data. This may occur if unsupported features or services are removed from the GPRS/EPS subscriber data in the HLR.

If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is used only by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

LSA Information Withdraw

This parameter is used to indicate whether all LSA Information for the subscriber shall be deleted or if only a subset of the stored LSA Information for the subscriber shall be deleted. In the latter case only the LSA data whose LSA identities are included in the subsequent LSA data list will be deleted. This parameter is used by the VLR and the SGSN.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

IST Information Withdraw

This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for the use of this parameter.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Regional Subscription Response

If included in the Delete Subscriber Data response this parameter indicates one of:

– Network Node Area Restricted;

– Regional Subscription Not Supported.

This parameter is used by the VLR, the SGSN and the IWF.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

GMLC List Withdraw

This parameter indicates that the subscriber’s LCS GMLC List shall be deleted from the VLR or SGSN. This parameter is used by the VLR and the SGSN and IWF.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Subscribed Charging Characteristics Withdraw

This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the SGSN or in the MME (see 3GPP TS 32.251).
This parameter is used only by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it.

This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

CSG Information Deleted

This parameter indicates that CSG Subscription Information received from the HLR/HSS shall be deleted from VLR, SGSN, or MME.
This parameter is used by the VLR, SGSN and the IWF. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

VPLMN CSG Information Deleted

This parameter indicates that CSG Subscription Information received from the CSS shall be deleted from VLR, SGSN.
This parameter is used by the VLR and SGSN. This parameter is not applicable for the HLR/HSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the HLR/HSS.

APN-OI-Replacement Withdraw

This parameter indicates that APN-OI-Replacement shall be deleted from the SGSN or the MME.
This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

STN-SR Withdraw

This parameter indicates that STN-SR shall be deleted from the SGSN or the MME.
This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Subscribed vSRVCC Withdraw

This parameter indicates that Subscribed vSRVCC shall be deleted from the MME.
This parameter is used by the MME and the IWF and if the SGSN or VLR receives this parameter it shall ignore it. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Subscribed Periodic RAU-TAU Timer Withdraw

This parameter indicates that Subscribed Periodic RAU-TAU Timer value shall be deleted from the SGSN or the MME.
This parameter is used by the SGSN and the IWF and if the VLR receives this parameter it shall ignore it. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Subscribed Periodic LAU Timer Withdraw

This parameter indicates that Subscribed Periodic LAU Timer value shall be deleted from the VLR.
This parameter is used by the VLR and if the MME or SGSN receives this parameter it shall ignore it. This parameter is not applicable for the CSS and the VLR or SGSN or IWF shall ignore this parameter if it is received from the CSS.

Additional MSISDN Withdraw

This parameter indicates that Additional MSISDN shall be deleted from the SGSN or MME.
This parameter is used by the SGSN and the IWF.

CS-to-PS-SRVCC Withdraw

This parameter indicates by its presence that CS to PS SRVCC is no longer subscribed.

User Plane Integrity Protection Withdraw

This parameter indicates by its presence that User Plane Integrity Protection may no longer be required.

DL-Buffering Suggested Packet Count Withdraw

This parameter indicates by its presence that a suggested DL-Buffering Packet Count is no longer subscribed.

UE-Usage-Type Withdraw

This parameter indicates by its presence that a UE-Usage-Type is no longer subscribed.
This parameter is not applicable for VLRs.
The HLR shall include this parameter towards the SGSN or MME (via IWF) that supports the Dedicated Core Network functionality if the subscription to a UE-Usage-Type is removed.

Reset-IDs Withdraw

This parameter indicates by its presence that Reset-IDs are no longer subscribed.

IAB-Operation-Withdraw

This parameter indicates by its presence that IAB operation is no longer authorized for the UE.

User error

Only one of the following values is applicable:

– Unidentified subscriber;

– Data missing;

– Unexpected data value.

8.9 Identity management services

8.9.1 MAP-PROVIDE-IMSI service

8.9.1.1 Definition

This service is used by a VLR in order to get, via the MSC, the IMSI of a subscriber (e.g. when a subscriber has identified itself with a TMSI not allocated to any subscriber in the VLR).

It is a confirmed service and consists of the primitives shown in table 8.9/1.

8.9.1.2 Service primitives

Table 8.9/1: MAP-PROVIDE-IMSI

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI			C	C(=)
User error			C	C(=)
Provider error				O

8.9.1.3 Parameter use

All parameters are described in clause 7.6. The following clarifications are applicable:

IMSI

This parameter is received when the request is successfully carried out. It contains the requested IMSI.

User error

Only one of the following values is applicable:

– Absent subscriber.

8.9.2 MAP-FORWARD-NEW-TMSI service

8.9.2.1 Definition

This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call set-up, location updating or supplementary services operation).

It is a confirmed service and consists of the primitives shown in table 8.9/2.

8.9.2.2 Service primitives

Table 8.9/2: MAP-FORWARD-NEW-TMSI

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
TMSI	M	M(=)
Provider error				O

8.9.2.3 Parameter use

The parameter TMSI is described in clause 7.6.

8.10 Fault recovery services

8.10.1 MAP_RESET service

8.10.1.1 Definition

This service is used by the HSS/HLR or CSS, after a restart, to indicate to a list of VLRs, SGSNs or MMEs (via IWF) that a failure occurred.

This service may also be used by the HSS/HLR as part of operation and maintenance actions e.g. to allow planned HLR/HSS outage without service interruption, or to update subscription data shared by multiple subscribers.

The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1.

8.10.1.2 Service primitives

Table 8.10/1: MAP_RESET

Parameter name	Request	Indication
Invoke Id	M	M(=)
Sending Node Number	M	M(=)
HLR Id LIST	U	C(=)
Reset-ID LIST	C	C(=)
Subscription Data	C	C(=)
Subscription Data Deletion	C	C(=)

8.10.1.3 Parameter definition and use

Invoke Id

See definition in clause 7.6.1.

SendingNode Number

For a restart of the HLR/HSS, this parameter shall contain the HLR number. See definition in clause 7.6.2.

For a restart of the CSS, this parameter shall contain the CSS number. See definition in clause 7.6.2.

HLR Id LIST

The HLR Id List is a list of HLR Ids. If the parameter is present in the indication, the VLR, the SGSN or the MME may base the retrieval of subscribers to be restored on their IMSI: the subscribers affected by the reset are those whose IMSI leading digits are equal to one of these numbers. If the parameter and the Reset-ID List is absent, subscribers to be restored are those for which the OriginatingEntityNumber received at location updating time matches the equivalent parameter of the Reset Indication.

This parameter shall only be applicable for a restart of the HLR/HSS. It shall not be present if Reset-ID LIST is present.

Reset-ID LIST

The Reset-ID LIST is a list of Reset-IDs. It shall not be present if Reset-IDs are not supported by the HLR/HSS and by theVLR or SGSN or MME (via IWF). If the parameter is present in the indication, the VLR, the SGSN or the MME may base the retrieval of affected subscribers (i.e. those impacted by the restoration or by the shared data update) on their subscribed Reset-IDs: The subscribers affected by the reset are those whose subscription contains at least one of these Reset-IDs.

Subscription Data

If the Reset Procedure is used to add/ modify subscription data shared by multiple subscribers, this Information Element shall contain the part of the subscription profile that either is to be added to the subscription profile stored in the VLR, MME or SGSN or combined MME/SGSN or is replacing a part of the subscription profiles of the impacted subscribers stored in the VLR, MME or SGSN.

Shall be absent if Subsciption Data Deletion is present.
Shall be absent if Reset-ID LIST is absent

Subscription Data Deletion

If the Reset Procedure is used to delete subscription data shared by multiple subscribers, this Information Element shall contain the identifications of the part of the subscription profile that is to be deleted from the subscription profiles of the impacted subscribers stored in the VLR, MME or SGSN.

Shall be absent if Subsciption Data is present.
Shall be absent if Reset-ID LIST is absent

8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service

8.10.2.1 Definition

This service may be used by an HLR as an implementation option, to indicate to a mobile subscriber that supplementary services parameters may have been altered, e.g. due to a restart. If received from the HLR, the VLR shall forward this indication to the MSC, which in turn forwards it to the MS. The HLR only sends this indication after successful completion of the subscriber data retrieval from HLR to VLR that ran embedded in a MAP_UPDATE_LOCATION procedure.

The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives defined in table 8.10/2.

8.10.2.2 Service primitives

Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION

Parameter name	Request	Indication
Invoke Id	M	M(=)

8.10.2.3 Parameter definition and use

Invoke Id

See definition in clause 7.6.1.

8.10.3 MAP_RESTORE_DATA service

8.10.3.1 Definition

This service is invoked by the VLR on receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an unknown IMSI, or for a known IMSI with the indicator " Subscriber Data Confirmed by HLR" set to "Not confirmed". The service is used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that are to be stored in the subscriber’s IMSI record.

This service may be invoked by the VLR on receipt of a "MAP-MT-FORWARD-SHORT-MESSAGE" message for an unknown IMSI, or for a known IMSI with the indicator "Subscriber Data Confirmed by HLR" set to "Not confirmed". The service is used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that are to be stored in the subscriber’s IMSI record.

The HLR shall return the error "system failure" to the VLR if the subscriber is not registered on the VLR.

The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 8.10/3.

8.10.3.2 Service primitives

Table 8.10/3: MAP_RESTORE_DATA

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
LMSI	U	C(=)
Supported CAMEL phases	C	C(=)
SoLSA Support Indicator	C	C(=)
IST Support Indicator	C	C(=)
Super-Charger Supported in Serving Network Entity	C	C(=)
Long FTN Supported	C	C(=)
Supported LCS Capability Sets	C	C(=)
Offered CAMEL 4 CSIs	C	C(=)
Restoration Indicator	U	C(=)
Supported RAT Types Indicator	U	C(=)
MTRF Supported	U	C(=)
MSISDN-less Operation Supported	C	C(=)
HLR number			C	C(=)
MS Not Reachable Flag			C	C(=)
User error			C	C(=)
Provider error				O

8.10.3.3 Parameter definitions and use

Invoke Id

See definition in clause 7.6.1.

IMSI

See definition in clause 7.6.2.

LMSI

See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR to support the LMSI handling procedures.

Supported CAMEL Phases

This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from phase 1 is supported. Otherwise may be absent.

SoLSA Support Indicator

This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling.

IST Support Indicator

This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Restore Data indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available.

This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Restore Data indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.

Long FTN Supported

This parameter indicates that the VLR supports Long Forwarded-to Numbers.

Super-Charger Supported in Serving Network Entity

This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and that subscriber data is required.

If this parameter is absent then the VLR does not support the Super-Charger functionality.

Supported LCS Capability Sets

This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no capability set is marked as supported then the VLR does not support LCS at all.

If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 version.

Offered CAMEL 4 CSIs

This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D).

Restoration Indicator

Supported RAT Types Indicator

This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the MSC/VLR (see clause 7.6.3)

MTRF Supported

See 3GPP TS 23.018 [97] and 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

MSISDN-less Operation Supported

See clause 3.6.1.5 of 3GPP TS 23.012 [23] for the use of this parameter and the conditions for its presence.

HLR number

See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service.

MS Not Reachable Flag

See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS Not Reachable flag" was set in the HLR.

User error

In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes defined in clause 7.6.1 may be used, depending on the nature of the fault:

– unknown subscriber;

– system failure;

– unexpected data value;

– data missing.

Provider error

For definition of provider errors see clause 7.6.1.

8.11 Subscriber Information services

8.11.1 MAP-ANY-TIME-INTERROGATION service

8.11.1.1 Definition

This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the GMLC at any time. This service may also be used by the gsmSCF to request the Mobile Number Portability (MNP) information from the NPLR.

This service is also used by the Presence Network Agent to request information, (e.g. subscriber state and location) about the subscriber (associated with a presentity) from the HLR at any time (see 3GPP TS 23.141 [128]).

When this service is used to the HLR, the subscriber state, location, Time Zone, or T-ADS data may be requested.

When this service is used to the GMLC, only the location may be requested.

When this service is used to the NPLR, only the MNP information may be requested.

The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in table 8.11/1.

8.11.1.2 Service primitives

Table 8.11/1: Any_Time_Interrogation

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
Requested Info	M	M(=)
Requested domain	C	C(=)
MNP Requested Info	C	C(=)
gsmSCF-Address	M	M(=)
IMSI	C	C(=)
MSISDN	C	C(=)
Location Information			C	C(=)
Location Information for GPRS			C	C(=)
Location Information for EPS			C	C(=)
Subscriber State			C	C(=)
PS Subscriber State			C	C(=)
EPS Subscriber State			C	C(=)
IMEI			C	C(=)
MS Classmark 2			C	C(=)
GPRS MS Class			C	C(=)
MNP info Result			C	C(=)
IMS Voice Over PS Sessions Support Indicator			C	C(=)
Last UE Activity Time			C	C(=)
Last RAT Type			C	C(=)
Time Zone			C	C(=)
Daylight Saving Time			C	C(=)
User error			C	C(=)
Provider error				O

8.11.1.3 Parameter definition and use

All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98].

The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Interrogation indication.

The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98].

IMS Voice Over PS Sessions Support Indicator

This parameter indicates the most recent IMS-Voice-Over-PS-Sessions support (based on the Last UE Activity Time), as received from the serving nodes. This parameter shall be present if Requested Info indicates that T-ADS Data are requested.

Last UE Activity Time

This parameter indicates the most recent available point in time of the UE’s last radio contact, as received from the serving nodes. This value may not represent the absolute last instant of radio activity of the UE, when any of the serving nodes has not answered to the T-ADS query. This parameter may be present if requested Info indicates that T-ADS Data are requested. This value may not be available when all the serving nodes have indicated an homogeneous support or an homogeneous non support of IMS Voice Over PS Sessions, since in that case, the serving nodes do not need to be explicitly asked for T-ADS Data.

Last RAT Type

This parameter indicates the most recent available RAT Type of the access (based on the Last UE Activity Time), as received from the serving nodes. This parameter shall be present if requested Info indicates that T-ADS Data are requested and the IMS Voice Over PS Sessions Support Indicator does not take the value "unknown". This value may not represent the absolute last RAT Type of the UE, when any of the serving nodes has not answered to the T-ADS query. This parameter may be present if requested Info indicates that T-ADS Data are requested. This value may not be available when all the serving nodes have indicated an homogeneous support or an homogeneous non support of IMS Voice Over PS Sessions, since in that case, the serving nodes do not need to be explicitly asked for T-ADS Data.

Time Zone

This parameter indicates the Time Zone of the location in the visited network where the UE is attached, including any adjustment for summertime (daylight saving time).

Daylight Saving Time

This parameter indicates the Daylight Saving Time (in steps of 1 hour) used to adjust for summertime the time zone of the location where the UE is attached in the visited network.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– System Failure;

– Any Time Interrogation Not Allowed;

– Data Missing;

– Unexpected Data Value;

– Unknown Subscriber.

Provider error

These are defined in clause 7.6.1.

8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service

8.11.2.1 Definition

This service is used to request information (e.g. subscriber state and location) from the VLR, SGSN or MME (via an IWF) at any time.

The MAP-PROVIDE-SUBSCRIBER-INFO service is a confirmed service using the primitives defined in table 8.11/2.

8.11.2.2 Service primitives

Table 8.11/2: Provide_Subscriber_Information

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
Requested Info	M	M(=)
IMSI	M	M(=)
LMSI	U	O
Call Priority	U	O
Location Information			C	C(=)
Location Information for GPRS			C	C(=)
Subscriber State			C	C(=)
PS Subscriber State			C	C(=)
IMEI			C	C(=)
MS Classmark 2			C	C(=)
GPRS MS Class			C	C(=)
IMS Voice Over PS Sessions Support Indicator			C	C(=)
Last UE Activity Time			C	C(=)
Last RAT Type			C	C(=)
Location Information for EPS			C	C(=)
Time Zone			C	C(=)
Daylight Saving Time			C	C(=)
User error			C	C(=)
Provider error				O

8.11.2.3 Parameter definition and use

All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98].

Call Priority

This parameter indicates the eMLPP priority of the call (see 3GPP TS 24.067 [137]). This parameter should be present if the HLR supports this parameter and if the Call Priority was received in the MAP_SEND_ROUTING_INFORMATION request.

IMS Voice Over PS Sessions Support Indicator

This parameter indicates whether IMS Voice Over PS Sessions is supported at the UE’s current Routing Area. This parameter shall be present if the UE’s current Routing Area is known to the SGSN and the Requested Info indicates that T-ADS Data are requested; otherwise it shall be absent.

Last UE Activity Time

This parameter indicates the point in time of the UE’s last radio contact. This parameter shall be present if requested Info indicates that T-ADS Data are request.

Last RAT Type

This parameter indicates the RAT Type of the access where the UE was present at the time of the last radio contact. This parameter shall be present if requested Info indicates that T-ADS Data are request.

Time Zone

This parameter indicates the Time Zone of the location in the visited network where the UE is attached, including any adjustment for summertime (daylight saving time).

Daylight Saving Time

This parameter indicates the Daylight Saving Time (in steps of 1 hour) used to adjust for summertime the time zone of the location where the UE is attached in the visited network.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Data Missing;

– Unexpected Data Value.

If the subscriber is not found on the VLR, SGSN or MME, this may be indicated to the requester with the "Unexpected Subscriber" value inside the Unexpected Data Value error

Provider error

These are defined in clause 7.6.1.

8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service

8.11.3.1 Definition

This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service data or CSI) from the HLR at any time. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this service.

8.11.3.2 Service primitives

Table 8.11/3: Any_Time_Subscription_Interrogation

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
Requested Subscription Info	M	M(=)
GsmSCF-Address	M	M(=)
IMSI	C	C(=)
MSISDN	C	C(=)
Long FTN Supported	C	C(=)
Call Forwarding Data			C	C(=)
Call Barring Data			C	C(=)
ODB Info			C	C(=)
CAMEL Subscription Info			C	C(=)
Supported CAMEL phases in VLR			C	C(=)
Supported CAMEL phases in SGSN			C	C(=)
Offered CAMEL 4 CSIs in VLR			C	C(=)
Offered CAMEL 4 CSIs in SGSN			C	C(=)
MSISDN-BS-List			C	C(=)
CSG Subscription Data			C	C(=)
Call Hold Data			C	C(=)
Call Waiting Data			C	C(=)
Explicit Call Transfer Data			C	C(=)
Calling Line Identification Presentation Data			C	C(=)
Calling Line Identification Restriction Data			C	C(=)
User error			C	C(=)
Provider error				O

8.11.3.3 Parameter definition and use

All parameters are described in clause 7.6.

The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Subscription_Interrogation indication. The gsmSCF-address shall contain the IM-SSF address when the IM-SSF takes the role of the gsmSCF.

The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125].

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Unexpected Data Value;

– Unknown Subscriber;

– BearerServiceNotProvisioned;

– TeleserviceNotProvisioned;

– CallBarred;

– IllegalSS-Operation;

– SS-NotAvailable;

– InformationNotAvailable;

– Any Time Subscription Interrogation Not Allowed;

– Data Missing.

Provider error

These are defined in clause 7.6.1.

8.11.4 MAP-ANY-TIME-MODIFICATION service

8.11.4.1 Definition

This service is used by the gsmSCF, to modify information of the HLR at any time.

This service is also used by the Presence Network Agent to activate or deactivate reporting of mobility management events (associated with a presentity) from the VLR or SGSN (see 3GPP TS 23.141 [128]).

This service is also used by a Service Related Entity (e.g. the IP-SM-GW) to activate a one-time subscription of UE-reachability in the MME (see 3GPP TS 23.204 [134]) and SGSN (see 3GPP TS 23.060 [104]).

This service is also used by external Short Message Gateway (IP-SM-GW) for updating the IP-SM-GW Number stored in the HLR, and for retrieving SC Address from the HLR.

8.11.4.2 Service primitives

Table 8.11/4: Any_Time_Modification

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
gsmSCF-Address	M	M(=)
Subscriber Identity	M	M(=)
Modification request for ODB data	C	C(=)
Modification request for SS information	C	C(=)
Modification request for CSI	C	C(=)
Modification request for CSG	C	C(=)
Long FTN Supported	C	C(=)
Modification request for IP-SM-GW data	C	C(=)
Activation request for UE-Reachability	C	C(=)
Ext Forwarding information-for-CSE			C	C(=)
Ext Call barring information-for-CSE			C	C(=)
ODB Info			C	C(=)
CAMEL subscription info			C	C(=)
Service Centre Address			C	C(=)
User error			C	C(=)
Provider error				O

8.11.4.3 Parameter definition and use

All parameters are described in clause 7.6.

The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Modification indication.

The use of parameters other than described below and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125].

gsmSCF-Address

This parameter indicates the address of the interrogating gsmSCF. The gsmSCF Address shall be in international E.164 format. If the service is used by IP-SM-GW, the parameter contains the address of the IP-SM-GW. See also 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125].

Modification request for CSG

This parameter is used by the gsmSCF to request notification of modification of CSG subscription data.

Modification request for IP-SM-GW data

This parameter is used by the external IP-SM-GW for updating the IP-SM-GW Number and IP-SM-GW Diameter Address stored in the HLR. If this parameter is present then other modification requests shall not be present.

Activation request for UE Reachability

This parameter is used by the Service Related Entity (e.g. IP-SM-GW) to activate the one-time subscription for UE-Reachability. If this parameter is present then other modification requests shall not be present.

Service Centre Address

See definition in clause 7.6.2.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Any Time Modification Not Allowed;

– Data Missing;

– Unexpected Data Value;

– Unknown Subscriber;

– Bearer service not provisioned;

This error is returned only if not even a subset of the requested bearer service group has been subscribed to;

– Teleservice not provisioned;

This error is returned only if not even a subset of the requested teleservice group has been subscribed to;

– Call Barred;

– Illegal SS operation;

– SS error status;

– SS incompatibility;

– SS subscription violation;

– Information Not Available.

Provider error

These are defined in clause 7.6.1.

8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service

8.11.5.1 Definition

This service is used by the HLR to inform the gsmSCF that subscriber data have been modified. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this service.

This service is also used by the HLR to inform the Service Related Entity (e.g. IP-SM-GW) that the UE has become reachable (see 3GPP TS 23.204 [134]).

8.11.5.2 Service primitives

Table 8.11/5: Note_Subscriber_Data_Modified

Parameter name	Request	Indication	Response	Confirm
Invoke id	M	M(=)	M(=)	M(=)
IMSI	M	M(=)
MSISDN	M	M(=)

Ext Forwarding information-for-CSE	C	C(=)
Ext Call barring information-for-CSE	C	C(=)
ODB Info	C	C(=)
CAMEL subscription info	C	C(=)
CSG Subscription Data	C	C
CW info	C	C(=)
CH info	C	C(=)
CLIP Info	C	C(=)
CLIR Info	C	C(=)
ECT Info	C	C(=)
All Information Sent	C	C(=)
UE reachable	C	C(=)
User error			C	C(=)
Provider error				O

8.11.5.3 Parameter definition and use

Invoke id

See clause 7.6.1 for the use of this parameter.

IMSI

See clause 7.6.2 for the use of this parameter.

MSISDN

See clause 7.6.2 for the use of this parameter. In an IP Multimedia Core Network, if no MSISDN is available, the HLR shall populate this parameter with the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]).

Ext Forwarding information-for-CSE

See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98].

Ext Call barring information-for-CSE

See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98].

ODB Info

See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98].

CAMEL subscription info

See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125].

CSG Subscription Data

This parameter contains a list of CSG-Ids and the associated expiration dates (see 3GPP TS 22.011 [138]). The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98].

CW Info

This parameter contains the status of the call waiting supplementary service. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]

CH Info

This parameter contains the status of the call hold supplementary service.The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]

ECT Info

This parameter contains the status of the explicit call transfer supplementary service.The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]

CLIP Info

This parameter contains the status of the calling line identification presentation supplementary service.The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]

CLIR Info

This parameter contains the status of the calling line identification restriction supplementary service.The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078 [98]

All Information Sent

This parameter is set when the HLR has sent all information to gsmSCF.

UE Reachable

This parameter is used when the HLR indicates to the Service related entity (e.g. IP-SM-GW) that the UE is reachable again.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Data Missing;

– Unexpected Data Value;

– Unknown Subscriber.

Provider error

These are defined in clause 7.6.1.

The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.278 [125].