Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.231  Word version:  17.0.0

Top   Top   Up   Prev   None
1…   4…   4.4.2   4.4.3   4.4.4   4.4.5…   6…   6.1.2…   6.2…   6.2.2…   7…   7.2.3   7.2.4…   7.3…   8…   9…   13…   14…   15…

 

15  Messages/Procedures and their contentsp. 69

15.1  Messages between (G)MSC serversp. 69

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 TS 29.231.
SIP method Reference
INVITE RFC 3261
ACK RFC 3261
BYE RFC 3261
CANCEL RFC 3261
OPTIONS RFC 3261
INFO RFC 2976
UPDATE RFC 3311
PRACK RFC 3262
Up

15.2  Procedures between (G)MSC server and MGWp. 69

15.2.1  Generic Mc Interface Proceduresp. 69

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 TS 23.205.
Procedure defined in TS 23.205 Remarks
Change Flow Direction Note 1 in that clause is replaced by the following Note:
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:
Activate Interworking Function
Bearer Released
Release Termination
Send Tone
Stop Tone
Play Announcement
Stop Announcement
Announcement Completed
Tone Completed
Detect DTMFThe NOTE in that clause is replaced by the following Note:
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
Up

15.2.2  SIP-I Specific Mc Interface Proceduresp. 71

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

16  Bearer Redirectp. 71

Bearer Redirect is not supported within this 3GPP Release.

17  (G)MSC MGW Tandemingp. 71

For (G)MSC MGW Tandeming, the procedures specified in the clause 18 of TS 23.205 shall apply.

18  Timers for SIP-I based CS core networkp. 72

The Start_Bearer_Establishment Timer, as defined in TS 23.205, shall apply to a SIP-I based CS core network.
Timer functionality and procedures defined within ITU-T Q.1912.5 [9] Profile C shall apply to a SIP-I based CS core network.

19  Multiple IP Realmsp. 72

Multiple IP realms are supported as specified in TS 23.205.

$  Change historyp. 73


Up   Top