Msoftx3000 V200r010c10 Typical Signaling Flows Manual 01.pdf 711m1f

MSC

This message is sent by the MS/UE to the network either to request update of its location file (generic or periodic location update) or to request IMSI attach. This message is sent by the network to notify the MS/UE that authentication has failed. The receiving MS/UE should abort all activities. This message is sent by the network to the MS/UE to initiate authentication of the MS/UE identity. This message is sent by the MS/UE to deliver a calculated authentication response to the network. This message is sent by the MS/UE to notify the network that authentication of the network has failed. This message is sent by the MS/UE to provide the requested identity to the network. This message is sent by the network to notify the MS/UE that the requested service has been accepted. This message is sent by the MS/UE to the network to request a service for the Connection Management (CM) sublayer entities, for example, circuit switched connection establishment, supplementary services activation, short message transfer, and location services. This message is sent by the network to notify the calling MS/UE that the called party is reached and alerted. This message is sent by the network to notify the calling MS/UE that the requested call establishment information has been received and no more call establishment information will be accepted. This message is sent by the called MS/UE to confirm an incoming call request. This message is sent by the called MS/UE to indicate its acceptance of the incoming call to the network. It is also sent by the network to notify the calling MS/UE of call acceptance by the called MS/UE. This message is sent by the calling MS/UE to the network to acknowledge call acceptance by the called MS/UE. It is also sent by the network to notify the called MS/UE that the calling MS/UE has been awarded the call. In the mobile originating call (MOC) scenario, this message is sent by the calling MS/UE to the network to provide more information (called party binary-coded data (BCD) number

SETUP

MS>MSC

DISCONNECT

MS<>MSC

RELEASE

MS<>MSC

RELEASE COMPLETE

MS<>MSC

FACILITY

MS<>MSC

MS>MSC HOLD MSCACKNOWLEDGE >MS START dual tone MSmultiple frequency >MSC (DTMF) HOLD

START DTMF MSCACKNOWLEDGE >MS MS>MSC STOP DTMF MSCACKNOWLEDGE >MS STOP DTMF

and calling party subaddress, for example) required to continue the MOC. In the mobile terminated call (MTC) scenario, this message is sent by the network to the called MS/UE to provide more information required to continue the MTC. This message is sent, from the network to the MS/UE or conversely, to indicate that the end-to-end connection has been cleared. This message is sent, from the network to the MS/UE or conversely, to indicate that the sender intends to release the transaction identifier and that the receiver should release the transaction identifier after sending a RELEASE COMPLETE message. This message is sent, from the network to the MS/UE or conversely, to indicate that the sender has released the transaction identifier and the receiver should also release the transaction identifier. This message is sent, from the network to the MS/UE or conversely, to request or acknowledge a supplementary service. This message is sent by the MS/UE to request the network to place the existing call on hold. This message is sent by the network to indicate that the existing call has been placed on hold. This message is sent by the MS/UE to the network. It conveys the digit the network should reconvert back into a DTMF tone which is then applied towards the remote . This message is sent by the network to the MS/UE to indicate the successful initiation of the action requested by the START DTMF message (conversion of the digit contained in this message into a DTMF tone). This message is sent by the MS/UE to request the network to stop sending the DTMF tone towards the remote . This message is sent by the network to notify the MS/UE that the sending of the DTMF tone has been stopped.

Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Reference Standards Table 1 describes the information element (IE) carried in the common part of messages. Table 1 IE carried in the common part of messages Information Element Description (IE)

layer-3information

Conveys the information that the MS/UE intends to send to the network. The reference point Um or Uu, between the MS/UE and the base station subsystem (BSS)/universal terrestrial radio access network (UTRAN), adopts a 3-layer protocol structure. Layer 3 is in essence the control layer, forcing control or system control information into dedicated logical channels based on protocol type. It consists of three sublayers: Radio Resource Management (RR), Mobility Management (MM), and Connection Management (CM). The CM sublayer provides multiple Call Control (CC) entities to allow parallel call processing. It also provides Supplementary Service (SS) entity and Short Message Service (SMS) entity to handle supplementary service and short message service. RR messages are terminated at the BSS/UTRAN where they are interpreted into Base Station Subsystem Management Application Part (BSSMAP)/Radio Access Network Application Part (RANAP) messages and flow on the A/Iu interface. MM and CM messages, however, are terminated at the MSC. The BSS/UTRAN es these messages transparently on the A/Iu interface to the MSC as DTAP messages.

An international mobile subscriber identity (IMSI) DETACH INDICATION message is considered as an example here. In this example: mm-layer-message indicates that the message belongs to the MM sublayer. skip-indicator indicates whether the message should be ignored. A message received with skip indicator different from 0000 should be

ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons. mm-msg-type indicates the type of the message, for example, IMSI DETACH INDICATION. Reference Standards For details, see 10.1 "Overview" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Registration Messages at the MM Sublayer IMSI DETACH INDICATION LOCATION UPDATING ACCEPT LOCATION UPDATING REJECT LOCATION UPDATING REQUEST Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IMSI DETACH INDICATION Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to notify the network that the MS/UE has been switched off. After reception of this message, the network places the MS/UE in international mobile subscriber identity (IMSI) Detached state so that it would not bother to page the MS/UE when learning that some other parties are attempting to reach the MS/UE. A readily apparent benefit of reducing unnecessary paging is to save scarce radio resources. Figure 1 shows the main IEs of the message. Figure 1 IMSI DETACH INDICATION message

Associated IEs Information Element (IE)

Description Identifies the L3 protocol to which the L3

message belongs. In an IMSI DETACH INDICATION message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Protocol Discriminator

Skip indicator

Indicates whether the message should be ignored. A message received with skip indicator different from 0000 should be ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons. For details, see Skip indicator.

Message Type

Indicates the type of the message. For an IMSI DETACH INDICATION message, the message type is IMSI DETACH INDICATION. For details, see Message Type.

Mobile Station Classmark 1

Indicates general characteristics of the MS/UE in multiband environment. It is included in the Mobile Station Classmark IE. For details, see Mobile Station Classmark 1.

Mobile Identity

Provides identity information of the MS/UE. For details, see Mobile Identity.

Reference Standards For details, see 9.2.12 "IMSI detach indication" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Registration Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

LOCATION UPDATING ACCEPT Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the MS/UE that location update or international mobile subscriber identity (IMSI) attach in the network has been completed. Figure 1 shows the main IEs of the message. Figure 1 LOCATION UPDATING ACCEPT message


Description


Identifies the L3 protocol to which the L3 message belongs. In a LOCATION UPDATING ACCEPT message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For a LOCATION UPDATING ACCEPT message, the message type is LOCATION UPDATING ACCEPT. For details, see Message Type.

Location Area Identification

Provides unambiguous identification of location areas where the MS/UE is staying. The location area information is stored in subscriber identity module (SIM)/ service identity module (USIM). For details, see Location Area Identification.

Mobile Identity


Reference Standards For details, see 9.2.13 "Location updating accept" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Registration Messages at the MM Sublayer Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

LOCATION UPDATING REJECT Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the MS/UE that location update or international mobile subscriber identity (IMSI) attach has failed. Figure 1 shows the main IEs of the message. Figure 1 LOCATION UPDATING REJECT message



Description Identifies the L3 protocol to which the L3 message belongs. In a LOCATION UPDATING REJECT message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol.

For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For a LOCATION UPDATING REJECT message, the message type is LOCATION UPDATING REJECT. For details, see Message Type.

Reject cause

Indicates the reason why LOCATION UPDATING REQUEST from the MS/UE is rejected by the network. For details, see Reject cause.

Reference Standards For details, see 9.2.14 "Location updating reject" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Registration Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

LOCATION UPDATING REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent by a mobile terminal to the network side to request a location update (normal or periodic location update) or an IMSI attach. Figure 1 shows the LOCATION UPDATING REQUEST message. Figure 1 LOCATION UPDATING REQUEST message

On a Multi-Operator Core Network (MOCN), when a mobile terminal that does not the MOCN feature initiates a location update (normal or periodic location update) or an IMSI attach, it sends this message carrying the Redirect Attempt Flag information element

(IE) to the network side. Figure 2 shows the LOCATION UPDATING REQUEST message carrying the Redirect Attempt Flag IE. Figure 2 LOCATION UPDATING REQUEST message carrying the Redirect Attempt Flag IE

Associated IEs IE

Description


Identifies the L3 protocol to which the L3 message belongs. In a LOCATION UPDATING REQUEST message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For a LOCATION UPDATING REQUEST message, the message type is LOCATION UPDATING REQUEST. For details, see Message Type.

Location updating type

Indicates the type of location update. For details, see Location updating type.

Ciphering Key Sequence Number

Indicates the sequence number of the ciphering key. For details, see Ciphering Key Sequence Number.


Provides unambiguous identification of location areas where the MS/UE is staying. For details, see Location Area Identification.


Includes classmark1 corresponding to the frequency band in use. For details, see Mobile Station Classmark 1.

Mobile Identity




Redirect Attempt Flag

Indicates a redirection attempt for a mobile terminal on a MOCN network. For details, see Redirect Attempt Flag.

Reference Standards For details, see section 9.2.15 "Location updating request" in 3GPP TS24008-830. Parent topic: Description of Registration Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Security Messages at the MM Sublayer AUTHENTICATION REJECT AUTHENTICATION REQUEST AUTHENTICATION RESPONSE AUTHENTICATION FAILURE IDENTITY REQUEST IDENTITY RESPONSE Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AUTHENTICATION REJECT Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the MS/UE that authentication has failed. The receiving MS/UE should abort all activities. Figure 1 shows the main IEs of the message. Figure 1 AUTHENTICATION REJECT message


Description


Identifies the L3 protocol to which the L3 message belongs. In an AUTHENTICATION REJECT message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator. Indicates whether the message should be ignored. A message received with skip

Skip indicator

Message Type

indicator different from 0000 should be ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons. For details, see Skip indicator. Indicates the type of the message. For an AUTHENTICATION REJECT message, the message type is AUTHENTICATION REJECT. For details, see Message Type.

Reference Standards For details, see 9.2.1 "Authentication reject" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AUTHENTICATION REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent by the network to the MS/UE to initiate authentication of the MS/UE identity. Figure 1 shows the main IEs of the message. Figure 1 AUTHENTICATION REQUEST message



Description Identifies the L3 protocol to which the L3 message belongs. In an AUTHENTICATION REQUEST message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM)

protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For an AUTHENTICATION REQUEST message, the message type is AUTHENTICATION REQUEST. For details, see Message Type.



Spare Half Octet

Reserved for future use. It is half-octet long. For details, see Spare Half Octet.

Authentication parameter random number (RAND)

Provides the non-predictable number to be used to calculate the authentication response parameters. For details, see Authentication parameter RAND.

Provides the UE with a means of Authentication Parameter AUTN (Universal authenticating the network. Mobile Telecommunications System (UMTS) For details, see Authentication Parameter authentication challenge only) AUTN (UMTS authentication challenge only). Reference Standards For details, see 9.2.2 "Authentication request" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential


AUTHENTICATION RESPONSE Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to deliver a calculated authentication response to the network. Figure 1 shows the main IEs of the message. Figure 1 AUTHENTICATION RESPONSE message



Description Identifies the L3 protocol to which the L3 message belongs. In an AUTHENTICATION RESPONSE message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol.

For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For an AUTHENTICATION RESPONSE message, the message type is AUTHENTICATION RESPONSE. For details, see Message Type.

Authentication Response parameter

Provides the network with the authentication response calculated in the subscriber identity module (SIM)/ service identity module (USIM). For details, see Authentication Response parameter.

Reference Standards For details, see 9.2.3 "Authentication response" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AUTHENTICATION FAILURE Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to notify the network that authentication of the network has failed. Figure 1 shows the main IEs of the message. Figure 1 AUTHENTICATION FAILURE message


Description


Identifies the L3 protocol to which the L3 message belongs. In an AUTHENTICATION FAILURE message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For an AUTHENTICATION FAILURE message, the message type is AUTHENTICATION FAILURE. For details, see Message Type.

Reject Cause

Indicates the reason why the MS/UE rejects to authenticate the network. For details, see Reject cause.

Authentication Failure parameter

Provides the network with the necessary information to begin a re-authentication procedure when Universal Mobile Telecommunications System (UMTS) authentication challenge fails.

Reference Standards For details, see 9.2.3a "AUTHENTICATION FAILURE" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IDENTITY REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent by the network to the MS/UE to request the specified identity. Figure 1 shows the main IEs of the message. Figure 1 IDENTITY REQUEST message


Description


Identifies the L3 protocol to which the L3 message belongs. In an IDENTITY REQUEST message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator. Indicates whether the message should be ignored. A message

Skip indicator

received with skip indicator different from 0000 should be ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons. For details, see Skip indicator.

Message Type

Indicates the type of the message. For an IDENTITY REQUEST message, the message type is IDENTITY REQUEST. For details, see Message Type.

Identity type

Specifies which identity is requested from the MS/UE. For details, see Identity type.

Spare Half Octet


Reference Standards For details, see 9.2.10 "Identity request" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IDENTITY RESPONSE Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to provide the requested identity to the network. Figure 1 shows the main IEs of the message. Figure 1 IDENTITY RESPONSE message


Description Identifies the L3 protocol to which the L3


message belongs. In an IDENTITY RESPONSE message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For an IDENTITY RESPONSE message, the message type is IDENTITY RESPONSE. For details, see Message Type.

Mobile Identity


Reference Standards For details, see 9.2.11 "Identity response" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Security Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Connection Management Messages at the MM Sublayer CM SERVICE ACCEPT CM SERVICE REQUEST Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CM SERVICE ACCEPT Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the MS/UE that the requested service has been accepted. Figure 1 shows the main IEs of the message. Figure 1 CM SERVICE ACCEPT message


Description


Identifies the L3 protocol to which the L3 message belongs. In a connection management (CM) SERVICE ACCEPT message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator. Indicates whether the message should be

Skip indicator

Message Type

ignored. A message received with skip indicator different from 0000 should be ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons. For details, see Skip indicator. Indicates the type of the message. For a CM SERVICE ACCEPT message, the message type is CM SERVICE ACCEPT. For details, see Message Type.

Reference Standards For details, see 9.2.5 "CM service accept" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Connection Management Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CM SERVICE REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent by a mobile terminal to the network side to request a connection management (CM) service, such as circuit switched connection establishment, supplementary service, short message service, and location service. Figure 1 shows the CM SERVICE REQUEST message. Figure 1 CM SERVICE REQUEST message

Associated IEs IE

Description


Identifies the L3 protocol to which the L3 message belongs. In a CM SERVICE REQUEST message, Protocol Discriminator takes the value 5, indicating that the message belongs to the mobility management (MM) protocol. For details, see Protocol Discriminator.

Skip indicator


Message Type

Indicates the type of the message. For a CM SERVICE REQUEST message, the message type is CM SERVICE REQUEST. For details, see Message Type.

CM service type

Specifies which service is requested from the network. For details, see CM service type.





Mobile Identity


Priority Level

Provides information defining the priority level requested or applied. For details, see Priority Level.

Reference Standards

For details, see 9.2.9 "CM service request" in 3GPP TS24008-830. Parent topic: Description of Connection Management Messages at the MM Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Call Establishment Messages at the CC Sublayer ALERTING CALL PROCEEDING CALL CONFIRMED CONNECT CONNECT ACKNOWLEDGE SETUP MODIFY MODIFY COMPLETE MODIFY REJECT Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ALERTING Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the calling MS/UE that the called party is reached and alerted. Figure 1 shows the main IEs of the message. Figure 1 ALERTING message


Description


Identifies the L3 protocol to which the L3 message belongs. In an ALERTING message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.

Transaction identifier

Distinguishes a few message flows for a given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Transaction identifier.

Message Type

Indicates the type of the message. For an ALERTING message, the message type is ALERTING. For details, see Message Type.

Facility

Conveys supplementary service related information. For details, see Facility.

Progress indicator

Describes a mid-call event. For details, see Progress indicator.

Reference Standards For details, see 9.3.1 "Alerting" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CALL PROCEEDING Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the calling MS/UE that the requested call establishment information has been received and no more call establishment information will be accepted. Figure 1 shows the main IEs of the message. Figure 1 CALL PROCEEDING message


Description


Identifies the L3 protocol to which the L3 message belongs. In a CALL PROCEEDING message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a CALL PROCEEDING message, the message type is CALL PROCEEDING. For details, see Message Type.

Bearer capability

Describes the ed bearer capability. For details, see Bearer capability.

Reference Standards For details, see 9.3.3 "Call proceeding" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CALL CONFIRMED Message Function Associated IEs Reference Standards Message Function This message is sent by the called MS/UE to confirm an incoming call request. Figure 1 shows the main IEs of the message. Figure 1 CALL CONFIRMED message


Description


Identifies the L3 protocol to which the L3 message belongs. In a CALL CONFIRMED message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.


Distinguishes a message flow for a given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Transaction identifier.

Message Type

Indicates the type of the message. For a CALL CONFIRMED message, the message type is CALL CONFIRMED. For details, see Message Type.

Reference Standards For details, see 9.3.2 "Call confirmed" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CONNECT Message Function Associated IEs Reference Standards Message Function This message is sent by the called MS/UE to indicate its acceptance of the incoming call to the network. It is also sent by the network to notify the calling MS/UE of call acceptance by the called MS/UE. Figure 1 shows the main IEs of the message. Figure 1 CONNECT message


Description


Identifies the L3 protocol to which the L3 message belongs. In a CONNECT message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a CONNECT message, the message type is CONNECT. For details, see Message Type.

Facility


Progress indicator


Connected number

Identifies the connected party of a call, for example, 13107554238. For details, see Connected number.

Reference Standards For details, see 9.3.5 "Connect" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CONNECT ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent by the calling MS/UE to the network to acknowledge call acceptance by the called MS/UE. It is also sent by the network to notify the called MS/UE that the calling MS/UE has been awarded the call. Figure 1 shows the main IEs of the message. Figure 1 CONNECT ACKNOWLEDGE message


Description


Identifies the L3 protocol to which the L3 message belongs. In a CONNECT ACKNOWLEDGE message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a CONNECT ACKNOWLEDGE message, the message type is CONNECT ACKNOWLEDGE. For details, see Message Type.

Reference Standards For details, see 9.3.6 "Connect acknowledge" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SETUP Message Function Associated IEs Reference Standards Message Function In the mobile originated call (MOC) scenario, this message is sent by the calling MS/UE to the network to provide more information (called party binary-coded data (BCD) number and calling party subaddress, for example) required to continue the MOC. In the mobile terminated call (MTC) scenario, this message is sent by the network to the called MS/UE to provide more information required to continue the MTC. Figure 1 shows the main IEs of the message. Figure 1 SETUP message


Description


Identifies the L3 protocol to which the L3 message belongs. In a SETUP message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.


Distinguishes a few message flows for a given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction.

For details, see Transaction identifier.

Message Type

Indicates the type of the message. For a SETUP message, the message type is SETUP. For details, see Message Type.

Repeat indicator

Indicates how the associated repeated information elements should be interpreted when included in a message. For details, see Repeat indicator.

Bearer capability


Called party BCD number

Identifies the called party. For details, see Called party BCD number.

Low layer compatibility

Provides a means for the addressed entity to perform compatibility check. For details, see Low layer compatibility.

Reference Standards For details, see 9.3.23 "Setup" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MODIFY Message Function Associated IEs Reference Standards Message Function This message is sent, from the MS/UE to the network or conversely, to request a change in bearer capability for a call. Figure 1 shows the main IEs of the message. Figure 1 MODIFY message

Figure 2 shows Data Bearer Capability Octet in the message. Figure 2 Data Bearer Capability Octet


Description


Identifies the L3 protocol to which the L3 message belongs. In a MODIFY message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a MODIFY message, the message type is MODIFY.

For details, see Message Type. Bearer capability


Reference Standards For details, see 9.3.13 "Modify" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MODIFY COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent, from the MS/UE to the network or conversely, to indicate that a request to change bearer capability for a call has been fulfilled. Figure 1 shows the main IEs of the message. Figure 1 MODIFY COMPLETE message

Figure 2 shows Data Bearer Capability Octet in the message. Figure 2 Data Bearer Capability Octet


Description


Identifies the L3 protocol to which the L3 message belongs. In a MODIFY COMPLETE message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a MODIFY COMPLETE message, the message type is MODIFY COMPLETE.

For details, see Message Type. Bearer capability


Reference Standards For details, see 9.3.14 "Modify complete" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MODIFY REJECT Message Function Associated IEs Reference Standards Message Function This message is sent, from the MS/UE to the network or conversely, to indicate that a request to change bearer capability for a call failed to be fulfilled. Figure 1 shows the main IEs of the message. Figure 1 MODIFY REJECT message


Description Identifies the L3 protocol to which the L3 message belongs. In a MODIFY REJECT message, Protocol Discriminator takes the


value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a MODIFY REJECT message, the message type is MODIFY REJECT. For details, see Message Type.

Bearer capability


Cause

Indicates the reason why a request to change bearer capability for a call cannot be fulfilled. For details, see Cause.

Reference Standards For details, see 9.3.15 "Modify reject" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Establishment Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Call Clearing Messages at the CC Sublayer DISCONNECT RELEASE RELEASE COMPLETE Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

DISCONNECT Message Function Associated IEs Reference Standards Message Function This message is sent, from the network to the MS/UE or conversely, to indicate that the end-to-end connection has been cleared. Figure 1 shows the main IEs of the message. Figure 1 DISCONNECT message

Associated IEs

Information Element (IE)

Description


Identifies the L3 protocol to which the L3 message belongs. In a DISCONNECT message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a DISCONNECT message, the message type is DISCONNECT. For details, see Message Type.

Cause

Indicates the reason why the end-to-end connection is cleared. For details, see Cause.

Progress indicator


Reference Standards For details, see 9.3.7 "Disconnect" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Clearing Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELEASE Message Function Associated IEs Reference Standards Message Function This message is sent, from the network to the MS/UE or conversely, to indicate that the sender intends to release the transaction identifier and that the receiver should release the transaction identifier after sending a RELEASE COMPLETE message. Figure 1 shows the main IEs of the message. Figure 1 RELEASE message

Associated IEs


Description


Identifies the L3 protocol to which the L3 message belongs. In a RELEASE message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a RELEASE message, the message type is RELEASE. For details, see Message Type.

Cause

Indicates the reason why the transaction identifier is released. For details, see Cause.

Reference Standards For details, see 9.3.18 "Release" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Call Clearing Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELEASE COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent, from the network to the MS/UE or conversely, to indicate that the sender has released the transaction identifier and the receiver should also release the transaction identifier. Figure 1 shows the main IEs of the message. Figure 1 RELEASE COMPLETE message


Description


Identifies the L3 protocol to which the L3 message belongs. In a RELEASE COMPLETE message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator. Distinguishes a few message flows for a


given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Transaction identifier.

Message Type

Indicates the type of the message. For a RELEASE COMPLETE message, the message type is RELEASE COMPLETE. For details, see Message Type.

Cause

Indicates the reason why the transaction identifier is released. For details, see Cause.

Reference Standards For details, see 9.3.19 "Release complete" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Call Clearing Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Supplementary Service Control Messages at the CC Sublayer HOLD FACILITY HOLD ACKNOWLEDGE RETRIEVE RETRIEVE ACKNOWLEDGE Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HOLD Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to request the network to place the existing call on hold. Figure 1 shows the main IEs of the message. Figure 1 HOLD message


Description


Identifies the L3 protocol to which the L3 message belongs. In a HOLD message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator. Distinguishes a few message flows for a given protocol discriminator and a given


Message Type

session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Skip indicator. Indicates the type of the message. For a HOLD message, the message type is HOLD. For details, see Message Type.

Reference Standards For details, see 9.3.10 "Hold" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

FACILITY Message Function Associated IEs Reference Standards Message Function This message is sent, from the network to the MS/UE or conversely, to request or acknowledge a supplementary service. Figure 1 shows the main IEs of the message. Figure 1 FACILITY message


Description


Identifies the L3 protocol to which the L3 message belongs. In a FACILITY message, Protocol Discriminator takes the value B, indicating that the message belongs to the supplementary service (SS) protocol. For details, see Protocol Discriminator. Distinguishes a few message flows for a


given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Skip indicator.

Message Type

Indicates the type of the message. For a FACILITY message, the message type is FACILITY. For details, see Message Type.

Facility


Reference Standards For details, see 9.3.9 "Facility" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HOLD ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent by the network to indicate that the existing call has been placed on hold. Figure 1 shows the main IEs of the message. Figure 1 HOLD ACKNOWLEDGE message


Description


Identifies the L3 protocol to which the L3 message belongs. In a HOLD ACKNOWLEDGE message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator. Distinguishes a few message flows for a


Message Type

given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Skip indicator. Indicates the type of the message. For a HOLD ACKNOWLEDGE message, the message type is HOLD ACKNOWLEDGE. For details, see Message Type.

Reference Standards For details, see 9.3.10 "Hold Acknowledge" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RETRIEVE Message Function Associated IEs Message Function This message is sent by the MS/UE to request the retrieval of a held call. Figure 1 shows the main IEs of the message. Figure 1 RETRIEVE message


Description

Message Type

Indicates the type of the message. For a RETRIEVE message, the message type is RETRIEVE. For details, see Message Type.

Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RETRIEVE ACKNOWLEDGE Message Function Associated IEs Message Function This message is sent by the network to notify the MS/UE that call retrieval has been successfully performed. Figure 1 shows the main IEs of the message. Figure 1 RETRIEVE ACKNOWLEDGE message


Description

Message Type

Indicates the type of the message. For a RETRIEVE ACKNOWLEDGE message, the message type is RETRIEVE ACKNOWLEDGE. For details, see Message Type.

Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential


Message Function Associated IEs Reference Standards Message Function This message is sent, from the network to the MS/UE or conversely, to assign a new transaction identifier for call independent supplementary service control and to request or acknowledge a supplementary service. Figure 1 shows the main IEs of the message. Figure 1 message


Description


Identifies the L3 protocol to which the L3 message belongs. In a message, Protocol Discriminator takes the value 11, indicating that the message belongs to the call independent supplementary service (SS) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a message, the message type is . For details, see Message Type.

Facility


SS version indicator

Indicates the SS protocol version in use. It must be present if the supplementary service operation being invoked is implemented according to the phase 2 or higher protocol version.

Reference Standards For details, see 2.4 "" in 3rd Generation Partnership Project (3GPP) TS24080-740. Parent topic: Description of Supplementary Service Control Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Miscellaneous Messages at the CC Sublayer NOTIFY START DTMF START DTMF ACKNOWLEDGE STOP DTMF STOP DTMF ACKNOWLEDGE Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

NOTIFY Message Function Associated IEs Reference Standards Message Function This message is sent either from the MS/UE or from the network to convey call-related information, such as suspended. Figure 1 shows the main IEs of the message.

Figure 1 NOTIFY message Associated IEs Information Element (IE)

Description


Identifies the L3 protocol to which the L3 message belongs. In a NOTIFY message, Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.


Distinguishes a message flow for a given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. For details, see Transaction identifier. Indicates the type of the message. For a NOTIFY message, the message type is

Message Type

Notification indicator

NOTIFY. For details, see Message Type. Provides information pertaining to a call, such as suspended, resumed, and bearer change.

Reference Standards For details, see 9.3.16 "Notify" in 3rd Generation Partnership Project (3GPP) TS24008840. Parent topic: Description of Miscellaneous Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

START DTMF Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to the network. It conveys the digit the network should reconvert back into a dual tone multiple frequency (DTMF) tone which is then applied towards the remote . Figure 1 shows the main IEs of the message. Figure 1 START DTMF message

Associated IEs Information Element Description (IE) Identifies the L3 protocol to which the L3 message belongs. In a START DTMF message, Protocol Discriminator takes the value 3,

Protocol Discriminator indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a START DTMF message, the message type is START DTMF. For details, see Message Type.

Reference Standards For details, see 9.3.24 "Start DTMF" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Miscellaneous Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

START DTMF ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent by the network to the MS/UE to indicate the successful initiation of the action requested by the START dual tone multiple frequency (DTMF) message (conversion of the digit contained in this message into a DTMF tone). Figure 1 shows the main IEs of the message. Figure 1 START DTMF ACKNOWLEDGE message

Associated IEs Information Element Description

(IE) Identifies the L3 protocol to which the L3 message belongs. In a START DTMF ACKNOWLEDGE message, Protocol Discriminator Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a START DTMF ACKNOWLEDGE message, the message type is START DTMF ACKNOWLEDGE. For details, see Message Type.

Reference Standards For details, see 9.3.25 "Start DTMF Acknowledge" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Miscellaneous Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

STOP DTMF Message Function Associated IEs Reference Standards Message Function This message is sent by the MS/UE to request the network to stop sending the dual tone multiple frequency (DTMF) tone towards the remote . Figure 1 shows the main IEs of the message. Figure 1 STOP DTMF message

Associated IEs Information Element Description (IE) Identifies the L3 protocol to which the L3 message belongs. In a

STOP DTMF message, Protocol Discriminator takes the value 3, Protocol Discriminator indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a STOP DTMF message, the message type is STOP DTMF. For details, see Message Type.

Reference Standards For details, see 9.3.29 "Stop DTMF" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Miscellaneous Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

STOP DTMF ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent by the network to notify the MS/UE that the sending of the dual tone multiple frequency (DTMF) tone has been stopped. Figure 1 shows the main IEs of the message. Figure 1 STOP DTMF ACKNOWLEDGE message

Associated IEs Information Element Description (IE)

Identifies the L3 protocol to which the L3 message belongs. In a STOP DTMF ACKNOWLEDGE message, Protocol Discriminator Protocol Discriminator takes the value 3, indicating that the message belongs to the call controller (CC) protocol. For details, see Protocol Discriminator.



Message Type

Indicates the type of the message. For a STOP DTMF ACKNOWLEDGE message, the message type is STOP DTMF ACKNOWLEDGE. For details, see Message Type.

Reference Standards For details, see 9.3.30 "Stop DTMF acknowledge" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Miscellaneous Messages at the CC Sublayer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Protocol Discriminator Message Type Skip indicator Transaction identifier Priority Level Ciphering Key Sequence Number Location Area Identification Mobile Identity Mobile Station Classmark 1 Mobile Station Classmark 2 Spare Half Octet Authentication parameter RAND Authentication Parameter AUTN (UMTS authentication challenge only) Authentication Response parameter CM service type Identity type Location updating type Reject cause Cause Connected number Facility Low layer compatibility Progress indicator Repeat indicator Bearer capability Called party BCD number

Calling party BCD number Parent topic: Um/Uu Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Protocol Discriminator Description of the IE Reference Standards Description of the IE Information Element (IE) Description Bits 1 to 4 of the first octet of a standard L3 message contain the Protocol Discriminator IE. This IE identifies the L3 protocol to which a standard L3 message belongs. The correspondence between L3 protocols and protocol discriminators is one-to-one. The following are typical values of Protocol Discriminator: 0101: The message belongs to the mobility management (MM) protocol. An international mobile subscriber identity (IMSI) DETACH INDICATION message is considered as an example here. In this example, Protocol Discriminator is 0101. Therefore, mm-layer-message is present in layer-3-information.

0011: The message belongs to the call controller (CC) protocol. A SETUP message is considered as an example here. In this example, Protocol Discriminator is 0011. Therefore, cm-layer-message is present in layer-3information. Protocol Discriminator

1011: The message belongs to the supplementary service (SS) protocol. A FACILITY message is considered as an example here. In this example, Protocol Discriminator is 1011. Therefore, ss-layer-message is present in layer-3information.

1001: The message belongs to the short message service (SMS) protocol. A DATA message is considered as an example here. In this example, Protocol Discriminator is 1001. Therefore, sms-layer-message is present in layer-3information.

Reference Standards For details, see 10.2 "Protocol Discriminator" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Message Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of the message. The following are message types used for mobility management: international mobile subscriber identity (IMSI) DETACH INDICATION LOCATION UPDATING ACCEPT LOCATION UPDATING REJECT LOCATION UPDATING REQUEST AUTHENTICATION REJECT AUTHENTICATION REQUEST AUTHENTICATION RESPONSE AUTHENTICATION FAILURE IDENTITY REQUEST IDENTITY RESPONSE temporary mobile subscriber identifier (TMSI) REALLOCATION COMMAND TMSI REALLOCATION COMPLETE connection management (CM) SERVICE ACCEPT CM SERVICE REJECT CM SERVICE ABORT CM SERVICE REQUEST CM SERVICE PROMPT CM RE-ESTABLISHMENT REQUEST mobility management (MM) NULL MM STATUS MM INFORMATION The following are the message types used for call control and supplementary service control. ALERTING

Message Type

CALL CONFIRMED CALL PROCEEDING CONNECT CONNECT ACKNOWLEDGE EMERGENCY SETUP PROGRESS CC-ESTABLISHMENT CC-ESTABLISHMENT CONFIRMED RECALL START call controller (CC) SETUP MODIFY MODIFY COMPLETE MODIFY REJECT INFORMATION HOLD HOLD ACKNOWLEDGE HOLD REJECT RETRIEVE RETRIEVE ACKNOWLEDGE RETRIEVE REJECT DISCONNECT RELEASE RELEASE COMPLETE CONGESTION CONTROL NOTIFY STATUS STATUS ENQUIRY START dual tone multiple frequency (DTMF) STOP DTMF STOP DTMF ACKNOWLEDGE START DTMF ACKNOWLEDGE START DTMF REJECT FACILITY

An IMSI DETACH INDICATION message is considered as an example here. In this example, mm-msg-type is 1, indicating that the message type is IMSI DETACH INDICATION. Reference Standards For details, see 10.4 "Message Type" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Skip indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the message should be ignored. A message received with skip indicator different from 0000 should be ignored. A message received with skip indicator encoded as 0000 should not be ignored, unless it is ignored for other reasons.

Skip indicator

An international mobile subscriber identity (IMSI) DETACH INDICATION message is considered as an example here. In this example, Skip indicator is 0, indicating that the message will not be ignored. Reference Standards For details, see 10.3.1 "Skip indicator" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Transaction identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Distinguishes a few message flows for a given protocol discriminator and a given session announcement protocol (SAP). Such a message flow is called a transaction. This IE consists of the following fields:


transaction-value: indicates the transaction identifier (TI) value, which can be set to 6 at most. transaction-flag: identifies whether the message sender or receiver has assigned the TI value to this transaction. A message has transaction-flag set to 0 when it belongs to a transaction initiated by its sender, and to 1 otherwise.

A SETUP message is considered as an example here. In this example, transaction-value is 0 indicating that the TI value is 0, and transaction-flag is 0 indicating that the message is sent from the side that originates the TI. Reference Standards For details, see 11.2.3.1.3 "Transaction identifier" in 3rd Generation Partnership Project (3GPP) TS24007-700. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Priority Level Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides information defining the priority level requested or applied. The Priority Level IE is optional and may be included in CM_SERVICE_REQUEST, CALL_PROCEEDING, and SETUP messages. Calls with higher priority are set up more quickly. This IE takes the following values:

Priority Level

0: 1: 2: 3: 4: 5: 6: 7:

no priority applied call priority level 4 call priority level 3 call priority level 2 call priority level 1 call priority level 0 call priority level B call priority level A

A CM_SERVICE_REQUEST is considered as an example here. In this example, Priority Level is 1, indicating that call priority level 4 is applied.

Reference Standards For details, see 10.5.1.11 "Priority Level" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Ciphering Key Sequence Number Description of the IE Reference Standards Description of the IE Information Element (IE) Description


Makes it possible for the network to identify the ciphering key, which is stored in the MS/UE, without invoking the authentication procedure. In a location update, the access side es Ciphering Key Sequence Number to the network side. By using Ciphering Key Sequence Number, the network side identifies the ciphering key Kc (in GSM authentication challenge) or ciphering key ciphering key (CK) and integrity key IK (in UMTS authentication challenge) without invoking the authentication procedure. In the GSM network, if the Ciphering Key Sequence Number received from the MS is the same as that held by the network side, authentication challenge is byed.

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, the Ciphering Key Sequence Number stored in the MS/UE is 7.

An AUTHENTICATION REQUEST message is considered as an example here. In this example, the Ciphering Key Sequence Number allocated by the network is 6. Reference Standards For details, see 10.5.1.2 "Ciphering Key Sequence Number" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


Location Area Identification Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides unambiguous identification of location areas where the MS/UE is staying. This IE is five octets long and coded in the format: MCC+MNC+LAC.


A LOCATION UPDATING ACCEPT message is considered as an example here. In this example, location-area-identity (equivalent of Location Area Identification), which is stored in the subscriber identity module (SIM)/ service identity module (USIM), is 46073f0001. Reference Standards For details, see 10.5.1.3 "Location Area Identification" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Mobile Identity Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides one of the following MS/UE identity information: International mobile Subscriber Identity (IMSI) Temporary Mobile Subscriber Identity (TMSI or PTMSI) International Mobile Equipment Identity (IMEI) International Mobile Equipment Identity Together with the Software Version Number (IMEISV) Temporary Mobile Group Identity (TMGI) Associated Multimedia Broadcast Multicast Service (MBMS) Session Identity

Mobile Identity

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, the Mobile Identity IE is coded as follows: type-of-identity is IMSI, indicating that IMSI is selected to identify the MS/UE. odd-or-even-ind is 1, indicating that the selected mobile identity type consists of an odd number of digits. If there are an even number of digits, odd-or-even-ind should be set to 0. imsi is 460880001000111. Reference Standards

For details, see 10.5.1.4 "Mobile Identity" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Mobile Station Classmark 1 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the network with information concerning aspects of high priority of the MS/UE. This IE affects the manner in which the network handles the operation of the MS/UE. It consists of the following fields: rf-power-capability: indicates the radio frequency (RF) power capability of the frequency band used. It is dimensioned into five classes. a51-alrorithm-indicator: indicates whether the MS/UE s encryption algorithm A5/1. The MS/UE should set this indicator to 0 if A5/1 algorithm is ed, and to 1 otherwise. early-classmark-send: indicates whether "Controlled Early Classmark Sending" option is implemented in the MS/UE. The MS/UE should set this indicator to 1 if "Controlled Early Classmark Sending" option is ed, and to 0 otherwise. revision-level-indicator: indicates the protocol version ed by the MS/UE. This IE takes a few values, for example, value 0 for GSM phase 1, and value 2 for GSM phase 2 mobile stations.


A LOCATION UPDATING REQUEST message is considered as an example here. In this example, rf-power-capability is 3 indicating that RF power capability class 4 is applied, a51-alrorithm-indicator is 0 indicating that the MS/UE s the A5/1 algorithm, and earlyclassmark-send is 1 indicating that "Controlled Early Classmark Sending" option is implemented in the MS/UE. Reference Standards

For details, see 10.5.1.5 "Mobile Station Classmark 1" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Mobile Station Classmark 2 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the network with information concerning aspects of both high and low priority of the MS/UE. This IE is conveyed in a connection management (CM) SERVICE REQUEST or UE-originated LOCATION UPDATING REQUEST message. It contains a few fields, including: voice-group-call-service: indicates MS/UE for Voice Group Call Service (VGCS) notification reception. voice-broadcast-service: indicates MS/UE for Voice Broadcast Service (VBS) notification reception. short-message-capability: indicates MS/UE for mobile terminated point-to-point short message service (SMS). supplement-service-screen: indicates MS/UE for supplementary service screening. cm-service-prompt: indicates MS/UE for CM Service Prompt (also called CCBS). universal-character-set-2: indicates MS/UE for Universal Character Set 2 (UCS2). location-service-capability: indicates MS/UE for location request notification. classmark3-indicator: indicates MS/UE for options indicated in Mobile Station Classmark 3.


A CM SERVICE REQUEST message is considered as an example here. In this example, voice-group-call-service is 0 indicating that no VGCS capability or no notifications are wanted, and voice-broadcast-service is 0 indicating that no VBS capability or no notifications are wanted. Reference Standards For details, see 10.5.1.6 "Mobile Station Classmark 2" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Spare Half Octet Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Reserved for future use. This IE is half-octet long and filled with spare bits set to zero.

Spare Half Octet An AUTHENTICATION REQUEST message is considered as an example here. In this example, spare is 0, indicating that a spare bit equal to zero is added. Reference Standards For details, see 10.5.1.8 "Spare Half Octet" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Authentication parameter RAND Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides the MS/UE with a non-predictable number to be used to calculate the authentication response signature SRES and the ciphering key Kc (for GSM authentication challenge), or the response RES and both the ciphering key CK and integrity key IK (for UMTS authentication challenge). The non-predictable number is called RAND. Authentication parameter random number (RAND)

An AUTHENTICATION REQUEST message is considered as an example here. In this example, the RAND value (indicated by auth-rand) is 1F 8E ED E0 C8 FC 99 F6 B3 32 AE CF 48 DD 71 E0. Reference Standards For details, see 10.5.3.1 "Authentication parameter RAND" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Authentication Parameter AUTN (UMTS authentication challenge only) Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides the UE with a means of authenticating the network. This IE is sent from the network to the UE only when Universal Mobile Telecommunications System (UMTS) authentication challenge is used. Authentication Parameter authentication token (AUTN) An AUTHENTICATION REQUEST message is considered as an example here. In this example, the AUTN value (indicated by autn) is 5E FB DE ED 57 43 72 4C AF 9C AE 5E 8B F3 25 7B. Reference Standards For details, see 10.5.3.1.1 "Authentication Parameter AUTN (UMTS authentication challenge only)" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Authentication Response parameter Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the network with the authentication response calculated in the subscriber identity module (SIM)/ service identity module (USIM). In GSM authentication challenge, SRES (response calculated in the SIM/USIM) is 4 bytes in length and is placed in the Authentication Response Parameter IE. In Universal Mobile Telecommunications System (UMTS) authentication challenge, RES (response calculated in the USIM) may be up to 16 octets in length. The Authentication Response Parameter IE consists of the following fields: auth-sres: conveys SRES or four most significant octets of RES. auth-res-ext: conveys the remaining part of RES. This field is included if RES (UMTS only) is longer than 4 octets and therefore does not fit in the auth-sres field.

Authentication Response parameter

An AUTHENTICATION RESPONSE message is considered as an example here. In this example, auth-sres is FB 19 FC 2C, and authres-ext is EF 9B 0F 05. So, the complete RES is FB 19 FC 2C EF 9B 0F 05. Reference Standards For details, see 10.5.3.2 "Authentication Response parameter" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CM service type Description of the IE Reference Standards Description of the IE Information Element Description (IE) Specifies which service is requested from the network. This IE takes the following values:

connection management (CM) service type

1: mobile originating call establishment or packet mode connection establishment 2: emergency call establishment 4: short message service 8: supplementary service activation 9: voice group call establishment 10: voice broadcast call establishment 11: location services

A CM SERVICE REQUEST message is considered as an example here. In this example, cm-service-type is 1, indicating that the mobile originating call establishment or packet mode connection establishment is being requested by the MS/UE. Reference Standards For details, see 10.5.3.3 "CM service type" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Identity type Description of the IE Reference Standards Description of the IE Information Element (IE) Description Specifies which identity is requested from the MS/UE. This IE takes the following values:

Identity type

1: international mobile subscriber identity (IMSI) 2: international mobile equipment identity (IMEI) 3: international mobile station equipment identity and software version (IMEISV) 4: temporary mobile subscriber identifier (TMSI)

An IDENTITY REQUEST message is considered as an example here. In this example, mobile-identity-type is 2, indicating that IMEI is being requested from the MS/UE. Reference Standards For details, see 10.5.3.4 "Identity type" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Location updating type Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates whether a generic updating, a periodic updating, or an international mobile subscriber identity (IMSI) attach is wanted. This IE may also indicate that a follow-on request has been received from the connection management (CM) entity of the MS/UE. It consists of the following fields: location-update-type: indicates the type of location update. 0: generic location update 9: periodic location update 2: IMSI attach follow-on-request-bit: indicates whether a follow-on request is pending. The presence of follow-on indicator implies that the current service is followed by CM services and CM services may be established on existing radio resource (RR) and mobility management (MM) connections.

Location updating type

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, location-update-type is 0 indicating that generic location update is wanted, and follow-on-request-bit is 0 indicating that no follow-on request is pending. Reference Standards For details, see 10.5.3.5 "Location updating type" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


Reject cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason why a request from the MS/UE is rejected by the network. This IE takes the following values:

Reject cause

2: international mobile subscriber identity (IMSI) unknown in HLR 3: Illegal MS 4: IMSI unknown in VLR 5: international mobile equipment identity (IMEI) not accepted 6: Illegal mobile equipment (ME) 11: public land mobile network (PLMN) not allowed 12: Location Area not allowed 13: Roaming not allowed in this location area 15: No Suitable Cells In Location Area 17: Network failure 20: mobile access code (MAC) failure 21: Synch failure 22: Congestion 23: GSM authentication unacceptable

A LOCATION UPDATING REJECT message is considered as an example here. In this example, reject-cause is 11, indicating that the location update request is denied because the MS/UE is not authorized to enter the PLMN. Reference Standards For details, see 10.5.3.6 "Reject cause" in 3rd Generation Partnership Project (3GPP)

TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Describes the reason for generating certain messages, to provide diagnostic information in the event of procedural errors and to indicate the location of the cause originator.

Cause

A DISCONNECT message is considered as an example here. In this example, cause-value is 44, indicating that the call is released because the requested circuit/channel is not available. Reference Standards For details, see 10.5.4.11 "Cause" in 3rd Generation Partnership Project (3GPP) TS24008830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Connected number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the connected party of a call. This IE is sent from the network to the calling MS/UE. It consists of the following fields: number-plan-identification: indicates the numbering plan in use. 0: Unknown 1: integrated services digital network (ISDN)/telephony numbering plan 2: generic numbering plan 3: data numbering plan 4: telex numbering plan 5: Maritime mobile numbering plan 6: Land mobile numbering plan 7: ISDN/mobile numbering plan

Connected number

type-of-number: indicates the type of connected number. For example, subscriber number, unknown number, national number, and international number. screening-indicator: indicates whether the connected number should be hidden from the calling party. presentation-indicator: indicates whether the connected number should be presented to the calling party. This field is set to 0 if presentation is allowed, and to 1 otherwise. number: indicates the directory number for which the call is destined.

A CONNECT message is considered as an example here. In this example, number-plan-identification is 1 indicating that the ISDN/telephony numbering plan is applied, type-of-number is 2 indicating that the connected number is an national number, screening-indicator is 0 indicating that the connected number is not screened, and presentationindicator is 0 indicating that presentation of the connected number is allowed. Reference Standards For details, see 10.5.4.13 "Connected number" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Facility Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Conveys supplementary service related information. This IE is included only when a supplementary service, identified by the operation-code field within the Facility IE, is required. The operation-code field takes the following values:

Facility

10: SS 11: eraseSS 12: activateSS 13: deactivateSS 14: interrogateSS 16: notifySS 17: 18: get 19: processUnstructuredSS-Data 38: forwardCheckSS-Indication 59: processUnstructuredSS-Request 60: unstructuredSS-Request 61: unstructuredSS-Notify 77: eraseCCEntry 110: activatePSS 115: lcs-MOLR 116: lcs-LocationNotification 117: callDeflection 118: Service 119: accessCCEntry 120: forwardCUG-Info 121: splitMPTY 122: retrieveMPTY 123: holdMPTY

124: buildMPTY 125: forwardChargeAdvice 126: explicitCT

A FACILITY message is considered as an example here. In this example, operation-code is 61, indicating that invocation or operation of unstructured supplementary service data (USSD) supplementary service is in progress. Reference Standards For details, see 10.5.4.15 "Facility" in 3rd Generation Partnership Project (3GPP) TS24008-830 and 4.2.2 "Operations description" in 3GPP TS24080-740. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Low layer compatibility Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides a means for the addressed entity to perform compatibility check.

Low layer compatibility

A SETUP message is considered as an example here. In this example, lower-layer-compatibility-1 is 00 01, indicating that the call originating entity has sent compatibility check method 00 01 to the addressed entity.

Reference Standards For details, see 10.5.4.18 "Low layer compatibility" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Progress indicator Description of the IE Reference Standards Description of the IE Information Element Description (IE) Describes an event that has occurred during the life of a call.

Progress indicator A DISCONNECT message is considered as an example here. In this example, Progress description is 1, indicating that the call is not end-to-end public land mobile network (PLMN)/integrated services digital network (ISDN) and further call progress information may be available in-band. Reference Standards For details, see 10.5.4.21 "Progress indicator" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Repeat indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates how the associated repeated information elements should be interpreted when included in a message. The Repeat indicator IE is included immediately before the first occurrence of the associated information element that will be repeated in a message.

Repeat indicator

A SETUP message is considered as an example here. In this example, bc-repeat-indicator is 1, indicating that a circular for successive circuit selection. Reference Standards For details, see 10.5.4.22 "Repeat indicator" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Bearer capability Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Describes a bearer service. The purpose of this IE is to let access side and network side notify each other of the locally ed codecs so that both sides can reach an agreement on the codec that will be used. This IE contains a few fields, including: information-transfer-capability: indicates the type of information that can be transferred during the lifetime of the call. This field has a few values, for example, 010 (3.1 kHz audio, ex PLMN), 001 (unrestricted digital information), 011 (facsimile group 3), and 000 (speech). default-speech-ed-ind: indicates the speech version ed.

Bearer capability

A SETUP message from the calling MS/UE is considered as an example here. In this example, information-transfer-capability is 0 indicating that the calling MS/UE requests speech bearer capability (BC), and default-speeched-ind is 1 indicating that the access side s full rate speech version 1. Reference Standards For details, see 10.5.4.5 "Bearer capability" in 3rd Generation Partnership Project (3GPP) TS24008-830.

Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Called party BCD number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the called party. This IE contains the following fields, including: number-plan-identification: indicates the numbering plan in use. 0: Unknown 1: integrated services digital network (ISDN)/telephony numbering plan 2: generic numbering plan 3: data numbering plan 4: telex numbering plan 5: Maritime mobile numbering plan 6: Land mobile numbering plan 7: ISDN/mobile numbering plan

Called party binarycoded data (BCD) number

type-of-number: indicates the type of called number, for example, subscriber number, unknown number, national number, and international number. number: indicates the called number.

A SETUP message from the calling MS/UE is considered as an example here. In this example, number-plan-identification is 1 indicating that the ISDN/telephony numbering plan is applied, type-of-number is 2 indicating that the called number is a national number, and called number is 13107559917. Reference Standards

For details, see 10.5.4.7 "Called party BCD number" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling party BCD number Description of the IE Reference Standards Description of the IE Information Element Description (IE) Identifies the origin of a call. This IE contains the following fields, including: number-plan-identification: indicates the numbering plan in use.

Calling party binarycoded data (BCD) number

0: Unknown 1: integrated services digital network (ISDN)/telephony numbering plan 2: generic numbering plan 3: data numbering plan 4: telex numbering plan 5: Maritime mobile numbering plan 6: Land mobile numbering plan 7: ISDN/mobile numbering plan type-of-number: indicates the type of calling number, for example, subscriber number, unknown number, national number, and international number. number: indicates the calling number.

A SETUP message from the called MS/UE is considered as an example here. In this example, number-plan-identification is 1 indicating that the ISDN/telephony numbering plan is applied, typeof-number is 2 indicating that the calling number is an national number, and calling number is 13620016111. Reference Standards For details, see 10.5.4.9 "Calling party BCD number" in 3rd Generation Partnership Project (3GPP) TS24008-830.


A Interface Protocol Description of the A Interface Protocol Description of the Common Part of Messages Description of Assignment Messages Description of Cipher Mode Control Messages Description of Paging Messages Description of Handover Management Messages Description of Resource Release Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the A Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC server/VLR communicates with the base station subsystem (BSS) through BSS Application Part (BSSAP). Figure 1 shows the application of the A interface protocol BSSAP. Figure 1 Application of the A interface protocol

Protocol Stack Figure 2 shows the protocol stack for time division multiplexing (TDM) transport over the A interface. Figure 3 shows the protocol stack for IP transport over the A interface. Figure 2 Protocol stack for TDM transport over the A interface

Figure 3 Protocol stack for IP transport over the A interface

NOTE: When interfacing the IP-capable BSC, the A interface s a few adaptation protocols, including MTP3- Adaptation Layer (M3UA) and Signaling Connection and Control Part Adaptation Layer (SUA) protocols. Figure 3 takes M3UA as an example. BSSAP is split into two sub application parts: BSS Management Application Part (BSSMAP) and Direct Transfer Application Part (DTAP). DTAP is used to realize direct transfer of call control and mobility management messages between the MSC and the MS, with no interpretation of layer 3 information at the BSS. BSSMAP s all of the MSC-BSC procedures that require interpretation and processing of information related to single calls, and resource management. BSSMAP messages are not distributed to the MS. As shown in Figure 4, BSSAP messages are encapsulated into payload of Signaling Connection Control Part (SC) messages. Figure 4 Encapsulation of BSSAP messages

Message List Table 1 List of common A interface messages Message ASSIGNMENT REQUEST ASSIGNMENT COMPLETE ASSIGNMENT

Direction Function This message is sent from the MSC server to the BSS MSC via the relevant SC connection in order to request the server -> BSS to assign radio resource(s), the attributes of which BSC are defined within the message. BSC -> This message is sent from the BSS to the MSC server MSC and indicates that the requested assignment has been server completed correctly. This message is sent from the BSS to the MSC server BSC -> via the relevant SC connection. It indicates that there MSC

FAILURE

server

CIPHER MODE COMMAND

MSC server -> BSC

CIPHER MODE COMPLETE

BSC -> MSC server

PAGING

MSC server -> BSC

HANDOVER REQUEST

MSC server -> BSC

HANDOVER REQUIRED

BSC -> MSC server

HANDOVER REQUEST ACKNOWLEDGE

BSC -> MSC server

HANDOVER COMMAND

MSC server -> BSC

HANDOVER COMPLETE

BSC -> MSC server

BSC -> HANDOVER DETECT MSC server

CLEAR COMMAND

MSC server -> BSC

has been a failure in the assignment process at the BSS and that the assignment procedure has been aborted. This message is sent from the MSC server to the BSS via the relevant SC connection associated with that MS transaction. It updates the encryption parameters for the concerned MS. This message is sent from the BSS to the MSC server via the relevant SC connection. It indicates that a successful cipher synchronization has been achieved across the radio interface. This message is sent from the MSC server to the BSS and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. This message is sent from the MSC server to the target BSS via the relevant SC connection to indicate that the MS will be handed over to that BSS. This message is sent from the source BSS to the MSC server to indicate that a handover is required for a given MS that already has dedicated radio resource(s) assigned. This message is sent from the target BSS to the MSC server to indicate that the handover request can be ed by the target BSS, and also to convey information about radio channel(s) the MS should be directed to. This message is sent from the MSC server to the source BSS via the relevant SC connection and contains the target channel to which the MS should return. This message is sent from the target BSS to the MSC server via the relevant SC connection. It indicates that the correct MS has successfully accessed the target cell. This message is sent from the target BSS to the MSC server via the relevant SC connection. It indicates that the correct MS has successfully accessed the target cell. This message is sent from the MSC server to the BSS to instruct the BSS to release the associated dedicated resource(s). After reception of this message, the BSS releases the radio interface and marks any assigned terrestrial resources as idle.

BSC -> CLEAR COMPLETE MSC server MSC REROUTE COMMAND server -> BSC REROUTE COMPLETE

This message is sent from the BSS to the MSC server to inform the MSC that the associated dedicated resource(s) has been successfully cleared. This message is sent from the MSC server to the BSS to instruct the BSS to select another core network. This message applies only to the 2G MOCN flow. This message is sent from the MSC server to the BSS to MSC notify the BSS that the core network selection is server -> complete. This message applies only to the 2G MOCN BSC flow.

Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 IEs carried in the common part of messages Information Element (IE)

Description Provides a brief description of the message sender and receiver.

Header

sender-mid: identifies the calling control unit (CCU) module on the sender side. sender-pid: identifies the internal processing module on the sender side. receiver-mid: identifies the CCU module on the receiver side. receiver-pid: identifies the internal processing module on the receiver side.

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, the message is originated from CCU module 23 via the Signaling Connection Control Part (SC) module and interpreted by CCU module 23 before reaching the AIM module. Provides SC connection information and signaling point code (SPC) of the BSC. sc-connect-id: identifies the SC connection in use. spc-of-14-bit: conveys the 14-bit SPC of the BSC.

SC information

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, sc-connect-id is 130 indicating that SC connection 130 is used to transport the message, and spc-of-

14-bit is 0x2771 indicating that the BSC is assigned the SPC 0x2771. Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Assignment Messages ASSIGNMENT REQUEST ASSIGNMENT COMPLETE ASSIGNMENT FAILURE Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASSIGNMENT REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the base station subsystem (BSS) via the relevant Signaling Connection Control Part (SC) connection in order to request the BSS to assign radio resource(s), the attributes of which are defined within the message. Figure 1 shows the main IEs of the message. Figure 1 ASSIGNMENT REQUEST message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In an ASSIGNMENT REQUEST message, Message Type takes the fixed value 1. For details, see Message Type.

Channel Type

Contains all of the information that the BSS requires to determine the required radio resource(s). This IE has a minimum length of

5 octets and a maximum length of 13 octets. For details, see Channel Type.

Layer 3 Header Information

Provides the BSS with information that must be included in the header of layer 3 messages over the radio interface. For details, see Layer 3 Header Information.

Priority

Indicates the priority of the request. This IE is three octets long. For details, see Priority.

Circuit Identity Code

Defines the terrestrial channel over which the call will . For details, see Circuit Identity Code.

Reference Standards For details, see 3.2.1.1 "ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Assignment Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASSIGNMENT COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent from the base station subsystem (BSS) to the MSC and indicates that the requested assignment has been completed correctly. Figure 1 shows the main IEs of the message. Figure 1 ASSIGNMENT COMPLETE message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In an ASSIGNMENT COMPLETE message, Message Type takes the fixed value 2. For details, see Message Type.

radio resource (RR) Cause

Indicates the reason ed from the radio interface to the MSC transparently. For details, see RR Cause.


Defines the terrestrial channel over which the call will . For details, see Circuit Identity Code. Indicates the speech version being used by

Speech Version

the BSS. For details, see Speech Version.

Reference Standards For details, see 3.2.1.2 "ASSIGNMENT COMPLETE" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Assignment Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASSIGNMENT FAILURE Message Function Associated IEs Reference Standards Message Function This message is sent from the base station subsystem (BSS) to the MSC via the relevant Signaling Connection Control Part (SC) connection. It indicates that there has been a failure in the assignment process at the BSS and that the assignment procedure has been aborted. Figure 1 shows the main IEs of the message. Figure 1 ASSIGNMENT FAILURE message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In an ASSIGNMENT FAILURE Message, Message Type takes the fixed value 3. For details, see Message Type.

Cause

Indicates the reason why an assignment failure was encountered. For details, see Cause.

radio resource (RR) Cause

Indicates the reason ed from the radio interface to the MSC transparently. For details, see RR Cause.

Reference Standards For details, see 3.2.1.3 "ASSIGNMENT FAILURE" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Assignment Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Cipher Mode Control Messages CIPHER MODE COMMAND CIPHER MODE COMPLETE Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CIPHER MODE COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the base station subsystem (BSS) via the relevant Signaling Connection Control Part (SC) connection associated with that MS transaction. It updates the encryption parameters for the concerned MS. Figure 1 shows the main IEs of the message. Figure 1 CIPHER MODE COMMAND message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a CIPHER MODE COMMAND message, Message Type takes the fixed value 83. For details, see Message Type.


Provides the BSS with information that must be included in the header of layer 3 messages over the radio interface. For details, see Layer 3 Header Information. Contains the data encryption information used to control any encryption equipment at

Encryption Information

the BSS. For details, see Encryption Information.

Reference Standards For details, see 3.2.1.30 "CIPHER MODE COMMAND" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Cipher Mode Control Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CIPHER MODE COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent from the base station subsystem (BSS) to the MSC via the relevant Signaling Connection Control Part (SC) connection. It indicates that a successful cipher synchronization has been achieved across the radio interface. Figure 1 shows the main IEs of the message. Figure 1 CIPHER MODE COMPLETE message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a CIPHER MODE COMPLETE message, Message Type takes the fixed value 85. For details, see Message Type.

Chosen Encryption Algorithm

Indicates the encryption algorithm being used by the BSS. For details, see Chosen Encryption Algorithm.

Reference Standards For details, see 3.2.1.31 "CIPHER MODE COMPLETE" in 3rd Generation Partnership Project (3GPP) TS48008-840.

Parent topic: Description of Cipher Mode Control Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Paging Messages PAGING PAGING RESPONSE Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PAGING Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the base station subsystem (BSS) and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. Figure 1 shows the main IEs of the message.

Figure 1 PAGING message Associated IEs Information Element (IE)

Message Type

Description Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a PAGING message, Message Type takes the fixed value 82.

For details, see Message Type. international mobile subscriber identity (IMSI)

Provides IMSI of the called party. For details, see IMSI.

temporary mobile subscriber identifier (TMSI)

Provides TMSI of the called party. For details, see TMSI.

Cell Identifier List

Identifies the cells on the called side. For details, see Cell Identifier List.

enhanced multi-level precedence and preemption (eMLPP) Priority

Contains the eMLPP priority of the call. For details, see eMLPP Priority.

Reference Standards For details, see 3.2.1.19 "PAGING" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Paging Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PAGING RESPONSE Message Function Associated IEs Reference Standards Message Function This message is sent from the base station subsystem (BSS) to the MSC server as a response to the PAGING message. Figure 1 shows the PAGING RESPONSE message. Figure 1 PAGING RESPONSE message


Description


Identifies the L3 protocol to which the L3 message belongs. For details, see Protocol Discriminator.

Skip Indicator


Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a PAGING RESPONSE message, Message Type takes the fixed value 39. For details, see Message Type.



Spare Half Octet



Includes classmark2 corresponding to the frequency band in use. For details, see Classmark Information Type 2.

Mobile Identity

Provides identity information of the MS. For details, see Mobile Identity.

Reference Standards For details, see section 9.1.25 "Paging response" in 3GPP TS44018-840. Parent topic: Description of Paging Messages

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Handover Management Messages HANDOVER REQUEST HANDOVER REQUIRED HANDOVER REQUEST ACKNOWLEDGE HANDOVER COMMAND HANDOVER COMPLETE HANDOVER DETECT Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the target base station subsystem (BSS) via the relevant Signaling Connection Control Part (SC) connection to indicate that the MS will be handed over to that BSS. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER REQUEST message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a HANDOVER REQUEST message, Message Type takes the fixed value 16. For details, see Message Type.

Channel Type

Provides information such as channel rate, channel type, and permitted speech version. For details, see Channel Type.


Contains the data encryption information used to control any encryption equipment at the BSS. The encryption information includes the permitted A5 algorithm(s). For details, see Encryption Information.

Classmark Information 1 or Classmark Information 2

Indicates general capability of the MS. For details about Classmark Information Type 1, see Classmark Information Type 1. For details about Classmark Information Type 2, see Classmark Information Type 2.

Cell Identifier (Serving)

Identifies the source cell. For details, see Cell Identifier.

Priority

Indicates subscriber priority. For details, see Priority.


Identifies a circuit between SPCs. For details, see Circuit Identity Code.

Cell Identifier (Target)

Identifies the target cell. For details, see Cell Identifier.

Cause

Indicates the reason for a handover to have occurred. For details, see Cause.

Speech Version (Used)

Indicates the speech version being used by the BSS. For details, see Speech Version.

Chosen Encryption Algorithm (Serving)

Indicates the encryption algorithm being used by the BSS. For details, see Chosen Encryption Algorithm.

Reference Standards For details, see 3.2.1.8 "HANDOVER REQUEST" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER REQUIRED Message Function Associated IEs Reference Standards Message Function This message is sent from the source base station subsystem (BSS) to the MSC to indicate that a handover is required for a given MS that already has dedicated radio resource(s) assigned. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER REQUIRED message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a HANDOVER REQUIRED message, Message Type takes the fixed value 17. For details, see Message Type.

Cause

Indicates the reason for a handover to have occurred. For details, see Cause. Identifies a list of preferred target cells.

Cell Identifier List (Preferred)

For details, see Cell Identifier List. Current Channel Type 1

Contains a description of the channel allocated to the MS. For details, see Current Channel Type 1.

Speech Version (Used)

Indicates the speech version being used by the BSS. This IE is included only when the channel is used for speech service. For details, see Speech Version.

Reference Standards For details, see 3.2.1.9 "HANDOVER REQUIRED" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER REQUEST ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent from the target base station subsystem (BSS) to the MSC to indicate that the handover request can be ed by the target BSS, and also to convey information about radio channel(s) the MS should be directed to. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER REQUEST ACKNOWLEDGE message


Description

Message Type

Identifies the message being sent. It is a single-octet IE and mandatory in all messages. In a HANDOVER REQUEST ACKNOWLEDGE message, Message Type

takes the fixed value 18. For details, see Message Type. Layer 3 Information

Provides information about the channel to which the MS should retune. For details, see Layer 3 Information.

Chosen Channel

Contains a description of the channel that the target BSS allocated to the MS. For details, see Chosen Channel.


Indicates the encryption algorithm being used by the target BSS. For details, see Chosen Encryption Algorithm.

Reference Standards For details, see 3.2.1.10 "HANDOVER REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the source base station subsystem (BSS) via the relevant Signaling Connection Control Part (SC) connection and contains the target channel to which the MS should retune. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER COMMAND message


Description

Message Type

Indicates the type of message. For a HANDOVER COMMAND message, the message type is bssmap-Handover-Command. For details, see Message Type.

Layer 3 Information

Provides radio channel information. For details, see Layer 3 Information.

Cell Identifier

Identifies a cell. For details, see Cell Identifier.

Reference Standards For details, see 3.2.1.11 "HANDOVER COMMAND" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent from the target base station subsystem (BSS) to the MSC via the relevant Signaling Connection Control Part (SC) connection. It indicates that the correct MS has successfully accessed the target cell. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER COMPLETE message


Description

Message Type

Indicates the type of message. For a HANDOVER COMPLETE message, the message type is bssmap-Handover-Complete. For details, see Message Type.

Radio Resource (RR) Cause

Indicates the reason why a HANDOVER COMPLETE message was sent. Generally, sending of a HANDOVER COMPLETE message is a normal event and does not result from errors.

For details, see RR Cause. Reference Standards For details, see 3.2.1.12 "HANDOVER COMPLETE" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HANDOVER DETECT Message Function Associated IEs Reference Standards Message Function This message is sent from the target base station subsystem (BSS) to the MSC via the relevant Signaling Connection Control Part (SC) connection. It indicates that the correct MS has successfully accessed the target cell. Figure 1 shows the main IEs of the message. Figure 1 HANDOVER DETECT message


Description

Message Type

Indicates the type of message. For a HANDOVER DETECT message, the message type is bssmap-Handover-Detect. For details, see Message Type.

Reference Standards For details, see 3.2.1.40 "HANDOVER DETECT" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Handover Management Messages


Description of Resource Release Messages CLEAR COMMAND CLEAR COMPLETE Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CLEAR COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the base station subsystem (BSS) to instruct the BSS to release the associated dedicated resource(s). After reception of this message, the BSS releases the radio interface and marks any assigned terrestrial resources as idle. Figure 1 shows the main IEs of the message. Figure 1 CLEAR COMMAND message


Description

Message Type

Indicates the type of message. For a CLEAR COMMAND message, the message type is bssmap-Clear-Command.


Provides the BSS with information that must be included in the header of layer 3 messages over the radio interface. For details, see Layer 3 Header Information.

Cause

Indicates the reason why resources are released. Generally, resource release is initiated for call control purposes. For details, see Cause.

CSFB Indication

Indicates that the radio connection is established in a circuit switched fallback (CSFB) procedure. For details, see CSFB Indication.

Reference Standards For details, see 3.2.1.21 "CLEAR COMMAND" in 3rd Generation Partnership Project (3GPP) TS48008-a60. Parent topic: Description of Resource Release Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CLEAR COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent from the base station subsystem (BSS) to the MSC to inform the MSC that the associated dedicated resource(s) has been successfully cleared. Figure 1 shows the main IEs of the message. Figure 1 CLEAR COMPLETE message


Description

Message Type

Indicates the type of message. For a CLEAR COMPLETE message, the message type is bssmap-Clear-Complete.

Reference Standards For details, see 3.2.1.22 "CLEAR COMPLETE" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Resource Release Messages


Description of Associated IEs Message Type Encryption Information Channel Type Cell Identifier Priority Classmark Information Type 2 Circuit Identity Code RR Cause Layer 3 Information Cell Identifier List Classmark Information Type 1 Chosen Channel Chosen Encryption Algorithm Current Channel Type 1 Cause Speech Version eMLPP Priority IMSI TMSI Layer 3 Header Information CSFB Indication Redirect Attempt Flag Parent topic: A Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Identifies the message being sent. The following are typical values of this IE:

Message Type

1: ASSIGNMENT REQUEST 2: ASSIGNMENT COMPLETE 3: ASSIGNMENT FAILUR 4: CHANNEL MODIFY REQUEST 16: HANDOVER REQUEST 17: HANDOVER REQUIRED 18: HANDOVER REQUEST ACKNOWLEDGE 19: HANDOVER COMMAND 20: HANDOVER COMPLETE 21: HANDOVER SUCCEEDED 22: HANDOVER FAILURE 23: HANDOVER PERFORMED 27: HANDOVER DETECT 32: CLEAR COMMAND 33: CLEAR COMPLETE 82: PAGING 83: CIPHER MODE COMMAND 85: CIPHER MODE COMPLETE

An ASSIGNMENT REQUEST message is considered as an example here. In this example, bssmap-message-type is 1, indicating that the message being sent is ASSIGNMENT REQUEST. Reference Standards

For details, see 3.2.2.1 "Message Type" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Encryption Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains the data encryption information used to control any encryption equipment at the base station subsystem (BSS). This IE contains a few fields, including: permitted-algorithms: indicates whether encryption is applied, and if encryption is applied, the A5 encryption algorithm(s) that will be used. This field occupies eight bits. The meaning of each bit is as follows:


Bit Bit Bit Bit Bit Bit Bit Bit

0: 1: 2: 3: 4: 5: 6: 7:

no encryption. GSM A5/1 algorithm GSM A5/2 algorithm GSM A5/3 algorithm GSM A5/4 algorithm GSM A5/5 algorithm GSM A5/6 algorithm GSM A5/7 algorithm

Bit 0 is encoded as 1 to indicate that encryption will be applied, and as 0 to indicate otherwise. Among bits 1-6, a bit encoded as 1 indicates that the BSS may use the option represented by that bit; a bit encoded as 0 indicates that the BSS shall not use the option represented by that bit. key: identifies the ciphering key Kc. This field must be present if at least one of the A5 encryption algorithms is permitted.

A CIPHER MODE COMMAND message is considered

as an example here. In this example, permittedalgorithms is FF indicating that the BSS may select the GSM A5/1 algorithm, and the Kc sent to the BSS is B2 CA 7C 5B 95 C9 89 60. Reference Standards For details, see 3.2.2.10 "Encryption Information" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Channel Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains all of the information that the base station subsystem (BSS) requires to determine the required radio resource(s). This IE has a minimum length of 5 octets and a maximum length of 13 octets. It consists of the following fields:

Channel Type

bsc-swithc: reserved for future use. sp-data: indicates whether the channel is used for speech or data service. The sp-data field is encoded as 1 to indicate speech service, and as 2 to indicate data service. rate: indicates channel rate. permitted-speech-version-identifier-value-1: indicates the permitted speech version.

An ASSIGNMENT REQUEST message is considered as an example here. In this example, sp-data is 1 indicating that a speech channel is required, rate is 8 indicating that the required channel rate is full rate traffic channel (TCH) channel Bm (ch-tyep-rate-bm), and permitted-speechversion-identifier-value-1 is 1 indicating that the permitted speech version is GSM speech full rate version 1. Reference Standards For details, see 3.2.2.11 "Channel Type" in 3rd Generation Partnership Project (3GPP) TS48008-840.


Cell Identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies a cell covered by the base station subsystem (BSS). In handover procedures, two types of cell identifier are introduced: cell-identifier-serving for the source cell and cell-identifier-target for the target cell. cell-identifier-serving consists of the following fields: spare4: indicates whether the whole or a part of Cell Global Identification (CGI) is used for source cell identification. 0: The whole CGI is used to identify the source cell. 1: The Location Area Identification (LAI) is used to identify the source cell. 2: The Cell Identity (CI) is used to identify the source cell. gci: provides source cell identification in the selected form.

Cell Identifier

A HANDOVER REQUEST message is considered as an example here. In this example, spare4 is 0 indicating that CGI is used to identify the source cell, and gci (CGI of the source cell) is 4607100010001.

cell-identifier-target consists of the following fields: spare4: indicates whether the whole or a part of CGI is used for target cell identification. 0: The whole CGI is used to identify the target cell. 1: The LAI is used to identify the target cell. 2: The CI is used to identify the target cell. gci: provides target cell identification in the selected form.

A HANDOVER REQUEST message is considered as an example here. In this example, spare4 is 0 indicating that CGI is used to identify the target cell, and gci (CGI of the target cell) is 4607200010001. Reference Standards For details, see 3.2.2.17 "Cell Identifier" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Priority Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the priority of the request. This IE contains a few fields, including:

Priority

priority-level: indicates the priority level. preemption-Capability-Indicator: indicates whether this allocation request can preempt an existing connection. This field is encoded as 1 to allow preemption, and as 0 to disallow preemption. queuing: indicates whether this allocation request can be queued. preemption-Vulnerability-indicator: indicates whether the connection used by this allocation request can be preempted by another allocation request. This field is encoded as 1 to indicate that this allocation request can be the target of preemption, and as 0 to indicate otherwise.

An ASSIGNMENT REQUEST message is considered as an example here. In this example, preemption-Capabilityindicator is 0 indicating that this allocation request cannot preempt an existing connection, priority-level is 12 indicating that this allocation request is assigned priority level 12, queuing is 1 indicating that this allocation request can be queued, and preemption-Vulnerability-indicator is 0 indicating that the connection used by this allocation request cannot be preempted. Reference Standards

For details, see 3.2.2.18 "Priority" in 3rd Generation Partnership Project (3GPP) TS48008840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Classmark Information Type 2 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the network with information concerning aspects of both high and low priority of the MS. This IE is conveyed in a connection management (CM) SERVICE REQUEST or UE-originated LOCATION UPDATING REQUEST message. It contains a few fields, including: voice-group-call-service: indicates MS for Voice Group Call Service (VGCS) notification reception. voice-broadcast-service: indicates MS for Voice Broadcast Service (VBS) notification reception. short-message-capability: indicates MS for mobile terminated point-to-point short message service (SMS). supplement-service-screen: indicates MS for supplementary service screening. cm-service-prompt: indicates MS for CM Service Prompt (also called CCBS). universal-character-set-2: indicates MS for Universal Character Set 2 (UCS2). location-service-capability: indicates MS for location request notification. classmark3-indicator: indicates MS for options indicated in Mobile Station Classmark 3.

Classmark Information Type 2

A CM SERVICE REQUEST message is considered as an example here. In this example, voice-group-call-service is 0 indicating that no VGCS capability or no notifications are wanted, and voice-broadcast-service is 0 indicating that no VBS capability or no notifications are wanted. Reference Standards For details, see 10.5.1.6 "Mobile Station Classmark 2" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Circuit Identity Code Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Defines the terrestrial channel over which the call will . Circuit identity code = pcm-multiplex-in-use x 32 + actualtimeslot-in-use, where: pcm-multiplex-in-use: defines the pulse code modulation (PCM) multiplex in use. actual-timeslot-in-use: defines the number of the timeslot assigned to the circuit.


An ASSIGNMENT REQUEST message is considered as an example here. In this example, pcm-multiplex-in-use is 0 indicating that PCM multiplex 0 is in use, and actualtimeslot-in-use is 0x1 indicating that timeslot 1 within PCM is activated. So, the circuit identity code is 1 (0x32 + 1 = 1). Reference Standards For details, see 3.2.2.2 "Circuit Identity Code" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RR Cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason for a message to have been sent.

Radio Resource (RR) Cause

An ASSIGNMENT COMPLETE message is considered as an example here. In this example, rr-cause is 0, indicating that sending of that message is a normal event and does not result from any errors.

Reference Standards For details, see 3.2.2.22 "Mobile Station Classmark 1" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Layer 3 Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description es radio interface messages from one network entity to another. This IE conveys different messages, depending on scenarios.

Layer 3 Information

In a GSM-to-UMTS inter-MSC handover, the Layer 3 Information IE conveys a HANDOVER TO universal terrestrial radio access network (UTRAN) COMMAND message. In an intra-GSM-system inter-MSC handover, the Layer 3 Information IE conveys a Radio Resource (RR) HANDOVER COMMAND message. In a GSM-to-cdma2000 inter-MSC handover, the Layer 3 Information IE conveys a HANDOVER TO CDMA2000 COMMAND message.

A HANDOVER COMMAND message in an intra-GSMsystem inter-MSC handover is considered as an example here. In this example, L3info is 09 06 26 00 00 00 00 00 00 00, indicating that the Layer 3 Information IE conveys an RR HANDOVER COMMAND message. Reference Standards For details, see 3.2.1.10 "Layer 3 Information" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cell Identifier List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies a list of cells. choice-by-cell-identification-discriminator: indicates whether the whole or a part of Cell Global identification (CGI) is used for cell identification of the cells in the list. 0: The whole CGI is used to identify the cells in the list. 1: A combination of Location Area Code (LAC) and Cell Identity (CI) is used to identify the cells in the list. 2: The CI is used to identify the cells in the list. 3: The Location Area Identification (LAI) is used to identify all cells within a location area. lai: identifies the location area where the MS is presently located.

Cell Identifier List

A PAGING message is considered as an example here. In this example, choice-by-cell-identification-discriminator is 4 indicating that LAI is used to identify all cells within the current location area, and lai is 460710001 indicating that the MS is presently located in location area 460710001. Reference Standards For details, see 3.2.2.27 "Cell Identifier List" in 3rd Generation Partnership Project (3GPP) TS48008-840.


Classmark Information Type 1 Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides the network with information concerning aspects of high priority of the MS. This IE affects the manner in which the network handles the operation of the MS. It contains a few fields, including:

Classmark Information Type 1

rf-power-capability: indicates the radio frequency (RF) power capability of the frequency band used. It is dimensioned into five classes. a51-alrorithm-indicator: indicates whether the MS s the encryption algorithm A5/1. The MS should set this indicator to 0 if the A5/1 algorithm is ed, and to 1 otherwise. early-classmark-send: indicates whether "Controlled Early Classmark Sending" option is implemented in the MS. The MS should set this indicator to 1 if "Controlled Early Classmark Sending" option is ed, and to 0 otherwise. revision-level-indicator: indicates the protocol version ed by the MS. This IE takes a few values, for example, value 0 for GSM phase 1, and value 2 for GSM phase 2 mobile stations.

A LOCATION UPDATING REQUEST message is considered as an example here. In this example, rf-power-capability is 1 indicating that RF power capability class 1 is applied, a51-alrorithm-indicator is 0 indicating that the MS s the A5/1 algorithm, earlyclassmark-send is 0 indicating that "Controlled Early Classmark Sending" option is not implemented in the MS, and revision-levelindicator is 0 indicating that GSM phase 1 MS is used.

Reference Standards For details, see 10.5.1.5 "Mobile Station Classmark 1" in 3rd Generation Partnership Project (3GPP) TS24008-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Chosen Channel Description of the IE Reference Standards Description of the IE Information Description Element (IE) Contains a description of the channel allocated to the MS. This IE is included only when the base station subsystem (BSS) has allocated a channel. It consists of the following fields: channel-mode: indicates the mode of the allocated channel. channel: indicates the data rate of the allocated channel.

Chosen Channel

A HANDOVER REQUEST ACKNOWLEDGE message is considered as an example here. In this example, channel-model is 13 indicating that channel mode is data-36-kbits-radio-interface, and channel is 4 indicating that the channel rate is eight-full-rate-tchs. Reference Standards For details, see 3.2.2.33 "Chosen Channel" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Chosen Encryption Algorithm Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the encryption algorithm being used by the base station subsystem (BSS). This IE is included only when the BSS has chosen an encryption algorithm. Chosen Encryption Algorithm A CIPHER MODE COMPLETE message is considered as an example here. In this example, chosen-encryption-algorithm is 2, indicating that the BSS has chosen GSM A5/1 algorithm. Reference Standards For details, see 3.2.2.44 "Chosen Encryption Algorithm" in 3rd Generation Partnership Project (3GPP) TS24008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Current Channel Type 1 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains a description of the channel allocated to the MS. This IE consists of the following fields: channel-mode: indicates the mode of the allocated channel. channel: indicates the data rate of the allocated channel.

Current Channel Type 1 A HANDOVER REQUIRED message is considered as an example here. In this example, channel-mode is 1 indicating that a speech (full rate or half rate) channel is allocated, and channel is 8 indicating that the channel rate is one-full-rate-tch. Reference Standards For details, see 3.2.2.49 "Current Channel Type 1" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cause Description of the IE Reference Standards Description of the IE Information Description Element (IE) Indicates the reason for a particular event to have occurred. This IE contains the cause-value field. Cause A HANDOVER COMPLETE message is considered as an example here. In this example, cause-value is 11, indicating that the message is sent because the handover is successful. Reference Standards For details, see 3.2.2.5 "Cause" in 3rd Generation Partnership Project (3GPP) TS48008840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Speech Version Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the speech version being used by the base station subsystem (BSS). Speech Version An ASSIGNMENT COMPLETE message is considered as an example here. In this example, speech-version-identifier is 1, indicating that the BSS is using GSM speech full rate version 1. Reference Standards For details, see 3.2.2.51 "Speech Version" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

eMLPP Priority Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains the eMLPP priority of the call. This IE contains the callpriority field.

enhanced multi-level precedence and preemption (eMLPP) Priority

A PAGING message is considered as an example here. In this example, call-priority is 4, indicating that eMLPP priority level 1 is applied to the call.

Reference Standards For details, see 3.2.2.56 "eMLPP Priority" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IMSI Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides the International Mobile Subscriber Identity (IMSI).

IMSI type-of-identity: indicates which type of identity information is selected to identify the MS. odd-or-even-ind: indicate whether the selected mobile identity type consists of an odd or even number of digits. imsi: indicates IMSI. A PAGING message is considered as an example here. In this example, typeof-identity is 1 indicating that IMSI is selected to identify the MS, odd-or-evenind is 1, indicating that IMSI contains an odd number of digits, and IMSI is 4600007550009082. Reference Standards For details, see 3.2.2.6 "IMSI" in 3rd Generation Partnership Project (3GPP) TS48008840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TMSI Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

TMSI

Provides the Temporary Mobile Subscriber Identity (TMSI). This IE is included in a PAGING message if the network uses TMSI to page the MS. A PAGING message is considered as an example here. In this example, TMSI is 0x60340039.

Reference Standards For details, see 3.2.2.7 "TMSI" in 3rd Generation Partnership Project (3GPP) TS48008840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Layer 3 Header Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the base station subsystem (BSS) with information that must be included in the header of layer 3 messages over the radio interface. This IE is not included, unless otherwise required. It contains the following fields, including:


protocol-discriminator: identifies the L3 protocol to which the L3 message belongs. ti-value: indicates the value of transaction identifier. ti-flag: identifies whether the message sender or receiver has assigned the transaction identifier (TI) value to this transaction.

An ASSIGNMENT REQUEST message is considered as an example here. In this example, protocol-discriminator is 6 indicating that the message belongs to the radio resource (RR) protocol, and ti-value is 0 indicating that the transaction identifier is 0. Reference Standards For details, see 3.2.2.9 "Layer 3 Header Information" in 3rd Generation Partnership Project (3GPP) TS48008-840. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CSFB Indication Description of the IE Reference Standards Description of the IE Information Description Element (IE) Indicates that the radio connection is established in a circuit switched fallback (CSFB) procedure. Cause CSFB Indication: Indicates the cause IE. A CLEAR_COMMAND message is used as an example. Reference Standards For details, see 3.2.2.121 in 48008-a60. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Redirect Attempt Flag IE Description Reference Standards IE Description IE

Description Indicates that the MSC server is required to initiate a Multi-Operator Core Network (MOCN) flow for the current call.

Redirect Attempt Flag

The example message in the preceding figure is Location updating request. If this message contains the redirect-attempt-flag IE, the BSS s the MOCN feature but the mobile terminal does not the MOCN feature. In this case, the MSC server must initiate a MOCN flow.

Reference Standards For details, see section 3.2.2.111 "Redirect Attempt Flag" in 3GPP TS 48008-b40. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Iu-CS Interface Protocol Description of the Iu-CS Interface Protocol Description of the Common Part of Messages Description of the Identity Messages Description of the Messages Used in the RAB Assignment Flow Description of the Encryption Mode Messages Description of the Paging Messages Description of the Messages Used in the Relocation Flow Description of the Release Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Iu-CS Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC/VLR communicates with the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) through the Radio Access Network Application Part (RANAP). Figure 1 shows the application of the RANAP.

Figure 1 Application of the RANAP Protocol Stack Figure 2 and Figure 3 show the protocol stack of the Iu interface. Figure 2 Protocol stack of the Iu interface (ATM)

Figure 3 Protocol stack of the Iu interface (IP)

RANAP is the Signaling System No. 7 (SS7) layer signaling protocol for the Iu interface, which is between the UTRAN and the Core Network (CN). The MSC, serving as a functional entity in the Circuit-Switched (CS) domain, interconnects with the UTRAN by using the RANAP through the control plane of the Iu-CS interface. The Iu-CS interface protocol includes the following: 1. Control plane: the control plane signaling RANAP and signaling bearer 2. plane: the plane protocol IuUP and data bearer 3. Control plane of the transmission network: the data bearer and control signaling Access Link Control Application Part (ALCAP) and signaling bearer Message List Table 1 List of common -network interface messages Message

Direction

RAB ASSIGNMENT REQUEST MSC->RNC

RAB ASSIGNMENT RESPONSE

RNC->MSC

SECURITY MODE COMMAND MSC->RNC

SECURITY MODE COMPLETE RNC->MSC

Function This message is sent by the MSC to the RNC to request the establishment, modification, or release of one or more Radio Access Bearer (RAB) for a subscriber. This message is sent by the RNC to report the outcome of the request from the RAB ASSIGNMENT REQUEST message. This message is sent by the MSC to trigger the integrity and ciphering functions over the radio interface. This message is sent by the RNC as a successful response to a SECURITY MODE COMMAND message.

PAGING

MSC->RNC

Relocation Required

RNC->MSC

RELOCATION COMMAND

MSC->RNC

RELOCATION REQUEST

MSC->RNC

RELOCATION REQUEST ACKNOWLEDGE

RNC->MSC

RELOCATION DETECT

RNC->MSC

RELOCATION COMPLETE

RNC->MSC

COMMON ID

MSC->RNC

IU RELEASE COMMAND

MSC->RNC

IU RELEASE COMPLETE

RNC->MSC

This message is sent by the MSC to request the RNC to page a Equipment (UE). This message is sent by the source RNC to inform the MSC that a relocation is to be performed. This message is sent by the MSC to the source RNC to inform that resources for the relocation are allocated in the target RNC. This message is sent by the MSC to request the target RNC to allocate necessary resources for a relocation. This message is sent by the target RNC to inform the MSC of the result of the resource allocation for the requested relocation. This message is sent by the RNC to inform the MSC that the UE has detected a new channel but has not switched to the new channel. This message is sent by the target RNC to inform the MSC that the relocation is complete. This message is sent by the MSC to inform the RNC of the permanent NAS UE identity and additional information of a subscriber. This message is sent by the MSC to instruct the RNC to release all resources related to the Iu connection. This message is sent by the RNC as a response to the IU RELEASE COMMAND message.

Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 IEs carried in the common part of messages Information Element (IE)

Description Indicates the sender and receiver of a message.

Header

sender-mid: Indicates the number of the calling control unit (CCU) module from which the message is sent. sender-pid: Indicates the number of the internal processing module that sends the message. receiver-mid: Indicates the number of the CCU module to which the message is sent. receiver: Indicates the number of the internal processing module that receives the message. The Location Updating Request message is considered as an example here. In this example, sender-mid is 22, which indicates the number of the CCU module from which the message is sent; senderpid is 179, which indicates that the message is sent by the sc module, receiver-mid is 22, which indicates the number of the CCU module to which the message is sent; receiver-pid is 141, which indicates that the message is sent to the Radio Access Network Application Part (RANAP) module. The message is sent from the sc module to the RANAP module on CCU module 22. Indicates the SC connection and signaling point of the RNC.

Signaling Connection Control Part (SC) message identifier

sc-connect-id: Identifies an SC connection. spc-of-14-bit: Indicates the 14-bit signaling point code (SPC) of the RNC. ssn: Indicates the subsystem number. The Location Updating Request message is considered as an example here. This message indicates that the SC connection number is 103, the SPC of the RNC is 0x2773, and the subsystem number of the RNC is 142 (which indicates that the subsystem is ranap). Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Identity Messages COMMON ID Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

COMMON ID Message Function Associated IEs Reference Standards Message Function This message is sent by the MSC to inform the RNC of the permanent NAS UE identity and additional information of a subscriber. Figure 1 shows the main IEs of the message.

Figure 1 COMMON ID message Associated IEs Information Element (IE)

Description

Message Type

Uniquely identifies the message being sent. In a COMMON ID message, Message type is COMMON ID. For details, see Message Type.

Permanent NAS UE Identity

Contains the international mobile subscriber identity (IMSI) of a subscriber. For details, see Permanent NAS UE Identity.

SNA Access Information

Provides information about the area(s) in the PLMN(s) that the UE is authorized to access. For details, see SNA Access Information.

Reference Standards For details, see 9.1.24 "COMMON ID" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Identity Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Messages Used in the RAB Assignment Flow RAB ASSIGNMENT REQUEST RAB ASSIGNMENT RESPONSE Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RAB ASSIGNMENT REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the RNC to request the establishment, modification, or release of one or more RABs for a UE. Figure 1 and Figure 2 show the IEs contained in the radio access bearer (RAB) ASSIGNMENT REQUEST message. Figure 1 RAB ASSIGNMENT REQUEST (carrying RABs To Be Setup Or Modified List)

Figure 2 RAB ASSIGNMENT REQUEST (carrying RABs To Be Released List)


Description

RABs To Be Setup Or Modified List

Provides a list of the RABs to be set up or modified. For details, see RABs To Be Setup Or Modified List.

RABs To Be Setup Or Modified Item IEs

Provides the detailed information about the RABs to be set up or modified. For details, see RABs To Be Setup Or Modified Item IEs.

First Setup Or Modify Item

Indicates the first RAB to be set up or modified. For details, see First Setup Or Modify Item.

RAB ID

Indicates the ID of a RAB. For details, see RAB ID.

NAS Synchronisation Indicator

Contains the transparent NAS information that is transferred without interpretation in the RNC.

For details, see NAS Synchronisation Indicator. RAB Parameters

Specifies the attributes of a RAB. For details, see RAB Parameters.

Plane Information

Contains the information about the plane. For details, see Plane Information.

Plane Mode

Indicates the mode of operation of the plane. For details, see Plane Mode.

UP Mode Versions

Indicates the versions of the selected plane modes that are required and ed by the CN. For details, see UP Mode Versions.

Transport Layer Information

Contains the information about the transport layer. For details, see Transport Layer Information.

Transport Layer Address

Indicates the IP address to be used for the plane transport. For details, see Transport Layer Address.

Iu Transport Association

Indicates the association between a RAB and the corresponding transport bearer. For details, see Iu Transport Association.

RABs To Be Released List

Provides a list of the RABs to be released. For details, see RABs To Be Released List.

RABs To Be Released Item IEs

Provides the detailed information about the RABs to be released. For details, see RABs To Be Released Item IEs.

Cause

Contains the cause of the release of a RAB. For details, see Cause.

Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the RAB Assignment Flow


RAB ASSIGNMENT RESPONSE Message Function Associated IEs Reference Standards Message Function This message is sent from the RNC to the MSC, carrying the outcome of the request from the radio access bearer (RAB) ASSIGNMENT REQUEST message. Figure 1, Figure 2, and Figure 3 show the IEs contained in the RAB ASSIGNMENT RESPONSE message. Figure 1 RAB ASSIGNMENT RESPONSE (carrying RABs Setup Or Modified List)

Figure 2 RAB ASSIGNMENT RESPONSE (carrying RABs Released List)

Figure 3 RAB ASSIGNMENT RESPONSE (carrying RABs Failed To Release List)


RABs Setup Or Modified List

Description Provides a list of the established or modified RABs. For details, see RABs Setup Or Modified

List.

RABs Setup Or Modified Item IEs

Provides the detailed information about the established or modified RABs. For details, see RABs Setup Or Modified Item IEs.

RAB ID

Indicates the ID of a RAB. For details, see RAB ID.

RABs Released List

Provides a list of the released RABs. For details, see RABs Released List.

RABs Released Item IEs

Provides the detailed information about the released RABs. For details, see RABs Released Item IEs.

RABs Failed To Release List

Provides a list of the RABs that are not successfully released. For details, see RABs Failed To Release List.

RABs Failed To Release Item IEs

Provides the detailed information about the RABs that are not successfully released. For details, see RABs Failed To Release Item IEs.

Cause

Indicates the cause of the failure to release a RAB. For details, see Cause.

Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the RAB Assignment Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Encryption Mode Messages SECURITY MODE COMMAND SECURITY MODE COMPLETE Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SECURITY MODE COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent from the MSC to the RNC to trigger the integrity and ciphering functions over the radio interface. Figure 1 shows the main IEs of the message. Figure 1 SECURITY MODE COMMAND message


Description

Message Type

Uniquely identifies the message being sent. In a SECURITY MODE COMMAND message, Message type is SECURITY MODE COMMAND. For details, see Message Type.

Integrity Protection Information

Contains the integrity protection information, including the key and available algorithms. For details, see Integrity Protection Information.


Contains the data encryption information, including the key and available algorithms. For details, see Encryption Information.

Key Status

Indicates whether the key contained in a SECURITY MODE COMMAND message is new or used. The key status can be NEW or OLD. For details, see Key Status.

Reference Standards For details, see 9.1.26 "SECURITY MODE COMMAND" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Encryption Mode Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SECURITY MODE COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent by the RNC as a successful response to a SECURITY MODE COMMAND message. Figure 1 shows the main IEs of the message. Figure 1 SECURITY MODE COMPLETE message

Associated IEs


Description

Message Type

Uniquely identifies the message being sent. In a SECURITY MODE COMPLETE message, Message type is SECURITY MODE COMPLETE. For details, see Message Type.

Chosen Integrity Protection Algorithm

Indicates the integrity protection algorithm being used by the RNC. For details, see Chosen Integrity Protection Algorithm.


Indicates the encryption algorithm being used by the RNC. For details, see Chosen Encryption Algorithm.

Reference Standards For details, see 9.1.27 "SECURITY MODE COMPLETE" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Encryption Mode Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Paging Messages PAGING Paging response Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PAGING Message Function Associated IEs Reference Standards Message Function This message is sent by the MSC to request the RNC to page a UE. Figure 1 shows the main IEs of the message.

Figure 1 PAGING message Associated IEs Information Element (IE)

Description

Message Type

Uniquely identifies the message being sent. In a PAGING message, Message type is PAGING. For details, see Message Type.

CN Domain Indicator

Indicates the CN domain from which the message is sent or to which the message is sent. The CN domain consists of the CS domain and the Packet-Switched domain (PS domain). For details, see CN Domain Indicator.


Indicates the permanent identity of a UE in the universal terrestrial radio access network (UTRAN) and the CN. For details, see Permanent NAS UE Identity.

Temporary UE Identity

Indicates a temporary identity of a UE in the UTRAN and the CN. This IE is carried in the PAGING message only when the UE is paged based on the temporary mobile subscriber identifier (TMSI). For details, see Temporary UE Identity.

Paging Area ID

Identifies the area where a PAGING message is to be broadcast. For details, see Paging Area ID.

Paging Cause

Indicates the cause for paging a UE. For details, see Paging Cause.

Global CN-ID

Globally identify a CN. For details, see Global CN-ID.

Reference Standards For details, see 9.1.23 "PAGING" in 3rd Generation Partnership Project (3GPP) 25413801. Parent topic: Description of the Paging Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Paging response Message Function Associated IEs Reference Standards Message Function This message is sent by the RNC to the MSC as a response to the paging request message. Figure 1 shows the main IEs of the message. Figure 1 Paging response message


Description


Indicates the Layer 3 protocol to which the Layer 3 messages belong. For details, see Protocol Discriminator.

Skip Indicator

Indicates whether the message is valid. If Skip Indicator is 0, it indicates that the message is valid. The invalid messages are not processed. For details, see Skip indicator.

Message Type

Uniquely identifies a message. Message Type occupies one byte. In a PAGING RESPONSE message, Message Type is 39. For details, see Message Type.



Spare Half Octet

Indicates the reserved half Octet. For details, see Spare Half Octet.


Indicates Classmark2 of the UE. For details, see Classmark Information Type 2.

Mobile Identity

Identifies a UE. For details, see Mobile Identity.

Reference Standards For details, see 9.1.25 "Paging response" in 3rd Generation Partnership Project (3GPP) 44018-840. Parent topic: Description of the Paging Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Messages Used in the Relocation Flow RELOCATION REQUIRED RELOCATION COMMAND RELOCATION REQUEST RELOCATION REQUEST ACKNOWLEDGE RELOCATION DETECT RELOCATION COMPLETE Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION REQUIRED Message Function Associated IEs Reference Standards Message Function This message is sent by the source RNC to inform the MSC that a relocation is to be performed. Figure 1 shows the main IEs of the message. Figure 1 RELOCATION REQUIRED message


Description Uniquely identifies the message being sent. In a RELOCATION REQUIRED message,

Message Type

Message type is RELOCATION REQUIRED. For details, see Message Type.

Relocation Type

Indicates whether the relocation of the Serving Radio Network Subsystem (SRNS) is to be executed with or without involvement of the UE. For details, see Relocation Type.

Cause

Indicates the cause of the relocation. For details, see Cause.

Source ID

Identifies the source for the relocation of the SRNS. For details, see Source ID.

Target ID

Identifies the target for the relocation of the SRNS. For details, see Target ID.

Source RNC To Target RNC Transparent Container

Contains the information sent from the source RNC to the target RNC. For details, see Source RNC To Target RNC Transparent Container.

Reference Standards For details, see 9.1.9 "RELOCATION REQUIRED" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent by the MSC to the source RNC to inform that resources for the relocation are allocated in the target RNC. Figure 1 shows the main IEs of the message. Figure 1 RELOCATION COMMAND message

Associated IEs


Description

Message Type

Uniquely identifies the message being sent. In a RELOCATION COMMAND message, Message type is RELOCATION COMMAND. For details, see Message Type.

Target RNC To Source RNC Transparent Container

Indicates the message that is transparently sent from the target RNC to the source RNC. For details, see Target RNC To Source RNC Transparent Container.

L3 Information

Contains the radio interface message. For details, see L3 Information.

RABs To Be Released List

Provides a list of the RABs to be released. For details, see RABs To Be Released List.


Provides the detailed information about the RABs to be released. For details, see RABs To Be Released Item IEs.

radio access bearer (RAB) ID

uniquely identifies a radio access bearer for a UE. At present, RAB ID is set to 1. For details, see RAB ID.

Reference Standards For details, see 9.1.12 "RELOCATION COMMAND" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION REQUEST Message Function Associated IEs Reference Standards Message Function This message is sent by the MSC to request the target RNC to allocate necessary resources for a relocation. Figure 1 shows the main IEs of the message. Figure 1 RELOCATION REQUEST message


Description

Message Type

Uniquely identifies the message being sent. In a RELOCATION REQUEST message, Message type is RELOCATION REQUEST. For details, see Message Type.


Identifies a UE in the universal terrestrial radio access network (UTRAN) and the CN. For details, see Permanent NAS UE Identity.

Cause

Indicates the cause of the relocation. For details, see Cause.

CN Domain Indicator

Indicates the CN domain from which the message is sent or to which the message is sent. The CN domain consists of the CS domain and the PS domain. For details, see CN Domain Indicator.

Source RNC To Target RNC Transparent Container

Indicates an information element that is produced by the source RNC and is transmitted to the target RNC. For details, see Source RNC To Target RNC Transparent Container.

RABs To Be Setup List

Provides a list of the RABs to be established. For details, see RABs To Be Setup List.

RABs To Be Setup Item IEs

Provides the detailed information about the RABs to be established. For details, see RABs To Be Setup Item IEs.


Indicates the address of the transport layer. For details, see Transport Layer Address.


Indicates the association between a radio access bearer (RAB) and the corresponding transport bearer. For details, see Iu Transport Association.


Contains the integrity protection information. For details, see Integrity Protection Information.


Contains the data encryption information. For details, see Encryption Information.

Iu Signalling Connection Identifier

Identifies an Iu connection between the CN and the RNC. For details, see Iu Signalling Connection Identifier.

Reference Standards For details, see 9.1.10 "RELOCATION REQUEST" in 3rd Generation Partnership Project (3GPP) 25413-801.

Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION REQUEST ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function This message is sent by the target RNC to inform the MSC of the result of the resource allocation for the requested relocation. Figure 1 shows the main IEs of the message. Figure 1 RELOCATION REQUEST ACKNOWLEDGE message


Description

Message Type

Uniquely identifies the message being sent. In a RELOCATION REQUEST ACKNOWLEDGE message, Message type is RELOCATION REQUEST ACKNOWLEDGE.

Target RNC To Source RNC Transparent Container

Indicates the message that is transparently sent from the target RNC to the source RNC. For details, see Target RNC To Source RNC Transparent Container.

RABs Setup List

Provides a list of the established RABs. For details, see RABs Setup List.

RABs Setup Item IEs

Provides the detailed information about the established RABs. For details, see RABs Setup Item IEs.

RABs Failed To Setup List

Provides the detailed information about the RABs that are not successfully established. For details, see RABs Failed To Setup List.

RABs To Be Setup List

Provides a list of the RABs to be established. For details, see RABs To Be Setup List.


Provides the detailed information about the RABs to be established. For details, see RABs To Be Setup Item IEs.


Indicates the address of the transport layer. For details, see Transport Layer Address.


Indicates the association between a radio access bearer (RAB) and the corresponding transport bearer. For details, see Iu Transport Association.


Contains the integrity protection information. For details, see Integrity Protection Information.


Contains the data encryption information. For details, see Encryption Information. Identifies an Iu connection between the CN


and the RNC. For details, see Iu Signalling Connection Identifier.

Reference Standards For details, see 9.1.11 "RELOCATION REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION DETECT Message Function Associated IEs Reference Standards Message Function This message is sent by the target RNC to inform the MSC that the UE has detected a new channel but has not switched to the new channel. Figure 1 shows the main IEs of the message.

Figure 1 RELOCATION DETECT message Associated IEs Information Element (IE)

Description

Message Type

Uniquely identifies the message being sent. In a RELOCATION DETECT message, Message type is RELOCATION DETECT. For details, see Message Type.

Reference Standards For details, see 9.1.13 "RELOCATION DETECT" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELOCATION COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent by the target RNC to inform the MSC that the relocation is complete. Figure 1 shows the main IEs of the message.

Figure 1 RELOCATION COMPLETE message Associated IEs Information Element (IE)

Description

Message Type

Uniquely identifies the message being sent. In a RELOCATION COMPLETE message, Message type is RELOCATION COMPLETE. For details, see Message Type.

Reference Standards For details, see 9.1.14 "RELOCATION COMPLETE" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Messages Used in the Relocation Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Release Messages IU RELEASE COMMAND IU RELEASE COMPLETE Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IU RELEASE COMMAND Message Function Associated IEs Reference Standards Message Function This message is sent by the MSC to instruct the RNC to release all resources related to the Iu connection. Figure 1 shows the IEs of the message. Figure 1 IU RELEASE COMMAND message

Associated IEs


Description

Message Type

Uniquely identifies the message being sent. In a IU RELEASE COMMAND message, Message type is IU RELEASE COMMAND. For details, see Message Type.

Cause

Indicates the cause of the release. For details, see Cause.

End Of CSFB

Indicates that the radio connection is established in a circuit switched fallback (CSFB) procedure. For details, see End Of CSFB.

Reference Standards For details, see 9.1.7 "IU RELEASE COMMAND" in 3rd Generation Partnership Project (3GPP) 25413-a70. Parent topic: Description of the Release Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IU RELEASE COMPLETE Message Function Associated IEs Reference Standards Message Function This message is sent by the RNC to inform the MSC that all the resources related to the Iu connection are released. Figure 1 shows the IEs of the message.

Figure 1 IU RELEASE COMPLETE message Associated IEs Information Element (IE)

Description

Message Type

Uniquely identifies the message being sent. In a IU RELEASE COMPLETE message, Message type is IU RELEASE COMPLETE. For details, see Message Type.

Uniquely identifies a RAB for a UE. At present, RAB ID is radio access bearer (RAB) ID set to 1.

For details, see RAB ID. RABs Released List

Provides a list of released RABs. For details, see RABs Released List.


Provides the detailed information about the released RABs. For details, see RABs Released Item IEs.

Reference Standards For details, see 9.1.8 "IU RELEASE COMPLETE" in 3rd Generation Partnership Project (3GPP) 25413-801. Parent topic: Description of the Release Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Cause Chosen Encryption Algorithm Chosen Integrity Protection Algorithm CN Domain Indicator Encryption Information First Setup Or Modify Item Global CN-ID Integrity Protection Information Iu Transport Association Key Status L3 Information Message Type MS Classmark 2 MS Classmark 3 NAS Synchronisation Indicator Paging Area ID Paging Cause Permanent NAS UE Identity RAB ID RAB Parameters RABs Failed To Release Item IEs RABs Failed To Release List RABs Failed To Setup Item IEs RABs Failed To Setup List RABs Released Item IEs RABs Released List

RABs Setup Item IEs RABs Setup List RABs Setup Or Modified Item IEs RABs Setup Or Modified List RABs To Be Released Item IEs RABs To Be Released List RABs To Be Setup Item IEs RABs To Be Setup List RABs To Be Setup Or Modified Item IEs RABs To Be Setup Or Modified List Relocation Type SNA Access Information Source ID Source RNC To Target RNC Transparent Container Iu Signalling Connection Identifier Target ID Target RNC To Source RNC Transparent Container Temporary UE Identity Transport Layer Address Transport Layer Information UP Mode Versions Plane Information Plane Mode End Of CSFB Parent topic: Iu-CS Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cause Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the reason for a particular event for the Radio Access Network Application Part (RANAP) protocol.

Cause cause: Indicates the cause IE. radioNetwork: Indicates the specific reason. The RELOCATION REQUIRED message is considered as an example here. In this example, radioNetwork is 2, which indicates that the reason for the current relocation is trelocoverall-expiry. Reference Standards For details, see 9.2.1.4 "Cause" in 3rd Generation Partnership Project (3GPP) TS25413801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Chosen Encryption Algorithm Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the encryption algorithm being used by the RNC.


chosenEncryptionAlgorithm: Indicates the encryption algorithm being used by the RNC. The SECURITY MODE COMPLETE message is considered as an example here. In this example, chosenEncryptionAlgorithm is 1, which indicates that the encryption algorithm used by the RNC is standard-UMTS-encryption-algorithm-UEA1.

Reference Standards For details, see 9.2.1.14 "Chosen Encryption Algorithm" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Chosen Integrity Protection Algorithm Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the integrity protection algorithm being used by the RNC.

Chosen Integrity Protection Algorithm

chosenIntegrityProtectionAlgorithm: Indicates the integrity protection algorithm being used by the RNC. The SECURITY MODE COMPLETE message is considered as an example here. In this example, chosenIntegrityProtectionAlgorithm is 0, which indicates that the integrity protection algorithm being used by the RNC is standard-UMTS-integrity-algorithm-UIA1.

Reference Standards For details, see 9.2.1.13 "Chosen Integrity Protection Algorithm" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CN Domain Indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the CN domain from which the message is sent or to which the message is sent. The CN domain consists of the CS domain and the PS domain.

CN Domain Indicator

cN-DomainIndicator: Indicates the CN domain. The PAGING message is considered as an example here. In this example, cN-DomainIndicator indicates that the PAGING message is sent to the CS domain. Reference Standards For details, see 9.2.1.5 "CN Domain Indicator" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Encryption Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the data encryption information (key and available algorithms) used to control any encryption equipment at the RNC.


permittedAlgorithms: Indicates the algorithm list. EncryptionAlgorithm: Indicates the algorithm used for data encryption. key: Indicates the key used for data encryption. The SECURITY MODE COMMAN message is considered as an example here. The message indicates that the RNC uses the standard-UMTSencryption-algorith-UEA1 algorithm and the key contained in the message for data encryption. Reference Standards For details, see 9.2.1.12 "Encryption Information" in 3rd Generation Partnership Project (3GPP) TS25413-801.


First Setup Or Modify Item Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the first radio access bearer (RAB) to be established or modified.

rAB-ID: Uniquely identifies a RAB for a UE. At present, it is set to 1. nAS-SynchronisationIndicator: Indicates the nAS information transferred without interpretation in the RNC. rAB-Parameters: Indicates the radio access bearer (rAB) parameters. PlaneInformation: Provides the information about the plane. transportLayerInformation: Provides the information about the transport layer.

First Setup Or Modify Item

The RAB ASSIGNMENT REQUEST message is considered as an example here. In this example, rAB-ID is 1, which indicates that RAB 1 is the first RAB to be established or modified for the UE. Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


Global CN-ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the ID of the CN. Global CN-ID contains the public land mobile network (PLMN) identity and the CN ID.

Global CN-ID pLMNidentity: Identifies a PLMN. cN-ID: Identifies a CN. It is used to identify a CN in POOL networking. The PAGING message is considered as an example here. This message indicates that the PLMN identity is 64 F0 37 and CN ID is 0. Reference Standards For details, see 9.2.1.46 "Global CN-ID" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Integrity Protection Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the integrity protection information (key and available algorithms).


IntegrityProtectionInformation: Indicates the Integrity Protection Information IE. IntegrityProtectionAlgorithm: Indicates the available algorithms. key: Indicates the key used for integrity protection. The SECURITY MODE COMMAND message is considered as an example here. This message indicates that the standard-UMTSintergrity-alorithm-UIA1 algorithm and the key contained in the message are used for data integrity protection. Reference Standards For details, see 9.2.1.11 "Integrity Protection Information" in 3rd Generation Partnership Project (3GPP) TS25413-801.


Iu Transport Association Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the association between a radio access bearer (RAB) and the corresponding transport bearer.


bindingID: Identifies the association between a RAB and the corresponding transport bearer. The RELOCATION REQUEST message is considered as an example here. The message indicates that the ID of the association between the RAB and the transport bearer is 01 1E 00 12.

Reference Standards For details, see 9.2.2.2 "Iu Transport Association" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Key Status Description of the IE Reference Standards Description of the IE Information Description Element (IE) Indicates whether the keys contained in a SECURITY MODE COMMAND message are new or have been used.

Key Status keyStatus: Indicates the status of the key. The SECURITY MODE COMMAN message is considered as an example here. In this message, keyStatus is 1, which indicates that the key contained in message is new. Reference Standards For details, see 9.2.1.36 "Key Status" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

L3 Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains the information about the radio interface. The contents of L3 Information vary according to the type of the relocation. In the case of 2G-to-3G inter-office relocation, L3 Information carries the HANDOVER TO universal terrestrial radio access network (UTRAN) COMMAND message. In the case of 2G inter-office relocation or 3G-to-2G relocation, L3 Information carries the radio resource (RR) HANDOVER COMMAND message. In the case of 2G-to-cdma2000 inter-office relocation, L3 Information carries the HANDOVER TO CDMA2000 COMMAND message.

L3 Information

The RELOCATION COMMAND message used in 3G-to-2G intra-office relocation is considered as an example here. In this example, l3-Information is 06 2B 00 2F 0D 00 2F 08 05 D8 63 21 93, which indicates the RR HANDOVER COMMAND message. Reference Standards For details, see 9.2.1.31 "L3 Information" in 3rd Generation Partnership Project (3GPP) TS25413-801.



Description Uniquely identifies the message being sent. It is mandatory for all messages.

Message Type initiatingMessage: Indicate the type of message. commonID: Indicates the specific message. The COMMON ID message is considered as an example here. This message indicates that the COMMON ID message is one of initiatingMessage messages. Reference Standards For details, see 9.2.1.1 "Message Type" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MS Classmark 2 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the access priority of a UE. The CN implements the access of a UE based on the value of Classmark2.

MS Classmark 2

voice-group-call-service: Indicates whether the UE s the voice group call service. voice-broadcast-service: Indicates whether the UE s the voice broadcast service. short-message-capability: Indicates whether the UE s the short message service. supplement-service-screen: Indicates whether the UE s supplementary services. cm-service-prompt: Indicates whether the UE s the completion of calls to busy subscriber (CCBS) service. universal-character-set-2: Indicates whether the UE s ucs2 characters. location-service-capability: Indicates whether the UE s the location service.

classmark3-indicator: Indicates whether the UE s the Classmark3 indicator. The Relocation Required message is considered as an example here. In this example, voice-group-call-service and voice-broadcast-service are 0, which indicates that the UE does not the voice group call service or voice broadcast service. Reference Standards For details, see 9.2.1.26 "MS Classmark 2" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MS Classmark 3 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the general features (for example, single mode or dual mode) of a UE. The network operations vary according to the value of MS Classmark 3.

MS Classmark 3

classmakr-information-type3:Classmark3 The Classmark Update message is considered as an example here. In this example, classmakr-information-type3 is 60 14 54 00 00. The network obtains the information about the features of the UE after analyzing this code stream, and then perform the related operation.

Reference Standards For details, see 9.2.1.27 "MS Classmark 3" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

NAS Synchronisation Indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains the transparent NAS information that is transferred without interpretation in the RNC.

NAS Synchronisation Indicator

nAS-SynchronisationIndicator: Indicates the transparent NAS information that is transferred without interpretation in the RNC. The radio access bearer (RAB) ASSIGNMENT REQUEST message is considered as an example here. In this example, nASSynchronisationIndicator is 60, which indicates that the content of the NAS message that is transferred without interpretation in the RNC is 60.

Reference Standards For details, see 9.2.3.18 "NAS Synchronisation Indicator" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Paging Area ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the area where a PAGING message is to be broadcast. Paging Area ID can be a Location Area ID (LAI) or a Routing Area ID (RAC).

Paging Area ID LAI: Indicates that the PAGING message is to be broadcast in a location area (LA). The PAGING message is considered as an example here. In this example, pLMNidentity is 64 F0 44 and location area code (lAC) is 00 44, which indicate that the PAGING message is to be broadcast in LA 460440044. Reference Standards For details, see 9.2.1.21 "Paging Area ID" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Paging Cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the cause for paging a UE.

Paging Cause

pagingCause: Indicates the reason for the paging. The PAGING message is considered as an example here. In this example, pagingCause is 0, which indicates that the UE is paged because an ordinary call is to be terminated.

Reference Standards For details, see 9.2.3.3 "Paging Cause" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Permanent NAS UE Identity Description of the IE Reference Standards Description of the IE Information Element (IE) Description Identifies a UE used in the universal terrestrial radio access network (UTRAN) and the CN. The RNC uses this IE to find other existing signaling connections of the same UE.


imsi: Indicates the international mobile subscriber identity (IMSI). imsi-content: Indicates the contents of the IMSI. The COMMON ID message is considered as an example here. In this example, imsi-content is 460881104008832, which indicates that the IMSI of the subscriber is 460881104008832.

Reference Standards For details, see 9.2.3.1 "Permanent NAS UE Identity" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RAB ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Uniquely identifies a RAB for a UE. At present, RAB ID is set to 1.

Identifies a radio access bearer (RAB). rAB-ID: Indicates the ID of the RAB. The IU RELEASE COMPLETE message is considered as an example here. This message indicates that the UE uses RAB 1. Reference Standards For details, see 9.2.1.2 "RAB ID" in 3rd Generation Partnership Project (3GPP) TS25413801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RAB Parameters Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicate all RAB attributes.

radio access bearer (RAB) Parameters trafficClass: Indicates the type of application for which the RAB service is optimized. rAB-AsymmetryIndicator: Indicates asymmetry or symmetry of the RAB and traffic direction. The RAB ASSIGNMENT REQUEST message is considered as an example here. In this example, trafficClass is 0, which indicates the RAB is used for voice calls, and rAB-AsymmetryIndicator is 0, which indicates that the RAB is symmetric and the traffic direction is bidirectional. Reference Standards For details, see 9.2.1.3 "RAB Parameters" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Failed To Release Item IEs Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the detailed information about the RABs that are not successfully released.

RABs Failed To Release Item IEs

rAB-ID: Indicates the ID of the radio access bearer (RAB). cause: Indicates the reason for the release failure. The RAB ASSIGNMENT RESPONSE message is considered as an example here. In this example, rAB-ID is 1, which indicates the ID of the RAB.

Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Failed To Release List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides a list of the RABs that are not successfully released.

RABs Failed To Release List rAB-FailedItem: Indicates the specific RABs that are not successfully released. The radio access bearer (RAB) ASSIGNMENT RESPONSE message is considered as an example here. The message indicates that the RABs Failed To Release List contains only one rAB-FailedItem. Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Failed To Setup Item IEs Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides the detailed information about the RABs that are not successfully established.

RABs Failed To Setup Item IEs

rAB-ID: Indicates the ID of the radio access bearer (RAB). radioNetwork: Indicates the reason for the failure. The RELOCATION REQUEST ACKNOWLEDGE message is considered as an example here. In this message, rAB-ID is 3, which indicates RAB 3 is not successfully established, and radioNetwork is 30, which indicates that RAB 3 is not established because the RAB ID is invalid.

Reference Standards For details, see 9.1.11 "RELOCATION REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Failed To Setup List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides a list of the RABs that are not successfully established.

RABs Failed To Setup List

RAB-FailedList: Indicates the RABs Failed To Setup List IE. rAB-FailedItem: Indicates the specific RABs that are not successfully established. The RELOCATION REQUEST ACKNOWLEDGE message is considered as an example here. The message indicates that the RABs Failed To Setup List contains only one rAB-FailedItem. Reference Standards For details, see 9.1.11 "RELOCATION REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Released Item IEs Description of the IE Reference Standards Description of the IE information element (IE)

Description Provides the detailed information about the released RABs.


rAB-ID: Indicates the radio access bearer (RAB) ID, which is 1. dL-GTP-PDU-SequenceNumber: Indicates the GTP-PDU sequence number to be sent to the UE. uL-GTP-PDU-SequenceNumber:: Indicates the GTP-PDU sequence number to be sent to the SGSN. The IU RELEASE COMPLETE message is considered as an example here. In this example, rAB-ID is 1, which indicates that the ID of the current RAB is 1, and dL-GTP-PDU-SequenceNumber is 1, which indicates that the GTP-PDU sequence number to be sent to the UE.

Reference Standards For details, see 9.2.2.3 "DL GTP-PDU Sequence Number" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Released List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides a list of the released RABs.

RABs Released List rAB-ReleasedList-IuRelComp: Indicates the RABs Released List IE. rAB-ReleasedItem-IuRelComp: Indicates the specific RABs that are released. The IU RELEASE COMPLETE message is considered as an example here. The message indicates that the RABs Released List contains only one rAB-ReleasedItem. Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Setup Item IEs Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the detailed information about the established RABs.

RABs Setup Item IEs

rAB-ID: RABID. For details, see RAB ID. The RELOCATION REQUEST ACKNOWLEDGE message is considered as an example here. In this example, rAB-ID is 1, which indicates that the ID of the radio access bearer (RAB) for the UE is 1.

Reference Standards For details, see 9.1.11 "RELOCATION REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Setup List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides a list of the established RABs.

RABs Setup List rAB-SetupList-RelocReqAck: Indicates the list of the established RABs. rAB-SetupItem-RelocReqAck: Indicates the specific RABs that are successfully established. The RELOCATION REQUEST ACKNOWLEDGE message is considered as an example here. The message indicates that the RABs Setup List contains only one rAB-SetupItem. Reference Standards For details, see 9.1.11 "RELOCATION REQUEST ACKNOWLEDGE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Setup Or Modified Item IEs Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides the detailed information about the RABs that are established or modified. RABs Setup Or Modified Item IEs

rAB-ID: Indicates the ID of the radio access bearer (RAB). The RAB ASSIGNMENT RESPONSE message is considered as an example here. In this example, rAB-ID is 1, which indicates that the ID of the RAB for the UE is 1.

Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs Setup Or Modified List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides a list of the RABs that are established or modified.

RABs Setup Or Modified List rAB-SetupOrModifiedList: Indicates the list of the RABs that are established or modified. rAB-SetupOrModifiedItem: Indicates the specific RABs that are established or modified. The radio access bearer (RAB) ASSIGNMENT RESPONSE message is considered as an example here. The message indicates that the RABs Setup Or Modified List contains only one rABSetupOrModifiedItem. Reference Standards For details, see 9.1.4 "RAB ASSIGNMENT RESPONSE" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Released Item IEs Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the detailed information about the RABs to be released.


rAB-ReleaseItem: Indicates the radio access bearer (RAB) to be released. rAB-ID: Indicates the ID of the RAB. cause: Indicates the reason for the release. The RAB ASSIGNMENT REQUEST message is considered as an example here. In this example, rAB-ID is 1, which indicates the ID of the RAB for the UE is 1.

Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Released List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides a list of the RABs to be released.

RABs To Be Released List rAB-ReleaseList: Indicates the list of the RABs to be released. rAB-ReleaseItem: Indicates the specific RABs to be released. The radio access bearer (RAB) ASSIGNMENT REQUEST message is considered as an example here. The message indicates that the RABs To Be Released List contains only one rABReleaseItem. Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Setup Item IEs Description of the IE Reference Standards Description of the IE Information Element Description (IE) Provides the detailed information about the RABs to be established.


rAB-ID: Indicates the ID of the radio access bearer (RAB). For details, see RAB ID. nAS-SynchronisationIndication: Indicates the transparent non-access stratum (NAS) information that is transferred without interpretation in the RNC. For details, see NAS Synchronisation Indicator. rAB-Parameters: Indicates the radio access bearer (rAB) parameters. PlaneInformation: Provides the information about the plane. For details, see Plane Information. The RELOCATION REQUEST message is considered as an example here. In this example, rAB-ID is 1, which indicates that the ID of the RAB for the UE is 1.

Reference Standards For details, see 9.1.10 "RELOCATION REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Setup List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides a list of the RABs to be established.

RABs To Be Setup List rAB-SetupList-RelocReq: Indicates the list of the RABs to be established. rAB-SetupItem-RelocReq: Indicates the specific RABs to be established. The RELOCATION REQUEST message is considered as an example here. The message indicates that the RABs To Be Setup List contains only one rAB-SetupItem. Reference Standards For details, see 9.1.10 "RELOCATION REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Setup Or Modified Item IEs Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides the detailed information about the RABs to be established or modified.

RABs To Be Setup Or Modified Item IEs

The radio access bearer (RAB) ASSIGNMENT REQUEST message is considered as an example here. Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RABs To Be Setup Or Modified List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the list of the RABs to be established or modified.

RABs To Be Setup Or Modified List rAB-SetupOrModifyList: Indicates the list of the RABs to be established or modified. rAB-SetupOrModifyItemFirst: Indicates the RABs to be established or modified. The radio access bearer (RAB) ASSIGNMENT REQUEST message is considered as an example here. The message indicates that only one RAB is contained in the list of the RABs to be established or modified. Reference Standards For details, see 9.1.3 "RAB ASSIGNMENT REQUEST" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Relocation Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the relocation of the serving radio network system (SRNS) is to be executed with or without involvement of the UE. If Relocation Type is ue-involved, the RNC sends a handover command to the UE to trigger the relocation. If Relocation Type is uenot-involved, the relocation is triggered through the Iur interface.

Relocation Type

relocationType: Indicates the type of the relocation. The RELOCATION REQUIRED message is considered as an example here. In this example, relocationType is 0, which indicates that UE is not involved in the relocation, that is, the relocation is triggered through the Iur interface. Reference Standards For details, see 9.2.1.23 "Relocation Type" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SNA Access Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the area(s) in the PLMN(s) that the UE is authorized to access.

SNA Access Information

sNA-Access-Information: Indicates the SNA Access Information IE. authorisedPLMNs: Indicates the PLMN(s) that the UE is authorized to access. pLMNidentity: Identifies a PLMN. The COMMON ID message is considered as an example here. In this example, pLMNidentity is 00 00 01, which indicates that the UE is authorized to access the PLMN identified by 00 00 01.

Reference Standards For details, see 9.2.3.24 "SNA Access Information" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Source ID Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the ID of the source for the relocation of the serving radio network system (SRNS). The source ID contains the information about the public land mobile network (PLMN) and ID of the RNC.

Source ID

pLMNidentity: Identifies a PLMN. rNC_ID: Indicates the ID of the RNC. The RELOCATION REQUIRED message is considered as an example here. In this example, pLMNidentity is 64 F0 37, which indicates that the ID of the PLMN is 46073, and rNC-ID is 73, which indicates that the ID of the RNC on the access side is 73. Reference Standards For details, see 9.2.1.24 "Source ID" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Source RNC To Target RNC Transparent Container Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates an information element that is produced by the source RNC and is transmitted to the target RNC.

Source RNC To Target RNC Transparent Container relocationType: Indicates the type of the relocation. The RELOCATION REQUIRED message is considered as an example here. In this example, relocationType is 0, which indicates that UE is not involved in the relocation, that is, the relocation is triggered through the Iur interface. Reference Standards For details, see 9.2.1.28 "Source RNC To Target RNC Transparent Container" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Iu Signalling Connection Identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies an Iu connection between the CN and the RNC. The value of Iu Signalling Connection Identifier is a string of a maximum of 24 bits. The most significant bit of this IE indicates the node that allocates resources for this connection. Value:


1: Indicates that the resources for the Iu connection are allocated by the CN. 0: Indicates that the resources for the Iu connection are allocated by the RNC.

iuSignallingConnectionIdentifier: Indicates an Iu connection between the CN and the RNC. The RELOCATION REQUEST message is considered as an example here. The message indicates that the resources for Iu connection FC 00 01 are allocated by the CN. Reference Standards For details, see 9.2.1.38 "Iu Signalling Connection Identifier" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the target for the relocation of the serving radio network system (SRNS). The target ID can be the target RNC-ID (for 3G-3G relocation) or the Cell Global ID (GCI) of the relocation target (in case of 3G-to-2G relocation).

Target ID targetID: Identifies the target for the relocation of the SRNS. targetRNC-ID: Indicates that the target ID is the target RNCID. lAI: Indicates the location area identity. rNC-ID: Indicates the ID of the RNC. The RELOCATION REQUIRED message for 3G-3G relocation is considered as an example here. The message indicates that the target RNC is RNC 74 located in lAI 460740001. Reference Standards For details, see 9.2.1.25 "Target ID" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target RNC To Source RNC Transparent Container Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Indicates that the IE is an IE for information. This IE is produced by the target RNC and transmitted to the Target RNC To Source RNC source RNC. Transparent Container The RELOCATION COMMAND message is considered as an example here. Reference Standards For details, see 9.2.1.30 "Target RNC To Source RNC Transparent Container" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Temporary UE Identity Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the temporary identity of a UE.

Temporary UE Identity

tMSI: Indicates the temporary mobile subscriber identifier (TMSI) of a UE. The PAGING message is considered as an example here. In this example, tMSI is 60 34 00 69, which indicates that the TMSI of the UE is 60 34 00 69.

Reference Standards For details, see 9.2.3.2 "Temporary UE Identity" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Transport Layer Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the address to be used for Transport Network Control Plane signaling to establish the transport bearer in the case of transport bearer establishment with Access Link Control Application Part (ALCAP).

Transport Layer Address transportLayerAddress: Indicates the address to be used in the transport layer. The RELOCATION REQUEST message is considered as an example here. Reference Standards For details, see 9.2.2.1 "Transport Layer Address" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Transport Layer Information Description of the IE Reference Standards Description of the IE Information Element (IE) Description Contains the information about the transport layer.

Transport Layer Information

transportLayInformation: Indicates the transportLayInformation IE. transportLayerAddress: Indicates the address to be used in the transport layer. bindlingID: Identifies the association between the radio access bearer (RAB) and the corresponding transport bearer. The RAB ASSIGNMENT REQUEST message is considered as an example here. The message contains the address to be used in the transport layer and the ID of the association between the RAB and the corresponding transport bearer.


UP Mode Versions Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the versions for the selected Iu plane mode that are required and ed by the CN.

UP Mode Versions

uP-ModeVersions: Indicates the versions of the Iu plane mode that are required and ed by the CN. The RELOCATION REQUEST message is considered as an example here. This message indicates that the version of the Iu plane mode is 00 03.

Reference Standards For details, see 9.2.1.19 "UP Mode Versions" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Plane Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Contains the required plane mode and plane node versions.

PlaneInformation: Indicates the Plane Information IE, which contains the following information: Plane Information

1. Plane Mode: Indicates the plane mode. For details, see Plane Mode. 2. UP Mode Versions: Indicates the versions for the selected Iu plane mode that are required and ed by the CN. For details, see UP Mode Versions. The RELOCATION REQUEST message is considered as an example here. In this example, PlaneMode is 1, which indicates that the plane mode is -mode-for-predefined-SDUsizes, and uP-ModeVersions is 00 03, which indicates the plane node version ed by the CN is 00 03.


Plane Mode Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the mode of the requested operation of the Iu plane.

Plane Mode

PlaneMode: Indicates the mode of the requested operation of the Iu plane. The RELOCATION REQUEST message is considered as an example here. In this example, PlaneMode is 1, which indicates that the mode of the requested operation of the Iu plane is -mode-for-predefinedSDE-size.

Reference Standards For details, see 9.2.1.18 " Plane Mode" in 3rd Generation Partnership Project (3GPP) TS25413-801. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

End Of CSFB Description of the IE Reference Standards Description of the IE Information Description Element (IE) Indicates that the radio connection is established in a circuit switched fallback (CSFB) procedure.

End Of CSFB

End Of CSFB: Indicates that a CSFB procedure is complete. An IU_RELEASE_COMMAND message is used as an example. Reference Standards For details, see 9.2.1.111 in 25413-a70. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

C/D Interface Protocol Description of C/D Interface Protocol Description of the Common Part of Messages Description of MSRN Management Messages Description of Location Management Messages Description of Subscriber Data Management Messages Description of Authentication Messages Description of SMS Management Messages Description of SS Management Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of C/D Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC interworks with the HLR. In this networking, the MSC/VLR communicates with the HLR through Mobile Application Part (MAP). Figure 1 shows the application of the C/D interface protocol.

Figure 1 Application of the C/D interface protocol Protocol Stack Figure 2 through Figure 4 show the protocol stack of the C/D interface. Figure 2 Protocol stack of the C/D interface (non-peer-to-peer M3UA networking)

Figure 3 Protocol stack of the C/D interface (peer-to-peer M3UA networking)

Figure 4 Protocol stack of the C/D interface (M2UA networking)

The MAP messages are encoded in the ASN.1 format and encapsulated in the data of Transaction Capability Application Part (TCAP) messages. Figure 5 shows the message structure. Figure 5 MAP message structure

Message List Table 1 List of common C/D interface messages Message MAP_SEND_ROUTING_INFORMATION_REQ MAP_SEND_ROUTING_INFORMATION_CNF

MAP_PROVIDE_ROAMING_NUMBER_IND

MAP_PROVIDE_ROAMING_NUMBER_RSP MAP_UPDATE_LOCATION_REQ MAP_UPDATE_LOCATION_CNF MAP_CANCEL_LOCATION_IND

MAP_CANCEL_LOCATION_RSP

Direction Function

MSC/VLR- This message is sent >HLR routing information of This message is sent HLRacknowledge the >MSC/VLR MAP_SEND_ROUTIN This message is sent HLRstation roaming numb >MSC/VLR MSC/VLR. This message is sent MSC/VLRacknowledge the >HLR MAP_PROVIDE_ROA MSC/VLR- This message is sent >HLR request the location u This message is sent HLRacknowledge the MAP >MSC/VLR message. HLRThis message is sent >MSC/VLR cancel a location upda This message is sent MSC/VLR- acknowledge the MAP

>HLR

message.

HLRThis message is sent >MSC/VLR insert the subscriber d This message is sent MSC/VLRMAP_INSERT_SUBSCRIBER_DATA_RSP acknowledge the >HLR MAP_INSERT_SUBS This message is sent MSC/VLRMAP_PURGE_MS_REQ location information of >HLR deletes the subscribe HLRThis message is sent MAP_PURGE_MS_CNF >MSC/VLR acknowledge the MAP MSC/VLR- This message is sent MAP_SEND_AUTHENTICATION_INFO_REQ >HLR authentication set from This message is sent HLRMAP_SEND_AUTHENTICATION_INFO_CNF acknowledge the >MSC/VLR MAP_SEND_AUTHEN MSC/VLR- This message is sent MAP_AUTHENTICATION_FAILURE_REPORT_REQ >HLR report the authenticat This message is sent HLRacknowledge the MAP_AUTHENTICATION_FAILURE_REPORT_CNF >MSC/VLR MAP_AUTHENTICATI message. MSC/VLR- This message is sent MAP_READY_FOR_SHORT_MESSAGE_REQ >HLR of the subscriber reac This message is sent HLRMAP_READY_FOR_SHORT_MESSAGE_CNF acknowledge the >MSC/VLR MAP_READY_FOR_S HLRThis message is sent MAP_PROVIDE_SUBSCRIBER_INFO_IND >MSC/VLR information of the sub This message is sent MSC/VLRMAP_PROVIDE_SUBSCRIBER_INFO_RSP acknowledge the >HLR MAP_PROVIDE_SUB This message is sent MSC/VLRMAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ unstructured supplem >HLR operation from the HL This message is sent HLRacknowledge the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_CNF >MSC/VLR MAP_PROCESS_UN message. HLRThis message is sent MAP_UNSTRUCTURED_SS_REQUEST_IND MAP_INSERT_SUBSCRIBER_DATA_IND

MAP_UNSTRUCTURED_SS_REQUEST_RSP

MAP_UNSTRUCTURED_SS_NOTIFY_IND MAP__SS_REQ MAP__SS_CNF MAP_ACTIVATE_SS_REQ MAP_ACTIVATE_SS_CNF MAP_DEACTIVATE_SS_REQ MAP_DEACTIVATE_SS_CNF MAP_INTERROGATE_SS_REQ MAP_INTERROGATE_SS_CNF MAP_ERASE_SS_REQ MAP_ERASE_SS_CNF

>MSC/VLR the HLR) to request th MSC/VLR- This message is sent acknowledge the >HLR MAP_UNSTRUCTURE

This message is sent HLRthe HLR) to request a >MSC/VLR subscriber, in connect MSC/VLR- This message is sent >HLR data related t HLRThis message is sent >MSC/VLR acknowledge the MAP MSC/VLR- This message is sent >HLR activate a supplement HLRThis message is sent >MSC/VLR acknowledge the MAP MSC/VLR- This message is sent >HLR deactivate a suppleme HLRThis message is sent >MSC/VLR acknowledge the MAP MSC/VLR- This message is sent >HLR interrogate a supplem This message is sent HLRacknowledge the MAP >MSC/VLR message. MSC/VLR- This message is sent >HLR supplementary service HLRThis message is sent >MSC/VLR acknowledge the MAP

Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Reference Standards Table 1 IEs carried in the common part of messages Information Element Description (IE) Identifies a Mobile Application Part (MAP) dialog. Dialogue ID

The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, ie-dialogue-id is 0x40a. Identifies the functions of messages. It corresponds to the operation code in the Transaction Capability Application Part (TCAP) component.

Operation code The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, ie-mapoperation-code is send-routing-information. Reference Standards For details, see 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of MSRN Management Messages MAP_SEND_ROUTING_INFORMATION_REQ MAP_SEND_ROUTING_INFORMATION_CNF MAP_PROVIDE_ROAMING_NUMBER_IND MAP_PROVIDE_ROAMING_NUMBER_RSP Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_ROUTING_INFORMATION_REQ Message Function Associated IEs Reference Standards Message Function The MAP_SEND_ROUTING_INFORMATION_REQ message is sent by the GMSC to request the routing information of the callee from the HLR. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_ROUTING_INFORMATION_REQ message

Associated IEs Information Element (IE) Invoke Id

Description Uniquely identifies an operation in a Mobile Application Part (MAP) dialogue.

For details, see Invoke Id. Interrogation Type

Indicate the interrogation type. For details, see Interrogation Type.

GMSC or GSM service control function (gsmSCF) Address

Indicates the address of the GMSC or the gsmSCF. For details, see GMSC or gsmSCF Address.

Mobile Station International integrated Indicates the MSISDN of the subscriber. services digital network For details, see MSISDN. (ISDN) Number (MSISDN) Network Signal Info

Indicates the network signal information. For details, see Network Signal Info.

ed Customized Applications for Mobile Indicates which phases of CAMEL are ed in the VLR. network Enhanced Logic For details, see ed CAMEL Phases. (CAMEL) Phases Suppress terminating CAMEL subscription information (T-CSI)

Indicates whether to suppress the T-CSI information. For details, see Suppress T-CSI.

Suppression of Announcement

Indicates whether to suppress the announcements. For details, see Suppression of Announcement.

Call Reference Number

Indicates the call reference number. For details, see Call Reference Number.

Forwarding Reason

Indicates the reason for which the call is to be forwarded For details, see Forwarding Reason.

Number of Forwarding

Indicates the number of times a call is forwarded. For details, see Number of Forwarding.

Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of MSRN Management Messages Huawei Proprietary and Confidential


MAP_SEND_ROUTING_INFORMATION_CNF Message Function Associated IEs Reference Standards Message Function The MAP_SEND_ROUTING_INFORMATION_CNF message is sent by the HLR to the GMSC to acknowledge the MAP_SEND_ROUTING_INFORMATION_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_ROUTING_INFORMATION_CNF message

Associated IEs


Description

Invoke Id

Uniquely identifies an operation in a Mobile Application Part (MAP) dialogue. For details, see Invoke Id.

Mobile Station International ISDN Number (MSISDN)

Indicates the MSISDN of the subscriber. For details, see MSISDN.

ed Customized Applications for Mobile Indicates which phases of CAMEL are ed in the VLR. network Enhanced Logic For details, see ed CAMEL Phases. (CAMEL) Phases mobile station roaming number (MSRN)

Indicates the roaming number. For details, see MSRN.

Forwarding Data

Indicates the call forwarding data. For details, see Forwarding Data.

visited mobile switching Indicates the address of the VMSC. center (VMSC) address For details, see address of the VMSC. Location Information

Indicates the location information. For details, see Location Information.

Subscriber State

Indicates the status of the subscriber. For details, see Subscriber State.

Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of MSRN Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROVIDE_ROAMING_NUMBER_IND Message Function Associated IEs Reference Standards Message Function The MAP_PROVIDE_ROAMING_NUMBER_IND message is sent by the HLR to obtain the mobile station roaming number (MSRN) from the terminating MSC. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROVIDE_ROAMING_NUMBER_IND message


Description

Invoke Id


Indicates the IMSI of the subscriber. international mobile subscriber identity (IMSI) For details, see IMSI. Mobile Station International ISDN Number (MSISDN)

Indicates the MSISDN of the subscriber. For details, see MSISDN.

GSM Bearer Capability

Indicates the GSM bearer capability. For details, see GSM Bearer Capability.

Network Signal Info

Indicates the network signal information. For details, see Network Signal Info.

Suppression Of Announcement

Indicates whether to suppress the announcements. For details, see Suppression of Announcement.

Call Reference Number

Indicates the call reference number. For details, see Call Reference Number.

GMSC Address

Indicates the address of the GMSC. For details, see GMSC Address.

Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of MSRN Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROVIDE_ROAMING_NUMBER_RSP Message Function Associated IEs Reference Standards Message Function The MAP_PROVIDE_ROAMING_NUMBER_RSP message is sent by the terminating VLR to the HLR to acknowledge the MAP_PROVIDE_ROAMING_NUMBER_IND message. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROVIDE_ROAMING_NUMBER_RSP message


Description

Invoke Id


Roaming Number

Indicates the roaming number. For details, see Roaming Number.

Indicates that the MAP_RELEASE_RESOURCES service is ReleaseResourcesed ed at the visited mobile switching center (VMSC). For details, see ReleaseResourcesed. error

Indicator the error. For details, see error.

Provider error

Indicates a protocol-related error. For details, see Provider error.

Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of MSRN Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Location Management Messages MAP_UPDATE_LOCATION_REQ MAP_UPDATE_LOCATION_CNF MAP_CANCEL_LOCATION_IND MAP_CANCEL_LOCATION_RSP Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_UPDATE_LOCATION_REQ Message Function Associated IEs Reference Standards Message Function The MAP_UPDATE_LOCATION_REQ message is sent by the MSC/VLR to update the location information in the HLR. Figure 1 shows the main IEs of the message. Figure 1 MAP_UPDATE_LOCATION_REQ message


Invoke Id


For details, see Invoke Id. Indicates the IMSI of the subscriber. international mobile subscriber identity (IMSI) For details, see IMSI. MSC Address

Indicates the MSC number involved when the location information of the subscriber is updated. For details, see MSC Address.

VLR number

Indicates the VLR number involved when the location information of the subscriber is updated. For details, see VLR number.

ed Customized Applications for Mobile Indicates which phases of CAMEL are ed in the VLR. network Enhanced Logic For details, see ed CAMEL Phases. (CAMEL) Phases Reference Standards For details, see 8.1.2 "MAP_UPDATE_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Location Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_UPDATE_LOCATION_CNF Message Function Associated IEs Reference Standards Message Function The MAP_UPDATE_LOCATION_CNF message is sent by the HLR to the VLR to acknowledge the MAP_UPDATE_LOCATION_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_UPDATE_LOCATION_CNF message

Associated IEs Information Element

(IE)

Description

Invoke Id


HLR number

Indicates the integrated services digital network (ISDN) number of an HLR that processes the location update. For details, see HLR number.

Reference Standards For details, see 8.1.2 "MAP_UPDATE_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Location Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_CANCEL_LOCATION_IND Message Function Associated IEs Reference Standards Message Function The MAP_CANCEL_LOCATION_IND message is sent by the HLR to instruct the VLR to delete the specified subscriber data. Figure 1 shows the main IEs of the message. Figure 1 MAP_CANCEL_LOCATION_IND message


Description Uniquely identifies an operation in a Mobile Application Part

Invoke Id

(MAP) dialogue. For details, see Invoke Id.

Indicates the IMSI of the subscriber. international mobile subscriber identity (IMSI) For details, see IMSI. Cancellation Type

Indicates the reason of location cancellation. For details, see Cancellation Type.

Reference Standards For details, see 8.1.3 "MAP_CANCEL_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Location Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_CANCEL_LOCATION_RSP Message Function Associated IEs Reference Standards Message Function The MAP_CANCEL_LOCATION_RSP message is sent by the VLR to the HLR to acknowledge the MAP_CANCEL_LOCATION_IND message. Figure 1 shows the main IEs of the message. Figure 1 MAP_CANCEL_LOCATION_RSP message


Description

Invoke Id


Reference Standards For details, see 8.1.3 "MAP_CANCEL_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Location Management Messages


Description of Subscriber Data Management Messages MAP_INSERT_SUBSCRIBER_DATA_IND MAP_INSERT_SUBSCRIBER_DATA_RSP MAP_PURGE_MS_REQ MAP_PURGE_MS_CNF Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_INSERT_SUBSCRIBER_DATA_IND Message Function Associated IEs Reference Standards Message Function The MAP_INSERT_SUBSCRIBER_DATA_IND message is sent by HLR to insert the subscriber data to the VLR. Figure 1 shows the main IEs of the message. Figure 1 MAP_INSERT_SUBSCRIBER_DATA_IND message


Description

Invoke Id


international mobile subscriber identity (IMSI)

Indicates the IMSI of the subscriber. For details, see IMSI.

Mobile Station International Indicates the MSISDN of the subscriber. ISDN Number (MSISDN) For details, see MSISDN. Category

Indicates the subscriber category. For details, see Category.

Subscriber Status

Indicates the status of the subscriber. For details, see Subscriber Status.

Bearer service List

Indicates the bearer service capability. For details, see Bearer service List.

Teleservice List

Indicates the teleservice capability. For details, see Teleservice List.

Forwarding information List

Indicates the call forwarding data of the subscriber. For details, see Forwarding information List.

Call barring information List

Indicates the call barring information. For details, see Call barring information List.

Closed group (CUG) information List

Indicates the CUG information. For details, see CUG information List.

SS-Data List

Indicates the SS-Data information. For details, see SS-Data List.

enhanced multi-level Indicates the eMLPP subscription data. precedence and preemption (eMLPP) Subscription Data For details, see eMLPP Subscription Data. MC-Subscription Data

Indicates the multicard service (MC) subscription data. For details, see MC-Subscription Data.

Operator Determined Barring General data

Indicates all the Operator Determined Barring categories that may be applied to a subscriber ed in any public land mobile network (PLMN). For details, see Operator Determined Barring General data.

Operator Determined Barring home public land mobile network (HPLMN) data

Indicates all the Operator Determined Barring categories that may be applied only to a subscriber ed in the HPLMN. For details, see Operator Determined Barring HPLMN data. Indicates the roaming restriction for the features that are not

Roaming Restriction Due To ed. Uned Feature For details, see Roaming Restriction Due To Uned Feature. Regional Subscription Data

Indicates the regional subscription data. For details, see Regional Subscription Data.

VLR Customized Indicates the CAMEL subscription information. Applications for Mobile network Enhanced Logic For details, see VLR CAMEL Subscription Info. (CAMEL) Subscription Info Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Subscriber Data Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_INSERT_SUBSCRIBER_DATA_RSP Message Function Associated IEs Reference Standards Message Function The MAP_INSERT_SUBSCRIBER_DATA_RSP message is sent by the VLR to the HLR to acknowledge the MAP_INSERT_SUBSCRIBER_DATA_IND message. Figure 1 shows the main IEs of the message. Figure 1 MAP_INSERT_SUBSCRIBER_DATA_RSP message


Description

Invoke Id


Bearer service List

Indicates the bearer service capability. For details, see Bearer service List.

Teleservice List

Indicates the teleservice capability. For details, see Teleservice List.


Indicates all the Operator Determined Barring categories that may be applied to a subscriber ed in any public land mobile network (PLMN).

For details, see Operator Determined Barring General data. Regional Subscription Response

Indicates the regional subscription response. For details, see Regional Subscription Response.

ed Customized Applications for Mobile network Enhanced Logic (CAMEL) Phases

Indicates which phases of CAMEL are ed in the VLR. For details, see ed CAMEL Phases.

Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Subscriber Data Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PURGE_MS_REQ Message Function Associated IEs Reference Standards Message Function The MAP_PURGE_MS_REQ message is sent by the VLR to instruct the HLR to remove the location information of the specified subscriber. This message contains the international mobile subscriber identity (IMSI) of the subscriber. Figure 1 shows the main IEs of the message. Figure 1 MAP_PURGE_MS_REQ message


Description

Invoke Id


IMSI


VLR number

Indicates the VLR number of the subscriber. For details, see VLR number.

Reference Standards For details, see 8.1.6 "MAP_PURGE_MS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Subscriber Data Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PURGE_MS_CNF Message Function Associated IEs Reference Standards Message Function The MAP_PURGE_MS_CNF is sent by the HLR to the VLR to acknowledge the MAP_PURGE_MS_REQ message. Figure 1 shows the main IEs of the message.

Figure 1 MAP_PURGE_MS_CNF message Associated IEs Information Element (IE)

Description

Invoke Id


Reference Standards For details, see 8.1.6 "MAP_PURGE_MS service" in 3rd Generation Partnership Project (3GPP) TS29002-870.

Parent topic: Description of Subscriber Data Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Authentication Messages MAP_SEND_AUTHENTICATION_INFO_REQ MAP_SEND_AUTHENTICATION_INFO_RSP MAP_AUTHENTICATION_FAILURE_REPORT_REQ MAP_AUTHENTICATION_FAILURE_REPORT_RSP Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_AUTHENTICATION_INFO_REQ Message Function Associated IEs Reference Standards Message Function The MAP_SEND_AUTHENTICATION_INFO_REQ message is sent by the VLR to request authentication sets from the HLR. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_AUTHENTICATION_INFO_REQ message


Description

Invoke Id


International mobile Indicates the IMSI number of the subscriber. subscriber identity For details, see IMSI. (IMSI) Number of requested vectors

Indicates the number of authentication sets to be requested. For details, see Number of requested vectors.

Requesting node type

Indicates the type of requesting node. For details, see Requesting node type.

Indicates if the VLR allows segmentation of the response at MAP Segmentation level. prohibited indicator For details, see Segmentation prohibited indicator. Reference Standards For details, see 8.5.2 "MAP_SEND_AUTHENTICATION_INFO service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Authentication Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_AUTHENTICATION_INFO_RSP Message Function Associated IEs Reference Standards Message Function The MAP_SEND_AUTHENTICATION_INFO_RSP message is sent by the HLR to the VLR to acknowledge the MAP_SEND_AUTHENTICATION_INFO_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_AUTHENTICATION_INFO_RSP message


Description

Invoke Id


AuthenticationSetList

Indicates a list of authentication sets. For details, see AuthenticationSetList.

Reference Standards For details, see 8.5.2 "MAP_SEND_AUTHENTICATION_INFO service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Authentication Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_AUTHENTICATION_FAILURE_REPORT_REQ Message Function Associated IEs Reference Standards Message Function The MAP_AUTHENTICATION_FAILURE_REPORT_REQ message is sent by the VLR to inform the HLR of the authentication failure. Figure 1 shows the main IEs of the message. Figure 1 MAP_AUTHENTICATION_FAILURE_REPORT_REQ message

Associated IEs Information Description Element (IE)

Invoke Id


international Indicates the IMSI of the subscriber. mobile subscriber For details, see IMSI. identity (IMSI) Failure cause

Indicates the reason for which an authentication failure occurs. For details, see Failure cause.

Re-attempt

Indicates whether a failure occurs in a normal authentication attempt or in an authentication re-attempt. For details, see Re-attempt.

Access Type

Indicates the access type. For details, see Access Type.

Rand

Indicates the specific AV that fails authentication. For details, see Rand.

VLR number

Indicates the VLR number of the subscriber. For details, see VLR number.

Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Authentication Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_AUTHENTICATION_FAILURE_REPORT_RSP Message Function Associated IEs Reference Standards Message Function The MAP_AUTHENTICATION_FAILURE_REPORT_RSP message is sent by the HLR to the VLR to acknowledge the MAP_AUTHENTICATION_FAILURE_REPORT_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_AUTHENTICATION_FAILURE_REPORT_RSP message

Associated IEs Information Description Element (IE) Invoke Id


Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Authentication Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of SMS Management Messages MAP_READY_FOR_SHORT_MESSAGE_REQ MAP_READY_FOR_SHORT_MESSAGE_RSP Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_READY_FOR_SHORT_MESSAGE_REQ Message Function Associated IEs Reference Standards Message Function The MAP_READY_FOR_SHORT_MESSAGE_REQ message is sent by the MSC/VLR to inform the HLR that the MS is reachable or the MS memory is available. Figure 1 shows the main IEs of the message. Figure 1 MAP_READY_FOR_SHORT_MESSAGE_REQ message



For details, see Invoke Id. International Indicates the IMSI of the subscriber. mobile subscriber For details, see IMSI. identity (IMSI) Temporary mobile Indicates the TMSI of the subscriber. subscriber identifier (TMSI) For details, see TMSI. Alert Reason

Indicates the alerting reason. For details, see Alert Reason.

Alert Reason Indicator

Indicates the alerting reason indicator. For details, see Alert Reason Indicator.

Reference Standards For details, see 12.4 "MAP-READY-FOR-SM service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SMS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_READY_FOR_SHORT_MESSAGE_RSP Message Function Associated IEs Reference Standards Message Function The MAP_READY_FOR_SHORT_MESSAGE_RSP message sent by the MSC/VLR to the HLR to acknowledge the MAP_READY_FOR_SHORT_MESSAGE_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_READY_FOR_SHORT_MESSAGE_RSP message


Description

Invoke Id


Reference Standards For details, see 12.4 "MAP-READY-FOR-SM service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SMS Management Messages Huawei Proprietary and Confidential


Description of SS Management Messages MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_CNF MAP_PROVIDE_SUBSCRIBER_INFO_IND MAP_PROVIDE_SUBSCRIBER_INFO_RSP MAP_UNSTRUCTURED_SS_REQUEST_IND MAP_UNSTRUCTURED_SS_REQUEST_RSP MAP_UNSTRUCTURED_SS_NOTIFY_IND MAP__SS_REQ MAP__SS_RSP MAP_ACTIVATE_SS_REQ MAP_ACTIVATE_SS_RSP MAP_DEACTIVATE_SS_REQ MAP_DEACTIVATE_SS_RSP MAP_INTERROGATE_SS_REQ MAP_INTERROGATE_SS_RSP MAP_ERASE_SS_REQ MAP_ERASE_SS_RSP Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ Message Function Associated IEs Reference Standards Message Function This message is sent between the MSC and the VLR, between the VLR and the HLR, between the HLR and GSM service control function (gsmSCF) and between the HLR and HLR to relay information to allow unstructured supplementary service operation. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ message


Description

Invoke Id


Unstructured supplementary service data (USSD) Data Coding Scheme

Indicates the coding scheme of the USSD data. For details, see USSD Data Coding Scheme.

USSD String

Indicates the USSD character string. For details, see USSD String.

Mobile Station International ISDN Indicates the MSISDN of the subscriber. Number For details, see MSISDN. (MSISDN) Reference Standards For details, see 11.9 "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_CNF Message Function Associated IEs Message Function The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_CNF message is sent to acknowledge the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ message and contains the unstructured supplementary service data (USSD) operation result. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_CNF message


Description

Invoke Id


USSD Data Coding Scheme


USSD String


Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROVIDE_SUBSCRIBER_INFO_IND Message Function Associated IEs Reference Standards Message Function The MAP_PROVIDE_SUBSCRIBER_INFO_IND message (that is, the PSI message) is sent by the HLR to request the current location information of the subscriber from the MSC/VLR. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROVIDE_SUBSCRIBER_INFO_IND message


Description

Invoke Id


International Indicates the IMSI of the subscriber. mobile subscriber For details, see IMSI. identity (IMSI) Requested information

Indicates the information to be requested. For details, see Requested information.

Reference Standards For details, see 8.3.4 "Provide Subscriber Info" in 3rd Generation Partnership Project (3GPP) TS23018-810. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROVIDE_SUBSCRIBER_INFO_RSP Message Function Associated IEs Reference Standards Message Function The MAP_PROVIDE_SUBSCRIBER_INFO_RSP message is sent by the MSC to the HLR to acknowledge the MAP_PROVIDE_SUBSCRIBER_INFO_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROVIDE_SUBSCRIBER_INFO_RSP message


Invoke Id


For details, see Invoke Id. Location information

Indicate the subscription location information. For details, see Location Information.

Reference Standards For details, see 8.3.5 "Provide Subscriber Info ack" in 3rd Generation Partnership Project (3GPP) TS23018-810. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_UNSTRUCTURED_SS_REQUEST_IND Message Function Associated IEs Reference Standards Message Function The MAP_UNSTRUCTURED_SS_REQUEST_IND message is sent by the invoking entity (for example, the HLR) to request the information from the mobile subscriber, in connection with the unstructured supplementary service data (USSD) service. This message is sent between the GSM service control function (gsmSCF) and the HLR, the HLR and the VLR, and between the VLR and the MSC. Figure 1 shows the main IEs of the message. Figure 1 MAP_UNSTRUCTURED_SS_REQUEST_IND message


Description

Invoke Id




USSD String


Alerting Pattern

Indicates the alerting pattern. For details, see Alerting Pattern.

Reference Standards For details, see 11.10 "MAP_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_UNSTRUCTURED_SS_REQUEST_RSP Message Function Associated IEs Reference Standards Message Function The MAP_UNSTRUCTURED_SS_REQUEST_RSP message is sent to acknowledge the MAP_UNSTRUCTURED_SS_REQUEST_IND message and contains the unstructured supplementary service data (USSD) operation result. Figure 1 shows the main IEs of the message. Figure 1 MAP_UNSTRUCTURED_SS_REQUEST_RSP message


Description

Invoke Id




USSD String


Reference Standards For details, see 11.10 "MAP_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_UNSTRUCTURED_SS_NOTIFY_IND Message Function Associated IEs Reference Standards Message Function The MAP_UNSTRUCTURED_SS_NOTIFY_IND message is sent by the invoking entity (for example, the HLR) to request a notification to be sent to the mobile subscriber, in connection with the unstructured supplementary service data (USSD) service. This message is sent between the GSM service control function (gsmSCF) and the HLR, the HLR and the VLR, and between the VLR and the MSC. Figure 1 shows the main IEs of the message. Figure 1 MAP_UNSTRUCTURED_SS_NOTIFY_IND message


Description Uniquely identifies an operation in a Mobile Application Part (MAP)

Invoke Id

dialogue. For details, see Invoke Id.



USSD String


Alerting Pattern


Reference Standards For details, see 11.11 "MAP_UNSTRUCTURED_SS_NOTIFY service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP__SS_REQ Message Function Associated IEs Reference Standards Message Function The MAP__SS_REQ message is sent by the MSC/VLR to the HLR to data related to a supplementary service. Figure 1 shows the main IEs of the message. Figure 1 MAP__SS_REQ message



For details, see Invoke Id. SS-Code

Indicates the supplementary service code ed by the subscriber. For details, see SS-Code.

Basic service

Indicates the basic service ed by the subscriber. For details, see Basic service.

Forwarded-to number with subaddress

Indicates the forwarded-to number which optionally includes a subaddress. For details, see Forwarded-to number with subaddress.

No reply condition Indicates the duration at which the call is not answered. time For details, see No reply condition time. EMLPP default priority

Indicates the enhanced multi-level precedence and preemption (eMLPP) default priority level. For details, see EMLPP default priority.

Long FTN ed

Indicates that the mobile station s long forwarded-to numbers. For details, see Long FTN ed.

Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP__SS_RSP Message Function Associated IEs Reference Standards Message Function The MAP__SS_RSP message is sent by the HLR to the VLR to acknowledge the MAP__SS_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP__SS_RSP message

Associated IEs


Description

Invoke Id


Forwarding information

Indicates the call forwarding data. For details, see Forwarding information.

EMLPP default priority

Indicates the enhanced multi-level precedence and preemption (eMLPP) default priority level. For details, see EMLPP default priority.

Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_ACTIVATE_SS_REQ Message Function Associated IEs Reference Standards Message Function The MAP_ACTIVATE_SS_REQ message is sent by the MSC/VLR to the HLR to activate a supplementary service. Figure 1 shows the main IEs of the message.

Figure 1 MAP_ACTIVATE_SS_REQ message Associated IEs Information Element (IE)

Description

Invoke Id


SS-Code


Basic service


Long FTN ed


Reference Standards For details, see 11.3 "MAP_ACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_ACTIVATE_SS_RSP Message Function Associated IEs Reference Standards Message Function The MAP_ACTIVATE_SS_RSP message is sent by the HLR to the MSC/VLR to acknowledge the MAP_ACTIVATE_SS_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_ACTIVATE_SS_RSP message


Description

Invoke Id




Call barring

Indicates the call barring information.

information

For details, see Call barring information.

SS-Data

Indicates the supplementary service data. For details, see SS-Data.

Reference Standards For details, see 11.3 "MAP_ACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_DEACTIVATE_SS_REQ Message Function Associated IEs Reference Standards Message Function The MAP_DEACTIVATE_SS_REQ message is sent by the MSC/VLR to the HLR to deactivate a supplementary service. Figure 1 shows the main IEs of the message.

Figure 1 MAP_DEACTIVATE_SS_REQ message Associated IEs Information Element (IE)

Description

Invoke Id


SS-Code

Indicates the supplementary service code to be ed by the subscriber. For details, see SS-Code.

Basic service

Indicates the basic service to be ed by the subscriber. For details, see Basic service.

Reference Standards For details, see 11.4 "MAP_DEACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_DEACTIVATE_SS_RSP Message Function Associated IEs Reference Standards Message Function The MAP_DEACTIVATE_SS_RSP message is sent by the HLR to acknowledge the MAP_DEACTIVATE_SS_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_DEACTIVATE_SS_RSP message


Description

Invoke Id




Call barring information

Indicates the call barring information. For details, see Call barring information.

SS-Data

Indicates the supplementary service data. For details, see SS-Data.

Reference Standards For details, see 11.4 "MAP_DEACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_INTERROGATE_SS_REQ Message Function Associated IEs Reference Standards Message Function The MAP_INTERROGATE_SS_REQ message is sent by the MSC/VLR to the HLR to interrogate the supplementary service. Figure 1 shows the main IEs of the message. Figure 1 MAP_INTERROGATE_SS_REQ message


Description

Invoke Id


SS-Code


Long FTN ed


Basic service


Reference Standards For details, see 11.5 "MAP_INTERROGATE_SS service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_INTERROGATE_SS_RSP Message Function Associated IEs Reference Standards Message Function The MAP_INTERROGATE_SS_RSP message is sent by the HLR to acknowledge the MAP_INTERROGATE_SS_REQ message. It carries the interrogateSS operation result. Figure 1 shows the main IEs of the message.

Figure 1 MAP_INTERROGATE_SS_RSP message Associated IEs Information Element (IE)

Description

Invoke Id


SS-Status

Indicates the status of the supplementary service. For details, see SS-Status.

Basic service Group LIST

Indicates a list of basic service groups. For details, see Basic service Group LIST.

Forwarding feature Indicates a list of call forwarding features. LIST For details, see Forwarding feature LIST. Calling line Indicate the CLI restriction information. identification (CLI) For details, see CLI restriction Info. restriction Info Enhanced multilevel precedence and preemption (EMLPP) Info

Indicates the EMLPP information. For details, see EMLPP Info.

Reference Standards For details, see 11.5 "MAP_INTERROGATE_SS service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_ERASE_SS_REQ Message Function Associated IEs Reference Standards Message Function The MAP_ERASE_SS_REQ message is sent by the MSC/VLR to delete the supplementary service data from the HLR. Figure 1 shows the main IEs of the message.

Figure 1 MAP_ERASE_SS_REQ message Associated IEs Information Element (IE)

Description

Invoke Id


SS-Code


Basic service


Reference Standards For details, see 11.2 "MAP_ERASE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_ERASE_SS_RSP Message Function Associated IEs Reference Standards Message Function The MAP_ERASE_SS_RSP message is sent by the HLR to acknowledge the MAP_ERASE_SS_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_ERASE_SS_RSP message


Description

Invoke Id


Forwarding

Indicates the call forwarding data.

information

For details, see Forwarding information.

Reference Standards For details, see 11.2 "MAP_ERASE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of SS Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Access Type Alert Reason Alert Reason Indicator Alerting Pattern AuthenticationSetList Basic service Basic service Group LIST Bearer service List Call barring information Call barring information List Call Reference Number Cancellation Type Category CLI restriction Info CUG information List EMLPP default priority EMLPP Info eMLPP Subscription Data Failure cause Forwarded-to number with subaddress Forwarding Data Forwarding feature LIST Forwarding information Forwarding information List Forwarding Reason GMSC Address

GMSC or gsmSCF Address GSM Bearer Capability HLR number IMSI Interrogation Type Invoke Id Location Information Long FTN ed MC-Subscription Data MSC Address MSC Number MSISDN MSRN Network Signal Info No reply condition time Number of Forwarding Number of requested vectors Operator Determined Barring General data Operator Determined Barring HPLMN data Provider error Rand Re-attempt Regional Subscription Data Regional Subscription Response ReleaseResourcesed Requested information Requesting node type Roaming Number

Roaming Restriction Due To Uned Feature Segmentation prohibited indicator SS-Code SS-Data SS-Data List SS-Status Subscriber State Subscriber Status ed CAMEL Phases Suppress T-CSI Suppression of Announcement Teleservice List TMSI error USSD Data Coding Scheme USSD String VLR CAMEL Subscription Info VLR number address of the VMSC Parent topic: C/D Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Access Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the access type. Values: call: Indicates basic calls. emergency call: Indicates emergency calls. location updating: Indicates the location update. supplementary service procedure: Indicates supplementary services. short message transfer: Indicates short messages.

Access Type

The MAP_AUTHENTICATION_FAILURE_REPORT_REQ message is considered as an example here. In this example, accessType is locationUpdating. Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Alert Reason Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason why the short message service center is alerted. Values: ms Present: Indicates that the MS is present or reachable. memoryAvaliable: Indicates that the MS has the available memory.

Alert Reason

The MAP_READY_FOR_SHORT_MESSAGE_REQ message is considered as an example here. In this example, alertReason is ms Present, which indicates the MS is present or reachable. Reference Standards For details, see 12.4 "MAP-READY-FOR-SM service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Alert Reason Indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the alerting reason is sent to the HLR due to general packet radio service (GPRS) activation.

Alert Reason Indicator

The MAP_READY_FOR_SHORT_MESSAGE_REQ message is considered as an example here. As long as the Alert Reason Indicator IE is contained, the alerting reason is sent to the HLR at the time of GPRS activation, regardless of the value of the Alert Reason Indicator IE.

Reference Standards For details, see 12.4 "MAP-READY-FOR-SM service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Alerting Pattern Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates an alerting level or alerting category. The meanings of the bits of the Alerting Pattern IE are as follows: Bits 8-5: reserved Bits 4 -3: Indicate the alerting level by 00 and the alerting range by 01 or 10. Bits 2-1: Indicate the alerting category.

Alerting Pattern

The MAP_UNSTRUCTURED_SS_REQUEST_IND message is considered as an example here. In this example, alertPattern is 00, which indicates the alerting level is 0. Reference Standards For details, see 11.10 "MAP_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AuthenticationSetList Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of authentication sets. Values: TripletList (for GSM authentication): The triplet list contains all the triplet authentication sets required by the VLR. QuintupletList (for Universal Mobile Telecommunications System (UMTS) authentication): The quintuplet list contains all the quintuplet authentication sets required by the VLR.

AuthenticationSetList

SEQUENCE consists of the following parts: rand: Indicates a random number used for authentication. It is used as an input field for the other fields of the authentication algorithm.

sres: Indicates the response to an authentication request. It is used by the network side to authenticate the subscriber. kc: Indicates the key used for ciphering data during the communication procedure. The MAP_SEND_AUTHENTICATION_INFO_RSP message is considered as an example here. In this example, rand is 27 E4 0A 15 AD 98 45 6A C3 41 70 4A D8 BA 86 2D; sres is 16 D3 87 07; kc is 00 04 5C CC DD AF 6A FD. Reference Standards For details, see 8.5.2 "MAP_SEND_AUTHENTICATION_INFO service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Basic service Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the basic services ed by the subscriber.

Basic service

bearerService teleservice The MAP__SS_REQ message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services; teleservice is allTeleservices, which indicates all the teleservices.

Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Basic service Group LIST Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates a list of basic service groups.

Basic service Group LIST The MAP__SS_RSP message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services. Reference Standards For details, see 11.5 "MAP_INTERROGATE_SS service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Bearer service List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of extensible bearer services.

Bearer service List

BEARER-SERVICE-04: Indicates a type of bearer service. The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. In this example, BEARER-SERVICE-04 is allAlternateSpeech-DataCDA, which indicates the allAlternateSpeechDataCDA is ed. Reference Standards

For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Call barring information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the call barring information of the subscriber.

Call barring information

SEQUENCE: Indicates a list of call barring information. bearerService The MAP_ACTIVATE_SS_RSP message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services. Reference Standards For details, see 11.3 "MAP_ACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Call barring information List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of extensible call barring information. It consists of the following subordinate IEs: ss-Code callBarringFeatureList

Call barring information List

ss-Code: Indicates the supplementary service code. SEQUENCE: Indicates a list of call barring information. The MAP-INSERT-SUBSCRIBER-DATA_IND message is considered as an example here. In this example, ss-Code is allSS, which indicates all the supplementary service codes. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


Call Reference Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a reference number allocated by the GMSC during a call.

Call Reference Number The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, callReferenceNumber is 17 10 5A 13 A0 74, which indicates that the call reference number is allocated by the GMSC. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cancellation Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason of location cancellation.

Cancellation Type

The MAP_CANCEL_LOCATION_REQ message is considered as an example here. In this example, cancellationType is subscriptionWithdraw, which indicates that the reason of location cancellation is that the related subscriber data is deleted.

Reference Standards For details, see 8.1.3 "MAP_CANCEL_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Category Description of the IE Reference Standards Description of the IE Information Element (IE)

Category

Description Indicates the subscriber categories. Invalid values include UNKNOWN, FRENCH, ENGLISH, GERMAN, RUSSIAN, SPANISH, SPECIAL1SPECIAL2, SPECIAL3, RESERVE, COMMON, SUPERIOR, DATACALL, TESTCALL, SPARE, PAYPHONE, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, COIN, 33, and 34 through 254. Category is generally set to COMMON and the meaning of each value can be determined by carriers. The MAP-INSERT-SUBSCRIBER-DATA_IND message is considered as an example here. In this example, category is 0A.

Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CLI restriction Info Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the CLI restriction information.

calling line identification (CLI) restriction Info

The MAP_INTERROGATE_SS_RSP message is considered as an example here. In this example, cliRestrictionOption is permanent, which indicates permanent restriction.

Reference Standards For details, see 11.5 "MAP_INTERROGATE_SS service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CUG information List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of CUG information. It includes: CUG-SubscriptionList CUG-FeatureList

Closed group (CUG) information List

cug-SubscriptionList: Indicates the CUG subscription information list. cug-index: Indicates the CUG index. cug-Interlock: Indicates the CUG interlock. intraCUG-Options: Indicates the internal CUG options. CUG-FeatureList: Indicates a list of CUG features. interCUG-Restrictions: Indicates the inter-CUG restrictions.

The MAP-INSERT-SUBSCRIBER-DATA_IND message is considered as an example here. In this example, cug-index is 0, which indicates that the CUG index is 0; cug-Interlock is 00 00 00 00, which indicates the CUG interlock information; intraCUG-Options is noCUG-Restriction, which indicates no CUG restriction; interCUGRestrictions is cug-only-facilities, which indicates that only the CUG device is used. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

EMLPP default priority Description of the IE Reference Standards Description of the IE Information Element (IE) Enhanced multi-level precedence and preemption (EMLPP) default priority

Description Indicates the default EMLPP priority level. The MAP__SS_REQ message is considered as an example here. In this example, defaultPriority is 0, which indicates the default priority level is 0.


EMLPP Info Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the EMLPP information.

Enhanced multi-level precedence and preemption (EMLPP) Info

maximumentitledPriority defaultPriority The MAP_INTERROGATE_SS_RSP message is considered as an example here. In this example, maximumentitledPriority is 0, which indicates the maximum priority level is 0; defaultPriority is 0, which indicates the default priority level is 0.


eMLPP Subscription Data Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the eMLPP subscription data, including:

Enhanced multi-level precedence and preemption (eMLPP) Subscription Data

maximumentitledPriority defaultPriority The MAP-INSERT-SUBSCRIBER-DATA_RSP message is considered as an example here. In this example, maximumentitledPriority is 0, which indicates the maximum priority level is 0; defaultPriority is 0, which indicates the default priority level is 0.


Failure cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason for which an authentication failure occurs. Values: Wrong response Wrong network signature

Failure cause

The MAP_INTERROGATE_SS_RSP message is considered as an example here. In this example, failureCause is wrongResponse. Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Forwarded-to number with subaddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the forwarded-to number.

Forwarded-to number with subaddress

nature-of-address-indicator number The MAP__SS_REQ message is considered as an example here. In this example, nature-of-address-indicator is international-number, which indicates that the number address nature is international; number is 13907556789, which indicates the forwarded-to number is 13907556789.


Forwarding Data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the call forwarding data, including:

Forwarding Data forwardedToNumber nature-of-address-indicator content forwardingOptions forwarding-reason The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, nature-of-addressindicator is international-number, which indicates that the number address nature is international; content is 8613912340030, which indicates the forwarded-to number is 13912340030; forwardingreason is ms-not-reachable, which indicates that the call is forwarded at the reason of subscriber unreachable. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870.


Forwarding feature LIST Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of call forwarding features. A list of one or more forwarding features is returned by the responder when the interrogation request applied to the call forwarding supplementary service.

Forwarding feature LIST

bearerService forwardedToNumber nature-of-address-indicator content The MAP_INTERROGATE_SS_RSP message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services; nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 8613912340030, which indicates the forwarded-to number is 8613912340030.


Forwarding information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the call forwarding information returned by the HLR after the subscriber successfully s the call forwarding service.


forwardindFeatureList bearerService forwardedToNumber nature-of-address-indicator content forwardingOptions forwarding-reason The MAP__SS_RSP message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services; nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 8613912340030, which indicates the forwarded-to number is 8613912340030; forwarding-reason is ms-not-reachable, which indicates that the call is forwarded at the reason of subscriber unreachable. Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Forwarding information List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of call forwarding information.

Forwarding information List

forwardindFeatureList

bearerService forwardedToNumber nature-of-address-indicator content forwardingOptions forwarding-reason The MAP_INSERT_SUBSCRIBER_DATA_RSP message is considered as an example here. In this example, bearerService is allBearerServices, which indicates all the bearer services; nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 8613912340030, which indicates the forwarded-to number is 8613912340030; forwarding-reason is ms-not-reachable, which indicates that the call is forwarded at the reason of subscriber unreachable. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Forwarding Reason Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason for which the call is to be forwarded. Values:

Forwarding Reason

Busy subscriber Mobile subscriber not reachable No subscriber reply Call forwarded unconditionally The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, forwardingReason is notReachable, which indicates that the call is forwarded because the subscriber is not reachable.

Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GMSC Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the address of the GMSC.

nature-of-address-indicator: Indicates the number address nature. content: Indicates the GMSC address.

GMSC Address

The MAP_PROVIDE_ROAMING_NUMBER_IND message is considered as an example here. In this example, nature-of-addressindicator is international-number, which indicates that the number address nature is international; content is 86139025, which indicates that the GMSC address is 86139025. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GMSC or gsmSCF Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates E.164 address of the GMSC or the gsmSCF. This parameter contains the gsmSCF address if the Customized Applications for Mobile network Enhanced Logic (CAMEL) service is invoked; otherwise, it is the GMSC address.

GMSC or GSM service control function (gsmSCF) Address

nature-of-address-indicator content The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, nature-of-addressindicator is international-number, which indicates that the number address nature is international; content is 86139025, which indicates that the GMSC address is 86139025.


GSM Bearer Capability Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the GSM bearer capability.

GSM Bearer Capability

protocolId signalInfo The MAP_PROVIDE_ROAMING_NUMBER_IND message is considered as an example here. In this example, protocolId is gsm0408 and signalInfo is 04 09 A1 B8 19 88 20 15 6B 00 88.

Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

HLR number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the HLR number that is used for location update. The updated location information of the subscriber is stored in the HLR.

HLR number

nature-of-address-indicator content The MAP_UPDATE_LOCATION_CNF message is considered as an example here. In this example, nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 861310751099, which indicates the HLR number is 861310751099.

Reference Standards For details, see 8.1.2 "MAP_UPDATE_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IMSI Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the IMSI number of the subscriber.

International mobile content subscriber identity (IMSI) The MAP_PROVIDE_ROAMING_NUMBER_IND message is considered as an example here. In this example, content is 460000000030183, which indicates the IMSI is 460000000030183. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Interrogation Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the interrogation type. Values: Basic call Forwarding

Interrogation Type

The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, interrogationType is basicCall, indicates that the interrogation type is basic call. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Invoke Id Description of the IE Reference Standards Description of the IE Information Element (IE)


Invoke Id

The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, invoke-ID is 0x4e, which indicates the invoking identifier of the MAP dialogue.


Location Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the location information of the subscriber.

Location Information

ageOfLocaltionInformation: Indicates the useful life of the location information. geographicalInformation: Indicates the geographical location information. vlr-number: Indicates the VLR number information. nature-of-address-indicator: Indicates the number address nature. content: Inidcates the VLR number. The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, ageOfLocaltionInformation is 0x0, which indicates that the useful life of the location information is 0; geographicalInformation is 10 00 00 00 00 00 00 00 00; nature-of-address-indicator is internationalnumber, which indicates that the number address nature is international; content is 861310751315.


Long FTN ed Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether to the long forwarded-to number.

The MAP__SS_REQ message is considered as an Long FTN ed example here. In this example, longFTN-ed is NULL. As long as the Long FTN ed IE is contained, the long forwardedto number is ed regardless of the value of the Long FTN ed IE. Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MC-Subscription Data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the subscription data related to the multicard service (MC) service, including:

MC-Subscription Data

nbrSB: Indicates the maximum number of parallel bearers that may be used as defined by the 's subscription. nbr: Indicates the maximum number of parallel bearers that may be used as defined by the at registration of the MC supplementary service (SS). The MAP_INSERT_SUBSCRIBER_DATA_RSP message is considered as an example here. In this example, nbrSB is 0x2 and nbr is 0x01. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs


MSC Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the MSC address.

nature-of-address-indicator content

MSC Address

The MAP_UPDATE_LOCATION_REQ message is considered as an example here. In this example, nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 861310751315, which indicates that the MSC address is 861310751315. Reference Standards For details, see 8.1.2 "MAP_UPDATE_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MSC Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of the MSC at which the subscriber resides.


MSC Number

The MAP_PROVIDE_ROAMING_NUMBER_IND message is considered as an example here. In this example, nature-of-addressindicator is international-number, which indicates that the number address nature is international; content is 86139025, which indicates that the MSC number is 86139025. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MSISDN Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the MSISDN of the subscriber.


nature-of-address-indicator content The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, nature-of-addressindicator is international-number. content is 8613912340183, which indicates the MSISDN is 8613912340183.


MSRN Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the MSRN allocated by the MSC serving the callee.

mobile station roaming number (MSRN)

content The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, content is 86139025399, which indicates the newly allocated MSRN. Generally, this MSRN is in the same number segment as the MSC/VLR number.


Network Signal Info Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the network signal information, including the bearer capability.

Network Signal Info protocolId: Indicates the protocol type. signalInfo: Indicates the bearer information. The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, protocolid is ets300102-1, which indicates the ETS-300102-1 protocol; signalInfo is 04 03 88 90 A6, which indicates the bearer information. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

No reply condition time Description of the IE Reference Standards Description of the IE Information Element (IE)

No reply condition time

Description Indicates the time at which the call is not answered. This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service. The MAP__SS_REQ message is considered as an example here. In this example, noReplyConditionTime is 0x05.


Number of Forwarding Description of the IE Reference Standards Description of the IE Information Element (IE)

Number of Forwarding

Description Indicates the number of times the incoming calls are forwarded. This parameter is present only when the callee has ed the call forwarding supplementary service. The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, numberOfForwarding is 0x01.


Number of requested vectors Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of authentication sets the new VLR is prepared to receive from the HLR.

Number of requested vectors

The MAP_SEND_AUTHENTICATION_INFO_REQ message is considered as an example here. In this example, numberOfRequestedVectors is 0x05.

Reference Standards For details, see 8.5.2 "MAP_SEND_AUTHENTICATION_INFO service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Operator Determined Barring General data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the Operator Determined Barring data that may be applied to a subscriber ed in any public land mobile network (PLMN).


The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation

Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Operator Determined Barring HPLMN data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the Operator Determined Barring data that may be applied only to a subscriber ed in the HPLMN.

Operator Determined Barring home public land mobile network (HPLMN) data The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Provider error Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a protocol-related error.

Provider error

The MAP_PROVIDE_ROAMING_NUMBER_IND message is considered as an example here. In this example, ie-provider-error is duplicated-invoke-id, which indicates the repeated invoking IDs exist.

Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Rand Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the random number used for authentication.

Rand

The MAP_AUTHENTICATION_FAILURE_REPORT_REQ message is considered as an example here. In this example, rand is 27 E4 0A 15 AD 98 45 6A C3 41 70 4A D8 BA 86 2D.

Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Re-attempt Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the failure occurs in a normal authentication attempt or in an authentication re-attempt.

Re-attempt

The MAP_AUTHENTICATION_FAILURE_REPORT_REQ message is considered as an example here. In this example, re-attempt is FALSE, which indicates that the failure occurs in a normal authentication attempt.

Reference Standards For details, see 8.5.3 "MAP_AUTHENTICATION_FAILURE_REPORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Regional Subscription Data Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the regional subscription area in which the subscriber is allowed to roam. Regional Subscription Data The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. In this example, regionalSubscriptionData is 00 00. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Regional Subscription Response Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the response to the regional subscription data. Values: Network Restriction, Too Many Zone Codes, Regional Subscription Not ed by the VLR or the SGSN, Zone Codes Conflict

Regional Subscription Response

The MAP_INSERT_SUBSCRIBER_DATA_RSP message is considered as an example here. In this example, regionalSubscriptionResponse is networkNodeAreaRestricted, indicates the reason for inserting the regional subscription data.


ReleaseResourcesed Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the MAP_RELEASE_RESOURCES service is ed at the visited mobile switching center (VMSC).

ReleaseResourcesed The MAP_PROVIDE_ROAMING_NUMBER_RSP message is considered as an example here. In this example, releaseResourcesed is NULL, which indicates that the VMSC s the MAP_RELEASE_RESOURCES service. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Requested information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the subscription information requested by the HLR, including one or more of the following: Location information Subscriber state international mobile equipment identity (IMEI) MS classmark

Requested information locationInformation: Indicates the location information. subscriberState: Indicates the subscriber state. The MAP_PROVIDE_SUBSCRIBER_INFO_IND message is considered as an example here. In this example, locationInformation is NULL, which indicates that the location information is requested by the HLR; subscriberState is NULL, which indicates that the subscriber state is requested by the HLR. Reference Standards For details, see 8.3.4 "Provide Subscriber Info" in 3rd Generation Partnership Project (3GPP) TS23018-810. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Requesting node type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of the requesting node, include VLR and SGSN.

Requesting node type

The MAP_SEND_AUTHENTICATION_INFO_REQ message is considered as an example here. In this example, requestingNodeType is vlr, which indicates the VLR at the CS domain requests the authentication set.


Roaming Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the mobile station roaming number (MSRN) allocated by the MSC serving the callee.

Roaming Number The MAP_PROVIDE_ROAMING_NUMBER_RSP message is considered as an example here. In this example, content is 86139025553, which indicates the MSRN allocated by the MSC serving the callee is 86139025553. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Roaming Restriction Due To Uned Feature Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the MSC/VLR performs roaming restriction because of uned features.

Roaming Restriction Due To Uned The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered Feature as an example here. In this example, roamingRestrictionDueToUnedFeature is NULL. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Segmentation prohibited indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the new VLR allows segmentation of the response at Mobile Application Part (MAP) level.

Segmentation prohibited indicator

The MAP_SEND_AUTHENTICATION_INFO_REQ message is considered as an example here. In this example, segmentationProhibited is NULL, which indicates the new VLR allows segmentation of the response at MAP level.


SS-Code Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the supplementary service code ed by the mobile subscriber.

SS-Code The MAP__SS_REQ message is considered as an example here. In this example ss-Code is allSS. Reference Standards For details, see 11.1 "MAP__SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SS-Data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the necessary set of information required to characterize the supplementary service, for example, call hold, at the period of service activation.

SS-Data ss-Code: Indicates the supplementary service code. ss-Status: Indicates the supplementary service status. a-bit: Indicates whether the supplementary service is activated. ss-SubscriptionOption: Indicates the supplementary service subscription option. cliRestrictionOption: Indicates the command-line interface (CLI)

restriction option. basicServiceGroupList: Indicates a list of basic service groups. bearerService: Indicates bearer services. teleservice: Indicates teleservices. defaultPriority: Indicates the default priority. nbr: Indicates the maximum number of parallel bearers that may be used as defined by the at registration of the multicard service (MC) service. The MAP__SS_REQ message is considered as an example here. In this example, ss-Code is allSS; a-bit is not-active; cliRestrictionOption is permanent; bearerService is allBearerServices; teleservice is allTeleservices; defaultPriority is 0x0; nbr is 0x1. Reference Standards For details, see 11.3 "MAP_ACTIVATE_SS service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SS-Data List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of extensible SS-Data parameters.

SS-Data List ss-Code: Indicates the supplementary service code. ss-Status: Indicates the supplementary service status. a-bit: Indicates whether the supplementary service is activated. The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. In this example, ss-Code is allSS and a-bit is notactive. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SS-Status Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the status of the supplementary service.

SS-Status a-bit: Indicates whether the supplementary service is activated. The MAP_INTERROGATE_SS_RSP message is considered as an example here. In this example, a-bit is not-active. Reference Standards For details, see 11.5 "MAP_INTERROGATE_SS service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Subscriber State Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicate the status of the subscriber. Values: Busy Unreachable Idle Unknown

Subscriber State

assumedIdle: Indicates that the subscriber is in the idle state. The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, assumedIdle is NULL, which indicates that the subscriber is in the idle state. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Subscriber Status Description of the IE Reference Standards Description of the IE Information Element (IE)

Subscriber Status

Description Indicates whether the subscriber s the Operator Determined Barring service. If not, the value of this IE is service granted; if yes, the value of this IE is operatorDeterminedBarring. The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, subscriberStatus is service granted.


ed CAMEL Phases Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates which phases of CAMEL are ed

ed Customized Applications for Mobile network Enhanced Logic (CAMEL) Phases

phase4 The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, phase4 is 0x01, which indicate the CAMEL phase 4 is ed.


Suppress T-CSI Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the invocation of terminating Customized Applications for Mobile network Enhanced Logic (CAMEL) services is suppressed, that is, the HLR does not includes the T-CSI information in the SRIACK message.

Suppress terminating CAMEL subscription information (T-CSI)

suppress-T-CSI The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, suppress-T-CSI is NULL, which indicates that the T-CSI information is suppressed. Reference Standards For details, see 10.1 "MAP_SEND_ROUTING_INFORMATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Suppression of Announcement Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the call failure announcement is suppressed.

Suppression of Announcement

The MAP_SEND_ROUTING_INFORMATION_REQ message is considered as an example here. In this example, suppressionOfAnnouncement is NULL, which indicates the call failure announcement is suppressed as long as the Suppression of Announcement IE is contained.


Teleservice List Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of teleservices.

Teleservice List

TELE-SERVICE-04: Indicates a type of teleservice. The MAP_INSERT_SUBSCRIBER_DATA_IND message is considered as an example here. In this example, TELE-SERVICE-04 is emergencyCalls, which indicates the emergency call service is ed. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description

Indicates the TMSI of the subscriber. temporary mobile subscriber identifier The MAP_READY_FOR_SHORT_MESSAGE_REQ message is (TMSI) considered as an example here. In this example, tmsi is 60 38 00 07. Reference Standards For details, see 12.4 "MAP-READY-FOR-SM service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

error Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the errors. Values: Unknown subscriber Call restriction Absent subscriber Busy No reply System error

error

The MAP_PROVIDE_ROAMING_NUMBER_RSP message is considered as an example here. In this example, ie--error is absent-subscriber, which indicates that the MS is powered off. Reference Standards For details, see 10.2 "MAP_PROVIDE_ROAMING_NUMBER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

USSD Data Coding Scheme Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Indicates the coding scheme of the USSD data. Unstructured Supplementary Service Data The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ (USSD) Data Coding message is considered as an example here. In this example, ussdScheme DataCodingScheme is 0F. Reference Standards For details, see 11.9 "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

USSD String Description of the IE Reference Standards Description of the IE Information Element (IE) Unstructured Supplementary Service Data (USSD) String

Description Indicates the USSD character string. The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_REQ message is considered as an example here. In this example, ussdString is AA 11 0E 37 02.

Reference Standards For details, see 11.9 "MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

VLR CAMEL Subscription Info Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the subscriber has ed the CAMEL service. The contents of this IE vary according to the CAMEL phases. In CAMEL phase 1, this IE contains only the originating CAMEL subscription information (O-CSI). In CAMEL phase 2, this IE may contain O-CSI, supplementary service notification CAMEL subscription information (SS-CSI) and translation information flag CAMEL subscription information (TIF-CSI). In CAMEL phase 3, this IE may contain O-CSI, dialed services CAMEL subscription information (D-CSI), SSCSI, visited mobile switching center (VMSC) terminating CAMEL subscription information (VT-CSI), mobile origination short message service (MO-SMS-CSI), mobility management event notification CAMEL subscription information (M-CSI) and TIF-CSI. In CAMEL phase 4, this IE may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, mobile termination short message service camel subscription information (MTSMS-CSI), M-CSI and TIF-CSI.

VLR Customized Applications for Mobile network Enhanced

Logic (CAMEL) Subscription Info

originating camel subscription information (o-CSI): Indicates the O-CSI information. gsmSCF-Address: Indicates the address of the GSM service control function (gsmSCF). nature-of-address-indicator: Indicates the number address nature. content: Indicates the specific gsmSCF address. The MAP_INSERT_SUBSCRIBER_DATA_RSP message is considered as an example here. In this example, nature-ofaddress-indicator is international-number, which indicates that the number address nature is international; content is 000000, which indicates that the specific gsmSCF address is 000000. Reference Standards For details, see 8.8.1 "MAP_INSERT_SUBSCRIBER_DATA service" in 3rd Generation Partnership Project (3GPP) TS24008-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

VLR number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of the VLR at which the subscriber resides.


VLR number

The MAP_UPDATE_LOCATION_REQ message is considered as an example here. In this example, nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 861310751315, which indicates that the specific VLR number is 861310751315. Reference Standards For details, see 8.1.2 "MAP_UPDATE_LOCATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

address of the VMSC Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of the VMSC at which the subscriber resides.

visited mobile switching center (VMSC) address

nature-of-address-indicator: Indicates the number address nature. content: Indicates the specific VMSC number. The MAP_SEND_ROUTING_INFORMATION_CNF message is considered as an example here. In this example, nature-of-addressindicator is international-number, which indicates that the number address nature is international; content is 139000, which indicates that the VMSC address is 139000.


E/Nc Interface Protocol (Handover Management of MAP) Description of the E/Nc Interface Protocol Description of the Common Part of Messages Description of Handover Management Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the E/Nc Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC interworks with another MSC. In this networking, the MSC communicates with another MSC through Mobile Application Part (MAP). Figure 1 shows the application of the E/Nc interface protocol.

Figure 1 Application of the E/Nc interface protocol Protocol Stack Figure 2 through Figure 4 show the protocol stack of the E/Nc interface. Figure 2 Protocol stack of the E/Nc interface (non-peer-to-peer M3UA networking)

Figure 3 Protocol stack of the E/Nc interface (peer-to-peer M3UA networking)

Figure 4 Protocol stack of the E/Nc interface (M2UA networking)


Message List Table 1 List of common E/Nc interface messages Message

Direction Function

MSC-A- This message is sent to hand >MSC-B source MSC (MSC-A) to the This message is sent by MSC MSC-BMAP_PREPARE_HANDOVER_RSP acknowledge the >MSC-A MAP_PREPARE_HANDOVER This message is sent by MSC MSC-B- transmit the received Relocat MAP_PROCESS_ACCESS_SIGNALLING >MSC-A Element (IE) (in the case of 2 indicating that the MS has det This message is sent by MSC MSC-B- transmit the received Relocat MAP_SEND_END_SIGNAL_REQ >MSC-A case of 2G network) to MSCinter-MSC handover is comple MSC-B- This message is sent by MSC MAP_SEND_END_SIGNAL_RSP >MSC-A MSC MAP resources and rele This message is sent by MSC MSC-BMAP_PREPARE_SUBSEQUENT_HANDOVER_REQ that a handover or relocation >MSC-A third MSC is required. This message is sent by MSC MSC-A- MAP_PREPARE_SUBSEQUE MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP >MSC-B message and inform MSC-B o MAP_PREPARE_HANDOVER_REQ

subsequent handback and res Parent topic: E/Nc Interface Protocol (Handover Management of MAP) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Reference Standards Table 1 IEs carried in the common part of messages Information Element Description (IE) Identifies a Mobile Application Part (MAP) dialogue. Dialogue ID

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, ie-dialogue-id is 0x40a. Identifies the functions of messages. It corresponds to the operation code in the Transaction Capability Application Part (TCAP) component.

Operation code The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, ie-map-operation-code is prepare-handover. Reference Standards For details, see 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: E/Nc Interface Protocol (Handover Management of MAP) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Handover Management Messages MAP_PREPARE_HANDOVER_REQ MAP_PREPARE_HANDOVER_RSP MAP_PROCESS_ACCESS_SIGNALLING MAP_SEND_END_SIGNAL_REQ MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP MAP_SEND_END_SIGNAL_RSP MAP_U_ABORT_REQ Parent topic: E/Nc Interface Protocol (Handover Management of MAP) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PREPARE_HANDOVER_REQ Message Function Associated IEs Reference Standards Message Function The MAP_PREPARE_HANDOVER_REQ message is sent when a call is to be handed over or relocated from the source MSC (MSC-A) to the target MSC (MSC-B). Figure 1 shows the main IEs of the message. Figure 1 MAP_PREPARE_HANDOVER_REQ message

Associated IEs Information Element Description (IE) Invoke Id

Uniquely identifies an operation in a Mobile Application Part (MAP) dialogue.

For details, see Invoke Id. Target Cell Id

Indicates the location area or cell into which the subscriber intends to roam. For details, see Target Cell Id.

Target RNC Id

Indicates the identity of the RNC to which a call has to be relocated. For details, see Target RNC Id.

Indicates that no handover number is required. HONumberNotRequired For details, see HO-NumberNotRequired. International mobile subscriber identity (IMSI)



Indicates the integrity protection information used by the source MSC. For details, see Integrity Protection Information.


Indicates the encryption information used by the source MSC. For details, see Encryption Information.

Radio Resource Information

Indicates the radio resource information. For details, see Radio Resource Information.

AN-APDU

Indicates the application protocol data unit of the access network. For details, see AN-APDU.

Allowed GSM Algorithms

Indicates the GSM encryption algorithm ed by the source MSC. For details, see Allowed GSM Algorithms.

Allowed Universal Mobile Telecommunications System (UMTS) Algorithms

Indicates the UMTS encryption algorithm ed by the source MSC. For details, see Allowed UMTS Algorithms.

Radio Resource List

Indicates a list of radio resources. For details, see Radio Resource List.

radio access bearer (RAB) ID

Indicates the radio access identifier. For details, see RAB ID.

Iu-Currently Used Codec

Indicates the codec used at the Iu interface before handover. For details, see Iu-Currently Used Codec.

Iu-ed Codecs Indicates the codecs ed by the Iu interface.

List

For details, see Iu-ed Codecs List.

Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PREPARE_HANDOVER_RSP Message Function Associated IEs Reference Standards Message Function This message is sent by MSC_B to inform MSC_A that handover preparation is completed. (Assume that an MS/UE is handed over from MSC_A to MSC_B.) Figure 1 shows the main information element of the message. Figure 1 MAP_PREPARE_HANDOVER_RSP message


(IE)

Description

Invoke Id


AN-APDU

Indicates an application protocol data unit of the access network. For details, see AN-APDU.

Handover Number

Indicates a handover number. For details, see Handover Number.

Relocation Number List

Indicates a handover number list. For details, see Relocation Number List.

Selected Universal Mobile Telecommunications System (UMTS) Algorithms

Indicates a selected UMTS algorithm. For details, see Selected UMTS Algorithms.

Indicates the selected radio resource information. Chosen Radio Resource Information For details, see Chosen Radio Resource Information. Iu-Selected Codec

Indicates a codec selected for the Iu interface. For details, see Iu-Selected Codec.

Iu-Available Codecs List

Indicates a codec list available for the Iu interface. For details, see Iu-Available Codecs List

error

Indicates a error. For details, see error.

Provider error

Indicates a provider error. For details, see Provider error.

Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PROCESS_ACCESS_SIGNALLING Message Function Associated IEs Reference Standards Message Function The MAP_PROCESS_ACCESS_SIGNALLING message is sent by MSC-B to transparently transmit the received Relocation Detect IE (in the case of 2G network) to MSC-A, indicating that the MS has detects a new channel. Figure 1 shows the main IEs of the message. Figure 1 MAP_PROCESS_ACCESS_SIGNALLING message

Associated IEs

Information Element Description (IE) Invoke Id


AN-APDU


Selected GSM Algorithm

Indicates the GSM encryption algorithm selected. For details, see Selected GSM Algorithm.

Selected radio Indicates the radio access identifier selected. access bearer (RAB) For details, see Selected RAB ID. id Selected Universal Mobile Telecommunications System (UMTS) Algorithms

Indicates the UMTS encryption algorithm selected. For details, see Selected UMTS Algorithms.

Indicates the radio resource information selected. Chosen Radio Resource Information For details, see Chosen Radio Resource Information. Iu-Selected Codec

Indicates the codecs selected by the Iu interface. For details, see Iu-Selected Codec.


Indicates the codecs available for the Iu interface. For details, see Iu-Available Codecs List.

Reference Standards For details, see 8.4.3 "MAP_PROCESS_ACCESS_SIGNALLING service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_END_SIGNAL_REQ Message Function Associated IEs Reference Standards Message Function The MAP_SEND_END_SIGNAL_REQ message is sent by MSC-B to transparently transmit the received Relocation Complete IE (in the case of 2G network) to MSC-A, indicating that the handover of MSC-A is complete. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_END_SIGNAL_REQ message



AN-APDU


Reference Standards For details, see 8.4.2 "MAP_SEND_END_SIGNAL service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ Message Function Associated IEs Reference Standards Message Function The MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ message is sent to inform MSC-A that a handover or relocation to either MSC-A or a third MSC is required. Figure 1 shows the main IEs of the message. Figure 1 MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ message


(IE)

Description

Invoke Id


Target Cell Id

Indicates the location area or cell into which the subscriber intends to roam. For details, see Target Cell Id.

Target RNC Id

Indicates the identity of the RNC to which a call has to be relocated. For details, see Target RNC Id.

AN-APDU


Selected radio Indicates the radio access identifier selected. access bearer (RAB) For details, see Selected RAB ID. id Indicates the integrated services digital network (ISDN) number of Target MSC Number an MSC to which a call has to be handed over. For details, see Target MSC Number. Reference Standards For details, see 8.4.5 "MAP_PREPARE_SUBSEQUENT_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP Message Function Associated IEs Reference Standards Message Function This message is sent by MSC_A to MSC_B to acknowledge the MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ message. It is used to notify MSC_B whether subsequent handover is allowed and how resources are allocated. Figure 1 shows the main information elements (IEs) of the message. Figure 1 MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP message


Uniquely identifies an operation in a Mobile Application Part (MAP) dialogue. For details, see Invoke Id. Indicates an application protocol data unit of the access network.

AN-APDU

For details, see AN-APDU.

error

Indicates a error. For details, see error.

Provider error

Indicates a provider error. For details, see Provider error.

Reference Standards For details, see 8.4.5 "MAP_PREPARE_SUBSEQUENT_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_END_SIGNAL_RSP Message Function Associated IEs Reference Standards Message Function The MAP_SEND_END_SIGNAL_RSP message is sent to release the Mobile Application Part (MAP) resources between MSCs and to release the inter-MSC call. Figure 1 shows the main IEs of the message.

Figure 1 MAP_SEND_END_SIGNAL_RSP message Associated IEs Information Element Description (IE) Invoke Id

Uniquely identifies an operation in a MAP dialogue. For details, see Invoke Id.

Reference Standards For details, see 8.4.2 "MAP_SEND_END_SIGNAL service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_U_ABORT_REQ Message Function Associated IEs Reference Standards Message Function This message is sent when the upper-layer becomes abnormal during a Mobile Application Part (MAP) dialog. Figure 1 shows the main information element of the message. Figure 1 MAP_U_ABORT_REQ message

Associated IEs Information Element Description (IE) reason

Indicates a reason. For details, see reason.

Diagnostic information

Indicates the diagnostic information. For details, see Diagnostic information.

Reference Standards For details, see 7.3.4 "MAP_U_ABORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870.

Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Allowed GSM Algorithms Allowed UMTS Algorithms AN-APDU Chosen Radio Resource Information Encryption Information Handover Number HO-NumberNotRequired Integrity Protection Information Iu-Available Codecs List Iu-Currently Used Codec Iu-Selected Codec Iu-ed Codecs List RAB ID Radio Resource Information Radio Resource List Relocation Number List Selected GSM Algorithm Selected RAB ID Selected UMTS Algorithms Target Cell Id Target MSC Number Target RNC Id error Provider error reason Diagnostic information

error Parent topic: E/Nc Interface Protocol (Handover Management of MAP) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Allowed GSM Algorithms Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the GSM encryption algorithms that are ed. Values:

no-encryption gsm-a5-1 gsm-a5-2 gsm-a5-3 gsm-a5-4 gsm-a5-5 gsm-a5-6 gsm-a5-7

Allowed GSM Algorithms

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, no-encryption is allowed, which indicates the 2G encryption algorithm is not ed; gsm-a5-1 is not-allowed, which indicates the a5-1 algorithm is not ed; gsm-a5-2 is not-allowed, which indicates the a5-2 algorithm is not ed; gsm-a5-3 is not-allowed, which indicates the a5-3 algorithm is not ed; gsm-a5-4 is not-allowed, which indicates the a5-4 algorithm is not ed; gsm-a5-5 is not-allowed, which indicates the a5-5 algorithm is not ed; gsm-a5-6 is notallowed, which indicates the a5-6 algorithm is not ed; and gsm-a5-7 is not-allowed, which indicates the a5-7 algorithm is not ed. Reference Standards

For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Allowed UMTS Algorithms Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the UMTS encryption algorithms that are ed. Values:

Allowed Universal Mobile Telecommunications System (UMTS) Algorithms

INTEGRITY-PROTECTION-ALGORITHM ENCRYPTION-ALGORITHM The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, INTEGRITY-PROTECTIONALGORITHM is standard-UIA1, which indicates that the standardUIA1 integrity protection algorithm is ed; ENCRYPTIONALGORITHM is standard-UEA1, which indicates the standard-UEA1 encryption algorithm is ed.

Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AN-APDU Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the application protocol data unit of the access network. It includes the complete Relocation Request (or Handover Request) message and is sent by the MSC to the target RNC or BSC without being parsed.

AN-APDU

accessNetworkProtocolId: Indicates the access network protocol ID. signalInfo: Indicates the signal information. The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, accessNetworkProtocolId is ts3G-48006, which indicates that the access network protocol is ts3G-48006. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870.


Chosen Radio Resource Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the radio resource information used by the target MSC involved in handover.

Chosen Radio Resource Information

chosenChannelInfo: Indicates the channel information used. chosenSpeechVersion: Indicates the speech version used. The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, chosenChannelInfo is 03, which indicates that the used channel is 3; chosenSpeechVersion is 01, which indicates that the used speech version is 1.


Encryption Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the encryption information. Encryption Information

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, encryptionInfo is 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.


Handover Number Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the number allocated by the target MSC and used for routing a call between MSCs during handover.

Handover Number

nature-of-address-indicator content The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, nature-of-address-indicator is international-number, which indicates that the number address nature is international; content is 13907558888, which indicates the handover number is 13907558888.


HO-NumberNotRequired Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates that no handover number is required. The MAP_PREPARE_HANDOVER_REQ message is considered as HONumberNotRequired an example here. In this example, ho-NumberNotRequired is NULL. As long as the HO-NumberNotRequired IE is contained, no handover number is required regardless of the value of the HONumberNotRequired IE. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Integrity Protection Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the integrity protection information used by the source MSC. Integrity Protection Information

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, integrityProtectionInfo is 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.


Iu-Available Codecs List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the codecs available for the Iu interface.


The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, iuAvailableCodecsList is codec1, codec2, codec3, codec4, which indicates the codecs available for the Iu interface are codec1, codec2, codec3, and codec4. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Iu-Currently Used Codec Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the codecs that currently used by the Iu interface. Iu-Currently Used Codec

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, iuCurrentlyUsedCodec is 00, indicates that the codec currently used by the Iu interface is 00.


Iu-Selected Codec Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the codecs that are selected the Iu interface. Iu-Selected Codec

The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, iuSelectedCodec is 01, indicates that the codec selected by the Iu interface is 01.


Iu-ed Codecs List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates a list of codecs ed by the Iu interface.

Iu-ed Codecs List

iuedCodecsList codec1 The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, codec1 is 00, indicates that the codec ed by the Iu interface is 00.


RAB ID Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the radio access identifier. Radio Access Bearer (RAB) ID The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, rab-Id is 0x01. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Radio Resource Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Radio Resource Information

Description Indicates the radio resource information. If the Radio Resource List IE is included in the handover request message, the Radio Resource Information IE will not be included in the handover request message. The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, radioResourceInformation is 00 00 00.


Radio Resource List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates a list of radio resources, include radioResourceInformation and rab-Id. If the Radio Resource Information IE is included in the handover request message, the Radio Resource List IE will not included in the handover request message.

Radio Resource List

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, radioResourceInformation is 00 00 00, which indicates the radio resource list; rab-Id is 0x01, which indicates the radio access identifier. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Relocation Number List Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates a list of handover numbers that are allocated by the target MSC and used for routing a call between MSCs during handover. If the Relocation Number List IE is returned, the Handover Number IE will not be returned.

Relocation Number List

The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, content is 8613907554567, which indicates that the handover number allocated by the target MSC is 8613907554567. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Selected GSM Algorithm Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the GSM algorithm selected by GSM BSC controlled by the target MSC. Selected GSM Algorithm

The MAP_PROCESS_ACCESS_SIGNALLING_REQ message is considered as an example here. In this example, selectedGSMAlgorithm is no-encryption-used, which indicates that the GSM algorithm is not selected.

Reference Standards For details, see 8.4.3 "MAP_PROCESS_ACCESS_SIGNALLING service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Selected RAB ID Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the radio access identifier selected by GSM BSC controlled by the target MSC.

Selected Radio Access Bearer (RAB) The MAP_PROCESS_ACCESS_SIGNALLING_REQ message is ID considered as an example here. In this example, selectedRab-Id is 0x01. Reference Standards For details, see 8.4.3 "MAP_PROCESS_ACCESS_SIGNALLING service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Selected UMTS Algorithms Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the UMTS algorithm selected by GSM BSC controlled by the target MSC.

Selected Universal Mobile Telecommunications System (UMTS) Algorithms

integrityProtectionAlgorithm encryptionAlgorithm The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, integrityProtectionAlgorithm is standard-UIA1, which indicates that the standard-UIA1 integrity protection algorithm is selected; encryptionAlgorithm is noencryption, which indicates that the no encryption algorithm is selected.


Target Cell Id Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the identity of the cell to which a call has to be handed over. This IE is used for a 2G network. Target Cell Id The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, targetCellId is 46 00 00 77 55. Reference Standards For details, see 8.4.1 "MAP_PREPARE_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target MSC Number Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the number of the MSC to which a call has to be handed over.

Target MSC Number

nature-of-address-indicator content The MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ message is considered as an example here. In this example, nature-ofaddress-indicator is international-number, which indicates that the number address nature is international; content is 861310751201, which indicates that the specific MSC number is 861310751201.

Reference Standards For details, see 8.4.5 "MAP_PREPARE_SUBSEQUENT_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target RNC Id Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the identity of the RNC to which a call has to be handed over. This IE is used for a 3G network. Target RNC Id

The MAP_PREPARE_HANDOVER_REQ message is considered as an example here. In this example, targetRNCId is 46 00 00 77 55 00 44.



Description Indicates a error.

error

The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, ie--error is system-failure.


Provider error Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a provider error.

Provider error

The MAP_PREPARE_HANDOVER_RSP message is considered as an example here. In this example, ie-provider-error is service-completefailure.


reason Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a reason.

reason

The MAP_U_ABORT_REQ is considered as an example here. In this example, ie-abort--reason is mpa-application-procedurecancellation, which indicates that reason is that the application is cancelled.

Reference Standards For details, see 7.3.4 "MAP_U_ABORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Diagnostic information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the diagnostic information.

Diagnostic information

The MAP_U_ABORT_REQ is considered as an example here. In this example, ie-abort-diagnostic-info is mpa-associated-procedurefailure, which indicates that associated procedures fail.

Reference Standards For details, see 7.3.4 "MAP_U_ABORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates a error.

error

The MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP message is considered as an example here. In this example, ie--error is system-failure, indicating that the system fails.

Reference Standards For details, see 8.4.5 "MAP_PREPARE_SUBSEQUENT_HANDOVER service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

G Interface Protocol Description of the G Interface Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the G Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC interworks with the VLR. In this networking, it also functions as the VLR and communicates with the VLR through Mobile Application Part (MAP). Figure 1 shows the application of the G interface protocol.

Figure 1 Application of the G interface protocol Protocol Stack Figure 2 through Figure 4 show the protocol stack of the G interface. Figure 2 Protocol stack of the G interface (non-peer-to-peer M3UA networking)

Figure 3 Protocol stack of the G interface (peer-to-peer M3UA networking)

Figure 4 Protocol stack of the G interface (M2UA networking)


Message List Table 1 List of common G interface messages Message

Direction

MAP_SEND_IDENTIFICATION_REQ

VLR-A>VLR-B

MAP_SEND_IDENTIFICATION_RSP

VLR-B>VLR-A

Function This message sent by VLR-A to request the International mobile subscriber identity (IMSI) and authentication data from VLR-B. This message sent by VLR-B to VLR-A to acknowledge the MAP_SEND_IDENTIFICATION_REQ message.

Parent topic: G Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, ie-dialogue-id is 0x40a. Identifies the functions of messages. It corresponds to the operation code in the Transaction Capability Application Part (TCAP) component.

Operation code The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, ie-map-operation-code is send-identification. Reference Standards For details, see 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: G Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages MAP_SEND_IDENTIFICATION_REQ MAP_SEND_IDENTIFICATION_RSP Parent topic: G Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_IDENTIFICATION_REQ Message Function Associated IEs Reference Standards Message Function The MAP_SEND_IDENTIFICATION_REQ message is sent by the serving VLR to request the International mobile subscriber identity (IMSI) and authentication data from the previous VLR (PVLR). Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_IDENTIFICATION_REQ message



For details, see Invoke id. temporary mobile subscriber identifier (TMSI)

Indicates the TMSI of the subscriber. For details, see TMSI.


Indicates the number of requested authentication sets. For details, see Number of requested vectors.

Indicates if the VLR allows segmentation of the response at MAP Segmentation prohibited level. indicator For details, see Segmentation prohibited indicator. MSC Number

Indicates the MSC number of the subscriber. For details, see MSC Number.

Previous Location Area Id

Indicates the ID of the previous location area. For details, see Previous Location Area Id.

Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_SEND_IDENTIFICATION_RSP Message Function Associated IEs Reference Standards Message Function The MAP_SEND_IDENTIFICATION_RSP message is sent by previous VLR (PVLR) to the serving VLR to acknowledge the MAP_SEND_IDENTIFICATION_REQ message. Figure 1 shows the main IEs of the message. Figure 1 MAP_SEND_IDENTIFICATION_RSP message



For details, see Invoke id. Indicates the IMSI number of the subscriber. International mobile subscriber identity (IMSI) For details, see IMSI. Authentication set

Indicates the authentication set of the subscriber. For details, see Authentication set.

Current Security Context

Indicates the security context. For details, see Current Security Context.

Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Authentication set Current Security Context IMSI Invoke id MSC Number Number of requested vectors Previous Location Area Id Segmentation prohibited indicator TMSI Parent topic: G Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Authentication set Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of authentication sets. TripletList (for GSM authentication): The triplet list contains all the triplet authentication sets required by the VLR. QuintupletList (for Universal Mobile Telecommunications System (UMTS) authentication): The quintuplet list contains all the quintuplet authentication sets required by the VLR.

Authentication set

The MAP_SEND_IDENTIFICATION_CNF message is considered as an example here. In this example, rand is 27 E4 0A 15 AD 98 45 6A C3 41 70 4A D8 BA 86 2D, which indicates a set of random numbers; sres is 16 D3 87 07, which indicates the subscriber response; kc is 00 04 5C CC DD AF 6A FD, which indicates the encryption key used for authentication.

Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Current Security Context Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates a list of security context parameters. This list either contains GSM Security Context data (Kc and Cksn) or Universal Mobile Telecommunications System (UMTS) Security Context Data (Ck, Ik, and Ksi).

Current Security Context

The MAP_SEND_IDENTIFICATION_CNF message is considered as an example here. In this example, ck is B2 E9 5C BC 03 14 C9 40 7B 7B BB 69 E0 AF C7 69, which indicates the ciphering key; ik is 40 56 94 D7 D5 76 64 03 DD C5 CA D0 C5 D9 1B 33, which indicates the integrity key; ksi is 06; which indicates the key set identifier. Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description

International mobile Indicates the IMSI number of the subscriber. subscriber identity (IMSI) Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Invoke id Description of the IE Reference Standards Description of the IE Information Element (IE)


Invoke Id

The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, invoke-ID is 0x4e, which indicates the invoking identifier of the MAP dialogue.


MSC Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of the MSC at which the subscriber resides.

MSC Number The MAP_OPEN_REQ message is considered as an example here. In this example, content is 86139025, which indicates the MSC number of the subscriber is 86139025. Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Number of requested vectors Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number of authentication sets the new VLR is prepared to receive from the previous VLR (PVLR).


The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, numberOfRequestedVectors is 0x5, which indicates the serving VLR can receive a maximum of five authentication sets from the PVLR..


Previous Location Area Id Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the ID of the previous location area. Previous Location Area Id

The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, previous-LAI is 4600007788, which indicates the previous location area ID is 4600007788.


Segmentation prohibited indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the new VLR allows segmentation of the response at Mobile Application Part (MAP) level.

Segmentation prohibited indicator

The MAP_SEND_IDENTIFICATION_REQ message is considered as an example here. In this example, segmentationProhibited is NULL, which indicates the segmentation of the response at MAP level is allowed.



Description Indicates the TMSI of the subscriber.

Temporary mobile subscriber identifier The MAP_SEND_IDENTIFICATION_REQ message is considered as (TMSI) an example here. In this example, tmsi is 60 38 00 07, which indicates TMSI allocated by previous VLR (PVLR) is 60 38 00 07. Reference Standards For details, see 8.1.4 "MAP_SEND_IDENTIFICATION service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

E Interface Protocol Description of the E Interface Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the E Interface Protocol Scenario Description Protocol Stack Message List Scenario Description The MSC interworks with the SMC. In this networking, the MSC communicates with the SMC through Mobile Application Part (MAP). Figure 1 shows the application of the E interface protocol.

Figure 1 Application of the E interface protocol Protocol Stack Figure 2 through Figure 4 show the protocol stack of the E interface. Figure 2 Protocol stack of the E interface (non-peer-to-peer M3UA networking)

Figure 3 Protocol stack of the E interface (peer-to-peer M3UA networking)

Figure 4 Protocol stack of the E interface (M2UA networking)


Message List Table 1 List of common E interface messages Message

Direction Function

MAP_MO_FORWARD_SHORT_MESSAGE_REQ

MSC>SMC

MAP_MO_FORWARD_SHORT_MESSAGE_CNF

SMC>MSC

MAP_MT_FORWARD_SHORT_MESSAGE_IND

SMC>MSC

MAP_MT_FORWARD_SHORT_MESSAGE_RSP

MSC>SMC

This message is sent by the MS short message to the SMC. This message is sent by the SM acknowledge the MAP_MO_FORWARD_SHORT message. This message is sent by the SM terminate a short message. This message is sent by the MS acknowledge the MAP_MT_FORWARD_SHORT_ message.

Parent topic: E Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, ie-dialogue-id is 0x40a. Identifies the functions of messages. It corresponds to the operation code in the Transaction Capability Application Part (TCAP) component.

Operation code The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, ie-mapoperation-code is mo-forward-sm. Reference Standards For details, see 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: E Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages MAP_MO_FORWARD_SHORT_MESSAGE_REQ MAP_MO_FORWARD_SHORT_MESSAGE_CNF MAP_P_ABORT_IND MAP_MT_FORWARD_SHORT_MESSAGE_IND MAP_MT_FORWARD_SHORT_MESSAGE_RSP data ACK Parent topic: E Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_MO_FORWARD_SHORT_MESSAGE_REQ Message Function Associated IEs Reference Standards Message Function The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is sent by the mobile switching center (MSC) server to forward a short message to the short message center (SMC). Figure 1 shows the main information elements (IEs) in the message. Figure 1 MAP_MO_FORWARD_SHORT_MESSAGE_REQ message

Associated IEs IE

Description

Invoke Id


Short Message (SM) RP Indicates the destination address used by the short message service relay sub-layer protocol. Destination Address (DA) For details, see SM RP DA. SM RP Origination Address (OA)

Indicates the originating address used by the short message service relay sub-layer protocol, for example, Mobile Station International ISDN Number (MSISDN). For details, see SM RP OA.

SM RP UI

Represents the data field carried by the short message service relay sub-layer protocol. For details, see SM RP UI.

Reference Standards For details, see section 12.2 "MAP-MO-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_MO_FORWARD_SHORT_MESSAGE_CNF Message Function Associated IEs Reference Standards Message Function The MAP_MO_FORWARD_SHORT_MESSAGE_CNF message is sent by the short message center (SMC) to the mobile switching center (MSC) server to acknowledge the MAP_MO_FORWARD_SHORT_MESSAGE_REQ message. If an error occurs when the SMC processes the received short message, the SMC includes the corresponding cause value in the MAP_MO_FORWARD_SHORT_MESSAGE_CNF message. Figure 1 shows the main information elements (IEs) in the message. Figure 1 MAP_MO_FORWARD_SHORT_MESSAGE_CNF message

Associated IEs IE

Description

Invoke Id


Reference Standards For details, see section 12.2 "MAP-MO-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_P_ABORT_IND Message Function Associated IEs Reference Standards Message Function The MAP_P_ABORT_IND message is sent when a short message cannot arrive at the SMC. Figure 1 shows the main IEs of the message.

Figure 1 MAP_P_ABORT_IND message Associated IEs Information Element (IE)

Description Indicates the reason for aborting the Mobile Application Part (MAP) dialogue. Values:

Provider reason

1. 2. 3. 4. 5. 6.

Provider malfunction ing dialogue/transaction released Resource limitation Maintenance activity Version incompatibility Abnormal MAP dialogue

Indicates the source of the abort. Values:

Source

1. MAP problem 2. Transmission convergence (TC) problem 3. Network service problem

Reference Standards For details, see 7.3.5 "MAP-P-ABORT service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_MT_FORWARD_SHORT_MESSAGE_IND Message Function Associated IEs Reference Standards Message Function The MAP_MT_FORWARD_SHORT_MESSAGE_IND message is sent by the short message center (SMC) to instruct the mobile switching center (MSC) server to send a short message to the destination subscriber. Figure 1 shows the main information elements (IEs) in the message. Figure 1 MAP_MT_FORWARD_SHORT_MESSAGE_IND message

Associated IEs

IE

Description

Invoke Id


Indicates the destination address used by the short message Short Message (SM) RP service relay sub-layer protocol, that is, the international mobile subscriber identity (IMSI) number in the mobile terminated (MT) Destination Address short message. (DA) For details, see SM RP DA. SM RP Origination Address (OA)

Indicates the originating address used by the short message service relay sub-layer protocol, for example, that is, the SMC address in the MT short message. For details, see SM RP OA.

SM RP UI

Represents the data field carried by the short message service relay sub-layer protocol. For details, see SM RP UI.

Reference Standards For details, see section 12.9 "MAP-MT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MAP_MT_FORWARD_SHORT_MESSAGE_RSP Message Function Associated IEs Reference Standards Message Function The MAP_MT_FORWARD_SHORT_MESSAGE_RSP message is sent by the mobile switching center (MSC) server to notify the short message center (SMC) of the result of sending a short message to the destination subscriber. If the MSC server fails to send the short message to the destination subscriber, the MSC server includes a failure cause value in the MAP_MT_FORWARD_SHORT_MESSAGE_RSP message. Figure 1 shows the associated information elements (IEs) in the message. Figure 1 MAP_MT_FORWARD_SHORT_MESSAGE_RSP message

Associated IEs IE

Description

Invoke Id


error

(Optional IE) Indicates the reason for the failure of sending short messages. For details, see error.

Reference Standards For details, see section 12.9 "MAP-MT-FORWARD-SHORT-MESSAGE service" in 3rd

Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

data Message Function Associated IEs Reference Standards Message Function The data message is sent between MSCs to deliver the routing performer (RP) data. Figure 1 shows the main IEs of the message. Figure 1 data message


Description

sms msg type

Indicates the short message type. For details, see Message type.

Reference Standards For details, see 9.3.2 "Protocol element repertoire at Short Message (SM) Relay Layer (RL)" in 3rd Generation Partnership Project (3GPP) TS23040-830. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ACK Message Function Associated IEs Reference Standards Message Function The ACK message is sent to acknowledge the data message. Figure 1 shows the main IEs of the message. Figure 1 ACK message


Description

sms msg type

Indicates the short message type. For details, see Message type.

Reference Standards For details, see 9.3.2 "Protocol element repertoire at Short Message (SM) Relay Layer (RL)" in 3rd Generation Partnership Project (3GPP) TS23040-830. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs IMSI Invoke Id SM RP DA SM RP OA error Message type SM RP UI Parent topic: E Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates the IMSI of the subscriber who receives the multicast tunnel (MT) short messages.

International mobile subscriber identity (IMSI) The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, content is 460000240946695, which indicates that the MT short message is received by the subscriber with the IMSI of 460000240946695. Reference Standards For details, see 12.9 "MAP-MT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Invoke Id Description of the IE Reference Standards Description of the IE Information Element (IE)


Invoke Id

The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, invoke-ID is 0x4e, which indicates the invoking identifier of the MAP dialogue.

Reference Standards For details, see 12.2 "MAP-MO-FORWARD-SHORT-MESSAGE service" or 12.9 "MAPMT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SM RP DA Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the destination address used by the short message service relay sub-layer protocol, that is, the SMC address in an multiplex option (MO) short message or the subscriber address in an multicast tunnel (MT) short message.

Short Message (SM) RP Destination Address (DA)

The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, number is 86139075555, which indicates that the SMC number is 86139075555. Reference Standards For details, see 12.2 "MAP-MO-FORWARD-SHORT-MESSAGE service" or 12.9 "MAPMT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SM RP OA Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the source address used by the short message service relay sub-layer protocol, that is, the message sender address in an multiplex option (MO) short message or the SMC address in an multicast tunnel (MT) short message.

Short Message (SM) RP Origination Address (OA)

The MAP_MO_FORWARD_SHORT_MESSAGE_REQ message is considered as an example here. In this example, content is 8613907551605, which indicates the number of the subscriber who sends the short message. Reference Standards For details, see 12.2 "MAP-MO-FORWARD-SHORT-MESSAGE service" or 12.9 "MAPMT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates the reason why a short message cannot be sent successfully. Values:

error

1. Unidentified subscriber: Indicates that the network side does not store any information of the subscriber. 2. Absent Subscriber_SM: Indicates the MS power-off or roaming restriction. 3. Subscriber busy for mobile terminating (MT) short message service (SMS): Indicates that the MS cannot receive two short messages at the same time. 4. Facility Not ed: Indicates the MS does not the SMS. 5. Illegal Subscriber: Indicates that delivery of the MT short message failed because the MS fails authentication. 6. Illegal equipment: Indicates that delivery of the MT short message failed because an international mobile equipment identity (IMEI) check fails. 7. System Failure 8. Short Message (SM) Delivery Failure, including: memory capacity exceeded in the mobile equipment, protocol error, and mobile equipment does not the mobile terminated short message service 9. Unexpected Data Value 10. Data Missing The MAP_MO_FORWARD_SHORT_MESSAGE_CNF message is considered as an example here. In this example, ie--error is smdelivery-failure(32).

Reference Standards For details, see 12.9 "MAP-MT-FORWARD-SHORT-MESSAGE service" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Message type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicate the type of short message. It can be included in different types of messages. 1. _DATA: This message is sent between the MS and the network side and contains the subscriber data or the other related information. 2. _ACK: This message is sent between the MS and the network side to acknowledge the _DATA message. 3. _ERROR: This message is sent between the MS and the network side to transmit the error information.

sms msg type

The _data message is considered as an example here. In this example, sms-msg-type is -data, which indicates the MS sends a short message to the network side. Reference Standards For details, see 9.3.2 "Protocol element repertoire at Short Message (SM) Relay Layer (RL)" in 3rd Generation Partnership Project (3GPP) TS23040-830. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SM RP UI Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Short Message (SM) Represents the data field carried by the short message service RP UI relay sub-layer protocol. Reference Standards For details, see section 7.6.8 "Short message parameters" in 3rd Generation Partnership Project (3GPP) TS29002-870. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Sv Interface Protocol Description of the Sv Interface Protocol Description of the Common Part of Messages Description of Handover Management Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Sv Interface Protocol Scenario Description Protocol Stack Message List Scenario Description At the initial phase of Voice over Long Term Evolution (VoLTE) network deployment, carriers' networks are upgraded from the GSM/Enhanced Data rates for GSM Evolution (EDGE) radio access network (GERAN) or Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) to the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The Long Term Evolution (LTE) network usually covers only hot spots and provides services only in certain areas. When a subscriber roams from an E-UTRAN to a GERAN/UTRAN, the subscriber have to be handed over from E-UTRAN to the GERAN/UTRAN. When a subscriber roams from an E-UTRAN to a UTRAN/GERAN during a call, the EUTRAN determines whether the subscriber needs to be handed over based on the information about neighboring networks (including signaling availability and signal strength) received from equipment (UE). If a handover is required, the E-UTRAN sends a handover request to the mobility management entity (MME) or the serving GPRS node (SGSN). The MME/SGSN then sends a Single Radio Voice Call Continuity (SRVCC) handover request to the mobile switching center (MSC) server over the Sv interface. In this way, subscribers can continue ongoing calls when roaming from an E-UTRAN to a UTRAN/GERAN. The MME/SGSN interworks with the SRVCC Interworking Function (SRVCC IWF), which is the MSC server equipped with the SRVCC IWF function, using General Packet Radio Service (GPRS) Tunneling Protocol (GTP) version 2, control plane (GTPv2-C). Figure 1 shows the application of the GTPv2-C protocol.

Figure 1 Application of the GTPv2-C protocol Protocol Stack The Sv interface uses GTPv2-C protocol stack. Figure 2 shows the protocol stack for the Sv interface. Figure 2 Protocol stack of the Sv interface

NOTE: Based on Datagram Protocol (UDP), the GTPv2-C is the control part of the GTP. L1: Layer 1 of the GTPv2-C protocol stack. Carriers can adopt an appropriate protocol based on their requirements. L2: Layer 2 of the GTPv2-C protocol stack. Typically Ethernet is used at a Layer 2, but carriers may use other protocols. Message List Table 1 List of common Sv interface messages Message

Direction

GTP_MSG_SRVCC_PS_TO_CS_REQ

This message is sent from th MME/SGSN- MME/SGSN to the target MS >MSC server Sv interface, instructing the M initiate an SRVCC handover.

GTP_MSG_SRVCC_PS_TO_CS_RSP

This message is sent by the source MME/SGSN over the MSC server- response to the >MME/SGSN GTP_MSG_SRVCC_PS_TO message during the SRVCC procedure.

GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF

This message is sent from th MSC server- the Sv interface to notify the >MME/SGSN that the SRVCC handover wi successful.

GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK

Function

This message is sent from th MME/SGSN to the MSC serv MME/SGSN- interface in response to the

>MSC server GTP_MSG_SRVCC_PS_TO message during the SRVCC procedure.

This message is sent from th MME/SGSN- MME/SGSN to the target MS GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF >MSC server Sv interface, requesting the c ongoing SRVCC handover.

This message is sent from th source MME/SGSN over the MSC server- response to the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_ACK >MME/SGSN GTP_MSG_SRVCC_PS_TO message during the SRVCC procedure. Parent topic: Sv Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 describes the information elements (IEs) carried in the common part of messages. Table 1 IEs carried in the common part of messages Information Element (IE)

Description Indicates the sender and receiver of a message.

senderMID: identifies the BSG process which sends the message. senderPid: identifies the internal processing module which sends the message. receiverMid: identifies the BSG process which receives the message. recvrPid: identifies the internal processing module which receives the message. Header

The GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, meanings of each parameter are as follows: senderMID is set to 1400: indicating that the BSG process whose process identification (PID) is 1400 sends the message. senderPid is set to sx-PID-IPD(204): indicating that an internal integrated product development (IPD) module sends the message. receiverMid is set to 1400: indicating that the BSG process whose PID is 1400 receives the message. recvrPid is set to sx-PID-GTP(356): indicating that the internal GPRS tunneling protocol (GTP) module receives the message. Describes the GTP message.

pathID: identifies the GTP path. entityID: identifies the GTP peer (GTPPE) entity, corresponding to the local mobile management entity (MME). fromIP: identifies the source IP address of the message, corresponding to the IP address of the MME. toIP: identifies the target IP address of the message, corresponding to the IP address of the mobile switching center (MSC) server. fromPort: identifies the port through which the message is sent. toPort: identifies the port through which the message is received. msgType: indicates the message type. spare: indicates that the field is not used. teid-present: indicates whether the message contains tunnel endpoint identifier (TEID) IE. Value: 1: The message contains TEID IE. 0: The message does not contain TEID IE. Body

piggyback: indicates whether the PIGGYBACK feature is ed. Value: 0: The PIGGYBACK feature is not ed. 1: The PIGGYBACK feature is ed version: identifies the ed GTP versions. The GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here.

In the example, meanings of each parameter are as follows: pathID is set to 0: indicating that the sequence number of the GTP path is 0. entityID is set to 0: indicating that the sequence number of the local MME is 0. fromIP is set to 09 01 42 a1, which is a hexadecimal number. After the value is reversed to "a1 42 01 09" and converted to a decimal equivalent, the sending IP address "161.66.1.9" is obtained. toIP is set to 52 01 42 a1, which is a hexadecimal number. After the value is reversed to "a1 42 01 52" and converted to a decimal equivalent, the receiving IP address "161.66.1.81" is obtained. fromPort is set to 2124: indicating that the message is sent through the port whose port number is 2124. toPort is set to 2123: indicating that the message is received through the port whose port number is 2123. msgType is set to 25: indicating that the message type is PS to CS Request. spare is set to 0: indicating that the field is idle. teid-present is set to 1: indicating that the message contains TEID IE. piggyback is set to 0: indicating that the PIGGYBACK feature is not ed. version is set to 2: indicating that the ed GTP version number is version 2.

ie-common field

It is an example of the GTP_MSG_SRVCC_PS_TO_CS_REQ message. In the stn-sr IE of this example, ie-common is the common field of the IEs in the Sv interface messages. The ie-common field is used with the IE type field to identify an IE. In this message, the ie-common is not added, therefore, spare and instance are set to 0.

Parent topic: Sv Interface Protocol


Description of Handover Management Messages GTP_MSG_SRVCC_PS_TO_CS_REQ GTP_MSG_SRVCC_PS_TO_CS_RSP GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF GTP_MSG_SRVCC_PS_TO_CS_CANCEL_ACK Parent topic: Sv Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_REQ Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_REQ message is sent from the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) to the target mobile switching center (MSC) server over the Sv interface, instructing the MSC server to initiate a Single Radio Voice Call Continuity (SRVCC) handover. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_REQ message sent during an intra-MSC 3G

handover Associated IEs Information Element (IE)

Description

IP-Address

This IE specifies the control plane message's address which is determined by the source MME/SGSN. It is mandatory. For details, see IP Address.

TEID-C

This IE specifies the control plane message tunnel which is determined by the source MME/SGSN. It is mandatory. The target MME can include this tunnel endpoint identifier (TEID) in the GPRS tunneling protocol (GTP) header of all related control plane messages which are related to the requested bearer. For details, see TEID-C.

Target GCI

This IE identifies the target access for an SRVCC to GSM/Enhanced Data rates for GSM Evolution (EDGE) radio access network (GERAN) handover. It is optional. If the target side of a handover is a 2G network, the Target global cell identity (GCI) IE will be included in the GTP_MSG_SRVCC_PS_CS_REQ message. For details, see Target GCI. This IE identifies the international mobile subscriber identity (IMSI) of the subscriber. It is optional. It is included in the GTP_MSG_SRVCC_PS_CS_REQ message sent from the MME/SGSN except for the following cases:

IMSI

The equipment (UE) is emergency attached and it is UICCless (UICC refers to universal integrated circuit card). The UE is emergency attached and the IMSI is not authenticated. For details, see IMSI.


This IE identifies the mobile station international integrated services digital network (ISDN) number (MSISDN) of the subscriber. It is optional. It is included in the GTP_MSG_SRVCC_PS_CS_REQ message sent from the MME/SGSN except for the following cases: The UE is emergency attached and

it is UICCless. The UE is emergency attached and the IMSI is not authenticated. The MSISDN is defined in 3rd Generation Partnership Project (3GPP) TS 23.003 [4]. For details, see MSISDN.

STN-SR

This IE is included in the GTP_MSG_SRVCC_PS_TO_CS_REQ message if this session is not for an emergency call. It is optional. For details, see STN-SR.

Mobility management (MM) Context for EUTRAN SRVCC

The MME includes mobile station classmarks, ed codecs, and CS Security key in MM Context for SRVCC for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) SRVCC. This IE is optional. The derivation of the CS security keys shall follow the procedures defined 3GPP TS 33.401[7]. For details, see MM Context for E-UTRAN SRVCC.

Source to Target Transparent Container

This MME or SGSN includes Source to Target Transparent Container IE. This IE is mandatory. For details, see Source to Target Transparent Container.

Target RNC ID

This IE identifies the target access for SRVCC handover to Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN). It is optional. If the target side of a handover is a 3G network, the Target RNC ID IE is included in the GTP_MSG_SRVCC_PS_CS_REQ message. For details, see Target RNC ID.

Reference Standards For details, see 5.2.2 "SRVCC PS to CS Request" in 3GPP 29.280 V9.3.0.

Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_RSP Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_RSP message is sent by the mobile switching center (MSC) server to the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) over the Sv interface in response to the GTP_MSG_SRVCC_PS_TO_CS_REQ message during the Single Radio Voice Call Continuity (SRVCC) handover procedure. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_RSP message sent during an intra-MSC 3G

handover Associated IEs Information Element (IE)

Description

Cause

This IE specifies whether the GTP_MSG_SRVCC_PS_TO_CS_REQ message is accepted. If Cause is not Request accepted, the

GTP_MSG_SRVCC_PS_TO_CS_REQ message is rejected. It is mandatory. For details, see Cause.

SRVCC Cause

This IE specifies why the GTP_MSG_SRVCC_PS_TO_CS_REQ message is rejected if Cause is not Request accepted. It is optional. For details, see SRVCC Cause.

TEID-C

This IE is included in the GTP_MSG_SRVCC_PS_TO_CS_RSP message by the target MSC server if Cause is Request accepted. The source MME/SGSN includes this TEID-C in the GPRS Tunneling Protocol-Control plane (GTP-C) header of all subsequent uplink control plane messages from the source MME/SGSN to the target MSC servers. This IE is optional. For details, see TEID-C.

Target to Source Transparent Container

This IE is included to carry the Handover command from the target access network if Cause is Request accepted. It is optional. For details, see Target to Source Transparent Container.

Reference Standards For details, see 5.2.3 "SRVCC PS to CS Response" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF message is sent over the Sv interface to notify the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) that the Single Radio Voice Call Continuity (SRVCC) handover with the CS domain is successful. The SRVCC procedure is stipulated in 3GPP TS 23.216 [2]. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF message sent during an intra-MSC

3G handover Associated IEs Information Element (IE)

Description This IE indicates the international mobile subscriber identity (IMSI) of the subscriber. It is optional. It is included in the GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF message except for the following cases:

IMSI

The equipment (UE) is emergency attached and it is UICCless (UICC refers to universal

integrated circuit card). The UE is emergency attached and the IMSI is not authenticated. For details, see IMSI. Reference Standards For details, see 5.2.4 "SRVCC PS to CS Complete Notification" in 3GPP 29.280 V9.3.0. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK message is sent from the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) to the mobile switching center (MSC) server over the Sv interface in response to the GTP_MSG_SRVCC_PS_TO_CS_COMP_NTF message during the Single Radio Voice Call Continuity (SRVCC) handover procedure. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK message sent during an intra-

MSC 3G handover Associated IEs Information Element (IE)

Cause

Description This IE specifies whether the GTP_MSG_SRVCC_PS_TO_CS_REQ message is accepted. If Cause is not Request accepted, the GTP_MSG_SRVCC_PS_TO_CS_REQ message is rejected. It is mandatory.

For details, see Cause. Reference Standards For details, see 5.2.5 "SRVCC PS to CS Complete Acknowledge" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message is sent from the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) to the target mobile switching center (MSC) server over the Sv interface, requesting the cancelation of an ongoing Single Radio Voice Call Continuity (SRVCC) handover. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message sent during an intra-


Description

SRVCC Cause

This IE specifies the reason for the handover cancelation or rejection. It is mandatory. For details, see SRVCC Cause. This IE identifies the international mobile subscriber identity (IMSI) of the subscriber. It is

optional. It is included in the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message except for the following cases: IMSI

The equipment (UE) is emergency attached and it is UICCless (UICC refers to universal integrated circuit card). The UE is emergency attached and the IMSI is not authenticated. For details, see IMSI.

Reference Standards For details, see 5.2.6 "SRVCC PS to CS Cancel Notification" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

GTP_MSG_SRVCC_PS_TO_CS_CANCEL_ACK Message Function Associated IEs Reference Standards Message Function A GTP_MSG_SRVCC_PS_TO_CS_COMP_ACK message is sent from the mobile switching center (MSC) server to the source mobility management entity (MME) or the serving general packet radio service (GPRS) node (SGSN) over the Sv interface in response to the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message during the Single Radio Voice Call Continuity (SRVCC) handover procedure. Figure 1 shows the main information elements (IEs) in the message. Figure 1 GTP_MSG_SRVCC_PS_TO_CS_CANCEL_ACK message sent during an intra-


Description

Cause

This IE specifies whether the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message is accepted. If Cause is not Request accepted, the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message is rejected. It is mandatory. For details, see Cause.

Sv Flags

The Service trigger information (STI) flag in this IE is included if the MSC server triggers the IP multimedia subsystem (IMS) session transfer procedure. This IE is optional. For details, see Sv Flags.

Reference Standards For details, see 5.2.7 "SRVCC PS to CS Cancel Acknowledge" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Handover Management Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs STN-SR Source to Target Transparent Container Target to Source Transparent Container MM Context for E-UTRAN SRVCC SRVCC Cause Target RNC ID Target GCI TEID-C Sv Flags IMSI MSISDN IP Address Cause Parent topic: Sv Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

STN-SR Description of the IE Reference Standards Description of the IE Information Element (IE)

STN-SR

Description Is used for re-establishing remote session connected to the IP multimedia subsystem (IMS) domain. It is transferred through General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnels. The sending entity copies the value part of the STN-SR into the Value field of the STN-SR IE. Session Transfer Number (STN) is public telecommunication number defined in the E.164 encoding scheme and recommended by the International Telecommunication UnionTelecommunication Standardization Sector (ITU-T). It is used in the Single Radio Voice Call Continuity (SRVCC) PS to CS Request session. Session Transfer Number for SRVCC (STN-SR) is the STN allocated during the SRVCC.

The STN-SR IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, stn-sr is set to 21 43 65 12 34. After the sequence of the two numbers of each byte is reversed, the STN-SR "12 34 56 21 43" is obtained. Reference Standards For details, see 3rd Generation Partnership Project (3GPP) 23.003 [4].


Source to Target Transparent Container Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Includes radio access network (RAN) or base station subsystem (BSS) parameters that are necessary for the target RAN to set up radio bearers. When the target network is GSM/Enhanced Data rates for GSM Evolution (EDGE) radio access network (GERAN), this container carries the Old BSS to New BSS Information defined in 3rd Generation Partnership Project (3GPP) TS 48.008 [8]. When the target network is Universal Terrestrial Radio Access Network (UTRAN), this container carries the Source Radio Network Controller (RNC) to Target RNC Transparent Container IE defined in 3GPP TS 25.413 [9].

Source to Target Transparent Container length-of-transparent-container: specifies the length of transparent container. transparent-container: specifies the value of Source to Target Transparent Container IE. The Source to Target Transparent Container IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ

message is used as an example here. In this example, meanings of each parameter are as follows: length-of-transparent-container is set to 6: indicating that the length of the transparent container is 6. transparent-container is set to 01 00 01 01 80 01: indicating that the value of the Source to Target Transparent Container IE is 01 00 01 01 80 01. Reference Standards For details, see 6.3 "Source to Target Transparent Container" in 3GPP 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target to Source Transparent Container Description of the IE Reference Standards Description of the IE Information Element Description (IE) Contains the bearer information that is necessary for the equipment (UE) to access the target radio access network (RAN). When the target network is GSM/Enhanced Data rates for GSM Evolution (EDGE) radio access network (GERAN), this container carries the New business system (BSS) to Old BSS Information defined in 3rd Generation Partnership Project (3GPP) TS 48.008 [8]. When the target network is Universal Terrestrial Radio Access Network (UTRAN), this container carries the Target RNC to Source RNC Transparent Container IE defined in 3GPP TS 25.413 [9].

Target to Source Transparent Container

length-of-transparent-container: specifies the length of transparent container. transparent-container: specifies the value of Target to Source Transparent Container IE. The Target to Source Transparent Container IE in the GTP_MSG_SRVCC_PS_TO_CS_RSP message is used as an example here. In this example, meanings of each parameter are as follows: length-of-transparent-container is set to 46: indicating that the length of the transparent container is 46. transparent-container is set to 84 B7 E4 00 00 56 A8 00 A3 0C 7C 5E 84 80 23 57 9A 88 08 0C 90 00 99 88 A9 D8 8E 47 47 04 52 FB 66 7C E0 08 64 54 26 02 00 60 01 02 04 00: indicating that the value for the Target to Source Transparent Container IE is 84 B7 E4 00 00 56 A8 00 A3 0C 7C 5E 84 80 23 57 9A 88 08 0C 90 00 99 88 A9 D8

8E 47 47 04 52 FB 66 7C E0 08 64 54 26 02 00 60 01 02 04 00. Reference Standards For details, see 6.4 "Target to Source Transparent Container" in 3GPP 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MM Context for E-UTRAN SRVCC Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains Mobile Station Classmarks, ed codec list, and the security parameters that are necessary for the mobile switching center (MSC) server to set up the ciphering connection (and integrity protection for 3G) with the target access for Single Radio Voice Call Continuity (SRVCC). In addition, it carries CS ciphering keys parameters: CKSRVCC, IKSRVCC, and eKSI for Evolved Universal Terrestrial Radio Access Network (EUTRAN) SRVCC which are defined in 3rd Generation Partnership Project (3GPP) TS 33.401 [6]. Mobile Station Classmark 2, Mobile Station Classmark 3, and ed codec list IEs indicate the ed encryption algorithm for GSM/Enhanced Data rates for GSM Evolution (EDGE) radio access network (GERAN) access and CS ed codec. The coding of Mobile Station Classmarks and ed codec list fields include the IE value part as it is specified in 3GPP TS 24.008 [7].

Mobility management (MM) Context for E-UTRAN SRVCC

eksi: integrity mode information. It indicates whether the mobility management entity (MME) transfers a valid security context to the MSC server. If the value for eksi is between 0 and 6, ck and ik are valid. Otherwise, ck and ik are invalid. ck (Cipher Key): 3G encryption parameter. ik (Integrity Key): 3G encryption parameter. length-of-classmark2: specifies the length of Mobile Station Classmark 2. mobile-station-classmark2: specifies the Mobile Station Classmark type. length-of-classmark3: specifies the length of Mobile Station Classmark 3. mobile-station-classmark3: specifies the Mobile Station Classmark type. length-of-codec-list: specifies the length of codec list. ed-codec-list: specifies the ed codec list. The MM Context for E-UTRAN SRVCC IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, meanings of each parameter are as follows: eksi is set to 6: indicating that ck and ik are valid. ck is set to 76 DB 58 56 F9 76 2C D7 EC 20 79 EB 52 B3 8D BE: indicating that the 3G encryption information is 76 DB 58 56 F9 76 2C D7 EC 20 79 EB 52 B3 8D BE. ik is set to 05 A5 24 2D 5E D2 38 16 B0 C9 E4 46 65 9C 56 EA: indicating that the 3G encryption information is 05 A5 24 2D 5E D2 38 16 B0 C9 E4 46 65 9C 56 EA.

length-of-classmark2 is set to 3: indicating that the length of Mobile Station Classmark 2 is 3. mobile-station-classmark2 is set to 01 00 81: indicating that the value for Mobile Station Classmark 2 is 01 00 81. length-of-classmark3 is set to 12: indicating that the length of Mobile Station Classmark 3 is 12. mobile-station-classmark3 is set to 12 11 11 11 11 11 11 11 11 11 11 11: indicating that the value for Mobile Station Classmark 3 is 12 11 11 11 11 11 11 11 11 11 11 11. length-of-codec-list is set to 8: indicating that the length of codec list is 8. ed-codec-list is set to 00 02 1F 00 04 02 60 04: indicating that the ed codec list is 00 02 1F 00 04 02 60 04. Reference Standards For details, see 3GPP 33.401 [6]. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SRVCC Cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Specifies the reason for canceling or denying the GTP_MSG_SRVCC_PS_TO_CS_REQ message.

SRVCC Cause The Single Radio Voice Call Continuity (SRVCC) Cause IE in the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_NTF message is used as an example here. In this example, srvcc-cause-value is set to 5, indicating an unknown target ID 5. Table 1 shows the meanings of SRVCC Cause values. Table 1 SRVCC Cause values Cause Value Meaning (decimal) 0

Reserved. Shall not be sent and if received the Cause shall be treated as an invalid IE.

1

Unspecified.

2

Handover/Relocation canceled by source system.

3

Handover /Relocation Failure with Target system.

4

Handover/Relocation Target not allowed.

5

Unknown Target ID.

6

Target Cell not available.

7

No Radio Resources Available in Target Cell.

8

Failure in Radio Interface Procedure.

9-255

Spare. This value range is reserved for SRVCC Cause values.

Reference Standards For details, see 6.7 "SRVCC Cause" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target RNC ID Description of the IE Reference Standards Description of the IE IE

Description If the target side of a handover is a 3G network, the GTP_MSG_SRVCC_PS_TO_CS_REQ message will include this information element (IE) containing the identity of the target RNC. The encoding of this IE is defined in 3rd Generation Partnership Project (3GPP) TS 29.002 [11] TS 29.002 [11].

Target RNC ID

The Target RNC ID IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. For the encoding of rnc-id as shown in the previous diagram, see Target ID. Where, LAI is 64 F0 00 01 73 and RNC ID is 00 59. Reference Standards For details, see 6.8 "Target RNC ID" in 3GPP 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Target GCI Description of the IE Reference Standards Description of the IE IE

Description If the target side of a handover is a 2G network, the GTP_MSG_SRVCC_PS_TO_CS_REQ message will include the Target Global Cell ID (GCI) information element (IE) containing the identity of the target Global System for Mobile Communications (GSM) Cell ID. The encoding of this IE is defined in 3rd Generation Partnership Project (3GPP) TS 29.002 [11].

Target GCI

The Target GCI IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message when the target side is a 3G network is used as an example here. In this example, cell-id is set to 00, indicating that the Target GCI ID is invalid. Reference Standards For details, see 3GPP 29.002 [11]. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TEID-C Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the Tunnel Endpoint Identifier for Control Plane (TEID-C).

TEID-C

The GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, teid is set to 10000003. Reference Standards For details, see 6.10 "Tunnel Endpoint Identifier for Control Plane (TEID-C)" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Sv Flags Description of the IE Reference Standards Description of the IE IE

Description This information element (IE) is optional.

Sv Flags

EmInd (Emergency Indicator): indicates the IP multimedia subsystem (IMS) emergency session. ICS (IMS Centralized Service): is used to request IMS Centralized Service (ICS) . STI (Session Transfer Indicator): indicates whether the IMS session transfer has been invoked. The Sv Flags IE in the GTP_MSG_SRVCC_PS_TO_CS_CANCEL_ACK message is used as an example here. In this example, meanings of each parameter are as follows: emind is set to 0: indicating that the IMS emergency session is not ed. ics is set to 0: indicating that requesting ICS is not ed. sti is set to 1: indicating that the IMS session transfer has been invoked.

Reference Standards

For details, see 6.11 "Sv Flags" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Identifies the international mobile subscriber identity (IMSI) of the subscriber.

IMSI

The IMSI IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, imsi is set to 64 00 20 00 10 88 14 F9. After the sequence of the two numbers of each byte is reversed, the IMSI "46 00 02 00 01 88 41 9" of the subscriber is obtained. In this value, F is invalid and should not be considered.

Reference Standards For details, see 3rd Generation Partnership Project (3GPP) 29.274 [3]. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MSISDN Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the mobile station international ISDN number (MSISDN) of the subscriber.

MSISDN

The MSISDN IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, msisdn is set to 68 31 83 29 85 14 F9. After the sequence of the two numbers of each byte is reversed,, the MSISDN "86 13 38 92 58 41 9" of the subscriber is obtained. In this value, F is invalid and should not be considered.

Reference Standards For details, see 3rd Generation Partnership Project (3GPP) 29.274 [3]. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IP Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Specifies the control plane message's address which is determined by the source mobility management entity (MME) or the serving GPRS node (SGSN).

IP Address The IP Address IE in the GTP_MSG_SRVCC_PS_TO_CS_REQ message is used as an example here. In this example, ipaddr is set to A1 42 01 9F, which is a hexadecimal number. After the value is converted to a decimal equivalent, the IP address "161.66.1.159" for control plane message is obtained. Reference Standards For details, see 5.2.2 "SRVCC PS to CS Request" in 3rd Generation Partnership Project (3GPP) 29.280 V9.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Specifies whether the GTP_MSG_SRVCC_PS_TO_CS_REQ message is accepted.

cause: specifies whether the GTP_MSG_SRVCC_PS_TO_CS_REQ message is accepted. cs (Cause Source): specifies whether the local mobile switching center (MSC) server or the peer MSC server generates the cause value. Value: 1: The incorrect cause value is generated by peer network elements (NEs). 0: The incorrect cause value is generated by local NEs. bce (Bearer Context IE Error): specifies whether the Single Radio Voice Call Continuity (SRVCC) PS to CS handover rejection is caused by Bearer Context IE error. Value:

Cause

1: The SRVCC PS to CS handover rejection is caused by Bearer Context IE error. 0: The SRVCC PS to CS handover rejection is not caused by Bearer Context IE error. pce (PDN Connection IE Error): specifies whether the SRVCC PS to CS handover rejection is caused by packet data network (PDN) Connection IE Error. Value: 1: The SRVCC PS to CS handover rejection is caused by PDN Connection IE Error. 0: The SRVCC PS to CS handover rejection is not caused by PDN Connection IE Error. The Cause IE in the GTP_MSG_SRVCC_PS_TO_CS_RSP message is used as an example here. In this example, meanings of each parameter are as follows: cause is set to 6: indicating that the SRVCC PS to CS Request is accepted. cs is set to 0: indicating that the incorrect cause value is generated by local NEs. bce is set to 0: indicating that the SRVCC PS to CS handover rejection is not caused by Bearer Context IE error. pce is set to 0: indicating that the SRVCC PS to CS handover rejection is not caused by PDN Connection IE Error.

Reference Standards For details, see 3rd Generation Partnership Project (3GPP) 29.274 [3]. Parent topic: Description of Associated IEs


H.248 Protocol Description of the H.248 Protocol Extended 3GPP-based H.248 Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the H.248 Protocol Scenario Description Protocol Stack Message Structure IE Structure Message List Reference Standards In the 3rd Generation Partnership Project (3GPP) R4 core network, the control plane is separated from the bearer plane. The H.248 protocol is applied to the Mc interface between the control plane and the bearer plane. Using the H.248 protocol, the MGC controls the bearer resources on the MGW and the MGW notifies the MGC of the bearer status. Scenario Description Major scenarios of interaction between the MGC and the MGW are as follows: 1. The MGC notifies the MGW to allocate the bearer resource. 2. The MGC notifies the MGW to modify the attributes of the bearer resource. 3. The MGC notifies the MGW to release the bearer resource. 4. The MGW notifies the MGC of the status change of the MGW. 5. The MGW notifies the MGW of the occurrence of the bearer-specific events. 6. The MGC audits the bearer resource status of the MGW. Protocol Stack The H.248 protocol can be carried over either IP or asynchronous transfer mode (ATM). The IP networking mode is generally used. Figure 1 shows the protocol stack of the H.248 protocol carried over IP.

Figure 1 Protocol stack of the H.248 protocol carried over IP Message Structure The H.248 messages are encoded in a binary format or in a text format. When the binary format is used, the H.248 messages comply with the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) X.680 (ASN.1) specification and are encoded in accordance with X.690-specified basic encoding rule (BER) rules. When the text format is used, the H.248 messages comply with the RFC 2234 ABNF specification. An H.248 message contains one or more transactions, a transaction contains one or more actions, and an action contains one or more commands. A command contains one or more parameters that are defined and described by descriptors and packets. Figure 2 shows the hierarchical structure of the H.248 message. Figure 2 Hierarchical structure of the H.248 message

IE Structure Figure 3 shows the IE Structure of the H.248 message. Figure 3 IE Structure

Message List Table 1 describes seven pairs of H.248 messages. Table 1 List of H.248 messages Message Direction Function ADD REQ

MGC>MGW

Requests the MGW to add a termination to a context.

ADD REPLY

MGW>MGC

Responds to the ADD REQ message.

NTFY REQ

MGW>MGC

Notifies the occurrence of events in the MGW.

NTFY REPLY

MGC>MGW

Responds to the NTFY REQ message.

MOD REQ

MGC>MGW

Requests the MGW to modify the properties, events, or signals of a termination.

MOD REPLY

MGW>MGC

Responds to the MOD REQ message.

SUB REQ

MGC>MGW

Requests the MGW to remove a termination from a context.

SUB REPLY

MGW>MGC

Responds to the SUB REQ message.

MOV REQ

MGC>MGW

Requests the MGW to move a termination from one context to another context.

MOV REPLY

MGW>MGC

Responds to the MOV REQ message.

AUDIT VAL REQ

MGC>MGW

Requests the MGW to return the current state of properties, events, signals and statistics of terminations.

AUDIT VAL REPLY

MGW>MGC

Responds to the AUDIT VAL REQ message.

ServiceChange REQ

MGC<>MGW

Instructs the MGW to take a termination or group of terminations in or out of service. Notifies the MGC that a termination or group of terminations is about to be taken out of service or has just returned to service.

ServiceChange REPLY

MGC<>MGW

Responds to the ServiceChange REQ message.

Reference Standards For details about the H.248 protocol, see ITU-T H.248 versions. Parent topic: H.248 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Extended 3GPP-based H.248 Protocol Application Scenarios Interaction with Other Protocols Packages of the Extended 3GPP-based Protocol feature Protocol Reference The Extended 3GPP-based H.248 Protocol feature enables the medial gateway controller (MGC) to control bearer resources on the media gateway (MGW) and enables the MGW to notify the MGC of the bearer status. It is designed based on the H.248/MEGACO protocol defined by the ITU-T/IETF. It applies to the Mc interface between control and bearer planes on the 3rd Generation Partnership Project (3GPP) R4 network for which control and bearer are separated. Application Scenarios This feature applies to the following H.248–ed scenarios: The MGC instructs the MGW to allocate bearer resources. The MGC instructs the MGW to modify bearer resources. The MGC instructs the MGW moves a termination from one context to another context. The MGC instructs the MGW to release bearer resources. The MGW notifies the MGC of its status change. The MGW notifies the MGC of an bearer event. The MGC audits the status of MGW bearer resources. The MGC audits attributes information of MGW terminations. Interaction with Other Protocols This feature adds multiple applications to the application layer of the H.248 protocol by expanding protocol packages described in Packages of the Extended 3GPP-based Protocol feature. Multiple 3GPP protocols and Q.1950 are involved in implementing this feature. For example, Iu and Nb interfaces comply with the 3GPP TS 25.415 protocol. For details about the new applications and their application scenarios, see the reference list in the 3GPP TS 29.232 protocol. Packages of the Extended 3GPP-based Protocol feature

Table 1 describes the packages of the Extended 3GPP-based Protocol feature. Table 1 Packages of the Extended 3GPP-based Protocol feature Package Name Description 3GUP package:threegup (0x002f)

Specifies the operation mode on the plane (Iu and Nb interfaces).

Circuit Switched Data package:threegcsd (0x0030)

Negotiates circuit switched (CS) data services on the GSM or UMTS network.

TFO package:threegtfoc (0x0031)

Implements the tandem free operation (TFO) function to reduce the number of encoding and decoding times in the voice stream.

Trace package:calltrace (0x0097)

Activates or deactivates MGW tracing tasks.

Protocol Reference For details about the Extended 3GPP-based H.248 Protocol feature, see 3GPP 29.232 protocols. Parent topic: H.248 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 describes the IEs carried in the common part of messages. Table 1 the Common Part of Messages Information Element (IE)

Description Indicates the version of the H.248 protocol used by the message sender.

Version

Represents the message identifier.

mid

For details about the common part of messages, see H.248 Message Header. Parent topic: H.248 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages ADD REQ ADD REPLY NTFY REQ NTFY REPLY MOD REQ MOD REPLY SUB REQ SUB REPLY MOV REQ MOV REPLY AUDIT VAL REQ AUDIT VAL REPLY ServiceChange REQ ServiceChange REPLY Parent topic: H.248 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ADD REQ Message Function Associated IEs Message Function The ADD REQ message is used to add a termination to a context. If the MGC does not specify an existing context by setting contextId to 0xfffffffe, the MGW creates a context. Figure 1 shows important IEs in the ADD REQ message.

Figure 1 ADD REQ message Associated IEs Information Element (IE)

Description Every H.248 message contains a header.

H.248 message header

For details, see H.248 Message Header. transactions

One or more transactions constitute an H.248 message. For details, see transactions.

actions

One or more actions constitute a transaction. For details, see actions.

context

One context maps to only one action. For details, see context.

command

One or more commands constitute an action. For details, see command.

termination

A termination receives or sends streams. For details, see termination.

descriptor

A descriptor describes the parameters in commands. For details, see descriptor.

Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ADD REPLY Message Function Associated IEs Message Function The ADD REPLY message is used to respond to the ADD REQ message. If the ADD command fails, the MGW includes error information in the ADD REPLY message. If the ADD command is successful, the MGW includes the context and termination information in the ADD REPLY message. Figure 1 shows important IEs in the ADD REPLY message.

Figure 1 ADD REPLY message Associated IEs Information Element (IE)

Description


Every H.248 message contains a header. For details, see H.248 Message Header.

transactions


actions


context


command


termination


descriptor



NTFY REQ Message Function Associated IEs Message Function The NTFY REQ message is used to inform the MGC of the occurrence of events in the MGW. Common events are as follows: g-Cause: indicates the asynchronous transfer mode (ATM) or IP termination state and the bearer state. g-SignalComplet: completion of signals tonedet-std: detection of dual tone multiple frequency (DTMF) signals gB-BNCChange: bearer change bT-TunnelInd: tunnel indication Figure 1 shows important IEs in the NTFY REQ message.

Figure 1 NTFY REQ message Associated IEs Information Element (IE)

Description



transactions


actions


context


command


termination


descriptor



NTFY REPLY Message Function Associated IEs Message Function The NTFY REPLY is used to respond to the NTFY REQ message. Figure 1 shows important IEs in the NTFY REPLY message.

Figure 1 NTFY REPLY message Associated IEs Information Element (IE)

Description



transactions


actions

One or more actions constitute a transaction.

For details, see actions. context


command


termination



MOD REQ Message Function Associated IEs Message Function The MOD REQ message is used to modify the properties, events, or signals (tones for example) of a termination. As the MOD REQ message is used only for existing terminations, wildcards are not allowed to represent a termination ID. Figure 1 shows important IEs in the MOD REQ message.

Figure 1 MOD REQ message


Description



transactions


actions


context


command


termination


descriptor



MOD REPLY Message Function Associated IEs Message Function The MOD REPLY message is used to respond to the MOD REQ message. If the MOD command fails, the MGW includes error information in the MOD REPLY message. Figure 1 shows important IEs in the MOD REPLY message.

Figure 1 MOD REPLY message Associated IEs Information Element (IE)

Description



transactions


actions


context


command


termination



SUB REQ Message Function Associated IEs Message Function The SUB REQ message is used to remove a termination from a context. After the last termination is removed from the context, the MGW releases the context. Figure 1 shows important IEs in the SUB REQ message.

Figure 1 SUB REQ message Associated IEs Information Element (IE)

Description



transactions


actions


context


command


termination



SUB REPLY Message Function Associated IEs Message Function The SUB REPLY message is used to respond to the SUB REQ message. If the SUB command fails, the MGW includes error information in the SUB REPLY message. Figure 1 shows important IEs in the SUB REPLY message.

Figure 1 SUB REPLY message Associated IEs


Description



transactions


actions


context


command


termination


descriptor



MOV REQ Message Function Associated IEs Message Function The MOV REQ message is used to request the MGW to move a termination from one context to another context. The contextId identifies the context to which the termination is moved. Its value 0xfffffffe indicates that the MGW is required to create a new context. Figure 1 shows important IEs in the MOV REQ message.

Figure 1 MOV REQ message Associated IEs Information Element (IE)

Description


Every H.248 message contains a header. For details, see H.248 Message Header. One or more transactions constitute an H.248 message.

transactions

For details, see transactions.

actions


context


command


termination


descriptor

It describes the parameters in commands. For details, see descriptor.


MOV REPLY Message Function Associated IEs Message Function The MOV REPLY message is used by the MGW to respond to the MOD REQ message. If the MOV command fails, the MGW includes error information in the MOV REPLY message. If the MOV command is successful, the MGW includes the context and termination information in the MOV REPLY message. Figure 1 shows important IEs in the MOV REPLY message.

Figure 1 MOV REPLY message Associated IEs Information Element (IE)



For details, see H.248 Message Header.

transactions


actions


context


command


termination


descriptor



AUDIT VAL REQ Message Function Associated IEs Message Function The AUDIT VAL REQ message is used to return the current state of properties, events, signals and statistics of terminations or request the contents of a descriptor or of a single property, event, signal or statistic. Figure 1 shows important IEs in the AUDIT VAL REQ message.

Figure 1 AUDIT VAL REQ message Associated IEs Information Element (IE)

Description



transactions


actions


context


command


termination


descriptor



AUDIT VAL REPLY Message Function Associated IEs Message Function The AUDIT VAL REPLY message is used to respond to the AUDIT VAL REQ message. Figure 1 and Figure 2 shows important IEs in the AUDIT VAL REPLY message.

Figure 1 AUDIT VAL REPLY message Figure 2 AUDIT VAL REPLY message


Description



transactions


actions


context


command

One or more commands constitute an action. For details, see command. A termination receives or sends streams.

termination

For details, see termination.

descriptor



ServiceChange REQ Message Function Associated IEs Message Function The ServiceChange REQ message is used by: MGW to notify the MGC that a termination or a group of terminations is about to be taken out of service or has just returned to service. MGW to announce its availability to the MGC (registration) and notify the MGC of impending or completed restart of the MGW. MGC to announce a handover to the MGW. MGC to instruct the MGW to take a termination or a group of terminations in or out of service. Figure 1 shows important IEs in the ServiceChange REQ message.

Figure 1 ServiceChange REQ message Associated IEs Information Element (IE)

Description



transactions


actions


context


command


termination


descriptor



ServiceChange REPLY Message Function Associated IEs Message Function The ServiceChange REPLY message is used by the MGW or MGC to respond to the ServerChange REQ message. Figure 1 shows important IEs in the ServiceChange REPLY message.

Figure 1 ServiceChange REPLY message Associated IEs Information Element (IE)



For details, see H.248 Message Header.

transactions


actions


context


command


termination


descriptor



Description of Associated IEs H.248 Message Header transactions actions context command termination descriptor tateDescr localControlDescriptor localDescriptor remoteDescriptor signalsDescriptor eventsDescriptor observedEventsDescriptor auditDescriptor serviceChange statisticsDescriptor errorDescriptor Parent topic: H.248 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

H.248 Message Header Description of the IE Reference Standards The H.248 protocol named by International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) is also known as media gateway controller (MeGaCo) named by Internet Engineering Task Force (IETF). It is a combination of the H.323 protocol defined by ITU-T and the Media Gateway Control Protocol (MG) protocol defined by IETF. The H.248 message header consists of the protocol version and message identifier (mid). When the MGC interworks with the MGW, the H.248 entity, either MGC or MGW, uses the same mid for all messages it sends out. The mid can be an IP address, domain name, or device name; the IP address is generally used as the mid. Description of the IE Information Element Description (IE)

ADD REQ H.248 message header unitemessagetpye: The value standardmessage indicates a standard message type. version: The value 1 indicates the H.248 version number.

Presently, the MGW s versions 1 and 2, but not version 3. address: The value 50 01 01 2D indicates that the Internet Protocol version 4 (IPv4) address is 80.1.1.45 in decimal notation. portNumber: The value 0xbd0 indicates that the port number is 3024 in decimal notation. The mid of the message sender MGC is the destination IP address used in the man-machine language (MML) command ADD H248LNK for configuring the H.248 link on the MGW.

ADD REPLY H.248 message header

unitemessagetype: The value standardmessage indicates a standard message type. version: The value 1 indicates the H.248 version number. address: The value 50 3C 19 0A indicates that the IPv4 address is 80.60.25.10 in decimal notation. portNumber: The value 0xbd0 indicates that the port number is 3024 in decimal notation. The mid of the message sender MGW is Virtual media gateway id preset in the SET VMGW command.

It is recommended that Virtual media gateway id be set in the format of "IP address + port number" as used in ADD H248LNK. This IP address, which is used for signaling forwarding, is configured on the operation and maintenance center (OMC) interface of the MPU board in the service frame when three SSM-32 frames are cascaded.

Reference Standards For details about contexts, see section 8.3 "Contexts" in ITU-T H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

transactions Description of the IE Reference Standards An H.248 message consists of one or more transactions, each of which is identified by a transactionid. Transactions consist of one or more actions. Commands in a transaction are executed in sequence. If a command in a transaction fails, the following commands in the same transaction are no longer executed. Transactions are presented as TransactionRequests. Corresponding responses to a TransactionRequest are received in a single reply (transactionReply). Description of the IE Information Element (IE)

Description

ADD REQ transactions transactionRequest: It is used in the ADD REQ message to initiate a new transaction. transactionid: The value 0x80000075 indicates that the transactionid is 2147483765.

ADD REPLY transactions transactionReply: It responds to the transactionRequest in

the ADD REQ message. transactionid: It is the same as the transactionid in the ADD REQ message, 2147483765. transactionResult: indicates the transaction result.

NTFY REQ transactions transactionRequest: It is used in the NTFY REQ message to initiate a new transaction. transactionid: The value 0x9e40055e indicates that the transactionid is 2654995806.

NTFY REPLY transactions transactionReply: It responds to the transactionRequest in the NTFY REQ message. transactionid: It is the same as the transactionid in the NTFY REQ message, 2654995806. transactionResult: indicates the transaction result. Reference Standards For details about transactions, see section 8 "Transactions" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs


actions Description of the IE Reference Standards One or more actions constitute a transaction. Each action typically specifies a contextId and consists of a series of commands. Commands in an action are executed in sequence. An action is initiated by an ActionRequest, which is responded with an ActionReply. Description of the IE Information Element (IE)

Description

ADD REQ actions

ActionRequest: The ActionRequest in the ADD REQ message initiates an action. contextId: The value 0xfffffffe indicates creation of a context. For details, see context. CommandRequest: The CommandRequest in an action initiates a command.

ADD REPLY actions

ActionReply: It responds to the ActionRequest in the ADD REQ message. contextId: The value 0x1e012e indicates that the contextId assigned by the MGW is 1966382. For details, see context. CommandReply: It responds to the CommandRequest.

NTFY REQ actions ActionRequest: The ActionRequest in the NTFY REQ message initiates an action. contextId: The value 0x1e012e indicates the contextId 1966382. For details, see context. CommandRequest: The CommandRequest in an action initiates a command. Reference Standards For details about actions, see section 8 "Transactions" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

context Description of the IE Reference Standards A context maps to an action and is identified by a contextId. A context is an association between a number of terminations. It describes the topology (who hears/sees whom) as well as the media mixing and switching parameters if more than two terminations are involved in the association. Description of the IE Information Element (IE)

Description

contextId: The value 0xfffffffe (4294967294 in decimal notation) is a CHOOSE wildcard, indicating that the MGC requests the MGW to create a context. contextId, 32-bit identifier, is unique within the scope of the MGW. The other values are as follows: 0xffffffff: The ALL wildcard identifies all contexts on the MGW. 0: The NULL value indicates the NULL context containing all terminations that are not added to any specific context. Specific values: Identify the contexts that have been created by the MGW.

ADD REQ context

contextRequest: Contains context properties. priority: The value 0 indicates priority level 0. The value ranges from 0 to 15; a smaller value indicates a higher priority level. NOTE:

If a termination is to be added to an existing context, the ADD REQ message must contain a specific contextId. Otherwise, the contextId is 0xfffffffe.

ADD REPLY context contextId: The value 0x1e012e indicates that the contextId assigned by the MGW is 1966382. Reference Standards For details about contexts, see section 6.1 "Contexts" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

command Description of the IE Reference Standards The command consists of the termination ID field and the descriptor field. The descriptor field contains various parameters in the command. Commands are usually executed in pairs. The CommandRequest in an action initiates a command and the CommandReply responds to the CommandRequest. Description of the IE Information Element (IE)

Description

ADD REQ command

addReq: It is used to add a termination to a context. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination. descriptors: For details, see descriptor.

ADD REPLY command

addReply: It is used to respond to the ADD REQ message. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination. terminationAudit: It is used to return the terminal audit information. For details, see descriptor.

NTFY REQ command notifyReq: It is used to notify the MGC of the occurrence of events in the MGW. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination. observedEventsDescriptor: It is used to inform the MGC of which events were detected. For details, see observedEventsDescriptor.

NTFY REPLY command

notifyReply: It is used to respond to the NTFY REQ message. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination.

AUDIT VAL REQ command auditValueRequest: It is used to return the current state of properties, events, signals, and statistics of terminations. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination. auditDescriptor: For details, see auditDescriptor.

AUDIT VAL REPLY command

auditValueReply: It is used to respond to the AUDIT VAL REQ message. For details on more commands, see Description of the H.248 Protocol. terminationID: For details, see termination. errorDescriptor: For details, see errorDescriptor.

terminationID: For details, see termination. tateDescr: For details, see tateDescr. localControlDescriptor: For details, see

localControlDescriptor. Reference Standards For details about the command, see section 7 "Commands" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

termination Description of the IE Reference Standards A termination is a logical entity on the MGW that receives and sends media streams and control streams. A termination is described by a number of characterizing properties, which are grouped in a set of descriptors that are included in commands. Terminations have unique identities (terminationID), assigned by the MGW at the time of their creation. Description of the IE Information Element (IE)

Description

ADD REQ termination wildcard: indicates whether wildcards can be used as termination IDs. WildcardField: The value 7F indicates the ALL wildcard. id: The value of all 0s indicates that the MGW is required to assign an ephemeral termination.

ADD REPLY termination

wildcard: No wildcard indicates a specified termination. id: The value 00 00 00 00 20 1E 00 7F indicates an assigned termination ID. The rules for asg termination IDs between the

MSOFTX3000 and the UMG8900 are as follows: 00 00 00 00 2X XX XX XX: indicates asynchronous transfer mode (ATM) terminations. 00 00 00 00 3X XX XX XX: indicates IP terminations. 00 00 00 00 4X XX XX XX: indicates time division multiplexing (TDM) terminations. 00 00 00 00 5F XX XX XX: indicates Dummy terminations for audio playback.

ADD REPLY (IP termination) termination wildcard: No wildcard indicates a specified termination. id: The value 00 00 00 00 30 00 04 1F indicates an assigned termination ID.

contextId: The value is 0xffffffff. id: The value 00 00 00 00 40 00 00 5F indicates the nonNULL context to which the to-be-audited termination is

AUDIT VAL REQ termination

added.

contextId: The value is 0. id: The value 00 00 00 00 40 00 00 5F indicates the to-beaudited terminations that do not belong to any specific contexts.

ServiceChange REQ termination

contextId: The value is 0. id: The value FF FF FF FF FF FF FF FF indicates a root termination; the ServiceChange command is effective on the entire MGW. Reference Standards For details about terminations, see section 6.2 "Terminations" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

descriptor Description of the IE Reference Standards A descriptor is a syntactic element of the protocol that groups related properties. A descriptor has a name and contains a list of parameters. Figure 1 shows the structure of descriptors.

Figure 1 Descriptors Description of the IE


Description

ADD REQ descriptor

mediaDescriptor: Lists media stream specifications. streams: Lists Remote/Local/LocalControl Descriptors for streams. localControlDescriptor: For details, see localControlDescriptor. localDescriptor: For details, see localDescriptor. eventsDescriptor: For details, see eventsDescriptor.

ADD REPLY descriptor

terminationAudit: Returns termination information. mediaDescriptor: Lists media stream specifications. localDescriptor: For details, see localDescriptor.

NTFY REQ

descriptor

observedEventsDescriptor: For details, see observedEventsDescriptor.

ADD REPLY (IP termination) descriptor

mediaDescriptor: Lists media stream specifications. tateDescr: For details, see tateDescr. streams: Lists Remote/Local/LocalControl Descriptors for streams. localControlDescriptor: For details, see localControlDescriptor. localDescriptor: For details, see localDescriptor. eventsDescriptor: For details, see eventsDescriptor.

MOD REQ descriptor

mediaDescriptor: Lists media stream specifications. streams: Lists Remote/Local/LocalControl Descriptors for streams. remoteDescriptor: For details, see remoteDescriptor. eventsDescriptor: For details, see eventsDescriptor. signalsDescriptor: For details, see signalsDescriptor.

SUB REPLY descriptor terminationAudit: Returns termination information. statisticsDescriptor: For details, see statisticsDescriptor.

AUDIT VAL REQ descriptor

auditDescriptor: For details, see auditDescriptor.

errorDescriptor: For details, see errorDescriptor.

AUDIT VAL REPLY descriptor

tateDescr: For details, see tateDescr. localControlDescriptor: For details, see localControlDescriptor.

ServiceChange REQ descriptor

serviceChangeParms: For details, see serviceChange. Reference Standards For details about contexts, see section 7.1 "Contexts" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

tateDescr Description of the IE Reference Standards The tateDescr contains the termination properties that are defined in packages and are not stream specific. Description of the IE Information Element (IE)

Description

name: The name emp-ip-interface indicates a logical interface corresponding to an IP address. value: The value 0 indicates that the logical interface is numbered 0. IP-interface is defined in the Middlebox Package.

ADD REQ (IP termination) tateDescr

traceid: indicates the trace ID. traceinfo: Provides information. cmode: indicates the communication mode. muxlv: indicates the highest multiplexing level. traceid and traceinfo are defined in the Trace Package. cmode and muxlv are defined in the H324 Package

AUDIT VAL RLY tateDescr

serviceState: The value inSvc indicates that the termination is inservice and functioning normally. The other values are as follows:

outOfSvc: The termination is out-of-service and not available for traffic. test: The termination is undergoing testing. Reference Standards For details about the tateDescr, see section 7.1.5 "TerminationState Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the Middlebox Package, see section 4 in European Telecommunications Standards Institute (ETSI) TS101332. The Trace Package is used for fullflow call trace between the MGW and the MGC. For details about the H324 Package, see section 4 in ITU-T H.248.12. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

localControlDescriptor Description of the IE Reference Standards The localControl Descriptor contains the streamMode, reserveValue, and reserveGroup properties and properties of a termination (defined in packages) that are stream specific. The streamMode indicates the current service state of the termination. The reserveValue and reserveGroup indicate how the MGW behaves after receiving the localDescriptor or remoteDescriptor. Description of the IE Information Element Description (IE)

streamMode: The value sendRecv indicates that the media stream can be received and sent. reserveValue: The value FALSE indicates that the MGW is to reserve a single set of property values from those indicated in the selected media group. reservGroup: The value FALSE indicates that the MGW is to reserve a single media group from each of the localDescriptor and the remoteDescriptor.

name: The name b-BNCChar indicates the characteristics of the added termination, that is, bearer type of the media stream. value: The value aal2 indicates that ATM transport is used because the added termination is an ATM termination. BNCChar: Backbone Network Connection Characteristics, which is defined in the Bearer Characteristics Package. The other value can be IP/RTP, indicating that IP transport is used because the added termination is an IP termination.

name: The name p3gUP-mode indicates the up mode. value: The value supp indicates the mode. mode: It is defined in the 3G UP Package (UP refers to Plane). The values are as follows: trans: indicates the Transparent mode. supp: indicates the mode for predefined service distribution unit (SDU) sizes.

ADD REQ(asynchronous transfer mode (ATM) termination) localControlDescriptor

name: The name p3gUP-DelErrSDU indicates how erroneous SDUs are handled. value: The value yes indicates performing error check and setting frame quality classification.

DelErrSD: delivery of erroneous SDUs, which is defined in the 3G UP Package. The other value no indicates performing error check and discarding the corrupted frame detected.

name: The name p3gUP-interface indicates the type of the interface to which the termination is applied. value: The value ran indicates that the termination is applied to the RAN (Iu interface). interface: It is defined in the 3G UP Package. The other value cn indicates that the termination is applied to the CN (Nb interface).

name: The name p3gUP-initDir indicates the UP initialization direction. value: The value in indicates that the termination receives UP initialization initiated by the peer end. initDir: initialization direction, which is defined in the 3G UP Package. The other value out indicates that the termination initiates UP initialization.

name: The name version indicates the version number of the ed UP protocol. value: The values are version1 ( the trans mode) and version2 ( the supp mode). version is defined in the 3G UP Package. For details about the UP protocol, see Description of the IU_UP/NB_UP Protocol.

streamMode: The value sendRecv indicates that the media stream can be received and sent. reserveValue: The value FALSE indicates that the MGW is to reserve a single set of property values from those indicated in the selected media group. reservGroup: The value FALSE indicates that the MGW is to reserve a single media group from each of the localDescriptor and the remoteDescriptor.

ADD REQ (IP termination applied to the A interface) localControlDescriptor

name: The name net-MaxJitBuf indicates the maximum jitter buffer. value: The value 40 indicates that the maximum jitter buffer is 40(ms). MaxJitBuf: maximum jitter buffer, which is defined in the Network Package.

name: The name b-BNCChar indicates the characteristics of the added termination, that is, bearer type of the media stream. value: The value ip-rtp indicates that IP transport is used because the added termination is an IP termination.

name: The name p3giptra-ipv4trans indicates the Internet Protocol version 4 (IPv4) transport address. value: The empty value indicates that the IP address is contained in the returned ADD REPLY message.

ADD REQ (IP termination applied ipv4trans: IPv4 transport address, which is defined in the IP to the Iu interface) Transport Package.

localControlDescriptor

name: The name p3giptra-UDport indicates the Datagram Protocol (UDP) port number. value: The empty value indicates that the UDP port number is contained in the returned ADD REPLY message. UDport: UDP port, which is defined in the IP Transport Package.

ADD REPLY (IP termination applied to the Iu interface) localControlDescriptor

name: The name p3giptra-ipv4trans indicates the IPv4 transport address. value: In the value 35 00 01 50 3C 3C D0 00 00 00 00 00 00 00 00 00 00 00 00 00, 50 3C 3C D0 indicates that the transport address on the plane is 80.60.60.208.

name: The name p3giptra-UDport indicates the UDP port number. value: The value 436 indicates that the port number is 436.

ADD REQ (IP termination applied to the Nb interface) localControlDescriptor

name: The name bT-TunOpt indicates when the MGW reports tunneling related messages to the MGC. value: The value any-time indicates that the MGW can report tunneling related messages to the MGC at any time. TunOpt: tunneling options, which is defined in the Bearer Control Tunneling Package. Reference Standards For details about the localControlDescriptor, see section 7.1.7 "LocalControl Descriptor"in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the Bearer Characteristics Package, see Annex A in ITU-T Q.1950. For details about the 3G UP Package, see section 15 in 3rd Generation Partnership Project (3GPP) TS 29.232. For details about the Network Package, see Annex E "Basic packages" in ITU-T H.248.1. For details about the IP Transport Package, see section 15 in 3GPP TS 29.232. For details about the Bearer Control Tunneling Package, see Annex A in ITU-T Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

localDescriptor Description of the IE Reference Standards The localDescriptor describes the media stream received by the MGW. If the localDescriptor is present in the message delivered by the MGC, the MGW is required to reserve media encoding and decoding resources for the termination. The localDescriptor present in the message returned by the MGW indicates the resources ed by the MGW. Text encoding of the localDescriptor complies with the Session Description Protocol (SDP). The localDescriptor consists of media groups (propGrps) and related properties (LRPropertyParm). Description of the IE Information Element (IE)

Description

name: The name sdp-v indicates the version of the SDP protocol. sdpString: The value 0 indicates that the version number is 0.

name: The name sdp-c indicates the connection set up for a media session. sdpString: The value ATM NSAP $ indicates an ATM

connection without knowing the network service access point (NSAP) address.

name: The name sdp-m indicates the media type, that is, media name and transport address. sdpString: The value audio- - - indicates audio media; indicates that port information is not required for media streams using the ATM connection.

ADD REQ (asynchronous transfer mode (ATM) termination) localDescriptor

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value eecid:$ indicates that the end-to-end connection identifier (cid) of the ATM plane is unknown and the MGW is requested to assign the cid.

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value vsel:UMTS-AMR indicates that the codec used is UMTS-AMR.

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value codecconfig:02053F3F06 indicates the codec configuration. 02, which indicates the codec organization identifier, represents 3rd Generation Partnership Project (3GPP). 05, which indicates the codec identification, represents Universal Mobile Telecommunications System (UMTS) automatic meter reading system (AMR). 3F indicates the active codec set (ACS); that is, the active rates are 4.75 kbit/s, 5.15 kbit/s, 5.9 kbit/s, 6.7 kbit/s, 7.4 kbit/s, and 7.95 kbit/s. 3F indicates the ed codec set (SCS); that is, the ed rates are 4.75 kbit/s, 5.15 kbit/s, 5.9 kbit/s, 6.7 kbit/s, 7.4 kbit/s, and 7.95 kbit/s. 06 indicates that the optimization mode (OM) is 0 (the given ACS will not be changed) and the maximal number of codec modes (MACS) is 6.

name: The name sdp-c indicates the connection set up for a media session. sdpString: The value ATM NSAP 4700.0000.0000.0000.0000.0000.0000.0000.0000.0C28 indicates the returned NSAP address.

This address is the NSAP address configured on the MGW for adding a Q.AAL2 node.

ADD REPLY (ATM termination) localDescriptor name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value eecid:981e007f indicates the returned cid of the ATM plane. The least significant 7 bits (0011000) in the first byte 98 indicates that the virtual MGW ID is 24. The last 3 bytes (1e007f) are the last 3 bytes in the ATM termination ID.

1E is the board number of the CMU (30); 00 7F is the termination index ID.

name: The name sdp-c indicates the connection set up for a

media session. sdpString: The value IN IP4 $ indicates an INTERNET connection without knowing the Internet Protocol version 4 (IPv4) address.

name: The name sdp-m indicates the media type, that is, media name and transport address. sdpString: The value audio $ RTP/AVP 112 indicates audio media, unknown port, Real-Time Transport Protocol (RTP)/attribute-value pair (AVP) as the transport protocol, and 112 as the payload type (PT).

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value rtpmap:112 AMR/8000/1 indicates that the PT 112 corresponds to the codec AMR, with the sampling frequency at 8000 Hz and the number of channels at 1.

ADD REPLY (IP termination) localDescriptor

name: The name sdp-a indicates zero or more session attribute lines.

sdpString: The value ptime:20 indicates 20 ms of packet time.

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value fmtp:112mode-set=0,1,2,3,4,5;modechange-period=2 indicates that the bit rates of the used codecs are 4.75 kbit/s, 5.15 kbit/s, 5.9 kbit/s, 6.7 kbit/s, 7.4 kbit/s, and 7.95 kbit/s. The mapping between codec numbers and bit rates is as follows: 0: 1: 2: 3: 4: 5: 6: 7:

4.75 kbit/s 5.15 kbit/s 5.9 kbit/s 6.7 kbit/s 7.4 kbit/s 7.95 kbit/s 10.2 kbit/s 12.2 kbit/s

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value maxPTime:20 indicates that the maximum packet time is 20 ms.

name: The name sdp-c indicates the connection set up for a media session. sdpString: The value IN IP4 80.60.60.208 indicates the IP address 80.60.60.208; this IP address is configured for the HRB on the MGW.

ADD REPLY (IP termination) localDescriptor

name: The name sdp-m indicates the media type, that is, media name and transport address. sdpString: The value audio 128 RTP/AVP 112 indicates audio media, port number 128, RTP/AVP as the transport protocol, and 112 as the PT.

name: The name sdp-a indicates zero or more session attribute lines. sdpString: The value rtpmap:112 AMR/8000 indicates that the PT 112 corresponds to the codec AMR, with the sampling frequency at 8000 Hz. Reference Standards For details about the localDescriptor, see section 7.1.8 "Local and Remote Descriptors" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the SDP, see Internet Engineering Task Force (IETF) RFC 2327. For details about the audio codec protocol, see 3GPP TS 26103. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

remoteDescriptor Description of the IE Reference Standards The remoteDescriptor describes the media stream sent by the MGW. If the remoteDescriptor is present in the message delivered by the MGC, the MGW is required to reserve media encoding and decoding resources for the termination. Text encoding of the remoteDescriptor complies with the Session Description Protocol (SDP). The remoteDescriptor consists of media groups (propGrps) and related properties (LRPropertyParm). Description of the IE Information Element (IE)

MOD REQ (IP termination applied to the A interface) remoteDescriptor

Description

name: The name sdp-c indicates the connection set up for a media session. sdpString: The value IN IP4 80.1.2.145 indicates an Internet connection with the IP address 80.1.2.145. This IP address is the 's IP address on the bearer plane of the BSC.

name: The name sdp-m indicates the media type, that is, media name and transport address. sdpString: The value audio 96 RTP/AVP 112 indicates audio

media, port number 96, Real-Time Transport Protocol (RTP)/attribute-value pair (AVP) as the transport protocol, and 112 as the payload type (PT). Reference Standards For details about the remotelDescriptor, see section 7.1.8 "Local and Remote Descriptors" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the SDP, see Internet Engineering Task Force (IETF) RFC 2327. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

signalsDescriptor Description of the IE Reference Standards Description of the IE The signalsDescriptor contains a set of signals that the MGW is requested to apply to a termination. Information Element (IE)

MOD REQ signalsDescriptor

Description

signalName: The name tonegen-RingTone indicates a ringing tone. sigType: The type timeOut indicates that the signal lasts until it is turned off or a specific period of time elapses. The other signal types are as follows: brief: The signal will stop on its own unless a new signalsDescriptor is applied that causes it to stop; no timeout value is needed. onOff: The signal lasts until it is turned off. duration: The value 0xffff indicates the time that the signal lasts. notifyCompletion: The value 1001 indicates that the MGC wishes to be notified when the signal finishes play out. RingTone is defined in tonegen.

Reference Standards For details about descriptors, see section 7.1.11 "Signals Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about tonegen, see Annex E "Basic packages" in ITU-T H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

eventsDescriptor Description of the IE Reference Standards The eventsDescriptor contains a requestID and a list of events that the MGW is requested to detect and report. The requestID is used to correlate the request with the notifications that it may trigger. Description of the IE Information Element (IE)

Description

requestID: The value is 0. pkgdName: The value g-Cause indicates that the MGC requests the MGW to report the Cause event. The Cause event is defined in the Generic package. The meanings of Cause values are as follows: NR: Normal Release UR: Unavailable Resources FT: Failure, Temporary FP: Failure, Permanent IW: Interworking Error UN: Uned

ADD REQ eventsDescriptor

eventParameterName: The value gB-BNCChange:Ox1(1) indicates that the MGC requests the MGW to report the BNCChange event. tag: The value stag indicates an encoding format. gB-BNCChange: The value bearer-Established(1) indicates that the MGC requests the MGW to report the result of bearer-Established in the BNCChange event. The BNCChange event is defined in the Generic Bearer Connection Package.

eventParameterName: The value gB-BNCChange:Ox1(1) indicates that the MGC requests the MGW to report the BNCChange event with the ID of 1.

tag: The value stag indicates an encoding format. gB-BNCChange: The value bearer-ModificationFailure(1) indicates that the MGC requests the MGW to report the result of bearer-ModificationFailure in the BNCChange event.

eventParameterName: The value gB-BNCChange:Ox1(1) indicates that the MGC requests the MGW to report the BNCChange event with the ID of 1. tag: The value stag indicates an encoding format. gB-BNCChange: The value bearer-Modified(2) indicates that the MGC requests the MGW to report the result of bearerModified in the BNCChange event. Reference Standards For details about the eventsDescriptor, see section 7.1.9 "Events Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the Generic package, see Annex E "Generic package" in ITU-T H.248.1. For details about the Generic Bearer Connection Package, see Annex A in ITU-T Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


observedEventsDescriptor Description of the IE Reference Standards The observedEventsDescriptor consists of the requestID and the parameters of the events detected by the MGW. The requestID is used to associate the event request with the Notify command. Description of the IE Information Element (IE) Description

requestID: The requestID is 0, which is the same as

NTFY REQ observedEventsDescriptor

that in the eventsDescriptor. eventParameterName: The value gBBNCChange:Ox1(1) indicates that the MGW reports the BNCChange event. gB-BNCChange: The value bearer-Established(1) indicates that the MGW reports the result of bearerEstablished in the BNCChange event. date: The value 20101110 indicates that the event occurred on November 10, 2010. time: The value 14480688 indicates that the event occurred at 14:48:06.

eventParameterName: The value g-Cause:cause(1) indicates that the MGW reports the Cause event. gCause: The value normal-release(1) indicates that bearer resources are released normally. For information about IEs in the BNCChange and Cause events, see eventsDescriptor. Reference Standards For details about the observedEventsDescriptor, see section 7.1.17 "ObservedEvents Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1.

For details about the Generic Bearer Connection Package, see Annex A in ITU-T Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

auditDescriptor Description of the IE Reference Standards The auditDescriptor specifies what information about a termination is to be audited. It consists of the list of descriptors and individual properties to be returned. Audit may be used in any command to force the return of any descriptor containing the current values of its properties, events, signals and statistics. Description of the IE Information Element (IE)

Description

auditToken: The value 0010000000 indicates that the mediaDescriptor is to be audited. The meanings of auditToken values are as follows: AUDIT VAL REQ auditDescriptor

Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit

0: muxToken 1:modemToken 2: mediaToken 3: eventsToken 4: signalsToken 5: digitMapToken 6: statsToken 7: observedEventsToken 8: packagesToken 9: eventBufferToken

Reference Standards For details about the auditDescriptor, see section 7.1.12 "Audit Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs


serviceChange Description of the IE Reference Standards The serviceChange includes the serviceChangeMethod field and the reason field. Description of the IE Information Element (IE)

Description

When running a command to deactivate the MGW, the MGC sends the ServiceChange REQ message to notify the MGW that it shall terminate services running on all terminations. serviceChangeMethod: The value forced indicates that the specified terminations were taken abruptly out of service and all established connections associated with them will be lost. The other service change methods specified in the H.248.1 protocol are as follows: Failover: It is sent from the MGW to the MGC, indicating that the primary MGW is out of service and a secondary MGW is taking over. Graceful: It indicates that the specified terminations will be taken out of service after the specified ServiceChangeDelay; established connections are not yet affected. However, the MGC should refrain from establishing new connections and should attempt to gracefully tear down existing connections on the terminations affected by the serviceChange command. Restart: When sent by the MGW to the MGC, it announces that the MGW has restarted and wishes to

ServiceChange REQ serviceChange

renegotiate the protocol version, profile, or is announcing a capability change. The ServiceChangeReason indicates what actions may need to be taken by the MGC. When sent by the MGC, the MGW shall restart itself using the indicated ServiceChangeReason. Disconnect: It is always applied with the Root TerminationID, indicating that the MGW lost communication with the MGC, but it was subsequently restored to the same MGC. Since MGW state may have changed, the MGC may wish to use the Audit command to resynchronize its state with the MGW's. Handoff: When sent from the MGC to the MGW, this method indicates that the MGC is going out of service and a new MGC association must be established. When sent from the MGW to the MGC, this indicates that the MGW is attempting to establish a new association in accordance with a Handoff received from the MGC with which it was previously associated. Another value whose meaning is mutually understood between the MGW and the MGC. reason: The value 03 8D indicates that the cause is MGC Impending Failure.

The MGW sends the ServiceChange REQ message to itself with an MGC and inform the MGC to perform parameter negotiations. serviceChangeMethod: The value restart indicates that the MGW s with an MGC after it is restarted. serviceChangeVersion: The value 1 indicates that the message

sender s H.248 version 1. reason: The value 03 86 indicates that the reason for service change is Warm Boot. Reference Standards For details about the serviceChange, see section 7.1.13 "ServiceChange Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. For details about the serviceChange, see section 5.2 in ITU-T H.248.8. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

statisticsDescriptor Description of the IE Reference Standards The statisticsDescriptor provides information describing the status and usage of a termination during its existence (ephemeral) or while it is outside the NULL context (physical). The statisticsDescriptor consists of statistics parameters. Description of the IE Information Element (IE)

Description

statName: The value net-Duration indicates the duration of a termination's existence in a context. OCTET-STRING: The value 00 00 00 00 00 00 50 82 indicates that a termination has existed for 20610 ms. Duration is defined in the Network Package.

SUB REPLY statisticsDescriptor statName: The value net-OctetsReceived indicates the number of bytes received by a termination. OCTET-STRING: The value 00 00 00 00 00 00 3F EC indicates that a termination has received 16364 bytes. OctetsReceived is defined in the Network Package.

statName: The value rtp-PacketsSent indicates the number of packets sent by a termination. OCTET-STRING: The value 00 00 00 00 00 00 03 A0 indicates that a termination has sent 928 packets. PacketsSent is defined in the Real-Time Transport Protocol (RTP) Package. Reference Standards For details about the statisticsDescriptor, see section 7.1.15 "Statistics Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

errorDescriptor Description of the IE Reference Standards If a responder encounters an error when processing a transaction request, it must include an errorDescriptor in its response. An errorDescriptor consists of an IANA-ed error code, optionally accompanied by an error text. (Internet Assigned Numbers Authority (IANA) is short for Internet Assigned Numbers Authority.) Description of the IE Information Element (IE)

Description

AUDIT_VAL_RLY errorDescriptor

errorCode: The value errTermNotInSpecCtx indicates that the error cause is "Termination ID is not in Specified Context." errorText: The value Termination ID is not in Specified Context indicates that a termination to be audited does not exist in the specified context.

Reference Standards For details about the errorDescriptor, see section 7.1.20 "Error Descriptor" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) H.248.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Q.AAL2 Protocol Description of the Q.AAL2 Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Q.AAL2 Protocol Scenario Description Protocol Stack Message Structure IE Structure Message List Reference Standards As the AAL2 signaling protocol, the Q.AAL2 protocol is used to perform signaling negotiations to establish, release, and maintain the asynchronous transfer mode (ATM) Adaption Layer type 2 (AAL type 2) connections between two AAL2 signaling nodes. The AAL2 protocol is a transport layer protocol that is dedicated to transporting low-speed, real-time, and multirate connection services, for example, voice compression. The Q.AAL2 protocol is a control plane protocol used in the transport layer. It is dedicated to controlling AAL2 connections. Scenario Description The Q.AAL2 protocol allows AAL2 signaling nodes (such as RNC and MGW) to exchange signaling messages with each other when ATM transport is used on the Iu interface in 3G services. It can be used in any of the following scenarios: 1. An AAL2 connection is established. 2. An AAL2 connection is released. Protocol Stack Figure 1 shows the Q.AAL2 protocol stack.

Figure 1 Q.AAL2 protocol stack Message Structure The Q.AAL2 message consists of the message compatibility field and the parameters field. A parameters field contains one or multiple parameters. Each parameter consists of the parameter compatibility field and the parameter value field. Figure 2 shows the hierarchical structure of the Q.AAL2 message. Figure 2 Hierarchical structure of the Q.AAL2 message

IE Structure Figure 3 shows the Information Element (IE) Structure of the Q.AAL2 message. Figure 3 IE Structure

Message List Table 1 lists the common Q.AAL2 messages. Table 1 List of Q.AAL2 messages Message

Direction

Function

ERQ

RNC>MGW

Requests the MGW to establish an AAL2 connection.

ECF

MGW>RNC

Responds to the establish request (ERQ) message.

REL

RNC>MGW

Requests the MGW to release an AAL2 connection.

RLC

MGW>RNC

Responds to the release (REL) message.

Reference Standards For details about the Q.AAL2 protocol, see the International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Q.AAL2 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1describes the IEs carried in the common part of messages. Table 1 the Common Part of Messages Information Element (IE)

Description Identifies the signaling association of the receiver.

destination signaling association identifier

For details about the common part of messages, see Q.AAL2 Message Header.

Parent topic: Q.AAL2 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages ERQ ECF REL RLC Parent topic: Q.AAL2 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ERQ Message Function Associated IEs Message Function The establish request (ERQ) message is used by the RNC to request the MGW to establish an ATM Adaptation Layer Type 2 (AAL2) connection. Figure 1 shows important IEs in the ERQ message.

Figure 1 ERQ message Associated IEs Information Element (IE)

Description

Q.AAL2 message header

Indicates the header information of the Q.AAL2 message. Every Q.AAL2 message contains a header. For details, see Q.AAL2 Message Header.

message

Identifies a Q.AAL2 message. For details, see message.

message_compatibility

Indicates the compatibility information about the message. For details, see message_compatibility.

establishRequest-Param

Indicates the parameter carried in the ERQ message. For details, see establishRequestParam.

Parent topic: Description of Associated Messages Huawei Proprietary and Confidential


ECF Message Function Associated IEs Message Function The establish confirm (ECF) message is used by the MGW to respond to the establish request (ERQ) message sent by the RNC. Figure 1 shows important IEs in the ECF message.

Figure 1 ECF message Associated IEs Information Element (IE)

Description

Indicates the header information of the Q.AAL2 message. Q.ATM Adaptation Layer Type Every Q.AAL2 message contains a header. 2 (AAL2) message header For details, see Q.AAL2 Message Header. message




establishConfirm-Param

Indicates the parameter carried in the ECF message. For details, see establishConfirm-Param.


REL Message Function Associated IEs Message Function The release (REL) message is used by the RNC to request the MGW to release an ATM Adaptation Layer Type 2 (AAL2) connection. Figure 1 shows important IEs in the REL message.

Figure 1 REL message Associated IEs Information Element (IE)

Description



message




releaseRequest-Param

Indicates the parameter carried in the REL message. For details, see releaseRequest-Param.


RLC Message Function Associated IEs Message Function The Release Confirm (RLC) message is used by the MGW to respond to the release (REL) message sent by the RNC. Figure 1 shows important IEs in the RLC message.

Figure 1 RLC message Associated IEs Information Element (IE)

Description



message




releaseCofirm-Param

Indicates the parameter carried in the RLC message. For details, see releaseConfirm-param.


Description of Associated IEs Q.AAL2 Message Header message message_compatibility establishRequestParam establishConfirm-Param releaseRequest-Param releaseConfirm-param connection-element-identifier originating-signaling-association-identifier aal2-service-endpoint-address link-characteristics served--generated-reference cause Parent topic: Q.AAL2 Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Q.AAL2 Message Header Description of the IE Reference Standards The Q.AAL2 message header consists only of the destination signaling association identifier field. A signaling association indicates a signaling capability that exists between two adjacent AAL2 nodes. It controls the AAL2 connections that may exist in one or more AAL2 paths. Description of the IE Information Element (IE)

Description

establish request (ERQ) dsaid: The value 0 indicates that the destination signaling association Q.AAL2 message identifier is unknown. A specific value of this field indicates the header signaling association identifier of the receiver. Establish Confirm (ECF) Q.AAL2 message dsaid: The value 40 indicates the signaling association identifier on the RNC. For details, see originating-signaling-association-identifier. header

Release (REL) Q.AAL2 message header

dsaid: The value 83886091 indicates the signaling association identifier on the MGW. For details, see originating-signaling-associationidentifier. The ASU uses the four-byte said to identify the asynchronous transfer mode (ATM) termination. The most significant byte identifies its board number.

Reference Standards For details about the destination signaling association identifier, see section 7.4.2 "Signaling association identifier" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs


message Description of the IE Reference Standards The message consists of the message compatibility field and the parameters field. Description of the IE Information Element (IE)

Description

establish request (ERQ) message establishrequest: It is used by the RNC to request the MGW to establish an ATM Adaptation Layer Type 2 (AAL2) connection. message-compatibility: For details, see message_compatibility. establishRequest-param: For details, see establishRequestParam.

Establish Confirm(ECF) message

Release (REL) message

establishconfirm: It is used by the MGW to respond to the ERQ message sent by the RNC. message-compatibility: For details, see message_compatibility. establishConfirm-param: For details, see establishConfirm-Param.

releaserequest: It is used by the RNC to request the MGW to release an AAL2 connection. message-compatibility: For details, see message_compatibility. releaseRequest-param: For details, see releaseRequest-Param.

Release Confirm(RLC) message

releaseconfirm: It is used to respond to the REL message sent by the RNC. message-compatibility: For details, see message_compatibility. releaseCofirm-param: For details, see releaseConfirm-param.

Reference Standards For details about the message, see section 7.2 "Format and coding of the ATM Adaptation Layer (AAL) type 2 signaling protocol messages" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

message_compatibility Description of the IE Reference Standards The message_compatibility is used by an ATM Adaptation Layer Type 2 (AAL2) node to process the unrecognized signaling information. It allows the protocol of an earlier version to process the messages coded using the protocol of a later version. Description of the IE Information Element Description (IE)

ERQ message_compatibility

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-not-sendnotification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. send-notification: Sends the notification. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. Other values are as follows: discard-parameter: Discards parameters. discard-message: Discards the message. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value sendnotification indicates that the notification is sent when general actions are performed. general-action-instruction: The value discard-message indicates that the unrecognized message is discarded when general actions are performed.

Reference Standards For details about the message_compatibility, see section 8.1 "Compatibility" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

establishRequestParam Description of the IE Reference Standards The establishRequestParam contains parameters carried in the ERQ message. Description of the IE Information Element (IE)

Description

ERQ establishRequestParam connection-element-identifier: For details, see connection-elementidentifier. originating-signaling-association-identifier: For details, see originating-signaling-association-identifier. aal2–service-endpoint-address: For details, see aal2-serviceendpoint-address. link-characteristics: For details, see link-characteristics. served--generated-reference: For details, see served-generated-reference. Reference Standards For details about the establishRequestParam, see section 7.3 "Parameter specification of the ATM Adaptation Layer (AAL) type 2 signaling protocol messages" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


establishConfirm-Param Description of the IE Reference Standards The establishConfirm-Param contains parameters carried in the ECF message. Description of the IE Information Element (IE) ECF establishConfirmParam

Description

osaid: For details, see originating-signaling-association-identifier.

Reference Standards For details about the establishConfirm-Param, see section 7.3 "Parameter specification of the ATM Adaptation Layer (AAL) type 2 signaling protocol messages" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

releaseRequest-Param Description of the IE Reference Standards The releaseRequest-Param contains parameters carried in the REL message. Description of the IE Information Element (IE) REL releaseRequestParam

Description

cause: For details, see cause.

Reference Standards For details about the releaseRequest-Param, see section 7.3 "Parameter specification of the ATM Adaptation Layer (AAL) type 2 signaling protocol messages" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

releaseConfirm-param Description of the IE Reference Standards The releaseConfirm-param contains parameters carried in the RLC message. Description of the IE Information Element (IE) RLC releaseConfirmparam

Description

ceid: For details, see connection-element-identifier.

Reference Standards For details about the releaseConfirm-param, see section 7.3 "Parameter specification of the ATM Adaptation Layer (AAL) type 2 signaling protocol messages" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

connection-element-identifier Description of the IE Reference Standards The connection-element-identifier identifies all ATM Adaptation Layer Type 2 (AAL2) paths between two adjacent AAL2 nodes associated with a signaling association, a particular AAL2 path, or a particular channel on a particular AAL2 path. Description of the IE Information Element (IE)

Description

compatibility: The parameter compatibility is similar with message compatibility. For details, see message_compatibility.

Establish request (ERQ) connection-elementidentifier

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value sendnotification indicates that the notification is sent when general actions are performed. general-action-instruction: The value discard-

message indicates that the unrecognized message is discarded when general actions are performed. ceid: indicates the connection element identifier. path-identifier: The value 13 indicates that the identifier of the AAL2 path is 13. channel-identifier: The value 236 indicates that the channel identifier is 236. The asynchronous transfer mode (ATM) transport is connection-oriented and a virtual circuit (VC) must be established before data transfer. In addition, each VC maps to an AAL2 path. Every VC is identified by a Virtual Path Identifier (VPI) and a Virtual Channel Identifier (VCI). NOTE: You can run LST AAL2PATH to query AAL2 connections on the MGW side. Reference Standards For details about the connection-element-identifier, see section 7.3.2 "Connection element identifier" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

originating-signaling-association-identifier Description of the IE Reference Standards The originating-signaling-association-identifier indicates the signaling association identifier of the originating ATM Adaptation Layer Type 2 (AAL2) node. Description of the IE Information Element (IE)

Description


establish request (ERQ) originating-signalingassociationidentifier

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value sendnotification indicates that the notification is sent when general actions are performed. general-action-instruction: The value discardparameter indicates that unrecognized parameter is discarded when general actions are performed.

osaid: The value 40 indicates that the signaling association identifier (SAID) of the originating AAL2 node is 40.

Event charging function (ECF) osaid

osaid: The value 83886091 indicates that the SAID of the originating AAL2 node on the MGW side is 83886091. The ASU uses the four-byte SAID that is allocated by the Q.AAL2 module on each ASU, to identify the asynchronous transfer mode (ATM) termination. The most significant byte identifies its board number.

Reference Standards For details about the originating-signaling-association-identifier, see section 7.3.6 "Originating signaling association identifier" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

aal2-service-endpoint-address Description of the IE Reference Standards The aal2-service-endpoint-address can be the destination Network Service Access Point (NSAP) service endpoint address that is configured on the MGW. The RNC can obtain the address from the radio access bearer (RAB) ASSIGNMENT REQUEST message sent by the MGC. Description of the IE Information Element (IE)

Description


Establish request (ERQ) originating-signalingassociationidentifier

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value do-notsend-notification indicates that the notification is not sent when general actions are performed.

general-action-instruction: The value -onmessage-or-parameter indicates that the unrecognized information or parameter is forwarded when general actions are performed. nsap: The value 4700.0000.0000.0000.0000.0000.0000.0000.0000.0C28 indicates the NSAP service endpoint address on the MGW side. For details, see localDescriptor. Reference Standards For details about the aal2-service-endpoint-address, see section 7.3.4 "Destination NSAP service endpoint address" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

link-characteristics Description of the IE Reference Standards The link-characteristics contains attributes related to ATM Adaptation Layer Type 2 (AAL2) links. Description of the IE Information Element (IE)

Description

compatibility: The parameter compatibility is similar with message compatibility. For details, see message_compatibility. -on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that

Establish request (ERQ) link-characteristics

the unrecognized parameter is reserved. general-action-sendNotificaion: The value do-notsend-notification indicates that the notification is not sent when general actions are performed. general-action-instruction: The value -onmessage-or-parameter indicates that the unrecognized information or parameter is forwarded when general actions are performed. maxBitRate: indicates the maximum S-SDU bit rate available to the AAL2 served . forwardBitRate: The value 191 indicates that the maximum S-SDU bit rate in the forward direction is 191 kbit/s. backwardBitRate: The value 191 indicates that the maximum S-SDU bit rate in the backward direction is 191 kbit/s. averageBitRate: indicates the average S-SDU bit rate available to the AAL2 served . forwardBitRate: The value 191 indicates that the average S-SDU bit rate in the forward direction is 191 kbit/s. backwardBitRate: The value 191 indicates that the average S-SDU bit rate in the backward direction is 191 kbit/s. maxSize: indicates the maximum AAL2 S-SDU size, in bytes, allowed to be sent. forwardSize: The value 45 indicates that the maximum S-SDU size in the forward direction is 45 bytes. backwardSize: The value 45 indicates that the maximum S-SDU size in the backward direction is 45 bytes. averageSize: indicates the average AAL2 S-SDU size, in bytes, allowed to be sent. forwardSize: The value 45 indicates that the average S-SDU size in the forward direction is 45 bytes. backwardSize: The value 45 indicates that the average S-SDU size in the backward direction is

45 bytes. Reference Standards For details about the link-characteristics, see section 7.3.5 "Link characteristics" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

served--generated-reference Description of the IE Reference Standards The served--generated-reference uniquely identifies the radio access bearer (RAB) management and control module on the MGW side. Description of the IE Information Element (IE)

Description


Establish request (ERQ) served-generatedreference

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value do-notsend-notification indicates that the notification is not sent when general actions are performed. general-action-instruction: The value -onmessage-or-parameter indicates that the unrecognized information or parameter is forwarded when general actions are performed.

sugr: The value 0x981e007f indicates that the served generated reference is 2552103039, which can be obtained by the RNC from the RAB ASSIGNMENT REQUEST message sent by the MGC. For details, see localDescriptor. Reference Standards For details about the served--generated-reference, see section 7.3.7 "Served generated reference" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

cause Description of the IE Reference Standards The cause describes why an ATM Adaptation Layer Type 2 (AAL2) connection is released or fails to be established. Description of the IE Information Element (IE)

Description


Release (REL) cause

-on-impossible-reserved: The value 0 indicates that the unrecognized parameter is reserved. -on-impossible-sendNotif: The value do-notsend-notification indicates that the notification is not sent if the unrecognized message or parameter cannot be forwarded. -on-impossible-instruction: The value -onmessage-or-parameter indicates that the unrecognized message or parameter is forwarded. general-action-reserved: The value 0 indicates that the unrecognized parameter is reserved. general-action-sendNotificaion: The value sendnotification indicates that the notification is sent

when general actions are performed. general-action-instruction: The value discardparameter indicates that unrecognized parameter is discarded when general actions are performed. cause-value: indicates the cause value. reserved1: The value 0 indicates the unrecognized parameter is reserved. coding-standard: The value itu-t-standardized indicates that International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) standardized codes are used. reserved2: The value 0 indicates the unrecognized parameter is reserved. cause: The value normal-unspecified indicates that it is a normal connection release. diagnostics: indicates the diagnostics information. Reference Standards For details about the cause, see section 7.3.1 "Cause" in ITU-T Q.2630.1. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IU_UP/NB_UP Protocol Description of the IU_UP/NB_UP Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the IU_UP/NB_UP Protocol Scenario Description Protocol Stack Message Structure IE Structure Message List Reference Standards The plane (UP) protocol is used to convey data associated to Radio Access Bearers (RABs). The UP protocol can be classified into the IU_UP protocol and the NB_UP protocol based on the interface over which it is used. The control procedures of the two protocols, however, are the same. IU_UP: The Iu interface is used to transfer data and plane signaling between an RNC and an MGW. The IU_UP protocol is used for UP operations performed between an RNC and an MGW. NB_UP: The Nb interface is used to transfer data and plane signaling between two MGWs. The NB_UP protocol is used for UP operations performed between two MGWs. Modes of operation of the IU_UP/NB_UP protocol are defined as follows: Transparent mode: This mode is intended for those RABs that do not require any particular feature from the IU_UP/NB_UP protocol other than transfer of data. In this mode, no UP frame is sent. The typical services in this mode are H.324M video phone (VP) services and transparent data services. mode for predefined service distribution unit (SDU) size: This mode is intended for those RABs that require some procedure control functions and some data streams specific functions while the sizes of the data being transferred can vary in a predefined manner. The typical services in this mode are voice services and non-transparent data services. Scenario Description The IU_UP/NB_UP protocol is used during the negotiation in the plane of the Iu or Nb interface. The protocol in mode for pre-defined SDU sizes can be used in any of the following scenarios:

1. UP initialization and exchange of bearer path information between an RNC and an MGW or between two MGWs. 2. Time alignment between an RNC and an MGW or between two MGWs. 3. Rate control between an RNC and an MGW or between two MGWs. This procedure controls the allowed rate sets between transmission entities. 4. Handling of error events between an RNC and an MGW or between two MGWs. This procedure controls fault monitoring information. 5. Transfer of data between an RNC and an MGW or between two MGWs. Protocol Stack Figure 1 shows the protocol stack of the IU_UP protocol carried over asynchronous transfer mode (ATM).

Figure 1 Protocol stack of the IU_UP protocol carried over ATM Figure 2 shows the protocol stack of the IU_UP/NB_UP protocol carried over IP. Figure 2 Protocol stack of the IU_UP/NB_UP protocol carried over IP

Message Structure

An IU_UP/NB_UP message consists of a message header, the Frame Control part, the Frame Checksum part, and the Frame Payload part. Figure 3 shows the hierarchical structure of the IU_UP/NB_UP message. Figure 3 Hierarchical structure of the IU_UP/NB_UP message

IE Structure Figure 4 shows the Information Element (IE) Structure of the IU_UP/NB_UP message. Figure 4 IE Structure

Message List Table 1 lists common IU_UP/NB_UP messages. Table 1 List of common IU_UP/NB_UP messages Message Direction Function TRC_IU/NB_UP_INIT (Sent by RNC)

RNC>MGW

Sends an IU_UP initialization frame transported over ATM.

TRC_IU/NB_UP_INIT (Sent by MGW)

MGW>RNC

Responds to the IU_UP initialization frame transported over ATM.

TRC_IU/NB_UP_INIT_TOIP

RNC>MGW MGW>MGW

Sends an IU_UP initialization frame transported over IP. Sends an NB_UP initialization frame.

MGW-

>RNC MGW>MGW

Responds to the IU_UP initialization frame transported over IP. Responds to the NB_UP initialization frame.

TRC_IU/NB_UP_TA (Received)

RNC>MGW MGW>MGW

Sends an IU_UP time alignment frame. Sends an NB_UP time alignment frame.

TRC_IU/NB_UP_TA (Sent)

MGW>RNC MGW>MGW

Responds to the UP time alignment frame.

TRC_IU/NB_UP_ACK_FRMIP

Reference Standards For details about the IU_UP protocol, see 3rd Generation Partnership Project (3GPP) TS 25.415 versions. For details about the NB_UP protocol, see 3GPP TS 29.415 versions. Parent topic: IU_UP/NB_UP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages There is no common part in IU_UP/NB_UP messages. Parent topic: IU_UP/NB_UP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages TRC_IU/NB_UP_INIT (Sent by RNC) TRC_IU/NB_UP_INIT (Sent by MGW) TRC_IU/NB_UP_INIT_TOIP TRC_IU/NB_UP_ACK_FRMIP TRC_IU/NB_UP_TA (Received) TRC_IU/NB_UP_TA (Sent) Parent topic: IU_UP/NB_UP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TRC_IU/NB_UP_INIT (Sent by RNC) Message Function Associated IEs Message Function The TRC_IU/NB_UP_INIT message (sent by RNC) is used by the RNC to send an UP initialization frame to the MGW, controlling the exchange of initialization information such as the radio access bearer (RAB) sub-Flow Combination Indicator (RFCI). Figure 1 shows important IEs in the TRC_IU/NB_UP_INIT message (sent by RNC).

Figure 1 TRC_IU/NB_UP_INIT message Associated IEs Information Element (IE)

Description

IU_UP/NB_UP message header

Indicates the header information of IU_UP/NB_UP messages. For details, see IU_UP/NB_UP Message Header.

frameControlPart

Indicates the frame control information of IU_UP/NB_UP messages. For details, see frameControlPart.

frameChecksumPart

Indicates the frame checksum information of IU_UP/NB_UP messages. For details, see frameChecksumPart.

framePayloadPart

Indicates the frame payload information of IU_UP/NB_UP messages. For details, see framePayloadPart.


TRC_IU/NB_UP_INIT (Sent by MGW) Message Function Associated IEs Message Function The TRC_IU/NB_UP_INIT message (sent by MGW) is used by the MGW to respond to the UP initialization frame. Figure 1 shows important IEs in the TRC_IU/NB_UP_INIT message (sent by MGW).

Figure 1 TRC_IU/NB_UP_INIT message Associated IEs Information Element (IE)

Description



frameControlPart


frameChecksumPart


framePayloadPart



TRC_IU/NB_UP_INIT_TOIP Message Function Associated IEs Message Function The TRC_IU/NB_UP_INIT_TOIP message is used to control the exchange of initialization information, for example, the exchange of radio access bearer (RAB) sub-Flow Combination Indicator (RFCI). This message can be used by the radio network controller (RNC) to instruct the media gateway (MGW) to start the initialization procedure over IPbased Iu interfaces, or by an MGW to instruct another MGW to start the initialization procedure over Nb interfaces. Figure 1 shows important IEs in the TRC_IU/NB_UP_INIT_TOIP message.

Figure 1 TRC_IU/NB_UP_INIT_TOIP message Associated IEs Information Element (IE)

Description



frameControlPart


frameChecksumPart


framePayLoadPart

Indicates the frame payload part of IU_UP/NB_UP messages. For details, see framePayloadPart.


TRC_IU/NB_UP_ACK_FRMIP Message Function Associated IEs Message Function The TRC_IU/NB_UP_ACK_FRMIP message is used by a media gateway (MGW) to reply to the radio network controller (RNC) over IP-based Iu interfaces during the initialization procedure, or reply to another MGW over Nb interfaces. Figure 1 shows important IEs in the TRC_IU/NB_UP_ACK_FRMIP message.

Figure 1 TRC_IU/NB_UP_ACK_FRMIP message Associated IEs Information Element (IE)

Description



frameControlPart


frameChecksumPart

Indicates the frame check information of IU_UP/NB_UP messages. For details, see frameChecksumPart.

framePayLoadPart

Indicates the frame payload part of IU_UP/NB_UP messages.

For details, see framePayloadPart. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TRC_IU/NB_UP_TA (Received) Message Function Associated IEs Message Function The TRC_IU/NB_UP_INIT (received) message is used by the radio network controller (RNC) to instruct the media gateway (MGW) to start the time alignment procedure over Iu interfaces, or by an MGW to instruct another MGW to start the time alignment produce over Nb interfaces. During the time alignment procedure, the RNC or MGW indicates the receiver (MGW) the necessary amount of the delay or advance adjustment. Figure 1 shows important IEs in the TRC_IU/NB_UP_TA message.

Figure 1 TRC_IU/NB_UP_TA message Associated IEs Information Element (IE)

Description

frameControlPart


frameChecksumPart

Indicates the frame check information of IU_UP/NB_UP messages. For details, see frameChecksumPart.

framePayLoadPart

Indicates the frame payload part of IU_UP/NB_UP messages. For details, see framePayloadPart.

Parent topic: Description of Associated Messages


TRC_IU/NB_UP_TA (Sent) Message Function Associated IEs Message Function The TRC_IU/NB_UP_INIT (sent) message is used by a media gateway (MGW) to reply to the radio network controller (RNC) or another MGW during the time alignment procedure. Figure 1 shows important IEs in the TRC_IU/NB_UP_TA message.

Figure 1 TRC_IU/NB_UP_TA message Associated IEs Information Element (IE)

Description

frameControlPart


frameChecksumPart


framePayLoadPart



Description of Associated IEs IU_UP/NB_UP Message Header frameControlPart frameChecksumPart framePayloadPart RFC (RAB sub-Flow Combination Indicator) Parent topic: IU_UP/NB_UP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IU_UP/NB_UP Message Header Description of the IE The IU_UP/NB_UP message header consists of information about contexts, terminations, and channels. Description of the IE Information Element (IE)

TRC_IU/NB_UP_INIT (sent by RNC) IU_UP/NB_UP message header

TRC_IU/NB_UP_INIT_FRMIP IU_UP/NB_UP message header

Description

contextID: The value 1966382 indicates the context of the termination receiving the initialization message. terminationID: The value 00 00 00 00 20 1E 00 7F indicates the identifier of the termination receiving the initialization message. channelID: The value 236 indicates the ATM Adaptation Layer Type 2 (AAL2) channel identifier. said: The value 10 indicates the UP instance number.

contextID: The value 1972295 indicates the context of the termination receiving the initialization message. terminationID: The value 0x46c indicates that the identifier of the termination receiving the initialization message is 00 00 00 00 30 00 04 6C. srcIpAddr: The value 0x503c3cd0 indicates that the source IP address is 80.60.60.208. srcUdp: The value 436 indicates the port number. rsv: The value 0 indicates that the parameter field is reserved.


frameControlPart Description of the IE Reference Standards The Frame Control part consists of the protocol data unit (PDU) Type field, the ackNack field, and the Frame Number field. Description of the IE Information Element Description (IE)

pduType: The value frame-14 indicates PDU type 14. The PDU types are as follows: PDU type 0 is defined to transfer data over the IU_UP/NB_UP in mode for pre-defined service distribution unit (SDU) sizes. Error detection scheme is provided over the IU_UP/NB_UP for the payload part. PDU type 1 is defined to transfer data over the IU_UP/NB_UP in mode for pre-defined SDU sizes when no payload error detection scheme is necessary over IU_UP/NB_UP (for example, no payload cyclic redundancy code (CRC)). PDU type 14 is defined to perform control procedures over the IU_UP/NB_UP in mode for pre-defined SDU sizes. The control procedure is identified by the procedure indicator. The Frame Payload part contains the data information related to the control procedure. ackNack: The value procedure indicates that the frame is a control procedure frame. The other values are as follows: ack: indicates that the frame is a positive

acknowledgement of a control procedure frame. Nack: indicates that the frame is a negative acknowledgement of a control procedure frame.

TRC_IU/NB_UP_INIT (sent by RNC) frameControlPart

frmNum: The value 0 indicates the frame number. The purpose of the PDU type 14 Frame Number is to provide the receiving entity with a mechanism to keep track of lost UP frames. It is also used to relate the acknowledgment frame to the frame being acknowledged. That is, the same PDU type 14 Frame Number is used in the acknowledgement frame as the one used in the frame being acknowledged. modeVer: indicates the IU_UP/NB_UP mode version. The values are as follows: 0: Mode version 1 is ed in transparent mode. 1: Mode version 2 is ed in mode for pre-defined SDU sizes. The only difference between services in transparent mode and those in mode for pre-defined SDU sizes is that no UP initialization procedure is available in transparent mode. procInd: indicates the control procedure in the current frame. The values are as follows: 0: initialization. 1: rate control. 2: time alignment. 3: error event. 4-15: reserved. NOTE: The transcoder free operation (TrFO) function can be ed only in mode for pre-defined SDU sizes.

TRC_IU/NB_UP_INIT ackNack: The value ack indicates that the frame is a positive (sent by MGW) acknowledgement of a control procedure frame (that is, a positive acknowledgement of an initialization frame). frameControlPart The other values are as follows: procedure: indicates that the frame is a control procedure frame. Nack: indicates that the frame is a negative acknowledgement of a control procedure frame.

TRC_IU/NB_UP_TA (receive) frameControlPart

procInd: The value timeAlignment indicates a time alignment procedure.

TRC_IU/NB_UP_TA (send) frameControlPart ackNack: The value ack indicates that the frame is a positive acknowledgement of a control procedure frame (that is, a positive acknowledgement of a time alignment frame). Reference Standards For details about the frameControlPart, see section 6.6 "Elements for Iu UP communication in mode" in 3rd Generation Partnership Project (3GPP) TS 25.415. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

frameChecksumPart Description of the IE Reference Standards The Frame Checksum part consists of the Header cyclic redundancy code (CRC) field and the Payload CRC field. Description of the IE Information Element Description (IE)

TRC_IU/NB_UP_INIT (sent by RNC) frameChecksumPart

TRC_IU/NB_UP_INIT (sent by MGW) frameChecksumPart

headerCRC: The value 3 indicates the header CRC. This field contains the CRC of all fields in the Frame Control part. With this CRC error bursts can be detected. payloadCRC: The value 484 indicates the payload CRC. This field contains the CRC of all the fields of the Frame Payload part. With this CRC error bursts can be detected.

headerCRC: The value 61 indicates the header CRC. spare10: idle.

Reference Standards For details about the frameChecksumPart, see section 6.6.3 "Coding of information elements in frames" in 3rd Generation Partnership Project (3GPP) TS 25.415. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

framePayloadPart Description of the IE Reference Standards The Frame Payload part consists of radio access bearer (RAB) sub Flow Combination (RFC) information and related control information. Description of the IE Information Element Description (IE)

spare3: The value 0 indicates that the spare field is set to 0 by the sender and should not be interpreted by the receiver. ti: The value iptiPresent indicates that Timing Information is included in the control procedure frame. numberOfSubflowsPerRfci: The value 3 indicates that each RFC consists of three sub-flows. chainInd: indicates whether the control procedure frame is the last frame related to the control procedure. The values are as follows: TRC_IU/NB_UP_INIT (sent by RNC) framePayloadPart

0: indicates that this frame is the last frame for the procedure. 1: indicates that additional frames will be sent for the procedure. firstRFC: For details, see RFC (RAB sub-Flow Combination Indicator). modeVerSupp: The value 3 indicates that the sender of the initialization frame s UP mode versions 1 and 2. dataPDUtype: The value 0 indicates that protocol data unit (PDU) type 0 is used for transferring data.

The PDU types are as follows: PDU type 0 is defined to transfer data over the IU_UP/NB_UP in mode for pre-defined service distribution unit (SDU) sizes. Error detection scheme is provided over the IU_UP/NB_UP for the payload part. PDU type 1 is defined to transfer data over the IU_UP/NB_UP in mode for pre-defined SDU sizes when no payload error detection scheme is necessary over IU_UP/NB_UP (for example, no payload cyclic redundancy code (CRC)). spare4: idle. TRC_IU/NB_UP_INIT (sent by MGW) framePayloadPart framePayloadPart: NULL.

dataTimeAlign: indicates the amount the sending time should be TRC_IU/NB_UP_TA advanced or delayed. (receive) The values ranging from 0 to 255 are as follows: framePayloadPart 1≤n≤80: indicates that the sending time is n×500 μs delayed. 129≤n≤208: indicates that the sending time is (n-128)×500 μs advanced. Other values: reserved. TRC_IU/NB_UP_TA (send) framePayloadPart: NULL. framePayloadPart spareExtension: indicates the spare extension field. Reference Standards For details about the framePayloadPart, see section 6.6.3 "Coding of information elements in frames" in 3rd Generation Partnership Project (3GPP) TS 25.415.


RFC (RAB sub-Flow Combination Indicator) Description of the IE Reference Standards RAB sub-Flow Combination (RFC) is a combination of the Radio Access Bearer (RAB) subflows. Description of the IE Information Element (IE)

Description

Last RFCI Indicator (LRI): The value notLast indicates that the current initialization frame is not the last RFC. Length Indicator (LI): The value oneByte indicates that the length of the sub-flow is 1 byte. RAB sub-flow combination indicator (RFCI): The value 0 indicates that the identifier assigned to this RFC is 0. lengthOfSubflow1 Byte: The value 42 indicates that the length of sub-flow 1 is 42 bits. lengthOfSubflow2 Byte: The value 53 indicates that the length of sub-flow 2 is 53 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The Adaptive Multi-Rate (AMR) codec mode for the corresponding RFC is 4.75 kbit/s. The calculation formula is as follows: (42 + 53 + 0) bits/AMR codec packet time 20 ms = 4.75 kbit/s

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 bit. RFCI: The value 1 indicates that the identifier assigned to this RFC is 1. lengthOfSubflow1 Byte: The value 49 indicates that the length of sub-flow 1 is 49 bits. lengthOfSubflow2 Byte: The value 54 indicates that the length of sub-flow 2 is 54 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The AMR codec mode for the corresponding RFC is 5.15 kbit/s. The calculation formula is as follows: (49 + 54 + 0) bits/AMR codec packet time 20 ms = 5.15 kbit/s

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 2 indicates that the identifier assigned to this RFC is 2. lengthOfSubflow1 Byte: The value 55 indicates that the length

of sub-flow 1 is 55 bits. lengthOfSubflow2 Byte: The value 63 indicates that the length of sub-flow 2 is 63 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The AMR codec mode for the corresponding RFC is 5.9 kbit/s. The calculation formula is as follows: (55 + 63 + 0) bits/AMR codec packet time 20 ms = 5.9 kbit/s

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 3 indicates that the identifier assigned to this RFC is 3. lengthOfSubflow1 Byte: The value 58 indicates that the length of sub-flow 1 is 58 bits. lengthOfSubflow2 Byte: The value 76 indicates that the length of sub-flow 2 is 76 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The AMR codec mode for the corresponding RFC is 6.7 kbit/s. The calculation formula is as follows: (58 + 76 + 0) bits/AMR codec packet time 20 ms = 6.7 kbit/s

TRC_IU/NB_UP_TA

(Sent by RNC) RAB sub-Flow Combination (RFC)

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 4 indicates that the identifier assigned to this RFC is 4. lengthOfSubflow1 Byte: The value 61 indicates that the length of sub-flow 1 is 61 bits. lengthOfSubflow2 Byte: The value 87 indicates that the length of sub-flow 2 is 87 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The AMR codec mode for the corresponding RFC is 7.4 kbit/s. The calculation formula is as follows: (61 + 87 + 0) bits/AMR codec packet time 20 ms = 7.4 kbit/s

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 5 indicates that the identifier assigned to this RFC is 5. lengthOfSubflow1 Byte: The value 75 indicates that the length

of sub-flow 1 is 75 bits. lengthOfSubflow2 Byte: The value 84 indicates that the length of sub-flow 2 is 84 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The AMR codec mode for the corresponding RFC is 7.95 kbit/s. The calculation formula is as follows: (75 + 84 + 0) bits/AMR codec packet time 20 ms = 7.95 kbit/s

LRI: The value notLast indicates that the current initialization frame is not the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 8 indicates that the identifier assigned to this RFC is 8. lengthOfSubflow1 Byte: The value 39 indicates that the length of sub-flow 1 is 39 bits. lengthOfSubflow2 Byte: The value 0 indicates that the length of sub-flow 2 is 0 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The total length of the sub-flow is 39 bits for the corresponding RFC, indicating that the silence voice (comfort noise) is transmitted.

LRI: The value isLast indicates that the current initialization frame is the last RFC. LI: The value oneByte indicates that the length of the subflow is 1 byte. RFCI: The value 9 indicates that the identifier assigned to this RFC is 9. lengthOfSubflow1 Byte: The value 0 indicates that the length of sub-flow 1 is 0 bits. lengthOfSubflow2 Byte: The value 0 indicates that the length of sub-flow 2 is 0 bits. lengthOfSubflow3 Byte: The value 0 indicates that the length of sub-flow 3 is 0 bits. The total length of the sub-flow is 0 bits for the corresponding RFC, indicating that no data is transmitted.

Inter PDU Timing Interval (IPTI): The value 8 indicates that the value of the IPTI is eight (in the same order as the RFCIs occur in the Initialization frame). NOTE: The LST RFCI can be used to query the RFCI set on the media gateway (MGW). Reference Standards For details about the RFC, see section 6.6.3 "Coding of information elements in frames" in 3rd Generation Partnership Project (3GPP) TS 25.415. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IPB Protocol Description of the IPB Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the IPB Protocol Scenario Description Protocol Stack Message Structure IE Structure Message List Reference Standards IP Bearer Control Protocol (IPB) is used for bearer attribute negotiation before the RealTime Transport Protocol (RTP) bearer is established for the NB-UP data transmitted over the Nb interface. The negotiation is implemented over the Mc and Nc interfaces. Figure 1 shows the IPB application.

Figure 1 IPB application The control plane protocol used on the Nb interface is defined in 3rd Generation Partnership Project (3GPP) TS 29.232. When IP bearer is used, two MGWs negotiate service bearer attributes over the connection established by the Mc-provided channel and Nb-defined tunnel. The Mc interface specification and Nb interface specification defined by 3GPP must both be met. IPB is used for the exchange of media stream characteristics, port numbers, and IP addresses of the receiver and sender of a media stream. IPB uses the Session Description Protocol (SDP) to encode the exchanged information. Scenario Description IPB is used for the exchange of information during Bearer Independent Call Control (BICC) call establishment when IP bearer is used on the Nb interface.

Protocol Stack Figure 2 shows the IPB protocol stack. Figure 2 IPB protocol stack

The MSC server transparently transmits Bearer Control Tunneling Protocol (BCTP) and IPB packets without processing them. BCTP and IPB packets originate from one MGW and terminate on another MGW. Message Structure IPB messages are encoded in compliance with SDP and contain a group of attribute names and attribute values. Figure 3 shows the hierarchical structure of the IPB message. Figure 3 IPB message structure

IE Structure Figure 4 shows the Information Element (IE) Structure of the IPB message. Figure 4 IE Structure

Message List Table 1 lists four IPB messages. Table 1 IPB messages Messages Direction

Function

Request

MGW>MGW

Requests to exchange information necessary for establishing and modifying an IP bearer. For details, see bT-TunnelInd-DATA.

Accepted

MGW>MGW

Responds to the Request message after the Request message is accepted and processed. For details, see bT-TunnelInd-DATA.

Confused

MGW>MGW

Responds to the Request message after the Request message is received but not processed.

Rejected

MGW>MGW

Responds to the Request message after the Request message is received but rejected.

IPB messages are transferred by means of H.248 messages and BICC messages. Table 2 lists the commands used for IPB messages. Table 2 Commands used for IPB messages Message Direction Function (Command) ADD REQ (bT)

MGC>MGW

Notifies the MGW of the time to report the tunneled information.

MOD REQ (bT)

MGC>MGW

Sends tunneled information to the MGW or instructs the MGW to report tunneled information events.

NTFY REQ (bT)

MGW>MGC

Reports tunneled information events to the MGC.

IAM (APP)

MGC>MGC

Sends tunneling related information to the MGC.

APM (Initiating bCI)

MGC>MGC

Sends tunneled information to the MGC.

APM (Receiving bCI)

MGC>MGC

Receives tunneling negotiation results from the MGC.

Reference Standards For details about IPB, see International Telecommunication Union-Telecommunication

Standardization Sector (ITU-T) Q.1970. Parent topic: IPB Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages There is no common part in IP Bearer Control Protocol (IPB) messages. Parent topic: IPB Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages ADD REQ (bT) MOD REQ (bT) NTFY REQ (bT) IAM (APP) APM (Initiating bCI) APM (Receiving bCI) Parent topic: IPB Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ADD REQ (bT) Message Function Associated IEs Message Function If the ADD REQ (bT) message contains the localControlDescriptor that carries the bTTunOpt attribute, it is used to notify the MGW of the time to report the tunneled information. If the ADD REQ (bT) message contains the signalsDescriptor that carries the bTBearInfoTrans attribute, it is used by the MGC to send the tunneled information to the MGW. Figure 1 and Figure 2 shows important IEs in the ADD REQ (bT) message.

Figure 1 ADD REQ (bT) message Figure 2 ADD REQ (bT) message


Description

bT-TunOpt

Notifies the MGW of the time to report the tunneled information. For details, see bT-TunOpt.

bT-BearInfoTrans

Sends the tunneled information to the MGW. For details, see bT-BearInfoTrans.


MOD REQ (bT) Message Function Associated IEs Message Function If the MOD REQ (bT) message contains the eventsDescriptor that carries the bT-TunnelInd attribute, it is used to instruct the MGW to report a tunneled information event. If the MOD REQ (bT) message contains the signalsDescriptor that carries the bTBearInfoTrans attribute, it is used by the MGC to send the tunneled information to the MGW. Figure 1 and Figure 2 shows important IEs in the MOD REQ (bT) message.

Figure 1 MOD REQ (bT) message Figure 2 MOD REQ (bT) message


Description

bT-TunnelInd

Instructs the MGW to report a tunneled information event. For details, see bT-TunnelInd.

bT-BearInfoTrans

Sends the tunneled information to the MGW. For details, see bT-BearInfoTrans.


NTFY REQ (bT) Message Function Associated IEs Message Function The NTFY REQ (bT) message contains the observedEventsDescriptor that carries the bTTunnelInd attribute. It is used to report an event that the tunneled information is sent from the MGW. Figure 1 shows important IEs in the NTFY REQ (bT) message.

Figure 1 NTFY REQ (bT) message Associated IEs Information Element (IE)

Description

bT-TunnelInd

Indicates an event that the tunneled information is sent from the MGW. For details, see bT-TunnelInd.

bT-TunnelInd-DATA

Indicates the tunneled information. For details, see bT-TunnelInd-DATA.


IAM (APP) Message Function Associated IEs Message Function The IAM (APP) message indicates the bearer related information. If the IAM (APP) message contains bearer-Control-Info, the fast bearer establishment is to be used; if bearer-Control-Info is not included, the delayed bearer establishment is to be used. Figure 1 shows important IEs in the IAM (APP) message.

Figure 1 IAM (APP) message Associated IEs Information Element (IE)

Description

action-indicator

Indicates the bearer establishment mode. For details, see action-indicator.

bearer-Control-Info

Indicates the tunneled bearer control information. For details, see bearer-Control-Info.

bearer-Control-Tunnel

Indicates the information related to bearer control tunneling. For details, see bearer-Control-Tunnel.


APM (Initiating bCI) Message Function Associated IEs Message Function The APM (initiating bCI) message is used to send the tunneled bearer control information. If the first bearer-Control-Info (bCI) is included in the APM (initiating bCI) message from the calling party side, the forward bearer establishment is to be used; if the bCI is included in the APM (initiating bCI) message from the called party side, the backward bearer establishment is to be used. Figure 1 shows important IEs in the APM (initiating bCI) message.

Figure 1 APM (initiating bCI) message Associated IEs Information Element (IE)

Description

bearer-Control-Info



APM (Receiving bCI) Message Function Associated IEs Message Function The APM (receiving bCI) message is used to receive the tunneling negotiation results. Figure 1 shows important IEs in the APM (receiving bCI) message.

Figure 1 APM (receiving bCI) message Associated IEs Information Element (IE)

Description

bearer-Control-Info



Description of Associated IEs bT-TunOpt bT-TunnelInd bT-BearInfoTrans bT-TunnelInd-DATA action-indicator bearer-Control-Tunnel bearer-Control-Info Parent topic: IPB Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bT-TunOpt Description of the IE Reference Standards The TunOpt, representing tunneling options, indicates when the MGW sends the tunneled information to an MGC. Description of the IE Information Element (IE)

Description

ADD REQ (bT) bT-TunOpt

name: The value bT-TunOpt indicates when the MGW sends the tunneled information to an MGC. value: The value any-time indicates that the MGW can send the tunneled information at any time and that the related termination goes into the initial state to wait for subsequent information. The other value as-rsp-cmd indicates that the MGW initiates the tunneling negotiation. TunOpt: tunneling options, which is defined in the Bearer Control Tunneling Package.

Reference Standards For details about the Bearer Control Tunneling Package, see Annex A in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bT-TunnelInd Description of the IE Reference Standards The TunnelInd, representing tunnel indication, indicates the event that the MGW sends the tunneled information. Description of the IE Information Element (IE)

Description

MOD REQ (bT) bT-TunnelInd name: The value TunnelInd indicates that the MGW sends the tunneled information and the relevant termination goes into the negotiation requesting state.

NTFY REQ (bT) bT-TunnelInd

name: The value bit, representing bearer information transport, indicates that the tunneled information is sent. value: The value bT-TunnelInd-DATA indicates the tunneled information.

TunnelInd: tunnel indication, which is defined in the Bearer Control Tunneling Package. Reference Standards For details about the Bearer Control Tunneling Package, see Annex A in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bT-BearInfoTrans Description of the IE Reference Standards The BearInfoTrans, representing bearer information transport, is used by the MGC to send the tunneled information to the MGW. Description of the IE Information Element (IE)

Description

ADD REQ (bT) (Receiver) bT-BearInfoTrans

name: The value bit, representing bearer information transport, indicates that the tunneled information is sent. value: The value bT-bit-DATA indicates the tunneled information. For details about the related parameters, see bT-TunnelInd-DATA. BearInfoTrans: bearer information transport, which is defined in the Bearer Control Tunneling Package.

MOD REQ (bT) (Receiver) bT-BearInfoTrans

name: The value bit, representing bearer information transport, indicates that the tunneled information is sent. value: The value bT-bit-DATA indicates the tunneled information. For details about the related parameters, see bT-TunnelInd-DATA.

MOD REQ (bT) (Sender) bT-BearInfoTrans

name: The value bit, representing bearer information transport, indicates that the tunneled information is sent and the related termination goes into the accepting negotiation response state. value: The value bT-bit-DATA indicates the tunneled information. For details about the related parameters, see bT-TunnelInd-DATA. Reference Standards For details about the Bearer Control Tunneling Package, see Annex A in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1950. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bT-TunnelInd-DATA Description of the IE Reference Standards The bT-TunnelInd-DATA indicates the tunneled information. Description of the IE Information Element (IE)

Description

tag: The value stag indicates an encoding format. hl: indicates the length of bT-TunnelInd-DATA with its header. l: The value 129 indicates an encoding format. v: The value 161 indicates that the length of bT-TunnelIndDATA is 161 bytes. ht: The value 4 indicates that an encoding format other than DoubleWrapping is used for encoding H.248 messages. vl: indicates the length of bT-TunnelInd-DATA without its header. l: The value 129 indicates an encoding format. v: The value 158 indicates that the length of bT-TunnelInd-

DATA (bctp and ipb parts) is 158 bytes. bctp: Bearer Control Tunneling Protocol, which is used to provide the tunneling mechanism. o1: The eighth bit of the first byte is permanently set to 0. bvei: version error indicator. The value 0 indicates no version error. The other value 1 indicates that the BCTP protocol version is not ed. i1: The sixth bit of the first byte is permanently set to 1. bctp-ver: version indicator. The value 0 indicates BCTP protocol version 1. o2: The eighth bit of the first byte is permanently set to 0. tpei: protocol error indicator. The value 0 indicates no protocol error. The other value 1 indicates that the BCTP protocol is not ed. tpi: protocol indicator. The value 32 indicates that information is transported using the IP Bearer Control Protocol (IPB) message of text format. ipb: indicates the IPB message entity.

NTFY REQ(bT) (Sender) bT-TunnelInd-DATA

v: version. The value 0 indicates the Session Description Protocol (SDP) version number. o: origin. The value 0 0 IN IP4 80.60.60.208 indicates the address of the session initiator. In the value 0 0 IN IP4 80.60.60.208, intelligent network (IN) indicates that the network type is Internet; IP4 indicates the Internet Protocol version 4 (IPv4) address type; 80.60.60.208 indicates the IP address used by the session initiator to send IPB messages. s: session name. The value - indicates null. c: connection information. The value IN IP4 80.60.60.208 indicates the IP address used by the Nb interface to carry media streams. t: start time and stop time. The value 0 indicates that this field is not in use. a: session attribute. The value ipb:1 Request indicates that IPB version 1 is used to initiate a request. m: media announcement. The value audio 492 RTP/AVP 96 indicates that media session type is audio, port number is 492, transport protocol is Real-Time Transport Protocol (RTP)/attribute-value pair (AVP), and payload type (PT) is

96. a: media attributes. The value ptime:5 indicates that the packetization time is 5 ms. a: media attributes. The value rtpmap:96 VND.3GPP.IUFP/16000 indicates that PT is 96, VND.3GPP.IUFP is a fixed field, and sampling frequency is 16000 Hz. For details about termination information in IPB messages, see localDescriptor.

NOTE: The SET IPB command can be used to set IPB negotiation parameters, such as Timeout(s) and PtimeFlag. An UP negotiation fails if the packetization time is different on the calling party and called party sides. Codec is not negotiated in IPB messages. The ADD MGC command can be used to set double wrapping.

NTFY REQ (bT) (Receiver) bT-TunnelInd-DATA

ipb: indicates the IPB message entity. a: session attribute. The value ipb:1 Accepted indicates that IPB version 1 is used to accept a request. m: media announcement. The value audio 508 RTP/AVP 96 indicates that media session type is audio, port number is 508, transport protocol is RTP/AVP, and PT is 96. NTFY REQ (bT) (Message trace on Tunneled information is presented in binary format in the messages the MGC) traced on the MGC. For details about the related parameters, see the bT-TunnelInd-DATA messages traced on the MGW. Reference Standards For details about BCTP, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1990. For details about SDP, see Internet Engineering Task Force (IETF) RFC 2327. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

action-indicator Description of the IE Reference Standards The action-indicator indicates the bearer establishment mode. Description of the IE Information Element (IE)

IAM (APP) action-indicator

Description

action-id-data: The value connect-forward indicates the forward bearer establishment. The other value connect-backward indicates the backward bearer establishment. NOTE: The ADD BICCTG command can be used to configure the bearer establishment mode on the MGC.

Reference Standards For details about Bearer Independent Call Control (BICC), see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.765.5. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bearer-Control-Tunnel Description of the IE Reference Standards The bearer-Control-Tunnel indicates the information related to bearer control tunneling. Description of the IE Information Element (IE) IAM (APP) bearer-ControlTunnel

Description

bearer-control-tunneling-indicator: The value 1 indicates that the bearer establishment mode is tunneling.

Reference Standards For details about Bearer Independent Call Control (BICC), see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.765.5. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bearer-Control-Info Description of the IE Reference Standards The bearer-Control-Info indicates the tunneled bearer control information. Description of the IE Information Element (IE)

Description

IAM (APP) bearer-Control-Info bearer-Control-Info: The tunneled bearer control information is sent between MGCs by means of Bearer Independent Call Control (BICC) messages. For details about the related parameters, see bTTunnelInd-DATA.

APM (Initiating bCI) bearer-Control-Info bearer-Control-Info: The tunneled bearer control information is sent between MGCs by means of BICC messages. For details about the related parameters, see bT-TunnelInd-DATA.

APM (Receiving bCI) bearer-Control-Info

bearer-Control-Info: The tunneled bearer control information is sent between MGCs by means of BICC messages. For details about the related parameters, see bT-TunnelInd-DATA. Reference Standards For details about BICC, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.765.5. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RTP/RT Protocol Description of the RTP/RT Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the RTP/RT Protocol Scenario Description Protocol Stack Message Structure IE Structure Message List Reference Standards Audio streams over IP are transmitted using the Datagram Protocol (UDP). As a protocol designed for data stream transmission, UDP does not address the specific needs of real-time data traffic, such as synchronization of media streams. For the transmission of real-time data, Internet Engineering Task Force (IETF) formulated the Real-time Transport Protocol (RTP) as an extension to UDP. RTP provides end-to-end delivery services for data with real-time characteristics, such as interactive audio and video. Those services include payload type identification, sequence numbering, timestamping, and delivery monitoring. RTP consists of two closely-linked parts: RTP: Carries data that has real-time properties. RTP Control Protocol (RT): Monitors the quality of service and conveys information about the participants in an on-going session. RTP allows for real-time transmission of audio and video and their synchronization. RT is used to monitor RTP packets and the quality of service (QoS). As RTP neither reserves resources nor ensures QoS of real-time services, RT is responsible for enhancing data transmission. RT is based on periodic transmission of control packets to all participants in a session, using the same transmission mechanism as data packets. RT performs the following functions: Provides on the quality of data transmission. The information contained in RT packets helps to diagnose network problems and control the transmission of RTP packets. Carries a persistent transport-level identifier for an RTP source, called the canonical name (CNAME). If a conflict is discovered or a program is restarted, synchronization source (SSRC) may change. Therefore, receivers require the CNAME to keep track of each participant.

Scenario Description RTP is used for audio stream transmission over the Nb interface, IP-enabled A or Iu interface, and IP over E1 (IPoE1). RT is used for monitoring RTP packets and QoS. Protocol Stack Figure 1 shows the RTP/RT protocol stack.

Figure 1 RTP/RT protocol stack Message Structure Figure 2 shows the hierarchical structure of the RTP/RT message. Figure 2 Hierarchical structure of the RTP/RT message

IE Structure Figure 3 shows the Information Element (IE) structure of the RTP message. Figure 3 IE structure of the RTP message

Figure 4 shows the IE structure of the RT message. Figure 4 IE structure of the RT message

Message List Table 1 lists RT messages. Table 1 RT messages Message Direction

Function

SR packet

The sender report (SR) packet provides statistics on BSC/RNC/MGW<- data packets sent and received by the sender. >MGW For details, see rtSR.

extension report (XR) packet

The extended report (XR) packet provides statistics BSC/RNC/MGW<- on extended information of data packets. >MGW For details, see rtXRVoIP.

RR packet

The receiver report (RR) packet provides statistics BSC/RNC/MGW<- on data packets received by the receiver. >MGW For details, see rtRR.

SDES packet

The source description (SDES) packet describes the BSC/RNC/MGW<- source of RT packets. >MGW For details, see rtSDES.

BYE packet

BSC/RNC/MGW<- The BYE packet indicates the end of audio >MGW transmission.

asymmetric digital The application-defined (APP) packet is intended for subscriber line experimental use as new applications and new (ADSL) Port BSC/RNC/MGW<- features are developed, for example, it can be used information >MGW for the RTP multiplex feature. Protocol (APP) For details, see rtAPP. packet Table 2 shows the commands used for RT messages. Table 2 Commands used for RT messages Message (Command)

Direction

RT_SEND_MSG

BSC/RNC/MGW<- Indicates the RT packet statistics sent by the >MGW local end.

RT_RCV_MSG

BSC/RNC/MGW<- Indicates the RT packet statistics received by >MGW the local end.

Function

Reference Standards For details about RTP/RT, see IETF RFC 3550. Parent topic: RTP/RT Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages There is no common part in Real-Time Transport Protocol (RTP)/Real-time Transport Control Protocol (RT) messages. Parent topic: RTP/RT Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages RT_SEND_MSG RT_RCV_MSG Parent topic: RTP/RT Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RT_SEND_MSG Message Function Associated IEs Message Function The RT_SEND_MSG indicates the Real-time Transport Control Protocol (RT) packet statistics sent by the local end. Figure 1 shows important IEs in the RT_SEND_MSG message.

Figure 1 RT_SEND_MSG message Associated IEs Information Element (IE)

Description

ip (ip header)

For details, see ip.

udp (udp header)

For details, see udp.

rt (rt packet)

For details, see rt.


RT_RCV_MSG Message Function Associated IEs Message Function The RT_RCV_MSG indicates the Real-time Transport Control Protocol (RT) packet statistics received by the local end. Figure 1 shows important IEs in the RT_RCV_MSG message.

Figure 1 RT_RCV_MSG message Associated IEs Information Element (IE)

Description

ip (ip header)

For details, see ip.

udp (udp header)

For details, see udp.

rt (rt packet)

For details, see rt.


Description of Associated IEs ip udp rt rtSR rtXRVoIP rtSDES rtRR rtAPP Parent topic: RTP/RT Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ip Description of the IE Reference Standards The ip header includes the IP version, IP packet length, and IP address. Description of the IE Information Element (IE)

Description

version: The value 4 indicates IP version 4. headerlen: header length. The value 5 indicates that the IP header length is 20 bytes (5 x 4). tos: type of service. If IPQoS attributes comply with the Differentiated Services Codepoint (DS) protocol, the DS field is used, where the most significant 6 bits represent a DS value and the least significant 2 bits are reserved. If the DS field has a value of 184, the most significant 3 bits, 101, indicate that the TOS is Expedited Forward (EF), which is generally used for low-delay services. The most significant 6 bits, 101110, indicate that the DS value is EF53(46), which is a default DS value. If IPQoS attributes comply with the TOS protocol, the TOS

field is used. The most significant 3 bits indicate priority, the following 4 bits indicate a TOS value, and the last bit must be reserved and set to 0. Different TOS values indicate varied forwarding strategies:

RT_SEND_MSG ip (ip header)

1000: 0100: 0010: 0001: 0000:

Minimize delay Maximize throughput Maximize reliability Minimize monetary cost Provide normal services

totallen: total length. The value 156 indicates that the total IP packet length is 156 bytes. identification: The value 17310 identifies a datagram. flags: The value 0 indicates the last fragment of a datagram that allows fragmentation. fragmentoffset: The value 0 indicates that the fragment offset is zero bytes (0 x 8). ttl: time to live. The value 128 indicates 128 seconds of lifespan. protocol: The value udp indicates that Datagram Protocol (UDP) is used for the data transport layer. checksum: The value 15466 indicates the IP header checksum. source-address: The value 80 60 13 15 indicates the source IP address. dest-address: The value 80 60 12 10 indicates the destination IP address. NOTE: The TOS byte is used in IP Diffserv, an IP quality of service (QoS) feature. The SET IPQOS command can be used to set IPQoS attributes. The SET PRITODS command can be used to set the mapping between the context priority and the DS value.

RT_RCV_MSG ip (ip header)

source-address: The value 80 60 12 10 indicates the source IP address. dest-address: The value 80 60 13 15 indicates the destination IP address. Reference Standards For details about the ip header, see Internet Engineering Task Force (IETF) Requirement For Comments (RFC) 791. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

udp Description of the IE Reference Standards The udp header includes the Datagram Protocol (UDP) port number and UDP packet length. Description of the IE Information Element (IE)

Description

RT_SEND_MSG udp (udp header)

RT_RCV_MSG udp (udp header)

Reference Standards

source-port: The value 63385 indicates the UDP port number used by the Real-time Transport Control Protocol (RT) packet sending end. It equals the UDP port number used by the local end to send Real-Time Transport Protocol (RTP) packets plus one. dest-port: The value 53369 indicates the UDP port number used by the RT packet receiving end. It equals the UDP port number used by the remote end to send RTP packets plus one. length: The value 136 indicates that the UDP packet length (including the UDP header) is 136 bytes. checksum: The value 0 indicates that checksum of the header and data is not calculated (the calculation of UDP checksum is optional).

source-port: The value 63385 indicates the UDP port number used by the RT packet sending end. dest-port: The value 53369 indicates the UDP port number used by the RT packet receiving end.

For details about the udp header, see Internet Engineering Task Force (IETF) RFC 768. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

rt Description of the IE Reference Standards The Real-time Transport Control Protocol (RT) packet includes the Real-Time Transport Protocol (RTP) version, packet type, sender report (SR) packet, and receiver report (RR) packet. Description of the IE Information Element (IE)

Description

ucbit2Version: The value 2 indicates RTP version 2. ucbit1PadFlag: The value 0 indicates that no padding is added after the payload. ucbit5Count: reception report count. The value 1 indicates that the RT packet contains one reception report. pktType: packet type. The value rctpSR indicates that the RT packet contains the sender report. rtSR: For details, see rtSR.

ucbit2Version: The value 2 indicates RTP version 2. ucbit1PadFlag: The value 0 indicates that no padding is added after the payload. ucbit5Count: The value 0 indicates that ucbit5Count is reserved. pktType: The value rtXRVoIP indicates that the RT packet contains the voice over IP (VoIP) extended report.

rtXRVoIP: For details, see rtXRVoIP.

RT_SEND_MSG rt (rt packet)

ucbit2Version: The value 2 indicates RTP version 2. ucbit1PadFlag: The value 0 indicates that no padding is added after the payload. ucbit5Count: refers to source count. The value 1 indicates the number of SSRCs and CSRCs contained in the source description (SDES) packet. pktType: The value rtSDES indicates that the RT packet contains the source description. rtSDES: For details, see rtSDES.

ucbit2Version: The value 2 indicates RTP version 2. ucbit1PadFlag: The value 0 indicates that no padding is added after the payload. ucbit5Count: refers to reception report count. The value 1 indicates that the RT packet contains one reception report. pktType: The value rctpRR indicates that the RT packet contains the receiver report. rtRR: For details, see rtRR.

ucbit2Version: The value 2 indicates RTP version 2. ucbit1PadFlag: The value 0 indicates that no padding is added after the payload.

ucbit5Count: refers to the subtype. The value 1 indicates that the subtype of the asymmetric digital subscriber line (ADSL) Port information Protocol (APP) packet is RTP multiplex negotiation packet. pktType: The value rctpAPP indicates that the RT packet is an APP packet. rtAPP: For details, see rtAPP. Reference Standards For details about RT packets, see section 6.4 "Sender and Receiver Reports" in RFC 3550. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

rtSR Description of the IE Reference Standards The rtSR report provides statistics about data packets sent and received by the sender. Description of the IE Information Element (IE)

Description

udwSsrc: synchronization source identifier. The value 3685259243 identifies the synchronization source of the sender report (SR). udwNtpSec: indicates the integer part (most significant) of the NodeB template file (NTP) time. udwNtpFrac: indicates the fractional part (least significant) of the NTP time. udwRtpTs: indicates the Real-Time Transport Protocol (RTP) timestamp used for time synchronization of RTP packets. udwPktSent: indicates the count of sent RTP packets. udwOctSent: indicates the count of sent octets. RtRcvrpt: indicates the reception of packets.

RT_SEND_MSG rtSR

udwSsrc: The value 3685759387 identifies the synchronization source of the received packets. udwbit8Fraction: fraction lost, indicating the RTP packet loss rate. The calculation formula is (udwbit8Fraction/256) x 100%.

udwbit24Lost: indicates the number of lost RTP packets. udwExtSeq: extended highest sequence number received, indicating the highest sequence number of the received RTP packet with extended information. udwJitter: indicates the interarrival jitter, measured in milliseconds. udwLsr: last SR timestamp, indicating the NTP time of the last received SR. The value 0 indicates that no SR is received. udwDlsr: delay since last SR. The value 0 indicates that no SR is received. NOTE: The SET RT command can be used to set Real-time Transport Control Protocol (RT) parameters, such as Switch to send RT packets or not and Alarm high threshold of fraction lost. If the local port detects that the packet loss rate of the RTP packets sent by the remote end is greater than or equal to Alarm high threshold of fraction lost during four consecutive RT packet sending periods, ALM-1023 Packet loss rate sent by remote end is reported. This alarm is cleared if the local port detects that the packet loss rate of the RTP packets sent by the remote end is smaller than that threshold during an RT packet sending period.

RT_RCV_MSG rtSR udwSsrc: The value 3685759387 identifies the synchronization source of the SR sent by the remote end. RtRcvrpt: indicates the reception of packets.

udwSsrc: The value 3685259243 identifies the synchronization source of the received packets. Reference Standards For details about the rtSR report, see section 6.4.1 "Sender Report RT Packet" in RFC 3550. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

rtXRVoIP Description of the IE Reference Standards The rtXRVoIP report provides metrics for monitoring voice over IP (VoIP) calls. Description of the IE Information Element (IE)

Description

udwSsrc: synchronization source identifier. The value 3685259243 identifies the synchronization source of the extension report (XR). xrBlockType: The value voipMetrics indicates that the report provides VoIP metrics. ucRes0: The value 0 indicates that ucRes0 is reserved. ucBlockLen: The value 8 indicates that the report block length

RT_SEND_MSG rtXRVoIP

(including the header) is 40 bytes (8 x 4 + 8). udwSrcSsrc: The value 3685759387 identifies the synchronization source of the XR report block. ucLossRate: The value 0 indicate that the Real-Time Transport Protocol (RTP) packet loss rate is 0. ucDiscardRate: The value 0 indicates that the RTP packet discard rate is 0. ucBurst Density: The value 0 indicates that the packet loss and discard rate within burst periods is 0. ucGap Density: The value 0 indicates that the packet loss and discard rate within inter-burst gaps is 0. ucBrustDruation: The value 0 indicates that the total duration of the burst periods that have occurred since the beginning of reception is 0. ucGapDuration: The value 0 indicates that the total duration of the gap periods that have occurred since the beginning of reception is 0. ucRoundDelay: The value 0 indicates that the round trip delay between RTP interfaces is not available. ucEndSysDelay: The value 0 indicates that the end system delay is not available. ucSignalLevel: The value 127 indicates that the signal level is not available. ucNoiseLevel: The value 127 indicates that the noise level is not available. ucRERL: residual echo return loss. The value 0 indicates that this parameter is not available. ucGmin: The value 16 indicates that the minimum gap threshold is 16. ucRfactor: refers to a voice quality metric. The value 127 indicates that this parameter is not available. ucExtRfactor: The value 127 indicates that this parameter is not available on the access side and the wireless side. ucMOSLQ: The value 127 indicates that the mean opinion score (MOS) for listening quality is not available. ucMOSCQ: The value 127 indicates that the MOS for conversational quality is not available. rxConfig: indicates the receiver configuration byte. bit2PLC: packet loss concealment. The value 3

indicates standard PLC. The other values are as follows: 2: enhanced 1: disabled 0: unspecified bit2JBA: jitter buffer adaptive. The value 0 indicates unknown. The other values are as follows: 3: adaptive 2: non-adaptive 1: reserved bit4JBRate: jitter buffer rate. The value 0 indicates that the adjustment time is unknown. ucRes1: reserved. uwJBNominal: The value 210 indicates that the nominal jitter buffer delay is 210 ms. ucJBMax: The value 320 indicates that the maximum jitter buffer delay is 320 ms. ucJBAbsMax: The value 4800 indicates that the absolute maximum jitter buffer delay is 4800 ms. NOTE: The PLC field is used in the enhanced PLC feature. The JBA field is used in the IP jitter buffer function. The Metrics Block in the Real-time Transport Control Protocol (RT) XR defines statistical information for monitoring the IP voice quality. The voice quality monitoring feature uses the collected statistics to calculate the MOS value and monitor the end-to-end voice quality. The SET TARA command can be used to set transmission convergence (TC) parameters, such as Packet loss compensation and Enable dynamic JB adaption. The SET RT command can be used to set RT parameters, such as RT XR mode and Gmin of RT XR. Reference Standards

For details about the rtXRVoIP report, see section 4 "Extended Report Blocks" in RFC 3611. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

rtSDES Description of the IE Reference Standards The rtSDES item describes the source of Real-time Transport Control Protocol (RT) packets and must contain the canonical end-point identifier (CNAME). Description of the IE Information Element (IE)

Description

RT_SEND_MSG rtSDES

RT_RCV_MSG rtSDES

udwSsrc: synchronization source identifier. The value 3685259243 identifies the synchronization source of the sender report (SR). cname: The value [email protected] indicates the CNAME identifier.

udwSsrc: The value 3685759387 identifies the synchronization source of the SR sent by the remote end. cname: The value [email protected] indicates the CNAME identifier.

Reference Standards For details about the rtSDES item, see section 6.5 "Source Description RT Packet" in RFC 3550. Parent topic: Description of Associated IEs


rtRR Description of the IE Reference Standards The rtRR report provides statistics only on the data packets received by the receiver (such as MGW). Description of the IE Information Element (IE)

Description

udwSsrc: synchronization source identifier. The value 2563960243 identifies the synchronization source of the receiver report (RR). RtRcvrpt: indicates the reception of packets. RT_SEND_MSG rtRR

udwbit8Fraction: fraction lost, indicating the RealTime Transport Protocol (RTP) packet loss rate. udwbit24Lost: indicates the number of lost RTP packets. udwExtSeq: extended highest sequence number received, indicating the highest sequence number of the received RTP packet with extended information. udwJitter: indicates the interarrival jitter, measured in milliseconds. udwLsr: last sender report (SR) timestamp, indicating the NodeB template file (NTP) time of the last received SR. The value 0 indicates that no SR is received. udwDlsr: delay since last SR. The value 0 indicates that no SR is received.

Reference Standards For details about the rtRR report, see section 6.4.2 "Receiver Report Real-time Transport Control Protocol (RT) Packet" in RFC 3550. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

rtAPP Description of the IE Reference Standards The rtAPP packet is intended for experimental use as new applications and new features are developed. This section describes its use for Real-Time Transport Protocol (RTP) multiplex negotiation. Description of the IE Information Element (IE)

Description

udwSsrc: synchronization source identifier. The value 2563960243 identifies the synchronization source of the ADSL Port information Protocol (APP). name: The name is 3GPP constantly. rtpmux: indicates RTP multiplex attributes.

RT_SEND_MSG rtAPP

bit1Mux: The value 1 indicates for the noncompressed RTP multiplex capability of the receiver. The other value 0 indicates no . bit1: The value 0 indicates no for the compressed RTP multiplex capability of the receiver. The other value 1 indicates for the compressed RTP multiplex capability of the receiver. bit2Selection: The value 1 indicates for the non-compressed RTP multiplex capability of the sender.

The other values are as follows: 0: not non-compressed RTP multiplex capability of the sender. 2: compressed RTP multiplex capability of the sender. 3: reserved. bit15LocalPort: The value 512 indicates that the number of the port receiving RTP multiplex packets is 1024 (512 x 2). NOTE: The MOD IPIF command can be used to set the RTP multiplex capability. The SET RTPMUX command can be used to set the number of the port receiving RTP multiplex packets.

RT_RECV_MSG rtAPP udwSsrc: The value 333759004 identifies the synchronization source of the APP. name: The name is 3GPP constantly. Reference Standards For details about the rtAPP packet, see section 6.7 "Application-Defined Real-time Transport Control Protocol (RT) Packet" in RFC 3550. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CAP Protocol Description of the CAP Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the CAP Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The MSC serves as an MSC server or a GMSC server in the Universal Mobile Telecommunications System (UMTS) R4 network, and is embedded with the SSP functional entity. The Customized Applications for Mobile network Enhanced Logic (CAMEL) Application Part (CAP) protocol is used over the CAP interface between the MSC and the S, as shown in Figure 1.

Figure 1 Application of the CAP protocol Protocol Stack The MSC s two modes for CAP protocol transmission: TDM-based: The CAP protocol information is transferred using services provided by the Message Transfer Part (MTP). IP-based: The CAP protocol information is transferred using services provided by the Signaling Transport (SIGTRAN) protocol. Figure 2 shows the CAP protocol stack. Figure 2 CAP protocol stack

Message Structure Figure 3 shows the structure of a CAP message. Figure 3 CAP message structure

In the Signaling System No.7 (SS7), the CAP messages are transferred as the components of the Transaction Capability Application Part (TCAP) messages. The ASN.1 format is adopted for the coding of the CAP messages. The CAP message types are in one-to-one relationship with the operation codes in TCAP components. In the message transfer process, each time an operation is initiated, an invoke ID is allocated. The invoke ID identifies an operation in a certain direction in a CAP dialog. Based on the invoke ID, a component can be "translated" into the corresponding CAP message. The message translation between the CAP and the TCAP is implemented by the Functional Entity Access

Manager (FEAM). Message List Interaction between different functional entities of the Mobile Intelligent Network (MIN) is implemented through various operations defined in the CAP protocol. The defined operation set varies according to the phase of the CAP protocol. In CAMEL Phase 3, 32 CAP operations are defined, wherein 24 operations are call specific and 8 operations are short message specific. Table 1 lists the common CAP messages. Table 1 List of common CAP messages Message

Direction

Function

Initial detection point (DP)

MSC -> S

This message is used to activate the intelligent network (IN) call flow.

Request Report basic call state model (BCSM) Event

S-> MSC

This message is used to specify the BCSM event to be reported in the current call.

S -> MSC

This message is used to change some parameters, such as the called address and calling number display, of the current call so that the current call proceeds according to the service requirements.

S -> MSC

This message is used to control the duration of the current call. It contains the control parameters, such as the maximum call duration and the tariff switch interval. When the actual call duration reaches the maximum call duration or when the caller or callee releases the call, the MSC sends an Apply Charging Report message to notify the S.

MSC -> S

This message is used to report the actual duration of the current call and other relevant information. The MSC sends this message when the actual call duration reaches the maximum call duration or when the caller or callee releases the call.

Connect

Apply Charging

Apply Charging Report

This message is used to send the e parameter to the MSC. It contains the Charge

Furnish Charging Information

S -> MSC

Advice Information (CAI), which can be used to replace the CAI generated by the MSC and inhibit any further generation of the CAI by the MSC.

S -> MSC

This message is used to request the MSC to proceed with the processing of the suspended call.

Event Report BCSM

MSC -> S

This message is used to notify the S of a call-related event previously requested by the S.

Play Announcement

S -> MSC

This message is used to request the MSC to play an announcement to the subscriber.

S -> MSC

This message is used to request the MSC to play an announcement to the subscriber. This announcement notifies the subscriber to enter relevant information, such as the and .

MSC -> S

This message is used to notify the S that a Play Announcement operation has been completed.

Connect To Resource

S -> MSC

This message is used to connect a call segment from the GSM service switching function (gsmSSF) to a specialized local resource.

Any Time Interrogation

S -> HLR

This message is used to query the location and status information of a subscriber.

Continue

Prompt And Collect Information

Specialized Resource Report

Any Time Interrogation HLR -> S ACKnowledgement (ACK)

This message is used to return the requested location and status information of a subscriber.

Parent topic: CAP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages The CAMEL Application Part (CAP) messages do not contain any common part. Parent topic: CAP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages Initial DP Request Report BCSM Event Connect Apply Charging Apply Charging Report Furnish Charging Information Continue Event Report BCSM Play Announcement Prompt And Collect Information Specialized Resource Report Connect To Resource Any Time Interrogation Request Any Time Interrogation ACK Disconnect Forward Connection Parent topic: CAP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Initial DP Message Function Associated IEs Reference Standards Message Function The Initial Detection Point (DP) message is sent from the MSC to the S. The MSC generates the Initial DP message when a trigger is detected at a DP in the basic call state model (BCSM). The Initial DP message contains information required by the S, such as the calling number, called number, caller location, callee location, and subscriber status. The IDP message also contains key parameters such as the service key. Figure 1 shows the main IEs of the message.

Figure 1 Initial DP message


Description

ServiceKey

Identifies a type of Customized Applications for Mobile network Enhanced Logic (CAMEL) service in the S service logic. For details, see ServiceKey.

CalledPartyNumber

Indicates the called number. This IE is mandatory in the Mobile Terminated Call (MTC) flow and the Call Forwarding (CF) flow, and is optional in the Mobile Originated Call (MOC) flow. For details, see CalledPartyNumber.

CallingPartyNumber

Indicates the Mobile Station International ISDN Number (MSISDN) of the caller, for example, 8613903000001. For details, see CallingPartyNumber.

CallingPartys Category

Indicates the caller category. Caller are categorized into operator, pay phone, and ordinary subscriber. For details, see CallingPartys Category.

CallReference Number

Identify a call. This IE provides the call reference number allocated by the GMSC/MSC for the call. For details, see CallReference Number.

ipSSPCapabilities

Indicates which GSM specialized resource function (gsmSRF) resources are available within the visited mobile switching center (VMSC)/GMSC where the GSM service switching function (gsmSSF) resides. It notifies the S of the available resources configured on the VMSC/GMSC/gsmSSF. For details, see ipSSPCapabilities.

LocationNumber

Indicates the area code of the location. When the Calling Party Number does not contain any caller location information, this IE indicates the caller location. The format is Country code + Area code, for example, 8610. For details, see LocationNumber.

locationInformation

Indicates the location information. For details, see locationInformation.

international mobile subscriber identity (IMSI)

Identifies a mobile subscriber. For details, see IMSI.

SubscriberState

Indicates the current state of the subscriber. The states are CAMEL Busy, Network Determined Not Reachable, and Assumed Idle. For details, see SubscriberState.

MSCAddress

Indicates the MSC address. For details, see MSCAddress.

bearcapability

Indicates the bearer capability connection to the subscriber. For details, see bearcapability.

EventTypeBCSM

Indicates the configuration event detection point (EDP) event that triggers the current Initial DP event. Common EventTypeBCSMs are collectedInfo, termAttemptAuthorized(12), analyzedInformation, routeSelectFailure, oCalledPartyBusy, and oNoAnswer. DP2 is the mobile originated (MO) CAMEL service, and DP12 is the mobile terminated (MT) CAMEL service. For details, see eventTypeBCSM.

timeZone

Indicates the time that the CAMEL service is triggered and the time zone where the MSC that triggers the CAMEL service is located. For details, see timeZone.

Reference Standards For details, see 4.6.1.8 "Initial DP" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Request Report BCSM Event Message Function Associated IEs Reference Standards Message Function The Request Report basic call state model (BCSM) Event (RRBE) message is sent from the S to the MSC. According to the service requirements, the S uses the RRBE message to request the MSC to monitor the call-specific BCSM event. On receiving this message, the MSC records the BCSM event for which the S requests a report, and then notifies the S of the event through the Event Report BCSM message when this BCSM event occurs. The RRBE message contains the event to be monitored. Figure 1 shows the main IEs of the message. Figure 1 Request Report BCSM Event (RRBE) message


Description

eventTypeBCSM

Indicates the event type, that is, the detection point (DP) that the MSC is requested to monitor. collectedInfo and termAttemptAuthorized are invalid values of the eventTypeBCSM. For details, see eventTypeBCSM. Indicates the mode in which the event is reported. The values are as follows:

Monitor Mode

interrupted: indicates that the event is reported as a request. The MSC performs the subsequent processing only after the response is received. notifyandcontinue: indicates that the event is reported as a notification. The MSC performs the subsequent processing without receiving any response from the S. transparent: indicates that the event is not reported to the SCF. For details, see Monitor Mode. Indicates the party whose call events shall be reported to the SCF. The SCF can use only the option sendingSideID. If sendingSideID is not available, the following default values of legID are used:

legID

For the event types O-Abandon and T-Abandon, the default value of legID is 1. For the event types RouteSelectFailure, OCalledPartyBusy, O-NoAnswer, OAnswer, O-NotReachable, TCalledPartyBusy, T-NoAnswer, TAnswer, and T-NotReachable, the default value of legID is 2. For the event types O_Disconnect

and T_Disconnect, the value of legID ID must be explicitly given. For details, see legID.

Application Timer

Indicates the timer duration for No_Answer event. If the answer message is not received after this timer expires, the MSC reports the No_Answer event. Note that this duration must be shorter than the duration of the network No_Answer timer. For details, see Application Timer.

Reference Standards For details, see 4.6.2.14 "Request Report BCSM Event" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Connect Message Function Associated IEs Reference Standards Message Function The Connect message is sent from the S to the MSC. The S uses this message to change some parameters, such as the called address and calling number display, of the current call so that the current call proceeds according to the service requirements. Figure 1 shows the main IEs of the message. Figure 1 CONNECT message


Description

Destination Routing Address

Indicates the number to which the call is routed. It is a mandatory IE. For details, see Destination Routing Address.

Original Called Party ID

Indicates the original called number. This IE is present when the call is forwarded. For details, see Original Called Party ID.

Redirecting Party ID

Indicates the redirecting number from which the route is forwarded. For details, see Redirecting Party ID.

Redirection Information

Indicates the redirecting information, such as the forwarding times and forwarding reason. For details, see Redirection Information.

Generic Number

Indicates the generic number. This generic number is used to overwrite the calling line ID presented to the callee and is filled in the calling number field in the call detail record (CDR). For details, see Generic Number.

Alerting Pattern


Reference Standards For details, see 4.6.2.6 "Connect" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Apply Charging Message Function Associated IEs Reference Standards Message Function The Apply Charging (AC) message is sent from the S to the MSC. This message is used to control the duration of the current call. The AC message contains the control parameters, such as the maximum call duration and the tariff switch interval. When the actual call duration reaches the maximum call duration or when the caller or callee releases the call, the MSC sends an Apply Charging Report message to notify the S. Figure 1 shows the main IEs of the message.

Figure 1 Apply Charging message Associated IEs Information Element (IE)

Description

BillingCharging Characteristics

Indicates a list of parameters required for the Customer Engineer (CSE) control of call duration. It contains information, such as maxCallPeriodDuration, releaseIfdurationExceeded, and PlayTone. For details, see BillingCharging Characteristics. Indicates the maximum call duration of the current call. In the prepaid service (PPS) service, the value of MaxCallPeriod Duration is 15 minutes. If the duration of the last segment of conversation is equal to or shorter than one minute, the duration of the

MaxCallPeriod Duration

last but two segment of conversation must be configured as the duration of the last segment of conversation and set to a value between 15 and 16. In this way, the subscriber can still hear the announcement in the last minute of the conversation. For details, see MaxCallPeriod Duration.

releaseIfdurationExceeded

Indicates whether the call is released after the maximum call duration is reached. In normally cases, the value of this IE is FALSE. The value of this IE is TRUE (indicating that the call is released) in the last Apply Charging (AC) message only when the balance of the subscriber is sufficient only for one AC operation. For details, see releaseIfdurationExceeded.

Tariff Switch Interval

Indicates the tariff switch interval, that is, the time interval at which the tariff is switched. For details, see Tariff Switch Interval.

PartyToCharge

Indicates the party to be charged in a call. This IE must be present in the Apply Charging Report (ACR) message sent by the MSC. For details, see PartyToCharge.

sendCalculationToSIndication

Indicates that the MSC sends the Apply Charging Report (ACR) message after the maximum call duration specified in the Apply Charging (AC) message is reached. This IE is always set to TRUE. For details, see sendCalculationToSIndication.

PlayTone

Indicates that the MSC plays a warning tone or an announcement when the balance of the subscriber is insufficient. The MSC determines whether the announcement is played one minute or three minutes before the balance of the subscriber is exhausted. The IE PlayTone is present in the last Apply Charging (AC) message only when the value of the IE ReleaseIfDuration Exceeded is TRUE.

For details, see PlayTone. Reference Standards For details, see 4.6.2.2 "Apply Charging" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Apply Charging Report Message Function Associated IEs Reference Standards Message Function The Apply Charging Report (ACR) message is sent from the MSC to the S. When the actual call duration reaches the maximum call duration or when the caller or callee releases the call, the MSC sends the ACR message to the S, notifying the S of the actual call duration and other relevant information. Figure 1 shows the main IEs of the message.

Figure 1 Apply Charging Report message Associated IEs Information Element (IE)

Description

CallResult

Indicates the charging information requested by the SCF in the Apply Charging message. For details, see CallResult.

timeIfNoTariffSwitch

This IE is present only when no tariff switch has occurred. This IE is mutually exclusive with the IE timeIfTariffSwitch. For details, see timeIfNoTariffSwitch. This IE is present only when tariff switch has

occurred. It indicates the conversation duration before and after the tariff is switched. This IE contains the following information: Time SinceTariff Switch: indicates the conversation duration from the time that tariff switch occurs in the time that the ACR message is sent. Tariff Switch Interval: indicates the conversation duration from the time that the Apply Charging (AC) message is sent to the time that tariff switch occurs.

timeIfTariffSwitch

For details, see timeIfTariffSwitch.

partyToCharge

Indicates the party to be charged in a call. leg1 refers to the caller and leg2 refers to the callee. For details, see PartyToCharge.

CallActive

Indicates the call status (active or released) when the ACR message is sent. It is one of the criteria based on which the S determines whether to send the next AC message after receiving the ACR message. For details, see CallActive.

Reference Standards For details, see 4.6.1.2 "Apply Charging Report" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Furnish Charging Information Message Function Associated IEs Reference Standards Message Function The Furnish Charging Information (FCI) message is sent from the S to the MSC. The S uses this message to send the e parameter to the MSC. The FCI message contains the Charge Advice Information (CAI), which can be used to replace the CAI generated by the MSC and inhibit any further generation of the CAI by the MSC. Figure 1 shows the main IEs of the message. Relevant IEs in the FCI message sent by the S are filled in the CDRs to identify the CDRs and facilitate call detail record (CDR) sorting.

Figure 1 Furnish Charging Information message Associated IEs Information Element (IE)

FreeFormatData

Description Indicates the relevant charging information. This IE contains the free-format billing and/or charging characteristics. The MSC must insert the contents contained by this IE to the Customized Applications for Mobile network

Enhanced Logic (CAMEL) CDR. For details, see FreeFormatData. Indicates the party (caller or callee) to be charged or the party for which the CDR is generated. For details, see PartyToCharge.

PartyToCharge

Indicates how the MSC processes multiple FCIs that are sent in a flow. If the value is Append, it indicates that the next FCI is appended to the previous FCI. If the value is Overwrite, it indicates that the previous FCI is overwritten by the next FCI.

AppendFreeFormat Data

For details, see AppendFreeFormat Data. Reference Standards For details, see 4.6.2.12 "Furnish Charging Information" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Continue Message Function Associated IEs Reference Standards Message Function The Continue message is sent from the S to the MSC. The S uses this message to request the MSC to proceed with the processing of the suspended call. The Continue message does not contain any Information Element (IE), as shown in Figure 1.

Figure 1 Continue message Associated IEs IE

Description

None

None

Reference Standards For details, see 4.6.2.8 "Continue" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages


Event Report BCSM Message Function Associated IEs Reference Standards Message Function The Event Report BCSM (ERB) message is sent from the MSC to the S. On receiving the request report BCSM event (RRBE) message, the MSC records the event for which the S requests a report. When this event occurs, the MSC notifies the S of the event through the ERB message and the S determines the subsequent processing based on the event type. An RRBE message can request monitoring of multiple events, but these events are reported in different ERB messages. Figure 1 shows the main IEs of the Event Report basic call state model (BCSM) message.

Figure 1 Event Report BCSM message Associated IEs Information Element (IE)

Description

eventTypeBCSM

Indicates the type of the event to the reported. For details, see eventTypeBCSM. Indicates the call information related to the

specified event.

eventSpecificInformationBCSM

If the event is RouteSelectFailure, the IE eventSpecificInformationBCSM contains the failure cause (if available). If the event is O-Busy or T-Busy, the IE eventSpecificInformationBCSM contains the busy cause (if available). If the event is O-NoAnswer or TNoAnswer, the IE eventSpecificInformationBCSM is empty. If the event is O-Answer or TAnswer, the IE eventSpecificInformationBCSM is empty. If the event is O-Disconnect or TDisconnect, the IE eventSpecificInformationBCSM contains the release cause (if available). If the event type is O-NotReachable or T-NotReachable, the IE eventSpecificInformationBCSM contains the release cause (if available). For details, see eventSpecificInformationBCSM.

legID

Indicates the party whose call events shall be reported to the GSM service switching function (gsmSSF). The gsmSSF can use only the option receivingSideID. If the value of legID is 1, it indicates that the call events of the caller shall be reported to the gsmSSF. If the value of legID is 2, it indicates that the call events of the callee shall be reported to the gsmSSF. For details, see legID.

Reference Standards For details, see 4.6.1.4 "Event Report BCSM" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Play Announcement Message Function Associated IEs Reference Standards Message Function The Play Announcement message is sent from the S to the assistant MSC. When subscribers interact with other in a Customized Applications for Mobile network Enhanced Logic (CAMEL) call, the S sends this message to the MSC, requesting the MSC to play an announcement to the subscriber. In this process, the MSC serves as a signaling relay. On receiving the Play Announcement message, the MSC forwards this message to the relevant MSC. Figure 1 shows the main IEs of the message.

Figure 1 Play Announcement message Associated IEs Information Element (IE)

Description

informationToSend

Indicates the information to be sent. For details, see informationToSend. It contains the following IEs:

inbandInfo

Message ID: indicates the message(s) to be sent. Number Of Repetitions: indicates the maximum number of times the message shall be sent to the subscriber. It is an optional IE. Duration: indicates the maximum duration that the message shall be played or repeated. The value 0 indicates endless repetition. It is an optional IE. Interval: indicates the time interval between successive messages. It is an optional IE. For details, see inbandInfo. Indicates the tone information. It contains the following information:

tone

ToneID: identifies a tone. Duration: indicates the duration of the tone. It is an optional IE. For details, see tone. Indicates whether to release the connection between the special resource and the subscriber after the announcement is complete.

disconnectFromIPForbidden

If the value is TRUE, it indicates that disconnecting the subscriber from the special resource is prohibited. If the value is FALSE, it indicates that disconnecting the subscriber from the special resource is permitted. For details, see disconnectFromIPForbidden.

requestAnnouncementComplete

Indicates whether to send the Special Resource Report (SRR) after the tone or announcement is complete. For details, see requestAnnouncementComplete.

Reference Standards For details, see 4.6.3.3 "Play Announcement" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Prompt And Collect Information Message Function Associated IEs Reference Standards Message Function The Prompt And Collect Information message is sent from the S to the assistant MSC. When subscribers interact with other in a Customized Applications for Mobile network Enhanced Logic (CAMEL) call, the S sends this message to the MSC, requesting the MSC to play an announcement to the subscriber. This announcement notifies the subscriber to enter relevant information, such as the and . After the MSC collects the information entered by the subscriber, it sends the collected information as the result of the Prompt And Collect Information message to the S. In this process, the MSC serves as a signaling relay. On receiving the Prompt And Collect Information message, the MSC forwards this message to the controlling MSC. Figure 1 shows the main IEs of the message. Figure 1 Prompt And Collect Information message


Description Indicates the subscriber information to be

Collected Info

collected. For details, see Collected Info.

minimumNbOfDigits

Indicates the minimum number of valid digits to be collected. For details, see minimumNbOfDigits.

maximumNbOfDigits

Indicates the maximum number of valid digits to be collected. For details, see maximumNbOfDigits.

endOfReplyDigit

Indicates the digit string used to signal the end of input. It is an optional IE. For details, see endOfReplyDigit.

cancelDigit

Indicates the cancel digit string that may be entered by the to request a retry. It is an optional IE. For details, see cancelDigit.

startDigit

Indicates the start digit string that denotes the start of the valid digits to be collected. It is an optional IE. For details, see startDigit.

firstDigitTimeOut

Indicates the duration of the first-digit timer. It is an optional IE. If this IE is not present, the MSC uses a default value for the firstdigit timer. The default value is 10 seconds and is configurable. If the subscriber does not enter any valid information before the first-digit timer expires, the MSC performs the timeout processing. For details, see firstDigitTimeOut.

interDigitTimeOut

Indicates the duration of the inter-digit timer. It is an optional IE. If this IE is not present, the MSC uses a default value for the interdigit timer. The default value is 10 seconds and is configurable. When the subscriber enters the information, if the interval between two keystrokes exceeds the duration of the inter-digit timer, the MSC performs the timeout processing. For details, see interDigitTimeOut. Indicates the specific action to be taken

errorTreatment

when errors occur, that is, the processing mode of the MSC when the input of the subscriber is invalid or incorrect. For details, see errorTreatment.

interruptableAnnInd

Indicates whether to interrupt the announcement after the first valid digit is received by the MSC. If the value of this IE is TRUE, the announcement is interrupted after the first valid digit is received by the MSC. If the value of this IE is FALSE, the announcement is not interrupted after the first valid digit is received by the MSC. For details, see interruptableAnnInd.

informationToSend

Indicates the information to be sent. The values are inbandInfo and tone. For details, see informationToSend. It contains the following IEs:

inbandInfo

Message ID: indicates the message(s) to be sent. Number Of Repetitions: indicates the maximum number of times the message shall be sent to the subscriber. It is an optional IE. Duration: indicates the maximum duration that the message shall be played or repeated. The value 0 indicates endless repetition. It is an optional IE. Interval: indicates the time interval between successive messages. It is an optional IE. For details, see inbandInfo. It contains the following IEs:

tone

ToneID: identifies a tone. Duration: indicates the duration of the tone. It is an optional IE. For details, see tone. Indicates whether to release the connection between the special resource and the


subscriber after the announcement is complete. For details, see disconnectFromIPForbidden.

Reference Standards For details, see 4.6.3.4 "Prompt And Collect Information" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Specialized Resource Report Message Function Associated IEs Reference Standards Message Function The Specialized Resource Report (SRR) message is sent from the MSC to the S. The MSC uses this message to notify the S that a Play Announcement operation has been completed. The SRR message is a null message, as shown in Figure 1.

Figure 1 Specialized Resource Report message Associated IEs Information Element (IE)

Description

None

None

Reference Standards For details, see 4.6.4.4 "Specialized Resource Report" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Connect To Resource Message Function Associated IEs Reference Standards Message Function The Connect To Resource message is sent from the S to the MSC. The GSM service control function (gsmSCF) uses this operation to connect a call segment from the GSM service switching function (gsmSSF) to a specialized local resource. After the successful connection to the GSM specialized resource function (gsmSRF), the gsmSCF can interact with the subscriber. The gsmSSF relays all operations for the gsmSRF and all responses from the gsmSRF. Figure 1 shows the main IEs of the message. Figure 1 Connect To Resource message


Description

resourceAddress

Indicates the physical address of the gsmSRF. For details, see resourceAddress.

iPRoutingAddress

Indicates the routing address to set up a connection to the gsmSRF. For details, see iPRoutingAddress.

none

Indicates that the call segment shall be connected to a predefined gsmSRF. Indicates whether to set up the connection

serviceInteractionIndicatorsTwo

between the caller and the gsmSRF. This IE is sent from the gsmSCF to the gsmSSF. For details, see serviceInteractionIndicatorsTwo.

Reference Standards For details, see 4.6.2.7 "Connect To Resource" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Any Time Interrogation Request Message Function Associated IEs Reference Standards Message Function The Any Time Interrogation Request message is sent from the GSM service control function (gsmSCF) to the home location (HLR) serving called parties so that the gsmSCF can query subscriber information, such as the location, status, IMEI (with software version), and MS classmark information for the requested domain, from the HLR at any time. Figure 1 shows the information elements (IEs) contained in the message. Figure 1 IEs contained in the Any Time Interrogation Request message

Associated IEs IE Subscriber Identity

Description Identifies the subscriber whose information is being requested. This IE is either the subscriber's IMSI or MSISDN. Indicates the type of subscriber information being requested. This IE includes the following parameters: Location Information (optional): Indicates that the Location Information is requested.

Requested Info

Subscriber State (optional): Indicates that the Subscriber State is requested. Current Location (optional with a specific requirement): Indicates that the Current Location is requested. This parameter must be present together with Location Information. Location Information in EPS ed (optional with a specific requirement): Indicates by its presence that Location Information in EPS is ed. This parameter must be present together with Location Information. Requested Domain (mandatory): Indicates for which domain the subscriber info is requested. It shall be either of the following: CS domain PS domain IMEI (with software version) (optional): Indicates that the IMEI (with software version) is requested. MS class mark information for the requested domain (optional): Indicates that the MS classmark information for the indicated domain is requested.

gsmSCF Address

Indicates the address of the interrogating gsmSCF. The gsmSCF Address shall be in international E.164 format.

Reference Standards For details about the Any Time Interrogation Request message, see 11.3.3.1 "Any Time Interrogation Request" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Any Time Interrogation ACK Message Function Associated IEs Reference Standards Message Function The Any Time Interrogation ACK (ATI ACK) message is sent from the HLR to the gsmSCF. The HLR uses this message to return the requested subscriber location and/or subscriber state information to the gsmSCF. Associated IEs The table shows the main information elements (IEs) in the message. The following information elements (IEs) are optional: Information Element(IE) Description LocationInformation Location Information For GPRS Subscriber State PS Domain Subscriber State IMEI (with software version) MS Classmark 2

Indicates the location of the served subscriber in the MSC/VLR. Indicates the location of the served subscriber in the SGSN. Indicates the state of the MS in the CS domain. Indicates the state of the MS in the PS Domain. This IE contains the IMEISV of the ME in use by the served subscriber. This IE contains the MS classmark 2, which is returned by the MS when it responds to paging in the CS domain.

Reference Standards For details, see 11.3.4.1 "Any Time Interrogation Request ACK" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Disconnect Forward Connection Message Function Associated IEs Reference Standards Message Function The Disconnect Forward Connection message is sent from the S to the MSC. This message instructs the MSC to disconnect from the GSM specialized resource function (gsmSRF). The message does not contain any Information Element (IE), as shown in Figure 1. Figure 1 Disconnect Forward Connection message

Associated IEs IE

Description

None

None

Reference Standards For details, see 4.6.2.10 "Disconnect Forward Connection" in 3rd Generation Partnership Project (3GPP) 23.078. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs ipSSPCapabilities Alerting Pattern AppendFreeFormat Data Application Timer bearcapability BillingCharging Characteristics CallActive CalledPartyNumber CallingPartyNumber CallingPartys Category CallReference Number CallResult cancelDigit Collected Info Destination Routing Address disconnectFromIPForbidden endOfReplyDigit errorTreatment eventSpecificInformationBCSM eventTypeBCSM firstDigitTimeOut FreeFormatData Generic Number IMSI inbandInfo informationToSend

interDigitTimeOut interruptableAnnInd iPRoutingAddress legID locationInformation LocationNumber MaxCallPeriod Duration maximumNbOfDigits minimumNbOfDigits Monitor Mode MSCAddress Original Called Party ID PartyToCharge PlayTone Redirecting Party ID Redirection Information releaseIfdurationExceeded requestAnnouncementComplete resourceAddress sendCalculationToSIndication serviceInteractionIndicatorsTwo ServiceKey startDigit SubscriberState Tariff Switch Interval timeIfNoTariffSwitch timeIfTariffSwitch timeZone

tone Parent topic: CAP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ipSSPCapabilities Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the IP/SSP capabilities ed by the MSC. These capabilities are defined as optional in the CAMEL Application Part (CAP) protocol.

ipSSPCapabilities

IPRoutingAddressed: indicates whether the MSC s the field IPRoutingAddress in the ConnectToResource (CTR) message. VoiceBacked: indicates whether the number dialed by the subscriber can be announced back to the subscriber after the MSC collects the number. The initial detection point (DP) message is considered as an example here. In this example, the value of IPRoutingAddressed is yes, indicating that the MSC s the field IPRoutingAddress in the CTR message. The value of VoiceBacked is yes, indicating the number dialed by the subscriber can be announced back to the subscriber after the MSC collects the number. You can configure the parameters contained

by the IE ipSSPCapabilities by setting IP/SSP capability in the ADD SSPCAPA command. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Alerting Pattern Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the alerting pattern to be applied.

Alerting Pattern: indicates the alerting pattern to be applied. The Connect message is considered as an example here. In this example, the value of Alerting Pattern is 0x11, indicating that the key value of the alerting pattern of the subscriber is 0x11.

Alerting Pattern

Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

AppendFreeFormat Data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates how the MSC processes multiple FCIs that are sent in a flow. If the value is Append, it indicates that the next furnish charging information (FCI) is appended to the previous FCI. If the value is Overwrite, it indicates that the previous FCI is overwritten by the next FCI.

AppendFreeFormat Data AppendFreeFormatData: indicates how the MSC processes multiple FCIs that are sent in a flow. The Furnish Charging Information is considered as an example here. In this example, the value of AppendFreeFormat Data is Overwrite, indicating that the previous FCI is overwritten by the next FCI. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Application Timer Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the timer duration for No_Answer event. If the answer message is not received after this timer expires, the MSC reports the No_Answer event. Note that this duration must be shorter than the duration of the network No_Answer timer.

Application Timer

ApplicationTimer: indicates the timer duration for No_Answer event. The Request Report basic call state model

(BCSM) Event is considered as an example here. In this example, the value of Application Timer is 40, indicating that the MSC reports the No_Answer event if the answer message is not received within 40 seconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

bearcapability Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the bearer capability connection to the subscriber.

bearcapability

informationTransferCapability: indicates the transfer capability. transferMode: indicates the transfer mode. The Initial detection point (DP) is considered as an example here. In this example, the value of informationTransferCapability is speech, indicating the speech transmission is ed; the value of transferMode is circuit-mode, indicating that the transfer mode is the circuit mode.


BillingCharging Characteristics Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a list of parameters required for the Customer Engineer (CSE) control of call duration. It contains information, such as maxCallPeriodDuration, releaseIfdurationExceeded, and PlayTone.

BillingCharging Characteristics

The Apply Charging is considered as an example here. In this example, the value of maxCallPeriodDuration is 600, indicating that the maximum call duration is 60 seconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CallActive Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the call status (active or released) when the ACR message is sent. It is one of the criteria based on which the S determines whether to send the next Apply Charging (AC) message after receiving the Apply Charging Report (ACR) message.

CallActive

The Apply Charging Report message is considered as an example here. In this example, the value of CallActive is FALSE, indicating that the call is released. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CalledPartyNumber Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the called number. This IE is mandatory in the Mobile Terminated Call (MTC) flow and the Call Forwarding (CF) flow, and is optional in the Mobile Originated Call (MOC) flow.

CalledPartyNumber

The Initial detection point (DP) message is considered as an example here. In this example, the called number is 8613907550446. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CallingPartyNumber Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the calling number.

CallingPartyNumber The Initial detection point (DP) message is considered as an example here. In this example, the calling number is 8613907521137 (international number). Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CallingPartys Category Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the caller category.

The Initial detection point (DP) message is considered as an example here. In this example, the value of CallingPartys Category is ordinary subscriber, indicating that the caller is an ordinary subscriber.

CallingPartys Category


CallReference Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identify a call. This IE provides the call reference number allocated by the GMSC/MSC for the call.

CallReference Number The Initial detection point (DP) message is considered as an example here. In this example, the call reference number is 16 02 66 09 05 82. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CallResult Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the charging information requested by the SCF in the Apply Charging message.

CallResult The Apply Charging Report message is considered as an example here. In this example, partyToCharge and timeInformation are provided. The value of partyToCharge is leg1, indicating that the current call is paid by the caller. The value of callActive is TRUE, indicating that the call is in active state. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


cancelDigit Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the cancel digit string that may be entered by the to request a retry. It is an optional IE.

cancelDigit

The Prompt And Collect Information message is considered as an example here. In this example, the value of cancelDigit is oB, indicating that the entered characters are discarded if the asterisk (*) is received. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Collected Info Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the subscriber information to be collected. Information to be collected is as follows: minimumNbOfDigits maximumNbOfDigits endOfReplyDigit cancelDigit startDigit firstDigitTimeOut interDigitTimeOut errorTreatment interruptableAnnInd voiceInformation voiceBack

Collected Info

The Prompt And Collect Information message is considered as an example here. In this example, the value of maximumNbOfDigits is 16, indicating that the maximum number of valid digits to be collected is 16. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Destination Routing Address Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the number to which the call is routed. It is a mandatory IE.

Destination Routing Address The Connect message is considered as an example here. In this example, the destination routing address is 8613466784401 (international number). Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

disconnectFromIPForbidden Description of the IE Reference Standards Description of the IE Information Element (IE)


Description Indicates whether to release the connection between the special resource and the subscriber after the announcement is complete. If the value is TRUE, it indicates that disconnecting the subscriber from the special resource is prohibited. If the value is FALSE, it indicates that disconnecting the subscriber from the special resource is permitted.

The Play Announcement message is considered as an example here. In this example, the value of disconnectFromIPForbidden is TRUE, indicating that disconnecting the subscriber from the special resource is permitted. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

endOfReplyDigit Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the digit string used to signal the end of input. It is an optional IE.

endOfReplyDigit

The Prompt And Collect Information message is considered as an example here. In this example, the value of endOfReplyDigit is 0C, indicating that the input is complete when the pound key (#) is received. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

errorTreatment Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the specific action to be taken when errors occur, that is, the processing mode of the MSC when the input of the subscriber is invalid or incorrect.

errorTreatment

The Prompt And Collect Information message is considered as an example here. In this example, the value of errorTreatment is repeatPrompt, indicating that the system prompts the subscriber to enter information again when the input is invalid. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

eventSpecificInformationBCSM Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the call information related to the specified event.

eventSpecificInformationBCSM

If the event is RouteSelectFailure, the IE eventSpecificInformationBCSM contains the failure cause (if available). If the event is O-Busy or T-Busy, the IE eventSpecificInformationBCSM contains the busy cause (if available). If the event is O-NoAnswer or TNoAnswer, the IE eventSpecificInformationBCSM is empty. If the event is O-Answer or TAnswer, the IE eventSpecificInformationBCSM is empty. If the event is O-Disconnect or TDisconnect, the IE eventSpecificInformationBCSM contains the release cause (if available). If the event type is O-NotReachable or T-NotReachable, the IE eventSpecificInformationBCSM contains the release cause (if available).

The Event Report basic call state model (BCSM) message is considered as an example here. In this example, the release cause is terminal error. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

eventTypeBCSM Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of the event to the reported.

eventTypeBCSM

The Event Report basic call state model (BCSM) message is considered as an example here. In this example, the value of eventTypeBCSM is tDisconnect, indicating the call release event. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

firstDigitTimeOut Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the duration of the first-digit timer. It is an optional IE. If this IE is not present, the MSC uses a default value for the firstdigit timer. The default value is 10 seconds and is configurable. If the subscriber does not enter any valid information before the first-digit timer expires, the MSC performs the timeout processing.

firstDigitTimeOut

The Prompt And Collect Information message is considered as an example here. In this example, the value of firstDigitTimeOut is 8, indicating that the timer expires if the first digit is not received within eight seconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078.


FreeFormatData Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the relevant charging information. This IE contains the free-format billing and/or charging characteristics. The MSC must insert the contents contained by this IE to the Customized Applications for Mobile network Enhanced Logic (CAMEL) call detail record (CDR).

FreeFormatData

The Furnish Charging Information message is considered as an example here. In this example, the content to be inserted to the CAMEL CDR is 80 01 30. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Generic Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the generic number. This generic number is used to overwrite the calling line ID presented to the callee and is filled in the calling number field in the call detail record (CDR).

Generic Number

The Connect message is considered as an example here. In this example, the generic number is 607040. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Identifies a mobile subscriber.

international mobile subscriber identity (IMSI) The Initial detection point (DP) message is considered as an example here. In this example, the IMSI is 460077552000446. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

inbandInfo Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the inband information. This IE contains the following IEs: Message ID: indicates the message(s) to be sent. Number Of Repetitions: indicates the maximum number of times the message shall be sent to the subscriber. It is an optional IE. Duration: indicates the maximum duration that the message shall be played or repeated. The value 0 indicates endless repetition. It is an optional IE. Interval: indicates the time interval between successive messages. It is an optional IE.

inbandInfo

The Play Announcement message is considered as an example here. In this example, the announcement is repeated twice, the duration is 16 seconds, and there is no interval between two successive

announcements. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

informationToSend Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the information to be sent. The values are as follows: inbandInfo: indicates the inband information tone: indicates the tone.

informationToSend

The Play Announcement message is considered as an example here. In this example, the inband information is sent. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

interDigitTimeOut Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the duration of the inter-digit timer. It is an optional IE. If this IE is not present, the MSC uses a default value for the interdigit timer. The default value is 10 seconds and is configurable. When the subscriber enters the information, if the interval between two keystrokes exceeds the duration of the inter-digit timer, the MSC performs the timeout processing.

interDigitTimeOut

The Prompt And Collect Information message is considered as an example here. In this example, the value of interDigitTimeOut is 5, indicating that the timer expires if the interval between two digits exceeds five seconds.


interruptableAnnInd Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether to interrupt the announcement after the first valid digit is received by the MSC. If the value of this IE is TRUE, the announcement is interrupted after the first valid digit is received by the MSC. If the value of this IE is FALSE, the announcement is not interrupted after the first valid digit is received by the MSC.

interruptableAnnInd

The Prompt And Collect Information message is considered as an example here.

In this example, the value of interruptableAnnInd is TRUE, indicating that the announcement is interrupted after the first valid digit is received by the MSC. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

iPRoutingAddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the routing address to set up a connection to the GSM specialized resource function (gsmSRF).

iPRoutingAddress

The Connect To Resource message is considered as an example here. In this example, the routing address is 8613907521124. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

legID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the party whose call events shall be reported to the SCF. The SCF can use only the option sendingSideID. If sendingSideID is not available, the following default values of legID are used:

legID

For the event types O-Abandon and T-Abandon, the default value of legID is 1. For the event types RouteSelectFailure, OCalledPartyBusy, O-NoAnswer, OAnswer, O-NotReachable, TCalledPartyBusy, T-NoAnswer, TAnswer, and T-NotReachable, the default value of legID is 2. For the event types O_Disconnect and T_Disconnect, the value of legID must be explicitly given.

The Request Report basic call state model (BCSM) Event message is considered as an example here. In this example, the value of legID is 2, indicating that the call events of the callee shall be reported to the SCF. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078.


locationInformation Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the location information.

locationInformation

The Initial detection point (DP) message is considered as an example here. In this example, the VLR number is 861310752051. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

LocationNumber Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the area code of the location. When the Calling Party Number does not contain any caller location information, this IE indicates the caller location. The format is Country code + Area code.

LocationNumber

The Initial detection point (DP) message is considered as an example here. In this example, the value of LocationNumber is 86755, indicating that the country code is 86 and the area code is 755. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MaxCallPeriod Duration Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the maximum call duration of the current call. In the prepaid service (PPS) service, the value of MaxCallPeriod Duration is 15 minutes. If the duration of the last segment of conversation is equal to or shorter than one minute, the duration of the last but two segment of conversation must be configured as the duration of the last segment of conversation and set to a value between 15 and 16. In this way, the subscriber can still hear the announcement in the last minute.

MaxCallPeriod Duration

The Apply Charging message is considered as an example here. In this example, the maximum call duration is 120 seconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


maximumNbOfDigits Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the maximum number of valid digits to be collected.

maximumNbOfDigits The Prompt And Collect Information message is considered as an example here. In this example, the value of maximumNbOfDigits is 16, indicating that the maximum number of valid digits to be collected is 16. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

minimumNbOfDigits Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the minimum number of valid digits to be collected.

minimumNbOfDigits The Prompt And Collect Information message is considered as an example here. In this example, the value of minimumNbOfDigits is 1, indicating that the minimum number of valid digits to be collected is 1. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Monitor Mode Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the mode in which the event is reported. The values are as follows:

Monitor Mode

interrupted: indicates that the event is reported as a request. The MSC performs the subsequent processing only after the response is received. notifyandcontinue: indicates that the event is reported as a notification. The MSC performs the subsequent processing without receiving any response from the S. transparent: indicates that the event is not reported to the SCF.

The Request Report basic call state model (BCSM) Event message is considered as an example here. In this example, the value of Monitor Mode is interrupted, indicating that the event is reported as a request. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs


MSCAddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the MSC address.

MSCAddress The Initial detection point (DP) message is considered as an example here. In this example, the MSC address is 861310752051. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Original Called Party ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the original called number. This IE is present when the call is forwarded.

Original Called Party ID

The Connect message is considered as an example here. In this example, the original called number is 8613907521124. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PartyToCharge Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the party to be charged in a call. This IE must be present in the Apply Charging Report (ACR) message sent by the MSC.

PartyToCharge The Apply Charging message is considered as an example here. In this example, the value of PartyToCharge is leg1, indicating that the call is paid by the caller. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PlayTone Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the MSC plays a warning tone or an announcement when the balance of the subscriber is insufficient. The MSC determines whether the announcement is played one minute or three minutes before the balance of the subscriber is exhausted. The IE PlayTone is present in the last Apply Charging (AC) message only when the value of the IE ReleaseIfDuration Exceeded is TRUE.

PlayTone

The Apply Charging message is considered as an example here. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Redirecting Party ID Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the redirecting number from which the route is forwarded.

Redirecting Party ID

The Connect message is considered as an example here. In this example, the redirecting number is 8613907521124. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Redirection Information Description of the IE Reference Standards Description of the IE Information Element Description (IE) Indicates the redirecting information, such as the forwarding times and forwarding reason.

Redirection Information

The Connect message is considered as an example here. In this example, the call is forwarded for once because the subscriber is busy. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

releaseIfdurationExceeded Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether the call is released after the maximum call duration is reached. In normally cases, the value of this IE is FALSE. The value of this IE is TRUE (indicating that the call is released) in the Apply Charging (AC) message only when the balance of the subscriber is sufficient only for one AC operation.

releaseIfdurationExceeded

The Apply Charging message is considered as an example here. In this example, the value of releaseIfdurationExceeded is 1, indicating the call is released after the maximum call duration is reached. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

requestAnnouncementComplete Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether to send the Special Resource Report (specialized resource report (SRR)) after the tone or announcement is complete.

requestAnnouncementComplete

The Play Announcement message is considered as an example here. In this example, the value of requestAnnouncementComplete is TRUE, indicating that the MSC sends the SRR after the tone or announcement is complete.


resourceAddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the physical address of the GSM specialized resource function (gsmSRF).

resourceAddress The Connect To Resource message is considered as an example here. In this example, the value of resourceAddress is none, indicating that the MSC has the gsmSRF function. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

sendCalculationToSIndication Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the MSC sends the Apply Charging Report (ACR) message after the maximum call duration specified in the Apply Charging (AC) message is reached. This IE is always set to TRUE.

sendCalculationToSIndication

The Apply Charging message is considered as an example here. In this example, the value of sendCalculationToSIndication is TRUE, indicating that the MSC sends the ACR message after the maximum call duration specified in the AC message is reached.


serviceInteractionIndicatorsTwo Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether to set up the connection between the caller and the GSM specialized resource function (gsmSRF).

serviceInteractionIndicatorsTwo

The Connect To Resource message is considered as an example here. In this example, the bidirectional connection is set up. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ServiceKey Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies a type of Customized Applications for Mobile network Enhanced Logic (CAMEL) service. The S enters the service flow based on the service key contained in the initial detection point (IDP) message received by the S. This IE is mandatory. The service key of the prepaid service (PPS) service is 1, and the service key of the mobile virtual private network (MVPN) service is 3.

ServiceKey

The Initial detection point (DP) message is considered as an example here. In this example, the service key is 1. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

startDigit Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the start digit string that denotes the start of the valid digits to be collected. It is an optional IE.

startDigit

The Prompt And Collect Information message is considered as an example here. In this example, the value of startDigit is 0, indicating that the start digit string is 0. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SubscriberState Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the current state of the subscriber. The states are Customized Applications for Mobile network Enhanced Logic (CAMEL) Busy, Network Determined Not Reachable, and Assumed Idle.

SubscriberState

The Initial detection point (DP) message is considered as an example here. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Tariff Switch Interval Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the tariff switch interval, that is, the time interval at which the tariff is switched.

Tariff Switch Interval

The Apply Charging message is considered as an example here. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

timeIfNoTariffSwitch Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates whether tariff switch occurs. The Apply Charging Report message contains this IE only when the tariff is switched. This IE is mutually exclusive with the IE timeIfTariffSwitch.

timeIfNoTariffSwitch

The Apply Charging Report message is considered as an example here. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

timeIfTariffSwitch Description of the IE Reference Standards Description of the IE Information Element (IE)

Description This IE is present only when tariff switch has occurred during the conversation. It indicates the conversation duration before and after the tariff is switched. This IE contains the following information:

timeIfTariffSwitch

Time SinceTariff Switch: indicates the conversation duration from the time that tariff switch occurs in the time that the apply charging report (ACR) message is sent. Tariff Switch Interval: indicates the conversation duration from the time that the Apply Charging (AC) message is sent to the time that tariff switch occurs.

The Apply Charging Report message is considered as an example here. In this example, the value of timeSinceTariffSwitch is 5, indicating the conversation duration from the time that tariff switch occurs in the time that the ACR message is sent is 500 milliseconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078.


timeZone Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the time that the Customized Applications for Mobile network Enhanced Logic (CAMEL) service is triggered and the time zone where the MSC that triggers the CAMEL service is located.

timeZone

The Initial detection point (DP) message is considered as an example here. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

tone Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the tone information. It contains the following information: ToneID: identifies a tone. Duration: indicates the duration of the tone. It is an optional IE.

tone

The Play Announcement message is considered as an example here. In this example, the tone ID is 0x100001f and the tone duration is 15 seconds. Reference Standards For details, see 5.1 "Data types" in 3rd Generation Partnership Project (3GPP) 29.078. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ISUP Protocol Description of the ISUP Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the ISUP Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description Integrated Services Digital Network Part (ISUP) is the part of the signaling system No. 7 (SS7). It provides the signaling function for the basic bearer services and supplementary services for voice and non-voice purposes on the Integrated Services Digital Network (ISDN). The MSC communicates with other MSCs or the Public Switched Telephone Network (PSTN) through the ISUP protocol. Figure 1 shows the application of the protocol. Figure 1 Application of the ISUP protocol

Protocol Stack The MSOFTX3000 the following types of transmission of the ISUP protocol: MTP3-based transmission: Messages are transmitted through the services provided by the Message Transfer Part (MTP). Figure 2 shows the protocol stack. IP-based transmission: Messages are transmitted through the services provided by Signaling Transport (SIGTRAN). Figure 2 ISUP protocol stack (MTP3-based)

Figure 3 ISUP protocol stack (M3UA based)

Message Structure Figure 4 shows the structure of an ISUP message. Figure 4 ISUP message structure

The ISUP parameters can be classified into three types based on the message structure shown in Figure 4. Parameter Type

Description

The position and length of this type of parameter in messages are invariable; therefore, parameter name and length indicator Mandatory fixed parameter are not required. For example, transmission medium requirement in the IAM message is a mandatory fixed

parameter.

Mandatory variable parameter

The position of this type of parameter in messages is relatively fixed; therefore, parameter name is not required. The length of this type of parameter, however, is variable; therefore, the length indicator is required. For example, called party number in the IAM message is a mandatory variable parameter.

Optional parameter

This type of parameter may or may not be included in a message; therefore, parameter name and length indicator are required. For example, calling party number is an optional parameter.

Message List Message

Function

Initial address message (IAM)

This message is sent in the forward direction to initiate seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call.

Application transport message (APM)

This message is sent in either direction to convey application information using the Application Transport mechanism.

This message is sent in the backward direction indicating that Address complete message all the address signals required for routing the call to the called (ACM) party have been received. Answer message (ANM)

This message is sent in the backward direction indicating that the call has been answered.

Information request message (INR)

This message is sent by an exchange to request information in association with a call.

Information message (INF)

This message is sent to convey information in association with a call.

Call progress message (G)

This message is sent in either direction during the setup or active phase of the call, indicating that a significant event has occurred.

Connect message (CON)

This message is sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received and that the call has been answered.

Subsequent address message (SAM)

This message is sent in the forward direction following an IAM, to convey additional called party number information. This message is sent in either direction to indicate that the

Release message (REL)

circuit is being released due to the provided reason.

Release complete message This message is sent in either direction in response to a REL (RLC) or a reset circuit message. Suspend message (SUS)

This message is sent in either direction indicating that the calling or called party has been temporarily disconnected.

Resume message (RES)

This message is sent in either direction indicating that the calling or called party, after having been suspended, is reconnected.

Parent topic: ISUP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 describes the IEs carried in the common part of messages. Table 1 IEs carried in the common part of messages Information Element (IE)

Description Indicates the information provided to the message transfer part for the purpose of message routing.

Routing label

Destination point code: Indicates the signaling point code (SPC) of the network element (NE) to which the message is routed. If the message is sent to the local office, the destination point code is the same as the originating point code. Originating point code: Indicates the SPC of the NE that sends the message. Signalling link selection: Indicates the way in which a link is selected for sending the ISDN part (ISUP) message. Signalling link selection is carried in the message sent by the ISUP layer to the Message Transfer Part Layer 3 (MTP3) or MTP3- Adaptation Layer (M3UA) layer. The MTP3 or M3UA layer selects a link, based on Signalling link selection, to send the ISUP message. Circuit identification code: Uniquely identifies an interoffice circuit when the originating point code is the same as the destination point code and the network indicator of the originating signaling point is the same as the network indicator of the destination signaling point. According to the International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) recommendations, the circuit identification code (CIC) is of 12 bits. The CIC is of 14 bits according to the American National Standard Institute (ANSI) ISUP protocol released in 1995 and of 16 bits according to the ANSI ISUP protocol released in 2005. On the MSOFTX3000 the length of the CIC can be configured by

using the ADD OFC and MOD OFC commands. The IAM is considered as an example here. In this example, the destination point code is 2A1004, originating point code is 2A1003, signalling link selection is 0, and circuit identification code is 1. Parent topic: ISUP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages IAM APM ACM ANM INR INF G CON SAM REL RLC SUS RES Parent topic: ISUP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IAM Message Function Associated IEs Reference Standards Message Function This message is sent in the forward direction to initiate seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call. Figure 1 shows the main IEs of the message.

Figure 1 IAM Associated IEs Message

Function

Provides the information about the transmission path used Nature of connection indicators on a connection. For details, see Nature of Connection Indicators.

Forward call indicators

Provides the information about the characteristics of the connection, signaling path, and calling party sent in the forward direction. For details, see Forward Call Indicators.

Calling party's category

Indicates the category of the calling party. For details, see Calling Party's Category.

Transmission medium requirement

Indicates the type of transmission medium required for the connection. For details, see Transmission Medium Requirement.

Called party number

Indicates the number of the called party. For details, see Called Party Number.

Calling party number

Indicates the number of the calling party. For details, see Calling Party Number

Propagation delay counter

Indicates the propagation delay of a connection. For details, see Propagation Delay Counter.

Optional forward call indicators

Provides the information about the characteristics of the connection, signaling path, and called party sent in the forward direction. For details, see Optional Forward Call Indicators.

Reference Standards For details, see 2.28 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and Table 32/Q.763 in ITU-T Q-763. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

APM Message Function Reference Standards Message Function This message is sent in either direction to convey application information using the Application Transport mechanism. The MSOFTX3000 can either discard this message or transfers this message without interpreting it. Reference Standards For details, see the description related to "Application transport" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and Q763. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ACM Message Function Associated IEs Reference Standards Message Function This message is sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received. Figure 1 shows the main IEs of the message.

Figure 1 ACM Associated IEs Information Element (IE)

Description

Backward call indicators

Provides the information about the characteristics of the connection, signaling path, and called party sent in the backward direction. For details, see Backward Call Indicators.


ANM Message Function Associated IEs Reference Standards Message Function This message is sent in the backward direction indicating that the call has been answered. Figure 1 shows the main IEs of the message. The answer message (ANM) may carry no Information Element (IE).

Figure 1 ANM Associated IEs IE

Description




INR Message Function Associated IEs Reference Standards Message Function This message is sent by an exchange to request information in association with a call. Generally, the information request (INR) message is sent to request the calling number or category of the calling party. Figure 1 shows the main IEs of the message. Figure 1 INR message

Associated IEs Information Element (IE) Description Information request indicators

Identifies the optional parameters requested in a message. For details, see Information Request Indicators.


INF Message Function Associated IEs Reference Standards Message Function This message is sent to convey information in association with a call, which may have been requested in an information request (INR) message. Generally, this message conveys the calling number or category of the calling party. Figure 1 shows the main IEs of the message.

Figure 1 INF message Associated IEs Information Element (IE)

Description

Information indicators

Identifies the optional parameters included in a message. For details, see Information Indicators.


G Message Function Associated IEs Reference Standards Message Function This message is sent in either direction during the setup or active phase of the call, indicating that a significant event has occurred. Figure 1 shows the main IEs of the message.

Figure 1 G message Associated IEs Information Element (IE)

Description

Event information

Indicates the type of event which causes a call progress (G) message to be sent. For details, see Event Information.

Generic notification indicator

Indicates a generic notification. For details, see Generic Notification Indicator.


CON Message Function Associated IEs Reference Standards Message Function This message is sent in the backward direction indicating that all the address signals required for routing the call to the called party have been received and that the call has been answered. The connect (CON) message can be regarded as the address complete message (ACM) message + the answer message (ANM) message. Figure 1 shows the main IEs of the message.

Figure 1 CON message Associated IEs Information Element (IE)

Description




SAM Message Function Associated IEs Reference Standards Message Function This message is sent in the forward direction following an IAM, to convey additional called party number information. Figure 1 shows the main IEs of the message.

Figure 1 SAM Associated IEs Information Element (IE) Description

Subsequent number

Indicates the additional called party address digits sent subsequent to the sending of the called party number parameter. For details, see Subsequent Number.


REL Message Function Associated IEs Reference Standards Message Function This message is sent in either direction to indicate that the circuit is being released due to the provided reason and is ready to be put into the idle state on receipt of the Radio Link Control (RLC) message. Figure 1 shows the main IEs of the message.

Figure 1 REL message Associated IEs Information Element (IE) Description Cause indicators

Indicates the reason for sending the message. For details, see Cause Indicators.


RLC Message Function Associated IEs Reference Standards Message Function This message is sent in either direction in response to a release (REL) message or an reset circuit signal (RSC) message. When this message is sent, the related circuit has changed to the idle condition. Figure 1 shows the main IEs of the message. The Release Confirm (RLC) message may carry no Information Element (IE).

Figure 1 RLC message Associated IEs IE

Description

Cause indicators

Indicates the reason for sending the message. For details, see Cause Indicators.


SUS Message Function Reference Standards Message Function This message is sent in either direction indicating that the calling or called party has been temporarily disconnected. Figure 1 shows the main IEs of the message.

Figure 1 SUS message Reference Standards For details, see 2.40 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and Table 38/Q.763 in ITU-T Q-763. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RES Message Function Reference Standards Message Function This message is sent in either direction indicating that the calling or called party, after having been suspended, is reconnected. Figure 1 shows the main IEs of the message.

Figure 1 RES message Reference Standards For details, see 2.37 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and Table 38/Q.763 in ITU-T Q-763. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Called Party Number Propagation Delay Counter Transmission Medium Requirement Subsequent Number Backward Call Indicators Nature of Connection Indicators Forward Call Indicators Optional Forward Call Indicators Event Information Generic Notification Indicator Information Indicators Information Request Indicators Cause Indicators Calling Party Number Calling Party's Category Parent topic: ISUP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Called Party Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the called party. The message is routed and the called party is located based on this IE. Generally, this IE is contained in the IAM as a mandatory variable parameter.

Called party number

Nature of address indicator: Indicates the nature of a number, for example, integrated services digital network (ISDN) international number, ISDN national significant number, or ISDN subscriber number. Odd/even indicator: Indicates whether the number is even or odd. F, the character indicating the end of a number, is also treated as a digit of the called number. Address signal: Indicates the called number in binary-coded data (BCD) format. Every four bits represent a digit, and F indicates the end of a number. The IAM is considered as an example here. In this message, 4778613807557733F refers to the called number. This message indicates that the called number is a national number and is odd.

Reference Standards

For details, see 3.14 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.9 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Propagation Delay Counter Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the propagation delay of a connection. This IE is sent in the forward direction and carried in the IAM. It is accumulated when the IE is transferred through the network. The propagation delay information is represented by a counter counting in integer multiples of 1 ms.

Propagation delay counter Propagation delay value: Indicates the propagation delay in ms. The IAM is considered as an example here. In this example, Propagation delay value is 5, which indicates that the propagation delay is 5 ms. Reference Standards For details, see 3.58 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.42 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Transmission Medium Requirement Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of transmission medium required for the connection. It is sent in the forward direction and carried in the IAM as a mandatory parameter.

Transmission medium requirement

Transmission medium requirement: Indicates the type of transmission medium required for the connection. It can be speech, 3.1 kHz audio, or 64 kbit/s unrestricted. The IAM is considered as an example here. In this example, Transmission medium requirement is speech, which indicates that voice calls need to be ed.

Reference Standards For details, see 3.73 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.54 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Subsequent Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Subsequent number

Description Indicates the additional called party address digits sent subsequent to the sending of the called party number parameter. For example, in the case of overlap sending, the IAM does not carry the complete called number. The remaining digits of the called number are sent through the Subsequent number IE in several SAMs.


Backward Call Indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the characteristics of the connection, signaling path, and called party sent in the backward direction. This IE is mandatory for the address complete message (ACM) and connect (CON) message and optional for the answer message (ANM).


Charge indicator: Indicates whether the called party is charged for the call. On receiving a message carrying Backward call indicators, the MSOFTX3000 queries the data configuration and then determines whether the called party is charged. For details, see Charge Indicator in the online help of ADD CNACLD command. Called party's status indicator: Indicates the status of the called party. Echo control device indicator: Indicates whether an echo control device is enabled in the connection. The IAM is considered as an example here. In this example, Charge indicator is 2, which indicates that the called party is charged for the call; Called party's status indicator is 1, which indicates that the called party is free; Echo control device indicator is 1, which indicates that the echo control device is enabled.


Nature of Connection Indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the transmission path used on a connection. It is sent in the forward direction and carried in the IAM as a mandatory parameter.

Nature of connection indicators

Satellite indicator: Indicates whether the satellite is involved in the transmission. If the satellite is involved in the transmission, the propagation delay is comparatively long. Continuity check indicator: Indicates whether to perform a continuity check on the concerned circuit(s) and whether a continuity check is performed on a previous circuit in the connection. Echo control device indicator: Indicates whether an echo control device is enabled in the connection. The IAM is considered as an example here. In this example, Satellite indicator is 0, which indicates that satellite is not involved in the transmission; Continuity check indicator is 0, which indicates that continuity check need not be performed on the concerned circuit; Echo control device indicator is 1, which indicates that the echo control device is enabled.

Reference Standards For details, see 3.50 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.35 in ITU-T Q-763. Parent topic: Description of Associated IEs


Forward Call Indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the characteristics of the connection, signaling path, and calling party sent in the forward direction. This IE is sent in the forward direction and carried in the IAM.

Forward call indicators

National International Call Indicator: Indicates in the destination national network whether the call is treated as an international call or as a national call. End to End Method Indicator: Indicates the available methods for end-to-end transfer of information. Interwork Indicator: Provides the information about interworking. Isdn Part Indicator: Indicates that the integrated services digital network (ISDN) part is used in all preceding parts of the network connection. The IAM is considered as an example here. In this example, National International Call Indicator is 0, which indicates that the call is treated as a national call; End to End Method Indicator is 0, which indicates that the method for end-to-end transfer is unavailable and only the methods for link-to-link transfer are available; Interwork Indicator is 0, which indicates that Signaling System No. 7 (SS7) signaling is used in all preceding parts of the network connection and interworking is not involved; Isdn Part Indicator is 1, which indicates that

the ISDN part is used in all preceding parts of the network connection. Reference Standards For details, see 3.35 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.23 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Optional Forward Call Indicators Description of the IE Reference Standards Description of the IE Information Element (IE) Description Indicates the characteristics of the connection, signaling path, and called party sent in the forward direction This IE is sent in the forward direction and carried in the IAM.

Optional forward call indicators

Closed group call indicator: Indicates whether the concerned call can be set up as a closed group call and, if a closed group call, whether outgoing access is allowed. Simple segmentation indicator: Indicates whether additional information will be forwarded in an segment message (SGM). If an IAM is too long, an IAM carrying Simple segmentation indicator is sent, and then an SGM is sent. Connected line identity request indicator: Indicates whether the connected party number is requested. The IAM is considered as an example. In this example, Closed group call indicator is 3, which indicates that the outgoing calls are not allowed; Simple segmentation indicator is 0, which indicates that an SGM will not be sent; Connected line identity request indicator is 0, which indicates that the connected party number is not requested.



Event Information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of event which causes the sending of a call progress (G) message. This IE mandatory for the G message.

Event information

Event indicator: Indicates the type of event which causes a G message to be sent. A G message is sent when the called party is altered, inband announcement is played, or call forwarding occurs. In this example, Event indicator-ITUT is 2, which indicates that the call is being processed.


Generic Notification Indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provide supplementary service notification to a . It can be sent in either direction.

Generic notification indicator

Notification indicator: Indicates the supplementary service, such as call forwarding service and multiparty service. The IAM is considered as an example. In this example, Notification indicator is 105, which indicates the notification of the call forwarding service.


Information Indicators Description of the IE Reference Standards Description of the IE Information Element (IE) Description Identifies the optional parameters included in a message. It is carried in the information (INF) message.

Information indicators

Calling party address response indicator: Indicates whether the provided information contains the calling number. Calling party's category response indicator: Indicates whether the provided information contains the category of the calling party. Charge information response indicator: Indicates whether the provided information contains the charge information. The INF message is considered as an example here. In this example, Calling party address response indicator is 3, which indicates the calling number is provided; Calling party's category response indicator is 1, which indicates that the category of the calling party is provided; and Charge information response indicator is 0, which indicates that the charge information is not provided.



Information Request Indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the information requested for a call. It is carried in the information request (INR) message.

Calling party address request indicator: Indicates whether the calling number is required. Calling party's category request indicator: Indicates whether the category of the calling party is required. Charge information request indicator: Indicates whether the charge information is required.

Information request indicators

The INR message is considered as an example here. In this example, Calling party address request indicator is 1, which indicates the calling number is required; Calling party's category request indicator is 1, which indicates that the category of the calling party is required; and Charge information request indicator is 0, which indicates that the charge information is not required. Reference Standards For details, see 3.43 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.29 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Cause Indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason for sending the message (for example, release (REL) message). This IE is sent in either direction. Generally, it is carried in the REL, address complete message (ACM), and call progress (G) message.

Cause indicators Location: Indicates whether the event is caused by the network or subscriber. Cause value: Indicates the reason for sending the message. The REL message is considered as an example. In this example, Location is 1, which indicates that the local subscriber terminates the call; Cause value is 16, which indicates that the call is released normally. Reference Standards For details, see 3.17 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762, 3.12 in ITU-T Q-763, and ITU-T Q-850. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling Party Number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the calling party. Generally, this IE is carried in the IAM. It is optional.


Nature of address indicator: Indicates the nature of a number, for example, integrated services digital network (ISDN) subscriber number, unknown number, ISDN international number, or ISDN national significant number. Odd/even indicator: Indicates whether the number is even or odd. Address signal: Indicates the calling number in binary-coded data (BCD) format. Every four bits represent a digit. Address presentation restricted indicator: Indicates whether the calling number is presented to the called party. This IE is used in services such as the calling line identification presentation (CLIP) and calling line identification restriction (CLIR). Number Incomplete indicator: Indicates whether the delivered number is complete. The IAM is considered as an example. In this example, Nature of address indicator is international-number(4), which indicates an international number; Odd/even indicator is 1, which indicates that the number is odd; Address signal is

8613807557722, which indicates the calling number; Address presentation restricted indicator is presentation allowed(0), which indicates that the calling number is presented to the called party. Reference Standards For details, see 3.15 in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q-762 and 3.10 in ITU-T Q-763. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling Party's Category Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the category of the calling party. This IE is sent in the forward direction.

Calling party's category

Calling party's category: Indicates the category of the calling party. The IAM is considered as an example here. In this example, Calling party's category is ordinary-calling-subscriber(10), which indicates that the calling party is an ordinary subscriber.


BICC Protocol Description of the BICC Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the BICC Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The Bearer Independent Call Control (BICC) protocol is used by the Nc interface in the 3rd Generation Partnership Project (3GPP) R4 CS domain to provide for call connection between MSC servers. Completion of the BICC protocol is a historic step as it separates call control from bearer control, making it possible for call control signaling to traverse various transport networks, including asynchronous transfer mode (ATM), IP, and Message Transfer Part (MTP) Signaling System No. 7 (SS7) networks. Figure 1 shows the application of the BICC protocol.

Figure 1 Application of the BICC protocol Protocol Stack Theoretically, BICC can run on any underlying transport protocols. In real network environment, Message Transfer Part Layer 3 (MTP3), MTP3- Adaptation Layer (M3UA), message transfer part layer 3 broadband (MTP3b), and Stream Control Transmission Protocol (SCTP) are often selected to carry BICC messages as they are technologically mature. Figure 2 shows the BICC protocol stack. Figure 2 BICC protocol stack

Message Structure Figure 3 shows the structure of a BICC message. Figure 3 BICC message structure

Message List Message Direction

Type

Function

Initial Address MSC<->MSC BICC Message (IAM)

This message is sent in the forward direction to initialize seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call.

Application Transport MSC<->MSC BICC Message (APM)

This message is sent in either direction to convey application information using the Application Transport mechanism.

Address Complete MSC<->MSC BICC Message (ACM)

This message is sent in the backward direction to indicate that the address signals required for routing the call to the called party have been received.

Answer Message MSC<->MSC BICC (ANM)

This message is sent in the backward direction to indicate that the call has been answered.

Parent topic: BICC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Identifies the office direction that sends the message.

Office number An IAM message is considered as an example. In this example, officenumber is 0, indicating that the message is sent in office direction 0. Indicates the type of bearers that carry Bearer Independent Call Control (BICC) messages. Signal type An IAM message is considered as an example. In this example, signal-type is bicc-over-m3ua, indicating that BICC messages are transported on MTP3- Adaptation Layer (M3UA) links.

Bicc protocol type

Indicates the type of BICC protocol. This IE is encoded as 0 to indicate International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) BICC, and as 1 to indicate American National Standard Institute (ANSI) BICC.

An IAM message is considered as an example. In this example, bicrotocol-type is itut-protocol, indicating that ITU-T BICC is applied. Provides information about bearers that carry BICC messages. If BICC runs on Stream Control Transmission Protocol (SCTP), this IE contains the sctp-information field to convey SCTP link information. If BICC runs on M3UA or Message Transfer Part Layer 3 (MTP3), this IE contains the mtp-information field to convey Message Transfer Part (MTP) link information. The mtp-information field consists of the following subfields: net-indicator: identifies the signaling network across which BICC messages are transported. originating-point-code-24-bit: provides the 24-bit originating signaling point code (OPC) of the network entity that sends a

Signal information

BICC message. destination-point-code-24-bit: provides the 24-bit destination signaling point code (DPC) of the network entity that receives a BICC message. The sctp-information field consists of the following subfields: start-link-number end-link-number sis-data: indicates the signaling link selection code (SLS).

In the example figure, net-indicator is 2 indicating that the local MSC is served by a national signaling network and is assigned SPCs, OPC is 74a006, and DPC is 74a019. Identifies signaling relation between peer BICC entities. Call Instance Code An IAM message is considered as an example. In this example, callinstance-code is 0xf. Parent topic: BICC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages IAM APM ACM ANM Parent topic: BICC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IAM Message Function Associated IEs Reference Standards Message Function This message is sent in the forward direction to initialize seizure of an outgoing circuit and to transmit number and other information relating to the routing and handling of a call. Figure 1 shows the main IEs of the message.

Figure 1 IAM message Associated IEs Information Element (IE)

Description

nature of connection indicators

Provides information relating to the transmission path used on a connection. The information includes whether a satellite circuit is used in the connection and whether an echo control device is present. For details, see nature of connection indicators.

forward call indicators

Provides information relating to the characteristics of the connection, signaling path, and calling party sent in the forward direction. For details, see forward call indicators.

calling party's category

Provides information sent in the forward direction to indicate the category of the calling party, and in case of semi-automatic calls, the service language to be spoken by the incoming, delay, and assistance operators. For details, see calling party's category.

transmission medium requirement

Provides information sent in the forward direction to indicate the type of transmission medium required for the connection (for example, 64 kbit/s unrestricted and speech). For details, see transmission medium requirement.

called party number

Identifies the called party. For details, see called party number.

propagation delay counter

Provides information sent in the forward direction to indicate the propagation delay of a connection. The propagation delay information is accumulated whilst the IE is transferred across the network. The propagation delay information is represented by a counter counting in integer multiples of 1 millisecond. For details, see propagation delay counter.

calling party number

Provides called party address sent in the forward direction. For details, see calling party number.

location number

Identifies the geographical area of the origin of a call. This IE is primarily intended to provide services for mobile originated calls. For details, see location number.

service information

Provides information sent in the forward direction to indicate the bearer capability required by the calling party. For details, see service information.

call reference

Identifies a particular call. For details, see call reference.

optional forward call indicators

Provides information relating to the characteristics of the connection, signaling path, and called party sent in the forward direction. For details, see optional forward call indicators.

application transport parameter

Provides information sent in either direction to allow the peer-to-peer communication of Application Transport mechanism applications. For details, see application transport parameter.

Reference Standards For details, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.2 and Q.1902.3. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

APM Message Function Associated IEs Reference Standards Message Function This message is sent in either direction to convey application information using the Application Transport mechanism. Figure 1 shows the main IEs of the message.

Figure 1 APM message Associated IEs Information Element (IE)

Description Provides information sent in either direction to allow the peer-to-peer communication of


Application Transport mechanism applications. For details, see application transport parameter.

Reference Standards For details, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.2 and Q.1902.3. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ACM Message Function Associated IEs Reference Standards Message Function This message is sent in the backward direction to indicate that the address signals required for routing the call to the called party have been received. Figure 1 shows the main IEs of the message.

Figure 1 ACM message Associated IEs Information Element (IE)

Description

backward call indicators

Provides information relating to the characteristics of the connection, signaling path, and called party sent in the backward direction. For details, see backward call indicators.

cause indicators

Provides information sent in either direction to indicate the reason for sending the message. For details, see cause indicators.

Reference Standards For details, see International Telecommunication Union-Telecommunication Standardization

Sector (ITU-T) Q.1902.2 and Q.1902.3. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ANM Message Function Associated IEs Reference Standards Message Function This message is sent in the backward direction to indicate that the call has been answered. In semi-automatic working, this message has a supervisory function. In automatic working, this message is used in conjunction with charging information in order to: start metering the charge to the calling party (see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Rec.Q.28) start measurement of call duration for international ing purposes (see ITUT Rec.E.260) Figure 1 shows the main IEs of the message.

Figure 1 ANM message Associated IEs Information Element (IE)

Description


Provides information relating to the characteristics of the connection, signaling path, and called party sent in the backward direction. For details, see backward call indicators.

Reference Standards For details, see ITU-T Q.1902.2. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs called party number propagation delay counter transmission medium requirement location number backward call indicators nature of connection indicators forward call indicators optional forward call indicators service information call reference application transport parameter cause indicators calling party number calling party's category Parent topic: BICC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

called party number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the called party. This IE is primarily used to determine a route towards the called party. It is mandatory in an IAM message and consists of the following fields:

called party number

nature of address indicator: indicates the nature of called number, for example, international number, national number, subscriber number, or unknown number. odd/even indicator: indicates whether the number of address signals contained in the called number is even or odd. address signal: Address signals are represented by binary-coded data (BCD) numbers and sent in successive 4-bit fields. The character F indicates the end of address signal. numbering plan indicator: indicates the numbering plan used for the called number. internal network number indicator: indicates whether routing to an internal network number is allowed.

An IAM message is considered as an example here. In this example, nature of address indicator is national-number indicating that the called number is a national number, odd even flag is even(0) indicating that the called number consists of an even number of address signals, numbering plan

indicator is numbering-plan-according-to-e164 (1) indicating that the called number is E.164 coded, internal network number indicator is routing-to-internal-network-number-allowed (0). Reference Standards For details, see 6.17 "Called party number" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

propagation delay counter Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Expresses in pure binary representation the propagation delay value of a call in milliseconds to be accumulated during call setup. This IE is sent in the forward direction and optional in an IAM message.

propagation delay counter An IAM message is considered as an example here. In this example, propagation delay value is 0, indicating that the accumulated propagation delay is 0 milliseconds during call setup. Reference Standards For details, see 6.78 "Propagation delay counter" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

transmission medium requirement Description of the IE Reference Standards Description of the IE Information Element (IE)

transmission medium requirement

Description Indicates the type of transmission medium required for the connection, for example, speech, 3.1 kHz audio, or 64 kbit/s unrestricted. This IE is sent in the forward direction and mandatory in an IAM message. An IAM message is considered as an example. In this example, transmission medium requirement is speech (0), indicating that speech transmission medium is required.

Reference Standards For details, see 6.97 "Transmission medium requirement" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

location number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the geographical area of the origin of a call. This IE is primarily intended to provide services for mobile originated calls. It consists of the following fields:

location number

nature of address indicator: indicates the nature of location number, for example, international number, national number, subscriber number, or unknown number. odd/even indicator: indicates whether the number of address signals contained in location number is even or odd. screening indicator: indicates whether the location number is provided by the or network. address signal: Address signals are represented by binary-coded data (BCD) numbers and sent in successive 4-bit fields. address presentation restricted indicator: indicates whether the caller location number should be hidden from the called party. This field is included when calling line identification presentation (CLIP) or calling line identification restriction (CLIR) service is required. numbering plan indicator: indicates the numbering plan used for location number. internal network number indicator: indicates whether routing to an internal network number is allowed.

An IAM message is considered as an example here. In this example, nature of address indicator is international-number indicating that location number is an international number, odd even flag is even(0) indicating that location number consists of an even number of address signals, screening indicator is 3 indicating that location number is networkprovided, address presentation restricted indicator is 01 indicating that number presentation is not allowed, numbering plan indicator is isdn-numbering-plan indicating that location number is coded in compliance with the integrated services digital network (ISDN) numbering plan, internal network number indicator is routing-to-internalnetwork-number-allowed (0). Reference Standards For details, see 6.55 "Location number" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

backward call indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information relating to the characteristics of the connection, signaling path, and called party sent in the backward direction. This IE consists of the following fields:


charge indicator: indicates whether the call is chargeable. called party's status indicator: indicates the status of called party. called party's category indicator: indicates the category of called party. end-to-end method indicator: indicates available methods, if any, for end-to-end transfer of information. interworking indicator: indicates whether interworking is encountered. If Signaling System No. 7 (SS7) or Bearer Independent Call Control (BICC) is used in all parts of the network connection, it implies that no interworking is encountered. end-to-end information indicator: indicates whether the sending exchange has further call information available for end-to-end transmission. BICC indicator: indicates whether BICC is used all the way. holding indicator: indicates whether call hold is requested. integrated services digital network (ISDN) part/BICC preference indicator: indicates whether BICC is preferred. ISDN access indicator: indicates whether the access signaling protocol is ISDN. Signaling Connection Control Part (SC) method

indicator: indicates available SC method.

An address complete message (ACM) message is considered as an example here. In this example, charge indicator is charge, called party's status indicator is subscriber-free, called party's category indicator is ordinary-subscriber, end-to-end method indicator is no-endto-end-method-available, BICC indicator is used-all-the-way (BICC is used all the way), and holding indicator is holdingnot-requested. Reference Standards For details, see 6.6 "Backward call indicators" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

nature of connection indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information relating to the transmission path used on a connection. This IE is sent in the forward direction and mandatory in an IAM message. It consists of the following fields:

nature of connection indicators

satellite indicator: indicates the number of satellite circuits in the connection. The maximum value is 2. continuity indicator: indicates whether a continuity message is to be expected. This field is encoded as 00 to indicate that continuity check is not required, and as 10 to indicate otherwise. echo control device indicator: indicates whether an outgoing echo control device is present.

An IAM message is considered as an example here. In this example, satellite indicator is 0 indicating that no satellite circuit is used in the connection, continuity indicator is nocot-to-be-expected indicating that no continuity message is to be expected, and echo control device indicator is outgoing-echo-control-device-included. Reference Standards For details, see 6.61 "Nature of connection indicators" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


forward call indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information relating to the characteristics of the connection, signaling path, and calling party. This IE is sent in the forward direction and mandatory in an IAM message. It consists of the following fields:

forward call indicators

national/international call indicator: indicates whether the call has to be treated as an international call or a national call. end-to-end method indicator: indicates available methods, if any, for end-to-end transfer of information. interworking indicator: indicates whether interworking is encountered. If Signaling System No. 7 (SS7) or Bearer Independent Call Control (BICC) is used in all parts of the network connection, it implies that no interworking is encountered. end-to-end information indicator: indicates whether the sending exchange has further call information available for end-to-end transmission. BICC indicator: indicates whether BICC is used all the way. integrated services digital network (ISDN) part/BICC preference indicator: indicates whether BICC is preferred. ISDN access indicator: indicates whether the access signaling protocol is ISDN. Signaling Connection Control Part (SC) method indicator: indicates available SC method.

An IAM message is considered as an example here. In this example, national/international call indicator is call-to-betreated-as-a-national-call, end-to-end method indicator is no-end-to-end-method-available, interworking indicator is no-interworking-encountered (BICC is used all the way), BICC indicator is BICC-used-all-the-way, ISDN access indicator is originating-access-ISDN, and SC method indicator is no-indication. Reference Standards For details, see 6.43 "Forward call indicators" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

optional forward call indicators Description of the IE Reference Standards Description of the IE Information Element (IE) Description Provides information relating to the characteristics of the connection, signaling path, and called party. This IE is sent in an IAM message in the forward direction. It consists of the following fields: closed group call indicator: indicates whether the concerned call can be set up as a closed group call and, if a closed group call, whether outgoing access is allowed. 00: non-CUG call 01: spare 10: closed group (CUG) call, outgoing access allowed 11: CUG call, outgoing access not allowed optional forward call indicators

simple segmentation indicator: indicates that additional information will be forwarded in a segmentation message (SGM). SGM messages are used when an IAM message is too long and cannot contain all the information. connected line identity request indicator: indicates whether connected number identity is requested.

An IAM message is considered as an example here. In this example, closed group call indicator is non-CUG-call, simple segmentation indicator is no-additional-information-willbe-sent, and connected line identity request indicator is notrequested. Reference Standards

For details, see 6.67 "Optional forward call indicators" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

service information Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the bearer capability required by the calling party. This IE is sent in the forward direction and optional in an IAM message. It consists of the following fields: information transfer capability coding standard information transfer rate transfer mode

service information

An IAM message is considered as an example here. In this example, information transfer capability is speech, information transfer rate is 64 kbit/s, and transfer mode is circuit-mode. Reference Standards For details, see 6.102 " service information" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

call reference Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies a particular call. This IE is relevant to Bearer Independent Call Control (BICC) only in Message Transfer Part Layer 3 (MTP3) and message transfer part layer 3 broadband (MTP3b) based signaling networks. It consists of the following fields:

call reference

call identity: expresses in pure binary representation the identification number allocated to the call identity. signaling point code: indicates the code of the signaling point to which the call identity is relevant.

An IAM message is considered as an example. In this example, call identity is 0x20116, signaling point code is hexadecimal H'74a006 (7643142, 116-160-6) (decimal 7643142 or binary 116-160-6). Reference Standards For details, see 6.12 "Call reference" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

application transport parameter Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information sent in either direction to allow the peer-to-peer communication of Application Transport mechanism applications. application context identifier: identifies the application using the Application Transport mechanism. application transport instruction indicators: indicates how a node should react in case that the indicated application using the Application Transport mechanism is not ed. Release call indicator Send notification indicator APM segmentation indicator: indicates whether the received APM message is the final segment. sequence indicator: indicates whether this is the beginning of APM segmentation procedure. encapsulated application information: provides application information required to be transported by the Application Transport mechanism. Each information unit in this field is coded in the same manner, with four octets in total. It is suggested that this field be structured such that the first octet is an identifier, followed by length indicator and compatibility information. The following are typical identifiers: Action Indicator Codec List (codecs are listed in descending order of priority) Single Codec Bearer Network Connection Characteristics


Bearer Control Information Bearer Control Tunnelling Bearer Control Unit Identifier Signal Bearer Redirection Capability Bearer Redirection Indicators Signal Type Duration

An IAM message is considered as an example. In this example, application context identifier is bat-ase, release call indicator is release-call, send notification indicator is do-

not-send-notification, APM segmentation indicator is finalsegment, sequence indicator is new-sequence, and encapsulated application information conveys bearer information such as codec list and tunneling information. Reference Standards For details, see 6.61 "Application transport parameter" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.1902.3 and ITU-T Q.765.58.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

cause indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information sent in either direction to indicate the reason for sending the message. This IE consists of the following fields: location coding standard cause value

cause indicators

An release (REL) message is considered as an example here. In this example, cause value is normal-unspecified, indicating that the call release does not result from errors. Reference Standards For details, see 6.23 "Cause indicators" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3 and ITU-T Q.850. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

calling party number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the calling party. This IE is optional in an IAM message. It consists of the following fields:

calling party number

nature of address indicator: indicates the nature of calling number, for example, international number, national number, subscriber number, or unknown number. odd/even indicator: indicates whether the number of address signals contained in the calling number is even or odd. screening indicator: indicates whether the calling number is provided by the or network. address signal: Address signals are represented by binary-coded data (BCD) numbers and sent in successive 4-bit fields. address presentation restricted indicator: indicates whether the calling number should be hidden from the called party. This field is included when calling line identification presentation (CLIP) or calling line identification restriction (CLIR) service is required. numbering plan indicator: indicates the numbering plan used for the calling number. number incomplete indicator: indicates whether the delivered calling number is complete or incomplete.

An IAM message is considered as an example here. In this example, nature of address indicator is internationalnumber, odd even flag is odd, caller address signal is 8613802900318, numbering plan indicator is isdnnumbering-plan (calling number is coded in compliance with the integrated services digital network (ISDN) numbering plan), and number incomplete indicator is number-complete. Reference Standards For details, see 6.20 "Calling party number" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

calling party's category Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information sent in the forward direction to indicate the category of the calling party, and in case of semiautomatic calls, the service language to be spoken by the incoming, delay, and assistance operators.

calling party's category An IAM message is considered as an example here. In this example, calling party's category is ordinary-callingsubscriber, indicating that the calling party is an ordinary service subscriber. Reference Standards For details, see 6.21 "Calling party's category" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.1902.3. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SIP Protocol Description of the SIP Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the SIP Protocol Scenario Description Protocol Stack Message Structure Message List Description of the SIP-I Protocol Protocols with which the SIP complies Scenario Description Session Initiation Protocol (SIP) can be used for interworking between MSC servers (over the Nc interface), interworking between the MSC server and the IP multimedia subsystem (IMS), and interworking between the MSC server and the next generation network (NGN). Figure 1 shows the application of the protocol.

Figure 1 Application of the SIP protocol The SIP protocol is a session control protocol on the application layer. It is used for creation, modification, and termination of sessions, for example, multimedia conference sessions and Internet sessions. The SIP protocol s multi-party sessions in Multipoint Control Unit (MCU) mode, unicast mode, or multicast mode. In addition, it s alias mapping, redirection, integrated services digital network (ISDN) services, and intelligent network (IN) services. It also s personal mobility. In other words, an MS can request or obtain any telecommunication service at any time anywhere. The SIP protocol provides the following telecommunication functions: location: determination of the end system to be used for communication capabilities: determination of the media and media parameters to be used

availability: determination of the willingness of the callee to engage in communications Session setup: "ringing", establishment of session parameters on the caller and callee sides Session management: including transfer and termination of sessions, modifying session parameters, and invoking services Protocol Stack The SIP protocol can use Datagram Protocol (UDP), Stream Control Transmission Protocol (SCTP) or Transmission Control Protocol (T) as its transport protocol. By default, UDP is used. Figure 2 shows the protocol stack of the UDP-based SIP protocol. Figure 2 Protocol stack of the UDP-based SIP protocol

Figure 3 shows the protocol stack of the SCTP-based SIP protocol. Figure 3 Protocol stack of the SCTP-based SIP protocol

Figure 4 shows the protocol stack of the T-based SIP protocol. Figure 4 Protocol stack of the T-based SIP protocol

Message Structure SIP is a text-based protocol and uses the UTF-8 character set. A SIP message is either a request or a response. Both types of messages consist of a start line, one or more header fields, an empty line indicating the end of the header fields, and an optional message body. The start line in a request is named Request-Line, and that in a response is named Status-Line. A message body can be a specific implementation mode of the current session, which is described by using Session Description Protocol (SDP), or an encapsulated ISUP message. Any SIP message must contain header fields, whereas a message body is optional, depending on the message type and service requirements. A SIP request consists of a Request-Line, a message header, an empty line, and a message body. The carriage-return line-feed sequence (CRLF) is used to distinguish the parameter lines from each other in the message header. Figure 5 shows the structure of a SIP request. Figure 5 Structure of a SIP request

A SIP response consists of a Status-Line, a message header, an empty line, and a message body. The CRLF is used to distinguish the parameter lines from each other in the message header. The parameters vary in different responses. Figure 6 shows the structure of a SIP response. Figure 6 Structure of a SIP response

Message List A SIP message is either a request or a response. A SIP request is sent from a client to a server to activate a specific operation. SIP requests are categorized as follows: INVITE: Indicates that a UE originates a session request and invites another UE to the session. PRACK: Indicates a response to a 1xx message. acknowledgement (ACK): Indicates a final response to an INVITE message. BYE: To terminate an existing session. OPTIONS: To query the information and function of the callee. CANCEL: To cancel a request before the final response to the request is received. A SIP response is used to respond to a request, indicating the status (success or failure) of a session. SIP responses are categorized based on the Status-Code. The Status-Code is a 3-digit integer result code. The first digit defines the type of the SIP response. The other two digits provide a detailed description of the SIP response. SIP responses are categorized as follows: 1xx (Provisional): Indicates that a request is received and the server is continuing to process the request.

2xx (Success): Indicates that the action was successfully received, understood, and accepted. 3xx (Redirection): Indicates that a further action needs to be taken in order to complete the request. 4xx (Client Error): Indicates that the request contains bad syntax or cannot be fulfilled at this server. 5xx (Server Error): Indicates that the server failed to fulfill an apparently valid request. 6xx (Global Failure): Indicates that the request cannot be fulfilled at any server. Table 1 lists common SIP responses. Table 1 List of common SIP responses Message

Direction

Function

100

MSC -> MSC

Trying

180

MSC -> MSC

Ringing

181

MSC -> MSC

Call Is Being Forwarded

182

MSC -> MSC

Queued

183

MSC -> MSC

Session Progress

200

MSC -> MSC

OK

300

MSC -> MSC

Multiple Choices

301

MSC -> MSC

Moved Permanently

302

MSC -> MSC

Moved Temporarily

305

MSC -> MSC

Use Proxy

380

MSC -> MSC

Alternative Service

400

MSC -> MSC

Bad Request

401

MSC -> MSC

Unauthorized

402

MSC -> MSC

Payment Required

403

MSC -> MSC

Forbidden

404

MSC -> MSC

Not Found

405

MSC -> MSC

Method Not Allowed

406

MSC -> MSC

Not Acceptable

407

MSC -> MSC

Proxy Authentication Required

408

MSC -> MSC

Request Timeout

410

MSC -> MSC

Gone

413

MSC -> MSC

Request Entity Too Large

414

MSC -> MSC

Request-URI Too Long

415

MSC -> MSC

Uned Media Type

416

MSC -> MSC

Uned uniform resource identifier (URI) Scheme

420

MSC -> MSC

Bad Extension

421

MSC -> MSC

Extension Required

423

MSC -> MSC

Interval Too Brief

480

MSC -> MSC

Temporarily Unavailable

481

MSC -> MSC

Call/Transaction Does Not Exist

482

MSC -> MSC

Loop Detected

483

MSC -> MSC

Too Many Hops

484

MSC -> MSC

Address Incomplete

485

MSC -> MSC

Ambiguous

486

MSC -> MSC

Busy Here

487

MSC -> MSC

Request Terminated

488

MSC -> MSC

Not Acceptable Here

491

MSC -> MSC

Request Pending

493

MSC -> MSC

Undecipherable

500

MSC -> MSC

Server Internal Error

501

MSC -> MSC

Not Implemented

502

MSC -> MSC

Bad Gateway

503

MSC -> MSC

Service Unavailable

504

MSC -> MSC

Server Timeout

505

MSC -> MSC

Version Not ed

513

MSC -> MSC

Message Too Large

600

MSC -> MSC

Busy Everywhere

603

MSC -> MSC

Decline

604

MSC -> MSC

Does Not Exist Anywhere

606

MSC -> MSC

Not Acceptable

SIP header fields convey characteristics of SIP entities, attributes of message bodies, and other important parameters. One or more header fields may appear in a SIP message. The following are important header fields: Call-ID: uniquely identifies a particular invitation or all registrations of a particular client. From: indicates the logical initiator of the request. It always contains the tag parameter of the initiator. To: indicates the logical recipient of the request. It always contains the tag parameter of the recipient. : provides a URI for routing purposes. Via: indicates the path taken by the request so far and the path that should be followed in routing responses. Route: forces a request to be routed across a listed set of proxies. CSeq: provides a unique sequence number of the request. Content-Length: indicates the size of the message body in decimal number of octets. Content-Type: indicates the media type of the message body sent to the recipient. Record-Route: forces future requests in the dialog to be routed through a particular proxy. Max-Forwards: limits the number of proxies or gateways that can forward the request to the next downstream server. This is useful to prevent a routing loop. P-Access-Network-Info: conveys the Location Number parameter. A SIP message may contain zero or more message bodies, which are mostly SDP and ISUP bodies. An SDP body contains the session description, time description, and media description. Figure 7 shows the format of an SDP body. An ISUP body is in the binary format, as opposed to the textual form of an SDP body. Figure 7 Format of SDP body

Description of the SIP-I Protocol For interoperation between SIP signaling and ISUP signaling, a mechanism of SIP messages incorporated with ISUP signaling is provided. To meet the requirements, the ISUP information must be encapsulated in SIP messages without any loss, or some key information of ISUP messages must be mapped to the corresponding header fields of SIP messages. There are two types of mapping: Mapping between an ISUP message and a SIP message: This is a message-layer mapping between ISUP and SIP. For example, the IAM message of ISUP is mapped to the INVITE message of SIP. Mapping between ISUP parameters and SIP header fields: For example, the called number in the ISUP message must be mapped to the To and Request-URI header fields of the SIP message. Since certain header fields in a SIP request (especially in an INVITE message) change, a conflict may occur between the SIP

header fields and the encapsulated ISUP body. In such a case, the MSC server determines, based on the service scenario, whether to use the values of the SIP header fields or the values of the information elements (IEs) in the ISUP body. Protocols with which the SIP complies Table 2 shows the protocols with which the SIP complies. Table 2 Protocols with which the SIP complies Name

Description

3GPP TS 29.231

Application of SIP-I Protocols to Circuit Switched (CS) core network architecture

3GPP TS 29.235

Interworking between SIP-I based circuitswitched core network and other networks

ITU-T Q.1912.5

Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN Part

IETF RFC 2046

Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types

IETF RFC 2327

Caller Preferences for the Session Initiation Protocol (SIP)

IETF RFC 2833

RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals

IETF RFC 2916

E.164 number and DNS (ENUM)

IETF RFC 2976

The SIP INFO Method

IETF RFC 3204

MIME media types for ISUP and QSIG Objects

IETF RFC 3261

SIP: Session Initiation Protocol

IETF RFC 3262

Reliability of Provisional Responses in the Session Initiation Protocol

IETF RFC 3263

SIP: Locating SIP Servers

IETF RFC 3264

An Offer/Answer Model with the Session Description Protocol

IETF RFC 3265

SIP-Specific Event Notification

IETF RFC 3311

The Session Initiation Protocol (SIP) UPDATE Method

IETF RFC 3319

Dynamic Host Configuration Protocol (DHv6) Options for Session Initiation Protocol (SIP) Servers

IETF RFC 3323

A Privacy Mechanism for the Session Initiation Protocol

IETF RFC 3325

Private Extensions to the Session Initiation

IETF RFC 3326

The Reason Header Field for the Session Initiation Protocol

IETF RFC 3327

Session Initiation Protocol (SIP) Extension Header Field for ing Non-Adjacent s

IETF RFC 3329

Security Mechanism Agreement for the Session Initiation Protocol (SIP)

IETF RFC 3361

Dynamic Host Configuration Protocol (DHfor-IPv4) Option for Session Initiation Protocol (SIP) Servers

IETF RFC 3372

SIP-T Session Initiation Protocol for Telephones (SIP-T): Context and Architectures

IETF RFC 3398

Integrated Services Digital Network (ISDN) Part (ISUP) to Session Initiation Protocol (SIP) Mapping

IETF RFC 3420

Internet Media Type message/sipfrag

IETF RFC 3428

Session Initiation Protocol (SIP) Extension for Instant Messaging

IETF RFC 3455

Private Header (P-Header) Extensions to the Session intial Protocol (SIP) for the 3rdGeneration Partnership Project (3GPP)

IETF RFC 3515

The Session Initiation Protocol (SIP) Refer Method

IETF RFC 3578

Mapping of Integrated Services Digital Network (ISDN) Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)

IETF RFC 3581

An Extension to the Session Initiation Protocol (SIP) for Symmetric Response

Routing IETF RFC 3608

Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration

IETF RFC 3665

Session Initiation Protocol (SIP) Basic Call Flow Examples

IETF RFC 3666

Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows

IETF RFC 3702

Authentication, Authorization, and ing Requirements for the Session Initiation Protocol (SIP)

IETF RFC 3725

Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)

IETF RFC 3824

Using E.164 numbers with the Session Initiation Protocol (SIP)

IETF RFC 3840

Indicating Agent Capabilities in the Session Initiation Protocol (SIP)

IETF RFC 3841

Caller Preferences for the Session Initiation Protocol (SIP)

IETF RFC 3842

A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)

IETF RFC 3891

The Session Initiation Protocol (SIP) "Replaces" Header

IETF RFC 3892

The Session Initiation Protocol (SIP) Referred-By Mechanism

IETF RFC 3893

session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format

IETF RFC 3966

The tel URI for Telephone Numbers

IETF RFC 4028

Session Timers in the Session Initiation Protocol

IETF RFC 4240

Basic Network Media Services with SIP

IETF RFC 5009

Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for

Authorization of Early Media IETF RFC 5086

Diversion Indication in SIP

IETF RFC 6035

Session Initiation Protocol Event Package for Voice Quality Reporting

Parent topic: SIP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Reference Standards Table 1 describes the IEs carried in the common part of messages. Table 1 IEs carried in the common part of messages Information Element (IE)

Method

Description Indicates the type of a request. The methods in Session Initiation Protocol (SIP) requests can be categorized as INVITE, acknowledgement (ACK), BYE, CANCEL, , and OPTIONS. The INVITE method is considered as an example here. Indicates the receipt of a request. Generally, the Request-URI is in the following format: SIP: host: port; : ; transport-param|-param|methodparam|ttl-param|maddr-param|other-param The meaning of each part is as follows:

Request-URI

SIP: Indicates that SIP is used for communication with the specific end system. host: Indicates the domain name or IP address of the host. Port: Indicates the number of the port to which the request is sent. The default value is 5060, that is, the well-known SIP port number. : Is composed of any digit, for example, a telephone number or a name similar to an Email address. The default value is phone. : The can be placed in the SIP uniform resource identifier (URI). It is not safe to transfer authentication information in text mode. Thus, the is not displayed in the SIP URI. transport-param: An optional parameter. It indicates whether Transmission Control Protocol (T) or Datagram Protocol (UDP) is used for transmission. By default, UDP is used. -param: An optional parameter. The SIP URI allows the host to be an IP telephone gateway. In this case, the name can be a common telephone number. This field has two

options: IP and phone. When it is set to phone, it indicates that the name is a telephone number and the corresponding end system is an IP telephone gateway. method-param: An optional parameter. It indicates the method (operation) to be used. ttl-param: Indicates the lifespan of a UDP multicast packet. It is available only when transport-param is set to UDP and maddr-param is set to multicast address. maddr-param: Indicates the address of the server communicating with a specific . It covers the address specified by host and is set to multicast address usually. The Request-URI header field in the INVITE message is considered as an example here. In this example, the domain name of the host is +86263201800001. Indicates the version of the SIP protocol used by a message. SIP-Version

The SIP-Version header field in the INVITE message is considered as an example here. In this example, SIP/2.0 is used. Indicates the status code of a response. It is 3-digit long. 1xx, 2xx, 3xx, 4xx, 5xx, and 6xx indicate different types of responses.

Status-Code The Status-Code header field in the 183 message is considered as an example here. Indicates the meaning of the status code. It is a text description of Status-Code. Reason-Phrase The Reason-Phrase header field in the 183 message is considered as an example here. Reference Standards For details, see 20 "Header Fields" in RFC3261. Parent topic: SIP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages INVITE PRACK ACK BYE OPTIONS CANCEL Parent topic: SIP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

INVITE Message Function Associated IEs Reference Standards Message Function Through number analysis, the local MSC server detects that the outgoing office direction is a Session Initiation Protocol (SIP) office direction or a SIP subscriber, the MSC server sends an INVITE message to the callee, containing the bearer information about the caller. After receiving the INVITE message, the peer MSC server sends a 100 message immediately. Meanwhile, the peer MSC server performs paging, assignment, and tone playing. Figure 1 shows the main header fields of the message. Figure 1 INVITE message


Description

Via

Indicates the path through which the request has ed. For details, see Request-Line and Message Header.

Call-ID

Indicates the ID of the SIP session. For details, see Request-Line and Message Header.

From

Indicates the originator of the request. For details, see Request-Line and Message Header.

To

Indicates the receipt of the request. For details, see Request-Line and Message Header.

command sequence (CSeq)

Indicates the command sequence. For details, see Request-Line and Message Header.

Max-Forwards

Indicates the maximum number of times the request can be forwarded before it arrives at the destination. For details, see Request-Line and Message Header.

Session-Expires

Indicates the time at which the request expires. For details, see Request-Line and Message Header.

Indicates the address for direction communication. For details, see Request-Line and Message Header.

Allow

Indicates the request types ed by the server. For details, see Request-Line and Message Header.

Content-Length

Indicates the length of the message body. For details, see Request-Line and Message Header.

Content-Type

Indicates the media type of the message body. For details, see Request-Line and Message Header.

Message body 1

Indicates the Session Description Protocol (SDP) body contained in the request. For details, see Message Body 1. Indicates the integrated services digital

Message body 2

network (ISDN) part (ISUP) body contained in the request. For details, see Message Body 2.

Reference Standards For details, see 13.2.1 "Creating the Initial INVITE" in RFC3261. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PRACK Message Function Associated IEs Reference Standards Message Function When receiving a 180 message, the local MSC server sends a PRACK message (in response to the 180 message). When receiving the PRACK message, the peer MSC server sends a 200 message (in response to the PRACK message). When the callee answers the call, the peer MSC server sends a 200 message (in response to the INVITE message). The 1xx message defined in the Session Initiation Protocol (SIP) protocol use unreliable transmission. Reliable transmission must be guaranteed to carry media information in the 1xx message. Therefore, the PRACK message is introduced. The PRACK message is a response to the 1xx message, notifying the peer end that the 1xx message is received. Figure 1 shows the main header fields of the message. Figure 1 PRACK message


Description

Via


Call-ID

Indicates the ID of the SIP session. For details, see Request-Line and Message Header. Indicates the originator of the request.

From

For details, see Request-Line and Message Header. To


CSeq


Max-Forwards


RAck

Indicates the sequence number of the PRACK message that maps a reliable provisional response message 1XX. For details, see Request-Line and Message Header.

Content-Length


Reference Standards For details, see 4 "UAC Behavior" in RFC3262. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ACK Message Function Associated IEs Reference Standards Message Function The acknowledgement (ACK) message is a final response to the INVITE message. When receiving a 200 message (in response to an INVITE message), the local MSC server sends an ACK message. Then, the caller and the callee start conversation. Figure 1 shows the main header fields of the message. Figure 1 ACK message


Description

Via


Call-ID

Indicates the ID of the Session Initiation Protocol (SIP) session. For details, see Request-Line and Message Header.

From


To

Indicates the receipt of the request. For details, see Request-Line and Message Header. Indicates the command sequence.

command sequence (CSeq)

For details, see Request-Line and Message Header.

Max-Forwards


Content-Length


Reference Standards For details, see 17.1.1.3 "Construction of the ACK Request" in RFC3261. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

BYE Message Function Associated IEs Reference Standards Message Function If either party releases the session during the conversation, the MSC server to which the party belongs sends a BYE message to the peer MSC server, notifying the peer MSC server of the session release event. When receiving the BYE message, the peer MSC server sends a 200 message (in response to the BYE message). Thus, the session ends. Figure 1 shows the main header fields of the message. Figure 1 BYE message


Description

Via


Call-ID


From


To


Command sequence (CSeq)


Max-Forwards


Reason

Indicates the reason of session release. For details, see Request-Line and Message Header.

Content-Length


Reference Standards For details, see 15.1 "Terminating a Session with a BYE Request" in RFC3261. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

OPTIONS Message Function Associated IEs Reference Standards Message Function The OPTIONS message is used to query the information and function of the callee. Figure 1 shows the main header fields of the message. The MSOFTX3000 s inter-MSC heartbeat detection and Session Initiation Protocol (SIP) subscriber paging by using the OPTIONS message. Figure 1 OPTIONS message


Description

Via


Call-ID

Indicates the ID of the SIP session. For details, see Request-Line and Message Header.

From


To



Indicates the command sequence. For details, see Request-Line and Message

Header.

Max-Forwards


Content-Length


Reference Standards For details, see 11 "Querying for Capabilities" in RFC3261. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CANCEL Message Function Associated IEs Reference Standards Message Function The CANCEL message is used to cancel a pending session. The client can send a CANCEL message at any time. Figure 1 shows the main header fields of the message. Figure 1 CANCEL message


Description

Via


Call-ID


From


To



Indicates the command sequence. For details, see Request-Line and Message

Header.

Max-Forwards


Reason

Indicates the reason of session release. For details, see Request-Line and Message Header.

Content-Length


Reference Standards For details, see 16.10 "CANCEL Processing" in RFC3261. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Request-Line and Message Header Message Body 1 Message Body 2 183 180 200 FOR INVITE Parent topic: SIP Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Request-Line and Message Header Reference Standards Table 1 describes the IEs in the Request-Line and message header. Table 1 IEs in the Request-Line and message header Information Element Description (IE)

Via

Indicates the path through which the request has ed. The Via header field prevents loops during the transmission of a request. It also ensures that the corresponding response takes the same path as the request. Therefore, the transmission of the request and response es through firewalls or meets special requirements on route selection. Generally, the Via header field is in the following format: Via: sent-protocol sent-by; via-params comment Here, sent-protocol = protocol-name/protocol-version/transport; via-params = via-branch. The Via header field must contain the host name or network address of the client and if the default port number is not contained, the port number at which the client wishes to receive responses. Normally, each host that sends or forwards a Session Initiation Protocol (SIP) message places its host name or network address to the Via header field to indicate the path that the SIP message has ed. The sent-by parameter in the Via header field specifies the address to which a response is to be sent. The Via header field in the INVITE message is considered as an example here. In this example, the request is transmitted through Datagram Protocol (UDP) and sent from a termination with the IP address 129.9.30.50 and port number 5062.

Call-ID

Indicates the ID of the SIP session. A single multimedia conference may have several calls with different Call-IDs. For example, a subscriber can identify whether the invitations are repeated by using the session ID of the o IE and the version number in the Session Description Protocol (SDP) body. Generally, the Call-ID header field is in the following format: Call-ID: local-id@host Here, host must be a domain name or an available IP address defined globally. In such a case, local-id, which is composed of uniform resource identifier (URI)

characters, must be uniquely in the scope defined by host. local-id can also be set to a globally unique value to ensure the uniqueness of Call-ID globally. CallIDs are case-sensitive. The Call-ID header field in the INVITE message is considered as an example here. In this example, 10.18.5.64 is a globally defined domain name and 57a5882d4d39645728558b68cc55eb19 is a local ID.

From

Indicates the originator of the request. The server copies the value of the From header field from the request to the corresponding response. All the SIP requests and responses must contain this header field. Generally, the From header field is in the following format: From: display-name <SIP-URI>;tag=xxxx Here, display-name specifies the characters displayed on the interface. If presentation is forbidden, Anonymous is displayed on the interface by default. display-name is an optional parameter. tag must be set to a hexadecimal character string, including hyphens (-). When two instances sharing the same SIP address originate a session by using the same Call-ID, the tag parameter is used for distinguishing. The value of tag must be globally unique. The values of Call-ID and tag cannot be changed during a session. The From header field in the INVITE message is considered as an example here. In this example, 86263201800002 is the calling number of the session.

To

Indicates the recipient of the request. Its format is the same as that of the From header field. All the SIP requests and responses must contain this header field. The To header field in the INVITE message is considered as an example here. In this example, 86263201800001 is the called number of the session. Indicates the command sequence.


All the SIP requests must contain this header field. The header field consists of a decimal sequence number and a method. The sequence number must be unique in the scope defined by Call-ID. The initial sequence number is arbitrary. For the subsequent requests with the same Call-ID but different methods or message bodies, the sequence number increases by one for each request. The request that is resent has the same sequence number as that of the request that is sent for the first time.

The server copies the value of the CSeq header field from the request to the corresponding response. The CSeq header field in the INVITE message is considered as an example here. In this example, the sequence number of the INVITE message is 1. Indicates the session update interval for update negotiation. This header field can be contained in the INVITE, UPDATE, and 2xx messages. SessionExpires

The Session-Expires header field in the INVITE message is considered as an example here. In this example, the local end sends a re-INVITE or UPDATE message to the peer end every 1800 seconds after the session is connected, to check whether the peer end has terminated the session. Indicates the address for direction communication, that is, the URI of the originator. This header field can be contained in the INVITE, ACKnowledgement (ACK), , 1xx, 2xx, and 3xx messages. The header field in the INVITE and ACK messages indicates the location from which the request is sent. Therefore, the callee can directly send requests, for example, a BYE message, to the location identified by the header field, rather than through the proxy servers identified by the Via header field. The header field in the INVITE message is considered as an example here. In this example, the IP address of the caller is 129.9.30.50. Indicates the types of requests ed by the proxy server.

Allow

MaxForwards

The Allow header field in the INVITE message is considered as an example here. In this example, the proxy server s the following methods: INVITE, ACK, OPTIONS, BYE, CANCEL, Information (INFO), PRACK, NOTIFY, MESSAGE, REFER, and UPDATE. Indicates the maximum number of times the request can be forwarded before it arrives at the destination. When receiving a request containing the Max-Forwards header field, the proxy server or gateway must check and update the value of the header field. The initial value of the header field is 70. The value decreases by one at each hop, that is, when the request es through each proxy server or gateway. If the value reaches 0 but the request does not arrive at the destination, the server sends a 483 message and terminates the request. The header field is used to ensure that resources of the proxy servers are not

wasted because of loops during message transmission. The Max-Forwards header field in the INVITE message is considered as an example here. In this example, the request can be forwarded for 70 times before it arrives at the destination. If the request does not arrive at the destination after being forwarded for 70 times, the request is terminated.

Response Sequence (RSeq)

Indicates the sequence number of a reliable provisional response message 1XX. This header field consists of a decimal sequence number and a command name. When a 100rel message is sent and ed, this header field is contained in the reliable provisional response 1XX message, which ensures the reliability of message transmission. The RSeq header field in the 183 message is used as an example here. In this example, the sequence number of the 183 message is 101.

RAck

Indicates the sequence number of the PRACK message that maps a reliable provisional response message 1XX. This header field consists of three parts: two decimal sequence numbers and the message type. The first decimal sequence number is the sequence number indicated by the RSeq header field in the 1XX message. The second decimal sequence number and the message type are those indicated by the CSeq header field in the 1XX message. The RAck header field in the PRACK message is considered as an example here. In this example, the PRACK message is a message in response to the 1XX message, in which the RSeq header field has the sequence number 1 and the CSeq header field has the sequence number 1 INVITE. Indicates the reason of session release. This header field can be contained in the CANCEL and BYE messages.

Reason

ContentLength

The Reason header field in the BYE message is considered as an example here. In this example, the release cause value is 16, which indicates that the session is released normally. Indicates the length of the message body, expressed in decimal values. This header field is used to indicate the size of the message body to be sent. The empty line used for separating the message header from the message body is not counted as Content-Length. The value of Content-Length must not be smaller than 0. If no message body is contained, the value must be set to 0.

The Content-Length header field in the INVITE message is considered as an example here. In this example, the length of the message body is 444 bytes.

ContentType

Indicates the media type of the message body. If the message body is contained, the Content-Type header field must be specified. The Content-Type header field in the INVITE message is considered as an example here. In this example, the media type of the message body is SDP.

Reference Standards For details, see 20 "Header Fields" in RFC3261. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Message Body 1 Reference Standards Session Description Protocol (SDP) is a text-based protocol and uses the International Organization for Standardization (ISO) 10646 character set encoded based on unicode transformation format (8-bit form) (UTF-8). Table 1 describes the IEs carried in the SDP body. Table 1 IEs carried in the SDP body Information Element (IE)

Description Indicates the version number of the SDP protocol.

v

The v IE in the SDP body is considered as an example here. In this example, the version number of the SDP protocol is 0. Indicates the originator of the session and the session ID. Generally, the o IE is in the following format: o = <name><session id>

The o IE in the SDP body is considered as an example here. In this example,

o

<name>: Indicates the host to which the logs in and from which the originates the session. <session id>: Indicates the globally unique sequence number of the session. : IN stands for Internet Network.

: The value can be Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6).

: Indicates the address of the originator. Indicates the name of the session.

s

The s IE in the SDP body is considered as an

example here. In this example, the session name is SipCall. Indicates the connection information. It is an optional IE. Generally, the c IE is in the following format: c =

c

The c IE in the SDP body is considered as an example here. In this example, : IN stands for Internet Network.

: The value can be IPv4 and IPv6. : Indicates the multicast address that can receive the session.

t

Indicates the start time and end time of the association of the session. Generally, the t IE is in the following format: t = <start time><stop time> The t IE in the SDP body is considered as an example here. In this example, the t IE is set to 0, which indicates that the session is permanent. Indicates the media name and transmission address. Generally, the m IE is in the following format: m = <media><port> The m IE in the SDP body is considered as an example here. In this example,

m

<media>: The value can be audio, video, or data. <port>: Indicates the Session Initiation Protocol (SIP) port number used for media stream transmission. In a request for port number allocation, set the parameter to $. In this example, <port> is set to 8952.

: Real-Time Transport Protocol (RTP)/Audio Video Profile (AVP) indicates that the media stream uses the audio and video protocols in the real-time transport protocol. 108 indicates the PayloadType of the media stream. If the parameter is set to a value smaller than 96, the static PayloadType is used and a detailed description is not required. If the parameter is set to a value greater than 96, the dynamic PayloadType is used and a detailed description is required. The detailed description is contained in the "a=" line. 102 is a PayloadType. Provides a description of zero or multiple attributes. Generally, the a IE is in the following format: a = : a

The a IE in the SDP body is considered as an example here. In this example, rtpmap: 108 indicates the dynamic PayloadType in the "m=" line. Adaptive multirate (AMR) indicates the name of the codec. 8000 indicates the sampling rate of the codec.

Reference Standards For details, see 5 "Examples of MTP3- Adaptation Layer (M3UA) Procedures" in RFC4566. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Message Body 2 Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates that the integrated services digital network (ISDN) part (ISUP) body is encapsulated in a Session Initiation Protocol (SIP) message in binary format.

Message body 2 The IAM message body in the INVITE message is considered as an example here. In this example, the length of the IAM message body is 35 bytes. The ISUP body encapsulated in the SIP message has the same message structure as the common ISUP message. For details on the ISUP message, see the ISUP protocol. Reference Standards For details, see 6 "Incoming call interworking from SIP to Bearer Independent Call Control (BICC)/ISUP at I-IWU" in Q1912.5. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

183 Message Function Associated IEs Reference Standards Message Function The local MSC server completes the media negotiation using the media information contained in the INVITE message sent by the peer service data point (SDP). Meanwhile, it encapsulates bearer-related information in the 183 message and sends the message to the peer MSC server. The 1xx response defined in the Session Initiation Protocol (SIP) uses unreliable transmission. Reliable transmission must be used to carry media information in the 1xx response. A reliable 183 message must contain a Require header field and a RSeq header field. Figure 1 shows the main header fields of the message. Figure 1 183 message


Description

Via

Indicates the path through which a request message is transmitted. For details, see Request-Line and Message Header.

Call-ID

Identifies a SIP call. For details, see Request-Line and Message Header.

From


To

Indicates the recipient of the request. For details, see Request-Line and Message Header.



Max-Forwards

Indicates the maximum number of times the request can be forwarded before it reaches the destination. For details, see Request-Line and Message Header.

RSeq

Indicates the sequence of the temporary response message 1XX. For details, see Request-Line and Message Header.

Content-Length

Indicates the length of the message body of the request message. For details, see Request-Line and Message Header.

Reference Standards For details, see 4 "Overview of Operation" in RFC3261. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential


180 Message Function Associated IEs Reference Standards Message Function On setting up a bearer on the terminating side and asg the required Iu interface resources, the terminating mobile switching center (MSC) returns a 180 message to the originating MSC server. The 1xx response defined in the Session Initiation Protocol (SIP) uses unreliable transmission. Reliable transmission must be used to carry media information in the 1xx response. A reliable 180 message must contain a Require header field and a RSeq header field. Figure 1 shows the main header fields of the message. Figure 1 180 message


Description

Via

Indicates the path through which a request message is transmitted. For details, see Request-Line and Message Header.

Call-ID

Identifies a SIP call. For details, see Request-Line and Message Header.

From

Indicates the originator of the request. For details, see Request-Line and Message

Header. To




Max-Forwards


RSeq

Indicates the sequence of the temporary response message 1XX. For details, see Request-Line and Message Header.

Content-Length


Reference Standards For details, see 4 "Overview of Operation" in RFC3261. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

200 FOR INVITE Message Function Associated IEs Reference Standards Message Function The 200 FOR INVITE message is a message sent from the terminating MSC server to the originating MSC server after calls are answered. The originating MSC server then returns an ACK message, indicating that the call is connected. Figure 1 shows the main header fields of the message. Figure 1 200 FOR INVITE message


Description

Via

Indicates the path through which a request is transmitted. For details, see Request-Line and Message Header.

Call-ID

Identifies a Session Initiation Protocol (SIP) call. For details, see Request-Line and Message Header.

From


To




Max-Forwards


Content-Length


Reference Standards For details, see 4 "Overview of Operation" in RFC3261. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

M2UA Protocol Description of the M2UA Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the M2UA Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The Message Transfer Part 2 (MTP2)- Adaptation Layer (M2UA) protocol is used for signaling transmission between SGs and MSC servers. The services provided by M2UA to Message Transfer Part Layer 3 (MTP3) are the same as those provided by MTP2 to MTP3. The services include the following: for MTP2/MTP3 interface boundary for communication between Layer Management (LM) modules on the signaling gateway (SG) and the MSC server for management of Stream Control Transmission Protocol (SCTP) active associations between the SG and the MSC server Protocol Stack The signaling point (SP) in the Signaling System No. 7 (SS7) signaling network connects to the MSC server through the SG. On the SG side, the Nodal Interworking Function (NIF) module is used for interworking between MTP2 and M2UA through primitives. On the MSC server side, M2UA provides services for MTP3. Figure 1 shows the application of the protocol.

Figure 1 Application of the M2UA protocol

Message Structure An M2UA message consists of a common header, an M2UA message header, and multiple variable-length M2UA messages. Figure 2 shows the structure of an M2UA message. Figure 2 Structure of an M2UA message

NOTE: M2UA message 0 to M2UA message n indicate multiple variable-length M2UA messages. The common message classes are as follows: MTP2 Adaptation (MAUP) messages Application Service Provider (ASP) State Maintenance (ASPSM) messages ASP Traffic Maintenance (ASPTM) messages Management (MGMT) messages NOTE: Application Server (AS): A logical entity serving a specific application instance. Practically speaking, an AS is modeled on the SG as an ordered list of one or more related Application Server Processes (ASPs). ASP: A process instance of an AS. Its status is active/standby. Each ASP contains an SCTP endpoint and can process services of multiple ASs. Message List Table 1 List of common M2UA messages

Table 1 List of common M2UA messages Message

Direction

Function

MSC<->SG

The message contains an SS7 MTP2- Protocol Data Unit (PDU).

MSC -> SG

The message is used to establish an SS7 link or to indicate that a channel has been established. The MSC server controls the state of the SS7 link.

Establish Confirm

SG -> MSC

If the SG already has an SS7 link established at its layer, upon receipt of an Establish Request message, the SG takes no action except to send an Establish Confirm message.

Release Request

MSC -> SG

The message is used to release a channel.

SG -> MSC

The message is sent in response to a Release Request message.

SG -> MSC

The message is used to indicate that a channel has been released.

MSC -> SG

The message is sent from the MSC server to cause an action on a particular SS7 link ed by the SG. The SG sends a State Confirm message to the MSC server if the action has been successfully completed.

SG -> MSC

The message is sent in response to a State Request message.

Data

Establish Request

Release Confirm

Release Indication

State Request

State Confirm

State Indication

SG -> MSC

The message is sent from the SG to the ASP to indicate a

condition on an SS7 link.

Data Acknowledge Message MSC <-> SG

The message must contain the correlation ID of the Data message that the sending M2UA is acknowledging as successfully processed to the peer M2UA.

ASP Up

MSC <-> SG

The message is used to indicate to a remote M2UA peer that the adaptation layer is ready to receive traffic or maintenance messages.

MSC <-> SG

The message is used to indicate to a remote M2UA peer that the adaptation layer is not ready to receive traffic or maintenance messages.

MSC <-> SG

The message is optionally used to ensure that the M2UA peers are still available to each other.

MSC <-> SG

The message is used to acknowledge an ASP Up message received from a remote M2UA peer.

MSC <-> SG

The message is used to acknowledge an ASP Down message received from a remote M2UA peer.

MSC <-> SG

The message is sent in response to a Heartbeat message. A peer must send a Heartbeat Ack message in response to a Heartbeat message. The message includes all the parameters of the received Heartbeat message, without any change.

ASP Down

Heartbeat

ASP Up Ack

ASP Down Ack

Heartbeat Ack

ASP Active

MSC -> SG

ASP Inactive

ASP Active Ack

ASP Inactive Ack

Error

Notify

The message is sent by the ASP to indicate to the SG that the ASP is Active and ready to be used.

MSC -> SG

The message is sent by the ASP to indicate to the SG that the ASP is no longer an active ASP to be used from within a list of ASPs.

SG -> MSC

The message is used to acknowledge an ASP Active message received from a remote M2UA peer.

SG -> MSC

The message is used to acknowledge an ASP Inactive message received from a remote M2UA peer.

MSC <-> SG

The message is used to notify a peer of an error event associated with an incoming message. For example, the message type might be unexpected given the current state, or a parameter value might be invalid.

MSC <-> SG

The message is used to provide an autonomous indication of M2UA events to an M2UA peer.

Parent topic: M2UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates the version of the MTP2- Adaptation Layer (M2UA) protocol. Currently, the 1.0 version is ed.

Version version: Indicates the version of the M2UA protocol. The Application Service Provider (ASP) Up message is considered as an example here. In this example, version is 1, which indicates that the version of the M2UA protocol is 1.0. Indicates the class of an M2UA message. The message class is an 8-bit unsigned integer. M2UA messages are categorized as follows: 0: Management (MGMT) message [ISDN Q.921- Adaptation Layer (IUA)/M2UA/MTP3- Adaptation Layer (M3UA)/Signaling Connection and Control Part - Adaptation Layer (SUA)] 1: transfer messages [M3UA] 2: SS7 Signaling Network Management (SSNM) messages [M3UA/SUA] 3: ASP State Maintenance (ASPSM) messages [IUA/M2UA/M3UA/SUA] 4: ASP Traffic Maintenance (ASPTM) messages

Message Class

[IUA/M2UA/M3UA/SUA] 5: Q.921/Q.931 Boundary Primitives Transport (QPTM) messages [IUA] 6: MTP2 Adaptation (MAUP) messages [M2UA] 7: connectionless messages [SUA] 8: connection-oriented messages [SUA] 9: Routing Key Management (RKM) messages (M3UA) 10: Interface Identifier Management (IIM) messages (M2UA) 11 to 127: reserved by the Internet Engineering Task Force (IETF) 128 to 255: reserved for IETFdefined message class extensions

Message Class: Indicates the class of an M2UA message. The ASP Up message is considered as an example here. In this example, Message Class is 3, which indicates that the message is an ASPSM message. Indicates the type of an M2UA message. Each message class contains messages of different types. For example, the ASPSM messages have the following message types: 0: reserved 1: ASP Up (UP)

2: ASP Down (DOWN) 3: Heartbeat (BEAT) 4: ASP Up Ack (UP ACK) 5: ASP Down Ack (DOWN ACK) 6: Heartbeat Ack (BEAT ACK) 7 to 127: reserved by the IETF 128 to 255: reserved for IETFdefined ASPSM extensions Message Type

Message Type: Indicates the type of an M2UA message. The ASP Up message is considered as an example here. In this example, Message Type is 1, which indicates that the message is ASP Up. Indicates the length of an M2UA message. It is expressed in octets and must include the header and parameter padding bytes, if any.

Message Length

Message Length: Indicates the length of an M2UA message. The ASP Up message is considered as an example here. In this example, Message Length is 8, which indicates that the length of the message is 8. Parent topic: M2UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages Data Establish Release State Error Notify ASP Up ASP Active ASP Inactive Parent topic: M2UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Data Message Function Associated IEs Reference Standards Message Function The Data message is an MTP2 Adaptation (MAUP) message. It contains the protocol data unit (PDU) of Message Transfer Part Layer 3 (MTP3). Figure 1 shows the main IEs of the message.

Figure 1 Data message Associated IEs Information Element (IE)

Description

Protocol Data

Contains the MTP2- application message. For details, see Protocol Data.

Reference Standards For details, see 3.3.1.1 "Data" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Establish Message Function Associated IEs Reference Standards Message Function The Establish messages are MTP2 Adaptation (MAUP) messages. The Establish Request and Establish Confirm messages are used to set up an Signaling System No. 7 (SS7) link or to indicate a channel has been set up. Figure 1 and Figure 2 show the main IEs of the Establish Request and Establish Confirm messages.

Figure 1 Establish Request message Figure 2 Establish Confirm message


Description

Establish Request

The message is used to establish an SS7 link or to indicate that a channel has been established. The MSC server controls the state of the SS7 link. If the signaling gateway (SG) already has an

Establish Confirm

SS7 link established at its layer, upon receipt of an Establish Request message, the SG takes no action except to send an Establish Confirm message.

Reference Standards For details, see 3.3.1.3 "Establish (Request, Confirmation)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Release Message Function Associated IEs Reference Standards Message Function The Release messages are MTP2 Adaptation (MAUP) messages. The Release Request message is used to release a channel. The Release Indication and Release Confirm messages are used to indicate or confirm that a channel has been released. Figure 1 and Figure 2 show the main IEs of the Release Request and Release Indication messages. The Release Confirm message consists of only a common header and an M2UA message header.

Figure 1 Release Request message Figure 2 Release Indication message


Description

Release Request

The message is sent from the layer management (LM) to request the Application Service Provider (ASP) to release an Stream Control Transmission Protocol (SCTP) association with the signaling gateway (SG).

Release Indication

The message is sent from the SG to inform the LM that an ASP has released an SCTP association.

Release Confirm

The message is sent from the ASP to confirm to the LM that the ASP has released an SCTP association with the SG.

NOTE: LM is a node function in an SG or ASP that handles the inputs and outputs between the M2UA layer and a local management entity. Reference Standards For details, see 3.3.1.4 "Release (Request, Indication, Confirmation)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

State Message Function Associated IEs Reference Standards Message Function The State messages are MTP2 Adaptation (MAUP) messages. The State Request message is sent from the MSC server to cause an action on a particular Signaling System No. 7 (SS7) link ed by the signaling gateway (SG). The SG sends a State Confirm message to the MSC server if the action has been successfully completed. Figure 1 shows the main IEs of the State Request message.

Figure 1 State Request message The State Confirm message is sent by the SG in response to a State Request message from the MSC server. The State Confirm message reflects the state value received in the State Request message. The structure and valid state values of the State Confirm message are the same as those of the State Request message. Figure 2 shows the main IEs of the State Confirm message. Figure 2 State Confirm message

Associated IEs


Description The state parameter in the State Request message is mandatory. The common state values are as follows: 0 (STATUS_LPO_SET): request local processor outage 1 (STATUS_LPO_CLEAR): request local processor outage recovered 2 (STATUS_EMER_SET): request emergency alignment 3 (STATUS_EMER_CLEAR): request normal alignment (cancel emergency) 4 (STATUS_FLUSH_BUFFERS): flush or clear receive, transmit and retransmit queues 5 (STATUS_CONTINUE): continue or resume 6 (STATUS_CLEAR_RTB): clear the retransmit queue 7 (STATUS_AUDIT): audit state of link 8 (STATUS_CONG_CLEAR): congestion cleared 9 (STATUS_CONG_ACCEPT): congestion accept 10 (STATUS_CONG_DISCARD): congestion discard

State Request

The state value as shown in Figure 1 is 2 (STATUS_EMER_SET). State Confirm

The structure and valid state values of the State Confirm message are the same as those of the State Request message.

Reference Standards For details, see 3.3.1.5 "State Request" in RFC3331. Parent topic: Description of Associated Messages


Error Message Function Associated IEs Reference Standards Message Function The Error message is an MTP2- Adaptation Layer (M2UA) Management (MGMT) message. It is used to notify a peer of an error event associated with an incoming message. Figure 1 shows the main IEs of the message.

Figure 1 Error message Associated IEs Information Element (IE)

Description

Error Code

Indicates the reason for the Error message. For details, see Error Code.

Reference Standards For details, see 3.3.3.1 "Error (ERR)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Notify Message Function Associated IEs Reference Standards Message Function The Notify message is an MTP2- Adaptation Layer (M2UA) Management (MGMT) message. It is used to provide an autonomous indication of M2UA events to an M2UA peer. Figure 1 shows the main IEs of the message.

Figure 1 Notify message Associated IEs Information Element (IE)

Description

Status Type

Indicates the type of the Notify message. For details, see Status Type.

Reference Standards For details, see 3.3.3.2 "Notify (NTFY)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Up Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Up message is an ASP State Maintenance (ASPSM) message. It is used to indicate to a remote MTP2- Adaptation Layer (M2UA) peer that the adaptation layer is ready to receive traffic or maintenance messages. The ASP Up message consists of only a common header. It does not contain any parameter. Figure 1 shows the main IEs of the message.

Figure 1 ASP Up message Associated IEs Information Element (IE)

Description

None

None

Reference Standards For details, see 3.3.2.1 "ASP Up (ASPUP)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Active Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Active message is an ASP Traffic Maintenance (ASPTM) message. It is sent by the ASP to indicate to the SG that the ASP is Active and ready to be used. Figure 1 shows the main IEs of the message.

Figure 1 ASP Active message Associated IEs Information Element (IE)

Description

Traffic Mode Type

Indicates the traffic mode of operation of the ASP within an application server (AS). For details, see Traffic Mode Type.

Reference Standards For details, see 3.3.2.7 "ASP Active (ASPAC)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Inactive Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Inactive message is an ASP Traffic Maintenance (ASPTM) message. It is sent by the ASP to indicate to the SG that the ASP is no longer an active ASP to be used from within a list of ASPs. Figure 1 shows the main IEs of the message.

Figure 1 ASP Inactive message Associated IEs Information Element (IE)

Description

None

None

Reference Standards For details, see 3.3.2.9 "ASP Inactive (ASPIA)" in RFC3331. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Protocol Data Error Code Status Type Traffic Mode Type Parent topic: M2UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Protocol Data Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Contains the MTP2- application message, that is, Message Transfer Part Layer 3 (MTP3) message. Protocol Data is a mandatory IE of the Data message. It contains the MTP2- application message in network byte order starting with the Signaling Information Octet (SIO). The length of the Protocol Data IE cannot exceed the length of the MTP2- application message.

Protocol Data

ProtData: Contains the MTP2- application message. The Data message is considered as an example here. In this example, ProtData is C3 11 34 82 18 06 00 10 0A 00 01 03 00 01 2 and SIO is C3. Reference Standards For details, see 3.3.1.1 "Data" in RFC3331. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Error Code Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the reason for the Error message. Error Code is a mandatory IE of the Error message. Error Code can be any of the following values:

Error Code

1: invalid version 2: invalid interface identifier 3: uned message class 4: uned message type 5: uned traffic handling mode 6: unexpected message 7: protocol error 8: uned interface identifier type 9: invalid stream identifier 10: not used in MTP2- Adaptation Layer (M2UA) 11: not used in M2UA 12: not used in M2UA 13: refused-management blocking 14: Application Service Provider (ASP) identifier required 15: invalid ASP identifier 16: ASP active for interface identifier 17: invalid parameter value 18: parameter field error 19: unexpected parameter 20: not used in M2UA

21: not used in M2UA 22: missing parameter

Error Code: Indicates the reason for the Error message. The Error message is considered as an example here. In this example, Error Code is 8, which indicates an unexpected message. Reference Standards For details, see 3.3.3.1 "Error (ERR)" in RFC3331. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Status Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of the Notify message. Status Type can be set to any of the following values: 1: application server state change (AS_State_Change) 2: other

Status Type: Indicates the type of the Notify message. Status Information: Provides more detailed information for the notification, based on the value of Status Type. When Status Type is set to 1, Status Information can be set to any of the following values:

Status Type

1: reserved 2: application server inactive (AS_Inactive) 3: application server active (AS_Active) 4: application server pending

(AS_Pending) When Status Type is set to 2, Status Information can be set to any of the following values: 1: insufficient Application Service Provider (ASP) resources active in application server (AS) 2: alternate ASP active 3: ASP failure The NOTIFY message is considered as an example here. In this example, Status Type is 1, which indicates that the state of the AS changes; Status Information is 4, which indicates that the AS is pending. Reference Standards For details, see 3.3.3.2 "Notify (NTFY)" in RFC3331. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Traffic Mode Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the traffic mode of operation of the Application Service Provider (ASP) within an application server (AS). Within a particular AS, only one Traffic Mode Type can be used. Traffic Mode Type can be set to any of the following values: 1: override 2: load-share

Traffic Mode Type

Traffic Mode Type: Indicates the traffic mode of operation of the ASP within an AS. The ASP Active message is considered as an example here. In this example, Traffic Mode Type is 2, which indicates that the load-sharing mode is used. Reference Standards For details, see 3.3.2.7 "ASP Active (ASPAC)" in RFC3331. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

M3UA Protocol Description of the M3UA Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the M3UA Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The Message Transfer Part 3 (MTP3)- Adaptation Layer (M3UA) protocol implements interworking between the Signaling System No. 7 (SS7) network and the IP network by using Stream Control Transmission Protocol (SCTP) to transmit MTP3- signaling messages (for example, ISDN part (ISUP) and Signaling Connection Control Part (SC) messages) over the IP network. The services provided by M3UA to upper layer are the same as those provided by MTP3 to the upper layer (ISUP, Telephone Part (TUP), Bearer Independent Call Control (BICC), and SC). The services include the following: for the transfer of all SS7 MTP3- Part messages for interoperation of the MTP3 network management function for management of SCTP associations between the Signaling Gateway Process (SGP) and the Application Server Process (ASP) s for management of connections to multiple SGPs NOTE: Application Server (AS): A logical entity serving a specific routing key. An example of an AS is a virtual switch element handling all call processing for a unique range of public switched telephone network (PSTN) trunks, identified by a destination point code (DPC)/overrun performance counter (OPC)/CIC_range. Another example of an AS is a virtual database unit handling all query transactions, identified by a DPC/OPC/ signaling connection control part sub-system number (SC_SSN). Each AS contains a group of ASPs. Among them, one or multiple ASPs can process services. ASP: A process instance of an AS. Its status is active/standby. Each ASP contains an SCTP endpoint and can process services of multiple ASs. SGP: A process instance of a signaling gateway (SG). It serves as an active,

backup, or load-sharing process of an SG. IP Server Process (IPSP): A process instance of an IP-based application. An IPSP is essentially the same as an ASP, except that it uses M3UA in a point-topoint fashion. Conceptually, an IPSP does not use the services of an SG node. Protocol Stack The M3UA protocol can be used for signaling transmission between SGs and MSC servers as well as signaling transmission between IP-based applications. That is, the M3UA protocol s non-peer-to-peer networking and peer-to-peer networking modes. NOTE: The devices interworking through Signaling Transport (SIGTRAN) can be networked in any of the following modes: Non-peer-to-peer networking mode: In this mode, one end is an AS and the other end is an SG. Peer-to-peer networking mode: In this mode, both ends are ASs or SGs. 1. Protocol Stack of the M3UA Protocol in Non-Peer-to-Peer Networking Mode Figure 1 Protocol stack of the M3UA protocol in non-peer-to-peer networking

mode As shown in Figure 1, the M3UA protocol is used for signaling transmission between SGs and MSC servers. In the SIGTRAN protocol stack, M3UA runs on the upper layer of SCTP. In other words, M3UA is a of SCTP. On the MSC side, the upper layer of M3UA is MTP3 (ISUP, TUP, BICC, or SC). On the SG side, the upper layer of M3UA is Nodal Interworking Function (NIF). 2. Protocol Stack of the M3UA Protocol in Peer-to-Peer Networking Mode Figure 2 Protocol stack of the M3UA protocol in peer-to-peer networking mode

As shown in Figure 2, the M3UA protocol is used for signaling transmission between two MSC servers to provide the same primitives and services to the upper layer as those provided by MTP3. Message Structure An M3UA message consists of a common header followed by zero or more variable-length parameters. Figure 3 shows the structure of the common header. Figure 3 Structure of the common header

All the parameters in the M3UA message are in tag-length-value format. Figure 4 shows the structure of a parameter. Figure 4 Structure of a parameter

The common message classes are as follows: Management (MGMT) messages Transfer messages SS7 Signaling Network Management (SSNM) messages ASP State Maintenance (ASPSM) messages ASP Traffic Maintenance (ASPTM) messages Message List Table 1 List of common M3UA messages Message

Direction

Function The message is used to notify

Error

MSC <-> SG MSC <-> MSC

a peer of an error event associated with an incoming message.

Notify


The message used to provide an autonomous indication of M3UA events to an M3UA peer.

Data


The message contains the SS7 MTP3- protocol data.

SG -> MSC

The message is sent from the SGP in an SG to all concerned ASPs to indicate that the SG has determined that one or more SS7 destinations are unreachable.

Destination Available (DAVA) SG -> MSC

The message is sent from the SGP in an SG to all concerned ASPs to indicate that the SG has determined that one or more SS7 destinations are now reachable (and not restricted), or in response to a DAUD message if appropriate.

Destination State Audit (DAUD)

The message is sent from the ASP to the SGP to audit the availability/congestion state of SS7 routes from the SG to one or more affected destinations.

Destination Unavailable (DUNA)

MSC -> SG

Signaling Congestion (SCON) SG -> MSC

The message is sent from the SGP in an SG to all concerned ASPs to indicate that the SG has determined that there is congestion in the SS7 network to one or more destinations, or to the ASP in response to a DATA or DAUD

message as appropriate.

Destination Part Unavailable (DUPU)

Destination Restricted (DRST)

ASP Up

ASP Down

ASP Up Ack

ASP Down Ack

SG -> MSC

The message is used by the SGP to inform all concerned ASPs that a remote peer MTP3- Part (for example, ISUP or SC) at an SS7 node is unavailable.

SG -> MSC

The message is optionally sent from the SGP in an SG to all concerned ASPs to indicate that the SG has determined that one or more SS7 destinations are now restricted from the point of view of the SG, or in response to a DAUD message if appropriate.

MSC -> SG

The message is used to indicate to a remote M3UA peer that the adaptation layer is ready to receive any ASPSM/ASPTM messages for all routing keys that the ASP is configured to serve.

MSC -> SG

The message is used to indicate to a remote M3UA peer that the adaptation layer is not ready to receive Data, SSNM, or ASPTM messages.

SG -> MSC

The message is used to acknowledge an ASP Up message received from a remote M3UA peer.

SG -> MSC

The message is used to acknowledge an ASP Down message received from a remote M3UA peer. The message is sent by the ASP to indicate to a remote M3UA peer that the ASP is

ASP Active

MSC -> SG

ASP Inactive

ASP Active Ack

ASP Inactive Ack

ready to process signaling traffic for a particular AS.

MSC -> SG

The message is sent by the ASP to indicate to a remote M3UA peer that the ASP is no longer an active ASP to be used from within a list of ASPs.

SG -> MSC

The message is used to acknowledge an ASP Active message received from a remote M3UA peer.

SG -> MSC

The message is used to acknowledge an ASP Inactive message received from a remote M3UA peer.

Parent topic: M3UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates the version of the MTP3- Adaptation Layer (M3UA) protocol. Currently, the 1.0 version is ed.

Version M3UA Protocol Version: Indicates the version of the M3UA protocol. The Application Service Provider (ASP) Up message is considered as an example here. In this example, M3UA Protocol Version is 1, which indicates that the version of the M3UA protocol is 1.0. Indicates the class of an M3UA message. The message class is an 8-bit unsigned integer. M3UA messages are categorized as follows: 0: Management (MGMT) message 1: transfer messages 2: Signaling System No. 7 (SS7) SSNM messages 3: ASP State Maintenance (ASPSM) messages 4: ASP Traffic Maintenance (ASPTM) messages 5: reserved for other Signaling Transport (SIGTRAN) adaptation layers 6: reserved for other SIGTRAN adaptation layers 7: reserved for other SIGTRAN

Message Class

adaptation layers 8: reserved for other SIGTRAN adaptation layers 9: Routing Key Management (RKM) messages 10 to 127: reserved by the Internet Engineering Task Force (IETF) 128 to 255: reserved for IETFdefined message class extensions

Message Class: Indicates the class of an M3UA message. The ASP Up message is considered as an example here. In this example, Message Class is 3, which indicates that the message is an ASPSM message. Indicates the type of an M3UA message. Each message class contains messages of different types. For example, the ASPSM messages have the following message types: 0: reserved 1: ASP Up (ASPUP) 2: ASP Down (ASPDN) 3: Heartbeat (BEAT) 4: ASP Up Ack (ASPUP ACK) 5: ASP Down Ack (ASPDN ACK) 6: Heartbeat Ack (BEAT ACK) 7 to 127: reserved by the IETF 128 to 255: reserved for IETFdefined ASPSM extensions Message Type

Message Type: Indicates the type of an M3UA message. The ASP Up message is considered as an example here. In this example, Message Type is 1, which indicates that the message is ASP Up. Indicates the length of an M3UA message. It is expressed in octets and must include the header and parameter padding bytes, if any.

Message Length

Message Length: Indicates the length of an M3UA message. The ASP Up message is considered as an example here. In this example, Message Length is 8, which indicates that the length of the message is 8. Parent topic: M3UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages Notify ASP Up ASP Active ASP Inactive Parent topic: M3UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Notify Message Function Associated IEs Reference Standards Message Function The Notify message is an MTP3- Adaptation Layer (M3UA) Management (MGMT) message. It is used to provide an autonomous indication of M3UA events to an M3UA peer. Figure 1 shows the main IEs of the message.

Figure 1 Notify message Associated IEs Information Element (IE)

Description

Status Type

Indicates the type of the Notify message. For details, see Status Type.

Reference Standards For details, see 3.8.2 "Notify" in RFC3332. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Up Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Up message is an ASP State Maintenance (ASPSM) message. It is used to indicate to a remote MTP3- Adaptation Layer (M3UA) peer that the adaptation layer is ready to receive traffic or maintenance messages. Figure 1 shows the main IEs of the message.

Figure 1 ASP Up message Associated IEs Information Element (IE)

Description

None

None

Reference Standards For details, see 3.5.1 "ASP Up" in RFC3332. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Active Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Active message is an ASP Traffic Maintenance (ASPTM) message. It is sent by the ASP to indicate to a remote MTP3- Adaptation Layer (M3UA) peer that the ASP is ready to process signaling traffic for a particular application server (AS). Figure 1 shows the main IEs of the message.

Figure 1 ASP Active message Associated IEs Information Element (IE)

Description

Traffic Mode Type

Indicates the traffic mode of operation of the ASP within an AS. For details, see Traffic Mode Type.

Reference Standards For details, see 3.7.1 "ASP Active" in RFC3332. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ASP Inactive Message Function Associated IEs Reference Standards Message Function The Application Service Provider (ASP) Inactive message is an ASP Traffic Maintenance (ASPTM) message. It is sent by the ASP to indicate to a remote MTP3- Adaptation Layer (M3UA) peer that the ASP is no longer an active ASP to be used from within a list of ASPs. Figure 1 shows the main IEs of the message.

Figure 1 ASP Inactive message Associated IEs Information Element (IE)

Description

None

None

Reference Standards For details, see 3.7.3 "ASP Inactive" in RFC3332. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Traffic Mode Type Status Type Parent topic: M3UA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Traffic Mode Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the traffic mode of operation of the Application Service Provider (ASP) within an application server (AS). Traffic Mode Type can be set to any of the following values: 1: override 2: loadshare

Traffic Mode Type

Traffic Mode Type: Indicates the traffic mode of operation of the ASP within an AS. The ASP Active message is considered as an example here. In this example, Traffic Mode Type is 2, which indicates that the load-sharing mode is used. Reference Standards For details, see 3.7.1 "ASP Active" in RFC3332. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Status Type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of the Notify message. Status Type can be set to any of the following values: 1: application server state change (AS_State_Change) 2: other

Status Type: Indicates the type of the Notify message. Status Information: Provides more detailed information for the notification, based on the value of Status Type. When Status Type is set to 1, Status Information can be set to any of the following values:

Status Type

1: reserved 2: application server inactive (AS_Inactive) 3: application server active (AS_Active) 4: application server pending

(AS_Pending) When Status Type is set to 2, Status Information can be set to any of the following values: 1: insufficient Application Service Provider (ASP) resources active in application server (AS) 2: alternate ASP active 3: ASP failure The NOTIFY message is considered as an example here. In this example, Status Type is 1, which indicates that the state of the AS changes; Status Information is 2, which indicates that the AS is inactive. Reference Standards For details, see 3.8.2 "Notify" in RFC3332. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SC Protocol Description of the SC Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the SC Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The Signaling Connection Control Part (SC) protocol provides additional functions to Message Transfer Part (MTP). It implements the packet switching function for virtual circuits and data messages. Thus, it is used for both connectionless and connectionoriented network services between the MSC servers and devices such as the BSC, RNC, HLR, SGSN, and GMLC in telecommunication networks via the Signaling System No. 7 (SS7) network, thus transferring circuit related and non-circuit related signaling information and other types of information (for example, messages for management and maintenance purposes). SC and MTP3 together are equivalent to the functions of the network layer in the OSI system. They make transparent transmission available. The overall objectives of the SC protocol are to provide the means for the following: Logical signaling connections within the SS7 network Transfer capability for network service data units with or without the use of logical signaling connections The services provided by the SC protocol can be categorized as follows: 0: basic connectionless services 1: in-sequence delivery connectionless services 2: basic connection-oriented services 3: flow control connection-oriented services Protocol Stack As a middle layer for message transmission, the upper layers of SC include ISDN part (ISUP), Base Station Subsystem Application Part (BSSAP), and Transaction Capability Application Part (TCAP), and the lower layers of SC include MTP3 and MTP3- Adaptation Layer (M3UA). Figure 1 shows the protocol stack of the SC protocol.

Figure 1 Protocol stack of the SC protocol Message Structure As stipulated in the layered structure of SS7, when an upper layer requests services from a lower layer or a lower layer provides services to an upper layer, interaction is required between the service and the service provider. The signaling data transmitted between two neighboring layers is named primitive. Primitives can be categorized as follows: Request Indication Response Confirmation The lower layer of SC is MTP3 or M3UA. For example, for MTP, the corresponding primitive is marked as MTP-primitive. The upper layer is SC . The primitive transmitted between SC and SC is named N-primitive, also named SC primitive. SC messages are used for communication between SCs, and MTP messages are used for communication between MTPs. Figure 2 shows the primitives and messages between SC and MTP. Figure 2 Primitives and messages

A complete primitive consists of a primitive name, a primitive type, and primitive parameters. Figure 3 shows the structure of a primitive. Figure 3 Primitive structure

The meaning of each part of a primitive is as follows: X: Indicates the functional module that provides the service. (M stands for MTP and N stands for SC). Generic name: Primitive name, indicating the service provided. Specific name: Primitive type, indicating the direction of the primitive. Parameters: Indicates the data transmitted between two layers. NOTE: For example, a signaling message is transmitted to the destination in Unit Data (UDT) mode through a connectionless service protocol. When the SC on the destination node transfers the message to other s, the primitive in the UDT is N-UNITDATA-IND (CDA, CGA, and UD). Here, N stands for the SC primitive; UNITDATA stands for the generic name; IND stands for the specific name, and the direction is from SC to SC ; CDA, CGA, and UD are parameters, which stand for the called address, calling address, and data respectively. Message List Table 1 Common primitives of the SC protocol Primitive

N-UNITDATA-REQ

Direction

Function

SC -> SC

The primitive is used by SC to request SC to transfer SC data to

another SC.

N-UNITDATA-IND

N-CONNECT-REQ

N-CONNECT-IND

N-CONNECT-RES

N-CONNECT-CON

N-DISCONNECT-REQ

N-DISCONNECT-IND

SC -> SC

The primitive is used by SC to inform SC that SC data is being delivered to SC in a connectionless service.

SC -> SC

The primitive is used by SC to request SC to establish a signaling connection.

SC -> SC

The primitive is used by SC to request a callee to establish a signaling connection with a caller.

SC -> SC

The primitive is used by a callee to notify the local SC that the callee is agreed to establish a signaling connection.

SC -> SC

The primitive is used by SC on the originating side to confirm to the caller that a signaling connection has been established.

SC -> SC

The primitive is used by SC to request SC to reject a signaling connection request or disconnect a signaling connection.

SC -> SC

The primitive is used by SC to request SC to reject a signaling connection request or disconnect a signaling connection. The primitive is used by SC to request SC to transfer SC data to

N-DATA-REQ

N-DATA-IND

MTP-TRANSFER-REQ

MTP-TRANSFER-IND

MTP-RESUME-IND

MTP-PAUSE-IND

MTP-STATUS-IND

Parent topic: SC Protocol

SC -> SC

another SC in a connection-oriented service. In a connectionless service, the N-UNITDATA-REQ primitive is used by SC to request SC to transfer SC data to another SC.

SC -> SC

The primitive is used by SC to notify SC that the SC data is being delivered in a connectionoriented service.

SC -> MTP

The primitive is used by SC to request M3UA to transfer data to the peer M3UA.

MTP -> SC

The primitive is used by the peer M3UA to notify its SC that the data is received.

MTP -> SC

The primitive is used by MTP to inform SC of the ability of providing the MTP service to the specified destination.

MTP -> SC

The primitive is used by MTP to inform SC of the total inability of providing the MTP service to the specified destination.

MTP -> SC

The primitive is used by MTP to inform SC of the partial inability of providing the MTP service to the specified destination. The primitive is also used to indicate to a that a remote corresponding is unavailable and the cause of unavailability.



Description Indicates the type of an Signaling Connection Control Part (SC) message.

Message Type

Message Type: Indicates the type of an SC message. The N-STATE-IND primitive is considered as an example here. In this example, Message Type is N-STATE-IND. Indicates the direction of an SC message.

Message Direction

Message Direction: Indicates the direction of an SC message. The N-STATE-IND primitive is considered as an example here. In this example, Message Direction is sc-to- (0), which indicates that the SC message is sent from SC to SC . Indicates the contents of an SC message.

Message Content

Parent topic: SC Protocol

Message Content: Indicates the contents of an SC message. The N-STATE-IND primitive is considered as an example here. In this example, Message Content is the contents of the N-STATE-IND primitive.


Description of Associated Messages SC Primitive MTP Service Primitive Parent topic: SC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SC Primitive Message Function Associated IEs Reference Standards Message Function Signaling Connection Control Part (SC) primitives are used by service interfaces between SC and SC . The SC primitives can be used for connectionless services. For example, the N-UNITDATA-REQ primitive is used for connectionless services. Figure 1 shows the structure of the N-UNITDATA-REQ primitive. Figure 1 N-UNITDATA-REQ primitive

The SC primitives can also be used for connection-oriented services. For example, the N-DISCONNECT-REQ primitive is used for connection-oriented services. Figure 2 shows the structure of the N-DISCONNECT-REQ primitive. Figure 2 N-DISCONNECT-REQ primitive

The SC primitives can also be used for SC management; that is, to perform route reselection or service adjustment during network failure or congestion to maintain the network performance. For example, the N-STATE-IND primitive is used for SC management. Figure 1 shows the structure of the NSTATE-IND primitive. Figure 3 N-STATE-IND primitive


Description

Service Information Octet (SIO)

Indicates the class of an SC message. For details, see Service Information Octet.

Protocol class

Indicates the protocol class of an SC message. For details, see Protocol Class.

Calling/Called address

Indicates the originating point code (OPC)/destination point code (DPC) and (or) SC access point.

For details, see Calling/Called Address. data

Contains SC upper layer information or SC management information. For details, see Data.

Reason

Indicates the reason for signaling connection rejection or interruption. For details, see Reason.

N-PCSTATE

Is used to inform a local subsystem about the status of an signaling point (SP) during SC management. For details, see N-PCSTATE.

N-STATE

Is used to inform SC management about the status of a local subsystem. For details, see N-STATE.

Reference Standards For details, see 6 "Services provided by the SC" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MTP Service Primitive Message Function Associated IEs Reference Standards Message Function Message Transfer Part (MTP) service primitives are used by service interfaces between Signaling Connection Control Part (SC) and MTP. The MTP service primitives can be used to send messages from SC to MTP and messages from MTP to SC. Associated IEs Information Element (IE)

Description

MTP-TRANSFER-REQ

The primitive is used by SC to request MTP3- Adaptation Layer (M3UA) to transfer data to the peer M3UA.

MTP-TRANSFER-IND

The primitive is used by the peer M3UA to notify its SC that the data is received.

MTP-PAUSE-IND

The primitive is used by MTP to inform SC of the total inability of providing the MTP service to the specified destination. For details, see MTP-PAUSE-IND.

MTP-RESUME-IND

The primitive is used by MTP to inform SC of the ability of providing the MTP service to the specified destination. For details, see MTP-RESUME-IND.

MTP-STATUS-IND

The primitive is used by MTP to inform SC of the partial inability of providing the MTP service to the specified destination. The primitive is also used to indicate to a that a remote corresponding is unavailable and the cause of unavailability. For details, see MTP-STATUS-IND.

Reference Standards For details, see 7.2 "MTP-primitives and parameters" in International Telecommunication

Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs MTP-PAUSE-IND MTP-RESUME-IND MTP-STATUS-IND N-PCSTATE N-STATE Protocol Class Service Information Octet Data Reason Calling/Called Address Parent topic: SC Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MTP-PAUSE-IND Description of the IE Reference Standards Description of the IE Information Element (IE)

Description The primitive is used by Message Transfer Part (MTP) to inform Signaling Connection Control Part (SC) of the total inability of providing the MTP service to the specified destination.

MTP-PAUSE-IND

Affected destination point code (DPC): Indicates the affected SPs. The MTP-PAUSE-IND primitive is considered as an example here. In this example, Affected DPC is 0x840010, which indicates that MTP is unable to send messages to the destination with the signaling point (SP) 0x840010.

Reference Standards For details, see 7.2 "Services provided by the SC" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MTP-RESUME-IND Description of the IE Reference Standards Description of the IE Information Element (IE)

Description The primitive is used by Message Transfer Part (MTP) to inform Signaling Connection Control Part (SC) of the ability of providing the MTP service to the specified destination.

MTP-RESUME-IND

Affected destination point code (DPC): Indicates the affected SPs. The MTP-RESUME-IND primitive is considered as an example here. In this example, Affected DPC is 0x2A1002, which indicates that MTP is able to provide the MTP service to the destination with the signaling point (SP) 0x2A1002.

Reference Standards For details, see 7.2 "Services provided by the SC" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MTP-STATUS-IND Description of the IE Reference Standards Description of the IE information element (IE)

Description The primitive is used by Message Transfer Part (MTP) to inform Signaling Connection Control Part (SC) of the status of a signaling point (SP) of the destination.

MTP-STATUS-IND Affected destination point code (DPC): Indicates the affected SPs. The MTP-STATUS-IND primitive is considered as an example here. In this example, Affected DPC is 0x123456, which indicates that the SP 0x123456 is unavailable. Reference Standards For details, see 7.2 "Services provided by the SC" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

N-PCSTATE Description of the IE Reference Standards Description of the IE information element (IE)

Description Is used to inform a about the status of a signaling point (SP) during Signaling Connection Control Part (SC) management.

Affected signaling point: Indicates an affected SP, that is, an SP that is failed, congested, withdrawn, or allowed. Signaling point status: Indicates the status of an affected SP. Remote SC status: Indicates the status of a remote SC.

N-PCSTATE

The N-PCSTATE-IND primitive is considered as an example here. In this example, Affected signaling point is H'2a1111; signaling point status is 1, which indicates that the SP H'2a1111 is not allowed to use; Remote SC status is 1, which indicates that the remote SC is unreachable. Reference Standards For details, see 6.3.2 "Primitives and parameters of the SC management" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs


N-STATE Description of the IE Reference Standards Description of the IE information element (IE)

Description Is used to inform Signaling Connection Control Part (SC) management about the status of a .

N-STATE

Affected subsystem: Indicates an affected subsystem, that is, a subsystem that is failed, congested, withdrawn, or allowed. status: Indicates the status of the affected subsystem. Subsystem multiplicity indicator: Used by SC management messages; indicates the number of replications of a subsystem. The N-STATE-IND primitive is considered as an example here. In this example, Affected subsystem is 1, which indicates that the affected subsystem is an SC management subsystem; status is 1, which indicates that the SC management subsystem is not allowed to use; Subsystem multiplicity indicator is 0, which indicates that the number of replications of the SC management subsystem is 0.

Reference Standards For details, see 6.3.2 "Primitives and parameters of the SC management" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711.


Protocol Class Description of the IE Reference Standards Description of the IE information element (IE)

Description Indicates the protocol class of an Signaling Connection Control Part (SC) message. The protocol classes of the SC protocol can be categorized as follows:

Protocol Class

0: 1: 2: 3:

basic connectionless class in-sequence delivery connectionless class basic connection-oriented class flow control connection-oriented class

protocol class: Indicates the protocol class of an SC message. The N-UNITDATA-REQ primitive is considered as an example here. In this example, protocol class is 0, which indicates that the protocol class of the message is 0, basic connectionless class. Reference Standards For details, see 2.10 "protocol class" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.712. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Service Information Octet Description of the IE Reference Standards Description of the IE information element (IE)

Description Indicates the class of a Signaling Connection Control Part (SC) message. service information octet (SIO) consists of the network indicator and service indicator. MTP3 uses SIO to distribute messages to the corresponding functional module. The Service Information Octet parameter is 8-bit long, where the network indicator occupies 2 bits and the service indicator occupies 4 bits.

Network Indicator: Indicates the type of a signaling network. The network indicator can be set to any of the following values:

Service Information Octet

0: 1: 2: 3:

international network international reserved network national network national reserved network

Service indicator: Indicates a specific service. The common service indicators are as follows: 0: signaling network management messages 1: signaling network testing and maintenance messages 2: reserved 3: SC 4: Telephone Part (TUP)

5: ISDN part (ISUP) The N-UNITDATA-REQ primitive is considered as an example here. In this example, Network Indicator is 2, which indicates that the signaling network is a national network; Service indicator is 3, which indicates the SC service. Reference Standards For details, see 14.2 "Service information octet" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.704. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Data Description of the IE Reference Standards Description of the IE information element (IE)

Description Contains Signaling Connection Control Part (SC) upper layer information or SC management information. The SC upper layer information includes information about ISDN part (ISUP), Base Station Subsystem Application Part (BSSAP), and Transaction Capability Application Part (TCAP).

Data

SC DATA: Indicates the information contained in an SC message. The N-UNITDATA-IND primitive is considered as an example here. In this example, SC contains the TCAP information. Reference Standards For details, see 6.1.1.2.3 "Data transfer phase" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Reason Description of the IE Reference Standards Description of the IE information element (IE)

Description Indicates the reason for signaling connection rejection or interruption.

Reason reason: Indicates the reason for signaling connection rejection or interruption. The N-DISCONNECT-REQ primitive is considered as an example here. In this example, reason (disconnect cause) is 5, end-originated, which indicates that the signaling connection is released at the request of the . Reference Standards For details, see 6.1.1.2.4 "Release phase" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling/Called Address Description of the IE Reference Standards Description of the IE information element (IE)

Description Uniquely identifies an originating point code (OPC)/destination point code (DPC) and (or) a Signaling Connection Control Part (SC) access point. An SC address consists of GT, DPC, and SSN.

Calling/Called address

Subsystem number: Indicates the subsystem number in an SC address. Signaling point code: Indicates the

signaling point (SP) in an SC address. Global title: Indicates the GT in an SC address. The N-UNITDATA-REQ primitive is considered as an example here. In this example, the GT mode is used for addressing, and the address is the combination of GT and SSN. For the calling address, Subsystem number is 6, which indicates that the subsystem is an HLR; Global title is 8613990001. For the called address, Subsystem number is 8, which indicates that the subsystem is an MSC server; Global title is 8613915001. Reference Standards For details, see 6.1.1.2.2 "Connection establishment phase" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.711. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

PRA Protocol Description of the PRA Protocol Description of the Common Part of Messages Description of Associated Messages Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the PRA Protocol Scenario Description Protocol Stack Message Structure Message List Scenario Description The Primary Rate Access (PRA) protocol is one of the interface protocols defined by the Digital Subscriber Signaling No.1 (DSS1) signaling system. The DSS1 signaling system is a group of interface protocols between integrated services digital network (ISDN) s and networks. It consists of the physical layer, link layer, and network layer, corresponding to the three bottom layers of the OSI system. Figure 1 shows the scenarios of the PRA protocol. Figure 1 Networking between MSC servers through the PRA protocol

Figure 2 Networking between the MSC server and the PBX through the PRA protocol

Protocol Stack Figure 3 shows the protocol stacks of the PRA protocol in the two scenarios. Figure 3 Protocol stacks of the PRA protocol in the two scenarios

Message Structure Figure 4 shows the structure of a PRA message. Figure 4 Structure of a PRA message

Message List Message

Function

ALERTING

The message is sent by the callee to the network and by the network to the caller to indicate that callee alerting has been initiated.

CALL PROCEEDING

The message is sent by the callee to the network or by the network to the caller to indicate that requested call establishment has been initiated and no more call

establishment information will be accepted. CONNECT

The message is sent by the callee to the network and by the network to the caller to indicate call acceptance by the callee.

CONNECT ACKNOWLEDGE

The message is sent by the network to the callee to indicate the has been awarded the call. It may also be sent by the caller to the network to allow symmetrical call control procedures.

DISCONNECT

The message is sent by the to request the network to clear an end-to-end connection or is sent by the network to indicate that the end-to-end connection is cleared.

RELEASE

The message is sent by the or the network to indicate that the equipment sending the message has disconnected the channel (if any) and intends to release the channel and the call reference. Thus, the receiving equipment should release the channel and prepare to release the call reference after sending a RELEASE COMPLETE message.

RELEASE COMPLETE

The message is sent by the or the network to indicate that the equipment sending the message has released the channel (if any) and call reference, the channel is available for reuse, and the receiving equipment should release the call reference.

SETUP

The message is sent by the caller to the network and by the network to the callee to initiate call establishment.

SETUP ACKNOWLEDGE

The message is sent by the network to the caller or by the callee to the network to indicate that call establishment has been initiated, but additional information may be required.

Parent topic: PRA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 describes the IEs carried in the common part of messages. Table 1 IEs carried in the common part of messages information element (IE)

Description

Protocol discriminator: Is used to distinguish messages for -network call control from other messages. The length of the IE is one byte. Call reference: Identifies a call on the B channel. Message type: Indicates the type of the message being sent. The length of the IE is one byte. Q.931 has defined dozens of messages of different types. Messages of different types have different functions and contain different IEs.

Common IEs

The SETUP message is considered as an example here. In this example, Protocol discriminator is -network-call-controlmessage-recommendation-Q931(8), which indicates that the protocol class of the message is Q.931; Call reference is 0x500(1280), which indicates a call with the call ID 0x500 on the B channel; Message type is setup(5), which indicates that the message being sent is a SETUP message. Parent topic: PRA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages ALERTING CALL PROCEEDING CONNECT CONNECT ACKNOWLEDGE DISCONNECT RELEASE RELEASE COMPLETE SETUP SETUP ACKNOWLEDGE Parent topic: PRA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

ALERTING Message Function Associated IEs Reference Standards Message Function The message is sent by the callee to the network and by the network to the caller to indicate that callee alerting has been initiated. Figure 1 shows the main IEs of the message. Figure 1 ALERTING message

Associated IEs Message

Function

Message type

Indicates the type of a message. For details, see Message type.

Progress indicator

Indicates an event that has occurred during the life of a call. For details, see Progress indicator.

Reference Standards For details, see 3.1.1 "ALERTING" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CALL PROCEEDING Message Function Associated IEs Reference Standards Message Function The message is sent by the callee to the network or by the network to the caller to indicate that requested call establishment has been initiated and no more call establishment information will be accepted.

Figure 1 CALL PROCEEDING message Associated IEs Message

Function

Channel identification

Indicates a channel within the interface controlled by the signaling procedures. For details, see Channel identification.

Reference Standards For details, see 3.1.2 "CALL PROCEEDING" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CONNECT Message Function Associated IEs Reference Standards Message Function The message is sent by the callee to the network and by the network to the caller to indicate call acceptance by the callee. Figure 1 shows the main IEs of the message. Figure 1 CONNECT message

Associated IEs information element (IE)

Description

Progress indicator

Indicates an event that has occurred during the life of a call. For details, see Progress indicator.

Reference Standards For details, see 3.1.3 "CONNECT" in ITU-T Q.931.


CONNECT ACKNOWLEDGE Message Function Reference Standards Message Function The message is sent by the network to the callee to indicate the has been awarded the call. It may also be sent by the caller to the network to allow symmetrical call control procedures. Figure 1 shows the main IEs of the message. The message may contain no information element (IE). Figure 1 CONNECT ACKNOWLEDGE message

Reference Standards For details, see 3.1.4 "CONNECT ACKNOWLEDGE" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

DISCONNECT Message Function Associated IEs Reference Standards Message Function The message is sent by the to request the network to clear an end-to-end connection or is sent by the network to indicate that the end-to-end connection is cleared. Figure 1 shows the main IEs of the message. Figure 1 DISCONNECT message

Associated IEs Information Element (IE) Description Cause

Indicates the cause for the message. For details, see Cause.

Reference Standards For details, see 3.1.5 "DISCONNECT" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

RELEASE Message Function Associated IEs Reference Standards Message Function The message is sent by the or the network to indicate that the equipment sending the message has disconnected the channel (if any) and intends to release the channel and the call reference. Thus, the receiving equipment should release the channel and prepare to release the call reference after sending a RELEASE COMPLETE message. Figure 1 shows the main IEs of the message.

Figure 1 RELEASE message Associated IEs Information Element (IE)

Description

Cause

Indicates the cause for the message. For details, see Cause.

Reference Standards For details, see 3.1.9 "RELEASE" in ITU-T Q.931. Parent topic: Description of Associated Messages


RELEASE COMPLETE Message Function Reference Standards Message Function The message is sent by the or the network to indicate that the equipment sending the message has released the channel (if any) and call reference, the channel is available for reuse, and the receiving equipment should release the call reference. Figure 1 shows the main IEs of the message. Figure 1 RELEASE COMPLETE message

Reference Standards For details, see 3.1.10 "RELEASE COMPLETE" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SETUP Message Function Associated IEs Reference Standards Message Function The message is sent by the caller to the network and by the network to the callee to initiate call establishment. Figure 1 shows the main IEs of the message.

Figure 1 SETUP message Associated IEs Information Element (IE)

Description

Bearer capability

Indicate a requested bearer service to be provided by the network.

For details, see Bearer capability. Calling party number

Indicates a caller number. For details, see Calling party number.

Called party number

Indicates a callee number. For details, see Called party number.



Reference Standards For details, see 3.1.14 "SETUP" in ITU-T Q.931. Parent topic: Description of Associated Messages Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SETUP ACKNOWLEDGE Message Function Associated IEs Reference Standards Message Function The message is sent by the network to the caller or by the callee to the network to indicate that call establishment has been initiated, but additional information may be required. Figure 1 shows the main IEs of the message. Figure 1 SETUP ACKNOWLEDGE message

Associated IEs Information Element (IE) Description Channel identification


Reference Standards For details, see 3.3.10 "SETUP ACKNOWLEDGE" in ITU-T Q.931.


Description of Associated IEs Bearer capability Call reference Called party number Called party subaddress Calling party number Calling party subaddress Cause Channel identification Date/time Display High layer compatibility Keypad facility Low layer compatibility Message type Network-specific facilities Progress indicator Protocol discriminator Repeat indicator Sending complete Signal Transit network selection Parent topic: PRA Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Bearer capability Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a requested bearer service to be provided by the network. It contains bearer related information, for example, transmission information, transmission rate mode, and codec information.

Bearer capability info transfer capability: Indicates the transmission capability. info transfer rate: Indicates the transmission rate. info layer1 proto: Indicates the codec used for transmission. The SETUP message is considered as an example here. In this example, info transfer capability is speech(0), which indicates that the call is a voice call; info transfer rate is kbit-64; info layer1 proto is recommendation-G711-ALaw. Reference Standards For details, see 4.5.5 "Bearer capability" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs


Call reference Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates a call at the local -network interface to which the particular message applies.

Call reference

length: Indicates the length of the call reference. cr-value-2-byte: Indicates the value of the callee reference. The SETUP message is considered as an example here. In this example, length is 2, and cr-value-2-byte is 0x300.

Reference Standards For details, see 4.3 "Call reference" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Called party number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the callee of a call. Generally, this IE is contained in the SETUP message.

Called party number

Numbering plan identification: The values include unknown number and integrated services digital network (ISDN) number. Type of number: Indicates the type of the callee number, for example, a national number or an international number. Number: Indicates the callee number. The SETUP message is considered as an example here. In this example, Numbering plan identification is 1, which indicates that the number is an ISDN number; Type of number is subscriber-number(4), which indicates that the number is a subscriber number; Number is 13709260002, which indicates that the callee number is 13709260002.

Reference Standards For details, see 4.5.8 "Called party number" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Called party subaddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the subaddress of the callee. The maximum length of the IE is 23 octets.

Called party subaddress

Odd even indicator: Indicates whether the subaddress is an odd or even. Type of subaddress: Indicates the type of the subaddress. The SETUP message is considered as an example here. In this example, Odd even indicator is 0, which indicates that the subaddress is an even; Type of subaddress is NASP(0). (For details on the NASP, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Rec.X.213[23] and International Organization for Standardization (ISO)/International Electro Technical Committee (IEC) 8348).

Reference Standards For details, see 4.5.9 "Called party subaddress" in ITU-T Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling party number Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies the caller of a call.


Numbering plan identification: The values include unknown number and integrated services digital network (ISDN) number. Type of number: The values include unknown number, national number, and international number. Number: Indicates the caller number. The SETUP message is considered as an example here. In this example, Numbering plan identification is 1, which indicates that the number is an ISDN number; Type of number is international number(1), which indicates that the number is an international number; Number is 8613802900312, which indicates that the caller number is 8613802900312.

Reference Standards For details, see 4.5.10 "Calling party number" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Calling party subaddress Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the subaddress of the caller. The maximum length of the IE is 23 octets. It is expressed in binary-coded data (BCD) code.

Calling party subaddress

Odd even indicator: Indicates whether the subaddress is an odd or even. Type of subaddress: Indicates the type of the subaddress. The SETUP message is considered as an example here. In this example, Odd even indicator is 0, which indicates that the subaddress is an even; Type of subaddress is NASP(0). (For details on the NASP, see International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Rec.X.213[23] and International Organization for Standardization (ISO)/International Electro Technical Committee (IEC) 8348).

Reference Standards For details, see 4.5.11 "Calling party address" in ITU-T Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description Indicates the cause for the message.

Cause

location: Indicates the network location. coding standard: Indicates the coding standard adopted. cause value: Indicates the cause value contained in the message. The DISCONNECT message is considered as an example here. In this example, location is public-network-serving-thelocal-(2); coding standard is itu-T-standardizedcoding(0); cause value is normal-call-clearing(16).

Reference Standards For details, see 4.5.12 "Cause" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.931 and the related chapters in ITU-T Q.850. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Channel identification Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies a channel.


D channel indicator: Indicates whether the channel is a D channel. Preferred exclusive: Indicates the channel selection mode. It is applicable only to B channels. Interface type: Indicates the type of the interface. The SETUP message is considered as an example here. In this example, D channel indicator is not-D-channel(0), which indicates that the channel is not a D channel; Preferred exclusive is exclusive(1), which indicates that only identified channel is to be selected; Interface type is otherinterface(1), which indicates that the interface is not a basic interface.

Reference Standards For details, see 4.5.13 "Channel identification" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Date/time Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the date and time when the message is sent. The IE can be expressed to the precise of seconds.

Date/time Year: Indicates the year when the message is sent. Month: Indicates the month when the message is sent. The CONNECT message is considered as an example here. In this example, Year is 0x5(5), which indicates that the message is sent in 05; Month is 0x5(5), which indicates that the message is sent in May. Reference Standards For details, see 4.5.15 "Date/time" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Display Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Provides information that may be displayed to the .

Display

Display information: Indicates the information displayed. The SETUP message is considered as an example here. In this example, Display information is 0, which indicates that no information is displayed.

Reference Standards For details, see 4.5.16 "Display" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

High layer compatibility Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the high layer compatibility used by the call. This IE is transparently transmitted through two integrated services digital network (ISDN) entities.

High layer compatibility

coding standard: Indicates the coding standard adopted. high layer characteristic identification: Indicates the identification of the high layer characteristic. The SETUP message is considered as an example here. In this example, coding standard is itu-t-standardized coding, which indicates that the protocol type is International Telecommunication Union-Telecommunication Standardization Sector (ITU-T); high layer characteristic identification is facsimile Group, which indicates that the high layer characteristic is fax.

Reference Standards For details, see 4.5.17 "High layer compatibility" in ITU-T Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Keypad facility Description of the IE Reference Standards Description of the IE Information Element (IE)

Description It is used to convey IA5 characters. The maximum length of the IE is 34 octets.

Keypad facility

Keypad facility information: Indicates the information about the keypad facility. The SETUP message is considered as an example here. In this example, Keypad facility information is 0.

Reference Standards For details, see 4.5.18 "Keypad facility" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Low layer compatibility Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the bearer capability. It contains bearer related information, for example, transmission information, transmission rate mode, and codec information.

Low layer compatibility Information transfer capability: Indicates the transmission compatibility. Negotiation indicator: Indicates the compatibility negotiation. Transfer mode: Indicates the transmission mode. The SETUP message is considered as an example here. In this example, Information transfer capability is speech(0), which indicates that the call is a voice call; Negotiation indicator is out-band-negotiation-not-possible(0); Transfer mode is circuit-mode(0), which indicates that circuit transmission mode is used. Reference Standards For details, see 4.5.19 "Low layer compatibility" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs


Message type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the type of a message. The message type indicates the message function. Generally, the IE is the third part of every message. Bit 8 is reserved for possible future use as an extension bit.

Message type Message type: Indicates the type of a message. The SETUP message is considered as an example here. In this example, Message type is setup(5), which indicates that the message is a SETUP message. Reference Standards For details, see 4.4 "Message type" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Network-specific facilities Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates which network facilities are to be invoked. This IE is contained when the caller or the network has network-specific facilities. The number of IEs in a message cannot exceed 4.

Network-specific facilities Length of network identification: Indicates the length of the network facility information. Network specific facility specification: Indicates the information about the network-specific facilities. The SETUP message is considered as an example here. In this example, length of network identification is 0 and network specific facility specification is 0. Reference Standards For details, see 4.5.21 "Network-specific facilities" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Progress indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates an event that has occurred during the life of a call. The maximum length of the IE is four octets.

Progress indicator

location: Indicates the network location. Coding standard: Indicates the coding standard adopted. Progress description: Provides an event description. The ALERTING message is considered as an example here. In this example, Location is public network serving the local (2); Coding standard is itu-T-standardized coding; Progress description is In-band information or an appropriate pattern is now available(8).

Reference Standards For details, see 4.5.23 "Progress indicator" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Protocol discriminator Description of the IE Reference Standards Description of the IE Information Element (IE)

Protocol discriminator

Description Indicates the protocol class of the message. From the direction network -> , if the message is the first response to a SETUP message, this IE must be contained. From the direction -> network, if the message is the first response to a SETUP message, this IE must be contained unless the accepts the B channel indicated in the SETUP message. Protocol discriminator: Indicates the protocol class of the message. The SETUP message is considered as an example here. In this example, Protocol discriminator is network call control message recommendation-Q931, which indicates that the protocol class of the message is Q.931.

Reference Standards For details, see 4.2 "Protocol discriminator" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Repeat indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates how repeated IEs should be interpreted, when included in a message. The IE is included before the first occurrence of the IE that will be repeated in a message. The length of the IE is one octet.

Repeat indicator Repeat indicator: Four bits are used to indicate repeated information. The IE is valid only when it is set to 1, which indicates that one value will be selected according to the priority. The SETUP message is considered as an example here. In this example, Repeat indicator is 0. Reference Standards For details, see 4.5.24 "Repeat indicator" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Sending complete Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Indicates the completion of a callee number. The length of the IE is one octet.

Sending complete

Sending complete: Indicates the completion of a callee number. The SETUP message is considered as an example here. In this example, Sending complete is used to indicate the completion of a callee number.

Reference Standards For details, see 4.5.27 "Sending complete" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Signal Description of the IE Reference Standards Description of the IE Information Element (IE)

Description It is used to convey information to a regarding tones and alerting signals.

Signal

signal value: Indicates the value of the signal. The SETUP message is considered as an example here. In this example, signal value is dial-tone-on(0), which indicates the dial tone switch is enabled.

Reference Standards For details, see 4.5.28 "Signal" in International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Transit network selection Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Identifies one requested transit network. A message can contain multiple such IEs.

Transit network selection

Network identification plan: Indicates the network identification plan. For example, it can be set to unknown. For details, see Recommendation X121[21]. Type of network identification: Indicates the type of the network identification, for example, an international number identification. The SETUP message is considered as an example here. In this example, Network identification plan is 0, unknown; Type of network identification is 0, defined type.

Reference Standards For details, see 4.5.29 "Transit network selection" in International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) Q.931. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGs Interface Protocol Description of the SGs Interface Protocol Description of the Common Part of Messages Description of Associated Messages in the Alert Flow Description of Associated Messages in SMS Description of Associated Messages in Location Updates Description of Associated Messages in the Paging Flow Description of Associated Messages in the Fault Processing Flow Description of Associated Messages in the Reset Flow Description of Associated Messages in the Service Abort Flow Description of Associated IEs Parent topic: Appendix - Protocol Compliance Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the SGs Interface Protocol Scenario Description Protocol Stack Message List Reference Standards Scenario Description The SGs interface interconnects the mobile switching center (MSC) server and mobility management entity (MME). The MSC server together with the MME can implement mobility management, paging during the voice call service and short message service (SMS) for subscribers with the Evolved Packet System (EPS) and circuit switched (CS) networks. Figure 1 shows the application of the SGs interface protocol.

Figure 1 Application of the SGs interface protocol Protocol Stack Figure 2 shows the protocol stack of the SGs interface protocol. Figure 2 Protocol stack of the SGs interface protocol

In the above protocol stack: SGsAP is used on the application layer between the MSC server and MME. SCTP is used on the transmission layer to ensure reliability of signaling transmission between the MSC server and MME. Message List Table 1 List of common SGs interface messages

Message

Direction

Function

SGsAP-ALERTREQUEST

MSC server/VLR>MME

The MSC server/visitor location (VLR) sends this message, instructing the MME to notify the MSC server/VLR when detecting signaling exchange of a subscriber.

SGsAP-ALERT-ACK

MME->MSC server/VLR

The MME sends this message in response to an SGsAP-ALERT-REQUEST message when the MME has a subscriber's IMSI information.

MME->MSC server/VLR

The MME sends the message in response to an SGsAP-ALERT-REQUEST message when the MME does not have a subscriber's IMSI information.

SGsAP-UE-ACTIVITY- MME->MSC INDICATION server/VLR

The MME sends this message to the MSC server when detecting signaling exchange of a subscriber.

SGsAP-UPLINKUNITDATA

MME->MSC server/VLR

The MME sends this message to transparently convey the NAS message sent by the UE to the MSC server/VLR.

SGsAP-DOWNLINKUNITDATA

MSC server/VLR>MME

The MSC server/VLR sends this message to transparently convey the NAS message to be sent to the UE.

SGsAP-RELEASEREQUEST

MSC server/VLR>MME

The MSC server/VLR sends this message, notifying the MME that no subsequent NAS message is to be sent to the UE.

SGsAP-ALERTREJECT

SGsAP-EPS-DETACH- MME->MSC INDICATION server/VLR

The MME sends this message to the MSC server/VLR, notifying the MSC server/VLR of the EPS detach initiated by the UE or MME.

SGsAP-EPS-DETACH- MSC server/VLRACK >MME

The MSC server sends this message in response to an SGsAP-EPS-DETACHINDICATION message.

SGsAP-IMSIMME->MSC DETACH-INDICATION server/VLR

The MME sends this message to the MSC server/VLR, notifying the MSC server/VLR of the IMSI detach initiated by the UE.

SGsAP-IMSIDETACH-ACK

MSC server/VLR>MME

The MSC server sends this message in response to an SGsAP-IMSI-DETACHINDICATION message.

MME->MSC

The MME sends this message, notifying the MSC server/VLR that TMSI allocation is

SGsAP-TMSIREALLOCATION-

COMPLETE

server/VLR

complete on the UE.

SGsAP-LOCATIONUPDATE-REQUEST

MME->MSC server/VLR

The MME sends this message to the MSC server/VLR to request a location update or IMSI attach flow.

MSC server/VLR>MME

The MSC server sends this message in response to an SGsAP-LOCATION-UPDATEREQUEST message, indicating that a location update or IMSI attach flow succeeds.

SGsAP-LOCATIONUPDATE-REJECT

MSC server/VLR>MME

The MSC server sends this message in response to an SGsAP-LOCATION-UPDATEREQUEST message, indicating that a location update or IMSI attach flow fails.

SGsAP-PAGINGREQUEST

MSC server/VLR>MME

The MSC server sends this message, instructing the MME to page a UE.

MME->MSC server/VLR

The MME sends this message in response to an SGsAP-PAGING-REQUEST message, notifying the MSC server/VLR of a failure in paging the UE.

MME->MSC server/VLR

The MSC server sends this message in response to an SGsAP-PAGING-REQUEST message, notifying the MSC server/VLR that NAS signaling connection is available between the UE and MME.

MME->MSC server/VLR

The MME sends this message in response to an SGsAP-PAGING-REQUEST message, indicating that the paging fails because the MME determines that UE is unreachable.

SGsAP-LOCATIONUPDATE-ACCEPT

SGsAP-PAGINGREJECT

SGsAP-SERVICEREQUEST

SGsAP-UEUNREACHABLE

SGsAP-STATUS

SGsAP-RESETINDICATION

MME>MSC server/VLR The MSC server/VLR or MME sends this message to indicate an error. MSC server/VLR>MME MME>MSC The MSC server/VLR or MME sends this server/VLR message, indicating that the SGs association MSC on the VLR or MME is invalid.

server/VLR>MME

SGsAP-RESET-ACK

SGsAP-SERVICEABORT-REQUEST

MSC server/VLRThe MSC server/VLR or MME sends this >MME message in response to an SGsAP-RESETMMEINDICATION message. >MSC server/VLR MSC server/VLR>MME

The MSC server/VLR sends this message, instructing the MME to terminate the fallback process during a voice call destined for the UE.

Reference Standards For details about the SGs interface protocol, see 3GPP TS 29.118. Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of the Common Part of Messages Table 1 describes information elements (IEs) contained in the common part of messages. Table 1 IEs contained in the common part of messages IE

Description

Example An SGsAP-PAGING-REQUEST message is used as an example.

Specifies the sender and receiver of a message. A message header contains the following IEs:

Message header

Message content indicator

sender-mid: Specifies the number of the BSG process that sends a message. sender-pid: Specifies the internal processing module that sends a message. receiver-mid: Specifies the number of the BSG process that receives a message. recvr-pid: Specifies the internal processing module that receives a message.

In the message: sender-mid is set to 1400, indicating that a message is sent by BSC process 1400. sender-mid is set to pidSGSAP (354), indicating that a message is sent by the SGs module. receiverMid is set to 1400, indicating that a message is received by BSC process 1400. recvrPid is set to pid-SCTP (300), indicating that a message is received by the SCTP module.

An SGsAP-PAGING-REQUEST Specifies contents in an SGs message. message is used as an example. A message content indicator contains In the message, messagetype is set to the Message Type IE. sgsap-paging-request (1), indicating that the message is an SGsAPPAGING-REQUEST message.

Parent topic: SGs Interface Protocol


Description of Associated Messages in the Alert Flow SGsAP-ALERT-REQUEST SGsAP-ALERT-ACK SGsAP-ALERT-REJECT SGsAP-UE-ACTIVITY-INDICATION Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-ALERT-REQUEST Message Function Associated IEs Reference Standards Message Function An SGs SMS message is sent to an LTE subscriber who is unreachable or does not respond to a paging request. Then, the MSC server/VLR sets the subscriber status to unreachable and sends an SGsAP-ALERT-REQUEST message to the mobility management entity (MME). The SGsAP-ALERT-REQUEST message instructs the MME to notify the MSC server/VLR when detecting signaling interaction from the LTE subscriber. After the MSC server/VLR sends the SGsAP-ALERT-REQUEST message, it starts the Waiting a Response to SGsAP-ALERT-REQUEST Timer to wait for a SGsAP-ALERTACK/SGsAP-ALERT-REJECT message from the MME. If the timer expires for the first time, the MSC server/VLR sends another SGsAP-ALERT-REQUEST message to the MME. If the timer expires again before the MSC server/VLR receives a response from the MME, the MSC server/VLR generates 4061 Waiting a Response to SGsAP-ALERT-REQUEST Timeout. The MSC server/VLR can use the measurement entity SGs Service Alert Indication Times to count the number of SGsAP-ALERT-REQUEST messages sent by the MSC server/VLR. Figure 1 shows the key information element (IE) in an SGsAP-ALERT-REQUEST message. Figure 1 Key IE in an SGsAP-ALERT-REQUEST message

Associated IEs IE

Function

Message type

Uniquely identifies a message.

IMSI

Specifies a subscriber's IMSI.

Reference Standards For details, see 8.3 "SGsAP-ALERT-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Alert Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-ALERT-ACK Message Function Associated IEs Reference Standards Message Function During an SGs SMS message sent to an LTE subscriber, the mobility management entity (MME) receives an SGsAP-ALERT-REQUEST message from the MSC server/VLR. If a subscriber's IMSI is available on the MME, the MME sends an SGsAP-ALERT-ACK message in response to the SGsAP-ALERT-REQUEST message. Then, the MME sets the Non-EPS Alert Flag (NEAF) to 1 for the subscriber. Once detecting signaling interaction from the subscriber, the MME sets NEAF to 0. After receiving the SGsAP-ALERT-ACK message, the MSC server/VLR terminates the Waiting a Response to SGsAP-ALERT-REQUEST Timer and does not modify the subscriber's SGs association state. In addition, the MSC server/VLR waits for the subscriber activity information sent by the MME. The MSC server/VLR can use the measurement entity SGs Service Alert Indication Answered Times to count the number of SGsAP-ALERT-ACK messages received by the MSC server/VLR. Figure 1 shows the key information element (IE) in an SGsAP-ALERT-ACK message. Figure 1 Key IE in an SGsAP-ALERT-ACK message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.1 "SGsAP-ALERT-ACK message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Alert Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-ALERT-REJECT Message Function Associated IEs Reference Standards Message Function During an SGs SMS message sent to an LTE subscriber, the mobility management entity (MME) receives an SGsAP-ALERT-REQUEST message from the MSC server/VLR. If a subscriber's IMSI is unavailable on the MME, the MME sends an SGsAP-ALERT-REJECT message in response to the SGsAP-ALERT-REQUEST message. After receiving the SGsAP-ALERT-REJECT message, the MSC server/VLR terminates the Waiting a Response to SGsAP-ALERT-REQUEST Timer and changes the subscriber's SGs association state to SGs-NULL. The MSC server/VLR can use the measurement entity SGs Service Alert Indication Rejected Times to count the number of SGsAP-ALERT-REJECT messages received by the MSC server/VLR. Figure 1 shows the key information element (IE) in an SGsAP-ALERT-REJECT message. Figure 1 Key IE in an SGsAP-ALERT-REJECT message

Associated IEs IE

Function

Message type


IMSI


SGs Cause

Specifies a failure cause value.

Reference Standards For details, see 8.2 "SGsAP-ALERT-REJECT message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Alert Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-UE-ACTIVITY-INDICATION Message Function Associated IEs Reference Standards Message Function The Non-EPS Alert Flag (NEAF) is set to 1 on the mobility management entity (MME) for a subscriber. When the MME detects signaling interaction from the subscriber, and the MSC server/VLR does not participate in the signaling interaction, the MME sends an SGsAP-UEACTIVITY-INDICATION message to the MSC server/VLR and sets NEAF to 0. Figure 1 shows the key information elements (IEs) in an SGsAP-UE-ACTIVITY-INDICATION message. NOTE: If the MSC server/VLR participates in the signaling interaction detected by the MME, the MME sets NEAF to xx and does not send an SGsAP-UE-ACTIVITY-INDICATION message to the MSC server/VLR. The MSC server/VLR can use the measurement entity UE Active Times to count the number of SGsAP-UE-ACTIVITY-INDICATION messages received by the MSC server/VLR. Figure 1 shows the key information element (IE) in an SGsAP-UE-ACTIVITY-INDICATION message. Figure 1 Key IEs in an SGsAP-UE-ACTIVITY-INDICATION message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.20 "SGsAP-UE-ACTIVITY-INDICATION message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Alert Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages in SMS SGsAP-UPLINK-UNITDATA SGsAP-DOWNLINK-UNITDATA SGsAP-RELEASE-REQUEST Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-UPLINK-UNITDATA Message Function Associated IEs Reference Standards Message Function During an SGs SMS message, VLR-Reliable is not set to false in the MM context variable on the mobility management entity (MME). When the MME receives an Uplink NAS Transport message from the equipment (UE), the MME derives the NAS message container from the Uplink NAS Transport message and adds the derived information to an SGsAP-UPLINK-UNITDATA message sent to the MSC server/VLR. To ensure that the MSC server/VLR correctly generates call detail records (CDRs), the SGsAP-UPLINK-UNITDATA message also includes the IMEISV, UE Time Zone, Mobile Station Classmark 2, TAI, and ECGI IEs. The MSC server/VLR can use the measurement entity Number of Uplink Unitdata Message Received by MSC to count the number of SGsAP-UPLINK-UNITDATA messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-UPLINK-UNITDATA message. Figure 1 Key IEs in an SGsAP-UPLINK-UNITDATA message

Associated IEs

IE

Function

Message type


IMSI


NAS message container

Specifies SMS message contents.

IMEISV

Specifies the software version of an international mobile terminal. This IE is optional.

UE Time Zone

Specifies the offset between Greenwich Mean Time (GMT) and local time. This IE is optional.


Specifies the priority information of a mobile terminal. This IE is optional.

TAI

Uniquely identities a tracking area (TA). This IE is optional.

E-CGI

Uniquely identities cell on an LTE network. This IE is optional.

Reference Standards For details, see 8.22 "SGsAP-UPLINK-UNITDATA message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in SMS Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-DOWNLINK-UNITDATA Message Function Associated IEs Reference Standards Message Function During an SGs SMS message, if the equipment (UE) is in the SGs-ASSOCIATED or LA-UPDATE-PRESENT state, the MSC server sends an SGsAP-DOWNLINK-UNITDATA message containing the NAS message to be sent to the UE to the mobility management entity (MME). The MSC server/VLR can use the measurement entity Number of Downlink Unitdata Message Sent by MSC to count the number of SGsAP-DOWNLINK-UNITDATA messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-DOWNLINK-UNITDATA message. Figure 1 Key IEs in an SGsAP-DOWNLINK-UNITDATA message

Associated IEs IE

Function

Message type


IMSI



Specifies SMS message contents.

Reference Standards

For details, see 8.4 "SGsAP-DOWNLINK-UNITDATA message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in SMS Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-RELEASE-REQUEST Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-RELEASE-REQUEST message to the mobility management entity (MME) in either of the following scenarios: The MSC server detects that it does not have NAS signaling interaction with the equipment (UE), for example, because the SGs SMS is complete. The MSC server cannot continue exchanging NAS signaling interaction with the UE due to a fault, for example, the SGs association information or IMSI is unavailable. Figure 1 shows the key information elements (IEs) in an SGsAP-RELEASE-REQUEST message. Figure 1 Key IEs in an SGsAP-RELEASE-REQUEST message

Associated IEs IE

Function

Message type


IMSI


SGs cause

Specifies a failure cause value. This IE is optional.

Reference Standards For details, see 8.23 "SGsAP-RELEASE-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in SMS


Description of Associated Messages in Location Updates SGsAP-EPS-DETACH-INDICATION SGsAP-EPS-DETACH-ACK SGsAP-IMSI-DETACH-INDICATION SGsAP-IMSI-DETACH-ACK SGsAP-TMSI-REALLOCATION-COMPLETE SGsAP-LOCATION-UPDATE-REQUEST SGsAP-LOCATION-UPDATE-ACCEPT SGsAP-LOCATION-UPDATE-REJECT Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-EPS-DETACH-INDICATION Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-EPS-DETACH-INDICATION message, notifying the MSC server/VLR that the equipment (UE)/MME has initiated an evolved packet system (EPS) detach. The MSC server/VLR can use the measurement entity EPS Detached Times to count the number of SGsAP-EPS-DETACH-INDICATION messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-EPS-DETACHINDICATION message. Figure 1 Key IEs in an SGsAP-EPS-DETACH-INDICATION message

Associated IEs IE

Function

Message type


IMSI


MME name

Specifies the domain name of an MME.

IMSI detach from EPS service type

Specifies how a subscriber is detached from EPS services.

Reference Standards

For details, see 8.6 "SGsAP-EPS-DETACH-INDICATION message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-EPS-DETACH-ACK Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-EPS-DETACH-ACK message in response to an SGsAP-EPS-DETACH-INDICATION message sent by the mobility management entity (MME). After receiving an SGsAP-EPS-DETACH-INDICATION message: If a subscriber's SGs association information is unavailable in the VLR, the MSC server/VLR directly sends an SGsAP-EPS-DETACH-ACK message to the MME. If a subscriber's SGs association information is available in the VLR, the MSC server/VLR first deletes the subscriber's SGs association information and then sends an SGsAP-EPS-DETACH-ACK message to the MME. The MSC server/VLR can use the measurement entity EPS Detached Answer Times to count the number of SGsAP-EPS-DETACH-ACK messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-EPS-DETACH-ACK message. Figure 1 Key IEs in an SGsAP-EPS-DETACH-ACK message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.5 "SGsAP-EPS-DETACH-ACK message" in 3GPP TS 29.118 V11.3.0.

Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-IMSI-DETACH-INDICATION Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-IMSI-DETACH-INDICATION message, notifying the MSC server/VLR that the equipment (UE) has initiated an IMSI detach. The MSC server/VLR can use the measurement entity IMSI Detached Times to count the number of SGsAP-IMSI-DETACH-INDICATION messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-IMSI-DETACHINDICATION message. Figure 1 Key IEs in an SGsAP-IMSI-DETACH-INDICATION message

Associated IEs IE

Function

Message type


IMSI


MME name


IMSI detach from non-EPS service type

Specifies how a subscriber is detached from non-evolved packet system (EPS) services.

Reference Standards For details, see 8.8 "SGsAP-IMSI-DETACH-INDICATION message" in 3GPP TS 29.118

V11.3.0. Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-IMSI-DETACH-ACK Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-IMSI-DETACH-ACK message in response to an SGsAP-IMSI-DETACH-INDICATION message sent by the mobility management entity (MME). After receiving the SGsAP-IMSI-DETACH-INDICATION message: If a subscriber's SGs association information is unavailable in the VLR, the MSC server/VLR directly sends an SGsAP-IMSI-DETACH-ACK message. If a subscriber's SGs association information is available in the VLR, the MSC server/VLR first deletes the subscriber's SGs association information and then sends an SGsAP-IMSI-DETACH-ACK message to the MME. The MSC server/VLR can use the measurement entity IMSI Detached Answer Times to count the number of SGsAP-IMSI-DETACH-ACK messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-IMSI-DETACH-ACK message. Figure 1 Key IEs in an SGsAP-IMSI-DETACH-ACK message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.7 "SGsAP-IMSI-DETACH-ACK message" in 3GPP TS 29.118 V11.3.0.

Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-TMSI-REALLOCATION-COMPLETE Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-LOCATION-UPDATE-ACCEPT message containing a new TMSI allocated by the MSC server/VLR to the mobility management entity (MME). After the MME receives an ATTACH COMPLETE or TRACKING AREA UPDATE COMPLETE message from the equipment (UE), the MME sends an SGsAP-TMSIREALLOCATION-COMPLETE message, notifying the MSC server/VLR that the UE has completed the TMSI allocation flow. The MSC server/VLR can use the measurement entity TMSI Reallocation Complete Times to count the number of SGsAP-TMSI-REALLOCATION-COMPLETE messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-TMSI-REALLOCATIONCOMPLETE message. Figure 1 Key IEs in an SGsAP-TMSI-REALLOCATION-COMPLETE message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.19 "SGsAP-TMSI-REALLOCATION-COMPLETE message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in Location Updates


SGsAP-LOCATION-UPDATE-REQUEST Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-LOCATION-UPDATE-REQUEST message, notifying the MSC server/VLR that the equipment (UE) requests for a location update or IMSI attach flow. The MSC server/VLR can use the measurement entity Update Location Times to count the number of SGsAP-LOCATION-UPDATE-REQUEST messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-LOCATION-UPDATEREQUEST message. Figure 1 Key IEs in an SGsAP-LOCATION-UPDATE-REQUEST message

Associated IEs IE

Function

Message type


IMSI


MME name


EPS location update type

Specifies whether the UE has performed the IMSI attach flow or common location update.

New location area identifier

Identifies the new location area (LA) in which the UE is located.

Old location area identifier

Identifies the original LA in which the UE is located. This IE is optional.

TMSI status

Specifies whether the UE has a valid TMSI. This IE is optional.

IMEISV


TAI


E-CGI

Uniquely identities cell on an LTE network. This IE is optional.

Reference Standards For details, see 8.11 "SGsAP-LOCATION-UPDATE-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-LOCATION-UPDATE-ACCEPT Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-LOCATION-UPDATE-ACCEPT message, notifying the MME that a location update or IMSI attach flow is complete. If the MSC server/VLR s TMSI allocation, it includes the location area identity (LAI) and a new TMSI in the SGsAP-LOCATION-UPDATE-ACCEPT message. If the MSC server/VLR does not TMSI allocation, it includes the LAI and IMSI in the SGsAP-LOCATION-UPDATE-ACCEPT message. The MSC server/VLR can use the measurement entity Update Location Accepted Times to count the number of SGsAP-LOCATION-UPDATE-ACCEPT messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-LOCATION-UPDATEACCEPT message. Figure 1 Key IEs in an SGsAP-LOCATION-UPDATE-ACCEPT message

Associated IEs IE

Function

Message type


IMSI


Location area identifier

Identifies the location area (LA) in which the UE is located.

New TMSI, or IMSI

Identifies a subscriber. This IE is optional.

Reference Standards For details, see 8.9 "SGsAP-LOCATION-UPDATE-ACCEPT message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-LOCATION-UPDATE-REJECT Message Function Associated IEs Reference Standards Message Function If the MSC server rejects a location update request after receiving a SGsAP-LOCATIONUPDATE-REQUEST message from the mobility management entity (MME), the MSC server sends an GsAP-LOCATION-UPDATE-REJECT message containing the Reject cause IE, notifying the MME that the location update or IMSI attach flow fails. Then, the MSC server/VLR sets the UE's SGs association state to SGs-NULL. The MSC server/VLR can use the measurement entity Update Location Rejected Times to count the number of SGsAP-LOCATION-UPDATE-REJECT messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-LOCATION-UPDATEREJECT message. Figure 1 Key IEs in an SGsAP-LOCATION-UPDATE-REJECT message

Associated IEs IE

Function

Message type


IMSI


Reject cause

Specifies a cause value used by the MSC server/VLR to reject a service request sent by the UE.


Identifies the location area (LA) in which the UE is located. This IE is optional.

Reference Standards For details, see 8.10 "SGsAP-LOCATION-UPDATE-REJECT message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in Location Updates Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages in the Paging Flow SGsAP-PAGING-REQUEST SGsAP-PAGING-REJECT SGsAP-SERVICE-REQUEST SGsAP-UE-UNREACHABLE Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-PAGING-REQUEST Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-PAGING-REQUEST message, instructing the mobility management entity (MME) to page a equipment (UE). The MSC server/VLR can use the measurement entity SGs Interface Paging Message Times to count the number of SGsAP-PAGING-REQUEST messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-PAGING-REQUEST message. Figure 1 Key IEs in an SGsAP-PAGING-REQUEST message

Associated IEs IE

Function

Message type


IMSI


VLR name

Specifies the domain name of a VLR.

Service indicator

Specifies the CS service type.

TMSI

Specifies a subscriber's TMSI. This IE is optional.

CLI

Identifies a calling number in a circuit switched (CS) mobile terminated (MT) call. This IE is optional.


Identifies the location area (LA) in which the UE is located. This IE is optional.

Global CN-Id

Identifies a core network (CN) node. This IE is optional.

LCS indicator

Specifies that the origin of the message is due to a location service (LCS) request and the type of this request. This IE is optional.

LCS client identity

Specifies the information about the client that sends an LCS request. This IE is optional.

Channel needed

Specifies the type of the channel that is required for the paging flow. This IE is optional.

eMLPP Priority

Specifies the call priority information. This IE is optional.

Additional paging indicators

Specifies the additional information during the paging flow. This IE is optional.

Reference Standards For details, see 8.14 "SGsAP-PAGING-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Paging Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-PAGING-REJECT Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-PAGING-REJECT message, notifying the MSC server/VLR that the paging flow fails. The MSC server/VLR can use the measurement entity SGs Interface Paging Message Rejected Times to count the number of SGsAP-PAGING-REJECT messages received by the MME. Figure 1 shows the key information elements (IEs) in an SGsAP-PAGING-REJECT message.

Figure 1 Key IEs in an SGsAP-PAGING-REJECT message Associated IEs IE

Function

Message type


IMSI


SGs Cause


Reference Standards For details, see 8.13 "SGsAP-PAGING-REJECT message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Paging Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-SERVICE-REQUEST Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-SERVICE-REQUEST message in response to an SGsAP-PAGING-REQUEST message, notifying the MSC server/VLR that NAS signaling connection is available between the equipment (UE) and MME, or NAS signaling connection has been established after paging is complete. After the MME receives an SGsAP-PAGING-REQUEST message: If the UE is in the EMM-CONNECTED state, the MME directly sends an SGsAPSERVICE-REQUEST message to the MSC server/VLR. If the UE is in the MM-IDLE state, the MME does not send an SGsAP-SERVICEREQUEST message to the MSC server/VLR until the UE is in the EMMCONNECTED state. The service indicators contained in SGsAP-SERVICE-REQUEST and SGsAP-PAGINGREQUEST messages must be the same. To ensure that the MSC server/VLR correctly generates call detail records (CDRs), the SGsAP-SERVICE-REQUEST message also includes IMEISV, UE Time Zone, Mobile Station Classmark 2, TAI, and E-CGI. The MSC server/VLR can use the measurement entity SGs Interface Paging Answered Times to count the number of SGsAP-SERVICE-REQUEST messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-SERVICE-REQUEST message. Figure 1 Key IEs in an SGsAP-SERVICE-REQUEST message

Associated IEs IE

Function

Message type


IMSI


Service indicator

Specifies the CS service type.

IMEISV


UE Time Zone

Specifies the offset between Greenwich Mean Time (GMT) and local time. This IE is optional.


Specifies the priority information of a mobile terminal. This IE is optional.

TAI


E-CGI

Uniquely identities cell on an LTE network. This IE is optional. Specifies a subscriber's evolved packet

UE EMM Mode

system mobility management (EMM) state. This IE is optional.

Reference Standards For details, see 8.17 "SGsAP-SERVICE-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Paging Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-UE-UNREACHABLE Message Function Associated IEs Reference Standards Message Function The mobility management entity (MME) sends an SGsAP-UE-UNREACHABLE message, notifying the MSC server/VLR that the paging flow fails because the MME determines that the equipment (UE) is unreachable. The MSC server/VLR can use the measurement entity MME Returning Subscriber Unreachable Times to count the number of SGsAP-UE-UNREACHABLE messages received by the MME. Figure 1 shows the key information elements (IEs) in an SGsAP-UE-UNREACHABLE message. Figure 1 Key IEs in an SGsAP-UE-UNREACHABLE message

Associated IEs IE

Function

Message type


IMSI


SGs cause


Reference Standards For details, see 8.21 "SGsAP-UE-UNREACHABLE message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Paging Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages in the Fault Processing Flow SGsAP-STATUS Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-STATUS Message Function Associated IEs Reference Standards Message Function The MSC server/VLR or mobility management entity (MME) sends an SGsAP-STATUS message when an error occurs. For details about when the MSC server/VLR sends an SGsAP-STATUS message to the MME, see the description in 4038 SGsAP-STATUS Message Sent by MSC. For details about when the MME sends an SGsAP-STATUS message to the MSC server/VLR, see the description in 4039 SGsAP-STATUS Message Received by MSC. The MSC server/VLR can use the measurement entity Number of SGsAP-STATUS Message Send by MSC to count the number of SGsAP-STATUS messages sent by the MSC server/VLR and use the measurement entity Number of SGsAP-STATUS Message Received by MSC to count the number of SGsAP-STATUS messages received by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-STATUS message.

Figure 1 Key IEs in an SGsAP-STATUS message Associated IEs IE

Function

Message type


IMSI

Specifies a subscriber's IMSI. This IE is optional.

SGs cause


Erroneous message

Specifies the error information.

Reference Standards

For details, see 8.18 "SGsAP-STATUS message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Fault Processing Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages in the Reset Flow SGsAP-RESET-INDICATION SGsAP-RESET-ACK Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-RESET-INDICATION Message Function Associated IEs Reference Standards Message Function An SGsAP-RESET-INDICATION message is sent in either of the following scenarios: When the VLR restarts and bit 0 of P448 is set to 1, the MSC server/VLR sends an SGsAP-RESET-INDICATION message, notifying all interworking mobility management entities (MMEs) that the SGs association information of subscribers who with the VLR is unreliable. After sending the SGsAP-RESET-INDICATION message, the MSC server/VLR starts the TN_WAIT_FOR_RESET_ACK timer to wait for an SGsAP-RESET-ACK message from the MME. When the MME recovers from a fault, it sends an SGsAP-RESET-INDICATION message, notifying the MSC server/VLR that the SGs association information of subscribers who with the MME is unreliable. After receiving the SGsAP-RESET-INDICATION message, the MSC server/VLR generates 4040 SGsAP-RESET-INDICATION or SGsAP-RESET-ACK Message Received by VLR. The MSC server/VLR can use the measurement entity Number of Sent SGsAP-RESETINDICATION Messages to count the number of SGsAP-RESET-INDICATION messages sent by the MSC server/VLR and use the measurement entity Number of Received SGsAPRESET-INDICATION Messages to count the number of SGsAP-RESET-INDICATION messages received by the MSC server/VLR. An indicator in an SGsAP-RESET-INDICATION message can specify whether the MSC server/VLR or MME sends the message. Figure 1 shows the key IEs in an SGsAP-RESETINDICATION message. Figure 1 Key IEs in an SGsAP-RESET-INDICATION message

Associated IEs IE

Function

Message type


MME name

Specifies the domain name of an MME. This IE is optional.

VLR name

Specifies the domain name of a VLR. This IE is optional.

Reference Standards For details, see 8.16 "SGsAP-RESET-INDICATION message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Reset Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-RESET-ACK Message Function Associated IEs Reference Standards Message Function An SGsAP-RESET-ACK message is sent in either of the following scenarios: When the VLR restarts, the MSC server/VLR sends an SGsAP-RESETINDICATION message to all interworking mobility management entities (MMEs). Then, the MME sends an SGsAP-RESET-ACK message, notifying that the SGs association information of subscribers who with the VLR is set to unreliable on the MME. After receiving the SGsAP-RESET-ACK message, the MSC server/VLR generates 4040 SGsAP-RESET-INDICATION or SGsAP-RESET-ACK Message Received by VLR. When the MME recovers from a fault, it sends an SGsAP-RESET-INDICATION message. Then, the MSC server/VLR sends an SGsAP-RESET-ACK message, notifying the MME that the SGs association information of subscribers who with the MME is set to unreliable on the MSC server/VLR. After sending the SGsAP-RESET-ACK message, the MSC server/VLR generates 4040 SGsAPRESET-INDICATION or SGsAP-RESET-ACK Message Received by VLR. The MSC server/VLR can use the measurement entity Number of Sent SGsAP-RESETACK Messages to count the number of SGsAP-RESET-ACK messages sent by the MSC server/VLR and use the measurement entity Number of Received SGsAP-RESET-ACK Messages to count the number of SGsAP-RESET-ACK messages received by the MSC server/VLR. An indicator in an SGsAP-RESET-ACK message can specify whether the MSC server/VLR or MME sends the message. Figure 1 shows the key IEs in an SGsAP-RESETINDICATION message sent by the MME. Figure 1 Key IEs in an SGsAP-RESET-ACK message sent by the MME

Associated IEs

IE

Function

Message type


MME name

Specifies the domain name of an MME. This IE is optional.

VLR name

Specifies the domain name of a VLR. This IE is optional.

Reference Standards For details, see 8.15 "SGsAP-RESET-ACK message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Reset Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated Messages in the Service Abort Flow SGsAP-SERVICE-ABORT-REQUEST Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGsAP-SERVICE-ABORT-REQUEST Message Function Associated IEs Reference Standards Message Function The MSC server/VLR sends an SGsAP-SERVICE-ABORT-REQUEST message, instructing the mobility management entity (MME) to stop the fallback flow and retain the SGs association state when the calling party releases a voice call or supplementary service before the called party is alerted in either of following scenarios: The MSC server/VLR has sent an SGsAP-PAGING-REQUEST message to the MME but has not received an SGsAP-SERVICE-REQUEST message from the MME. The MSC server/VLR has received an SGsAP-SERVICE-REQUEST message from the MME after sending an SGsAP-PAGING-REQUEST message, but the UE has not performed a location update on a CS network or not responded to the paging request. NOTE: Bit 2 of P1180 determines whether the MSC server/VLR can send SGsAP-SERVICEABORT-REQUEST messages to the MME. The MSC server/VLR can use the measurement entity Number of Sent SGsAP-SERVICEABORT-REQUEST Messages to count the number of SGsAP-SERVICE-ABORTREQUEST messages sent by the MSC server/VLR. Figure 1 shows the key information elements (IEs) in an SGsAP-SERVICE-ABORTREQUEST message. Figure 1 Key IEs in an SGsAP-SERVICE-ABORT-REQUEST message

Associated IEs IE

Function

Message type


IMSI


Reference Standards For details, see 8.24 "SGsAP-SERVICE-ABORT-REQUEST message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated Messages in the Service Abort Flow Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Description of Associated IEs Additional paging indicators Channel needed CLI E-CGI eMLPP priority EPS location update type Erroneous message Global CN-Id IMEISV IMSI IMSI detach from EPS service type IMSI detach from non-EPS service type LCS client identity LCS indicator Location area identifier Message Type MME Name Mobile Station Classmark 2 NAS message container New location area identifier New TMSI, or IMSI Old location area identifier Reject cause Service indicator SGs Cause TAI

TMSI TMSI status UE EMM Mode UE Time Zone VLR name Parent topic: SGs Interface Protocol Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Additional paging indicators Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies the addition information, such as the CSRI indicator, during the paging flow. Value:

Additional paging indicators

0: CS restoration indicator (CSRI) is not set An SGsAP-PAGING-REQUEST 1: CS restoration indicator (CSRI) is set message is used as an example. In the message, csriIf the MSC server is required to enum-value is set to csri-is-set send additional information, such (1), indicating that data as the CSRI indicator, to the restoration is required. mobility management entity (MME) during the paging flow, the MSC server must include the Additional paging indicators IE in an SGsAP-PAGING-REQUEST message.

Reference Standards For details, see 9.4.25 "Additional paging indicators" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Channel needed Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies the type of the channel that is required for the paging flow. If the MSC server/VLR is required to notify the UE of the required channel type, the MSC server/VLR must include this IE in an SGsAP-PAGINGREQUEST message. Bit 0 of P1180 determines whether the MSC server/VLR includes the Channel needed IE in an SGsAP-PAGING-REQUEST message. If the SGsAPPAGING-REQUEST message does not contain the Channel needed IE, the channel type used by the UE is Any channel by default. Value: Channel needed

0: Any channel 1: SDCCH 2: TCH/F (Full rate) 3: TCH/H or TCH/F (Dual rate) Bit 1 of P1180 determines how the MSC server/VLR completes the Channel needed IE. When bit 1 of P1180 is set to 0, the MSC server/VLR sets the Channel needed IE to

An SGsAP-PAGING-REQUEST message is used as an example. In the message, channel-needed-value is set to E1, indicating that the channel type is SDCCH.

TCH/H or TCH/F (Dual rate). When bit 1 of P1180 is set to 1, the MSC server/VLR sets the Channel needed IE to TCH/F (Full rate). Reference Standards For details, see 9.4.23 "Channel needed" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

CLI Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Specifies a calling number in a circuit switched (CS) mobile terminated (MT) call. If the MSC server implements the calling line identification presentation (CLIP) service, the MSC server must include the CLI IE in an SGsAPPAGING-REQUEST message. The CLI IE consists of the mandatory parameter Calling party BCD number information and optional parameters Calling party subaddress and Cause. Calling party BCD number information species the call source. This parameter consists of the following parts: Type of number 0: unknown 1: international number 2: national number 3: network specific number 4: dedicated access, short code

Other values: Reserved Numbering plan identification Calling line identification (CLI)

0: unknown 1: ISDN/telephony numbering plan 3: data numbering plan 4: telex numbering plan 8: national numbering plan 9: private numbering plan Other values: Reserved Presentation indicator 0: Presentation allowed 1: Presentation restricted 2: Number not available due to interworking 3: Reserved Screening indicator 0: provided. not screened 1: provided, verified and ed 2: provided, verified and failed

An SGsAP-PAGING-REQUEST message is used as an example. In the message: type-of-number is set to nationalnumber (2), indicating that the calling number is a national number. numbering-plan-identification is set to isdn-telephony-numberingplan (1), indicating that numbering plan is ISDN/Telephony numbering plan. presentat-indicator is set to Presentation allowed (0), indicating that a calling number can be displayed on called party's mobile terminal. screening-indicator is set to network-provided, indicating that the screening indicator is provided by the network.

3: Network provided Reference Standards For details, see 9.4.1 "CLI" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

E-CGI Description of the IE Reference Standards Description of the IE Information Element (IE)

E-UTRAN Cell Global Identity (ECGI)

Description

Example

Uniquely identifies the E-UTRAN where the subscriber locates. The An SGsAP-SERVICE-REQUEST E-CGI IE contains the PLMN ID message is used as an example. and cell ID. In the message, plmn specifies the ID of PLMN to which a subscriber belongs, and eci identifies the cell where the subscriber locates.

Reference Standards For details, see 9.4.3a "E-UTRAN Cell Global Identity" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

eMLPP priority Description of the IE Reference Standards Description of the IE Information Element (IE)

eMLPP priority (enhanced Multi-Level Precedence and Preemption)

Description

Example

Specifies the call priority information. If the MSC server/VLR can process priority information during Circuit Switched Fallback (CSFB) calls and the MSC server/VLR has received a call request containing the priority information, the MSC server/VLR must include the eMLPP priority IE in an SGsAPPAGING-REQUEST message. Bit 0 of P1156 determines An SGsAP-PAGING-REQUEST whether the MSC server/VLR message is used as an includes the eMLPP priority IE in example. In the message, callan SGsAP-PAGING-REQUEST Priority is set to call-prioritymessage. level-1 (4), initiating that the call priority is 1. Value: 0: 1: 2: 3: 4: 5: 6: 7:

no priority applied call priority level 4 call priority level 3 call priority level 2 call priority level 1 call priority level 0 call priority level B call priority level A

Reference Standards For details, see 9.4.24 "eMLPP priority" in 3GPP TS 29.118 V11.3.0.


EPS location update type Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Species which flow a mobile terminal performs as instructed by the MSC server. Value: EPS location update type

An SGsAP-LOCATION-UPDATEREQUEST message is used as an 1: IMSI attach 2: Normal location example. In the message, eps-location-updateupdate Other values: The type is set to normal-location-update (2), indicating that the mobile terminal mobile terminal performs a common location update. performs a common location update.

Reference Standards For details, see 9.4.2 "EPS location update type" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Erroneous message Description of the IE Reference Standards Description of the IE Information Element Description Example (IE)

Erroneous message

Specifies the error information. This IE is in the typeAn SGsAP-STATUS message is used as an example. length-value (TLV) format.

Reference Standards For details, see 9.4.3 "Erroneous message" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Global CN-Id Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Global CN-Id

Identifies a core network (CN) node. The Global CN-Id IE consists of PLMN ID and CN ID. The PLMN ID consists of the mobile country code (MCC) and mobile network code (MNC). An SGsAP-PAGING-REQUEST The MSC server must include message is used as an this IE in an SGsAP-PAGINGexample. In the message: REQUEST message when a Values of mcc-dig-2, radio access network (RAN) is mcc-dig-1, and mccconnected to multiple MSC dig-3 specify the MCC. servers and the MSC server Values of mnc-dig-3, uses an IMSI to page a mnc-dig-2, and mncsubscriber. Whether the MSC dig-1 specify the MNC. server includes the Global CN-Id IE in an SGsAP-PAGINGThe value of cn-id REQUEST message is specifies the CN ID of determined by bit 2 of P1156. an MSC server.

Example

Reference Standards For details, see 9.4.4 "Global CN-Id" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IMEISV Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies the software version of an international mobile terminal.

IMEISV

If a mobility management entity (MME) s the Automatic Device Detection (ADD) function, the MME must include the IMEISV IE in an An SGsAP-SERVICESGsAP-LOCATIONREQUEST message is used as UPDATE-REQUEST an example. message. If the MME can obtain imeisv is set to IMEISV information, it 000000000000000, indicating includes the IMEISV IE the software version of an in SGsAP-SERVICE- international mobile terminal. REQUEST and SGsAP-UPLINKUNITDATA messages sent to the MSC server, ensuring that the MSC server correctly generates call detail records (CDRs) during calls.

Reference Standards For details, see 9.4.5 "IMEISV" in 3GPP TS 29. 118 V11.3.0.


IMSI Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Identifies an international mobile subscriber. The IMSI IE contains the following parameters: type-of-identity: Specifies the identity used to identify a subscriber.

IMSI

1: IMSI 2: IMEI 3: IMEISV 4: TMSI/PTMSI/MTMSI 5: TMGI and optional MBMS Session Identity 0: No An SGsAP-SERVICE-REQUEST Identity message is used as an example. In the message: Other values: type-of-identity is set to Reserved iMSI (1), indicating that an IMSI is used to identify a odd-or-even-indic: mobile subscriber. Specifies whether the IMSI length is an even odd-or-even-indic is set to or odd number. odd-number-of-identitydigits (1), indicating that 0: even the IMSI length is an odd number of

identity digits and also when the TMSI/PTMSI or TMGI and optional MBMS Session Identity is used 1: odd number of identity digits

number. imsi-body is set to 470011159200555 that is the subscriber's IMSI.

imsi-body: Specifies an IMSI. Reference Standards For details, see 9.4.6 "IMSI" in 3GPP TS 29.118 V11.3.0 and 10.5.1.4 "Mobile Identity" in 3GPP TS 24.008 V12.2.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

IMSI detach from EPS service type Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Specifies how a subscriber is detached from an evolved packet system (EPS) service. Value:

IMSI detach from EPS service type

1: Network initiated IMSI detach from An SGsAP-EPS-DETACH-INDICATION message is used as EPS an example. In the message, imsi-detach-from-eps-serviceservices type-value specifies how a subscriber is detached from an 2: UE EPS service. initiated IMSI detach from EPS services 3: EPS services not allowed

Reference Standards For details, see 9.4.7 "IMSI detach from EPS service type" in 3GPP TS 29.118 V11.3.0.


IMSI detach from non-EPS service type Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Species how a subscriber is detached from a non-evolved packet system (EPS) service.

IMSI detach from nonEPS service type

1: Explicit UE initiated IMSI detach from nonEPS services 2: An SGsAP-IMSI-DETACH-REQUEST message is used as Combined an example. UE In the message, imsi-detach-from-non-eps-service-type is initiated set to Implicit network initiated IMSI detach from EPS and IMSI non-EPS services, indicating that a subscriber performs an detach implicit attach from a non-EPS service. from EPS and nonEPS services 3: Implicit network initiated IMSI detach from EPS and non-

EPS services Reference Standards For details, see 9.4.8 "IMSI detach from non-EPS service type" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

LCS client identity Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Species identity information of the client that sends an LCS request. This IE is a compound parameter.

Location service (LCS) client identity

During the MT LCS service, the MSC server can include this IE in an SGsAPPAGINGAn SGsAP-PAGING-REQUEST message is REQUEST used as an example. In the message, lcsmessage, depending on the client-identity-value species identity setting of bit 3 of information of the client that sends an LCS request. P698. During the LCS service in emergency calls, the MSC server must include this IE in an SGsAPPAGINGREQUEST message.

Reference Standards For details, see 9.4.9 "LCS client identity" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs


LCS indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies whether a message is sent during the LCS service. Value:

Location service (LCS) indicator

1: MT-LR Other values: Undefined by the protocol The MSC server must include this IE during the MT LCS service in an SGsAP-PAGINGREQUEST message. Bit 3 of P698 determines whether the MSC server includes the LCS indicator in an SGsAP-PAGINGREQUEST message during the MT LCS service.

An SGsAP-PAGING-REQUEST message is used as an example. In the message, lcsindicator-value is set to MT-LR (1), indicating that the message is sent during the MT LCS service.

Reference Standards For details, see 9.4.10 "LCS indicator" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Location area identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

An SGsAP-LOCATIONUPDATE-ACCEPT message is used as an example.


Uniquely identifies a location area (LA). The Location area identifier IE consists of the mobile country code (MCC), mobile network code (MNC), and location area code (LAC).

In the message: Values of mcc-dig-1, mcc-dig-2, and mccdig-3 specify the MCC. Values of mnc-dig-3, mnc-dig-1, and mncdig-2 specify the MNC. The value of lac specifies the LAC.

Reference Standards For details, see 9.4.11 "Location area identifier" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


Description

Example

Specifies the message sent over the SGs interface. Value:

Message Type

Unassigned: Unknown message type 1: SGsAP-PAGINGREQUEST 2: SGsAP-PAGINGREJECT 6: SGsAP-SERVICEREQUEST 7: SGsAPDOWNLINK-UNITDATA 8: SGsAP-UPLINKUNITDATA 9: SGsAP-LOCATIONUPDATE-REQUEST 10: SGsAPLOCATION-UPDATEACCEPT 11: SGsAPLOCATION-UPDATEREJECT 12: SGsAP-TMSIREALLOCATIONCOMPLETE 13: SGsAP-ALERTREQUEST 14: SGsAP-ALERTIn a message, messagetype is ACK

set to sgsap-alert-request (13), 15: SGsAP-ALERTindicating that an SGsAPREJECT ALERT-REQUEST message is 16: SGsAP-UEsent over the SGs interface. ACTIVITYINDICATION 17: SGsAP-EPSDETACH-INDICATION 18: SGsAP-EPSDETACH-ACK 19: SGsAP-IMSIDETACH-INDICATION 20: SGsAP-IMSIDETACH-ACK 21: SGsAP-RESETINDICATION 22: SGsAP-RESETACK 23: SGsAP-SERVICEABORT-REQUEST 26: SGsAP-MMINFORMATIONREQUEST 27: SGsAP-RELEASEREQUEST 29: SGsAP-STATUS 31: SGsAP-UEUNREACHABLE Reference Standards For details, see 9.2 "Message type" in 3GPP TS 29. 118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

MME Name Description of the IE Reference Standards Description of the IE Information Element Description (IE) Mobility management Species the domain name of an MME. An SGsAP-SERVICE-UPDATE-REQUEST message is used as an example. entity (MME) name Reference Standards For details, see 9.4.13 "MME name" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Mobile Station Classmark 2 Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Specifies the priority information of a subscriber, based on which the MSC server decides how to process subscriber's operations. If the MME can obtain Mobile Station Classmark 2 information, it includes the Mobile Station Classmark 2 IE in SGsAP-SERVICEREQUEST and SGsAPUPLINK-UNITDATA messages sent to the MSC server, ensuring that the MSC server correctly generates call detail records (CDRs) during calls. The Mobile Station Classmark 2 IE contains the following parameters: Revision level Value: 0: Reserved for GSM phase 1 1: Used by GSM phase 2

mobile stations 2: Used by mobile stations ing R99 or later versions of the protocol 3: Reserved for future use NOTE: Revision level 3 is the highest priority. ES IND: Specifies whether a mobile terminal implements the "Controlled Early Classmark Sending" operation. 0: The mobile terminal does not implement the "Controlled Early Classmark Sending" operation. 1: The mobile terminal implements the

"Controlled Early Classmark Sending" operation. A5/1 0: encryption algorithm A5/1 available 1: encryption algorithm A5/1 not available RF Power Capability PS capability (pseudosynchronization capability) 0: PS capability not present 1: PS capability present Supplementary Service Screening Indicator 0: default value of phase 1 1: capability of handling of ellipsis notation and phase 2 error

handling Other values: Reserved SM capability (MT SMS pt to pt capability)


0: The mobile terminal station does not mobile terminated (MT) pointto-point SMS messages. 1: The mobile An SGsAP-SERVICE-REQUEST message is terminal used as an example. In the message: s revision-level is set to used-by-mobileMT pointstations-ing-R99-or-laterto-point versions-of-the-protocol (2), indicating SMS that he UE s R99 or later. messages. es-ind is set to 1, indicating that the UE Voice Broadcast implements the "Controlled Early Service (VBS) Classmark Sending" operation. notification reception a5-1 and a5-2 are set to 0, indicating 0: No VBS that the UE does not A5/1 or capability A5/2 encryption algorithm. a5-3 is set or to 1, indicating that the UE s notification A5/3 encryption algorithm. is required. rf-power-capability is set to 7, 1: VBS indicating that the radio frequency capabilities capability is not involved. and ss-screening-indicator is set to 1, notifications indicating "capability of handling of are ellipsis notation and phase 2 error required. handling" is ed.

Voice Group Call Service (VGCS) notification reception 0: No VGCS capability or notification is required. 1: VGCS capabilities and notifications are required. FC Frequency Capability 0: The mobile terminal does not the E-GSM or R-GSM band. 1: The mobile terminal s the E-GSM or R-GSM band. CM3: Specifies the Classmark 3 capability. 0: The MS does not any options that are indicated in

ps-capa, sm-capability, cm3, lcsvacap, and cmsp are set to 1, indicating the corresponding capabilities are ed. vbs-notification-reception, vgcsnotification-reception, and fcfrequency-capability are set to 0, indicating the corresponding capabilities are not ed or not required. solsa is set to 0, indicating that the SoLSA capability is not ed.

CM3 1: The MS s options that are indicated in classmark 3 IE LCS VA capability (LCS value added location request notification capability) 0: location request notification via CS domain not ed 1: location request notification via CS domain ed UCS2 treatment 0: The ME has a preference for the default alphabet over UCS2 1: The ME has no preference between the use of the default alphabet and the use

of UCS2 SoLSA ( of Localized Service Area) 0: The ME does not SoLSA 1: The ME s SoLSA CMSP (CM Service Prompt) 0: "Network initiated MO CM connection request" not ed 1: "Network initiated MO CM connection request" ed for at least one CM protocol A5/3: Specifies the A5/3 encryption algorithm capability. 0: encryption algorithm A5/3 not available 1: encryption algorithm A5/3

available A5/2: Specifies the A5/2 encryption algorithm capability. 0: encryption algorithm A5/2 not available 1: Reserved Reference Standards For details, see 9.4.14a "Mobile Station Classmark 2" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

NAS message container Description of the IE Reference Standards Description of the IE Information Element Description Example (IE)


Encapsulates SMS message contents, such as DATA, ACK, or - An SGsAP-UPLINK-UNITDATA message is used as an example. ERROR In the message: messages, protocol-discriminator is set to sms-messages (9), sent indicating that the message contains SMS message between the contents. MSC server transaction-identifier contains ti-value and ti-flag. and visited location type-of-sms-msg is set to -data (1), indicating that the SMS message type is -DATA. (VLR). --data contains the information element.

Reference Standards For details, see 9.4.15 "NAS message container" in 3GPP TS 29. 118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

New location area identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

New location area identifier

Description

Example

Identifies the target location area (LA) contained in an SGsAP-LOCATION-UPDATE- An SGsAP-LOCATIONREQUEST message, requesting UPDATE-REQUEST message is for an SGs combined location used as an example. update or an IMSI attach. The In the message: New location area identifier Values of mcc-dig-1, consists of the mobile country mcc-dig-2, and mcccode (MCC), mobile network dig-3 specify the MCC. code (MNC), and location area Values of mnc-dig-3, code (LAC). mnc-dig-1, and mncdig-2 specify the MNC. The value of lac specifies the LAC.


New TMSI, or IMSI Description of the IE Reference Standards Description of the IE Information Element Description (IE)

Example

Specifies whether a TMSI or IMSI is used to identify a subscriber.

New TMSI, or IMSI

If the IE contains an IMSI, the MSC server does not allocate a TMSI for the subscriber. If the IE contains a TMSI, the MSC server uses the TMSI to identify the subscriber. If the IE contains neither a TMSI nor an IMSI and the subscriber has a valid TMSI, the MSC server continues using the original TMSI to identify the subscriber.

An SGsAP-LOCATION-UPDATEACCEPT message is used as an example. In the message: type-of-identity is set to tMSI-or-PTMSI (4), indicating that the MSC server uses a TMSI either new or original to identify a subscriber. odd-or-even-indic is set to even-number-of-identitydigits (0), indicating that the length of the TMSI or IMSI is an even number. tmsi-or-ptmsi specifies the TMSI used by the subscriber.

Reference Standards For details, see 9.4.14 "Mobile identity" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs


Old location area identifier Description of the IE Reference Standards Description of the IE Information Element (IE)

Old location area identifier

Description

Example

Identifies the original location area. The Old location area identifier IE consists of the mobile country code (MCC), mobile network code (MNC), and location area code (LAC). An SGsAP-LOCATIONUPDATE-REQUEST message is If a mobile terminal does not add the original LA information used as an example. to an ATTACH REQUEST or Values of mcc-dig-1, TRACKING AREA UPDATE mcc-dig-2, and mccREQUEST message, the MME dig-3 specify the MCC. must include the Old location Values of mnc-dig-3, area identifier IE in an SGsAPmnc-dig-1, and mncLOCATION-UPDATE-REQUEST dig-2 specify the MNC. message. The value of lac specifies the LAC.


Reject cause Description of the IE Reference Standards Description of the IE Information Element (IE)

Description Specifies the reason the MSC server used to reject a request sent by a subscriber. Value: 02: IMSI unknown in HLR 03: Illegal MS 04: IMSI unknown in VLR 05: IMEI not accepted 06: Illegal ME 11: PLMN not allowed 12: Location Area not allowed 13: Roaming not allowed in this location area 15: No Suitable Cells In Location Area 17: Network failure 20: MAC failure 21: Synch failure 22: Congestion 23: GSM authentication unacceptable 25: Not authorized for this CSG 32: Service option not ed

Example

Reject cause

Reference Standards

33: Requested service option not subscribed 34: Service option temporarily out of An SGsAP-LOCATIONorder UPDATE-REJECT message is 38: Call cannot be used as an example. identified 48-63: retry upon entry into a new cell 95: Semantically incorrect message 96: Invalid mandatory information 97: Message type nonexistent or not implemented 98: Message type not compatible with the protocol state 99: Information element non-existent or not implemented 100: Conditional IE error 101: Message not compatible with the protocol state 111: Protocol error, unspecified Other values received by a mobile terminal: The reject cause value is same as reject cause value 34. Other values received by the network side: The reject cause value is same as reject cause value 111.

For details, see 9.4.16 "Reject cause" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Service indicator Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies the circuit switched (CS) service type. Value: Service indicator

1: CS call indicator 2: SMS indicator Other values: The service is considered as a CS voice call.

An SGsAP-PAGING-REQUEST message is used as an example. In the message, serviceindicator-value is set to CS-callindicator (1), indicating that the service is a CS voice call.

Reference Standards For details, see 9.4.17 "Service indicator" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

SGs Cause Description of the IE Reference Standards Description of the IE Information Description Element (IE)

Example

Specifies a failure cause value. Value:

SGs Cause

1: IMSI detached for EPS services 2: IMSI detached for EPS and nonEPS services 3: IMSI unknown 4: IMSI detached for non-EPS services 5: IMSI implicitly detached for non-EPS services 6: UE unreachable 7: Message An SGsAP-PAGING-REJECT is used as an example. In the message, sgs-cause-value is set to mobilenot terminating-cs-fallback-call-rejected-by-the- (13), compatible indicating that the SGs paging during a voice call fails with the protocol state because the Circuit Switched Fallback (CSFB) subscriber rejects the call. 8: Missing mandatory information

element 9: Invalid mandatory information 10: Conditional information element error 11: Semantically incorrect message 12: Message unknown 13: Mobile terminating CS fallback call rejected by the Reference Standards For details, see 9.4.18 "SGs cause" in 3GPP TS 29. 118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TAI Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Tracking Area Identity (TAI)

Uniquely identifies the tracking area (TA) where a subscriber locates. The TAI IE contains the PLMN ID and tracking area code (TAC).

An SGsAP-SERVICEREQUEST message is used as an example. In the message, plmn specifies the ID of PLMN to which a subscriber belongs, and tac identifies the TA where the subscriber locates.

Reference Standards For details, see 9.4.21a "Tracking Area Identity" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.


TMSI

Description

Example

Specifies the TMSI that is used An SGsAP-PAGING-REQUEST message is used as an by a mobile terminal to example. In the message tmsitemporarily identify itself. body specifies a subscriber's TMSI.

Reference Standards For details, see 9.4.20 "TMSI" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

TMSI status Description of the IE Reference Standards Description of the IE Information Element (IE)

TMSI status

Description

Example

Notifies the MSC server/VLR that whether a valid TMSI is available. Value of TMSI flag in the TMSI status IE:

An SGsAP-LOCATIONUPDATE-REQUEST message is used as an example. In the message, tmsi-flag is set 0: no valid TMSI to tmsi-flag-false (0), indicating available that a subscriber does not have 1: valid TMSI available a valid TMSI.

Reference Standards For details, see 9.4.21 "TMSI status" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

UE EMM Mode Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

Example

Specifies the UE's EPS mobility management (EMM) status when the mobility management entity (MME) notifies the MSC server/VLR that the UE has received an SGsAP-PAGINGREQUEST message. Value: 0: EMM-IDLE An SGsAP-PAGING-REQUEST 1: EMM-CONNECTED message is used as an UE EMM (EPS Mobility Management) Mode If the MSC server/VLR receives example. In the message, uean SGsAP-SERVICE-REQUEST emm-mode-value is set to emmidle (0), indicating that the UE is message in which UE EMM Mode is not set to EMM-IDLE in the EMM-IDLE state. or EMM-CONNECTED, the MSC server can send an SGsAP-STATUS message to the MME. Bit 2 of P1149 determines whether the MSC server/VLR sends an SGsAP-STATUS message to the MME. Reference Standards For details, see 9.4.21c "UE EMM mode" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

UE Time Zone Description of the IE Reference Standards Description of the IE Information Element (IE)

Description

UE Time Zone

Specifies the offset between the Greenwich Mean Time (GMT) and local time in steps of 15 minutes. If the MME can obtain time zone An SGsAP-SERVICEinformation, it includes the UE REQUEST message is used as Time Zone IE in SGsAPan example. SERVICE-REQUEST and time-zone is set to 0x0, SGsAP-UPLINK-UNITDATA indicating that the offset messages sent to the MSC between the GMT and local server, ensuring that the MSC time is zero. server correctly generates call detail records (CDRs) during calls.

Example

Reference Standards For details, see 9.4.21b "UE Time Zone" in 3GPP TS 29. 118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

VLR name Description of the IE Reference Standards Description of the IE Information Element Description (IE) Specifies the domain name of a visited location (VLR). VLR name An SGsAP-PAGING-REQUEST message is used as an example.

Reference Standards For details, see 9.4.22 "VLR name" in 3GPP TS 29.118 V11.3.0. Parent topic: Description of Associated IEs Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Msoftx3000 V200r010c10 Typical Signaling Flows Manual 01.pdf 711m1f

Overview 4q3b3c

More details 26j3b

Related Documents 171j1w

Msoftx3000 V200r010c10 Typical Signaling Flows Manual 01.pdf 711m1f

Bsc Signaling Flows 6i4b15

Msoftx3000 2q301

Cell Signaling 183j4g

Signaling Theory 1z683o

Signaling Theory 1z683o

More Documents from "Marius Matei" 3q5w45

Msoftx3000 V200r010c10 Typical Signaling Flows Manual 01.pdf 711m1f

Referat Fizica-curent Electric 3m6h4a

Hsk 6 Vocabulary List 6u86e

4. Pronumele Demonstrativ 3v606j

Arthur C. Clarke - Odiseea Spatiala 2001 58y3i

Inked Girls Us 22jr