15 Messages/Procedures and their contents

23.2313GPPRelease 17SIP-I based circuit-switched core networkStage 2TS

15.1 Messages between (G)MSC servers

Table 15.1.1 lists the SIP methods that shall be supported between (G)MSC servers on Nc interface. Amendments and Endorsements to the referenced specifications are specified in 3GPP TS 29.231[4].

Table 15.1.1: Messages between (G)MSC servers

SIP method

Reference

INVITE

RFC 3261 [15]

ACK

RFC 3261 [15]

BYE

RFC 3261 [15]

CANCEL

RFC 3261 [15]

OPTIONS

RFC 3261 [15]

INFO

RFC 2976 [17]

UPDATE

RFC 3311 [18]

PRACK

RFC 3262 [19]

15.2 Procedures between (G)MSC server and MGW

15.2.1 Generic Mc Interface Procedures

Table 15.2.1.1 below indicates the procedures used between the (G)MSC server and the MGW in the Mc interface. These procedures are defined in Clause 16.2 of 3GPP TS 23.205 [7].

Table 15.2.1.1: Required procedures defined in 3GPP TS 23.205 [7]

Procedure defined in 3GPP TS 23.205 [7]

Remarks

Change Flow Direction

NOTE 1 in that Clause is replaced by the following Note:

NOTE 1: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure, the "Join Bearer Termination" procedure, or the "Isolate Bearer Termination" procedure.

Join Bearer Termination

Isolate Bearer Termination

Prepare Bearer

This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport, or to seize internal terminations in a MGW, e.g. for conferencing scenarios or for VGCS.

The optional "Tunnel Support" Information element is not applicable.

Reserve Circuit

Change Through-Connection

The NOTE in that Clause is replaced by the following Note:

NOTE: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure, the "Join Bearer Termination" procedure, or the "Isolate Bearer Termination" procedure.

Activate Interworking Function

Bearer Released

Release Termination

Send Tone

Stop Tone

Play Announcement

Stop Announcement

Announcement Completed

Tone Completed

Detect DTMF

The NOTE in that Clause is replaced by the following Note:

NOTE: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, the "Reserve and Configure RTP Connection Point" procedure, the "Prepare Bearer" procedure, the "Reserve Circuit" procedure.

Stop DTMF Detection

Report DTMF

Send DTMF

Stop DTMF

MGW Out-of-Service/ Maintenance locking

MGW Communication Up

MGW Restoration

MGW Register

MGW Re-register

(G)MSC Server Ordered Re-register

(G)MSC Server Restoration

(G)MSC Server Out of Service

Termination Out-of-Service

Termination Restoration

Audit Value

Audit Capability

Capability Update

Command Reject

Activate Voice Processing Function

Modify Bearer Characteristics

This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS or A interface.

IWF Protocol Indication

MGW Resource Congestion Handling – Activate

MGW Resource Congestion Handling – Indication

Bearer Modification Support

This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface.

CTM report

Prepare IP Transport

Modify IP Transport Address

Emergency Call Indication

Trace Activation

Trace Deactivation

Trace Activation result notification

Continuity Check Tone

Continuity Check Verify

Continuity Check Response

Rate Change

Bearer Modified

This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport.

Bearer Modification Failed

This procedure is not applicable for terminations towards a 3GPP SIP-I based circuit-switched core network, but it is applicable for terminations toward an Iu-CS interface with ATM transport.

Termination heartbeat indication

Inactivity timeout activation

Inactivity timeout indication

Reserve RTP Connection Point

Configure RTP Connection Point

Reserve and Configure RTP Connection Point

15.2.2 SIP-I Specific Mc Interface Procedures

The clauses below indicate the procedures used between the (G)MSC server and the MGW in the Mc interface that are specific for a SIP-I based Nc network.

The procedures are logical, i.e. message identifiers are not part of the protocol. Several logical procedures can be combined into one H.248 command in order to perform required transactions. If several logical procedures are combined into one H.248 command, only one context/context request and only one bearer termination/bearer termination request is sent in the H.248 command.

All the procedures below describe a successful operation. If the procedure is rejected, a Command Reject is sent back to the entity that sent the command request.

Each Information Element, IE, is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory information element shall always be present. A conditional information shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and not a stage 3 classification to be used for the protocol.

The stage 2 and stage 3 message and information element names are not necessarily identical.