1	Introduction
1.1	Purpose and Scope
1.2	Target Group
1.3	Typographic Conventions
1.4	Prerequisites
2	CAI Overview
2.1	General
3	Communication Protocol
3.1	General
3.2	Transport and Network Layer
3.2.1	Direct Socket Communication
3.2.2	Telnet
3.3	Session and Presentation Layer
3.3.1	Opening a Session
3.3.2	Closing a Session
3.3.3	Ending a Session
4	Message Formats
4.1	Character Representation
4.1.1	Examples
4.2	Message Request Format
4.3	Message Response Format
5	Control Commands
5.1	Login
5.1.1	Request Syntax
5.1.2	Response Syntax
5.1.3	Examples
5.2	Logout
5.2.1	Request Syntax
5.2.2	Response Syntax
5.2.3	Examples
5.3	Message Response
6	HLR Subscription
6.1	Composite Parameter Definitions
6.1.1	Customer Service Orders (CSO)
6.1.2	Subscriber Data
6.1.3	Profiles
6.1.4	Additional MSISDN
6.1.5	CAMEL
6.1.6	Closed User Groups
6.1.7	Mobility Management Related IN Triggering
6.1.8	Remove References of IMSI Changeover
6.1.9	GPRS
6.1.10	Gateway Mobile Location Center (GMLC) Address
6.1.11	Location Services (LOCSERVICES)
6.1.12	Spatial Trigger Support (SPATIALTRIGGER)
6.1.13	SMS Spam Control
6.1.14	Multiple SIM
6.2	Request and Response Parameters
6.2.1	HLR GPRS Quality of Service Parameters
6.2.2	HLR Message Waiting Parameters
6.3	HLR Subscriber Data Abbreviations
6.3.1	Bearer Services
6.3.2	Tele Services
6.3.3	Barring Services
6.3.4	Call Forwarding Services
6.3.5	Line Identification Services
6.3.6	Operator Determined barring Services
6.3.7	Subscription Options
6.3.8	Closed User Groups
6.3.9	CAMEL
6.3.10	GPRS Services
6.3.11	Location Print Services
6.3.12	GMLC Address
6.3.13	Location Services (LOCSERVICES)
6.3.14	Supplementary Service Groups
6.3.15	Others
6.4	HLRSUB Message Response
7	MNP Subscription
7.1	Customer Service Orders
7.1.1	NPSUB
7.1.2	FNSUB
7.2	Request and Response Parameters
7.2.1	NP Subscription Parameters
7.2.2	FN Subscription Parameters
7.3	MNP Subscriber Data Abbreviations
7.4	FNSUB and NPSUB Message Response
7.4.1	FNSUB and NPSUB
8	IMSI Changeover
8.1	Customer Service Orders
8.1.1	Create IMSICH
8.1.2	Set IMSICH
8.1.3	Get IMSICH
8.1.4	Delete IMSICH
8.2	Request and Response Parameters
8.3	IMSICH Message Response
9	AUC Subscription
9.1	Composite Parameter Definitions
9.1.1	Decrypting Algorithm
9.1.2	Authentication Algorithms
9.2	Customer Service Orders
9.2.1	Create AUCSUB
9.2.2	Set AUCSUB
9.2.3	Get AUCSUB
9.2.4	Delete AUCSUB
9.3	Request and Response Parameters
9.4	AUCSUB Message Response
10	Appendix
10.1	Graphical Structure
10.1.1	Example 1
10.1.2	Example 2
10.2	Error Recovery
Reference List

1   Introduction

This document is a specific description of the interface between a Business Support System (BSS) and Ericsson™ Dynamic Activation (EDA) for management of Home Location Register (HLR), Authentication Center (AUC), and other Network Elements (NEs) of their respective relevant versions.

1.1   Purpose and Scope

This document describes the supported methods in CAI for NEs, the attributes used, and the format of input parameters. It aims to provide information for the integration of a BSS with Dynamic Activation.

The following core network databases are supported:

• Home Location Register (HLR)

  The HLR application based on a modular concept provides flexibility in various networks. It offers not only common maintenance and development methodology and well-proven process for introducing new and enhanced functionality, but also trouble-free and seamless inter-working between different nodes.

• Authentication Center (AUC)

  The AUC generates authentication and ciphering data.

• Mobile Number Portability (MNP)

  The MNP node is a high capacity entity designed to cope with the handling of large number series and minimal call setup delays.

The NE redundancy concept in Dynamic Activation support redundant HLRs as well as paired NEs such as MNP and AUC.

For further information, see Function Specification Resource Activation, Reference [2].

Note:  

This document is not intended to be used for M2M subscriptions.

1.2   Target Group

The target group for this document is as follows:

• System Integrator

For information about different target groups, see Library Overview, Reference [1]

1.3   Typographic Conventions

Typographic conventions are described in Library Overview, Reference [1].

1.4   Prerequisites

Users of this document must meet the following requirements:

• Have basic knowledge of Dynamic Activation.
• Have proper authority to use Dynamic Activation.
• Have common knowledge of Ericsson systems.
• Have sound knowledge of NEs.

2   CAI Overview

The CAI is the interface between a Business Support System (BSS) and Dynamic Activation. The interface simplifies the access to the Centralized User Database (CUDB) and different kinds of HLR-FE NEs by introducing one homogenous interface.

CAI controls all protocol conversions for the specific NE.

2.1   General

The CAI can handle independent multiple sessions towards the Business System. From each session, all authorized NEs are accessible.

A provisioning operation initiated from the Business System to Dynamic Activation is referred as a Customer Service Order (CSO).

A CSO contains a Managed Object (MO) and one of the following actions:

• GET (to display an MO)
• CREATE (to create an MO)
• DELETE (to delete an MO)
• SET (to modify an MO)

The MO contains the information to be transferred to or fetched from the NE. Each MO type corresponds to a specific NE function.

Actions that influence network data are called provisioning operations and are logged by CAI. It is possible to see Network Service Orders (NSOs) that have been sent, NE responses and the result of the complete provisioning operation.

CAI has a security system which can be used to prevent non-authorized operators from accessing data in the networks. This is implemented by access control. Any hostile attempt results in an error response to the Business System.

All provisioning operations are synchronized, which means that there are no provisioning operation queues in CAI.

In general, CAI supports the full set of MOs. A site can be configured not to have support for certain NEs. In such a case, an error explaining that the configuration did not allow the action is responded when CAI is trying to access non-supported MOs.

3   Communication Protocol

3.1   General

The CAI is based on proprietary Ericsson presentation and session layers.

Basic features of the CAI are:

• Semi-permanent connection

  The connection remains open until a logout procedure is initiated by BSS. Otherwise, if the idle time is triggered (time-out), the connection is closed by Dynamic Activation.

• Synchronous, one message always followed by its response
• ASCII-character-based presentation and session layer
• Multiple concurrent sessions

The following standards can be used as transport and network layers:

• TCP/IP
• Telnet

A connection is always initiated from BSS. First the transport layer is set up, either TCP/IP or Telnet. If it is possible to open a connection, a session is created using a login sequence. After a successful login, data can be transferred.

To terminate a session, a logout sequence is used followed by a disconnection of the transport layer.

3.2   Transport and Network Layer

The type of transport and network layers to be used are decided upon software installation. If more than one protocol are used, the number of concurrent sessions on each protocol is dependent upon the number of sessions the other protocol is using.

Depending on the type of protocol, a set of configuration parameters are available. Reconfigurations of these parameters are possible without a new software installation. At time of reconfiguration, ongoing sessions must be disconnected.

From BSS point of view each Dynamic Activation is associated with a specific network address. This address can be used for all parallel sessions initiated from BSS.

3.2.1   Direct Socket Communication

TCP/IP used in Dynamic Activation means TCP over IP. It is a connection-oriented protocol providing a reliable, full-duplex, and byte stream for a user process. TCP takes care of communication details such as acknowledgments, time-outs, and retransmissions.

BSS can communicate with Dynamic Activation by TCP/IP using an IP address with the following format: <ip_address>:<port_number>. The default value of port_number is 3300.

If the Dynamic Activation server has been set up correctly, Dynamic Activation listens to this port.

As for Figure 4, once a connection between BSS and Dynamic Activation is established, BSS can form a request and send it to Dynamic Activation. Dynamic Activation processes the request and responds to BSS. Status such as ESTABLISHED, LISTEN, CLOSE_WAIT, and TIME_WAIT, can be printed.

3.2.2   Telnet

Standard telnet procedures are used to open a connection and it is assumed that each end acts as network virtual terminals. The BSS is always the initiating side and option negotiation can take place within the structure of telnet Protocol, see RFC854. The CAI interface only supports the telnet options Suppress GO Ahead and Echo. Any side can choose to clear the connection. Once a connection is established, it is preferred that each message is sent as one string.

Negotiation telnet options are as follows:

• Suppress GO Ahead

  When this option is effective on the connection, both parties can send data at the same time, without any Go Ahead message from the opposite party.

  This option is enabled by default. Inbound telnet requests the client to use this option always.

• Echo

  This option is sent by the client or server for the use of telnet echo. The echo party is to return the received data characters to the other party. It is normally used by clients to not show password as plain text on the screen. The echo party instead replaces the password characters in the echoing with stars ‘‘*’’ that are printed on the client side.

  This option is disabled by default but can be initiated by the client.

3.3   Session and Presentation Layer

The session and presentation layers are proprietary Ericsson and support two types of messages:

• Control messages
• Data messages (CSO)

A message is coded using standard 8-bit ASCII characters.

A number of concurrent sessions can be established on each of the port on every processing node. The maximum number of connections allowed can be configured by system administrators.

Each session is independent of any previous opened sessions. Interference between two sessions must be handled by the BSS. Dynamic Activation does not guarantee a mutual exclusion. For example, if two sessions are concurrently operating on the same subscriber identity, one of the sessions can or cannot receive an error code back.

3.3.1   Opening a Session

BSS is the party which initializes a session. First, a channel is allocated by the transport layer. Thereafter BSS continues with sending a LOGIN control message (see Section 5.1). Dynamic Activation answers with a response message.

Table 1    Successful Opening of a Session

Parameter		Type	Occurrence	Description
USER_ID		String, up to 16 characters	Mandatory	User ID
PWD		String, up to 16 characters	Mandatory	Password

3.3.2   Closing a Session

When BSS needs to logout from Dynamic Activation, it sends a LOGOUT control message (see Section 5.2) and in turn Dynamic Activation replies with a response message. Then BSS clears the channel. If BSS does not clear the channel within a configurable time-out time, Dynamic Activation clears the channel.

3.3.3   Ending a Session

When Dynamic Activation needs to be terminated because of system maintenance, reconfiguration, and so on, Dynamic Activation can clear any ongoing sessions. If there is an ongoing message request, Dynamic Activation must execute it and reply with a response before Dynamic Activation can disconnect the transport layer.

4   Message Formats

The communication between BSS and Dynamic Activation consists of messages, BSS sends message requests which are answered by Dynamic Activation with message responses.

4.1   Character Representation

All values - strings and numbers - is to be in coded ASCII, that is, the decimal number 1285 is to be transferred as four ASCII characters ("1", "2", "8" and "5").

String values using unprintable characters (for example, ASCII value 0, LineFeed ASCII value 19) is to use standard C conventions ("\<ascii value>") or the standard names for C (for example "\n") to specify the character. String values must be quoted if they contain other characters than A-Z, a-z, 0-9, - "" or "_", for example, "string value". This type of string is further on called "<full_string>".

If "\" is part of the string, then the ASCII value or "\\" must be used. If """ is part of the string, then the ASCII value must be used or use "\”".

Operations and attribute names are case-sensitive. They must be in upper case.

4.1.1   Examples

String	String in Message Request/Message Response	Comment
AZ_09_az	AZ_09_az	String without "other" characters
AZ-09-ax<CR>	AZ-09-ax\x0D	<CR> represented by a hexadecimal ASCII value
\home\user<CR>	\\home\\user\r	<CR> represented by a standard C character constant
"quotes"<CR>	\042quotes\042\15	quotes ('"') and <CR> represented by octal ASCII values

4.2   Message Request Format

Message requests contain a message operation identifier, that is, the commands which shall be executed, see Section 1. It is possible to identify a request uniquely, except for login/logout requests, with a transaction identifier. Each transaction identifier can have a string up to 32 characters to identify the provisioning operations. It is possible to reuse the transaction identifier, if the BSS system wants to group a number of provisioning operations.

All message requests (provisioning operations) that cause data changes in the network are logged.

In a case where a parameter occurs more than once within a command, the following priorities applies:

• If possible (by nature of parameter) do append.
• Otherwise, let the last supplied parameter be valid.

Table 2    Message Request

Parameter		Type	Occurrence	Description
operation		One of the following strings: CREATE SET DELETE GET	Mandatory	Indicates what action that will be taken towards a target.
target		Managed object or an operator ID (login name), see Table 3.	Mandatory	Operation target
TRANSID		String, 1-32 characters in the intervals A-Z, a-z and 0-9.	Optional	The Transaction ID of the provisioning operation
ARGn		[1-n], parameters separated by colon :, see Table 4.	Mandatory

Table 3    Target Command

Parameter		Type	Occurrence	Description
op_id		String, up to 16 characters A number of characters which is to be in the intervals A-Z, a-z, 0-9 or an _ (underscore).	Optional	Operator ID
mo		A number of characters which is to be in the intervals A-Z, a-z, 0-9 or an _ (underscore).	Optional	The Managed Object to operate on

Table 4    ARGn Command

Parameter	Type	Occurrence	Description
attr_name	String Upper case letters	Mandatory	Name of the Attribute
subattr_name	String Upper case letters	Optional	Name of the subattribute
number	An unsigned Integer	Optional
full_string	String Characters, including white spaces and other unprintable characters enclosed in " "	Optional
string	String Characters which is to be in the intervals A-Z, a-z, 0-9 or an _ (underscore).	Optional
enum	String with defined values	Optional	Enumeration type

The whole message is terminated with a semicolon (";"). Between the separators (":"and ",") there can be an optional number of white spaces (tabs and spaces).

4.3   Message Response Format

Message responses contain a message response code <resp_code> which is a number, where "0" stands for a successful response, and any other value for an unsuccessful response. The request can also contain a transaction identifier <trans_id> depending on if there was a transaction identifier attached with the message request. The transaction identifier is only sent together with the response if the message request does not contain any syntactical errors.

Table 5    Provisioning Operation Response

Parameter	Type	Occurrence	Description
TRANSID	Same value as in the message request	Optional	Transaction identifier of the provisioning operation
RESP	See Message Response section of each section.	Mandatory	Message Response

As with the message request format, the whole message is terminated with a semicolon (;) and between the separators (":" and ",") there can be an optional number of white spaces (tabs and spaces).

Table 6    Get Response

Parameter	Type	Occurrence	Description
TRANSID	Same value as in the message request	Optional	Transaction identifier of the provisioning operation
RESP	See “Message Response” section of each section.	Mandatory	Message Response
attr_name	String Upper case letters	Optional	The name of the Attribute
value		Optional	The attribute Value

If a requested attribute name has no values attached, only the <attr_name> are printed. Parameters and attached values is only printed if the response code <resp_code> indicates a successful message response.

5   Control Commands

5.1   Login

The LOGIN command will log in the user on Dynamic Activation. The login passwords and User ID are stored in Dynamic Activation parameter database.

5.1.1   Request Syntax

Table 7    Login Command

Parameter		Type	Occurrence	Description
user_id		String, up to 16 characters	Mandatory	User ID
pwd		String, up to 16 characters	Mandatory	Password

5.1.2   Response Syntax

Table 8    Response

Parameter		Type	Occurrence	Description
RESP			Mandatory	Response code, see Section 5.3 for response codes.

5.1.3   Examples

Login request for user ID "EMA_OPER" with the password "SECRET":

LOGIN:EMA_OPER:SECRET;

Response to a successful login:

RESP:0;

Unsuccessful response to a login attempt with an invalid user ID or password:

RESP:3006;

5.2   Logout

This command will log out the user from Dynamic Activation. The request is rejected if no user is logged on.

5.2.1   Request Syntax

5.2.2   Response Syntax

Table 9    Response

Parameter		Type	Occurrence	Description
RESP			Mandatory	Response code, see Section 5.3 for response codes.

5.2.3   Examples

Logout request:

LOGOUT;

Successful logout:

RESP:0;

Unsuccessful response to a logout attempt without logging in first:

RESP:3007;

6.1   Composite Parameter Definitions

6.1.2   Subscriber Data

Each Subscriber Data parameter, either included in a message request or in a message response, is to be made up of an identifier followed by one or more attributes (for example, provision status, Basic Service Group, activation status, Forwarded-to number), defining the value of the parameter. Attributes are separated by commas and parameters are separated by colons.

Table 22    Get HLRMWINFO Response

Parameter	Type	Occurrence	Description
Data id		Mandatory	Abbreviated name of the Subscriber Data or service, see Section 6.3.
val/prov		Mandatory	Value of the Subscriber Data argument or provision state of a service.
act		Optional	Activation state of a service.
fnum		Optional	Forwarded-to number applicable for call forwarding services.
nrpy_time		Optional	No-reply-time, only applicable for the service ‘Call Forwarding on No ReplY' (CFNRY).
OFA		Optional	Origin Forward to number Analysis
subadd		Optional	Subaddress, can be added to the Forwarded-to number.
KEEP		Optional	Keeps the original Forwarded-to number. Only can be used when the value of act is 0.
bsg		Optional	Basic Service Group for which the service is to be (de)activated.

The Subscriber Data parameter must follow the rules defined as follows. A table of all possible Subscriber Data parameter together with their applicable values can be found in Section 6.2 and abbreviations are explained in Section 6.3.

6.1.2.1   Set Subscriber Data/Providing Services

• If a Supplementary Service is only to be provided and not activated, only then its provision status is given. This deactivates the activated service and leaving it provided, for example, CAW,1 - provide call waiting, not activated.
• If a services provision is being withdrawn, it cannot be activated or registered, for example, CFNRY,0 - do not provide CFNRY.
• If a service is only to be activated or deactivated regardless of the original provision state, "-" can be used in the provision state (only applicable for the Set operation). For example, CFNRY,-,1 means to ignore the provision state and only activate CFNRY.

6.1.2.2   Activate Supplementary Services

• Supplementary services can be activated independently for each Basic Service Group or for all subscribed BSGs. For example, BAIC,1,1,TS10- provide and activate BAIC only for the Basic Service Group `Speech transmission services'.
• If a service is to be activated, it must be provided irrespective of its previous provision status. If no BSG is specified the service is activated for all applicable BSGs. For example, BAIC,1,1 - provide and activate BAIC for all BSGs subscribed.
• A service can be activated for several BSGs at the same time by repeating the required attributes for the different BSG identifiers. For example, BAIC,1,1,TS10,1,TS60 - provide and activate BAIC for the BSGs `Speech transmission services' and `Facsimile transmission services'.

6.1.2.3   Register Forwarded-to Numbers

• When activating (by registration) call forwarding services and single personal number Supplementary Service, a Forwarded-to number must be provided. For example, CFNRC,1,1,46455381234,TS10 - provide, activate, and register CFNRC for Basic Service Group `Speech transmission services' with Forwarded-to number 491019120000. It is also possible to supply a subaddress with the Forwarded-to number, which is of the format: a-b - where a is 0.1 or 2 and b is 2 - 40 characters (in octet pairs). Each character representing a hexadecimal value 0-9, A-F, for example, CFNRC,1,1,46455381234, 1-0AFBE01C001A
• When activating (by registration) `Call forwarding on no reply', a No-reply-time may be specified (5 s - 30 s in 5 s steps). If the No-reply-time is not given, then the HLR default No-reply-time are taken, for example, CFNRY,1,1,46455381234,20 - a 20 sec. No-reply-time is set.

6.1.2.4   Origin for Forwarded-to Number Analysis

Each time a subscriber registers a forwarding-to-number, a check is performed in the HLR that this number is not restricted. Restricted numbers are those which are not allowed to be used for call forwarding for example, the number to a police station. For example, OFA,1 - 1 is origin for forwarding-to number analysis. When parameter OFA is required, and has not been specified in the command, a value assigned as default to the mobile subscriber is used.

6.1.2.5   Deactivate/Keep Registration

• A Supplementary Service can be explicitly deactivated for a certain Basic Service Group without the withdrawal of the service. For example, BAIC, 1,0,TS10 - Deactivate BAIC only for Basic Service Group `Speech transmission services' and leave it provided.
• If no BSG is specified the service is deactivated for all applicable BSGs, for example, BAIC,1,0 - deactivate BAIC for all applicable BSGs but leave it provided.
• If a service is withdrawn it is automatically deactivated for all Basic Service Groups, for example BAIC,0 - do not provide BAIC and therefore deactivate.
• Upon the deactivation of a Supplementary Service the registered Forwarded-to number (and No-reply-time if applicable) is lost if it is not included in the deactivation request. When the service shall be reactivated it must be specified again, for example, CFNRC,1,0,TS10 - deactivate CFNRC, the Forwarded-to number is not kept. CFNRC,1,1,491019120000,TS10 - reactivate CFNRC, the Forwarded-to number must be specified again.
• The Forwarded-to number (and No-reply-time if applicable) are kept upon deactivation of a service, if the Forwarded-to number is given in the deactivation command. For example, CFNRC,1,0,491019120000,TS10 - deactivate CFNRC but keep the Forwarded-to number as 491019120000. CFNRC,1,1,TS10 - activate CFNRC again, using the "old" Forwarded-to number.
• There is another way to keep the Forwarded-to number upon deactivation of a service, if "KEEP" is given in the deactivation command. For example, CFNRC,1,0,KEEP,TS10 - deactivate CFNRC but keep the original Forwarded-to number. CFNRC,1,1,TS10 - activate CFNRC again, using the "old" Forwarded-to number.

6.1.2.6   Supplementary Service Groups

• A Supplementary Service Group is a bundle of several related supplementary services. For example, the Supplementary Service Group CFS is a group of Call Forwarding services, which includes CFU, CFNRC, CFNRY, CFB. See Section 6.3.14 for the descriptions of these services.
• The Supplementary Service Group ALLSS only support the provision state and activation state. The activation state can only be set to 0, that is, only the commands " ALLSS,1,0", " ALLSS,0", " ALLSS,1", and " ALLSS,-,0" are valid.

6.1.2.7   Restrictions and Deviations

There are a number of Supplementary Service interactions possible in the network that should be kept in mind when working with Subscriber Data. Interaction means that the activation/registration of service might be influenced by the provision/activation/registration of other Supplementary Services or the roaming of the mobile subscriber.

The applicability of some services is limited (see Section 6.2). Furthermore, exceptional cases are:

SPN	This service can only be activated or deactivated. Therefore it is not possible to keep the registered forwarded-to number. Allowed requests are:
	SPN,0
	Deactivated
	SPN,-,0
	Deactivated
	SPN,1,1,<fnum>
	Activated/Registered
	SPN,-,1
	Activated/Registered
DCF	This service can only be activated or deactivated. Therefore it is not possible to keep the registered forwarded-to number. Allowed requests are:
	DCF,0
	Deactivated
	DCF,-,0
	Deactivated
	DCF,1,1,<fnum>,<bsg>
	Activated/Registered, for example:
	...DCF,1,1,46455381233,TS10,1,46455381234,TS60:...
	DCF,-,1,46455381233,TS10,1,46455381234,TS60:...
TSD1	The teleservice "Auxiliary Telephony" is automatically provided if a dual MSISDN is defined for a subscription. A dual number is an additional MSISDN with BC 1 associated to it. Therefore TSD1 cannot be provided, it is a `read-only' subscriber data.

6.1.3   Profiles

All Subscriber Data excluding password, MSISDN, and IMSI may be set in a HLR profile. For Supplementary Services (for example, cfu) only the provision status can be set.

HLR GPRS Subscriber Data or HLR CAMEL Subscriber Data can be set into a HLR GPRS profile or a HLR CAMEL profile.

HLR GPRS Roaming Distribution Subscriber Data or HLR non-GPRS Roaming Distribution Subscriber Data can be set in a HLR GPRS Roaming Distribution profile or a HLR non-GPRS Roaming Distribution profile.

A GSM HLR has up to 8192 profiles. In earlier versions, a GSM HLR had up to 256 profiles. These profiles can be defined through the GSM HLR Administration application.

A GSM HLR has up to 8161 GPRS profiles and CAMEL profiles respectively. In earlier versions, a GSM HLR had up to 256 GPRS profiles and CAMEL profiles respectively. These profiles can be defined through the GSM HLR Administration application. Users can also use GPRS or CAMEL profile to define or modify a subscriber.

A GSM HLR has up to 255 gsmSCF profiles. These profiles can be defined through the GSM HLR Administration application. Users can also use gsmSCF profile to define or modify a subscriber.

Table 23    Profiles

Parameter	Type	Occurrence	Description
profile_no	Values are 0–8191 for HLR UDC.	Optional	Profile number
gprsprofile_no	Values are 0-8160 for HLR UDC.	Optional	HLR GPRS Profile Number
camelprofile_no	Values are 0-8160 for HLR UDC.	Optional	HLR CAMEL Profile Number
gsmSCFprofile_no	Values are 0–255 for HLR UDC.	Optional	HLR gsmSCF Profile Number

The use of profiles for creation and modification of subscriptions is highly recommended because the requests can then be executed much faster. The HLR profile data is copied to the subscription data within the HLR in one step. Without the HLR profile, Dynamic Activation sends at least one Man-machine Language (MML) command per argument (provided service) to the HLR.

Additional parameter in the message request is only necessary if they are not contained in the profile (for example, activation of a service), or if profile parameter values shall be replaced. Any additional argument generates additional MML commands, increasing the time needed to create or to modify a subscription in the HLR.

6.1.3.1   Use of Profiles When Creating a Subscriber

1. If a profile is used, in the service request to define a subscriber the profile data is copied. Assume Profile number 1 contains the following data:

   OFA 1

   CAT 10

   SOCB 1

   CAW 1

   CFB 1

   CFU 0

   A message request to define a subscriber with profile number 1 might be: ...MSISDN,46455381234: IMSI,12345678912345: PROFILE,1... Hence, a request to get the Subscriber Data return: ... MSISDN,46455381234 : IMSI, 12345678912345: CAT,10: CAW, 1: CFB,1,0,TS10:CFU, 0: OFA,1:SOCB, 1:...

2. Profile number 0 is the default profile in the HLR. When a subscriber is defined in the HLR, all the services and Subscriber Data specified in profile 0 are allocated if no profile is specified in the request.

3. To minimize the time required for defining a subscriber, only parameters specifying different data to that in the relevant HLR profile should be included when creating a subscriber.

6.1.3.2   Use of Profiles When Setting a Subscriber

1. A profile may also be specified in a subscriber data setting request (using operation SET). Thus, the profile data are copied to the subscription.
2. There is no default profile for a setting request: If no profile is shown, none are used.
3. If a profile is used in a subscription setting request, then all previously assigned services and Subscriber Data are reset, excluding the subscriber password.

4. Because of the fact that the profile data is copied when it is used, there is no coupling between profile and subscription after the operation. This means that already created/modified subscribers is not affected by an updated profile.

6.1.4   Additional MSISDN

The HLR makes use of several MSISDNs called "Additional MSISDNs" (AMSISDNs), so that each of them are uniquely associated with a specific Bearer Capability (BC). Up to 15 AMSISDNs can be defined per subscription. Each of them has an associated BC. AMSISDNs can be defined and deleted but not modified for a certain subscriber.

Table 24    Create AMSISDN

Parameter	Type	Occurrence	Description
AMSISDN	Digit string 5-15 digits. Each digit is 0-9.	Mandatory	Additional MSISDN
bc_number	Values are 0, 1, 2, 3, 8-65534.	Mandatory	Bearer Capability Number

Table 25    Delete AMSISDN

Parameter	Type	Occurrence	Description
AMSISDN	Digit string 5-15 digits. Each digit is 0-9.	Mandatory	Additional MSISDN

Table 26    AMSISDN Combined Request

Parameter	Type	Occurrence	Description
AMSISDN	Digit string 5-15 digits. Each digit is 0-9.	Optional	Additional MSISDN
bc_number	Values are 0, 1, 2, 3, 8-65534.	Optional	Bearer Capability Number

Table 27    Get Subscription AMSISDN Response

Parameter	Type	Occurrence	Description
AMSISDN	Digit string 5-15 digits. Each digit is 0-9.	Mandatory	Additional MSISDN
bc_number	Values are 0, 1, 2, 3, 8-65534.	Mandatory	Bearer Capability Number
bs		Mandatory	Basic Service identifier. The Basic Service is represented by an associated Bearer Capability number. The connection between the Basic Service and its associated Bearer Capability number is done in the HLR.

6.1.4.1   Create Additional MSISDNs

1. AMSISDN data can be defined with the same message request to create a subscriber: for example, CREATE:HLRSUB:MSISDN,46455381234:IMSI,12345678933333:PROFILE,1:AMSISDN,DEF,46455381222,0,DEF, 46455381223,10... - Creates a subscriber and defines the AMSISDN 46455381222 associated with Bearer Capability number 0 and the AMSISDN 46455381223 associated with Bearer Capability number 10 for the new subscriber.
2. The Bearer Capability which shall be associated with an AMSISDN must be already defined in the HLR. The value range for GSM Bearer Capabilities is 0, 1, 2, 3, 8-65534. The BC number 1 is predefined and reserved for the teleservice `Auxiliary Speech'. BC number 8 and number 9 are predefined and reserved for the teleservice `Automatic Facsimile group 3'. The BC number 2 is used to define a dual subscription and BC number 3 is used to change the master subscription in a dual subscription that is defined previously.

6.1.4.2   Delete of Additional MSISDNs

1. AMSISDNs can be deleted with the message request to modify a subscriber, for example, :SET:HLRSUB:MSISDN,46455381234:AMSISDN,DEL,46455381222,DEL,46455381223,... - Both AMSISDNs for the subscription are deleted.
2. It is possible to delete and create AMSISDNs with the same message request, for example, SET:HLRSUB:MSISDN,46455381234:AMSISDN, DEL,46455381222,DEL,46455381223,DEF,46455381225,25,DEF, 46455381226,26... - Deletes the AMSISDNs 4645538122 and 46455381223. The AMSISDNs 46455381225 and 46455381226 are defined and associated with the Bearer Capabilities number 25 and number 26.
3. The DEL... and DEF... parts can occur in any order. However, place the DEL... parts before the DEF... parts in order not to surpass the allowed numbers of AMSISDNs.

6.1.5   CAMEL

The CAMEL services are predefined in the HLR, each subscriber can have one service for originating calls, one for terminating calls and one for GPRS calls.

6.1.5.1   Create CAMEL Subscription Data

Create CAMEL Subscription Trigger Detection Points

Table 28    Create CAMEL Subscription Trigger Detection Points

Parameter	Type	Occurrence	Description
MMTDP(1)	Values are 0-4.	Optional	Mobility Management CAMEL subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 3.
VTTDP (1)	Values are 12, 13, 14.	Optional	Visitor MSC Terminating CAMEL subscription data Trigger Detection Point This parameter is valid only for CAMEL phase 3.
OSMSTDP (1)	Value is 1.	Optional	Originating SMS CAMEL Subscription data Trigger Detection Point. DP SMS Collected information. This parameter is valid only for CAMEL phase 3.
OCTDP (1)	Values are 2, 4.	Optional	Originating CAMEL subscription data Trigger Detection Point
TCTDP (1)	Values are 12, 13, 14.	Optional	Terminating CAMEL subscription data Trigger Detection Point
GPRSTDP (1)	Values are 1, 2, 11, 12, 14.	Optional	GPRS CAMEL Subscription data Trigger Detection Point, Application system-dependent parameter If GPRSTDP is set in the command, the CAMEL subscription data are applicable in the GPRS network. This parameter is valid only for CAMEL phase 3.
I	Values: Y N (default)	Optional	Inhibition indicator. Application System dependent parameter. This parameter is only valid for TCTDP.
TSMSTDP (1)	Value is 2 (SMS Delivery Request).	Optional	Terminating SMS CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
DSTDP (1)	Values are 1-10.	Optional	Dialled service CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
DIALNUM	Expressed as na-dial where: na: Nature of address indicator: 0 = Unknown 1, 2 = Not used 3 = National number 4 = International number dial: Dialled number series. Text string 1-15 characters. Only digits 0-9, *, #, a, b, and c are allowed as characters.	Optional	Dialled Number This parameter is only valid for DSTDP.
GSA	Digit string 3-15 digits	Mandatory It is not mandatory for MMTDP.	GSM SCF Address
SK	Values are 0-2147483647.	Mandatory It is not mandatory for MMTDP.	Service Key number
DEH	Values are 0-1.	Mandatory	Default Error Handling value This parameter is not valid for MMTDP.
CCH	Values are 1-4: If OCTDP is set as 4 or TCTDP is set as 13 or 14 in the command, or VTTDP/MMTDP is set, CCH can accept value 3 only. Default value 1 is assigned when CCH is not present. If GPRSTDP or OSMSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If DSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If TSMSTDP is set in the command, CCH can accept value 4 only. Default value 4 is assigned when CCH is not present.	Optional	CAMEL Capability Handling. Application system-dependent parameter.

(1)  At least one of these parameters with respective value has to be mandatory.

Create CAMEL Conditional Triggering Criteria Data

Table 29    Create CAMEL Conditional Triggering Criteria Data

Parameter	Type	Occurrence	Description
MTY	Values are: E = Enabling I = Inhibiting	Optional(1)	Match Type
DNUM	Expressed as na-nb format where na can be 0-4 and nb can be 1-15 digits, *, #.	Optional	Destination Number
DLGH	Values are 1-15.	Optional Mandatory, if DNUM is not set.	Destination number Length
FTC	Values are: N = Not forwarding F = Forwarding	Optional	Forwarding Triggering Criteria
BS	Values are TS11, TS61, TS62, TSD1, BS21, BS22, BS23, BS24, BS25, BS26, BS2G, BS31, BS32, BS33, BS34, BS3G.	Optional	Basic Service. It is used to define basic service triggering criteria.
BSG	Values are TS10, TS60, TSD0, TS20, TS30.	Optional(2)	Basic Service Group identifier. It is used to define basic service triggering criteria.
CCH	Values are 1-4.	Optional	CAMEL Capability Handling. Application system-dependent parameter.

(1)  This parameter is mandatory when setting the parameter DNUM and DLGH for the first time, and it shall NOT be used again when setting other values of DNUM and DLGH.

(2)   For TCTDP12, this parameter is mandatory if BS is not set.

1. CAMEL subscriber data can be created by defining either one or two or all the followings: Originating CAMEL Subscription Trigger Detection Points (OCTDP), Terminating CAMEL Subscription Trigger Detection Points (TCTDP), GPRS CAMEL Subscription Trigger Detection Points, Terminating SMS CAMEL subscription data Trigger Detection Point and Dialled service CAMEL subscription data Trigger Detection Point:

   CREATE:HLRSUB:IMSI,12345678933333:MSISDN,46455381234:

   CAMEL,DEF,OCTDP,2,GSA,45000000,SK,1234,DEH,1,DEF,TCTDP,

   12,GSA,45000000,SK,3234,DEH,1,DEF,GPRSTDP,1,GSA,98765432,

   SK,1234333,DEH,0,CCH,3,DEF,TSMSTDP,2,SK,1234,GSA,8888,DEH,1, CCH,4,DEF,DSTDP,1,DIALNUM,3–1234,SK,1234,GSA,8888.DEH,1,CCH,3:...

   The previous example shows how to create a subscriber in HLR with a CAMEL service. One for originating calls on detection point 2, one for terminating calls on detection point 12, one for GPRS calls on detection point 1, one for terminating SMS calls on detection point 2 and one for dialled service calls on detection point 1.

2. To create CAMEL Conditional Triggering Criteria Data, for example:

   CREATE:HLRSUB:MSISDN,46455381234:CAMEL,DEF,CCAMEL,

   OCTDP2,FTC,F,CCH,2,...

   This example creates Conditional Triggering Criteria Data for originating calls on detection point 2, and forwarding triggering criteria on CAMEL phase 2.

6.1.5.2   Set CAMEL Subscription Data

Set Data in CAMEL Subscription Trigger Detection Points

Table 30    Set Data in CAMEL Subscription Trigger Detection Points

Parameter	Type	Occurrence	Description
MMTDP	Values are 0-4.	Optional	Mobility Management CAMEL subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 3.
VTTDP	Values are 12, 13, 14.	Optional	Visitor MSC Terminating CAMEL subscription data Trigger Detection Point This parameter is valid only for CAMEL phase 3.
OSMSTDP	Value is 1.	Optional	Originating SMS CAMEL Subscription data Trigger Detection Point. DP SMS Collected information. This parameter is valid only for CAMEL phase 3.
OCTDP	Values are 2, 4.	Optional	Originating CAMEL subscription data Trigger Detection Point
TCTDP	Values are 12, 13, 14.	Optional	Terminating CAMEL subscription data Trigger Detection Point
TSMSTDP	Value is 2 (SMS Delivery Request).	Optional	Terminating SMS CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
DSTDP	Values are 1-10.	Optional	Dialled service CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
GPRSTDP	Values are 1, 2, 11, 12, 14.	Optional	GPRS CAMEL Subscription data Trigger Detection Point. Application system-dependent parameter. If GPRSTDP is set in the command, the CAMEL subscription data are applicable in the GPRS network. This parameter is valid only for CAMEL phase 3.
I	Values: Y N (default)	Optional	Inhibition indicator. Application System dependent parameter.
GSA	Digit string 3-15 digits	Optional	GSM SCF Address
SK	Values are 0-2147483647.	Optional	Service Key number
DEH	Values are 0-1.	Optional	Default Error Handling value
CCH	Values are 1-4: If OCTDP is set as 4 or TCTDP is set as 13 or 14 in the command, or VTTDP/MMTDP is set, CCH can accept value 3 only. Default value 1 is assigned when CCH is not present. If GPRSTDP or OSMSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If DSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If TSMSTDP is set in the command, CCH can accept value 4 only. Default value 4 is assigned when CCH is not present.	Optional	CAMEL Capability Handling. Application system-dependent parameter.

Set Extended CAMEL Data for a Subscriber

Table 31    Set Extended CAMEL Data for a Subscriber

Parameter	Type	Occurrence	Description
ETICK	Values are 0-999.	Optional	Extended Terminating In Category Key
ETINCI	Values are 0-255.	Optional	Extended Terminating In Capability Indicator
EOICK	Values are 0-999.	Optional	Extended Originating In Category Key
EOINCI	Values are 0-255.	Optional	Extended Originating In Capability Indicator

Set Optional CAMEL Subscription Data

Table 32    Set the Optional CAMEL Subscription Data

Parameter	Type	Occurrence	Description
GCSO	Values are 0-1.	Mandatory	CAMEL Subscription Option when CAMEL phase 1 is not supported in the interrogating GMSC
SSLO	Values are 0-1.	Optional	CAMEL Subscription Option Subscriber State and Location Information
MCSO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 1 is not supported in the servicing MSC/VLR
MC2SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 2 is not supported in the servicing MSC/VLR
MC3SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 3 is not supported in the servicing MSC/VLR
MC4SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 4 is not supported in the servicing MSC/VLR
GC2SO	Values are 0-1.	Optional	CAMEL subscription Option when CAMEL phase 2 is not supported in the interrogating GMSC
GC3SO	Values are 0-1.	Optional	CAMEL subscription Option when CAMEL phase 3 is not supported in the interrogating GMSC
GC4SO	Values are 0-1.	Optional	GMSC/gsmSCF CAMEL Support subscription Option when CAMEL phase 4 is supported in the servicing GMSC/gsmSCF
TIF	Values are 0-1.	Optional	Translation Information Flag
GPRSSO	Values are 0-1.	Optional	GPRS CAMEL phase3 denied Subscription Option. Application system-dependent parameter.
OSMSSO	Values are 0-2.	Optional	Originating SMS CAMEL denied Subscription Option. Application system-dependent parameter.
TSMSSO	Values are 0-2.	Optional	Terminating SMS CAMEL phase 4 denied Subscription Option. Application system-dependent parameter.
MMSO	Values are 0-1.	Optional	Mobility Management CAMEL denied Subscription Option. Application system-dependent parameter.

1. To set the subscription data for either one or two or all the followings: Originating Trigger Detection Points, Terminating Trigger Detection Points, GPRS Trigger Detection Points, Terminating SMS CAMEL subscription data Trigger Detection Point and Dialled service CAMEL subscription data Trigger Detection Point. This is done per detection point. For example:

   SET:HLRSUB:MSISDN,46455381234:CAMEL,SET,OCTDP,2,

   SK,9876:...

   The example shows how to set the service key for the Originating CAMEL Subscription Data Trigger Detection Point 2–9876.

2. To set the Optional CAMEL Subscription Data. For example:

   SET:HLRSUB:MSISDN,46455381234:CAMEL,SET,OCAMEL,

   GCSO,1,MCSO,0,GC2SO,0:...

   This request changes the GSM CAMEL Subscription Options. Apply ODB of all incoming calls when no CAMEL phase is supported in the interrogating GMSC. Allow mobile subscribers registration in the serving MSC/VLR without sending any CAMEL data when no CAMEL data is allowed to be sent to the MSC/VLR. Allow call terminating handling with CAMEL phase 1 invocation when CAMEL phase 2 is not supported in the interrogating GMSC.

3. To set the Extended CAMEL Subscription Data. For example:

   SET:HLRSUB:MSISDN,46455381234:CAMEL,SET,ECAMEL,

   ETINCI,123,EOICK,9:...

   The previous example sets the Extended Terminating IN Capability Indicator to 123 and the Extended Originating IN Capability Key to 9.

   Note:  

   It is only possible to set an Extended Originating CAMEL service if an Originating CAMEL Subscription Data Trigger Detection Point is already created for the subscriber. The same behavior goes for the Extended Terminating CAMEL data.

   
   
4. DEF, DEL, and SET requests may occur in any order. For example:

   SET:HLRSUB:MSISDN,46455381234:CAMEL,DEF,OCTDP,2,

   GSA,451000000,SK,123,DEH,1,SET,OCAMEL,GCSO,1,

   SET,ECAMEL,EOICK,123,DEL,TCTDP,12:...

   This example defines an Originating Trigger Detection Point 2, sets the optional CAMEL data attribute GCSO to 1 and the extended CAMEL attribute EOICK to 123. The TCTDP 12 is removed from the subscription data.

Note:  

It is possible to combine different CAMEL operations in one command by using the SET, DEL, and DEF delimiter. That means it is possible to combine one ECAMEL, one OCAMEL, one or more OCTDP, TCTDP and GPRSTDP requests in one command.

6.1.5.3   Delete CAMEL Subscription Data

Delete CAMEL Subscription Trigger Detection Points

Table 33    Delete CAMEL Subscription Trigger Detection Points

Parameter	Type	Occurrence	Description
OCTDP	Values are 2, 4 and ALL.	Optional	Originating CAMEL subscription data Trigger Detection Point
TCTDP	Values are 12, 13, 14 and ALL.	Optional	Terminating CAMEL subscription data Trigger Detection Point
GPRSTDP	Values are 1, 2, 11, 12, 14 and ALL.	Optional	GPRS CAMEL Subscription data Trigger Detection Point, Application system-dependent parameter If GPRSTDP is set in the command, the CAMEL subscription data are applicable in the GPRS network. This parameter is valid only for CAMEL phase 3.
OSMSTDP	Value is 1 and ALL.	Optional	Originating SMS CAMEL Subscription data Trigger Detection Point. DP SMS Collected information. This parameter is valid only for CAMEL phase 3.
MMTDP	Values are 0-4 and ALL.	Optional	Mobility Management CAMEL subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 3.
VTTDP	Values are 12, 13, 14 and ALL.	Optional	Visitor MSC Terminating CAMEL subscription data Trigger Detection Point This parameter is valid only for CAMEL phase 3.
TSMSTDP	Value is 2 (SMS Delivery Request) and ALL.	Optional	Terminating SMS CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
DSTDP	Values are 1-10 and ALL.	Optional	Dialled service CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
CCH	Values are 1-4: If OCTDP is set as 4 or TCTDP is set as 13 or 14 in the command, or VTTDP/MMTDP is set, CCH can accept value 3 only. Default value 1 is assigned when CCH is not present. If GPRSTDP or OSMSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If DSTDP is set in the command, CCH can accept value 3 only. Default value 3 is assigned when CCH is not present. If TSMSTDP is set in the command, CCH can accept value 4 only. Default value 4 is assigned when CCH is not present. If the parameter CCH is given in the command but TDP is omitted, all CAMEL subscription data for the specified phase is removed for the mobile subscriber or for the CAMEL subscription profile.	Optional	CAMEL Capability Handling. Application system-dependent parameter.

Delete CAMEL Conditional Triggering Criteria Data

Table 34    Delete CAMEL Conditional Triggering Criteria Data

Parameter	Type	Occurrence	Description
DNUM	Expressed as na-nb format where na can be 0-4 and nb can be 1-15 digits, *, #.	Optional	Destination Number
DLGH	Values are 1-15 or ALL.	Optional	Destination number Length
FTC	Values are: N = Not forwarding F = Forwarding	Optional	Forwarding Triggering Criteria
BS	Values are TS11, TS61, TS62, TSD1, BS21, BS22, BS23, BS24, BS25, BS26, BS2G, BS31, BS32, BS33, BS34, BS3G and ALL.	Optional	Basic Service. It is used to define basic service triggering criteria.
BSG	Values are TS10, TS60, TSD0, TS20, TS30 and ALL.	Optional	Basic Service Group identifier. It is used to define basic service triggering criteria.

1. The deletion of the CAMEL subscription data is done for each CAMEL Subscription Data Trigger Detection Point. For example: SET:HLRSUB:MSISDN,46455381234:CAMEL,DEL,OCTDP,2:...
2. If the parameter OCTDP or TCTDP is used followed by specified ALL, all the originating or termination CAMEL subscription data of the specified phase are removed.

   If the parameter GPRSTDP is used followed by specified ALL, all the GPRS CAMEL subscription data are removed.

6.1.5.4   Get CAMEL Subscription

Table 35    Get CAMEL Subscription Trigger Detection Points

Parameter	Type	Occurrence	Description
MMTDP	Values are 0-4.	Optional	Mobility Management CAMEL subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 3.
VTTDP	Values are 12, 13, 14.	Optional	Visitor MSC Terminating CAMEL subscription data Trigger Detection Point This parameter is valid only for CAMEL phase 3.
OSMSTDP	Value is 1.	Optional	Originating SMS CAMEL Subscription data Trigger Detection Point. DP SMS Collected information. This parameter is valid only for CAMEL phase 3.
OCTDP	Values are 2, 4.	Optional	Originating CAMEL subscription data Trigger Detection Point
TSMSTDP	Value is 2 (SMS Delivery Request).	Optional	Terminating SMS CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
DSTDP	Values are 1-10.	Optional	Dialled service CAMEL Subscription data Trigger Detection Point. This parameter is valid only for CAMEL phase 4.
TCTDP	Values are 12, 13, 14.	Optional	Terminating CAMEL subscription data Trigger Detection Point
GPRSTDP	Values are 1, 2, 11, 12, 14.	Optional	GPRS CAMEL Subscription data Trigger Detection Point, Application system-dependent parameter If GPRSTDP is set in the command, the CAMEL subscription data are applicable in the GPRS network. This parameter is valid only for CAMEL phase 3.
I	Values are: Y N (default)	Optional	Inhibition indicator. Application System dependent parameter.
DIALNUM	Expressed as na-dial where: na: Nature of address indicator: 0 = Unknown 1, 2 = Not used 3 = National number 4 = International number dial: Dialled number series. Text string 1-15 characters. Only digits 0-9, *, #, a, b, and c are allowed as characters.	Optional	Dialled Number
GSA	Digit string 3-15 digits	Mandatory Optional for MMTDP.	GSM SCF Address
SK	Values are 0-2147483647.	Mandatory Optional for MMTDP.	Service Key number
DEH	Values are 0-1.	Mandatory	Default Error Handling value This parameter is invalid for MMTDP.
CCH	Values are 1-4.	Mandatory	CAMEL Capability Handling. Application system-dependent parameter.
ETICK	Values are 0-999.	Mandatory	Extended Terminating In Category Key
ETINCI	Values are 0-255.	Mandatory	Extended Terminating In Capability Indicator
EOICK	Values are 0-999.	Mandatory	Extended Originating In Category Key
EOINCI	Values are 0-255.	Mandatory	Extended Originating In Capability Indicator
GCSO	Values are 0-1.	Optional	CAMEL Subscription Option when CAMEL phase 1 is not supported in the interrogating GMSC
SSLO	Values are 0-1.	Optional	CAMEL Subscription Option Subscriber State and Location Information
MCSO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 1 is not supported in the servicing MSC/VLR
MC2SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 2 is not supported in the servicing MSC/VLR
MC3SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 3 is not supported in the servicing MSC/VLR
MC4SO	Values are 0-2.	Optional	MSC/VLR CAMEL Support subscription Option when CAMEL phase 4 is not supported in the servicing MSC/VLR
GC2SO	Values are 0-1.	Optional	CAMEL subscription Option when CAMEL phase 2 is not supported in the interrogating GMSC
GC3SO	Values are 0-1.	Optional	CAMEL subscription Option when CAMEL phase 3 is not supported in the interrogating GMSC
GC4SO	Values are 0-1.	Optional	GMSC/gsmSCF CAMEL Support subscription Option when CAMEL phase 4 is supported in the servicing GMSC/gsmSCF
TIF	Values are 0-1.	Optional	Translation Information Flag
GPRSSO	Values are 0-1.	Optional	GPRS CAMEL phase3 denied Subscription Option. Application system-dependent parameter.
OSMSSO	Values are 0-2.	Optional	Originating SMS CAMEL denied Subscription Option. Application system-dependent parameter.
TSMSSO	Values are 0-2.	Optional	Terminating SMS CAMEL phase 4 denied Subscription Option. Application system-dependent parameter.
MMSO	Values are 0-1.	Optional	Mobility Management CAMEL denied Subscription Option. Application system-dependent parameter.
MTY	Values are: E = Enabling I = Inhibiting	Optional	Match Type
DNUM	Expressed as na-nb format where na can be 0-4 and nb can be 1-15 digits, *, #.	Optional	Destination Number
DLGH	Values are 1-15.	Optional	Destination number Length
FTC	Values are: N = Not forwarding F = Forwarding	Optional	Forwarding Triggering Criteria
BS	Values are TS11, TS61, TS62, TSD1, BS21, BS22, BS23, BS24, BS25, BS26, BS2G, BS31, BS32, BS33, BS34, BS3G.	Optional	Basic Service. It is used to define basic service triggering criteria.
BSG	Values are TS10, TS60, TSD0, TS20, TS30.	Optional	Basic Service Group identifier. It is used to define basic service triggering criteria.

Example:

RESP:0:MSISDN,22220000:IMSI,11110000:AUTHD,"NO ACCESS TO AUC":CAMEL,TSMSTDP,2,GSA,8888,SK,1234,DEH,1,CCH,4,ECAMEL,ETICK,0,ETINCI,0,EOICK,0,EOINCI,0:NAM,1:CAT,10:DBSG,1:OFA,0:PWD,0000:SCHAR,0-0;

6.1.6   Closed User Groups

Closed User Group (CUG) is an Ericsson-specific feature that makes it possible to group a number of subscribers with equal restrictions/possibilities.

6.1.6.1   Closed User Group Subscription

A subscriber can be a member of up to 10 CUGs. A subscriber can join or form a Closed Used Group. A Closed User Group can have different restrictions for different groups of members.

Each Closed User Group is defined by a unique Interlock Code (IC). Following restrictions are possible to attach to the CUG subscription:

1. Incoming Calls Barred within CUG (ICB)
2. Outgoing Calls Barred within CUG (OCB)
3. No restrictions within CUG (NONE)

To create a CUGSUB attribute, the following syntax is applied:

Table 36    Create CUGSUB

Parameter	Type	Occurrence	Description
index	Values are 0-32767.	Mandatory	CUG Index
ic	Value format falls into two parts that are connected with a -. The range starts from 0000-0 to 9999-65535.	Mandatory	Interlock Code
restriction	Values are ICB, OCB, or NONE.	Optional	CUG Restriction
bsg	Values are BS20, BS30, TS10, TS60or TSD0.	Optional	Basic Service Group identifier. It is attached by CUG membership.
add_bsg	Only the default value set 1 could be specified indicating that BSG is added to the CUG.	Optional	Add BSG flag

Table 37    Set CUGSUB

Parameter	Type	Occurrence	Description
index	Values are 0-32767.	Mandatory	CUG Index
restriction	Values are ICB, OCB, or NONE.	Optional	CUG Restriction
bsg	Values are BS20, BS30, TS10, TS60, or TSD0.	Optional	Basic Service Group identifier. It is attached by CUG membership.
add_bsg	If set 1 the specified BSG is added to the CUG, else if reset 0 the BSG is removed. Default value is 1.	Optional	Add BSG flag

Table 38    Delete CUGSUB

Parameter	Type	Occurrence	Description
index	Values are 0-32767.	Mandatory	CUG Index

Table 39    Create/Set/Delete CUGSUBs

Parameter	Type	Occurrence	Description
index	Values are 0-32767.	Mandatory	CUG Index
ic	Value format falls into two parts that are connected with a -. The range starts from 0000-0 to 9999-65535.	Mandatory	Interlock Code
restriction	Values are ICB, OCB, or NONE.	Mandatory	CUG Restriction
bsg	Values are BS20, BS30, TS10, TS60, or TSD0.	Optional	Basic Service Group identifier. It is attached by CUG membership.
add_bsg	If set 1 the specified BSG is added to the CUG, else if reset 0 the BSG is removed. Default value is 1.	Optional	Add BSG flag

If there is a modifying message request, creating/setting/deleting of CUGSUBs can be combined in any order.

For example: SET:HLRSUB:....:CUGSUB,DEF,12,0017–2871,ICB,BS20,DEL,1,DEL38,SET,34,OCB,TS60,0:...

The message response of a request to get a subscriber contains the CUGSUB data in following format:

Table 40    Get Subscriber Response

Parameter	Type	Occurrence	Description
index	Values are 0-32767.	Optional	CUG Index
ic	Value format falls into two parts that are connected with a -. The range starts from 0000-0 to 9999-65535.	Optional	Interlock Code
restriction	Values are ICB, OCB, or NONE.	Optional	CUG Restriction
bsg	Values are BS20, BS30, TS10, TS60, or TSD0.	Optional	Basic Service Group identifier. It is attached by CUG membership.

For example: RESP:0:...:CUGSUB, 12, 0007-98, ICB, BS20, TS20, 78, 0089-457, OCB, TS10:...

6.1.6.2   Closed User Group BSG Options

It is possible to set a HLR subscribers CUG Basic Service Group options by the attribute CUG. The options that can be attached to a CUG BSG are:

1. Access, determines the specific access for a BSG. Can be one of following: - Outgoing Access (OA) - Incoming Access (IA) - Outgoing and Incoming Access (OIA) - No access (NONE)
2. Preferential CUG index, determines the default CUG to be used by the network when no explicit CUG index is received from the mobile subscriber.

The CUG BSG options argument syntax is defined as follows:

Table 41    Closed User Group Options

Parameter	Type	Occurrence	Description
access	Values are OA, IA, OIA, or NONE.	Optional	Access attribute
pcug	Values are 0-32767, NONE.	Optional	Preferential CUG index
bsg	Values are BS20, BS30, TS10, TS60, or TSD0.	Optional	Basic Service Group

A CUG BSG options set can be used in an ordinary CREATE/SET operation, for example, SET:HLRSUB:...:CUG, IA, TS10, OA, 76, TS60:...

The message response of a request to get a subscription contains the CUG data in following format:

Table 42    CUG Response

Parameter	Type	Occurrence	Description
prov	Values are 0-1. If set to 0, the other values is not displayed.	mandatory	The Provision state of the Closed User Group BSG options.
access	Values are OA, IA, OIA, or NONE.	Optional	Access attribute
pcug	Values are 0-32767, NONE.	Optional	Preferential CUG index
bsg	Values are BS20, BS30, TS10, TS60, or TSD0.	Optional	Basic Service Group

6.1.7   Mobility Management Related IN Triggering

Table 43    Create Mobility Management Related IN Triggering Data

Parameter	Type	Occurrence	Description
DP	Values are 0-1.	Mandatory	The Detection Point which should be triggered
GSA	Digit string, 5-15 digits	Mandatory	The GSM SCF Address which points out the SCF node
SK	Values are 0-2147483647.	Mandatory	The Service Key value which points out the IN service in the SCF node
ACT	Values are 0-1.	Optional	Activate/deactivate the Mobility Management Related IN Trigger data for a specific Detection Point

Table 44    Set Mobility Management Related IN Triggering Data

Parameter	Type	Occurrence	Description
DP	Values are 0-1.	Mandatory	The Detection Point which should be triggered
GSA	Digit string, 5-15 digits	Optional	The GSM SCF Address which points out the SCF node
SK	Values are 0-2147483647.	Optional	The Service Key value which points out the IN service in the SCF node
ACT	Values are 0-1.	Optional	Activate/deactivate the Mobility Management Related IN Trigger data for a specific Detection Point

Table 45    Delete Mobility Management Related IN Triggering Data

Parameter	Type	Occurrence	Description
DP	Values are 0-1.	Mandatory	The Detection Point which should be triggered

Table 46    Set Mobility Management Related IN Triggering Data

Parameter	Type	Occurrence	Description
DP	Values are 0-1.	Mandatory	The Detection Point which should be triggered
GSA	Digit string, 5-15 digits	Mandatory	The GSM SCF Address which points out the SCF node
SK	Values are 0-2147483647.	Mandatory	The Service Key value which points out the IN service in the SCF node
ACT	Values are 0-1.	Mandatory	Activate/deactivate the Mobility Management Related IN Trigger data for a specific Detection Point

6.1.7.1   Create a Mobility Management Related IN Trigger

1. When defining the Mobility Management Related IN Trigger data, the Detection Point, the GSM SCF address, and the service key is to be provided in the request. For example:

   SET:HLRSUB:MSISDN,46455381234:MOBINT,DEF,DP,1,

   GSA,491000000,SK,12345:...

   This example defines a Mobility Management Related IN Trigger on the Detection Point 1 for the subscriber with MSISDN 46455381234. The GSM SCF address to the IN service is 491000000 and the Service Key is 12345.

6.1.7.2   Set Mobility Management Related IN Trigger Data

1. It is possible to set the Mobility Management Related IN Trigger data which should be used for a specific Detection Point. It is also possible to activate/deactivate a specific Detection Point. For example:

   SET:HLRSUB:MSISDN,46455381234:MOBINT,

   SET,DP,1,SK,565656,ACT,1:...

   The Mobility Management Related IN Trigger data which points out the IN service that should be used when Detection Point 1 is triggered points on the new Service Key value 565656 and are activated.

6.1.7.3   Delete Mobility Management Related IN Trigger Data

1. The deletion of the Mobility Management Related IN Trigger data is done by using the Detection Point as an identifier. For example:

   SET:HLRSUB:MSISDN,46455381234:MOBINT,DEL,DP,1:...

   This example removes the Mobility Management Related IN Trigger data for Detection Point 1.

6.1.8   Remove References of IMSI Changeover

If the Changeover procedure, (see Section 8.1) is in the state `Executed' or `Forced' the new IMSI is being in operation but the reference to the old IMSI is still being kept. This reference can be removed to complete the whole procedure and to free the old IMSI for further use. If the Changeover procedure is not in the state `Executed' or `Forced' this request fails.

A delete associated old IMSI argument is defined as follows:

Assoc old IMSI = ASSOCOLDIMSI, DEL

This argument can only be assigned to a SET operation, for example, SET:HLRSUB:.....:ASSOCOLDIMSI, DEL:...;

6.1.9   GPRS

GPRS is a set of GSM phase 2+ bearer services that allow subscribers to send and receive data in an end-to-end packet transfer mode. It enables efficient use of network resources for packet mode data applications that exhibit characteristics such as non-periodic data transmission, frequent transmission of small volumes of data, or infrequent transmission of larger volumes of data. The permanent subscriber data for a GPRS subscription is stored in the HLR. A Network Access Mode (NAM) decides what type of network access the subscriber has. It can be:

• Access to non-GPRS network only
• Access to GPRS network only
• Access to both non-GPRS network and GPRS network

The GPRS subscription data is handled in the HLRSUB MO in Dynamic Activation. To differentiate the GPRS data from non-GPRS as well as to provide a future-proof solution, two tags are defined: GPRS, starting tag of all GPRS subscription data and PDPCONTEXT, starting tag of the contents of PDP context. Below the syntax of GPRS subscription data administration is described. Definition of attributes and their value is described in Table 63.

6.1.9.1   Create GPRS Subscription Data

Table 47    Create GPRS Subscription Data

Parameter	Type	Occurrence	Description
APNID	Integer 0-16383 or NS (Not Subscribed)	Mandatory	Access Point Name Identifier
PDPADD	IP address	Optional	Packet Data Protocol Address
PDPID	Values are 1-50.	Mandatory	Subscriber PDP Context Identifier
VPAA	Values are 0-1.	Optional	Visited Public Land Mobile Network Address Allowed
EQOSID	Integer 0-4095	Mandatory	Extended Quality of Service Identifier
PDPTY	Values are IPv4, IPv6 address or ERASE	Optional	PDP Context Type
PDPCH	The format is pdppi[-pdpgb]: pdppi = PDP context Profile Index (Integer 0-15) Optional value pdpgb = PDP context GSN Behavior index (Integer 0–4095).	Optional	PDP Context Charging Characteristics

Creating a subscriber with only GPRS Subscription data:

CREATE:HLRSUB:MSISDN,46455381234:IMSI,12345678933333:NAM,2:

TSMO,0:GPRS,DEF,PDPCONTEXT,APNID,1,PDPADD,136.225.1.1,EQOSID,

1,PDPCH,1,PDPTY,IPV4,DEF,PDPCONTEXT,APNID,2,EQOSID,2,

PDPCH,2,PDPTY,PPP,VPAA,0,DEF,PDPCONTEXT,APNID,2047,

PDPADD,136.225.1.2,EQOSID,4095,PDPCH,15,VPAA,1,PDPID,1;

Creating a subscriber with both GPRS and non-GPRS Subscription data:

CREATE:HLRSUB:MSISDN,46455381234:IMSI,12345678933333:

AMSISDN,DEF,46455381235,9:CAT,10:CAW,1:NAM,0:TSMO,1:GPRS,

DEF,PDPCONTEXT,APNID,1,PDPADD,136.225.1.1,EQOSID,1,PDPCH,1,

PDPTY,IPV4,DEF,PDPCONTEXT,APNID,2,PDPCH,2,PDPTY,PPP,

VPAA,0,DEF,PDPCONTEXT,APNID,2047,PDPADD,

136.225.1.2,EQOSID,4095,PDPCH,15,VPAA,1,PDPID,1;

6.1.9.2   Set GPRS Subscription Data

Note:  

• At least one parameter in {APNID, EQOSID, PDPTY, PDPADD, PDPCH, VPAA} should be provided in the GPRS Set operation.
• EPDPIND and EPDPADD is valid since HLR UDC 11B.

Table 48    Set GPRS Subscription Data

Parameter	Type	Occurrence	Description
APNID	Integer 0-16383, NS (Not Subscribed)	Optional	Access Point Name Identifier
EPDPIND	Boolean	Optional	Extend PDP Context Indicator
EPDPADD	Values are IPv4, IPv6 address, or ERASE	Mandatory	Extend PDP Context Address
PDPADD	Possible values are IP Address or ERASE	Optional	Packet Data Protocol Address
PDPID	Values are 1-50.	Mandatory	Subscriber PDP Context Identifier
VPAA	Values are 0-1.	Optional	Visited Public Land Mobile Network Address Allowed
EQOSID	Integer 0-4095	Optional	Extended Quality of Service Identifier
PDPTY	Values are IPV4, IPV6, or PPP.		PDP Context Type
PDPCH	The format is pdppi[-pdpgb]: pdppi = PDP context Profile Index (Integer 0-15) Optional value pdpgb = PDP context GSN Behavior index (Integer 0–4095).	Optional	PDP Context Charging Characteristics

Examples:

SET:HLRSUB:MSISDN,22220000:GPRS,SET,PDPCONTEXT,PDPID,1,APNID,1,PDPADD,1.1.1.1,EQOSID,1,PDPCH,1-1,PDPTY,IPV4,VPAA,0;

SET:HLRSUB:MSISDN,22220000:GPRS,SET,PDPCONTEXT,PDPID,1,APNID,WILDCARD,PDPCH,ERASE,PDPADD,ERASE;

SET:HLRSUB:MSISDN,22220000:GPRS,SET,PDPCONTEXT,PDPID,1,EPD PIND,0,EPDPADD,1A25.FFD2.23BC.121d.78ee.3EE0.1eee.652A;

6.1.9.3   Delete GPRS Subscription Data

Table 49    Delete GPRS Subscription Data

Parameter	Type	Occurrence	Description
PDPID	Values are 1-50.	Mandatory	Subscriber PDP Context Identifier

Deleting GPRS Subscription data for a PDP context matching one PDPID:

SET:HLRSUB:MSISDN,46455381234: GPRS,DEL,PDPCONTEXT,PDPID,1;

6.1.9.4   Get GPRS Subscription Data

Table 50    Get GPRS Subscription Data

Parameter	Type	Occurrence	Description
APNID	Integer 0-16383 or NS (Not Subscribed).	Mandatory	Access Point Name Identifier
PDPADD	IP address	Optional	Packet Data Protocol Address
VPAA	Values are 0-1.	Optional	Visited Public Land Mobile Network Address Allowed
EQOSID	Integer 0-4095	Mandatory	Extended Quality of Service Identifier
PDPTY	Values are IPV4, IPV6, or PPP.	Optional	PDP Context Type
PDPCH	The format is pdppi[-pdpgb]: pdppi = PDP context Profile Index (Integer 0-15) Optional value pdpgb = PDP context GSN Behavior index (Integer 0–4095).	Optional	PDP Context Charging Characteristics
PDPID	Values are 1-50.	Mandatory	Subscriber PDP Context Identifier

6.1.10   Gateway Mobile Location Center (GMLC) Address

Gateway Mobile Location Center is the PLMN node that interfaces to location applications which request GSM Location Services (LCS) for a specific subscriber. The GMLC can perform location application authorizations to check the validity of the requesting application. There is wide range of location applications for the geographical positioning services, such as positioning of vehicles for transport and taxi companies, positioning of emergency calls, positioning of stolen vehicles, detection of hot spots for micro-cells and so on.

6.1.10.1   Create Subscriber GMLC Address

Table 51    Create Subscriber GMLC Address

Parameter	Type	Occurrence	Description
GMLCID	Values are 0-255.	Mandatory	GMLC Address Identifier
HGMLCID	Values are 0-255.	Optional	Home GMLC address Identifier
PPRID	Values are 0-255.	Optional	Privacy Profile Register address Identifier

1. A mobile subscriber in the HLR can be assigned GMLC address.

   CREATE:HLRSUB:IMSI,12345678933333:MSISDN,3417429013:

   GMLCA,DEF,GMLCID,33:...

   GMLC address with identifier 33 is assigned to the mobile subscriber with MSISDN 3417429013.

Note:  

Up to 5 GMLC addresses can be assigned to a mobile subscriber.

6.1.10.2   Delete Subscriber GMLC Address

Table 52    Delete Subscriber GMLC Address

Parameter	Type	Occurrence	Description
GMLCID	Values are 0-255 or ALL.	Mandatory	GMLC Address Identifier

1. A mobile subscriber's GMLC address data previously defined can be removed in the HLR.

   SET:HLRSUB:MSISDN,49513789000:GMLCA,DEL,PPRID;

   SET:HLRSUB:MSISDN,49513789000:GMLCA,DEL,GMLCID,125;

   GMLC address with identifier 125 is removed from the GMLC addresses of the mobile subscriber with MSISDN 49513789000.

Note:  

It is possible to remove all GMLC addresses for a mobile subscriber when GMLCID takes a value ALL.

6.1.10.3   Get Subscriber GMLC Address Response

Table 53    Get Subscriber GMLC Address

Parameter	Type	Occurrence	Description
GMLCID	Values are 0-255.	Mandatory	GMLC Address Identifier
GMLCADD	Digit string, 3–15 digits	Mandatory	GMLC Address Data
HGMLCID	Values are 0-255.	Optional	Home GMLC address Identifier
HGMLCADD		Optional	Home GMLC Address
PPRID	Values are 0-255.	Optional	Privacy Profile Register address Identifier
PPRADD		Optional	Privacy Profile Register Address

6.1.11   Location Services (LOCSERVICES)

Location Services are services related to the location of subscribers in the PLMN. For example, universal type service, related call service, unrelated call service, and related operator privacy .

Table 54    Create, Set, and Delete Subscriber Location Services Data

Parameter	Type	Occurrence	Description
prov	Values are: 0 = not activated 1 = activated	Optional
intidlist	To add value use +0, +1, +2, +3, +4, to remove value use -0, -1, -2, -3, -4.	Optional	Internal Identity List value. A list of one or more types of LOCSERVICES clients that are allowed to locate the mobile subscriber.
mocllist	The possible values are +ASL, +BSL, +TTP in definition, and -ASL, -BSL, -TTP, or -ALL in deletion.	Optional	LOCSERVICES Mobile Originating Class List
eadd	Digit string, 3–15 digits If parameter EADD is entered, one external address is added either for call/session unrelated LCS privacy class (CUNRL) or call/session related LCS privacy class (CREL). If parameter EADD is entered and both optional parameters CREL and CUNRL are omitted, then the external address is added to call/session unrelated LCS privacy class.	Mandatory	External LOCSERVICES client Address
gres	Values are 0, 1, 9.	Optional	Restriction on the Gateway Mobile Location Center
notf	Values are 0-4. Default is 0.	Optional	Location request restriction related to the Notification to the mobile subscriber
isCREL	Values are: 1 = CREL 0 = CUNRL (default)	Optional
servt	Values are 0-20 or 64-127.	Optional	Service Type. List of one or more service types for which an LCS client is allowed to locate the mobile subscriber.

0	Emergency services
1	Emergency alert services
2	Person tracking
3	Fleet management
4	Asset management
5	Traffic congestion reporting
6	Roadside assistance
7	Routing to nearest commercial enterprise
8	Navigation
9	City sightseeing
10	Localized advertising
11	Mobile yellow pages
12	Traffic and public transportation
13	Weather
14	Asset and service finding
15	Gaming
16	Find your friend
17	Dating
18	Chatting
19	Route finding
20	Where-am-I
64-127	Operator-specific service types
ALL	All service (only used in DEL suboperation).

Note:  

For CREL and CUNRL initialization and update, the same CAI requests are used:

SET:HLRSUB:MSISDN,msisdn:LOCSERVICE,SET,CREL,1,NOTF,<notf>;

SET:HLRSUB:MSISDN,msisdn:LOCSERVICE,SET,CUNRL,1,NOTF,<notf>;

Dynamic Activation first sends the MML update request. If it is successful, no more MML request is sent. If it fails, Dynamic Activation sends the MML initialization request.

6.1.11.1   Create Subscriber Location Services Data

External Location Services data for a mobile subscriber can be defined.

CREATE:HLRSUB:IMSI,12345678933333:MSISDN,12345678:

LOCSERVICES,SET,MOCLLIST,+ASL,+BSL,

DEF,EADD,333,SET,SERVT,1,GRES,1,NOTF,1...

The External LOCSERVICES client address 333 and the LOCSERVICES mobile originating classes ASL and BSL for the mobile subscriber with MSISDN 12345678 are defined.

6.1.11.2   Set Subscriber Location Services Data

Location Services classes data for a mobile subscriber can be set.

SET:HLRSUB:IMSI,12345678933333:MSISDN,12345678:

LOCSERVICES,SET,CREL,1,NOTF,1:...

Location request restriction for the call-related privacy class already defined for the subscriber with MSISDN 12345678 is set to location request allowed with notification.

6.1.11.3   Delete Subscriber Location Services Data

Location Services classes data for a mobile subscriber can be removed.

SET:HLRSUB:IMSI,12345678933333:MSISDN,12345678:

LOCSERVICES,DEL,EADD,333,CREL,1...

Call related Location Services privacy class for the mobile subscriber with MSISDN 12345678 and external LOCSERVICES address 333 is ended.

6.1.11.4   Get Subscriber Location Services Data Response

Table 55    Get Subscriber LCOSERVICES Data Response

Parameter	Type	Occurrence	Description
prov	Values are: 0 = not activated 1 = activated	Optional
intidlist	Values are 0-4.	Optional	Internal Identity List value
mocllist	Values are ASL, BSL, TTP.	Optional	LCS Mobile Originating Class List
eadd	Digit string, 3–15 digits	Mandatory	External LOCSERVICES client Address
gres	Values are 0, 1, 9.	Optional	Restriction on the Gateway Mobile Location Center
notf	Values are 0-4. Default is 0.	Optional	Location request restriction related to the Notification to the mobile subscriber
isCREL	Values are: 1 = CREL 0 = CUNRL (default)	Optional
servt	Values are 0-20 or 64-127.	Optional	Service Type. List of one or more service types for which an LCS client is allowed to locate the mobile subscriber.

0	Emergency services
1	Emergency alert services
2	Person tracking
3	Fleet management
4	Asset management
5	Traffic congestion reporting
6	Roadside assistance
7	Routing to nearest commercial enterprise
8	Navigation
9	City sightseeing
10	Localized advertising
11	Mobile yellow pages
12	Traffic and public transportation
13	Weather
14	Asset and service finding
15	Gaming
16	Find your friend
17	Dating
18	Chatting
19	Route finding
20	Where-am-I
64-127	Operator-specific service types
ALL	All service (only used in DEL suboperation).

6.1.12   Spatial Trigger Support (SPATIALTRIGGER)

6.1.12.1   Create/Set/Delete Subscriber Spatial Trigger Data

Table 56    Create/Set/Delete Subscriber Spatial Trigger Data

Parameter	Type	Occurrence	Description
STE	Numeral 0–15	Mandatory	Spatial Triggers Event
GMLCID	Numeral 0–255	Mandatory	Gateway Mobile Location Center (GMLC) address Identifier

Examples:

...:SPATIALTRIGGER,DEF,STE,12,GMLCID,200:...

...:SPATIALTRIGGER,SET,STE,12,GMLCID,201:...

6.1.12.2   Syntax of Retrieved Subscriber Spatial Trigger Data

Table 57    Retrieve Subscriber Spatial Trigger Data

Parameter	Type	Occurrence	Description
STE	Numeral 0–15	Mandatory	Spatial Triggers Event
GMLCID	Numeral 0–255	Mandatory	Gateway Mobile Location Center (GMLC) address Identifier
GMLCA		Mandatory	Gateway Mobile Location Center (GMLC) address

Example:

RESP:0:...:SPATIALTRIGGER,STE,12,GMLCID,200,GMLCA,49101924113:...

6.1.13   SMS Spam Control

SMS Spam control prevents undesired SMS from reaching the subscriber.

6.1.13.1   Create and Delete Subscriber SMS Spam Data

Table 58    Create and Delete Subscriber SMS Spam Data

Parameter	Type	Occurrence	Description
SCADDS		Mandatory	Short Message Service Center (SMSC) Address Series

6.1.13.2   Syntax of Retrieved Subscriber SMS Spam Data

Table 59    Retrieve Subscriber SMS Spam Data

Parameter	Type	Occurrence	Description
SCADDS		Mandatory	Short Message Service Center (SMSC) Address Series
ACTIVE		Mandatory	Active status

6.1.14   Multiple SIM

Multiple SIM defines multiple subscription data in the HLR.

Note:  

• If MCH is included, the multiple SIM group is created. If the group exists, a new subscription is added to the multiple SIM group.
• If MCH is not included, a new subscription is added to the multiple SIM group.

6.1.14.1   Create Subscriber Multiple SIM Data

Table 60    Create Subscriber Multiple SIM Data

Parameter	Type	Occurrence	Description
imsi	String, 6-15 digits	Mandatory	The IMSI number of the subscription to be defined
mch	Enumeration value LOC USSD	Mandatory	Multiple subscription activation mechanism
zoneid	Integer 0-65535	Optional	This attribute indicates to what geographical area the MultiSC or the association belongs
acimsi	String, 6-15 digits, each digit 0–9.	Optional	Active IMSI
mMsisdn	String, 6-15 digits, each digit 0–9.	Optional	Master MSISDN

6.1.14.2   Set and Delete Subscriber Multiple SIM Data

Table 61    Set and Delete Subscriber Multiple SIM Data

Parameter	Type	Occurrence	Description
imsi	String, 6-15 digits	Mandatory	The IMSI number of the subscription to be defined
mch	Enumeration value LOC USSD	Optional	Multiple subscription activation mechanism
zoneid	Integer 0-65535	Optional	This attribute indicates to what geographical area the MultiSC or the association belongs
acimsi	String, 6-15 digits, each digit 0–9.	Optional	Active IMSI
mMsisdn	String, 6-15 digits, each digit 0–9.	Optional	Master MSISDN

6.1.14.3   Subscriber Multiple SIM Data Response

Table 62    Subscriber Multiple SIM Data Response

Parameter	Type	Occurrence	Description
imsi	String, 6-15 digits	Mandatory	The IMSI number of the subscription to be defined.
active	String	Mandatory	Active Status
mch	Enumeration value: LOC USSD	Mandatory	Multiple subscription activation mechanism
zoneid	Integer 0-65535	Optional	This attribute indicates to what geographical area the MultiSC or the association belongs