7 MSC Server – CS-MGW interaction
29.2923GPPInterworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS)Release 17TS
7.1 Mobile originated call
7.1.1 CS-MGW selection
The MSC Server shall select a CS-MGW for the bearer connection before it performs the access bearer assignment or the network side connection point reservation.
7.1.2 IMS session side establishment
7.1.2.1 General
The MSC Server shall either select bearer characteristics or request the CS-MGW to select and provide the bearer characteristics for the network side session before sending the INVITE request. The MSC Server shall use the Reserve RTP Connection Point procedure as defined in 3GPP TS 23.205 [39] and in 3GPP TS 29.232 [11], with additional information elements as specified in the present subclause.
Within this procedure, the MSC Server shall indicate the received speech codecs from the UE and the MSC Server may indicate some configured speech codec(s) to the CS-MGW and request a local IP address and UDP port from the CS-MGW and the MSC Server may also indicate that the IP interface type is for MboIP as defined in 3GPP TS 23.205 [39] and in 3GPP TS 29.232 [11], with additional information elements as specified in the present subclause. The local IP address and UDP port are used by the CS-MGW to receive user plane data.
The CS-MGW shall reply to the MSC Server with the selected local speech codec(s) and the selected local IP address and UDP port(s).
After the succeeding node has provided the SDP answer, the MSC Server uses the Configure RTP Resources procedure as defined in 3GPP TS 29.232 [11] to request the CS-MGW to configure the bearer.
7.1.2.2 Additions to Reserve RTP Connection Point Procedure
This procedure is used to reserve an RTP bearer termination. The Reserve RTP Connection Point procedure defined in in 3GPP TS 23.205 [39] shall be applied with additional information elements as defined in table 7.1.2.2.1.
Table 7.1.2.2.1: Additions to Reserve RTP Connection Point Procedure
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|
Reserve RTP Connection Point |
(G)MSC-Server |
Priority information |
O |
This information element requests the CS-MGW to apply priority treatment for the terminations and bearer connections in the specified context. |
|
ECN Enable |
O |
This information element requests the CS-MGW to apply ECN procedures. |
||
|
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the CS-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. |
||
|
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. |
||
|
ICE password request |
O |
This information element is present if MSC Server requests an ICE password. |
||
|
ICE Ufrag request |
O |
This information element is present if MSC Server requests an ICE ufrag. |
||
|
ICE host candidate request |
O |
This information element is present if MSC Server requests an ICE host candidate. |
||
|
ICE pacing request |
O |
This information element is present if MSC Server requests a pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
|
STUN server request |
O |
This information element is present if MSC Server requests the CS-MGW to answer STUN connectivity checks for ICE. |
||
|
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
|
Reserve RTP Connection Point Ack |
MGW |
ICE password |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the CS-MGW. |
|
ICE Ufrag |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the CS-MGW. |
||
|
ICE host candidate |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the CS-MGW. |
||
|
ICE pacing |
C |
This information element shall be present only if it was contained in the request. It indicates a desired pacing value for connectivity checks (Ta timer value). |
||
|
ICE lite indication |
C |
This information element shall be present only if an ICE host candidate request was contained in the request, and the CS-MGW supports ICE lite, but not full ICE. It indicates that the CS-MGW only supports ICE lite. |
||
|
SDPCapNeg configuration |
C |
This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
7.1.2.3 Additions to Configure RTP Connection Point Procedure
This procedure is used to configure or reconfigure an RTP bearer termination. The Configure RTP Connection Point procedure defined in 3GPP TS 23.205 [39] shall be applied with additional information elements as defined in table 7.1.2.3.1.
Table 7.1.2.3.1: Additions to Configure RTP Connection Point Procedure
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|
Configure RTP Connection Point |
(G)MSC-Server |
Allowed RTCP APP message types |
O |
This information element is present if MSC server allows the MGW to send RTCP APP packets of the indicated types defined in TS 26.114 [28]. The MGW shall not send other RTCP APP packets. If the parameter is not supplied, the MGW shall not send any RTCP APP packets. |
|
ECN Enable |
O |
This information element requests the CS-MGW to apply ECN procedures. |
||
|
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the CS-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. |
||
|
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. |
||
|
ICE Connectivity Check |
C |
This information element requests the CS-MGW to perform ICE connectivity check as defined by IETF RFC 8445 [69]. It is only applicable for full ICE. |
||
|
Notify ICE Connectivity Check Result |
C |
This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. |
||
|
Notify New Peer Reflexive Candidate |
C |
This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. |
||
|
Additional ICE Connectivity Check |
C |
This information element requests the CS-MGW to perform additional ICE connectivity check as defined by IETF RFC 8445 [69]. It is only applicable for full ICE. |
||
|
ICE received candidate |
O |
This information element is present if MSC Server indicates a received candidate for ICE. |
||
|
ICE received password |
O |
This information element is present if MSC Server indicates a received password for ICE. |
||
|
ICE received pacing |
O |
This information element is present if MSC Server indicates a received pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
|
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
|
Configure RTP Connection Point Ack |
MGW |
|||
7.1.3 Access bearer establishment
7.1.3.1 General
The way the MSC Server media gateway interaction is carried out depends on the characteristics of the access bearer network.
7.1.3.2 Iu interface on IP
The MSC Server and the CS-MGW shall act in accordance with clause 6.1.3 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.1.3.3 A interface over IP
The MSC Server and the CS-MGW shall act in accordance with clause 6.1.5 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.1.3.4 A interface over TDM
The MSC Server and the CS-MGW shall act in accordance with clause 6.1.1.4 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.1.3.5 Iu over UTRAN and GERAN
The MSC Server and the CS-MGW shall act in accordance with clause 6.1.1.4 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.1.4 Apply ringing tone
If the condition as defined in clause 5.3.5 is fulfilled the MSC Server shall instruct the CS-MGW to send ringing tone towards the calling party. In this case the MSC Server shall use the Send Tone procedure in accordance with 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
If the MSC Server wishes to stop sending the ringing tone e.g. due to the receipt of a 200 OK response to the INVITE request the MSC Server shall apply the Stop Tone procedure as defined in 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
7.1.5 Through connection
If the MSC Server wants to configure the CS-MGW so that the bearer will be through-connected in the backward direction the MSC Server shall:
– use Change Through-Connection procedure as defined in 3GPP TS 29.232 [11] during any one of the Prepare Bearer and Reserve Circuit procedures as defined in 3GPP TS 29.232 [11]; or
– use Configure the RTP Connection Point procedure as defined in 3GPP TS 29.232 [11] during Prepare IP bearer procedure as defined in 3GPP TS 29.232 [11].
If the MSC Server wants to configure the CS-MGW so that the bearer will be both-way through connected the MSC Server shall use Change Through-Connection procedure as defined in 3GPP TS 29.232 [11].
7.1.5a Handling of Forking
The procedures described in subclauses 7.1.1 to 7.1.6 shall be applied with the addition that the MSC Server and the CS-MGW shall act in accordance with subclauses 9.2.3.4.1 to 9.2.3.4.4 in 3GPP TS 29.163 [46].
NOTE: For the references to 3GPP TS 29.163 [46], the O-MGCF and I-MGCF in 3GPP TS 29.163 [46] is to be understood as MSC Server, the IM-MGW is to be understood as CS-MGW, and the Configure IMS Resources procedure is to be understood as Configure RTP Resources procedure.
7.1.6 Failure handling in MSC server
If any procedure between the MSC Server and the CS-MGW has not completed successfully or the MSC Server receives a Bearer Released procedure from the CS-MGW the procedure in accordance with clause 6.1.1.12 of 3GPP TS 23.231 [40] and 3GPP TS 29.232 [11] shall be applied.
7.2 Mobile terminated call
7.2.1 CS-MGW selection
The MSC Server shall select an CS-MGW for the bearer connection before it performs the network side bearer establishment or the access bearer assignment. The selection of the CS-MGW does not take place before the call proceeding has been received by the MSC Server.
7.2.2 Network side session establishment
7.2.2.1 General
The MSC Server shall request the CS-MGW to prepare for the network side session establishment using the Reserve and Configure RTP Connection Point procedure as specified in 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11], with additional information elements as specified in the present subclause. Within this procedure, the MSC Server shall indicate the received speech codecs from the remote UE and request a local IP address and UDP port from the CS-MGW and the MSC Server may also indicate that the IP interface type is for MboIP as defined in 3GPP TS 29.232 [11]. The local IP address and UDP ports are used by the CS-MGW to receive user plane data. The MSC Server shall include the local IP address and UDP port number in the SDP answer for the selected codec.
7.2.2.2 Additions to Reserve and Configure RTP Connection Point
This procedure is used to reserve and configure an RTP bearer termination. The Reserve and Configure RTP Connection Point procedure defined in 3GPP TS 23.205 [39] shall be applied with additional information elements as defined in table 7.2.2.2.1.
Table 7.2.2.2.1: Additions to Reserve and Configure RTP Connection Point Procedure
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|
Reserve and Configure RTP Connection Point |
(G)MSC-Server |
Allowed RTCP APP message types |
O |
This information element is present if MSC server allows the MGW to send RTCP APP packets of the indicated types defined in TS 26.114 [28]. The MGW shall not send other RTCP APP packets. If the parameter is not supplied, the MGW shall not send any RTCP APP packets. |
|
Priority information |
O |
This information element requests the CS-MGW to apply priority treatment for the terminations and bearer connections in the specified context. |
||
|
ECN Enable |
O |
This information element requests the CS-MGW to apply ECN procedures and IP header settings as an ECN endpoint. |
||
|
ECN Initiation Method |
C |
This information element specifies the ECN Initiation method and requests the CS-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. |
||
|
Notify ECN Failure Event |
C |
This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. |
||
|
STUN server request |
O |
This information element is present if MSC Server requests the CS-MGW to answer STUN connectivity checks for ICE. |
||
|
ICE Connectivity Check |
C |
This information element requests the CS-MGW to perform ICE connectivity check as defined by IETF RFC 8445 [69]. It is only applicable for full ICE. |
||
|
Notify ICE Connectivity Check Result |
C |
This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. |
||
|
Notify New Peer Reflexive Candidate |
C |
This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. |
||
|
ICE password request |
O |
This information element is present if MSC Server requests an ICE password. |
||
|
ICE Ufrag request |
O |
This information element is present if MSC Server requests an ICE ufrag. |
||
|
ICE host candidate request |
O |
This information element is present if MSC Server requests an ICE host candidate. |
||
|
ICE pacing request |
O |
This information element is present if MSC Server requests a pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
|
ICE received candidate |
O |
This information element is present if MSC Server indicates a received candidate for ICE. |
||
|
ICE received password |
O |
This information element is present if MSC Server indicates a received password for ICE. |
||
|
ICE received Ufrag |
O |
This information element is present if MSC Server indicates a received Ufrag for ICE. |
||
|
ICE received pacing |
O |
This information element is present if MSC Server indicates a received pacing value for connectivity checks (Ta timer value). It is only applicable for full ICE. |
||
|
SDPCapNeg configuration |
O |
This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
||
|
Reserve and Configure RTP Connection Point Ack |
MGW |
ICE password |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the CS-MGW. |
|
ICE Ufrag |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the CS-MGW. |
||
|
ICE host candidate |
C |
This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the CS-MGW. |
||
|
ICE pacing |
C |
This information element shall be present only if it was contained in the request. It indicates a desired pacing value for connectivity checks (Ta timer value). |
||
|
ICE lite indication |
C |
This information element shall be present only if an ICE host candidate request was contained in the request, and the CS-MGW supports ICE lite, but not full ICE. It indicates that the CS-MGW only supports ICE lite. |
||
|
SDPCapNeg configuration |
C |
This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. |
7.2.3 Access bearer assignment
7.2.3.1 General
The way the MSC Server-CS-MGW interaction is carried out depends on the characteristics of the access bearer network.
7.2.3.2 Iu interface on IP
The MSC Server and the CS-MGW shall act in accordance with clause 6.2.3 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.2.3.3 A interface over IP
The MSC Server and the CS-MGW shall act in accordance with clause 6.2.4 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.2.3.4 A interface over TDM
The MSC Server and the CS-MGW shall act in accordance with clause 6.2.2.2.4 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.2.3.5 Iu over UTRAN and GERAN
The MSC Server and the CS-MGW shall act in accordance with clause 6.2.2.2.4 in 3GPP TS 23.205 [39] and apply the coding in accordance with 3GPP TS 29.232 [11].
7.2.4 Apply ringing tone
If the condition as defined in clause 5.4.7 is fulfilled the MSC Server shall instruct the CS-MGW to send ringing tone towards the calling party. In this case the MSC Server shall use the Send Tone procedure in accordance with 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
If the MSC Server wishes to stop sending the ringing tone, e.g. due to receipt of the CONNECT message, the MSC Server shall apply the Stop Tone procedure as defined in 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
7.2.5 Through connection
If the MSC Server wants to configure the CS-MGW so that the bearer will not be through-connected the MSC Server shall:
– use Change Through-Connection procedure as defined in 3GPP TS 29.232 [11] during any one of the Prepare Bearer and Reserve Circuit procedures as defined in 3GPP TS 29.232 [11]; or
– use Configure the RTP Connection Point procedure as defined in 3GPP TS 29.232 [11]during Prepare IP bearer procedure as defined in 3GPP TS 29.232 [11].
If the MSC Server wants to configure the CS-MGW so that the bearer will be both-way through connected the MSC Server shall use the Change Through-Connection procedure as defined in 3GPP TS 29.232 [11].
7.2.6 Announcement
If the MSC Server wants to provide an announcement, e.g. when the condition in clause 5.4.7 is fulfilled, the MSC Server shall instruct the CS-MGW to send an announcement. In this case the MSC Server shall use the Play Announcement procedure in accordance with 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
If the MSC Server wishes to stop the sending of an announcement the MSC Server shall apply the Stop Announcement procedure as defined in 3GPP TS 23.205 [39] and 3GPP TS 29.232 [11].
7.2.7 Failure handling in the MSC server
If any procedure between the MSC Server and the CS-MGW has not completed successfully or the MSC Server receives a Bearer Released procedure from the CS-MGW the procedure in accordance with clause 6.2.1.3.13 of 3GPP TS 23.231 [40] and 3GPP TS 29.232 [11] shall be applied.
7.2A Notification Procedures
7.2A.1 General information
This subclause contains procedures common to mobile originated and mobile terminated calls which are not defined in 3GPP TS 23.205 [39] but are applicabe to the MSC Server enhanced for ICS and the CS-MGW.
7.2A.2 ECN Failure Indication
This procedure is used to report ECN related errors (see 3GPP TS 29.163 [46] clause 9.2.11.1c).
Table 7.2A.2.1: Procedures between MSC Server and CS-MGW: ECN Failure Indication
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|---|---|---|---|---|
|
ECN Failure Indication |
CS-MGW |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination |
M |
This information element indicates the bearer termination for which the ECN failure is reported. |
||
|
ECN Failure Indication |
M |
This IE indicates an ECN failure event. |
||
|
ECN Failure Indication Ack |
MSC Server |
Context |
M |
This information element indicates the context where the command was executed. |
|
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
7.2A.3 ICE Connectivity Check Result Notification
This procedure is used to report ICE connectivity check result for Full ICE.
Table 7.2A.3.1: Procedures between MSC Server and CS-MGW: ICE Connectivity Check Result Notification
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|---|---|---|---|---|
|
ICE Connectivity Check Result Notification |
CS-MGW |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination |
M |
This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. |
||
|
ICE Connectivity Check Result |
M |
This information element indicates an ICE Connectivity Check Result event. |
||
|
ICE Connectivity Check Result Notification Ack |
MSC Server |
Context |
M |
This information element indicates the context where the command was executed. |
|
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
7.2A.4 ICE New Peer Reflexive Candidate Notification
This procedure is used to report ICE new peer reflexive candidate for Full ICE.
Table 7.2A.4.1: Procedures between MSC Server and CS-MGW: ICE New Peer Reflexive Candidate Notification
|
Procedure |
Initiated |
Information element name |
Information element required |
Information element description |
|---|---|---|---|---|
|
ICE New Peer Reflexive Candidate Notification |
CS-MGW |
Context |
M |
This information element indicates the context for the bearer termination. |
|
Bearer Termination |
M |
This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported |
||
|
ICE New Peer Reflexive Candidate |
M |
This information element indicates an ICE New Peer Reflexive Candidate event. |
||
|
ICE New Peer Reflexive Candidate Notification Ack |
MSC Server |
Context |
M |
This information element indicates the context where the command was executed. |
|
Bearer Termination |
M |
This information element indicates the bearer termination where the command was executed. |
7.3 Call clearing
7.3.1 Clearing received from the network
7.3.1.1 Access bearer clearing
Once the call clearing and the release of the associated radio resources have been completed, the MSC Server releases any CS-MGW allocated resources for the access side. If any resources were seized in the CS-MGW, the MSC Server uses the Release Termination procedure as specified in 3GPP TS 29.232 [11] to request the CS-MGW to remove the access side bearer termination.
7.3.1.2 Network side clearing
If the MSC Server requires to release resources due to the receipt of a BYE or CANCEL request or a response including a failure indication from the network the MSC Server shall act in accordance with clause 7.2.6 in 3GPP TS 23.231 [40] and 3GPP TS 29.232 [11].
7.3.2 Clearing received from the user
7.3.2.1 Access bearer clearing
Once the call clearing and the release of the associated radio resources have been completed, the MSC Server releases any CS-MGW allocated resources for the access side. If any resources were seized in the CS-MGW, the MSC Server uses the Release Termination procedure as specified in 3GPP TS 29.232 [11] to request the CS-MGW to remove the access side bearer termination.
7.3.2.2 Network side clearing
If the MSC Server requires to release resources due to the receipt of a BYE or CANCEL request or a response including a failure indication from the originating or terminating UE the MSC Server shall act in accordance with clause 7.2.6 in 3GPP TS 23.231 [40] and 3GPP TS 29.232 [11].
7.3.3 Call clearing received from the CS-MGW
7.3.3.1 Bearer released received on the access side
After the MSC Server has received the Bearer Released procedure from the CS-MGW on the access side, the MSC Server shall release the access resources as described in 3GPP TS 24.008 [3]. If the call is already established towards the network side, call clearing to the network side is performed as described in clause 5.5.3.
7.3.3.2 Bearer released received on the network side
After the MSC Server has received the Bearer Released procedure from the CS-MGW on the network side, the MSC Server shall clear the call to the network side as described in clause 5.5.3 and clear the call to the UE as described in 3GPP TS 24.008 [3].
7.4 Call independent procedures
The MSC Server and the CS-MGW are involved in a number of procedures which are not related to the setting up and clearing of calls. The MSC Server and the CS-MGW shall comply with the requirements stated in the different subclauses 10.1 – 10.10 of 3GPP TS 23.205 [39] and subclauses 10.12 – 10.16 of 3GPP TS 23.205 [39].
7.5 Explicit Congestion Notification
An MSC Server and a CS-MGW may support Multimedia Telephony using Explicit Congestion Notification (see IETF RFC 3168 [48], IETF RFC 6679 [49], and 3GPP TS 26.114 [28]), and may then act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network that properly handles ECN-marked packets.
The ECN procedures described in 3GPP TS 29.163 [46], clause 9.2.11, for MGCF and IM-MGW are then applicable for MSC Server and the CS-MGW.
7.6 Multimedia Priority Service (MPS) Support
The Multimedia Priority Service (MPS) is specified in 3GPP TS 22.153 [54]. An MSC Server and a CS-MGW may support the priority treatment of a call/session identified as an MPS call/session.
The MPS procedures described in 3GPP TS 29.163 [46], clause 9.4, for MGCF and IM-MGW are then applicable for MSC Server and the CS-MGW.
7.7 Interactive Connectivity Establishment
An MSC Server and a CS-MGW may support ICE functionality as specified in IETF RFC 8445 [69] and IETF RFC 8839 [70], and 3GPP TS 24.229 [2].
Support of full ICE functionality is optional, but if ICE is supported, the MSC Server and the CS-MGW shall at least support ICE lite as specified in IETF RFC 8445 [69].
The requirements as described in clause 9.2.12 of 3GPP TS 29.163 [46] for MGCF and IM-MGW, apply to the MSC Server and the CS-MGW when the ICE procedures are supported.
7.8 Codec Parameters Handling
7.8.1 Handling of common codec parameters
The requirements as described in clause 9.2.13.1 of 3GPP TS 29.163 [46] for the MGCF and the IM-MGW, apply to the MSC Server and the CS-MGW.
7.8.2 EVS speech codec
The Enhanced Voice Services (EVS) speech codec is defined in 3GPP TS 26.441 [61]. Its RTP payload type is defined in 3GPP TS 26.445 [62], and procedures for its usage as IMS Multimedia Telephony speech codec are defined in 3GPP TS 26.114 [28].
The MSC Server and the CS-MGW may support transcoding to and from the EVS speech codec. If they do so, the requirements as described in clause 9.2.13.2 of 3GPP TS 29.163 [46] for the MGCF and the IM-MGW, apply to the MSC Server and the CS-MGW.
7.9 SDP Capability Negotiation (SDPCapNeg)
The SDP Capability Negotiation (SDPCapNeg) as specified in IETF RFC 5939 [63] is adopted as an optional functionality to negotiate capabilities and their associated configurations according to 3GPP TS 24.229 [2].
The SDPCapNeg requirements and procedures described in subclause 5.2.23 of 3GPP TS 23.333 [64] for MRFC and MRFP are then applicable for MSC Server and the CS-MGW.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
06/2013 |
CT#60 |
CP-130343 |
0073 |
3 |
Handling of dialed digits home-local number |
11.6.0 |
12.0.0 |
|
06/2013 |
CT#60 |
CP-130343 |
0078 |
2 |
Identity mapping correction |
11.6.0 |
12.0.0 |
|
06/2013 |
CT#60 |
CP-130343 |
0083 |
1 |
Mapping between cause IE and SIP status code when timer expires |
11.6.0 |
12.0.0 |
|
06/2013 |
CT#60 |
CP-130343 |
0084 |
1 |
Mapping between cause values and SIP status code related to not implemented features/services |
11.6.0 |
12.0.0 |
|
06/2013 |
CT#60 |
CP-130343 |
0085 |
1 |
Mapping of CUG specific cause values |
11.6.0 |
12.0.0 |
|
06/2013 |
CT#60 |
CP-130343 |
0086 |
1 |
Mapping of cause value 8 "operator determined barring" |
11.6.0 |
12.0.0 |
|
09/2013 |
CT#61 |
CP-130558 |
0088 |
Identity mapping correction |
12.0.0 |
12.1.0 |
|
|
06/2014 |
CT#64 |
CP-140353 |
0095 |
– |
Conference creation |
12.1.0 |
12.2.0 |
|
06/2014 |
CT#64 |
CP-140354 |
0100 |
– |
Removal of CDIVN |
12.1.0 |
12.2.0 |
|
06/2014 |
CT#64 |
CP-140385 |
0089 |
1 |
Support of SIP precondition mechanism by MSC server |
12.1.0 |
12.2.0 |
|
06/2014 |
TSG#64 |
CP-140396 |
0090 |
2 |
ICE support for MSC Server enhanced for ICS |
12.1.0 |
12.2.0 |
|
09/2014 |
CT-65 |
CP-140542 |
0101 |
– |
ICE: reference correction |
12.2.0 |
12.3.0 |
|
09/2014 |
CT-65 |
CP-140554 |
0102 |
3 |
Sending of PROGRESS during aSRVCC |
12.2.0 |
12.3.0 |
|
12/2014 |
CT-66 |
CP-140912 |
0103 |
2 |
Update of protocol stacks and associated text for IuCS to Mb interworking |
12.3.0 |
12.4.0 |
|
12/2014 |
CT-66 |
CP-140919 |
0104 |
3 |
Sending of PROGRESS upon SIP UPDATE message |
12.3.0 |
12.4.0 |
|
12/2014 |
CT-66 |
CP-140933 |
0105 |
3 |
Adding support for EVS codec |
12.3.0 |
12.4.0 |
|
06/2015 |
CT-68 |
CP-150337 |
0111 |
2 |
Correcting rules condition for CFU service |
12.4.0 |
12.5.0 |
|
06/2015 |
CT-68 |
CP-150364 |
0112 |
2 |
Notify UE remote party state after SRVCC |
12.5.0 |
13.0.0 |
|
09/2015 |
CT-69 |
CP-150484 |
0113 |
1 |
Clarifying clearing initiated by the mobile |
13.0.0 |
13.1.0 |
|
09/2015 |
CT-69 |
CP-150484 |
0114 |
1 |
Autonomous clearing initiated by the MSC Server |
13.0.0 |
13.1.0 |
|
09/2015 |
CT-69 |
CP-150463 |
0120 |
– |
Missing 4xx final responses |
13.0.0 |
13.1.0 |
|
09/2015 |
CT-69 |
CP-150463 |
0126 |
2 |
Mapping to/from Q.850 cause codes |
13.0.0 |
13.1.0 |
|
12/2015 |
CT-70 |
CP-150667 |
0127 |
5 |
Stage 2 Mc supporting of SDP capability negotiation |
13.1.0 |
13.2.0 |
|
12/2015 |
CT-70 |
CP-150660 |
0128 |
1 |
Removing a conference participant |
13.1.0 |
13.2.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-03 |
CT#71 |
CP-160105 |
0130 |
1 |
F |
Removal of references to TS 26.235 |
13.3.0 |
|
2017-03 |
CT#75 |
CP-170085 |
0131 |
B |
Reception of 666 (Unwanted) response |
14.0.0 |
|
|
2017-06 |
CT#76 |
CP-171131 |
0132 |
1 |
F |
Mapping of additional 4xx response codes for SPECTRE |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171129 |
0133 |
3 |
B |
ICS: Interworking procedures of password |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171134 |
0134 |
2 |
F |
Mapping SIP Reason header field cause “Call completed elsewhere” to a cause information element in the DISCONNECT message |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171131 |
0135 |
1 |
F |
Reference update: draft-ietf-sipcore-status-unwanted |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171134 |
0136 |
1 |
F |
Completion of "Reserve RTP Connection Point", "Reserve and Configure RTP Connection Point" and "Configure RTP Connection Point" procedures. |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171129 |
0137 |
2 |
B |
Registration of password for ICS |
14.1.0 |
|
2017-06 |
CT#76 |
CP-171134 |
0138 |
F |
Response-Source header field handling completion |
14.1.0 |
|
|
2017-09 |
CT#77 |
CP-172049 |
0139 |
F |
Reference update from draft-ietf-sipcore-status-unwanted-06 to RFC 8197 |
14.2.0 |
|
|
2017-12 |
CT#78 |
CP-172049 |
0140 |
F |
Interworking of cause location parameter |
14.3.0 |
|
|
2017-12 |
CT#78 |
CP-173104 |
0141 |
F |
Call rejection when IMSI is detached |
15.0.0 |
|
|
2017-12 |
CT#78 |
CP-173104 |
0142 |
1 |
B |
Call rejection when VLR data cannot be retrieved |
15.0.0 |
|
2018-03 |
CT#79 |
CP-180044 |
0144 |
A |
Reference update: RFC 8224 |
15.1.0 |
|
|
2018-03 |
CT#79 |
CP-180042 |
0146 |
A |
Reference Update for the ISUP location parameter |
15.1.0 |
|
|
2018-03 |
CT#79 |
CP-180042 |
0148 |
A |
Correction of incorrect reference numbering |
15.1.0 |
|
|
2018-09 |
CT#81 |
CP-182018 |
0152 |
A |
Screening indicator values |
15.2.0 |
|
|
2018-09 |
CT#81 |
CP-182017 |
0153 |
F |
Mapping of calling identity number verification status |
15.2.0 |
|
|
2018-09 |
CT#81 |
CP-182024 |
0155 |
A |
Reference Update for the ISUP Q.850 location parameter |
15.2.0 |
|
|
2019-03 |
CT#83 |
CP-190126 |
0157 |
2 |
A |
Reference Update for the ISUP Cause Location Parameter Draft |
15.3.0 |
|
2019-06 |
CT#84 |
CP-191094 |
0159 |
A |
Reference Update for the ISUP Cause Location Parameter Draft |
15.4.0 |
|
|
2019-09 |
CT#85 |
CP-192166 |
0161 |
1 |
A |
Reference Update RFC8606 |
15.5.0 |
|
2020-07 |
SA#88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
CT#95e |
CP-220209 |
0162 |
C |
Update of IETF references for ICE |
17.0.0 |
|