INSERT SUBSCRIBER DATA ( ISD )

Parameters of ISD
1. Invoke Id 21. GPRS Subscription Data
2. IMSI 22. Roaming Restricted In SGSN Due To
3. MSISDN Unsupported Feature
4. Category 23. North American Equal Access preferred
5. Subscriber Status
6. Bearer service List Carrier Id list
7. Teleservice List 24. LSA Information
8. Forwarding information List 25. SS-Code List
9. Call barring information List 26. LMU Identifier
10. CUG information List 27. LCS Information
11. SS-Data List 28. Regional Subscription Response
12. eMLPP Subscription Data 29. Supported CAMEL Phases
13. Operator Determined Barring General data 30. User error
14. Operator Determined Barring HPLMN data 31. Provider error
15. Roaming Restriction Due To Unsupported
Feature
16. Regional Subscription Data
17. VLR CAMEL Subscription Info
18. Voice Broadcast Data
19. Voice Group Call Data
20. Network access mode
 Optional Parameters Mandatory Parameters

1. IMSI 1. Components of subscriber data

2. NAEA – preferred CI
3. GPRS subscription data
4. Roaming restricted in SGSN due to
unsupported feature
5. Network access mode
6. LSA information
7. LMU indication
8. LCS information
9. IST alert timers
10. Super charger supported in HLR
11. MC-SS-information
12. CS-allocation retention priority
13. SGSN – CAMEL – subscription information
14. Charging characteristics
 1) Invoke I.D

• This parameter identifies corresponding service primitives. The parameter is supplied by

the MAP service-user and must be unique over each service-user/service-provider interface.

2) International Mobile Subscriber Identity ( IMSI )

• An International Mobile Subscriber Identity or IMSI is a unique identification associated

with all GSM network mobile phone users.
• It is stored as a 64 bit field in the SIM inside the phone and is sent by the phone to the
network.
• 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.
• It is also used for acquiring other details of the mobile in the Home Location Register (HLR)
or as locally copied in the Visitor Location Register.
• To prevent eavesdroppers identifying and tracking the subscriber on the radio interface, the
IMSI is sent as rarely as possible and a randomly-generated TMSI is sent instead.
 3) Mobile Station ISDN Number ( MSISDN )
• MSISDN is a number uniquely identifying a subscription in a GSM or a UMTS
mobile network. Simply put, it is the telephone number of the SIM card in a
mobile/cellular phone.

• The MSISDN together with IMSI are two important numbers used for identifying a
mobile subscriber. The latter identifies the SIM, i.e. the card inserted in to the mobile
phone, while the former is used for routing calls to the subscriber.

• It is included either at location updating or when it is changed. The MSISDN sent

shall be the basic MSISDN. This parameter is used by the VLR and the SGSN.

4) 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 receives this parameter it shall ignore it.
 5) 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.
 6) Bearer Service List

• The codes for the Bearer service groups "all Alternate Speech - Data CDA" and
"all Alternate Speech - Data CDS" shall, if applicable, be sent from the HLR to the
VLR as a pair.

• The codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "all
Speech Followed By Data CDS" 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).

• The VLR discards the unsupported Extensible Bearer Services and sends a
response to the HLR when it wont support the parameters.

• The VLR receives 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 incase it supports it else it reports an error
to the HLR.
 7) Teleservice List

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

 8) Forwarding Information List

• It includes Call Forwarding services either at location updating or at restoration or

when they are changed.

• 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 which may include one Extensible Service
Group.

• If the Extensible SS-Status indicates that call forwarding is registered then (except for call
forwarding unconditional) the Extensible Forwarding Feature shall contain a forwarded-to
number and, if available, the forwarded-to sub address.

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

• 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
 9) Call Barring information List

• 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 or and Extensible Call Barring group.

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

• If the VLR 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).
 10) CUG information List
• At location updating, restoration or when there is a change in CUG data, the HLR
shall include the complete CUG Subscription List and, if there are options per basic group,
it shall also include the complete CUG-Feature List. If there are not options per extensible
basic service group the CUG-Feature List shall not be included.

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

• If CUG-Feature is received without preferential CUG, the VLR shall interpret that no
preferential CUG applies. If CUG-Feature List 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 the VLR detects that there is overlapping in the information received within a
dialogue, it shall send the error Unexpected Data Value and 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) and if the SGSN receives this parameter it
shall ignore it.
 11) SS Data List

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

• The Extensible SS-Data shall include the SS-Code for an individual supplementary
service and 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.

• 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 only by the VLR and if the SGSN receives this parameter it shall
ignore it.
 12) Operator Determined Barring General Data

• This parameter is only included in a Request/Indication when the parameter

Subscriber Status is set to the value Operator Determined Barring. It includes all the
Operator Determined Barring categories that may be applied to a subscriber
registered in any PLMN.

• If the VLR or the SGSN receives an Indication containing Operator Determined

Barring General Data which shows that the subscriber is subject to barring and if the
VLR or the SGSN doesn’t support barring of that specific ODB, 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.
 13) 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 when the subscriber is roaming into the HPLMN and when
the parameter Subscriber Status is set to the value Operator Determined Barring.

• 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 shall
not apply any HPLMN specific ODB services to the subscriber. This parameter is
used by the VLR and the SGSN.
 14) eMLPP Subscription Data

• If enhanced Multi-Level Precedence and Pre-emption service is included in the

Insert Subscriber Data request this parameter defines the priorities the subscriber
might apply for a call.

• 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 receives this parameter it shall ignore it.

• 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).
 15) 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 receives this parameter
it shall ignore it.
 16) Regional Subscription Data
• If included in the Insert Subscriber Data request, this parameter defines the subscriber's
subscription area for the addressed VLR or for the addressed SGSN. 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 or the
CC and NDC of the SGSN to be updated.
• Regional subscription data that have been stored previously in a subscriber data record in the
VLR or in the SGSN 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 response may have
- 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.
• If Regional Subscription Data are not included in any MAP ISD service, there is no
restriction of roaming due to Regional Subscription. This parameter is used by the VLR and
the SGSN.
 17) 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. If an O-CSI is contained, TDP-
Criteria may also be present in CAMEL Phase 2. In CAMEL Phase 2 this parameter contains
the SS-CSI and/or the O-CSI.

• The entire set of CAMEL Subscription Info is sent within one dialogue in a location update
or when any information in the applicable CAMEL Subscription Info in the HLR has been
changed.

• If a set of CAMEL Subscription Info is already stored in the VLR, i.e. received within a
previous dialogue, it is replaced by the received data. 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. Add-on and overlapping will also be taken care by the VLR.

• The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag).
 18) Voice Broadcast Data

• Voice broadcast service - VBS - is the process of transferring a single audio signal
(such as a news alert message) to be transmitted to all mobile devices that are operating
within a radio geographic coverage area (one or more cell sites). VBS subscribers or
devices that are capable of identifying and receiving the VBS communication signal receive
the conversation or message.

• This parameter contains a list of group id's a user might have subscribed to. It includes
VBS information either at location updating or at restoration or when it is changed.

• 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 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 receives this parameter it shall ignore it.
 19) Voice Group Call Data

• Voice group call service (VGCS) - is the process of transmitting a single voice
conversation on a channel or group of channels so it can be simultaneously received
by a predefined group of service subscribers. VGS allows the simultaneous reception
of speech conversation of a predefined group of mobile radios and/or a dispatch console.
Each mobile radio that has group call capability is called a group call member.

• This parameter contains a list of group id's a user might have subscribed to. 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 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 receives this parameter it shall ignore it.
 20) Network Access Mode

• This parameter defines if the subscriber has access to MSC/VLR and/or to

SGSN. This parameter is used by SGSN 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 as part of the subscriber data
at GPRS location updating.

• It shall be sent to the SGSN or VLR as appropriate if it is to be changed as a

result of administrative action.
 23) 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.
 24) LSA Information
• If Localized Service Area ( LSA ) is included in the ISD request, this parameter
contains a list of localized 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 localized service area. The access right
outside these localized service areas
is also indicated.

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

• When there is a change in LSA data the HLR shall include at least the new and/or
modified LSA data and When there is a change in the access right outside the
localized 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.
 25) SS – Code List

• The list of SS-Code parameters that are provided to a subscriber but are not
supported/allocated by the VLR. The list can only include individual SS-Codes that
were sent in the service request. This parameter is used only by the VLR.

26) 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.

• Location Measurement Unit ( LMU )is used for locating the geographic position
of the MS. It is controlled by Serving Mobile Location Center ( SMLC ). SMLC
gives the positioning methods to LMU for locating the MS.
 27) 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 shall keep any previously stored LCS Information that is not included in an
Insert Subscriber Data operation.

• This parameter is used only by the VLR and shall be ignored if received by an SGSN.
 28) Regional Subscription Response

• If included in the response this parameter indicates one of :

- MSC Area Restricted entirely because of regional subscription;
- SGSN 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.

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

• This parameter is used by the VLR and by the SGSN.

 29) Supported CAMEL Phases

• This parameter is used only by the VLR. A VLR not supporting any CAMEL-Phase
may omit this parameter.

30) GPRS Subscription Data

• This parameter contains a list of PDP-contexts a user has subscribed to. 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 replace
the whole existing subscription data or it modifies the PDP contexts and adds the new
PDP contexts 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.
 31) User Error

• Only one of the following values is applicable:

- Unidentified subscriber;
- Data missing;
- Unexpected data value.

32) Provider Error

• This parameter is used to indicate a protocol related type of error:
- duplicated invoke Id;
- not supported service;
- mistyped parameter;
- resource limitation;
- initiating release, i.e. the peer has already initiated release of the dialogue and
the service has to be released;
- unexpected response from the peer;
- service completion failure;
- no response from the peer;
- invalid response received.