A.4 Contents of messages

23.0663GPPRelease 17Stage 2Support of Mobile Number Portability (MNP)Technical realizationTS

This clause specifies the content of the following messages:

On the ISUP interface:

IAM.

On the MSC – NPDB interface:

"query";

"routing";

"result".

Messages in the MSC – NPDB interface are mapped into ETSI Core INAP or ANSI IN Query messages according to the protocols on this interface. This is listed in the following table:

Messages in MSC-NPDB interface

INAP messages

ANSI IN Query messages

"query"

INITIAL DP

ProvideInstruction:Start

"routing"

CONNECT

CONTINUE

ConnectionControl:Connect

"result"

CONTINUE

RELEASE CALL

ConnectionControl:Connect

In the tables that follow, information elements are shown as mandatory (M), conditional (C) or optional (O). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or absent, at the discretion of the application at the sending entity.

A.4.1 Messages on the ISUP interface

A.4.1.1 IAM for ETSI ISUP interface

This message is specified in [14]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [14].

A.4.1.2 IAM for ANSI ISUP interface

This message is specified in [8] and [9]. It is necessary for the IAM to contain the information needed to route the call to the subscription network of the ported subscriber. The ways in which this may be coded are shown in [8] and [9].

A.4.2 Messages on the MSC – NPDB interface

A.4.2.1 INITIAL DP

This message is specified in [5]. The following information elements are required:

Information element name

Required

Description

Service Key

M

Identifies the requested IN service (MNP query)

Called Party Number

M

The possibly ported MSISDN

A.4.2.2 INITIAL DP negative response

This message is specified in [5]. The negative response information element can take the following values:

1. missing parameter;

2. unexpected data value;

3. unexpected parameter;

4. system failure.

A.4.2.3 CONNECT

This message is specified in [5]. It shall be ensured that the information in the Connect message shall be aligned with the coding supported in the ISUP signalling.

A.4.2.4 CONTINUE

This message is specified in [5]. This message does not contain any information element.

A.4.2.5 RELEASE CALL

This message is specified in [5]. The following information elements are required:

Information element name

Required

Description

Cause

M

Indicates the reason for releasing the call

A.4.2.6 ProvideInstruction:Start

Parameter

Type

Number of Octets

Contents

Package Type Identifier

M

1

Query with Permission

Component Type Identifier

M

1

Invoke (last)

Operation Code Identifier

M

1

National TCAP

Operation Code

M

2

provideInstruction:Start (reply required)

Service Key

M

11*

10 digit called party number digits

Digits (calling party number)

M 1

6-9

3,6 or 10 ANI digits

Digits (LATA)

M 1

6

LATA ID

Originating Station Type

M 1

1

Binary value of ANI II digits

Note:

* = Value specific for number portability

1 = This mandatory parameter is required for the message but the content is not essential for number portability.

A.4.2.7 ConnectionControl:Connect

Parameter

Type

Number of Octets

Contents

Package Type Identifier

M

1

Response

Component Type Identifier

M

1

Invoke (last)

Operation Code Identifier

M

1

National TCAP

Operation Code

M

2

connectionControl:Connect (no reply required)

Digits (Carrier)

M 1

6

3 or 4 digit CIC

Digits (Routing Number)

M

9*

10 digit RN or Dialed Number

Billing Indicators

M 1

4

Unspecified

Note:

* = Value specific for number portability

1 = This mandatory parameter is required for the message but the content is not essential for number portability.

Annex B (normative):
Handling of Non-Call Related Signalling