Contents

1   Introduction

This section is an introduction to this document. It contains information about the prerequisites, purpose, scope, and target group for the document. This section also contains explanations of typographic conventions used in this document.

1.1   Purpose and Scope

This document describes the supported MML commands that can be used for provisioning of layered Authentication Center (AUC-FE) and layered Home Location Register (HLR-FE). The document also contains commands that have different characteristics internally in the Ericsson™ Dynamic Activation (EDA) system, individual and common data commands. Some of the commands are in the monolithic HLR considered as both individual and massive commands. This document lists only the individual commands. Additional Man-Machine Language (MML) commands, other than the ones mentioned in this document, are possible to add.

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
• Network Administrator

1.3   Typographic Conventions

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

In addition to the writing conventions mentioned above, the following applies:

• HLR-FE is referred to as HLR throughout this document.
• AUC-FE is referred to as AUC throughout this document.

For information about glossary and terms throughout this document, see Glossary of Terms and Acronyms, Reference [2].

1.4   Prerequisites

To use this document fully, users must meet the following prerequisites:

• Basic knowledge about the Dynamic Activation product
• For detailed descriptions about the parameters mentioned in this document, refer to HLR specific documentation.

2   Communication Protocol

The MML is a generic interface that has no dependencies between any data model and the data being sent and received.

The following are basic features of the MML:

• Synchronous operation; one command can be entered in one session.
• ASCII-character-based presentation

Note:  

Long client waiting times:

Depending on connection robustness configuration, the NE response time can result in long MML client waiting times. For more information, see Function Specification Resource Activation, Reference [7].

For some commands, a massive search is requested from CUDB and therefore the interface that is synchronized is waiting for the response to be processed. This can result in long MML client waiting times.

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

• Direct Socket (Raw Socket)
• TELNET
• SSH

2.1   Direct Socket

The Direct Socket interface is a raw TCP socket over IP. It is a connection-oriented protocol providing a reliable, full-duplex byte stream for a user process. TCP takes care of communication details such as acknowledgments, timers, and retransmissions.

2.2   TELNET

Standard telnet procedures are used to open a connection. Each end is assumed to act as a network virtual terminal. The client is always the initiating side and option negotiation can take place within the structure of the TELNET Protocol, see http://www.faqs.org/rfcs/rfc854.html, Reference [10]. Any side can choose to clear the connection.

The MML interface supports only the telnet options Suppress GO Ahead and Echo.

• Negotiating telnet options:
  • Suppress GO Ahead

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

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

  • Echo

    Sent by the client or server for the use of telnet echo. The echo party transmit back the data characters it receives to the other party. It is normally used by clients to not show entered passwords in clear text on the screen. The echo party replaces the password characters instead in the echoing with stars "*" that is printed on the client side.

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

2.3   SSH

Secure Shell (SSH) is a cryptographic network protocol for secure data communication between two networked computers that connects, through a secure channel over an insecure network, a server and a client running SSH server and SSH client programs, respectively.

The client is always the initiating side and option negotiation can take place within the structure of the SSH Protocol. Any side can choose to clear the connection.

For more information, see http://www.ietf.org/rfc/rfc4251.txt, Reference [11].

2.4   Ports

The default port for the MML interface is 8010 for TELNET, and 8111 for SSH.

2.5   Login Procedure

The login procedure for TELNET is as follows:

USERCODE: <username>
PASSWORD: <password>
DOMAIN: <CR>
MA MML PAGE 1
<

The login procedure for SSH is as follows:

login as: <username>
<username>@localhost's password:<password>
MA MML PAGE 1
<

2.5.1   Login Errors

This section contains information about the errors that can occur in a login attempt:

2.6   Logout Procedure

The logout procedure is as follows:

< EXIT;

LOGGED OFF
<Connection closed by foreign host.
CL24-PL-3:~ #

2.7   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 the port on every processing node. The maximum number of connections allowed can be configured by system administrators. For further information on how to use concurrent sessions, see System Administrators Guide for Native Deployment, Reference [3], or System Administrators Guide for Virtual and Cloud Deployment, Reference [4].

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 may or may not receive an error code back.

2.8   Queued Printouts

Printouts of commands that respond with RESULT PRINTOUT are queued and the terminal must be released for the printout to be printed.

To release the terminal and receive queued printouts, press CTRL-D (EOT).

For ORDERED commands, it is possible to receive NOT ACCEPTED FORMAT ERROR, either directly (without ORDERED) or after ORDERED is returned.

Note:  

The terminal is released and queued printouts are printed. No new commands are accepted when a queued printout is pending.

After the printout, press ENTER (NL) to receive a prompt, and resume with the command input.

The following commands can respond with RESULT PRINTOUT:

Note:  

They all have ORDERED in the Procedure Printout. As an example, see Section 4.1.1.2.2.

• AGAAC
• AGSUC
• HGAPE
• HGAPP^*
• HGLDP
• HGMSP
• HGPDP
• HGSGP
• HGPSP^*

Note:  

Commands with ^* do not return ORDERED by default. Users can change the default behavior by editing the file mml.properties. For example, by adding HGAPP_EOT=true at the designated EOT section in mml.properties.

For detailed instructions, refer to System Administrators Guide for Native Deployment, Reference [3], or System Administrators Guide for Virtual and Cloud Deployment, Reference [4].

3   MML Command Syntax

This section contains some general information about the MML commands.

3.1   Command Syntax

This section describes the syntax for the MML commands.

Each command is represented by a short name (five letters). For example, Set Subscriber Data has the short name HGSDC. The short name is always the one written in the command prompt. The following is an example of the command HGSDC:

>HGSDC:MSISDN=123456789012345,SUD=CFU-2;

3.1.1   Delimiters

The following table contains delimiters for the MML commands.

3.1.2   Command Descriptions

Note:  

The Command Descriptions throughout this document apply for the layered solution. Any deviations from the classic MML commands are shown for each command in their respective subsection.

The following is an example of the Set Subscriber Data Command Description.

                    �               �
                    �SUD=sud        �
HGSDC:MSISDN=msisdn,+               +;
                    �PROFILE=profile�
                    �               �

Note:  

There is no need to enter the parameters in the order they appear in the Command Description.

Table 2 explains how the Command Description is built.

[A]

� �
�A�
� �
�B�
� �

� �
�A�
+ +
�B�
� �

A=a

Note:  

The Command Description syntaxes can be nested inside each other.

4   MML AUC Commands

This section covers the supported individual MML AUC commands. Each subchapter contains the Command Description and parameter information for the specific command.

For information about the different fault types and error codes, see Section 7.

Note:  

If not explicitly stated otherwise, Check Printout does not apply.

4.1   AGAA: Authentication and Key Agreement Algorithm

This section covers the following MML AUC commands:

• Authentication Center, Authentication and Key Agreement Algorithm, Change (AGAAC) (Section 4.1.1)
• Authentication Center, Authentication and Key Agreement Algorithm, Print (AGAAP) (Section 4.1.2)

4.1.1   Authentication Center, Authentication and Key Agreement Algorithm, Change (AGAAC)

This command changes the AKA Algorithm indicator for those WCDMA subscribers whose Function Set (FSET) supports the two algorithm framework feature in Authentication Center (AUC). FSET supporting the two algorithm framework feature is determined by an AXE parameter.

Deviations:

• AKAALGIND does not support value DEFAULT.
• The AGAAC command does not support the CONTINUE parameter.
• Only the individual subscriber version of the command is supported.

4.1.1.1   AGAAC Command Description

AGACC:IMSIS=imsi,AKAALGIND=akaalgind;

Example of an AGAAC Command

AGAAC:IMSIS=123456789012345,AKAALGIND=1;

The Authentication and Key Agreement (AKA) algorithm indicator of the subscribed Wideband Code Division Multiple Access (WCDMA) International Mobile Subscriber Identity (IMSI) number 123456789012345 and associated FSET supporting two algorithm framework feature is changed to AKA algorithm 1.

4.1.1.1.1   AGAAC Subscription Parameters

The following table explains the parameters for the AGAAC Subscription command.

4.1.1.2   AGAAC Printout

This section list all AGAAC printouts.

4.1.1.2.1   Check Printout

Yes.

4.1.1.2.2   Procedure Printout

�                         �
�ORDERED                  �
+                         +
�NOT ACCEPTED             �
�fault type               �
�                         �

4.1.1.2.3   Answer Printout

This command has no answer printouts.

4.1.1.2.4   Result Printout

Result printout is supported.

AUC AKA ALGORITHM CHANGE RESULT
 
�                           �
�EXECUTED                   �
�[*** NOT LOGGED FOR BACKUP]�
+                           +
�NOT EXECUTED               �
�fault type                 �
�                           �
 
END

This printout has no parameters.

• EXECUTED - The command has been executed.
• NOT EXECUTED - The command has not been executed.

4.1.2   Authentication Center, Authentication and Key Agreement Algorithm, Print (AGAAP)

This command prints subscription and Authentication and Key Agreement (AKA) Algorithm data for UMTS mobile subscribers in the AUC.

Deviations:

• Only the individual subscriber version of the command is supported.

4.1.2.1   AGAAP Command Description

AGAAP:IMSIS=imsi;

Example of an AGAAP Command

AGAAP:IMSIS=123456789012345;

The subscription and AKA Algorithm data for subscribed UMTS IMSI numbers 123456789012345 are printed.

4.1.2.1.1   AGAAP Subscription Parameters

The following table explains the parameters for the AGAAP Subscription command.

4.1.2.2   AGAAP Printout

This section lists all AGAAP printouts.

4.1.2.2.1   Procedure Printout

NOT ACCEPTED
fault type

4.1.2.2.2   Answer Printout

The AKAALGIND parameter cannot have value N/A or DEFAULT in User Data Consolidation (UDC).

 AUC AKA ALGORITHM SUBSCRIPTION DATA

 IMSI
 EKI                               KIND  FSETIND  A4IND  AKAALGIND
 AMF
 imsi
 eki                               kind  fsetind  a4ind  akaalgind
 amf

[NONE]
 
 END

The following table contains information about the parameters in the answer printout:

4.1.2.2.3   Result Printout

This command has no result printouts.

4.2   AGSU: Subscription

This section covers the following MML AUC commands:

• Authentication Center, Subscription, Initiate (AGSUI) (Section 4.2.1)
• Authentication Center, Subscription, Change (AGSUC) (Section 4.2.2)
• Authentication Center, Subscription, End (AGSUE) (Section 4.2.3)
• Authentication Center, Subscription, Print (AGSUP) (Section 4.2.4)

4.2.1   Authentication Center, Subscription, Initiate (AGSUI)

This command initiates the subscription of a mobile subscriber in the AUC.

4.2.1.1   AGSUI Command Description

                                 ��                ��
                                 ��,A3A8IND=a3a8ind��
AGSUI:IMSI=imsi,EKI=eki,KIND=kind�+                +�
                                 ��,FSETIND=fsetind��
                                 ��                ��
[,A4IND=a4ind][,ZONEID=zoneid][,RID=rid];

Example of an AGSUI Command

AGSUI:IMSI=123456789012345,KIND=23,A3A8IND=1,A4IND=2,
      EKI=1234567890ABCDEF1234567890ABCDEF;

The subscription of a mobile subscriber with IMSI 123456789012345, EKI 1234567890ABCDEF1234567890ABCDEF, KIND 23, A3A8IND 1, A4IND 2 is initiated. The GSM AKA type is used.

4.2.1.1.1   AGSUI Subscription Parameters

The following table explains the parameters for the AGSUI Subscription command.

4.2.1.2   AGSUI Printouts

This section list all AGSUI printouts.

4.2.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

4.2.1.2.2   Answer Printout

This command has no answer printouts.

4.2.1.2.3   Result Printout

This command has no result printouts.

4.2.2   Authentication Center, Subscription, Change (AGSUC)

This command changes subscriber data in the AUC.

Deviations:

• The AGSUC command does not support the CONTINUE parameter.
• Only the individual subscriber version of the command is supported

4.2.2.1   AGSUC Command Description

AGSUC:IMSIS=imsi,AMF=amf,FSETIND=fsetind;

Example of an AGSUC Command

AGSUC:IMSIS=123456789012345,AMF=14532,FSETIND=2;

The Authentication Management Field (AMF) of the subscribed WCDMA IMSI numbers 123456789012345 and FSETIND 2 is changed to 14532.

4.2.2.1.1   AGSUC Subscription Parameters

The following table explains the parameters for the AGSUC Subscription command.

4.2.2.2   AGSUC Printouts

This section list all AGSUC printouts.

4.2.2.2.1   Procedure Printout

�                         �
�ORDERED                  �
+                         +
�NOT ACCEPTED             �
�fault type               �
�                         �

4.2.2.2.2   Answer Printout

This command has no answer printouts.

4.2.2.2.3   Result Printout

Result printout is supported.

 AUC SUBSCRIPTION DATA CHANGE RESULT 
 
�                                   �
�EXECUTED                           �
�[*** NOT LOGGED FOR BACKUP]        �
+                                   +
�NOT EXECUTED                       �
�fault type                         �
�                                   �
 
 END

This printout has no parameters.

• EXECUTED - The command has been executed.
• NOT EXECUTED - The command has not been executed.

4.2.3   Authentication Center, Subscription, End (AGSUE)

This command ends the subscription of a mobile subscriber in the AUC.

This command is always capable of removing an AUC subscription, even if a previous AGSUI or AGSUE has failed.

4.2.3.1   AGSUE Command Description

AGSUE:IMSI=imsi;

Example of an AGSUE Command

AGSUE:IMSI=123456789012345;

The subscription of mobile subscriber with IMSI 123456789012345 is ended.

4.2.3.1.1   AGSUE Subscription Parameters

The following table explains the parameters for the AGSUE Subscription command.

4.2.3.2   AGSUE Printout

This section list all AGSUE printouts.

4.2.3.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

4.2.3.2.2   Answer Printout

This command has no answer printouts.

4.2.3.2.3   Result Printout

This command has no result printouts.

4.2.4   Authentication Center, Subscription, Print (AGSUP)

This command prints subscription data of mobile subscribers in the AUC.

Deviations:

• Only the individual subscriber version of the command is supported
• The parameter AKATYPE is not supported.

4.2.4.1   AGSUP Command Description

AGSUP:IMSIS=imsi;

Example of an AGSUP Command

AGSUP:IMSIS=123456789012345;

The subscription data for subscribed IMSI numbers 123456789012345 are printed.

4.2.4.1.1   AGSUP Subscription Parameters

The following table explains the parameters for the AGSUP Subscription command.

4.2.4.2   AGSUP Printout

This section list all AGSUP printouts.

4.2.4.2.1   Procedure Printout

NOT ACCEPTED
fault type

4.2.4.2.2   Answer Printout

 AUC SUBSCRIPTION DATA
 
 AKATYPE  [ZONEID] [RID]
 akatype  [zoneid] [rid]
                                                         �       �
                                                         �A3A8IND�
 IMSI             EKI                               KIND +       + A4IND
                                                         �FSETIND�
                                                         �       �
                 �   �
                 �AMF�
                 �   �
                                                         �       �
                                                         �a3a8ind�
 imsi             eki                               kind +       + a4ind
                                                         �fsetind�
                                                         �       �
                 �   �
                 �amf�
                 �   �
[NONE]

 END

The following table contains information about the parameters in the answer printout

4.2.4.2.3   Result Printout

This command has no result printouts.

5   MML HLR Commands

This section covers the supported individual MML HLR commands. Each subchapter contains the Command Description parameter information for the specific command.

For information about the different fault types and error codes, see Section 7.

Note:  

If not explicitly stated otherwise, Check Printout does not apply.

5.1   HGAP: Access Point Name

This section covers the following MML HLR commands:

• Home Location Register, Access Point Name, Initiate (HGAPI) (Section 5.1.1)
• Home Location Register, Access Point Name, Change (HGAPC) (Section 5.1.2)
• Home Location Register, Access Point Name, End (HGAPE) (Section 5.1.3)
• Home Location Register, Access Point Name, Print (HGAPP) (Section 5.1.4)

5.1.1   Home Location Register, Access Point Name, Initiate (HGAPI)

This command initiates an APN in the HLR.

The entered APN must be compliant with the following syntax:

• The length of the APN cannot exceed 62 characters
• The APN consists of one or more labels separated by dots. Each label must start with a letter or a digit, end with a letter or a digit, and have as criteria characters only letters, digits, and hyphen
• APN must not start with the text RAC, LAC, SGSN, or RNC
• APN must not end in .GPRS

If the parameter APNID is entered, the APN identifier associated to the entered APN is chosen by the operator. If not an identifier is internally assigned.

Deviations:

• Monolithic HLR enforces the client to divide the APN in APN1 and APN2 if APN is longer than 41 characters. This is not the case in the Dynamic Activation interface. APN2 is only supported for backward compatible reason
• The parameter APNID is mandatory in UDC

5.1.1.1   HGAPI Command Description

HGAPI:APN1=apn1[,APN2=apn2],APNID=apnid[,HLRFEID=hlrfeid];

Example of an HGAPI Command

HGAPI:APN1="COM",APN2="PANY.COM",APNID=155,HLRFEID="FT_HLR";

The APN COMPANY.COM with APNID 155 is initiated on HLR Front End with Id FT_HLR.

5.1.1.1.1   HGAPI Parameters

The following table contains the parameters for the HGAPI command.

5.1.1.2   HGAPI Printout

This section lists all HGAPI printouts.

5.1.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.1.1.2.2   Answer Printout

This command has no answer printouts.

5.1.1.2.3   Result Printout

This command has no result printouts.

5.1.2   Home Location Register, Access Point Name, Change (HGAPC)

This command changes the APN associated to an APN identifier defined in the HLR.

The entered APN must be compliant with the following syntax:

• The length of the APN cannot exceed 62 characters
• The APN consists of one or more labels separated by dots. Each label must start with a letter or a digit, end with a letter or a digit, and have as criteria characters only letters, digits, and hyphen
• APN must not start with the text RAC, LAC, SGSN, or RNC
• APN must not end in .GPRS

Deviations:

• Monolithic HLR enforces the client to divide the APN in APN1 and APN2 if APN is longer than 41 characters. This is not the case in the Dynamic Activation interface. APN2 is only supported for backward compatible reason

5.1.2.1   HGAPC Command Description

HGAPC:APNID=apnid,APN1=apn1[,APN2=apn2][,HLRFEID=hlrfeid];

Example of an HGAPC Command

HGAPC:APNID=16000,APN1="COMMUNICATIONCENTER.2RDDEPARTMENT.",
APN2="MADRID.ES";

The APN COMMUNICATIONCENTER.2RDDEPARTMENT.MADRID.ES is associated to APNID 16000.

5.1.2.1.1   HGAPC Parameters

The following table contains the parameters for the HGAPC command.

5.1.2.2   HGAPC Printout

This section lists all HGAPC printouts.

5.1.2.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.1.2.2.2   Answer Printout

This command has no answer printouts.

5.1.2.2.3   Result Printout

This command has no result printouts.

5.1.3   Home Location Register, Access Point Name, End (HGAPE)

This command deletes an APN in the Home Location Register (HLR).

The entered APN must be compliant with the following syntax:

• The length of the APN cannot exceed 62 characters
• The APN consists of one or more labels separated by dots. Each label must start with a letter or a digit, end with a letter or a digit, and have as criteria characters only letters, digits, and hyphen
• APN must not start with the text RAC, LAC, SGSN, or RNC
• APN must not end in .GPRS

An APN can also be deleted by its corresponding APN identifier if parameter APNID is entered.

Deviations:

• Monolithic HLR enforces the client to divide the APN in APN1 and APN2 if APN is longer than 41 characters. This is not the case in the Dynamic Activation interface. APN2 is only supported for backward compatible reason

5.1.3.1   HGAPE Command Description

       �                     �
       �APN1=apn1[,APN2=apn2]�
 HGAPE:+                     +[,HLRFEID=hlrfeid];
       �APNID=apnid          �
       �                     �

Example of an HGAPE Command

HGAPE:APN1="1COMMUNICATIONCENTER.RDDEPARTMENT.MADRID.",
APN2="ES",HLRFEID="FT_HLR";

The APN 1COMMUNICATIONCENTER.RDDEPARTMENT.MADRID.ES on HLR Front End with Id FT_HLR is deleted.

5.1.3.1.1   HGAPE Parameters

The following table contains the parameters for the HGAPE command.

5.1.3.2   HGAPE Printout

This section lists all HGAPE printouts.

5.1.3.2.1   Procedure Printout

�                         �
�ORDERED                  �
+                         +
�NOT ACCEPTED             �
�fault type               �
�                         �

5.1.3.2.2   Answer Printout

This command has no answer printouts.

5.1.3.2.3   Result Printout

 HLR ACCESS POINT NAME END RESULT
 
�                                �
�EXECUTED                        �
+                                +
�NOT EXECUTED                    �
�fault type                      �
�                                �
 
 END

This printout has no parameters.

• EXECUTED - The command has been executed.
• NOT EXECUTED - The command has not been executed.

5.1.4   Home Location Register, Access Point Name, Print (HGAPP)

This command prints APN data in the HLR.

Answer printout HLR ACCESS POINT NAME DATA is received.

If parameter APN1 and, if necessary, APN2 are entered, the APN and the corresponding APN identifier are printed.

The entered APN must be compliant with the following syntax:

• The length of the APN cannot exceed 62 characters
• The APN consists of one or more labels separated by dots. Each label must start with a letter or a digit, end with a letter or a digit, and have as criteria characters only letters, digits, and hyphen
• APN must not start with the text RAC, LAC, SGSN, or RNC
• APN must not end in .GPRS

If parameter APNID is entered, the APN identifier and the corresponding APN are printed.

If parameter APNID or APN1 and, if necessary, APN2 are entered, the Mobile Subscriber ISDN Number (MSISDN) and the IMSI of the mobile subscribers that use the entered APN in any of their Packet Data Protocol (PDP) contexts, either directly assigned to the subscriber or through a PDP context profile, are printed. In case, the PDP context is assigned to the subscriber through a PDP context profile, the PDP context profile is printed. For those PDP contexts directly assigned to the subscriber, the corresponding PDP context identifiers are printed.

If parameter APNID or APN1 and, if necessary, APN2 are entered, the PDP context profiles that use the entered APN in any of their defined PDP contexts and the corresponding PDP context identifiers are printed.

In case the PDP context is assigned to the subscriber through a PDP context profile, the PDP context profile is printed.

For those PDP contexts directly assigned to the subscriber, the corresponding PDP context identifiers are printed.

Deviations:

• Monolithic HLR enforces the client to divide the APN in APN1 and APN2 if APN is longer than 41 characters. This is not the case in the Dynamic Activation interface. APN2 is only supported for backward compatible reason
• Parameters MSUSERS and PDPCPS are not supported.

5.1.4.1   HGAPP Command Description

       �                     �
       �APN1=apn1[,APN2=apn2]�
 HGAPP:+                     +[,HLRFEID=hlrfeid];
       �APNID=apnid          �
       �                     �

Example of an HGAPP Command

HGAPP:APN1="COMPANY.COM",HLRFEID="FT_HLR";

The APN COMPANY.COM and the corresponding APNID on HLR Front End with Id FT_HLR are printed.

5.1.4.1.1   HGAPP Parameters

The following table contains the parameters for the HGAPP command.

5.1.4.2   HGAPP Printout

This section lists all HGAPP printouts.

5.1.4.2.1   Procedure Printout

�                         �
�ORDERED                  �
+                         +
�NOT ACCEPTED             �
�fault type               �
�                         �

5.1.4.2.2   Answer Printout

HLR ACCESS POINT NAME DATA

 HLR ACCESS POINT NAME DATA

 APN                 APNID
 apn                 apnid

[NONE]

 END

The following table contains information about the parameters in the HGAPP answer printout:

5.1.4.2.3   Result Printout

Same as for Answer printout, see HLR ACCESS POINT NAME DATA.

5.2   HGAM: Additional MSISDN

This section covers the following MML HLR commands:

• Home Location Register, Additional MSISDN, Initiate (HGAMI) (Section 5.2.1)
• Home Location Register, Additional MSISDN, End (HGAME) (Section 5.2.2)

5.2.1   Home Location Register, Additional MSISDN, Initiate (HGAMI)

This command initiates the subscription of an additional MSISDN, which is tied to a specified Public Land Mobile Network (PLMN) Bearer Capability (BC) number, for a Mobile Subscriber (MS).

5.2.1.1   HGAMI Command Description

HGAMI:MSISDN=msisdn,AMSISDN=amsisdn,BC=bc;

Example of an HGAMI Command

HGAMI:MSISDN=345678901234567,AMSISDN=591900005020,BC=65534;

In the example above, the additional MSISDN 591900005020 is tied to the PLMN BC number 65534 and the MSISDN for the MS is 345678901234567. This command initiates the subscription of this additional MSISDN for the MS.

5.2.1.1.1   HGAMI Parameters

The following table lists the parameters for the HGAMI command.

5.2.1.2   HGAMI Printout

This section lists all HGAMI printouts.

5.2.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.2.1.2.2   Answer Printout

This command has no answer printouts.

5.2.1.2.3   Result Printout

This command has no result printouts.

5.2.2   Home Location Register, Additional MSISDN, End (HGAME)

This command ends the subscription of an additional MSISDN for a Mobile Subscriber (MS).

This command is always capable of removing an Additional MSISDN, even if a previous HGAMI or HGAME has failed.

5.2.2.1   HGAME Command Description

 HGAME:AMSISDN=amsisdn;

Example of an HGAME Command

HGAME:AMSISDN=591900005020;

In the example above, the subscription of the additional MSISDN 591900005020 is ended.

5.2.2.1.1   HGAME Parameter

The following table lists the parameter for the HGAME command.

5.2.2.2   HGAME Printout

This section lists all HGAME printouts.

5.2.2.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.2.2.2.2   Answer Printout

This command has no answer printouts.

5.2.2.2.3   Result Printout

This command has no result printouts.

5.3   HGCM: CAMEL Subscription Data

This section covers the following MML HLR commands:

• Home Location Register, CAMEL Subscription Data, Initiate (HGCMI) (Section 5.3.1)
• Home Location Register, CAMEL Subscription Data, Initiate (HGCMC) (Section 5.3.2)
• Home Location Register, CAMEL Subscription Data, Initiate (HGCME) (Section 5.3.3)
• Home Location Register, CAMEL Subscription Data, Initiate (HGCMP) (Section 5.3.4)

5.3.1   Home Location Register, CAMEL Subscription Data, Initiate (HGCMI)

This command initiates CAMEL subscription data for a mobile subscriber or for a CAMEL subscription profile.

The parameter CCH is used to indicate which CAMEL phase the subscription data is valid for.

When the parameter MMTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter MMTDP is used the CAMEL subscription data is applicable in mobility management event notifications to the GSM service control function.

When the first MMTDP is initiated, parameters SK and GSA are mandatory. For the following MMTDPs, parameters SK and GSA can be omitted or given with the same values as the first MMTDP.

It is possible to define up to ten mobility management CAMEL phase 3 subscription data for a subscriber or for a CAMEL subscription profile.

When the parameter DSTDP and DIALNUM have been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameters DSTDP and DIALNUM are used, the CAMEL subscription data is applicable for mobile originating and forwarded calls. The DIALNUM indicates if GSM service control function shall be contacted or not to trigger a dialled service for the call.

It is possible to define up to ten dialled service CAMEL phase 3 subscription data for a subscriber or for a CAMEL subscription profile.

When the parameter TSMSTDP has been given in the command, only CCH parameter value 4 is accepted. If the parameter CCH is not present, value 4 is assigned by default.

If the parameter TSMSTDP is used the CAMEL subscription data is applicable in mobile terminating SMS.

It is possible to define up to 10 terminating SMS CAMEL phase 4 subscription data for a subscriber or for a CAMEL subscription profile.

When the parameter OSMSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter OSMSTDP is used the CAMEL subscription data is applicable in mobile originating SMS.

It is possible to define up to 10 originating SMS CAMEL phase 3 subscription data for a subscriber or for a CAMEL subscription profile.

When the parameter GPRSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter GPRSTDP is used the CAMEL subscription data is applicable in the GPRS network.

It is possible to define up to ten GPRS CAMEL phase 3 subscription data for a subscriber or for a CAMEL subscription profile.

When the parameter OCTDP has been given in the command with the value 4, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in this case value 3 is assigned by default. For other value of parameter OCTDP, CCH parameter values 1, 2, 3 or 4, are accepted. If parameter CCH is not present in this case, value 1 is assigned by default.

If the parameter OCTDP is used the CAMEL subscription data is applicable for mobile originating and forwarded calls.

It is possible to define up to ten originating CAMEL subscription data per CAMEL phase for a subscriber or for a CAMEL subscription profile.

When the parameter TCTDP has been given in the command with the value 13 or 14, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in these cases values 3 is assigned by default. For other value of parameter TCTDP, CCH parameter values 1, 2, 3 or 4, are accepted. If parameter CCH is not present in this case, value 1 is assigned by default.

If parameter TCTDP is used the CAMEL subscription data is applicable for mobile terminating calls. The parameter I give the possibility to restrict the sending of terminating CAMEL subscription data for the given terminating CAMEL TDP to GMSC when the subscriber is roaming inside HPLMN.

If the parameter I is not present, default value N is assigned.

It is possible to define up to ten terminating CAMEL subscription data per CAMEL phase for a subscriber or for a CAMEL subscription profile.

When the parameter VTTDP has been given in the command, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter VTTDP is used the CAMEL subscription data is applicable for mobile terminating calls in the VMSC.

It is possible to define up to ten VMSC terminating CAMEL subscription data per CAMEL phase for a subscriber or for a CAMEL subscription profile.

When the first CAMEL subscription data is initiated for a mobile subscriber or a CAMEL subscription profile, a set of default values for CAMEL subscription options and extended CAMEL data are defined: default value 0 is assigned for each CAMEL subscription option, and value 0 (meaning not assigned) is applied to each extended CAMEL data.

5.3.1.1   HGCMI Command Description

                      �                                                   �
                      � MMTDP=mmtdp...[,SK=sk][,GSA=gsa]                  �
                      ��                           �                      �
                      ��DSTDP=dstdp,DIALNUM=dialnum�                      �
                      ��                           �                      �
                      ��TSMSTDP=tsmstdp            �                      �
                      ��                           �                      �
                      ��OSMSTDP=osmstdp            �                      �
       �             ���                           �                      �
       �MSISDN=msisdn���GPRSTDP=gprstdp            �                      �
 HGCMI:+             +,+                           +,SK=sk,GSA=gsa,DEH=deh+
       �CSP=csp      ���OCTDP=octdp                �                      �
       �             ���                           �                      �
                      ��TCTDP=tctdp[,I=i]          �                      �
                      ��                           �                      �
                      ��VTTDP=vttdp                �                      �
                      ��                           �                      �
                      �                                                   �
 
     [,CCH=cch];

Example of an HGCMI Command

HGCMI:CSP=25,OCTDP=2,SK=1234333,GSA=98765432,DEH=0,CCH=2;

The service key 1234333 and the GSM service control function address 98765432 are associated to the originating TDP 2, CAMEL phase 2, for CAMEL subscription profile number 25. If error in the dialogue between GSM service control function and GSM service switching function the call is released.

5.3.1.1.1   HGCMI Parameters

The following table explains the parameters for the HGCMI command.

(1)  dial is a text string and must use ” delimiter in MML command, for example, 3-“122#4”.

(2)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.3.1.2   HGCMI Printout

This section lists all HGCMI printouts.

5.3.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.3.1.2.2   Answer Printout

This command has no answer printouts.

5.3.1.2.3   Result Printout

This command has no result printouts.

5.3.2   Home Location Register, CAMEL Subscription Data, Change (HGCMC)

This command changes CAMEL subscription data for a mobile subscriber or for a CAMEL subscription profile.

The parameter CCH is used to indicate which CAMEL phase the changed subscription data is valid for.

When the parameter MMTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

When the parameter DSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

When the parameter TSMSTDP has been given in the command, only CCH parameter value 4 is accepted for the command. If the parameter CCH is not present, value 4 is assigned by default.

When the parameter OSMSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

When the parameter GPRSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

When the parameter OCTDP has been given in the command with the value 4, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in this case value 3 is assigned by default. For other value of parameter OCTDP, CCH parameter values 1, 2, 3 or 4 are accepted. If parameter CCH is not present in this case, value 1 is assigned by default.

When the parameter TCTDP has been given in the command with the value 13 or 14, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in this case value 3 is assigned by default. For other value of parameter TCTDP, CCH parameter values 1, 2, 3 or 4 are accepted. If parameter CCH is not present in this case, value 1 is assigned by default.

When the parameter VTTDP has been given in the command, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter SK is present, the new service key is associated to the specified TDP for the mobile subscriber or for the CAMEL subscription profile and the specified CAMEL phase. Except when the parameter MMTDP is given in the command, then the new service key is associated to all mobility management TDPs for the mobile subscriber or for the CAMEL subscription profile.

If the parameter GSA is present, the new GSM service control function address is associated to the specified TDP, for the mobile subscriber or for the CAMEL subscription profile and the specified CAMEL phase. Except when the parameter MMTDP is given in the command, then the new GSM service control function address is associated to all mobility management TDPs for the mobile subscriber or for the CAMEL subscription profile.

If the parameter DEH is present, only allowed along with parameter DSTDP, OCTDP, TCTDP, GPRSTDP, OSMSTDP, TSMSTDP, or VTTDP, the new default error handling is associated to the specified TDP, for the mobile subscriber or for the CAMEL subscription profile and the specified CAMEL phase.

If the parameter I is present, only allowed along with parameter TCTDP, the changed inhibition indicator is associated to the specified TDP, for the mobile subscriber or for the CAMEL subscription profile.

If any parameter is not present, it remains unchanged.

5.3.2.1   HGCMC Command Description

                     �                  �
                     � MMTDP=mmtdp      �
                     �                  �
                     � DSTDP=dstdp      �
                     �                  �
                     � TSMSTDP=tsmstdp  �
      �             ��                  �
      �MSISDN=msisdn�� OSMSTDP=osmstdp  ��                                  �
HGCMC:+             ,+                  ++[,SK=sk][,GSA=gsa][,DEH=deh][,I=i]+[,CCH=cch];
      �CSP=csp      �� GPRSTDP=gprstdp  ��                                  �
      �             ��                  �
                     � OCTDP=octdp      �
                     �                  �
                     � TCTDP=tctdp[,I=i]�
                     �                  �
                     � VTTDP=vttdp      �
                     �                  �

Example of an HGCMC Command

HGCMC:CSP=25,TCTDP=12,SK=250,GSA=434566765,I=N,CCH=4;

Service key 250 and the GSM service control function address 434566765 are associated to the terminating TDP 12, CAMEL phase 4, for the CAMEL subscription profile number 25. Terminating CAMEL subscription data is always sent to GMSC.

5.3.2.1.1   HGCMC Parameters

The following table contains the parameters for the HGCMC command.

(1)  If mmtdp is used, cch can only have value 3.

(2)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.3.2.2   HGCMC Printout

This section lists all HGCMC printouts.

5.3.2.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.3.2.2.2   Answer Printout

This command has no answer printouts.

5.3.2.2.3   Result Printout

This command has no result printouts.

5.3.3   Home Location Register, CAMEL Subscription Data, End (HGCME)

This command ends CAMEL subscription data for a mobile subscriber or for a CAMEL subscription profile.

The parameter CCH is used to indicate which CAMEL phase the removal of subscription data is valid for.

If the parameter CCH is omitted and no TDP is given in the command, default value 1 is assigned parameter CCH.

If parameter CCH is omitted, all the TDPs given in the same command parameter must belong to the same CAMEL phase.

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.

When the parameter MMTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter MMTDP is used, the mobility management CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 mobility management CAMEL TDPs can be specified in the command.

When the parameter DSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter DSTDP is used, the dialled service CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 dialled service CAMEL TDPs can be specified in the command.

When the parameter TSMSTDP has been given in the command, only CCH parameter value 4 is accepted. If the parameter CCH is not present, value 4 is assigned by default.

If the parameter TSMSTDP is used, the terminating SMS CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 terminating SMS CAMEL TDPs can be specified in the command.

When the parameter OSMSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter OSMSTDP is used, the originating SMS CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 originating SMS CAMEL TDPs can be specified in the command.

When the parameter GPRSTDP has been given in the command, only CCH parameter value 3 is accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter GPRSTDP is used, the GPRS CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 GPRS CAMEL TDPs can be specified in the command.

When the parameter OCTDP has been given in the command with the value 4, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in this case value 3 is assigned by default. For other value of parameter OCTDP, CCH parameter values 1, 2, 3 or 4 are accepted. If parameter CCH is not present in this case, value 1 is assigned by default.

If the parameter OCTDP is used, the originating CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 originating CAMEL TDPs can be specified in the command.

When the parameter TCTDP has been given in the command with the value 13 or 14, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present in this case value 3 is assigned by default. For other value of parameter TCTDP, CCH parameter values 1, 2, 3 or 4 are accepted. If parameter CCH is not present, value 1 is assigned by default.

If the parameter TCTDP is used, the terminating CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 terminating CAMEL TDPs can be specified in the command.

When the parameter VTTDP has been given in the command, only CCH parameter values 3 or 4 are accepted. If the parameter CCH is not present, value 3 is assigned by default.

If the parameter VTTDP is used, the VMSC terminating CAMEL subscription data is removed for a mobile subscriber or for a CAMEL subscription profile.

A maximum of 10 VMSC terminating CAMEL TDPs can be specified in the command.

All originating CAMEL phase 2, CAMEL phase 3, and CAMEL phase 4 TDPs are not allowed to be removed for a mobile subscriber or for a CAMEL subscription profile when the translation information flag is set for the subscriber or for the CAMEL subscription profile.

If several TDP values are given for a CAMEL TDP in a command and CCH parameter is not present, the command only is accepted in case that the CCH default parameter for all the TDP values is the same.

5.3.3.1   HGCME Command Description

                                �                                      �
                                ��                                    ��
                                ��,MMTDP=mmtdp...                     ��
                                ��                                    ��
                                ��,DSTDP=dstdp...                     ��
                                ��                                    ��
      �             �           ��,TSMSTDP=tsmstdp...                 ��
      �MSISDN=msisdn�           ��                                    ��
HGCME:+             +[,CCH=cch] �+,OSMSTDP=osmstdp...                 +�;
      �CSP=csp      �           ��                                    ��
      �             �           ��,GPRSTDP=gprstdp...                 ��
                                ���                ��                ���
                                ���,OCTDP=octdp... ||,TCTDP=tctdp... ���
                                ���                ��                ���
                                ��,VTTDP=vttdp...                     ��
                                ��                                    ��
                                |�                                    ��
                                �                                      �

Example of an HGCME Command

HGCME:CSP=25,CCH=2,OCTDP=ALL,TCTDP=12;

All originating CAMEL phase 2 subscription data and terminating CAMEL phase 2 subscription data with TDP 12 are removed for the CAMEL subscription profile number 25.

5.3.3.1.1   HGCME Parameters

The following table contains the parameters for the HGCME command.

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.3.3.2   HGCME Printout

This section lists all HGCME printouts.

5.3.3.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.3.3.2.2   Answer Printout

This command has no answer printouts.

5.3.3.2.3   Result Printout

This command has no result printouts.

5.3.4   Home Location Register, CAMEL Subscription Data, Print (HGCMP)

This command prints CAMEL subscription data in the HLR.

If parameter CSP is entered, answer printout HLR CAMEL SUBSCRIPTION PROFILE DATA is received. If parameter MSISDN is provided, answer printout HLR CAMEL SUBSCRIPTION DATA is received. CAMEL subscription data that is used for one or all CAMEL subscription profiles containing any CAMEL subscription data are printed.

When optional parameter OPT is given in the command, CAMEL subscription options are printed.

When optional parameter EXT is given in the command, extended CAMEL data are printed.

When optional parameter CRIT is given in the command, CAMEL triggering criteria are printed.

Deviations:

• Parameters CSP=ALL and MSISDN=ALL are not supported in the layered solution.

5.3.4.1   HGCMP Command Description

      �                                     �
      � MSISDN=msisdn [,OPT] [,EXT] [,CRIT];�
HGCMP:+                                     �
      � CSP=csp [,OPT] [,EXT] [,CRIT];      �
      �                                     �

Example of an HGCMP Command

HGCMP:CSP=21;

CAMEL subscription data for CAMEL subscription profile number 21 is printed.

5.3.4.1.1   HGCMP Parameters

The following table contains the parameters for the HGCMP command.

5.3.4.2   HGCMP Printout

This section lists all HGCMP printouts.

5.3.4.2.1   Procedure Printout

NOT ACCEPTED
fault type

5.3.4.2.2   Answer Printout

If parameter CSP is provided, the answer printout is as follows:

HLR CAMEL SUBSCRIPTION PROFILE DATA

    HLR CAMEL SUBSCRIPTION PROFILE DATA
�                                                                  � 
�   CSP                                                            � 
�   csp                                                            � 
�                                                                  � 
�   TDPTYPE  TDP  SK         GSA              DEH   CCH I  DIALNUM � 
�   tdptype  tdp  sk         gsa             [deh]  cch[i][dialnum]� 
�     .       .    .          .                .     .  .    .     � 
�     .       .    .          .                .     .  .    .     � 
�     .       .    .          .                .     .  .    .     � 
�   tdptype  tdp  sk         gsa             [deh]  cch[i][dialnum]� 
�                                                                  � 
� �                                                      �         � 
� � CAMEL SUBSCRIPTION OPTIONS                           �         � 
� �                                                      �         � 
� ��                                    ��      ��      ��         � 
� ��GCSO  MCSO  SSLO  GC2SO  MC2SO  TIF ��GPRSSO��OSMSSO��         � 
� ��gcso  mcso  sslo  gc2so  mc2so [tif]��gprsso��osmsso��         � 
� ��                                    ��      ��      ��         � 
� ��            ��            �                          �         � 
� ��GC3SO  MC3SO��GC4SO  MC4SO�                          �         � 
� ��gc3so  mc3so��gc4so  mc4so�                          �         � 
� ��            ��            �                          �         � 
� ��    � �      �                                       �         � 
� ��MMSO� �TSMSSO�                                       �         � 
� ��mmso� �tsmsso�                                       �         � 
� ��    � �      �                                       �         � 
� �                                                      �         � 
�  �                            �                                  � 
�  �EXTENDED CAMEL DATA         �                                  � 
�  �                            �                                  � 
�  �EOINCI  EOICK  ETINCI  ETICK�                                  � 
�  �eoinci  eoick  etinci  etick�                                  � 
�  �                            �                                  �

��                                                      �          � 
��  CAMEL TRIGGERING CRITERIA DATA                      �          � 
���                                                    ��          � 
��� TRIGGERING CRITERIA DATA FOR OCTDP 2               ��          � 
���                                                    ��          � 
��� MTY  DNUM               DLGH  FTC  BS    BSG   CCH ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���[mty]�dnum�             �dlgh�[ftc]�bs�  �bsg�  cch ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �dnum�             �dlgh�     �bs�  �bsg�      ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���[mty]�dnum�             �dlgh�[ftc]�bs�  �bsg�  cch ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �dnum�             �dlgh�     �bs�  �bsg�      ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���                                                    ��          � 
��� TRIGGERING CRITERIA DATA FOR TCTDP 12              ��          � 
���                                                    ��          � 
��� BS    BSG   CCH                                    ��          � 
����  �  �   �                                         ��          � 
����bs�  �bsg�  cch                                    ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����bs�  �bsg�                                         ��          � 
����  �  �   �                                         ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
����  �  �   �                                         ��          � 
����bs�  �bsg�  cch                                    ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����bs�  �bsg�                                         ��          � 
����  �  �   �                                         ��          � 
���                                                    ��          � 
��                                                      �          � 
�� [NO TRIGGERING CRITERIA DATA]                        �          � 
��                                                      �          � 

    END

If parameter MSISDN is provided, the answer printout is as follows:

HLR CAMEL SUBSCRIPTION DATA

    HLR CAMEL SUBSCRIPTION DATA
�                                                                  � 
�   MSISDN           CSP                                           � 
�   msisdn          [csp]                                          � 
�                                                                  � 
�   TDPTYPE  TDP  SK         GSA              DEH   CCH I  DIALNUM � 
�   tdptype  tdp  sk         gsa             [deh]  cch[i][dialnum]� 
�     .       .    .          .                .     .  .    .     � 
�     .       .    .          .                .     .  .    .     � 
�     .       .    .          .                .     .  .    .     � 
�   tdptype  tdp  sk         gsa             [deh]  cch[i][dialnum]� 
�                                                                  � 
� �                                                      �         � 
� � CAMEL SUBSCRIPTION OPTIONS                           �         � 
� �                                                      �         � 
� ��                                    ��      ��      ��         � 
� ��GCSO  MCSO  SSLO  GC2SO  MC2SO  TIF ��GPRSSO��OSMSSO��         � 
� ��gcso  mcso  sslo  gc2so  mc2so [tif]��gprsso��osmsso��         � 
� ��                                    ��      ��      ��         � 
� ��            ��            �                          �         � 
� ��GC3SO  MC3SO��GC4SO  MC4SO�                          �         � 
� ��gc3so  mc3so��gc4so  mc4so�                          �         � 
� ��            ��            �                          �         � 
� ��    � �      �                                       �         � 
� ��MMSO� �TSMSSO�                                       �         � 
� ��mmso� �tsmsso�                                       �         � 
� ��    � �      �                                       �         � 
� �                                                      �         � 
�  �                            �                                  � 
�  �EXTENDED CAMEL DATA         �                                  � 
�  �                            �                                  � 
�  �EOINCI  EOICK  ETINCI  ETICK�                                  � 
�  �eoinci  eoick  etinci  etick�                                  � 
�  �                            �                                  � 

��                                                      �          � 
��  CAMEL TRIGGERING CRITERIA DATA                      �          � 
���                                                    ��          � 
��� TRIGGERING CRITERIA DATA FOR OCTDP 2               ��          � 
���                                                    ��          � 
��� MTY  DNUM               DLGH  FTC  BS    BSG   CCH ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���[mty]�dnum�             �dlgh�[ftc]�bs�  �bsg�  cch ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �dnum�             �dlgh�     �bs�  �bsg�      ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���[mty]�dnum�             �dlgh�[ftc]�bs�  �bsg�  cch ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �.   �             � .  �     � .�  � . �      ��          � 
���     �dnum�             �dlgh�     �bs�  �bsg�      ��          � 
���     �    �             �    �     �  �  �   �      ��          � 
���                                                    ��          � 
��� TRIGGERING CRITERIA DATA FOR TCTDP 12              ��          � 
���                                                    ��          � 
��� BS    BSG   CCH                                    ��          � 
����  �  �   �                                         ��          � 
����bs�  �bsg�  cch                                    ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����bs�  �bsg�                                         ��          � 
����  �  �   �                                         ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
��� .                                                  ��          � 
����  �  �   �                                         ��          � 
����bs�  �bsg�  cch                                    ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����. �  � . �                                         ��          � 
����bs�  �bsg�                                         ��          � 
����  �  �   �                                         ��          � 
���                                                    ��          � 
��                                                      �          � 
�� [NO TRIGGERING CRITERIA DATA]                        �          � 
��                                                      �          � 

    END

The following table contains information about the parameters in the HGCMP answer printout:

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.3.4.2.3   Result Printout

This command has no result printouts.

5.4   HGCE: CAMEL Extended Information

This section covers the following MML HLR command:

• Home Location Register, Customized Applications for Mobile Networks Enhanced Logic (CAMEL) Extended Information, Change (HGCEC) (Section 5.4.1)

5.4.1   Home Location Register, CAMEL Extended Information, Change (HGCEC)

This command changes the CAMEL subscription options as well as extended CAMEL data for a mobile subscriber or for a CAMEL subscription profile with CAMEL subscription data defined.

Change of CAMEL subscription options is allowed only if the subscriber or the CAMEL subscription profile has any CAMEL subscription data defined.

Change of extended terminating CAMEL data is allowed only if terminating CAMEL subscription data is defined for the mobile subscriber or for the CAMEL subscription profile.

Change of extended originating CAMEL data is allowed only if originating CAMEL subscription data is defined for the mobile subscriber or for the CAMEL subscription profile.

Since parameters ETINCI and ETICK are mutually exclusive, when one of them is changed the other one is set to not assigned.

Since parameters EOINCI and EOICK are mutually exclusive, when one of them is changed the other one is set to not assigned.

Change of parameter TIF is allowed only if the subscriber or the CAMEL subscription profile has any originating CAMEL phase 2 or higher subscription data defined.

5.4.1.1   HGCEC Command Description

                       �
                       �                        �              �
                       �                        � �           ��
                       �                        � �MC4SO=mc4so��
       �             � �                        � �           ��
       �MSISDN=msisdn� �                        � �MC3SO=mc3so��
 HGCEC:+             + +[,SSLO=sslo][,GCSO=gcso]�,+           +�
       �CSP=csp      � �                        � �MC2SO=mc2so��
       �             � �                        � �           ��
                       �                        � �MCSO=mcso  ��
                       �                        � �           ��
                       |                        �              �
                       �

 
       [,GC2SO=gc2so][,GC3SO=gc3so][,GC4SO=gc4so][,TIF=tif][,GPRSSO=gprsso]

       [,OSMSSO=osmsso][,TSMSSO=tsmsso][,MMSO=mmso]
 
 
                                            �
                                            �
       �                � �                ��
       � �             �� � �             ���
       � �ETINCI=etinci�� � �EOINCI=eoinci���
       �,+             +� �,+             +�+;
       � �ETICK=etick  �� � �EOICK=eoick  ���
       � �             �� � �             ���
       �                � �                ��
                                            �
                                            �

Example of an HGCEC Command

HGCEC:CSP=3,MC3SO=0,GC3SO=0,TIF=0;

A check if registration with lower CAMEL phase is performed or register without CAMEL data when CAMEL phase 3 data is not allowed to be sent to the Mobile Switching Center (MSC)/Visitor Location Register (VLR). Call terminating handling with lower CAMEL phase invocation when CAMEL phase 3 is not supported in the interrogating GMSC/gsmSCF, is applied. When the subscriber or the service provider registers a forwarded-to number, number length, format, and conditional barring checks are performed on the forwarded-to number. All these actions are performed for CAMEL subscription profile number 3.

5.4.1.1.1   HGCEC Parameters

The following table contains the parameters for the HGCEC command.

5.4.1.2   HGCEC Printout

This section lists all HGCEC printouts.

5.4.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.4.1.2.2   Answer Printout

This command has no answer printouts.

5.4.1.2.3   Result Printout

This command has no result printouts.

5.5   HGCS: Closed User Group Basic Service Group Options

This section covers the following MML HLR commands:

• Home Location Register, Closed User Group Basic Service Group Options, Change (HGCSC) (Section 5.5.1)
• Home Location Register, Closed User Group Basic Service Group Options, Print (HGCSP) (Section 5.5.2)

5.5.1   Home Location Register, Closed User Group Basic Service Group Options, Change (HGCSC)

This command changes basic service group options of the closed user group for a mobile subscriber member of closed user group(s).

The basic service group options of the closed user group are the inter closed user group accessibility (ACCESS) and preferential closed user group index (PCUG).

If the parameter BSG is not specified, the changes are applied to all basic service groups defined within the closed user group(s) for the mobile subscriber.

5.5.1.1   HGCSC Command Description

                                �                              �
                                �                �            ��
                                �                �      �    ���
                                �                �      �pcug���
HGCSC:MSISDN=msisdn[,BSG=bsg...]+[,ACCESS=access]�,PCUG=+    +�+;
                                �                �      �NONE���
                                �                �      �    ���
                                �                �            ��
                                �                              �

Example of an HGCSC Command

HGCSC:MSISDN=345678901234567,BSG="TS10&TS60",ACCESS="OIA",PCUG=3;

In the example above, the outgoing and incoming access and preferential closed user group index 3 are given to basic service groups Speech Transmission (TS10) and Facsimile (TS60) for the mobile subscriber 345678901234567.

5.5.1.2   HGCSC Parameters

The following table contains the parameters for the HGCSC command.

(1)   For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.5.1.3   HGCSC Printout

This section lists all HGCSC printouts.

5.5.1.3.1   Check Printout

Yes.

5.5.1.3.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.5.1.3.3   Answer Printout

This command has no answer printouts.

5.5.1.3.4   Result Printout

This command has no result printouts.

5.5.2   Home Location Register, Closed User Group Basic Service Group Options, Print (HGCSP)

The command HGCSP initiates the printout of HLR closed user group basic service group options data. This command is used to print the existing basic service group options of closed user group for one or all mobile subscribers that are members of any closed user group.

Deviation:

• This command does not support MSISDN=ALL.

5.5.2.1   HGCSP Command Description

HGCSP:MSISDN=msisdn;

Example of an HGCSP Command

HGCSP:MSISDN=345678901234567;

In the example above, the closed user group basic service group options for the mobile subscriber 345678901234567 are printed.

5.5.2.2   HGCSP Parameters

The following table lists the parameter for the HGCSP command.

5.5.2.3   HGCSP Printout

This section lists all HGCSP printouts.

5.5.2.3.1   Procedure Printout

NOT ACCEPTED
fault type

5.5.2.3.2   Answer Printout

The answer printout of HLR closed user group basic service group options data are shown as follows:

HLR CLOSED USER GROUP BASIC SERVICE GROUP OPTIONS DATA
 
MSISDN            BSG      ACCESS   PCUG
msisdn            bsg      access   pcug
                    .         .       .
                    .         .       .
                    .         .       .
                  bsg      access   pcug

[NONE]
 
END

The following table contains information about the parameters in the HGCSP answer printout.

5.5.2.3.3   Result Printout

This command has no result printouts.

5.6   HGCT: CAMEL Triggering Criteria

This section covers the following MML HLR commands:

• Home Location Register, CAMEL Triggering Criteria, Initiate (HGCTI) (Section 5.6.1)
• Home Location Register, CAMEL Triggering Criteria, End (HGCTE) (Section 5.6.2)

5.6.1   Home Location Register, CAMEL Triggering Criteria, Initiate (HGCTI)

This command initiates CAMEL triggering criteria for a mobile subscriber or for a CAMEL subscription profile with CAMEL subscription data defined in the HLR.

The parameter CCH is used to indicate which CAMEL phase the subscription data is valid for. If the parameter CCH is not present, value 2 is assigned by default.

If the parameter OCTDP2 is used, the CAMEL triggering criteria are defined for originating CAMEL TDP "Collected Info". It is allowed only if originating CAMEL subscription information defined for the subscriber or for the CAMEL subscription profile, includes TDP "Collected Info" for the specified CAMEL phase.

If the parameter TCTDP12 is used, the CAMEL triggering criteria are defined for terminating CAMEL TDP "Terminating Attempt Authorized". It is allowed only if terminating CAMEL subscription information defined for the subscriber or for the CAMEL subscription profile includes TDP "Terminating Attempt Authorized" for the specified CAMEL phase.

The parameters MTY, DNUM, and DLGH are used to define destination number triggering criteria.

Parameter MTY must only be entered when the first destination number triggering criteria is defined. This parameter indicates whether the criterion is inhibiting or enabling the specified destination number or destination number length.

It is possible to define up to 10 destination numbers, 3 destination number lengths, and 5 BS triggering criteria for a subscriber or for a CAMEL subscription profile with TDP "Collected Info".

It is possible to define up to 5 BS triggering criteria for a subscriber or for a CAMEL subscription profile with TDP "Terminating Attempt Authorized".

5.6.1.1   HGCTI Command Description

                       �                                                   �
                       �      �                                            �
                       �      ��                                          ��
                       �      ��          �                              ���
                       �OCTDP2��[,MTY=mty]�[,DNUM=dnum...][,DLGH=dlgh...]���
                       �      ��          �                              ���
                       �      ��                                          ��
       �             � �      �                                            �
       �MSISDN=msisdn� �                                          �        �
 HGCTI:+             + +                                          �        +[,CCH=cch];
       �CSP=csp      � �                                          �        �
       �             � �        [,FTC=ftc][,BS=bs...][,BSG=bsg...]�        �
                       �                                          �        �
                       �                                          �        �
                       �                                          �        �
                       �       �                        �                  �
                       �TCTDP12+[,BS=bs...][,BSG=bsg...]+                  �
                       �       �                        �                  �
                       �                                                   �

Example of an HGCTI Command

HGCTI:CSP=12,CCH=3,OCTDP2,MTY=I,DNUM=0-"*21*678902000#",
      DLGH=3&4&5;

Triggering criteria for CAMEL subscription profile number 12 is initiated for originating CAMEL phase 3 TDP "Collected Info" with match type 'Inhibiting', destination number series *21*678902000# with unknown nature of address, and destination number lengths 3, 4 or 5.

5.6.1.1.1   HGCTI Parameters

The following table contains the parameters for the HGCTI command.

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

(2)  dn is a text string and must use ” delimiter in MML command, for example, 0-“*21*678902000#”.

5.6.1.2   HGCTI Printout

This section lists all HGCTI printouts.

5.6.1.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.6.1.2.2   Answer Printout

This command has no answer printouts.

5.6.1.2.3   Result Printout

This command has no result printouts.

5.6.2   Home Location Register, CAMEL Triggering Criteria, End (HGCTE)

This command ends CAMEL triggering criteria defined for a mobile subscriber or for a CAMEL subscription profile in the HLR.

The parameter CCH is used to indicate which CAMEL phase the subscription data is valid for. If the parameter CCH is not present, value 2 is assigned by default.

If no CAMEL Triggering criteria information is given, all CAMEL triggering criteria for the specified CAMEL phase are deleted for the subscriber or for the CAMEL subscription profile.

When only parameter OCTDP2 is used, all CAMEL triggering criteria of originating CAMEL TDP "Collected Info" defined for the specified CAMEL phase are deleted for the subscriber or for the CAMEL Subscription Profile.

When only parameter TCTDP12 is used, all CAMEL triggering criteria of terminating CAMEL TDP "Terminating Attempt Authorized" defined for the specified CAMEL phase are deleted for the subscriber or for the CAMEL Subscription Profile.

When parameter DNUM is given, the specified destination number is deleted from the destination number triggering criteria.

When parameter DNUM is given, the specified destination number is deleted from the destination number triggering criteria.

When parameter FTC is given, the forwarding triggering criterion is deleted.

When parameter BS is given, the specified BS is deleted from the specified TDP BS triggering criteria.

When parameter BSG is given, the specified BSG is deleted from the specified TDP BS triggering criteria.

5.6.2.1   HGCTE Command Description

      �             �
      �MSISDN=msisdn�
HGCTE:+             +[,CCH=cch]
      �CSP=csp      �
      �             �
�                                                                  �
��                                                                ��
��       �            ��            �      �         ��          ���
��       �      �    ���      �    ��      �    �   ���     �   ����
��       �      �dnum���      �dlgh��      �    �bs ���     �bsg����
��,OCTDP2�,DNUM=�    ���,DLGH=�    ��[,FTC]�,BS=�   ���,BSG=�   ����
��       �      �ALL ���      �ALL ��      �    �ALL���     �ALL����
��       �      �    ���      �    ��      �    �   ���     �   ����
��       �            ��            �      �         ��          ���
��                                                                ��;
��        �         ��          �                                 ��
��        �    �   ���     �   ��                                 ��
��        �    �bs ���     �bsg��                                 ��
��,TCTDP12�,BS=�   ���,BSG=�   ��                                 ��
��        �    �ALL���     �ALL��                                 ��
��        �    �   ���     �   ��                                 ��
��        �         ��          �                                 ��
��                                                                ��
�                                                                  �

Example of an HGCTE Command

HGCTE:CSP=127,CCH=3;

All CAMEL phase 3 triggering criteria are deleted for CAMEL subscription profile number 127.

5.6.2.1.1   HGCTE Parameters

The following table contains the parameters for the HGCTE command.

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

(2)  dn is a text string and must use ” delimiter in MML command, for example, 0-“*21*678902000#”.

5.6.2.2   HGCTE Printout

This section lists all HGCTE printouts.

5.6.2.2.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.6.2.2.2   Answer Printout

This command has no answer printouts.

5.6.2.2.3   Result Printout

This command has no result printouts.

5.7   HGCU: Closed User Group

This section covers the following MML HLR commands:

• Home Location Register, Closed User Group, Initiate (HGCUI) (Section 5.7.1)
• Home Location Register, Closed User Group, Change (HGCUC) (Section 5.7.2)
• Home Location Register, Closed User Group, End (HGCUE) (Section 5.7.3)
• Home Location Register, Closed User Group, Print (HGCUP) (Section 5.7.4)

5.7.1   Home Location Register, Closed User Group, Initiate (HGCUI)

This command initiates a mobile subscriber as a member of a closed user group. Follow the instructions as follows when this command is used:

• The information unit NI is optional. When it is not present in the parameter IC, a default value, set by an application parameter in the function block HLCUGA, are used.
• If the parameter BSG is not specified, the closed user group is applied for all applicable basic service groups in which any basic service is subscribed.
• If the parameter RESTR is not specified, NONE is used as the default value.
• The inter closed user group accessibility and preferential closed user group index are set to NONE by default.
• A mobile subscriber can be a member of up to 10 closed user groups.

5.7.1.1   HGCUI Command Description

HGCUI:MSISDN=msisdn,INDEX=index,IC=ic[,RESTR=restr][,BSG=bsg...];

Example of an HGCUI Command

HGCUI:MSISDN=345678901234567,INDEX=3,IC=5420,BSG="TS10&TS60";

In the example above, the mobile subscriber with MSISDN 345678901234567 is initiated as a member of a closed user group with index 3, default network identity, and cugcode 5420 for the basic service groups Speech transmission (TS10) and Facsimile (TS60).

5.7.1.1.1   HGCUI Parameters

The following table lists the parameters for the HGCUI command.

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.7.1.2   HGCUI Printout

This section lists all HGCUI printouts.

5.7.1.2.1   Check Printout

Yes.

5.7.1.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.7.1.2.3   Answer Printout

This command has no answer printouts.

5.7.1.2.4   Result Printout

This command has no result printouts.

5.7.2   Home Location Register, Close User Group, Change (HGCUC)

The command HGCUC changes closed user group data for a mobile subscriber member of a closed user group. This command adds or removes a basic service group to or from the list of basic service groups, to which closed user group index (INDEX) either applies or changes the intra closed user group restrictions (RESTR), or both.

Follow the instructions as follows when this command is used:

• If an additional and new basic service group for the closed user group mobile subscriber exists, the inter closed user group accessibility and preferential closed user group are set to NONE as default value.
• When the parameter ERASE is present, the specified basic service group is removed according to the specified closed user group index.

5.7.2.1   HGCUC Command Description

                               �                                �
                               �              �                ��
HGCUC:MSISDN=msisdn,INDEX=index+[,RESTR=restr]�,BSG=bsg[,ERASE]�+;
                               �              �                ��
                               �                                �

Example of an HGCUC Command

HGCUC:MSISDN=345678901234567,INDEX=3,BSG="TS60",ERASE;

In the example above, the basic service group Facsimile (TS60) is removed from the closed user group with index 3 for the mobile subscriber with MSISDN 345678901234567.

5.7.2.1.1   HGCUC Parameters

(1)   For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.7.2.2   HGCUC Printout

This section lists all HGCUC printouts.

5.7.2.2.1   Check Printout

Yes.

5.7.2.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.7.2.2.3   Answer Printout

This command has no answer printouts.

5.7.2.2.4   Result Printout

This command has no result printouts.

5.7.3   Home Location Register, Closed User Group, End (HGCUE)

This command ends a mobile subscriber as a member of one or all closed user groups to which it belongs.

5.7.3.1   HGCUE Command Description

                          �     �
                          �index�
HGCUE:MSISDN=msisdn,INDEX=+     +;
                          �ALL  �
                          �     �

Example of an HGCUE Command

HGCUE:MSISDN=345678901234567,INDEX=3;

In the example above, the mobile subscriber with MSISDN 345678901234567 is ended as a member of the closed user group with index 3.

5.7.3.1.1   HGCUE Parameters

The following table lists the parameters for the HGCUE command.

5.7.3.2   HGCUE Printout

This section lists all HGCUE printouts.

5.7.3.2.1   Check Printout

Yes.

5.7.3.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.7.3.2.3   Answer Printout

This command has no answer printouts.

5.7.3.2.4   Result Printout

This command has no result printouts.

5.7.4   Home Location Register, Closed User Group, Print (HGCUP)

This command initiates the printout of HLR closed user group data. Follow the instructions as follows when this command is used:

• The information unit NI is optional. When it is not present in the parameter IC, a default value, set by an application parameter in the function block HCUGA, are used.
• This command is used to print the existing closed user group data for one or all mobile subscribers.

Deviation:

• This MML command does not support MSISDN=ALL.

5.7.4.1   HGCUP Command Description

                   �            �
                   �,INDEX=index�
HGCUP:MSISDN=msisdn�            �;
                   �,IC=ic      �
                   �            �

Example of an HGCUP Command

HGCUP:MSISDN=345678901234567,INDEX=3;

In the example above, the closed user group data for the mobile subscriber 345678901234567, the member of the closed user group with Index 3, are printed.

5.7.4.1.1   HGCUP Parameters

The following table lists the parameters for the HGCUP command.

5.7.4.2   HGCUP Printout

This section lists all HGCUP printouts.

5.7.4.2.1   Procedure Printout

NOT ACCEPTED
fault type

5.7.4.2.2   Answer Printout

The printout of HLR closed user group data is shown as follows:

 HLR CLOSED USER GROUP DATA
 MSISDN            INDEX   IC           RESTR  BSG
 msisdn            index   ic           restr  bsg
                                                .
                                                .
                                                .
                                               bsg
                     .
                     .
                     .
                   index   ic           restr  bsg
                                                .
                                                .
                                                .
                                                bsg

[NONE]
 END

The following table contains information about the parameters in the HGCUP answer printout:

(1)  For more information, see HLR Subscriber Data Type Definitions, Reference [6].

5.7.4.2.3   Result Printout

This command has no result printouts.

5.8   HGIC: IMSI Changeover

This section covers the following MML HLR commands:

• Home Location Register, IMSI Changeover, Initiate (HGICI) (Section 5.8.1)
• Home Location Register, IMSI Changeover, Change (HGICC) (Section 5.8.2)
• Home Location Register, IMSI Changeover, End (HGICE) (Section 5.8.3)
• Home Location Register, IMSI Changeover, Print (HGICP) (Section 5.8.4)

These operations support AUC, HLR, IMS and EPS services.

Note:  

IMS is only supported by immediate IMSI Changeover procedure.

In layered data architecture, IMSI changeover procedure affects all services provisioned for this subscriber. If the subscriber has services other than AUC, HLR or EPS, execute IMSI changeover according to Layered Identity Changeover Provisioning over CAI3G, Reference [9].

5.8.1   Home Location Register, IMSI Changeover, Initiate (HGICI)

This command can initiate an IMSI changeover procedure in the HLR in the following two ways:

• This command can enforce the immediate execution if the parameter DATE is not specified or set to today's date. The subscriber location is set to unknown status.
• If the expiry date, defined in parameter DATE, is specified and is not today's date, the mobile subscriber can use the old Subscriber Identity Module (SIM) / Universal Subscriber Identity Module (USIM) card until the predefined date is reached or the new card is used for first time.

If the subscription is MSISDN-less, it is not allowed to execute IMSI Changeover.

This command is always capable of being executed, even if a previous HGICI has failed.

5.8.1.1   HGICI Command Description

       �             �
       �MSISDN=msisdn�
 HGICI:+             +,NIMSI=nimsi[,DATE=date];
       �IMSI=imsi    �
       �             �

Example of an HGICI Command

HGICI:MSISDN=345678901234567,NIMSI=123456789011111,DATE=111111;

In the example above, the change to the new IMSI 123456789011111 is initiated for the mobile subscriber with MSISDN 345678901234567, the expiry date of which is set as 11 November 2011.

5.8.1.1.1   HGICI Parameters

The following table lists the parameters for the HGICI command.

5.8.1.2   HGICI Printout

This section lists all HGICI printouts.

5.8.1.2.1   Check Printout

Yes.

5.8.1.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.8.1.2.3   Answer Printout

This command has no answer printouts.

5.8.1.2.4   Result Printout

This command has no result printouts.

5.8.2   Home Location Register, IMSI Changeover, Change (HGICC)

This command changes the expiry date of the IMSI changeover either by defining a new date, or enforcing an immediate execution for the new IMSI if the parameter DATE is not specified or set to today. The command is accepted only for a pending changeover.

5.8.2.1   HGICC Command Description

       �             �
       �MSISDN=msisdn�
 HGICC:+             +[,DATE=date];
       �NIMSI=nimsi  �
       �             �

Example of an HGICC Command

HGICC:MSISDN=345678901234567,DATE=111112;

In the example above, the change of the expiry date, 12 November 2011, is entered for the mobile subscriber with MSISDN 345678901234567.

5.8.2.1.1   HGICC Parameters

The following table lists the parameters for the HGICC command.

5.8.2.2   HGICC Printout

This section lists all HGICC printouts.

5.8.2.2.1   Check Printout

Yes.

5.8.2.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.8.2.2.3   Answer Printout

This command has no answer printouts.

5.8.2.2.4   Result Printout

This command has no result printouts.

5.8.3   Home Location Register, IMSI Changeover, End (HGICE)

This operation can be used when a delayed IMSI changeover has been ordered but date has not yet passed (IMSI changeover has not been executed). The result is that the old IMSI is kept for the subscriber. The new IMSI is released to be used again or deleted.

This command is always capable of being executed, even if a previous HGICE has failed.

5.8.3.1   HGICE Command Description

       �             �
       �MSISDN=msisdn�
 HGICE:+             +;
       �NIMSI=nimsi  �
       �             �

Example of an HGICE Command

HGICE:MSISDN=345678901234567;

In the example above, the data related to the new IMSI for the mobile subscriber with MSISDN 345678901234567 is deleted.

5.8.3.1.1   HGICE Parameters

The following table lists the parameters for the HGICE command.

5.8.3.2   HGICE Printout

This section lists all HGICE printouts.

5.8.3.2.1   Check Printout

Yes.

5.8.3.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.8.3.2.3   Answer Printout

This command has no answer printouts.

5.8.3.2.4   Result Printout

This command has no result printouts.

5.8.4   Home Location Register, IMSI Changeover, Print (HGICP)

This command initiates the HLR IMSI changeover data printout. The changeover data of one mobile subscriber with ongoing changeover procedure can be printed.

Deviations:

• The parameters PEND, EXEC, and FORCED are not supported.
• Only the individual version of command is supported. The command containing NIMSI=ALL is not supported.

5.8.4.1   HGICP Command Description

       �             �
       �MSISDN=msisdn�
 HGICP:+             +;
       �NIMSI=nimsi  �
       �             �

Example of an HGICP Command

HGICP:MSISDN=345678901234567;

In the example above, the changeover data for the mobile subscriber with MSISDN 345678901234567 are printed.

5.8.4.1.1   HGICP Parameters

The following table lists the parameters for the HGICP command.

5.8.4.2   HGICP Printout

This section lists all HGICP printouts.

5.8.4.2.1   Procedure Printout

NOT ACCEPTED
fault type

5.8.4.2.2   Answer Printout

 HLR IMSI CHANGEOVER DATA
                                           �     �
 MSISDN    IMSI    NIMSI    STATE  DATE    �AUTHD�
                                           �     �
 msisdn    imsi    nimsi    state  date    �authd�
                                           �     �
[NONE]
 
 END

The following table lists information about the parameters in the HGICP answer printout.

(1)  For information about the different states possible to receive, see Function Specification Identity Changeover for Layered Applications, Reference [8]

5.8.4.2.3   Result Printout

This command has no result printouts.

5.9   HGIR: IMSI Changeover Removal

This section covers the following MML HLR command:

• Home Location Register, IMSI Changeover Removal, Initiate (HGIRI) (Section 5.9.1)

In layered data architecture, IMSI changeover procedure affects all services provisioned for this subscriber. If the subscriber has services other than AUC, HLR or EPS, execute IMSI changeover according to Layered Identity Changeover Provisioning over CAI3G, Reference [9].

5.9.1   Home Location Register, IMSI Changeover Removal, Initiate (HGIRI)

This command initiates the removal of all references to the old IMSI, if the new IMSI has been taken into operation for all services.

This command is always capable of being executed, even if a previous HGIRI has failed.

5.9.1.1   HGIRI Command Description

       �             �
       �MSISDN=msisdn�
 HGIRI:+             +;
       �IMSI=imsi    �
       �             �

Example of an HGIRI Command

HGIRI:MSISDN=45678901234567;

In the example above, all references to the old IMSI for the mobile subscriber with MSISDN 345678901234567 are deleted.

5.9.1.1.1   HGIRI Parameters

The following table lists the parameters for the HGIRI command.

5.9.1.2   HGIRI Printout

This section lists all HGIRI printouts.

5.9.1.2.1   Check Printout

Yes.

5.9.1.2.2   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.9.1.2.3   Answer Printout

This command has no answer printouts.

5.9.1.2.4   Result Printout

This command has no result printouts.

5.10   HGLD: HLR Subscriber Location Services Data

This section covers the following MML HLR commands:

• Home Location Register, Subscriber Location Services Data, Initiate (HGLDI) (Section 5.10.1)
• Home Location Register, Subscriber Location Services Data, Change (HGLDC) (Section 5.10.2)
• Home Location Register, Subscriber Location Services Data, End (HGLDE) (Section 5.10.3)
• Home Location Register, Subscriber Location Services Data, Print (HGLDP) (Section 5.10.4)

5.10.1   Home Location Register, Subscriber Location Services Data, Initiate (HGLDI)

This command initiates the following services: Location Services (LCS) classes or service types for a mobile subscriber in the HLR. It also initiates external addresses for already initiated call or session unrelated privacy class, or call or session-related privacy class.

• Location Services (LCS) classes or service types for a mobile subscriber in the HLR
• External addresses for the already initiated call or session-related privacy class
• External addresses for the already initiated call or session unrelated privacy class

Follow the instructions as follows when this command is used:

• If the parameter EADD is entered, one external address is added either for call or session unrelated LCS privacy class (CUNRL), or call or session-related LCS privacy class (CREL).
• If the parameter EADD is entered and both optional parameters CREL and CUNRL are omitted, then the external address is added to call or session unrelated LCS privacy class.
• Up to 40 external addresses can be defined for call or session unrelated LCS privacy class.
• Up to 40 external addresses can be defined for call or session-related LCS privacy class.
• Up to 32 service types can be defined for a mobile subscriber.
• If the parameter NOTF is not entered, the default value is assigned.
• If the parameter INTID is entered, the internal identities entered are added for PLMN operators LCS privacy class.
• If the parameter GRES is not entered, no restriction on the Gateway Mobile Location Center (GMLC) is assigned.

5.10.1.1   HGLDI Command Description

                    �                                            �
                    �UNIV                                        �
                    �                                            �
                    �CREL[,NOTF=notf]                            �
                    �                                            �
                    �CUNRL[,NOTF=notf]                           �
                    �                                            �
                    �PLMNO[,INTID=intid...]                      �
                    �                                            �
HGLDI:MSISDN=msisdn,+MOCL=mocl...                                +;
                    �                                            �
                    �SERVT=servt...[,GRES=gres][,NOTF=notf]      �
                    �                                            �
                    �                                 � �      ���
                    �                                 � �CREL  ���
                    �EADD=eadd[,GRES=gres][,NOTF=notf]�,+      +��
                    �                                 � �CUNRL ���
                    �                                 � �      ���
                    �                                            �

Example of an HGLDI Command

HGLDI:MSISDN=345678901234567,EADD=666999,GRES=0,NOTF=1,CREL;

In the example above, the external address 666999 with location request allowed from identified GMLCs and notification for the mobile subscriber with MSISDN 345678901234567 is initiated for call or session-related LCS privacy class.

5.10.1.2   HGLDI Parameters

The following table lists the parameters for the HGLDI command.

5.10.1.3   HGLDI Printout

This section lists all HGLDI printouts.

5.10.1.3.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.10.1.3.2   Answer Printout

This command has no answer printouts.

5.10.1.3.3   Result Printout

This command has no result printouts.

5.10.2   Home Location Register, Subscriber Location Services Data, Change (HGLDC)

This command changes the LCS privacy class data or service type data for a mobile subscriber in the HLR. It also changes data related to an external address, the optional parameter CREL, or CUNRL of which can be used to specify the LCS privacy class (call or session related, or call or session unrelated) for which the change is applicable. If neither of these parameters are given, the specified external address is changed for call or session unrelated LCS privacy class.

5.10.2.1   HGLDC Command Description

                    �                               �
                    �CREL,NOTF=notf                 �
                    �                               �
                    �CUNRL,NOTF=notf                �
                    �          �         �� �     ���
                    �          �GRES=gres�� �CREL ���
                    �EADD=eadd,+         +�,+     +��
HGLDC:MSISDN=msisdn,+          �NOTF=notf�� �CUNRL��+;
                    �          �         �� �     ���
                    �            �         �        �
                    �            �GRES=gres�        �
                    �SERVT=servt,+         +        �
                    �            �NOTF=notf�        �
                    �            �         �        �
                    �                               �

Example of an HGLDC Command

HGLDC:MSISDN=345678901234567,EADD=9988776655,NOTF=2,CREL;

In the example above, the location request restriction for the call or session-related external address 9988776655 for the subscriber with MSISDN 345678901234567 is changed to location request with notification and privacy verification allowed in case of no response.

5.10.2.2   HGLDC Parameters

The following table lists the parameters for the HGLDC command.

5.10.2.3   HGLDC Printout

This section lists all HGLDC printouts.

5.10.2.3.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.10.2.3.2   Answer Printout

This command has no answer printouts.

5.10.2.3.3   Result Printout

This command has no result printouts.

5.10.3   Home Location Register, Subscriber Location Services Data, End (HGLDE)

This command ends the LCS classes or service types for a subscriber in the HLR. It also ends LCS class data corresponding to an LCS class already defined or service type data corresponding to a service type already defined. If all optional parameters are not entered, all LCS data for a mobile subscriber are ended.

5.10.3.1   HGLDE Command Description

                   �                           �
                   � �                        ��
                   � �UNIV                    ��
                   � �    �                 � ��
                   � �CREL�,EADD=eadd[,GRES]� ��
                   � �    �                 � ��
                   � �     �                 ���
                   � �CUNRL�,EADD=eadd[,GRES]���
                   � �     �                 ���
                   � �                        ��
HGLDE:MSISDN=msisdn�,+PLMNO[,INTID=intid...]  +�;
                   � �                        ��
                   � �ALLPCL                  ��
                   � �                        ��
                   � �MOCL= mocl...           ��
                   � �      �            �    ��
                   � �      �servt[,GRES]�    ��
                   � �SERVT=+            +    ��
                   � �      �ALL         �    ��
                   � �      �            �    ��
                   � �                        ��
                   �                           �

Example of an HGLDE Command

HGLDE:MSISDN=345678901234567,CREL,EADD=32453435,GRES;

In the example above, the GMLC restriction of the external address 32453435 for the call or session-related LCS privacy class for the mobile subscriber with MSISDN 345678901234567 is ended.

5.10.3.2   HGLDE Parameters

The following table lists the parameters for the HGLDE command.

5.10.3.3   HGLDE Printout

This section lists all HGLDE printouts.

5.10.3.3.1   Procedure Printout

EXECUTED

NOT ACCEPTED
fault type

5.10.3.3.2   Answer Printout

This command has no answer printouts.

5.10.3.3.3   Result Printout

This command has no result printouts.

5.10.4   Home Location Register, Subscriber Location Services Data, Print (HGLDP)

This command prints the LCS data for mobile subscribers in the HLR.

The printout of result for HLR subscriber location services data is received.

Deviations

• MSISDN can only accept individual value, not multiple ones.

5.10.4.1   HGLDP Command Description

HGLDP:MSISDNS=msisdns;

Example of an HGLDP Command

HGLDP:MSISDNS=345678901234567;

In the example above, the LCS data for the mobile subscriber with MSISDN 345678901234567 are printed.

5.10.4.2   HGLDP Parameters

The following table lists the parameter for the HGLDP command.