apkt_hmr knowledge transfer 20100519[1].pdf

8/10/2019 APKT_HMR Knowledge Transfer 20100519[1].pdf

1/387

Nortel HLR

Configuration - MobileSubscriber ProvisioningRelease: NSS19Document Revision: 01.02

www.nortel.com

NN10300-446.


2/387

Nortel HLR

Release: NSS19

Publication: NN10300-446

Document status: Standard

Document release date: 12 September 2007

Copyright 2007 Nortel Networks

All Rights Reserved.

Sourced in the United States of America

This document is protected by copyright laws and international treaties. All information, copyrights and any otherintellectual property rights contained in this document are the property of Nortel Networks. Except as expressly

authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and

this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed,

displayed or transmitted, in whole or part, in any form or media.

Information is subject to change without notice. Nortel reserves the right to make changes in design or components

as progress in engineering and manufacturing may warrant.

Nortel, the Nortel logo, the Globemark, and DMS are trademarks of Nortel. GSM is a trademark of GSM MOU

Association.

All other trademarks are the property of their owners.

.


3/387

3.

New in this release

The following sections detail whats new in Nortel HLR Configuration -Mobile Subscriber Provisioning for HLR19:

Features (page 3)

Other changes (page 3)

FeaturesThis document contains no feature updates in HLR19.

Other changesThis document is based on the MSP v15. See the following sections forinformation about changes that are not feature-related:

Mobile Subscriber Provisioning changes from MSP v14 ProvisioningLayer (page 3)

Restructured information (page 4)

Mobile Subscriber Provisioning changes from MSP v14 ProvisioningLayer

The following new MSP command is supported for MDSN and DPSN:

Customized Ring Back Tone (CRBT)

The subscriber data validation algorithm is changed to support theUMTS Authentication Provisioning Optimization feature (UMTS APO).

New error codes introduced:

91 MRF reached the maximum subscriber capacity

93 MRF is out of memory

B7 Insufficient HLR memory

B8 FOLLOW IMSI is not defined

B9 Relocation in progress

Nortel HLRConfiguration - Mobile Subscriber Provisioning

NN10300-446 01.02 Standard

12 September 2007Copyright 2007 Nortel Networks

.


4/387

4 New in this release

BA Subscriber creation is not allowed

CC MRF maintenance in progress

DFSB syntax is updated with the FOLLOW provisioning identifier. Thisprovides an ability to provision a subscriber on the same HLR as a

particular already provisioned subscriber.

DESB syntax is updated to allow provisioning of the HLRONLYparameter.

Data LInk LayerIt is no longer possible to log on to the HLR-PM with MSP v11.

Bulk File FormatBulk File provisioning can no longer use MSP v11.

Restructured informationDocuments were restructured, renamed, and renumbered for this release.The content contained in this document came from the retired GSM /UMTS HLR Mobile Subscriber Provisioning Guide NTP 411-2831-331available in previous releases.


NN10300-446 01.02 Standard


.


5/387

5.

Introduction

This document describes the interface between the Mobile SubscriptionAdministration Centre (AdC) for subscription administration towards anHLR via an HLR Provisioning Manager (HLR-PM) on a Database server.

The Operation and Support System (OSS) interface for subscription

administration is specified herein, namely the Mobile SubscriberProvisioning (MSP) protocol. This document is intended for either thecustomer or the end user of the system, whichever may be applicable.

Prerequistites

A general knowledge of the GSM standard.

Knowledge of the the following HLR data schema:

GHLRAUTH (AUC entries)

GHLRDATA (General subscriber data)

GHLRBSVC (Basic services) GHLRSSOP (Supplementary services)

GHLRCUG (CUG data)

GHLREA (Equal access)

GHLRSIMR (SIM replacement)

GHLRCAML (CAMEL)

GHLRGPRS (GPRS PDP contexts)

GHLRVGS (VBS and VGCS group provisioning for GSM Railways)

GHLRUCSI (USSD CSI) GHLRSCSI (Supplementary Service CSI)

GHLROTDP (Camel Originating TDP criteria)

GHLRTTDP (Camel Terminating TDP criteria)

GHLRGCSI (GPRS CSI)

GHSMSCSI (SMS CSI)


NN10300-446 01.02 Standard


.


6/387

6 Introduction

GHLRLCS (Location Services)

GHLRCLIN (CLI MSISDN)

GHLRDCSI (Dialled CSI)

GHLRMCSI (Mobility Management CSI)

GHLCSECL (Location Services External Client List)

Section introductory text

Navigation

MSP fundamentals (page 7)

Syntax convention (page 9)

MSP request and response formats (page 11)

Provisioning commands (page 19)

Provisioning subscriber data (page 47)

MSP data link protocol (page 293)

MSP bulk file format (page 341)

MSP audit file format (page 351)

MSP guide for developers (page 355)

Message response codes (page 367)


NN10300-446 01.02 Standard


.


7/387

7.

MSP fundamentals

The Mobile Subscriber Provisioning (MSP) protocol provides the ability tomanipulate (i.e. add, change, delete and display) subscriber data on theHLR.

The HLR Provisioning Manager (HLR-PM) enables a subscribers profile to

be modified in one MSP message, containing data which can affect manytuples in the HLR subscriber data tables. The subscription argumentsprovided in each message request have no distinct ordering. The HLR-PMorders the tuple operation to maximize the chance of the whole transactioncompleting successfully. If an error occurs during a transaction, thecompleted operations are rolled-back, and the subscriber is restored to theoriginal state before any of the tuple operations were attempted.

MSP defines a syntax for subscription administration. This information canbe transmitted in two ways (over data link and as part of an BSP file).

MSP Data Link

The MSP data link protocol is used when an AdC passes provisioninginformation (on a transaction basis) to an HLR-PM. In thisconfiguration, the AdC and HLR-PM are connected by a physicallink.To ensure requests and responses are passed accurately, theMSP data link protocol is used. For further information refer toMSPdata link protocol (page 293).The MSP protocol is transmitted to the HLR-PM via Ethernet, usingraw sockets over TCP/IP.MSP is half-duplex, only after a response is received from the HLR-PMshould the next message (with the exception of the Cancel message)be sent by the AdC. All communication is initiated by the AdC.MSP has logon and logoff messages to start and end a session, ifthere is no activity on a link for greater than a configurable number ofseconds, the HLR-PM logs the user off. To prevent this happeningduring a lengthy provisioning sequence an AdC can send NULLmessages. The HLR-PM resets the logoff timer when it receives aNULL message.

BSPBSP allows the AdC to provision information for multiple subscriberswithin a single BSP file. These files can be prepared during peak hours


NN10300-446 01.02 Standard


.


8/387

8 MSP fundamentals

and processed during off-peak hours. Files are transferred using themechanisms described in Nortel HLR Fundamentals (NN10300-411).The MSP encoding scheme is used within the BSP files to specifyprovisioning information. This provides consistency for both the AdCMSP encoding engine and HLR-PM MSP decoding engine. BSP

inherits the enhancements to MSP capabilities each release.The bulk file format supports all of the provisioning commands anddata provided by MSP. For further information refer toMSP bulk fileformat (page 341)

The MSP audit file is used to record MSP provisioning layer requests andresponses. MSP Audit file records MSP provisioning layer requests andresponses together with other information which describe how and wherethe transaction is processed. For further information refer toMSP auditfile format (page 351).

A third party AdC development agency must be supplied with the correct

specification and version and the method of connection must be agreed.

It is strongly recommended that new third party AdC developmentagencies perform integration testing with the HLR-PM before deployment.

The following sections describe the provisioning layer commands togetherwith the provisioning layer encoding scheme.


NN10300-446 01.02 Standard


.


9/387

9.

Syntax convention

In order to be able to describe messages in a generic way, the followingsyntax convention is used within this section:

expr An expression, which is any sequence of literal

characters or expressions.

Symbol_name:= expr Symbolic name is defined by expression

Symbolic name must be replaced with the value

for which it stands.

[expr] Expression optional, or applicable in certain

cases.

[expr] * Expression optional, or applicable in certain

cases.

[expr] + Repetition of expression, 1 or more instances.

expr1 expr2 Expression 1 is followed by expression 2.

expr1 | expr2 Expression 1 or expression 2 is applicable.

| The | symbol is used to separate values

accepted by a particular parameter and takes

precedence over all other notation (except :=).

For example:

example:= A B | C D

Here, "example" is either:

A followed by B or,

C followed by D.

{comment} Textual description

Messages will be shown in the following font:

message:= {an example message, shown with a different font}


NN10300-446 01.02 Standard


.


10/387

10 Syntax convention

Any spaces shown in grammar or examples are not required and areincluded for legibility only. For example, the spaces around the | areshown for clarity only.


NN10300-446 01.02 Standard


.


11/387

11.

MSP request and response formats

The MSP provisioning commands are split into four groups:

Subscriber definition commands (SB)

Subscription definition commands (SN)

SIM replacement definition commands (SR)

Translation command (TRAN)

Subscriber definition (SB) commands allow a subscriber to be added orremoved from the HLR. Conceptually, these commands access the AUCdatabase.

Subscription definition (SN) commands allow a subscription to be modifiedon the HLR. Conceptually, these commands access the HLR database.

SIM replacement (SR) commands allow the provisioning of SIMreplacement functionality on the HLR.

The translate (TRAN) command allows an MSISDN to be translated intoan IMSI.

The subscriber, subscription and SIMR command groups have a numberof operations types. These are:

Define (DF)

Modify (MD)

Display (DP)

Delete (DE)

The command name is derived from the operation and the commandgroup. For instance, the command to define a subscriber is called DFSB.

Note that the define command is only valid for the subscriber definitioncommand group. Therefore, DFSB is valid, but DFSN and DFSR is notvalid.


NN10300-446 01.02 Standard


.


12/387

12 MSP request and response formats

Request formats

Provisioning requests always contain a request type which is the commandto be executed. Dependent on the request type a number of arguments

can be provided.

:= | | | | | | | | | |

For information on each provisioning_request refer toProvisioning commands (page 19)

request_type := DFSB | MDSB | DPSB | DESB | MDSN | DPSN |DESN | MDSR | DPSR | DESR | TRAN

A provisioning command request:DFSB = Define a subscriberMDSB = Modify subscriber dataDPSB = Display subscriber dataDESB = Delete subscriberMDSN = Modify/add subscription dataDPSN = Display a subscription

DESN = Delete a subscriptionMDSR = Modify SIMR informationDPSR = Display SIMR informationDESR = Delete SIMR informationTRAN = Translate

For information on each refer toProvisioning commands (page 19).


NN10300-446 01.02 Standard


.


13/387

Prerequistites 13

Response formats

Provisioning responses contain a message response code whichis a two digit code. A response can contain, dependent on the

defined above, a number of arguments.

:= | | | | || | | | |


14/387


Common definitions

This section define parameters that are common to multiple commands.

The ASCII character 09 hex or the horizontalTAB character.

The provisioning identifier. The subscribers

IMSI or the MSISDN. For further information

refer toProvisioning identifier (page 14)

The term used to represent a service used

by the HLR as defined inSubscription Data

Syntax (page 54)

The term used to designate information

associated with a subscriber stored in the HLR

as defined inSubscription Data Syntax (page

54)

A two digit response code which is described

in section. For more information seeMessage

response codes (page 367)

Provisioning identifierThe provisioning identifier, or , corresponds to theInternational Mobile Subscriber Identity (IMSI) or the Mobile SubscriberISDN (MSISDN) of the subscriber.

The HLR uses the IMSI to uniquely identify a subscriber in the HLR. Whena Basic Service is provisioned, an MSISDN is provided. The MSISDN alsouniquely identifies the subscriber.

MSP allows both the IMSI and MSISDN to be used as a argument forsubscriber provisioning message types supported, with the followingexception:

For some MSP message types, using the MSISDN as the provisioningidentifier is not appropriate. For example, define subscriber (DFSB)


NN10300-446 01.02 Standard


.


15/387

Provisioning identifier 15

creates a new subscriber with no Basic Services and hence noMSISDN. In these cases, a inappropriate identifier error is produced.

Database server provisioning identifier format

The Database Server provides two methods of allocating subscribers toHLRs:

Pattern matching - matches IMSI patterns to HLRs

Manual allocation - MSP message specifies the HLR where thesubscriber should be created.

The manual allocation requires additional syntax in the provisioningidentifier of a DFSB message to specify the HLR. This syntax is used bythe Provisioning Manager (HLR-PM) on a Database Server to route theMSP message.

Once a subscriber has been created subsequent MSP messages will berouted to the correct HLR automatically without the need to specify theHLR

The following MSP commands also allow the specification of an HLR in theprovisioning identifier. The HLR specification functionality is only allowedwhen an IMSI is used as the message identifier.

DPSB

DPSN

DPSR DESB

Specifying the HLR for these commands is required for the internal auditfunctionality of the Database Server and is not intended for use by externalMSP users. HLR Group name is not recognized as a valid HLR namewhen specified for these commands.

For more details on specifying the HLR identifier, refer to Nortel HLRFundamentals (NN10300-411).

The following MSP command allows the specification of an IMSI to followin the provisioning identifier. IMSI to follow must be an already provisionedIMSI.

DFSB

This functionality allows a subscriber to be created on the same HLR asan existing subscriber.


NN10300-446 01.02 Standard


.


16/387


The following MSP commands also allow the specification of theHLRONLY flag in the provisioning identifier. The HLRONLY flagspecification functionality is allowed when the arg type is an IMSI with thefollowing commands:

DPSB DPSN

DPSR

DESB

If the HLRONLY flag is not set, display messages only query the OracleDatabase. If the HLRONLY flag is set, display messages only query theHLR.

If the HLRONLY flag is not set, the DESB messages deletes a subscriber

from the Oracle Database and the HLR. If the HLRONLY flag is set, theDESB messages deletes a subscriber only from the HLR. This is used tocleanup a subscriber from the source HLR blade in the extremely rarecase when the automatic deletion during the subscriber migration fails dueto a disaster. This functionality should never be used for another purpose.For the details on the subscriber migration within an ATCA HLR pleaserefer to Nortel HLR Fundamentals (NN10300-411).

The HLRONLY flag specification functionality is allowed when the arg typeis an MSISDN with the following command:

TRAN

SIMR provisioningThe syntax corresponds to the SIM Replacement (SIMR)information provisioned.

The HLR supports a system which allows for SIM replacement (SIMR).This operation involves transferring services associated with an IMSI to anew IMSI when a certain event occurs. The event can be one of two types:

At a fixed time (scheduled swapover)

When the new IMSI is used for the first time (user triggered swapover)

Before any swapover takes place, a new subscriber must be added to theHLR database.

The SR commands (defined inMSP request and response formats(page 11)) allow the provisioning of SIMR information in the HLRdatabase.


NN10300-446 01.02 Standard


.


17/387

Provisioning identifier 17

DES encryption of KiThe Ki may be encrypted in a DFSB or MDSB message, to providesecurity for this sensitive data. The only encryption algorithm supported bythe HLR-PM is Data Encryption Standard (DES)

Decryption Key. The secret key is specified in the configuration of theHLR-PM as 16 hexadecimal digits. The key is associated with an index,and this index is used in the DFSB message to refer to the key that wasused to encrypt the Ki in that record. Up to 255 keys are stored on theHLR-PM.

The HLR-PM supports Electronic Code Book mode DES decryption.illustrates the DES encryption of Ki by the MSP. See Figure 1 "Encryptionof Ki using Electronic Code Book mode DES" (page 17)

The HLR-PM applies DES decryption on the encrypted Ki within the MSP

provisioning request, by splitting the 16 byte Ki. The 8 most significantbytes of the Ki, encrypted, become the 8 most significant bytes of theresult Ki, decrypted. The least 8 significant bytes of the Ki, encrypted,become the 8 least significant bytes of the result Ki, decrypted.

Figure 1Encryption of Ki using Electronic Code Book mode DES


NN10300-446 01.02 Standard


.


18/387



NN10300-446 01.02 Standard


.


19/387

19.

Provisioning commands

This section defines the following provisioning commands:

Define a subscriber (DFSB) (page 20)

Modify Subscriber Data (MDSB) (page 22)

Display a Subscription (DPSN) (page 35)

Delete Subscriber (DESB) (page 27)

Modify or Add Subscription Data (MDSN) (page 30)

Delete a Subscription (DESN) (page 34)

Display a Subscription (DPSN) (page 35)

Modify SIMR Information (MDSR) (page 39)

Display SIMR Information (DPSR) (page 41)

Delete SIMR Information (DESR) (page 44)

Translate (TRAN) (page 45)


NN10300-446 01.02 Standard


.


20/387


21/387

Examples 21

Response syntax

:=

Refer to TableTable 13 "Message Responses- Meaning and Occurrence" (page 367) for

response codes.

ExamplesExample request to add a subscriber with IMSI 2400119120000:

DFSBIMSI,2400119120000ENC,25KI,C74D930B45F66867AFF2A0F4610A408F ALGPARM,NILALGSEL,1

Example request to add a subscriber with IMSI 2400119120001 with noencryption on the Ki:

DFSBIMSI,2400119120001ENC,NONEKI,07F420070A510C320BC411B5FC393FE 3ALGPARM,07F420070A510C320BC411B5FC393FE3ALGSEL,101

Example request to add a subscriber with IMSI 2400119120001 with anALGPARM of NIL:

DFSBIMSI,2400119120001ENC,25KI,07F420070A510C320BC411B5FC393FE 3ALGPARM,NILALGSEL,3

Example request to add a subscriber with IMSI 2400119120001 on theHLR having HLRID of AA30:

DFSBIMSI,2400119120001,HLRID,AA30ENC,25KI,07F420070A510C320BC411 B5FC393FE 3ALGPARM,NILALGSEL,3

Example of an error response where HLR dump is in progress:

EE


NN10300-446 01.02 Standard


.


22/387

22 Provisioning commands

Modify Subscriber Data (MDSB)

The MDSB command modifies information added as part of the DFSBmessage.

Request syntax

:= MDSB[ENC,KI,][ALGPARM,][ALGSEL,]

At least one of the optional fields (ENC/KI, ALGPARM or ALGSEL) mustbe included in the message.

IMSI, | MSISDN,

International Mobile Subscriber Identity (IMSI) ininternational E.212 format. 6-15 digits, including

the MCC, MNC and MSIN.

Mobile Subscriber ISDN Number (MSISDN) in

international E.164 format. 3-15 digits, including

the CC, NDC and SN. For further information

seeProvisioning identifier (page 14).

NONE |

NONE = No encryption.

1-3 numeric characters to indicate the DES

encryption index used to encode the Ki.Numeric values of 1 to 255 are valid. For

further information refer toDES encryption of

Ki (page 17)

32 hexadecimal characters that represent the

Ki value to be added to the subscriber, most

significant byte first. Encrypted as defined by

NIL |

NIL = no algorithm parameter.


algorithm parameter value.

1-3 numeric characters indicating the A3/A8

algorithm selector to be set for the subscriber.

Numeric values of 0 to 255 are valid.


NN10300-446 01.02 Standard


.


23/387

Examples 23

At least one of the optional fields (ENC/KI, ALGPARM or ALGSEL) mustbe included in the message

Response Syntax

:=

Refer toTable 13 "Message Responses -

Meaning and Occurrence" (page 367).

ExamplesExample message which changes the ALGSEL value:

MDSBIMSI,2400119120001ALGSEL,1

Example message which changes the Ki (unencrypted):

MDSBIMSI,2400119120001ENC,NONEKI,07F420070A510C320BC411B5FC393FE 3

Example message which changes the Ki and the algorithm selector:

MDSBIMSI,2400119120001ENC,12KI,07F420070A510C320BC411B5FC393FE3 ALGSEL,2

Example message which changes the OPC value:

MDSBIMSI,2400119120001ALGPARM,07F420070A510C320BC411B5FC393FE3

Example message which changes the ALGPARM field to NIL:

MDSBIMSI,2400119120001ALGPARM,NIL

Example of a successful response:

00

Example of an error response where an MK change is in progress:

E4


NN10300-446 01.02 Standard


.


24/387


Display Subscriber Data (DPSB)

The DPSB command displays information added as part of the DFSBmessage.

For security reasons, it is not possible to display the Ki.

Request syntax

:= DPSB[] *

IMSI,[,] [,] | MSISDN,

International Mobile Subscriber Identity (IMSI) in





the CC, NDC and SN. For further information

refer toProvisioning identifier (page 14).

HLRID, | HLRNAME,

3-10 hexadecimal characters.

HLR name, symbolic string of 1-32

alphanumeric, - and _ characters (first

character must be a letter).

HLRONLY

Display the subscriber requesting the HLR and

not the Oracle Database.

ALGPARM | ALGSEL | HLR

Response syntax

:= [HLR,][][ALGSEL, ]


NN10300-446 01.02 Standard


.


25/387

Examples 25

Refer to TableTable 13 "Message Responses

- Meaning and Occurrence" (page 367) for

response codes.

The HLR name, taken from the user

configration, if the HLR where the subscriberwas originally created.

NIL |

NIL = no algorithm parameter.


algorithm parameter value.

1-3 numeric characters indicating the A3/A8

algorithm selector to be added to the subscriber.

Numeric values of 1 to 255 are valid.

In normal operation the HLR name returned will be the HLR name storedin the Data Server as the location of that subscriber. In the case of matedpair HLRs there are scenarios where the HLR name returned will be themate HLR of the HLR where the subscriber is located.

ExamplesExample message which displays the ALGSEL value:

DPSBIMSI,2400119120001ALGSEL

Example response to this message:

00ALGSEL,3

Example of message which displays a name of HLR, where subscriber isprovisioned:

DPSBIMSI,2400119120001HLR


00HLR,London

Example message which displays the ALGPARM value:

DPSBIMSI,2400119120001ALGPARM


00ALGPARM,07F420070A510C320BC411B5FC393FE3

Example message which displays the ALGPARM and ALGSEL values:


NN10300-446 01.02 Standard


.


26/387


DPSBIMSI,2400119120001


00HLR,LondonALGPARM,NILALGSEL,3

Example message which displays the ALGPARM and ALGSEL values fora subscriber provisioned on HLR having HLRID AA30:

DPSBIMSI,2400119120005,HLRID,AA30


00HLR,LondonALGPARM,NILALGSEL,3

Example of an error response where the subscriber not defined:

9D


NN10300-446 01.02 Standard


.


27/387

Request syntax 27

Delete Subscriber (DESB)

The DESB command deletes a specified subscriber from the HLR. It canalso be used to remove the subscription before removing the subscriber.

A subscriber cannot be removed if they have:

Subscription services (unless the ALL option is specified).

SIM replacement information provisioned.

SIM replacement information can be removed by using the DESRcommand.

Request syntax

:= DESB




the MCC, MNC and MSIN

.

> Mobile Subscriber ISDN Number (MSISDN)

in international E.164 format. 3-15 digits,

including the CC, NDC and SN. To use an

MSISDN as the provisioning identifier requiresthe subscriber to have a Basic Services

provisioned. For further information refer to

Provisioning identifier (page 14).

HLRID, | HLRNAME,






NN10300-446 01.02 Standard


.


28/387


HLRONLY

Delete the subscriber from the HLR and not the

Oracle Database.

DEL,ALL | DEL,AUC

Indicates which type or group of data is to be

deleted.

ALL = Remove subscription and subscriber

data.

AUC = Remove subscriber data only.

HLRONLY flag is used to delete a subscriber from the HLR bypassing theOracle Database. This is used to cleanup a subscriber from the sourceHLR blade in the extremely rare case when the automatic deletion duringthe subscriber migration fails due to a disaster. This functionality shouldnever be used for another purpose. For the details on the subscribermigration within an ATCA HLR please refer to Nortel HLR Fundamentals(NN10300-411).

Response Syntax

:=

Refer to TableTable 13 "Message Responses - Meaning andOccurrence" (page 367)for response codes.

ExamplesExample of a request to delete a subscriber with no subscription servicesand IMSI 2400119120001:

DESBMSISDN,5233100001DEL,ALL

Example of a request to delete a subscriber with IMSI 2400119120005 andprovisioned on HLR having HLRNAME LONDON:

DESBIMSI,2400119120005,HLRNAME,LONDONDEL,ALL


00

Example of an error response where an IMSI range violation takes place:


NN10300-446 01.02 Standard


.


29/387

Examples 29

51


NN10300-446 01.02 Standard


.


30/387


Modify or Add Subscription Data (MDSN)

The MDSN command allows the subscribers basic and supplementaryservices to be added, deleted or modified. Many services can be modified

within the same MDSN request.

If the MDSN message is used for the modification of an already existingservice, only the parameters explicitly stated in the message protocol willbe modified in the HLR database. Existing data shall remain until explicitlymodified.

Request Syntax

:= MDSN[]+

The order in which these elements are presented is not significant.

IMSI, | MSISDN,






the CC, NDC and SN For further information to


Where corresponds todesignated information associated with a

subscriber stored in the HLR as defined in refer

toSubscription Data Syntax (page 54).

Response SyntaxResponses contain a message response code which is a two digit code. Aresponse will contain a response code and may have [0..n] arguments.

:= [ ]*


NN10300-446 01.02 Standard


.


31/387

Examples 31

Refer to TableTable 13 "Message Responses- Meaning and Occurrence" (page 367) forresponse codes.

On some error messages, the particular dataid

in error is indicated by . For example,

sending an MDSN message with a CFU

subscriber data that had a bad call forwarding

number would result in the following response:

provisioning_response:= 7C CFU

ExamplesExample message request to modify the following parameters of thesubscription with the IMSI 2400119120000:

CFU Deactivate for Telephony

CFNRY Activate for all Basic Services, Forwarded-tonumber 6102419300203, Nature-of-addressinternational number, Numbering-plan-indicatorISDN,No-Reply Time 5.

BAOC Provision

SOCFNRY Notify forwarding party with number, nonotification of calling party

BS23 Delete

TS62 Define No. 61491019120002, BC=20, BS =

TS62 (Automatic Facsimile Group 3)

MDSNIMSI,2400119120000CFU,1,0,TS10CFNRY,1,1,6102419300203,1,1,5 BAOC,1SOCFNRY,1,0BS23,0TS62,1,61,491,019120002,20

Example of the above profile using MSISDN as a subscriber identifier:

MDSNIMSI,2400119120000CFU,1,0,TS10CFNRY,1,1,6102419300203,1,1,5 BAOC,1SOCFNRY,1,0BS23,0TS62,1,61,491,019120002,20

Example of the above profile using MSISDN as a subscriber identifier:

MDSNMSISDN,61149101912001CFU,1,0,TS10CFNRY,1,1,6102419300203,1,1 ,5BAOC,1SOCFNRY,1,0BS23,0TS62,1,61,491,019120002,20

Example of a successful message response:

00


NN10300-446 01.02 Standard


.


32/387


Example of an unsuccessful message response, IMSI is not defined:

9D

MDSN Data Replacement and Data Merging ExamplesThe MDSN command can be used to replace existing subscription data ormerge new data with existing subscription information.

Data Replacement ExampleConsider the following example DPSN response:

00IMSI,2400119120000CFB,1,1,61019192222,1,1,TS10

This example response shows CFB provisioned and registered with callforward number 61019192222, nature of address international number and

numbering plan indicator ISDN against Speech.

If the following example MDSN message request is issued

CFB,x,1,61019192345,1,1,TS10

this message will overwrite the existing call forward number(61019192222) with the new call forward number (61019192345).

The original DPSN response will now contain the following information:

00IMSI,2400119120000CFB,1,1,610191922345,1,1,TS10

Data Merging ExampleConsider the following example DPSN response:

00IMSI,2400119120000BAIC,1,1,TS10,1,BS20

This example response shows BAIC provisioned and registered forSpeech and CDA.

If the following example MDSN message request is issued (to registerBAIC for all applicable BSGs should the service be provisioned):

BAIC,x,1

the MDSN message will merge any unregistered, applicable, BSGs withthe existing subscription data.

The original DPSN response will now contain the following information:


NN10300-446 01.02 Standard


.


33/387


34/387


Delete a Subscription (DESN)

The DESN command allows previously defined subscriptions to bedeleted together with all associated subscription data. This results in the

deprovisioning of all basic and supplementary services and the subscriberbeing set out of service.

Once the DESN command has successfully completed, the subscriber canbe removed from the database using the DESB command.

Request syntax

:=

DESN_provisioning_request>

IMSI, | MSISDN, International Mobile Subscriber Identity (IMSI) in





the CC, NDC and SN For further information to


Response Syntax

:=

For information on response codes, refer to

TableTable 13 "Message Responses - Meaning

and Occurrence" (page 367).

ExamplesExample request to delete subscription with IMSI 2400119120000:

DESNIMSI,2400119120000

Example of a successful message response:

00

Example of an unsuccessful message response, where no subscriptionwith this IMSI is defined:

9D


NN10300-446 01.02 Standard


.


35/387

Response Syntax 35

Display a Subscription (DPSN)

The DPSN command displays the subscription information provisionedfor a subscriber.

Request syntax

:= DPSN[]*







the CC, NDC and SN. For more information see

Provisioning identifier (page 14)

HLRID, | HLRNAME,





HLRONLY

HLRONLY Display messages query the HLR and not theOracle Database.

A service in the HLR as defined inSubscription

Data Syntax (page 54)

Response Syntax

DPSN_message_response> := [IMSI,][ ]*

Refer to TableTable 13 "Message Responses - Meaning and

Occurrence" (page 367)for response codes.

International Mobile Subscriber Identity (IMSI) in international E.212

format. 6-15 digits, including the MCC, MNC and MSIN.

Designated information associated with a subscriber stored in the

HLR as defined inSubscription Data Syntax (page 54).


NN10300-446 01.02 Standard


.


36/387


If the request message does not specify a , or set of data ids,all will be returned in the response. Otherwise, theresponse will contain the data ids sent in the request, in the order that theywere included in the request.

The following information is not returned in a DPSN response:

Not provisioned state

Not registered state

Read only data ids (SGSN and CVLR) if the data is not set or isunknown at the HLR

On the Data Server, the following information is not returned in theresponse of a DPSN with no parameters (i.e. DPSN of all the data fields):

The location data. But the location data can be added to the responseof a DPSN with no parameters by changing the user config.

When the HLR contains subscriber parameters that have no definitionin the MSP version being used, a ? character is sent. This is specificbehaviour of the DPSN command.

ExampleExample request to display the subscription with IMSI 2400119120000:

DSPNIMSI,2400119120000

Example of a successful message response from HLR-PM to display allsubscriber data:

00IMSI,2400119120000AOCC,1CLIP,1,0MPTY,1,1HOLD,1, BAIC,1BAOC,1BOICEXHC,1,1,TS10CW,1CFB,1CFNRC,1 CFNRY,1,1,61019192000,1,1,20,TS10,1,61019192000,1,1,20,BS30CFU,1,1,61101 912000,1,1,TS10,1,61101912000,1,1,BS30ODBO,1CAT,1PWD,0876BICCTRL,1BOCCTRL,1ROAMENT,UNKWISTATUS,ISOAPROV,NSOCFB,0,0H T>SOCFNRC,0SOCFNRY,0,0SOCFU,0TS11,1,61,123,311000,1BS33,1,61 ,123,31101,NIL

IMSI 2400119120000

AOCC advice of charge (charging) is provided and

activated

CLIP is provided and activated with no override

provisioned

MPTY is provided and activated for 6 port


NN10300-446 01.02 Standard


.


37/387

Example 37

HOLD is provided and activated

BAIC is provided (not activated)

BAOC is provided (not activated)

BOICEXHC is provided and active operational for TS10

(Speech)

CW is provided (not activated)

CFB is provided (not activated)

CFNRC is provided (not activated)

CFNRY is provided and active for TS10 (Speech)

and BS30 (CDS) with Forward-to-number

61019192000, Nature-of-address international

number, Numbering-plan-indicator ISDN

and

No-reply-time of 20 secs

CFU is provided and active for TS10 (Speech)

and BS30 (Fax) with Forwarded-to number

61101912000, Nature-of-address international

number, Numbering-plan-indicator ISDN

ODBO operator determined BAOC is active

CAT 1 (Subscriber priority)

PWD 0876 (password)

BICCTRL by the operatorBOCCTRL by the operator

ROAMENT is set to UNKW

ISTATUS Subscriber is in-service

SOAPROV set to no

SOCFB no notification to calling party for CFB, no

notification to forwarding party for CFB

SOCFNRC calling party notified with number for CFNRC

SOCFNRY no notification to calling party for CFNRY, no

notification to forwarding party for CFNRY

SOCFU calling party notified with number for CFU

TS11 CC = 61 NDC = 123, SN = 311000, BC = 1

BS33 CC = 61 NDC = 123, SN = 31101, BC = NIL

Example message request to display the call forwarding service data of thesubscription with IMSI 2400119120000:


NN10300-446 01.02 Standard


.


38/387


DPSNIMSI,2400119120000CFBCFNRYTS10SOCFNRY

Example of the above message using MSISDN as the subscriber identifier:

DPSNMSISDN,116542000CFBCFNRYTS10SOCFNRY

Example of a successful message response from HLR-PM:

00CFNRY,1,1,44304823310,1,1,20,TS10SOCFNRY,0,0

The following response shows a scenario where the HLR contains a valuefor CAT that is not defined in the MSP version being used.

00CAT,?

Example message request to display all service data of the subscriptionwith IMSI 2400119120005 and provisioned on HLR having HLRNAME

LONDON:

DPSNIMSI,2400119120005,HLRNAME,LONDON

Example of an unsuccessful message response caused because the HLRis temporarily busy:

ED


NN10300-446 01.02 Standard


.


39/387

Response Syntax 39

Modify SIMR Information (MDSR)

The MDSR command adds or modifies SIM replacement informationfor a subscriber. The refers to the replacement (new)

subscriber.

The new subscriber must be added prior to the provisioning of SIMreplacement.

The MDSR operation with the USER swap tag is not allowed forsubscribers located on an ATCA HLR node.

Request syntax

:= MDSR

IMSI,




OLDIMSI, |OLDMSISDN,

The OLDMSISDN is used only when modifying

(using MDSR). It is never returned as a result of

a display (DPSR).

FIXED, | USER,,

10 numeric characters indicating invocation

time in YYYYMMDDHH (year/month/day/hour)

format, for example 2005122512 represents 12

oclock on the 25th December 2005.

10 numeric characters indicating activation



oclock on the 25th July 2005.

Response Syntax

:=

Refer to TableTable 13 "Message Responses -

Meaning and Occurrence" (page 367)for response

codes.


NN10300-446 01.02 Standard


.


40/387


41/387

Response Syntax 41

Display SIMR Information (DPSR)

The DPSR command displays SIM replacement information provisionedfor a subscriber. The provisioning identifier can refer to either the existing

(old) subscriber or the replacement (new) subscriber.

Request syntax

:=

DPSR









HLRID, | HLRNAME,


HLR name, symbolic string of 1-32alphanumeric, - and _ characters (firstcharacter must be a letter).

HLRONLY

HLRONLY Display message requesting the HLR and not

the Oracle Database.

Response Syntax

:=

[IMSI,]

See tableTable 13 "Message Responses

- Meaning and Occurrence" (page 367) for

information on response codes.

The IMSI number of the replacement (new)

subscriber.


NN10300-446 01.02 Standard


.


42/387


OLDIMSI, |OLDMSISDN,

This information is not sent if there is no SIMR

information provisioned.The OLDMSISDN is

used only when modifying (using MDSR). It isnever returned as a result of a display (DPSR).

FIXED, | USER,,

10 numeric characters indicating invocation



oclock on the 25th December 2005.

10 numeric characters indicating activationtime in YYYYMMDDHH (year/month/day/hour)format, for example 2005072512 represents 12oclock on the 25th July 2005.

ExamplesExample of a request to display SIMR information (using new IMSI):

DPSRIMSI,2400119120001

Example of a response showing scheduled SIM replacement provisionedat midnight on the 22nd May 2005:

00IMSI,2400119120001OLDIMSI,2400119120002FIXED,2005052200

Example of a request to display SIMR information (using old IMSI):

DPSRIMSI,2400119120002

Example of a response showing user-triggered SIM replacement from 6pm(18:00) on the 19th September 2005 to 9pm (21:00) on the 1st January2006:

00IMSI,2400119120001OLDIMSI,2400119120002USER,2005091918, 2006010121

Example of a request to display SIMR information for a subscriberprovisioned on HLR having HLRID AA30:

DPSRIMSI,2400119120005,HLRID,AA30

Example of a response where no SIMR information is provisioned:


NN10300-446 01.02 Standard


.


43/387


44/387


Delete SIMR Information (DESR)

The DESR command deletes SIM replacement information provisionedfor a subscriber. The provisioning identifier can refer to either the existing

(old) subscriber or the replacement (new) subscriber.

Once the DESR command has successfully completed, the subscriber canbe removed from the database using the DESB command.

Request syntax

:=

DESR

IMSI, | MSISDN,

International Mobile Subscriber Identity (IMSI) ininternational E.212 format. 6-15 digits, including






Response syntax

:=


- Meaning and Occurrence" (page 367)for


ExamplesExample of a request to delete SIMR information:

DESRIMSI,2400119120001


00

Example of an error response indicating that the subscriber is not definedin the HLR:

9D


NN10300-446 01.02 Standard


.


45/387

Examples 45

Translate (TRAN)

The TRAN command allows translation of an MSISDN to an IMSI. AnMSISDN is assigned to a subscriber when provisioning a Basic Service.

Request syntax

:= TRAN

msisdn_number>[,]

Only MSISDN is applicable to the TRAN

command.



the CC, NDC and SN. For more information seeProvisioning identifier (page 14).

HLRONLY

HLRONLY Display requesting the HLR and not the Oracle

Database.

Response syntax

:= [IMSI,]

Field Description


- Meaning and Occurrence" (page 367)for





Examples Example of a request to translate an MSISDN to IMSI:

TRANMSISDN,611239120001


00IMSI,2400119120001


NN10300-446 01.02 Standard


.


46/387


Example of an error response indicating that the subscriber is not definedin the HLR:

9D


NN10300-446 01.02 Standard


.


47/387


48/387

48 Provisioning subscriber data

Provisioning and Deprovisioning Status

The provisioning setting expression provides information onhow the provisioning states of the service should change. The following

actions are provided: 0 - deprovision

1 - provision

x - no change

0 - deprovision the serviceWhen a service is deprovisioned, all service information is removed,including registration data such as Call Forwarding numbers. For example:

CFNRY,0

deprovisions the Call Forward No Reply service.

If the service is already deprovisioned, no error message is generated.

1 - provision the serviceWhen a service is provisioned, it becomes available for registration. Aservice can be provisioned without being registered. For example:

CW,1

provisions the Call Waiting service.

If a service is already provisioned, no change is made.

X - no change to the provisioning stateWhen the no change provisioning state is used, no change is made tothe provisioning state.

The use of the no change provisioning state affects the processing ofBSG-based services depending on whether a registration or deregistration

is being made.

The behavior of the three provisioning actions is summarized in Table 1"Provisioning actions" (page 49). These columns represents the initialstate of the service and each row represents an MSP message. The resultof the operation is given in each box indicating that the HLR remainsunaffected.


NN10300-446 01.02 Standard


.


49/387

X - no change to the provisioning state 49

Table 1Provisioning actions

Initial StatesOperation

Not provisioned Provisioned, not

registered

Provisioned,

registereddataid,0 Unaffected Not provisioned Not provisioned

dataid,1 Provisioned, not

registered

Unaffected Unaffected

dataid,1,0 Provisioned, not

registered

Unaffected Provisioned, not

registered

dataid,1,1,reg_data Provisioned, registered Provisioned, registered Provisioned, registered

dataid,X Unaffected Unaffected Unaffected

dataid,X,0 Unaffected Unaffected Provisioned, not

registereddataid,X,1,reg_data Unaffected Provisioned, registered Provisioned, registered


NN10300-446 01.02 Standard


.


50/387


Registering and deregistering services against

Basic Service groups

RegistrationOnce a service is provisioned it can be registered against a specificBSG. For some services, registration data is provided, for example aCall Forwarding number. The MSP syntax allows two basic forms ofregistration and deregistration - specific and general.

Specific registration allows registration data to be applied to a list ofBSGs. Any registration data already in the HLR that is not specified in theregistration data list is unaffected, for example:

CFU,1,1,54321,1,1,TS10,1,12345,1,1,BS20

provisions call forward unconditional, registers 54321 against speech and12345 against CDA.

General registration allows a single piece of registration data to be appliedto all provisioned BSGs:

COS,1,1,10,NIL

This example will provision COS and register a CUSTGRP of 10 andNCOS of NIL against all BSGs provisioned at that time.

If a later request provisions another BSG, the registration data will not beapplied to the new BSG.

Before setting registration data, the service must be provisioned. This canbe done by explicitly setting the provisioning state to provision as shownin the examples above. If the provisioning state is set to no change, theregistration information is only applied if the service is already provisionedin the HLR, for example:

BAIC,X,1,TS10,1,BS20

In this example, incoming barring will be registered for speech and CDAonly if incoming barring is already provisioned.

DeregistrationAs for registration, a service can be deregistered in two ways - specificand general. In both cases, once information has been deregistered, it islost from the HLR.


NN10300-446 01.02 Standard


.


51/387


52/387


53/387

BSG-based Supplementary Service Shorthand 53

Common sections

The following section defines parameters that are common to multiplecommands.

Provides information on how the provisioning

states of the service should change. For

information on provisioning states see

Provisioning and Deprovisioning Status (page

48).

The country code of the MSISDN.

The national destination code of the MSISDN.

The subscriber number of the MSISDN.

Bearer capability to be associated with the

Basic Service (as defined in table GHLRBCA).


54/387


55/387


| |

| | | | | |

| | | | | | | | | | | | | | | | | | | | | | | |

| | | | | | | | | | | |

:=

| | | | | | |

| | | | | | | | | | | |

| | | | | | | |


NN10300-446 01.02 Standard


.


57/387


data>| | | |

| | | | | | | | | | | | | | | | | | | | |

Table 2MSP data ids

MSP data id Service Service type

ACC Account Code Supplementary ServiceAOCC Advice of Charge Supplementary Service

AOCI Advice of Charge Information Supplementary Service

ACRJ Anonymous Call Rejection Supplementary Service

BAIC Barring of all Incoming Calls BSG-based Supplementary

Service

BAOC Barring of All Outgoing Calls BSG-based Supplementary

Service

BICCTRL Control of Incoming Barring Subscriber Attributes

BICROAM Barring of Incoming Calls whileRoaming outside of Home

Country

BSG-based SupplementaryService

BOCCTRL Control of Outgoing Barring Subscriber Attributes

BOIC Barring of Outgoing

International Calls

BSG-based Supplementary

Service


NN10300-446 01.02 Standard


.


58/387


59/387


Table 2MSP data ids (contd.)

CFNRC Call Forwarding Not

ReaChable

BSG-based Supplementary

Service

CFNRY Call Forwarding on No ReplY BSG-based SupplementaryService

CFU Call Forwarding Unconditional BSG-based Supplementary

Service

CLIN Calling Line Identification

Number

Supplementary Service

CLIP Calling Line Identification

Presentation


CLIR Calling Line Identification

Restricted


COLP Connected Line IdentificationPresentation


COLR Connected Line Identification

Restricted


COS Class Of Service BSG-based Supplementary

Service

CNAM Calling Name Delivery Supplementary Service

CRBT Customized Ring Back Tone Supplementary Service

Options

CSRECL Call Session Related External

Client List


CSRXECL Call Session Related eXtended

External Client List


CSUXECL Call Session Unrelated

eXtended External Client

List


CUG CUG feature CUG Service

CUGSUB CUG subscription CUG Service

CVLR Current VLR number Read only data

CW Call Waiting BSG-based Supplementary

Service

DCSI Dialled-Camel Subscription

Information

CAMEL Supplementary

Service

EMLPP Priority options for eMLPP and

WPS


Options


NN10300-446 01.02 Standard


.


60/387


Table 2MSP data ids (contd.)

ECT Explicit Call Transfer Supplementary Service

EXT Extension BSG-based Supplementary

Service

FM COR and Supplementary COR

options for Follow Me


Options

GCSI GPRS-Camel Subscription

Information

CAMEL Supplementary

Service

GPRSCNTX GPRS PDP context data GPRS Service

HOLD Call Hold Supplementary Service

HOTBILL Hot Billing Supplementary Service

INORIG Originating IN index Subscriber Attributes

INTERM Terminating IN index Subscriber Attributes

ISTATUS Subscriber service status Subscriber Attributes

LCO Local Calls Only Supplementary Service

LCS Location Services Supplementary Service

LMU Location Measurement Unit Subscriber Attributes

MCSI Mobility Management CAMEL

Subscription Information

CAMEL Supplementary

Service

MCT Malicious Call Trace Supplementary Service

MPTY Multiparty Supplementary Service

NAM Network Access Mode Subscriber Attributes

ODBAECT ODB of all Explicit Call

Transfer

Subscriber Attributes

ODBCCFMGT ODB of conditional call

forwarding subscriber

management


ODBCHDECT ODB of Explicit Call Transfer

when at least one of the calls

is charged to the served

subscriber


ODBCISSMGT ODB of supplementary

services management


ODBDBCECT ODB of Explicit Call Transfer

when both of the calls

are charged to the served

subscriber



NN10300-446 01.02 Standard


.


61/387


62/387


63/387


Basic Service Groups

Basic Services are organized into groups of services (BSGs). Whenthe first Basic Service is subscribed, this BSG is understood as being

subscribed, which implies that Supplementary Services can be activatedfor this BSG.

Basic Service Groups (page 63)lists the Basic Service Groups.

Table 3Basic service groups

MSP tags Basic service group MSP data IDs

TS10 Speech TS11

TS20 Short Message Service TS21

TS22

TS60 Facsimile TS61

TS62

TSD0 Auxiliary Speech TSD1

BS20 Circuit Duplex Asynchronous BS20

BS20G

BS21

BS22

BS23

BS24

BS25

BS26BS81A

BS61A

BS30 Circuit Duplex Synchronous BS30

BS30G

BS31

BS32

BS33

BS34

BS81S

BS61S

VGS Voice Group Services VBS

VGCS


NN10300-446 01.02 Standard


.


64/387


Account Code (ACC)

This service allows the subscriber to classify and charge their calls tovarious accounts or persons.

Syntax

,

ACC

0 | 1,0 = deprovision the service.1 = provision the service.

For a description of the provisioning settings

refer toProvisioning and Deprovisioning

Status (page 48).

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |12 | 13 | 14 | 15 | 16 | VOL | NV

1- 16 provisions ACC with the account code (a

number between 1 and 16)

VOL = provision ACC with account code

voluntary.

NV = provision ACC with account code not

verified.

MDSN Examples

The MDSN command allows multiple services to be modified within a

single message, for further information refer toService Ordering and

Rollback (page 362). When adding, modifying or removing services

for a subscriber, it is strongly recommended that the user place all the

subscription information within one MSP message. This will provide a

real-time saving over sending several messages.

MDSNIMSI,456230000001015ACC,1,4

This example provisions ACC with account code 4.

MDSNIMSI,456230000001015ACC,1,VOL

This example provisions ACC with account code voluntary.

MDSNIMSI,456230000001015ACC,1,NV

This example provisions ACC with account code not verified.


NN10300-446 01.02 Standard


.


65/387


66/387


Alternate Speech and Data (CDS) (BS61S)

This service provides the capability to swap between speech and dataduring a call. This service belongs to the CDS BSG.

Syntax

:= ,

BS61S

0 | 1[,,,,]

0 = deprovision the service.

1 = provision the service.

For a description of the provisioning settingsrefer toProvisioning and Deprovisioning

Status (page 48).

The following parameters are optional. Ifthe,,, sequence is notspecified, the MSISDN provisioned againstBasic Service Telephony will be used.

The country code of the MSISDN (1-3) digits).

The national destination code of the MSISDN (1

- 13 digits).

The subscriber number of the MSISDN (1 - 13

digits).

The number of digits in the


67/387

Syntax 67

MDSNIMSI,456230000001015BS61S,1

This example provisions the BS61S service with the MSISDN provisioned

against the Telephony Basic Service.

MSDNIMSI,456230000001015BS61S,1,61,123,7221234,NIL

This example provisions the BS61S service with the MSISDN611237221234 and adds no extra bearer capability information.

MSDNIMSI,456230000001015BS61S,0

This example deprovisions the BS61S service.

DPSN Examples

The following DPSN message requests the status of the BS61S service:

DPSNIMSI,2400119120000BS61S

The following example DPSN response shows BS61S provisioned with

MSISDN 6112331101 without bearer capability information.

00IMSI,2400119120000BS61S,1,61,123,31101,1

If the BS61S service is not provisioned, it will be absent from the DPSN

response. For example:

00IMSI,2400119120000


NN10300-446 01.02 Standard


.


68/387


Alternate Speech and Fax group 3 (TS61)

This service provides the services of speech and fax alternately within thesame call controlled by the handset. Data rates for the Fax portion of the

call can be up to 14.4kbps.

Syntax

:= ,

Parameter Description

TS61

0 | 1[,,,]





Status (page 48).

The following parameters are optional. If the

, , , sequence is not

specified, the MSISDN provisioned against

Basic Service Telephony will be used.



- 13 digits).


69/387

Syntax 69




MDSNIMSI,456230000001015TS61,1,61,123,7221234,NIL

This example provisions the TS61 service with the MSISDN611237221234 and adds no extra bearer capability information.

MDSNIMSI,456230000001015TS61,0

This MDSN example deprovisions the TS61 service.

DPSN Examples

The following DPSN message requests the status of the TS61 service:

DPSNIMSI,2400119120000TS61

The following example DPSN response shows TS61 provisioned with

MSISDN 6112331101 without bearer capability information.

00IMSI,2400119120000TS61,1,61,123,31101,NIL

The following example DPSN response shows TS61 provisioned with

MSISDN 6112331101 with a bearer capability of 1.

00IMSI,2400119120000TS61,1,61,123,31101,1

If the TS61 service is not provisioned, it will be absent from the DPSN


00IMSI,2400119120000


NN10300-446 01.02 Standard


.


70/387


Anonymous Call Rejection (ACRJ)

This service offers the subscriber the ability to reject anonymous calls.

Syntax := ,

ACRJ

0 | 1





Status (page 48).

MDSN Examples







MDSNIMSI,456230000001015ACRJ,1

This MDSN example provisions and activates ACRJ.

MDSNIMSI,456230000001015ACRJ,0

This MDSN example deprovisions and withdraws ACRJ.

DPSN Examples

The following DPSN message requests the status of the ACRJ service:

DPSNIMSI,2400119120000ACRJ

The following example DPSN response shows ACRJ provisioned:

00IMSI,2400119120000ACRJ,1

If the ACRJ service is not provisioned, it will be absent from the DPSN


00IMSI,2400119120000


NN10300-446 01.02 Standard


.


71/387

Syntax 71

Automatic Facsimile group 3 (TS62)

This service allows connection of CCITT group 3 fax apparatus to andfrom a mobile station. Data rates of the Fax service can be up to 14.4kbps

at MAP version 3 and above.

Syntax

:= ,


TS62_data_id>

0 | 1[,,,,]





Status (page 48).


,, sequence is not specified,

the MSISDN provisioned against Basic Service

Telephony will be used.



- 13 digits).


digits).

The number of digits in the ,,and sequence is restricted to a maximum of 15.

NIL |



A value of 0-255.

MDSN Examples





NN10300-446 01.02 Standard


.


72/387





MDSNIMSI,456230000001015TS62,1

This MDSN example provisions the TS62 service with the MSISDNprovisioned against the Telephony Basic Service.

MDSNIMSI,456230000001015TS62,1,61,123,7221234,NIL

This example provisions the TS62 service with the MSISDN

611237221234 and adds no extra bearer capability information.

MDSNIMSI,456230000001015TS62,0

This example deprovisions the TS62 service.

DPSN Examples

The following DPSN message requests the status of the TS62 service:

DPSNIMSI,2400119120000TS62

The following example DPSN response shows TS62 provisioned withMSISDN 6112331101 without bearer capability information.

00IMSI,2400119120000TS62,1,61,123,31101,NIL

The following example DPSN response shows TS62 provisioned withMSISDN 6112331101 with a bearer capability of 1.

00IMSI,2400119120000TS62,1,61,123,31101,1

If the TS62 service is not provisioned, it will be absent from the DPSNresponse. For example:

00IMSI,2400119120000


NN10300-446 01.02 Standard


.


73/387

Syntax 73

Auxiliary Telephony (TSD1)

This service is also known as the Alternate Line Service. It is a proprietaryservice which associates a second Telephony MSISDN with a subscriber

for Telephony calls. The two lines have a separate Supplementary Serviceprofiles and are billed separately.

Syntax

:= ,


TSD1

0 | 1[,,,,]





Status (page 48).


,, sequence is not specified,

the MSISDN provisioned against Basic Service

Telephony will be used.



- 13 digits).


digits).

The number of digits in the ,,and sequence is restricted to a maximum of 15.

NIL |



A value of 0-255.

MDSN Examples



Rollback (page 362).When adding, modifying or removing services


NN10300-446 01.02 Standard


.


74/387


75/387

Syntax 75

Barring of All Incoming Calls (BAIC)

This service prevents the subscriber from receiving any incoming calls.

Syntax := ,

BAIC

0 | 1 | 1[, | X | X,



X- no change



Status (page 48).

0 | 1 |

0 = deregister for all applicable Basic Service

Groups.

1 = register for all applicable Basic Service

Groups.

| ,

0, | 1,

TS10 | TS20 | TS60 | TSD0 | BS20 | BS30

A value of 0-255.

TS10 = Speech

TS20= Short Message Service

TS60 = Facsimile

TSD0 = Auxiliary Speech

BS20 = Circuit Duplex Asynchronous

BS30 = Circuit Duplex Synchronous


NN10300-446 01.02 Standard


.


76/387


77/387

Syntax 77

The following example DPSN response shows BAIC provisioned and

registered against Speech and CDA.

00IMSI,2400119120000BAIC,1,1,TS10,1,BS20

The following example DPSN response shows BAIC provisioned and

registered against all applicable BSGs.

00IMSI,2400119120000BAIC,1,1,TS10,1,TS20,1,TS60,1,TSD0,1,BS20,1,BS30

If the BAIC service is not provisioned, it will be absent from the DPSN


00IMSI,2400119120000


NN10300-446 01.02 Standard


.


78/387


Barring of All Outgoing Calls (BAOC)

This service prevents the subscriber from making any outgoing calls, withthe exception of emergency calls.

Sytax

:= ,

BAOC

0 | 1 | 1[, | X | X,



X- no change



Status (page 48).

0 | 1 |


Groups.

1 = register for all applicable Basic ServiceGroups.

| ,

0, | 1,

TS10 | TS20 | TS60 | TSD0 | BS20 | BS30| VGS

TS10 = Speech


TS60 = Facsimile





NN10300-446 01.02 Standard


.


79/387

Sytax 79


MDSN Examples


single message, for further information refer toService Ordering andRollback (page 362). When adding, modifying or removing services




MDSNIMSI,456230000001015BAOC,X,1,TS10,1,BS20

This example registers the BAOC service for speech and CDA only if the

BAOC service is already provisioned.

MDSNIMSI,456230000001015BAOC,X,0,TS10,0,BS20

This example deregister the BAOC service for speech and CDA only if the

service is already provisioned. If the BAOC service is not provisioned it

will remain unprovisioned.

MDSNIMSI,456230000001015BAOC,1,1,TS10

This example provisions the BAOC service and registers the service for

Speech.

MDSNIMSI,456230000001015BA0C,1,0

This example provisions the BAOC service and deregisters all applicable

BSG(s) registered against the service.

MDSNIMSI,456230000001015BA0C,1,1This example provisions the BAOC service and registers all applicable

BSG(s) against the service.

MDSNIMSI,456230000001015BAOC,X,0,TS10

This example deregisters the BAOC service for Speech only if the service

is already provisioned.

MDSNIMSI,456230000001015BAOC,0

This example deprovisions the BAOC service.

DPSN ExamplesThe following DPSN message requests the status of the BAOC service:

DPSNIMSI,2400119120000BAOC

The following example DPSN response shows BAOC provisioned and

registered against Speech.

00IMSI,2400119120000BAOC,1,1,TS10


NN10300-446 01.02 Standard


.


80/387



registered against Speech and CDA.

00HT>IMSI,2400119120000HT>BAOC,1,1,TS10,1,BS20


registered against all applicable BSGs.

00IMSI,2400119120000BAOC,1,1,TS10,1,TS20,1,TS60,1,TSD0,1,BS20,1,BS30

If the BAOC service is not provisioned, it will be absent from the DPSN


00IMSI,2400119120000


NN10300-446 01.02 Standard


.


81/387

Syntax 81

Barring of Incoming Calls while Roaming outside of

Home Country (BICROAM)

This service prevents the subscriber from receiving any incoming calls ifthe subscriber is roaming outside their Home PLMN country.

Syntax

:= ,

BICROAM

0 | 1 | 1[, | X | X,



X- no change



Status (page 48).

0 | 1 |


Groups.

1 = register for all applicable Basic Service

Groups.

| ,

0, | 1,

TS10 | TS20 | TS60 | TSD0 | BS20 | BS30| VGS

TS10 = Speech


TS60 = Facsimile




NN10300-446 01.02 Standard


.


82/387




MDSN ExamplesThe MDSN command allows multiple services to be modified within a






MDSNIMSI,456230000001015BICROAM,X,1,TS10,1,BS20

This example registers the BICROAM service for Speech and CDA only if

the service is already provisioned.

MDSNIMSI,456230000001015BICROAM,1,1,TS10

This example provisions the BICROAM service and registers all applicable

BSGs against the Speech service.

MDSNIMSI,456230000001015BICROAM,X,0,TS10,0,BS20

This example deregisters the BICROAM service for Speech and CDA only

if the service is already provisioned. If the service is not provisioned it will

remain unprovisioned.

DPSN Examples

The following DPSN message requests the status of the BICROAMservice:

DPSNIMSI,2400119120000BICROAM

The following example DPSN response shows BICROAM provisioned and

registered against Speech.

00IMSI,2400119120000BICROAM,1,1,TS10

The following example DPSN response shows BICROAM provisioned and

registered