Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.066  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   A…   A.1.4…   A.2   A.3…   A.4…   B…   B.3…   B.4…   B.4.4…   B.4.7…   C…   C.2…   C.3…   C.3.3…   C.3.6…   C.4   C.5…

 

A.4  Contents of messagesp. 39

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 DPProvideInstruction: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.
Up

A.4.1  Messages on the ISUP interfacep. 39

A.4.1.1  IAM for ETSI ISUP interfacep. 39

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 interfacep. 39

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].
Up

A.4.2  Messages on the MSC - NPDB interfacep. 39

A.4.2.1  INITIAL DPp. 39

This message is specified in [5]. The following information elements are required:
Information element name Required Description
Service KeyMIdentifies the requested IN service (MNP query)
Called Party NumberMThe possibly ported MSISDN
Up

A.4.2.2  INITIAL DP negative responsep. 40

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  CONNECTp. 40

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  CONTINUEp. 40

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

A.4.2.5  RELEASE CALLp. 40

This message is specified in [5]. The following information elements are required:
Information element name Required Description
CauseMIndicates the reason for releasing the call
Up

A.4.2.6  ProvideInstruction:Startp. 40

Parameter Type Number of Octets Contents
Package Type IdentifierM 1Query with Permission
Component Type IdentifierM 1Invoke (last)
Operation Code IdentifierM1National TCAP
Operation CodeM 2provideInstruction:Start (reply required)
Service KeyM11*10 digit called party number digits
Digits (calling party number)M 16-93,6 or 10 ANI digits
Digits (LATA)M 16LATA ID
Originating Station TypeM 11Binary 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.
Up

A.4.2.7  ConnectionControl:Connectp. 41

Parameter Type Number of Octets Contents
Package Type IdentifierM 1Response
Component Type IdentifierM 1Invoke (last)
Operation Code IdentifierM 1National TCAP
Operation CodeM 2connectionControl:Connect (no reply required)
Digits (Carrier)M 163 or 4 digit CIC
Digits (Routing Number)M9*10 digit RN or Dialed Number
Billing IndicatorsM 14Unspecified
NOTE:
* =
Value specific for number portability
1 =
This mandatory parameter is required for the message but the content is not essential for number portability.
Up

Up   Top   ToC