A.17 Procedures
29.3323GPPMedia Gateway Control Function (MGCF) - IM Media GatewayMn interfaceRelease 17TS
A.17.1 Call Independent Procedures
Table A.17.1/1 shows the relationship between each non call-related procedure in 3GPP TS 29.232 [5] and the corresponding procedure defined in 3GPP TS 29.163 [4].
For further description of error codes and service change reasons, refer to ITU-T Recommendation H.248.8 [10].
Table A.17.1/1: Non call-related transaction reused from 3GPP TS 29.232 [5]
|
Procedure defined in 3GPP TS 29.163 [4] |
Procedure defined in 3GPP TS 29.232 [5] |
Support |
Comment |
|
IM-MGW Out of service |
MGW Out of Service |
Mandatory |
|
|
IM-MGW Communication Up |
MGW Communication Up |
Mandatory |
|
|
IM-MGW Restoration |
MGW Restoration |
Mandatory |
|
|
IM-MGW Register |
MGW Register |
Mandatory |
|
|
IM-MGW Re-register |
MGW Re-register |
Mandatory |
|
|
MGCF Ordered Re-register |
(G)MSC Server Ordered Re-register |
Mandatory |
|
|
MGCF Restoration |
(G)MSC Server Restoration |
Optional |
|
|
MGCF Out of Service |
(G)MSC Server Out of Service |
Optional |
|
|
Termination Out-of-Service |
Termination Out-of-Service |
Mandatory |
|
|
Termination Restoration |
Termination Restoration |
Mandatory |
|
|
Audit Value |
Audit Value |
Mandatory |
Mandatory support only for audit of Termination Service State and for periodic audit of MGW (empty Audit descriptor). Optional support for audit of Packages or to retrieve MGC Information. |
|
Audit Capability |
Audit Capability |
Optional |
|
|
Command Rejected |
Command Rejected |
Mandatory |
The "Command Rejected" procedure may be used in response both to call-related and non-call-related ITU-T Recommendation H.248 Commands |
|
IM-MGW Capability Change |
Capability Update |
Optional |
|
|
IM-MGW Resource Congestion Handling – Activate |
MGW Resource Congestion Handling – Activate |
Mandatory |
|
|
IM-MGW Resource Congestion Handling – Indication |
MGW Resource Congestion Handling – Indication |
Mandatory |
|
|
Inactivity Timeout – Activate |
Inactivity Timeout – Activate |
Optional |
|
|
Inactivity Timeout – Indication |
Inactivity Timeout – Indication |
Optional |
A.17.1.2 Profile registration
The following description is based on H.248.1 profile registration procedure with some clarifications. The reply to the ServiceChange Request containing the SCP parameter indicates if the MGCF supports the requested profile or if it does not support it and wants to propose an alternative profile. The profile (name and version) is only returned in the reply if the MGCF cannot support the specified profile in the ServiceChangeRequest. The returned reply shall indicate the profile and version supported. Upon reception of a profile in the reply, if the IM-MGW supports the indicated profile, it shall issue a new ServiceChange Request with the agreed profile to explicitly confirm the acceptance of the profile to the MGCF ; otherwise, if the IM-MGW does not support the indicated profile, it may continue the registration or re-registration procedure by issuing a new ServiceChange Request with an alternative profile ; until such procedure is successfully completed the IM-MGW shall remain out of service. If the profile is not returned the MGCF shall use the capabilities specified by the Profile indicated in the service change request.
NOTE: It should be observed that the profile registration is not a "cold calling" negotiation; it is expected that the operator will have configured the network to support certain profiles and so the profile registration within the Mn interface permits network upgrade scenarios but otherwise is simply a means to confirm the connection of the profile to be used over the Mn interface between MGCF and IM-MGW.
A.17.2 IMS Terminations Procedures
A.17.2.1 Summary of Procedures related to a termination towards IM CN Subsystem
Table 1 shows the relationship between each call-related procedure in ITU‑T Recommendation Q.1950 [14] (see 3GPP TS 29.205 [3]) or TS 29.232 [5] and the corresponding stage 2 procedure defined in 3GPP TS 29.163 [4].
Table A.17.2.1/1: Correspondence between ITU-T Recommendation Q.1950 [14] or 29.232 [5] call-related transactions and 3GPP TS 29.163 [4] procedures
|
Procedure defined in 3GPP TS 29.163 [4] |
Transaction used in Q.1950 [14] |
Transaction used in TS 29.232 [5] |
Supported |
Comment |
|
Reserve IMS Connection point |
Not defined |
Not Defined |
Mandatory |
See A.17.2. 2 |
|
Configure IMS Resources |
Not Defined |
Not Defined |
Mandatory |
See A.17.2. 3 |
|
Reserve IMS Connection Point and configure remote resources |
Not defined |
Not Defined |
Mandatory |
See A.17.2. 4 |
|
Release IMS termination |
n. a. for reuse |
Release Termination |
Mandatory |
See A.17.2. 5 |
|
Change IMS ThroughConnection |
n. a. for reuse |
Change Through Connection |
Mandatory |
only the Explicit (MGC Controlled Cut-Through) procedure is supported |
|
Detect IMS RTP Tel Event |
n. a. for reuse |
Detect DTMF |
Optional |
Only applicable if termination towards IMS is connected with a termination towards a BICC network. |
|
End IMS RTP Tel Event |
n. a. for reuse |
Stop Detect DTMF |
Optional |
Only applicable if termination towards IMS is connected with a termination towards a BICC network. |
|
Notify IMS RTP Tel Event |
n. a. for reuse |
Report DTMF |
Optional |
Only applicable if termination towards IMS is connected with a termination towards a BICC network. |
|
Send IMS RTP Tel Event |
n. a. for reuse |
Send DTMF |
FFS |
|
|
Stop IMS RTP Tel Event |
n. a.for reuse |
Stop DTMF |
FFS |
|
|
IMS Send Tone |
n. a. for reuse |
Send Tone |
Optional |
|
|
IMS Stop Tone |
n. a. for reuse |
Stop Tone |
Optional |
|
|
IMS Tone Completed |
n. a. for reuse |
Tone Completed |
Optional |
|
|
Termination heartbeat Indication |
Not defined |
Termination hearbeat Indication |
Mandatory |
To allow detection of hanging contexts and terminations in the MGW that may result e.g. from a loss of communication between the MGCF and the IM-MGW. |
|
IMS Bearer Released |
n. a. for reuse. |
Bearer Released |
Mandatory |
|
|
Request RTCP-Interworking |
Not defined |
Not defined |
Optional |
Only applicable if RTCP AVPF message to feedback on the quality of the media distribution from the IMS side is required to be interworked with corresponding H.245 message towards the CS side. |
|
Notify of RTCP-Interworking |
Not defined |
Not defined |
Optional |
Only applicable if RTCP AVPF message to feedback on the quality of the media distribution from the IMS side is required to be interworked with corresponding H.245 message towards the CS side. |
|
Signal H.245-Interworking |
Not defined |
Not defined |
Optional |
Only applicable if H.245 message to feedback on the quality of the media distribution from the CS side is required to be interworked with corresponding RTCP AVPF messag towards the IMS side. |
|
ECN Failure Indication |
Not defined |
ECN Failure Indication |
Optional |
Only applicable if ECN capability is supported. |
|
ICE Connectivity Check Result Notification |
Not defined |
Optional |
Optional |
See A.17.2.11 Only applicable if full ICE is supported |
|
ICE New Peer Reflexive Candidate Notification |
Not defined |
Optional |
Optional |
See A.17.2.12 Only applicable if full ICE is supported |
|
NOTE 1: A procedure defined in table 13.2.1 can be combined with another procedure in the same table. This means that they can share the same contextID and termination ID(s) and that they can be combined in the same H.248 command. |
||||
A.17.2.2 Reserve IMS Connection Point
When the procedure "Reserve IMS Connection Point" is required the following procedure is initiated:
The MGCF sends an Add.req command with the following information.
1 Add.req (Reserve IMS Connection Point) MGCF to IM-MGW
Table A.17.2.2/1: Reserve IMS Connection Point Request
|
Address Information |
Control information |
Bearer information |
|
Stream ID Local Descriptor { Port = ? IP Address = ? } |
Transaction ID = z Termination ID = ? If Context Requested: Context ID = ? If Context Provided: Context ID = c1 If MPS call/session: Priority Indicator = x If IP Interface Type: IP interface = "IP interface type" If Resources for multiple Codecs shall be reserved: Reserve_Value NotificationRequested (Event ID = x, "termination heartbeat") If indication on Bearer Released requested: NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950 If multiple IP realms: IP realm Identifier = required IP realm identifier If ECN Endpoint support required ECN Enable = "True" Initiation Method = "ECN Initiation Method" If notification of ECN Failure Report: NotificationRequested (Event ID = x,"ECN Failure") If diffserv required: Diffserv Code Point If ICE is applied: STUN server request |
Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If ICE is applied: ICE host candidate request ICE password request ICE Ufrag request ICE pacing request If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Add.resp (Reserve IMS Connection Point Ack)
Table A.17.2.2/2: Reserve IMS Connection Point Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Stream ID Local Descriptor { Port IP Address } |
Transaction ID Termination ID Context ID |
Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If ICE is applied: ICE host candidate ICE password ICE Ufrag ICE pacing If ICE lite implementation ICE lite indication If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
A.17.2.3 Configure IMS Resources
When the procedure "Configure IMS Resources" is required the following procedure is initiated:
The MGCF sends a Mod.req command with the following information.
1 Mod.req (Configure IMS Resources) MGCF to IM-MGW
Table A.17.2.3/1: Configure IMS Resources Request
|
Address Information |
Control information |
Bearer information |
|
If local resources are modified: Stream ID Local Descriptor { Port IP Address } If remote resources are modified: Remote Descriptor { Port IP Address } |
Transaction ID Termination ID Context ID If IP Interface Type: IP interface = "IP interface type"(NOTE 1) If Resources for multiple Codecs shall be reserved: Reserve_Value If ECN Endpoint support required ECN Enable = "True" Initiation Method = "ECN Initiation Method" If notification of ECN Failure Report: NotificationRequested (Event ID = x,"ECN Failure") If full ICE is applied: Send Connectivity Check If notification of ICE Connectivity Check Result Report: NotificationRequested (Event ID= xx, "Connectivity Check Result") If notification of New Peer Reflexive Candidate: NotificationRequested (Event ID = xy," New Peer Reflexive Candidate ") Send Additional Connectivity Check |
If local resources are modified: Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } If remote resources are modified: Remote Descriptor { Codec List RTP Payloads If rate adaptation for media Additional Bandwidth RtcpbwRS RtcpbwRR If RTCP APP messages allowed Allowed RTCP APP message types If ICE is applied: ICE received candidate ICE received password ICE received Ufrag (NOTE 2) ICE received pacing (NOTE 4) If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
|
NOTE 1: If this property is included within the "Reserve IMS Connection Point" procedure or the "Reserve IMS Connection Point and configure remote resource" procedure then it shall not be modified by this procedure. NOTE 2: The support of ICE received candidate, ICE received password, ICE received Ufrag are optional for ICE lite, as specified in 3GPP TS 29.163 [4]. NOTE 3: The support of rate adaptation for media endpoints using the additional bandwidth properties is optional for the IM-MGW. If media transcoding is required the MGCF may provide for the selected payload type and the used IP version the additional bandwidth properties. NOTE 4: The ICE received pacing is only applicable for full ICE, as specified in IETF RFC 8445 [72]. |
||
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Configure IMS Resources Ack)
Table A.17.2.3/2: Configure IMS Resources Acknowledge
|
Address Information |
Control information |
Bearer information |
|
If local resources were provided in request: Stream ID Local Descriptor { Port IP Address } If remote resources were provided in request: Remote Descriptor { Port IP Address } |
Transaction ID Context ID Termination ID |
If local resources were provided in request: Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } If remote resources were provided in request: Remote Descriptor { Codec List RTP Payloads If rate adaptation for media Additional Bandwidth RtcpbwRS RtcpbwRR If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
A.17.2.4 Reserve IMS Connection Point and configure remote resources
When the procedure "Reserve IMS Connection Point and configure remote resources" is required the following procedure is initiated:
The MGCF sends an Add.req command with the following information.
1 Add.req (Reserve IMS Connection Point and configure remote resources) MGCF to IM-MGW
Table A.17.2.4/1: Reserve IMS Connection Point and configure remote resources Request
|
Address Information |
Control information |
Bearer information |
|
Stream ID Local Descriptor { Port = ? IP Address = ? } Remote Descriptor { Port IP Address } |
Transaction ID Termination ID = ? If Context Requested: Context ID = ? If Context Provided: Context ID = c1 If MPS call/session: Priority Indicator = x If IP Interface Type: IP interface = "IP interface type" If Resources for multiple Codecs shall be reserved: Reserve_Value NotificationRequested (Event ID = x, "termination heartbeat") If indication on Bearer Released requested: NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950 If multiple IP realms: IP realm Identifier = required IP realm identifier If ECN Endpoint support required ECN Enable = "True" Initiation Method = "ECN Initiation Method" If notification of ECN Failure Report: NotificationRequested (Event ID = x,"ECN Failure") If diffserv required: Diffserv Code Point If ICE is applied: STUN server request If full ICE is applied Send Connectivity Check notification of ICE Connectivity NotificationRequested (Event Result") If notification of New Peer Reflexive Candidate: NotificationRequested (Event ID = xy," New Peer Reflexive Candidate ") |
Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If ICE is applied: ICE host candidate request ICE password request ICE Ufrag request ICE pacing request If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } Remote Descriptor { Codec List RTP Payloads If rate adaptation for media Additional Bandwidth Properties (NOTE 2) RtcpbwRS RtcpbwRR If RTCP APP messages allowed Allowed RTCP APP message types If ICE is applied: ICE received candidate ICE received password ICE received Ufrag (NOTE 1) ICE received pacing (NOTE 3) If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
|
NOTE 1: The support of ICE received candidate, ICE received password, ICE received Ufrag are optional for ICE lite, as specified in 3GPP TS 29.163 [4]. NOTE 2: The support of rate adaptation for media endpoints using the additional bandwidth properties is optional for the IM-MGW. If media transcoding is required the MGCF may provide for the selected payload type and the used IP version the additional bandwidth properties. NOTE 3: The ICE received pacing is only applicable for full ICE, as specified in IETF RFC 8445 [72]. |
||
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Add.resp (Reserve IMS Connection Point and configure remote resources Ack)
Table A.17.2.4/2: Reserve IMS Connection Point and configure remote resources Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Stream ID Local Descriptor { Port IP Address } Remote Descriptor { Port IP Address } |
Transaction ID Termination ID Context ID |
Stream ID Local Descriptor { Codec List RTP Payloads RtcpbwRS RtcpbwRR If ICE is applied: ICE host candidate ICE password ICE Ufrag ICE pacing If ICE lite implementation ICE lite indication If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } Remote Descriptor { Codec List RTP Payloads If rate adaptation for media Additional Bandwidth Properties RtcpbwRS RtcpbwRR If SDPCapNeg is signalled to the gateway: SDPCapNeg configuration } |
A.17.2.5 VOID
A.17.2.6 Termination heartbeat indication
When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information.
Table A.17.2.6/1: NOT.req (Termination heartbeat) MGW to MGC
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 Event_ID (Event ID = x, "termination heartbeat") |
When the processing of command is complete, the MGC initiates the following procedure.
Table A.17.2.6/2: NOT.resp (Termination heartbeat) MGC to MGW
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 |
The heartbeat timer shall be configured to a value much greater than the mean call holding time.
The MGCF is in charge of correcting any detected mismatch, by substracting hanging terminations or clearing hanging contexts as specified for the hanging termination detection procedure in 3GPP TS 29.163 [4].
A.17.2.7 Request RTCP-Interworking
When the procedure "Request RTCP-Interworking" is required the following procedure is initiated:
the MGCF sends a Mod.req command with the following information.
Table A.17.2.7/1: Request RTCP-Interworking Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 NotificationRequested (Event ID = x, "Incoming RTCP Interworking (RTCP Filter)") |
When the processing of command is complete, the IM-MGW initiates the following procedure.
Table A.17.2.7/2: Request RTCP-Interworking Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 |
A.17.2.8 Notify RTCP-Interworking
When the procedure "Notify RTCP-Interworking" is required the following procedure is initiated:
the IM-MGW sends a NOT.req command with the following information.
Table A.17.2.8/1: Notify RTCP-Interworking Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 if RTCP PLI message received and the interworking required: Update Picture = UpdatePicture_Event if RTCP TMMBR message received and the interworking required: Max BitRate = MaxBitRate_Event |
When the processing of command is complete, the MGCF initiates the following procedure.
Table A.17.2.8/2: Notify RTCP-Interworking Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 |
The MGCF is in charge of sending the corresponding H.245 message to the CS side to request for the media adaption. as specified for the "Interworking between RTCP messages and H.245 messages" in 3GPP TS 29.163 [4].
A.17.2.9 Signal H.245-Interworking
When the procedure "Signal H.245-Interworking" is required the following procedure is initiated:
the MGCF sends a Mod.req command with the following information.
Table A.17.2.9/1: Signal H.245-Interworking Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 if H.245 VideoFastUpdatePicture message received and the interworking required: Interwork H.245-RTCP (UpdatePicture_Signal) if H.245 Flow Control Command received and the interworking required: Interwork H.245-RTCP (MaxBitRate_Signal) |
When the processing of command is complete, the IM-MGW initiates the following procedure.
Table A.17.2.9/2: Signal H.245-Interworking Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 |
The IM-MGW is in charge of constructing and sending the corresponding RTCP message to the IMS side to request for the media adaption as specified for the "Interworking between RTCP messages and H.245 messages" in 3GPP TS 29.163 [4].
A.17.2.10 ECN Failure Indication
The IM-MGWsends a NOTIFY request command as in Table A.17.2.10.1.
Table A.17.2.10.1: ECN Failure Indication
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID= C1 Termination ID = T1 Event_ID (Event ID = x, "ECN Failure (ECN Failure Type ") |
||
The MGCF responds as in Table A.17.2.10.2
Table A.17.2.10.2: ECN Failure Indication Ack
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID = C1 Termination ID = T1 |
A.17.2.11 ICE Connectivity Check Result Notification
The IM-MGW sends a NOTIFY request command as defined in Table A.17.2.11.1.
Table A.17.2.11.1: ICE Connectivity Check Result Notification
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID= C1 Termination ID = T1 Event_ID (Event ID = x, " Connectivity Check Result (Candidate/Transport Pair)") |
The MGCF responds as defined in Table A.17.2.11.2
Table A.17.2.11.2: ICE Connectivity Check Result Notification Ack
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID = C1 Termination ID = T1 |
A.17.2.12 ICE New Peer Reflexive Candidate Notification
The IM-MGW sends a NOTIFY request command as defined in Table A.17.2.12.1.
Table A.17.2.12.1: ICE New Peer Reflexive Candidate Notification
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID= C1 Termination ID = T1 Event_ID (Event ID = x, " New Peer Reflexive Candidate (Candidate)") |
The MGCF responds as defined in Table 5.17.2.12.2
Table A.17.2.12.2: ICE New Peer Reflexive Candidate Ack
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = x Context ID = C1 Termination ID = T1 |
A.17.3 TDM Terminations Procedures
A.17.3.1 Summary Procedures related to a termination towards ISUP
Table A.17.3.1/1: Correspondence between ITU-T Recommendation Q.1950 [14] or 29.232 [5] call-related transactions and 3GPP TS 29.163 [4] procedures related to a termination towards an ISUP network
|
Procedure defined in 3GPP TS 29.163 [4] |
Transaction used in ITU-T Q.1950 [14] |
Transaction used in TS 29.232 [5] |
Support |
Comment |
|
Reserve TDM Circuit |
n. a. for reuse |
n. a. for reuse, (NOTE 2) |
Optional (NOTE 4) |
See Clause A.17.3.2 |
|
Change TDM Through-connection |
n. a. for reuse |
Change Through-connection |
Optional (NOTE 4) |
only the Explicit (MGC Controlled Cut-Through) procedure is supported |
|
Activate TDM voice-processing function |
n. a. for reuse |
Activate Voice Processing Function |
Optional (NOTE 4) |
|
|
Send TDM Tone |
n. a. for reuse |
Send Tone |
Optional (NOTE 4) |
|
|
Stop TDM Tone |
n. a. for reuse |
Stop Tone |
Optional (NOTE 4) |
|
|
TDM Tone Completed |
n. a. for reuse |
Tone Completed |
Optional (NOTE 4) |
|
|
Play TDM Announcement |
n. a. for reuse |
Play Announcement |
Optional (NOTE 4) |
|
|
TDM Announcement Completed |
n. a. for reuse |
Announcement Completed |
Optional (NOTE 4) |
|
|
Stop TDM Announcement |
n. a. for reuse |
Stop Announcement |
Optional (NOTE 4) |
|
|
Continuity Check |
Continuity Check Tone |
n. a. for reuse |
Optional (NOTE 4) |
The addition to "Prepare BNC Notify" defined in Annex B.7.1.1 of Q.1950 [14] shall be applied instead to "Reserve TDM Circuit", as defined in Clause A.17.3.2 |
|
Continuity Check Verify |
Continuity Check Verify |
Continuity Check Verify |
Optional (NOTE 4) |
|
|
Continuity Check Response |
Continuity Check Response |
n. a. for reuse |
Optional (NOTE 4) |
The addition to "Prepare BNC Notify" defined in Annex B.7.1.2 of Q.1950 [14] shall be applied instead to "Reserve TDM Circuit", as defined in Clause A.17.3.2 |
|
Release TDM Termination |
n. a. for reuse |
n. a. for reuse |
Optional (NOTE 4) |
See Clause A.17.3.3 |
|
Termination heartbeat Event |
Not defined |
Termination heartbeat Indication |
Optional |
See Clause A.17.3.4 |
|
Not defined |
Not defined |
TFO Activation |
Optional |
See Clause A.14.21 |
|
Not defined |
Not defined |
Codec Modify |
Optional |
See Clause A.14.21 |
|
Not defined |
Not defined |
Optimal Codec and Distant List_Notify |
Optional |
See Clause A.14.21 |
|
Not defined |
Not defined |
Distant Codec List |
Optional |
See Clause A.14.21 |
|
Not defined |
Not defined |
TFO status Notify |
Optional |
See Clause A.14.21 |
|
Not defined |
Not defined |
TFO status |
Optional |
See Clause A.14.21 |
|
Bearer Released |
n. a. for reuse. |
Bearer Released |
Optional (NOTE 4) |
|
|
NOTE 1: A procedure defined in table 13.2.2 can be combined with another procedure in the same table. This means that they can share the same contextID and termination ID(s) and that they can be combined in the same H.248 command. NOTE 2: The reserve circuit procedure of 29.232 is not to be used only a reduced set of the parameters is required for reserve TDM circuit. NOTE 3: VOID NOTE 4: Required for TDM terminations towards an ISUP based network . |
||||
A.17.3.2 Reserve TDM Circuit
When the procedure "Reserve TDM Circuit" is required the following procedure is initiated:
The MGCF sends an Add.req command with the following information.
Table A.17.3.2/1: Add.req (Reserve TDM Circuit) MGCF to IM-MGW
|
Address Information |
Control information |
Bearer information |
|
Transaction ID Termination ID If Context Requested: Context ID = ? If Context Provided: Context ID = c1 If detection of hanging termination is requested: NotificationRequested (Event ID = x, "termination heartbeat") If indication on Bearer Released requested: NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950 |
Bearer Service Characteristics |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
Table A.17.3.2/2: Add.resp (Reserve TDM Circuit) IM-MGW to MGCF
|
Address Information |
Control information |
Bearer information |
|
Transaction ID Termination ID Context ID |
A.17.3.3 Release TDM Termination
When the procedure "Release TDM Termination" is required the following procedure is initiated:
The MGCF sends an Sub.req command with the following information.
Table A.17.3.3/1: Sub.req (Release TDM Termination) MGCF to IM-MGW
|
Address Information |
Control information |
Bearer information |
|
Transaction ID Termination ID Context ID |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
Table A.17.3.3/2: Sub.resp (Release TDM Termination) IM-MGW to MGCF
|
Address Information |
Control information |
Bearer information |
|
Transaction ID Termination ID Context ID |
A.17.3.4 Termination heartbeat indication
When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information.
Table A.17.3.4/1: NOT.req (Termination heartbeat) MGW to MGC
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 Event_ID (Event ID = x, "termination heartbeat") |
When the processing of command is complete, the MGC initiates the following procedure.
Table A.17.3.4/2: NOT.resp (Termination heartbeat) MGC to MGW
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = bearer1 |
The heartbeat timer shall be configured to a value much greater than the mean call holding time.
The MGCF is in charge of correcting any detected mismatch, by substracting hanging terminations or clearing hanging contexts as specified for the hanging termination detection procedure in 3GPP TS 29.163 [4].
A.17.4 BICC Terminations Procedures
A.17.4.1 Procedures related to a termination towards BICC
Table A.17.4.1/1: Correspondence between ITU-T Recommendation Q.1950 [14] or 3GPP TS 29.232 [5] call-related transactions and 3GPP TS 29.163 [4] procedures related to a termination towards a BICC network
|
Procedure defined in 3GPP TS 29.163 [4] |
Transaction used in Q.1950 [14] |
Transaction used in TS 29.232 [5] |
Support |
Comment |
|
Establish Bearer |
Establish_BNC_Notify |
Establish Bearer (NOTE 1) |
Optional (NOTE 5) |
|
|
Prepare Bearer |
Prepare_BNC_Notify |
Prepare Bearer (NOTE 1), (NOTE 2) |
Optional (NOTE 5) |
|
|
Change Through-Connection |
n. a. for reuse |
Change Through-Connection |
Optional (NOTE 5) |
only the Explicit (MGC Controlled Cut-Through) procedure is supported |
|
Release Bearer |
n. a. for reuse |
Release Bearer |
Optional (NOTE 5) |
(NOTE 3) |
|
Release Termination |
n. a. for reuse |
Release Termination |
Optional (NOTE 5) |
Includes Subtract in the transaction. Statistics about "Ctmbits" are not applicable in Sub.resp |
|
Bearer Established |
n. a. for reuse |
Bearer Established |
Optional (NOTE 5) |
|
|
Bearer Released |
n. a. for reuse |
Bearer Released |
Optional (NOTE 5) |
|
|
Send Tone |
n. a. for reuse |
Send Tone |
Optional (NOTE 5) |
|
|
Stop Tone |
n. a. for reuse |
Stop Tone |
Optional (NOTE 5) |
|
|
Tone Completed |
n. a. for reuse |
Tone Completed |
Optional (NOTE 5) |
|
|
Play Announcement |
n. a. for reuse |
Play Announcement |
Optional (NOTE 5) |
|
|
Stop Announcement |
n. a. for reuse |
Stop Announcement |
Optional (NOTE 5) |
|
|
Announcement Completed |
n. a. for reuse |
Announcement Completed n |
Optional (NOTE 5) |
|
|
Bearer Modification Support |
Not defined |
Bearer Modification Support |
Optional (NOTE 5) |
|
|
Confirm Char |
Confirm_Char |
Confirm Bearer Characterictics (NOTE 1) |
Optional (NOTE 6) |
|
|
Modify Bearer Characteristics |
Modify Char |
Modify Bearer Characteristics (NOTE 1) |
Optional (NOTE 6) |
|
|
Reserve Char |
Reserve_Char_Notify |
Reserve Bearer Characteristics (NOTE 1) |
Optional (NOTE 6) |
|
|
Bearer Modified |
BNC Modified |
Bearer Modified |
Optional (NOTE 6) |
|
|
Activate Voice Processing Function |
n. a. for reuse |
Activate Voice Processing Function |
Optional (NOTE 5) |
|
|
Tunnel Information Down |
Tunnel (MGC-MGW) |
Tunnel Information Down |
Optional (NOTE 7) |
For IP Transport at BICC termination |
|
Tunnel Information Up |
Tunnel (MGW-MGC) |
Tunnel Information Up |
Optional (NOTE 7) |
For IP Transport at BICC termination |
|
Termination heartbeat |
Not defined |
Termination heartbeat indication |
Mandatory |
|
|
Not defined |
Not defined |
TFO Activation |
Optional |
|
|
Not defined |
Not defined |
Codec Modify |
Optional |
|
|
Not defined |
Not defined |
Optimal Codec and Distant List_Notify |
Optional |
|
|
Not defined |
Not defined |
Distant Codec List |
Optional |
|
|
Not defined |
Not defined |
TFO status Notify |
Optional |
|
|
Not defined |
Not defined |
TFO status |
Optional |
|
|
NOTE 1: The procedure is only applicable if the Nb framing protocol is applied at the BICC termination. Only requesting of Observed events defined in the corresponding TS 29.232 and parameters defined in the "3GUP" package of TS 29.232 are applicable in addition the parameters of the corresponding Q.1950 procedure. Those parameters shall be applies as follows: UP mode = Supported mode; UP versions = 2; interface = CN; NOTE 2: Parameters and Observed events defined for Cellular Text telephone Modem Text Transport in the corresponding procedure of TS 29.232 are not applicable. NOTE 3: VOID NOTE 4: VOID NOTE 5: Necessary for optional terminations towards BICC NOTE 6: Optional for optional terminations towards BICC NOTE 7: Necessary for optional terminations towards BICC network with IP transport |
||||
A.17.5 Multiplex Termination Procedures
A.17.5.1 Procedures related to a Multiplex termination
Table A.17.5.1/1: Correspondence between ITU-T Recommendation Q.1950 [14] or 3GPP TS 29.232 [5] call-related transactions and 3GPP TS 29.163 [4] procedures related to a multiplex termination
|
Procedure defined in 3GPP TS 29.163 [4] |
Transaction used in Q.1950 [14] |
Transaction used in TS 29.232 [5] |
Support |
Comment |
|
Add Multiplex Termination |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.2 |
|
Configure Multiplex Termination |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.3 |
|
Signal H245 Message |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.4 |
|
Notify H245 message |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.5 |
|
Notify MONA Preference Reception |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.6 |
|
Notify MONA Preference Completed |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.7 |
|
Signal SPC |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.8 |
|
Notify SPC |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.9 |
|
Notify MPC |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.10 |
|
Notify Detection of Legacy Interworking |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.11 |
|
Stop MPC |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.12 |
|
Stop SPC |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.13 |
|
Stop MONA Negotiation |
Not defined |
Not defined |
Optional (NOTE 1) |
See A.17.5.14 |
|
NOTE 1: Necessary for interworking of multimedia calls |
||||
A.17.5.2 Add Multiplex Termination
When the procedure "Add Multiplex Termination" is required the following procedure is initiated:
The MGCF sends an Add.req command with the following information.
1 Add.req (Add Multiplex Termination) MGCF to IM-MGW
Table A.17.5.2/1: Add Multiplex Termination Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = ? Muxdescriptor If MONA procedures not supported: NotificationRequested (Event ID = x, "Incoming H245 message") f MONA procedures supported: NotificationRequested (Event ID = x, "Incoming H245 message (SPC=Both)") NotificationRequested (Event ID = x, "termination heartbeat") If indication on Bearer Released requested: NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU‑T Recommendation Q.1950 If MONA procedures supported: Signal = Outgoing MONA preferences (Outgoing MONA preference content) (NOTE) NotificationRequested (Event ID = x, "MONA Preference recv") NotificationRequested (Event ID = x, "MONA Preference completed") NotificationRequested (Event ID = x, "Legacy Interworking Detected" (Signal = Outgoing H245 message (Outgoing H.245 message content) ) ) NotificationRequested (Event ID = x, "Mona Preference Channel reception") Signal = Forward media in MPC (MPC MUX Code) Incoming Multiplex Table |
||
|
NOTE: The frequent retransmissions of MONA preference messages required by MONA procedures are to be performed by the IM-MGW autonomously to avoid unnecessary load at the Mn interface and the MGCF. |
||
On receipt of this procedure, and the setting of the muxdescriptor, the IM-MGW shall initiate the H.324 negotiation, with connection mode H.324M and predefined Highest Multiplexing Level.
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Add.resp (Add Multiplex Termination Ack)
Table A.17.5.2/2: Add Multiplex Termination Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.3 Configure Multiplex Termination
When the procedure "Configure Multiplex Termination" is required the following procedure is initiated:
The MGCF sends an Mod.req command with the following information.
1 Mod.req (Configure Multiplex Termination) MGCF to IM-MGW
Table A.17.5.3/1: Configure Multiplex Termination Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 If MONA completed or MONA not supported: Remote H223 Capability Incoming Multiplex table Outgoing Multiplex table If MONA MPC sending is requested: Signal = Forward media in MPC (MPC MUX Code) |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Configure Multiplex Termination Ack)
Table A.17.5.3/2: Configure Multiplex Termination Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.4 Signal H245 Message
When the procedure "Signal H245 Message" is required the following procedure is initiated:
The MGCF sends an Mod.req command with the following information.
1 Mod.req (Signal H245 Message) MGCF to IM-MGW
Table A.17.5.4/1: Signal H245 Message Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Signal = Outgoing H245 message (Outgoing H.245 message content) |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Signal H245 Message Ack)
Table A.17.5.4/2: Signal H245 Message Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.5 Notify H.245 Message
When the procedure "Notify H.245 message" is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify H245 Message) IM-MGW to MGCF
Table A.17.5.5/1: Notify H245 Message Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "Incoming H245 message (H245 message content)") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify H245 Message Ack) MGCF to IM-MGW
Table A.17.5.5/2: Notify H245 Message Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.6 Notify MONA Preference Reception
When the procedure "Notify MONA Preference Reception" is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify MONA Preference Reception) IM-MGW to MGCF
Table A.17.5.6/1: Notify MONA Preference Reception Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "MONA Preference recv (MONA preference message content)") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify MONA Preference Reception) MGCF to IM-MGW
Table A.17.5.6/2: Notify MONA Preference Reception Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.7 Notify MONA Preference Completed
When the procedure "Notify MONA Preference Completed" is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify MONA Preference Completed) IM-MGW to MGCF
Table A.17.5.7/1: Notify MONA Preference Completed Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "MONA Preference completed ") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify MONA Preference Completed) MGCF to IM-MGW
Table A.17.5.7/2: Notify MONA Preference Completed Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.8 Signal SPC
When the procedure "Signal SPC" is required the following procedure is initiated:
The MGCF sends an Mod.req command with the following information.
1 Mod.req (Signal SPC) MGCF to IM-MGW
Table A.17.5.8/1: Signal SPC Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Signal = Outgoing H245 message (Outgoing H.245 message content, SPC Out=ON) |
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Signal SPC Ack)
Table A.17.5.8/2: Signal SPC Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.9 Notify SPC
When the procedure "Notify SPC" is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify SPC) IM-MGW to MGCF
Table A.17.5.9/1: Notify SPC Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "(Incoming H245 message (H245 message content, SPC In=ON)") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify SPC Ack) MGCF to IM-MGW
Table A.17.5.9/2: Notify SPC Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.10 Notify MPC
When the procedure "Notify MPC" is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify MPC) IM-MGW to MGCF
Table A.17.5.10/1: Notify MPC Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "(Mona Preference Channel reception (Muxcode)") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify MPC Ack) MGCF to IM-MGW
Table A.17.5.10/2: Notify MPC Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.11 Notify Detection of Legacy Interworking
When the procedure "Notify Detection of Legacy Interworking " is required the following procedure is initiated: the IM-MGW sends a NOT.req command with the following information.
1 Not.req (Notify Detection of Legacy Interworking) IM-MGW to MGCF
Table A.17.5.11/1: Notify Detection of Legacy Interworking Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Event_ID (Event ID = x, "Legacy Interworking Detected ") |
When the processing of command is complete, the MGCF initiates the following procedure.
2 Not.resp (Notify Detection of Legacy Interworking ) MGCF to IM-MGW
Table A.17.5.11/2: Notify Detection of Legacy Interworking Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.12 Stop MPC
When the procedure "Stop MPC" is required the following procedure is initiated:
The MGCF sends an Mod.req command with the following information.
1 Mod.req (Stop MPC) MGCF to IM-MGW
Table A.17.5.12/1: Stop MPC Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Signal = x, NOTE 1 NotificationRequested (Event ID = x, NOTE 2 ) |
||
|
NOTE 1: The signal descriptor shall not include the "Forward media in MPC" signal. NOTE 2: The event descriptor shall not include the "Mona Preference Channel reception" event. |
||
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Stop MPC Ack)
Table A.17.5.12/2: Stop MPC Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.13 Stop SPC
When the procedure "Stop SPC" is required the following procedure is initiated:
The MGCF sends a Mod.req command with the following information.
1 Mod.req (Stop SPC) MGCF to IM-MGW
Table A.17.5.13/1: Stop SPC Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 If legacy H.245 or accelerated H.245 required: Signal = Outgoing H245 message (Outgoing H.245 message content, SPC Out=OFF) NotificationRequested (Event ID = x, "Incoming H245 message (SPC=H245)") NOTE 3 If legacy H.245 or accelerated H.245 not required: Signal = x, NOTE 1 NotificationRequested (Event ID = x, NOTE 2 ) |
||
|
NOTE 1: The signal descriptor shall not include the "Outgoing H.245 message" signal. NOTE 2: The event descriptor shall not include the "Incoming H.245 message" event. NOTE 3: SPC parameter may be omitted, as SPC=H245 is the default value. |
||
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Stop SPC Ack)
Table A.17.5.13/2: Stop SPC Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.5.14 Stop MONA Negotiation
When the procedure "Stop MONA negotiation" is required the following procedure is initiated:
The MGCF sends a Mod.req command with the following information.
1 Mod.req (Stop MONA Negotiation) MGCF to IM-MGW
Table A.17.5.14/1: Stop MONA Negotiation Request
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 Signal = x, NOTE 1 NotificationRequested (Event ID = x, NOTE 2 ) If legacy H.245 or accelerated H.245 required: Signal = Outgoing H245 message (Outgoing H.245 message content, SPC Out=OFF) NotificationRequested (Event ID = x, "Incoming H245 message (SPC=H245)") NOTE 3 |
||
|
NOTE 1: The signal descriptor shall not include any of the signals "Outgoing MONA preferences" and "Forward media in MPC". If legacy H.245 or accelerated H.245 is not required the signal descriptor shall also not include the "Outgoing H.245 message" signal. NOTE 2: The event descriptor shall not include any of the events "MONA Preference recv", "MONA Preference completed" and "Mona Preference Channel reception". If legacy H.245 or accelerated H.245 is not required the event descriptor shall also not include the "Incoming H.245 message" event. NOTE 3: SPC parameter may be omitted, as SPC=H245 is the default value. |
||
When the processing of command (1) is complete, the IM-MGW initiates the following procedure.
2 Mod.resp (Stop MONA Negotiation Ack)
Table A.17.5.14/2: Stop MONA Negotiation Acknowledge
|
Address Information |
Control information |
Bearer information |
|
Transaction ID = z Context ID = c1 Termination ID = mux1 |
A.17.6 SIP-I on Nc Terminations Procedures
A.17.6.1 Summary of Procedures related to a termination towards SIP-I on Nc CN Subsystem
The interworking between IMS domain and SIP-I on Nc is specified by 3GPP TS 29.235 [47] which requires the procedures for SIP-I on Nc as specified in 3GPP TS 23.231 [48] Clause 15.2.
Table A.17.6.1/1 shows the relationship between each call-related procedure in ITU‑T Recommendation Q.1950 [14] (see 3GPP TS 29.205 [3]) or TS 29.232 [5] and the corresponding stage 2 procedure defined in 3GPP TS 23.231 [48].
Table A.17.6.1/1: Correspondence between ITU-T Recommendation Q.1950 [14] or 29.232 [5] call-related transactions and 3GPP TS 23.231 [48] procedures
|
Procedure defined in 3GPP TS 23.231 [48] |
Transaction used in Q.1950 [14] |
Transaction used in TS 29.232 [5] |
Supported |
Comment |
|
Reserve RTP Connection Point |
Not defined |
Reserve RTP Connection Point (NOTE 2) |
Optional (NOTE1) |
See A.17.2. 2 |
|
Configure RTP Connection Point |
Not Defined |
Configure RTP Connection Point (NOTE 2) |
Optional (NOTE1) |
See A.17.2. 3 |
|
Reserve and Configure RTP Connection Point |
Not defined |
Reserve and Configure RTP Connection Point (NOTE 2) |
Optional (NOTE1) |
See A.17.2. 4 |
|
Release Termination |
n. a. for reuse |
Release Termination |
Mandatory |
Includes Subtract in the transaction. Statistics about "Ctmbits" are not applicable in Sub.resp |
|
Change Through-Connection |
n. a. for reuse |
Change Through-Connection |
Optional (NOTE 1) |
only the Explicit (MGC Controlled Cut-Through) procedure is supported |
|
Bearer Released |
n. a. for reuse |
Bearer Released |
Optional (NOTE 1) |
|
|
Send Tone |
n. a. for reuse |
Send Tone |
Optional (NOTE 1) |
|
|
Stop Tone |
n. a. for reuse |
Stop Tone |
Optional (NOTE 1) |
|
|
Tone Completed |
n. a. for reuse |
Tone Completed |
Optional (NOTE 1) |
|
|
Play Announcement |
n. a. for reuse |
Play Announcement |
Optional (NOTE 1) |
|
|
Stop Announcement |
n. a. for reuse |
Stop Announcement |
Optional (NOTE 1) |
|
|
Announcement Completed |
n. a. for reuse |
Announcement Completed n |
Optional (NOTE 1) |
|
|
Activate Voice Processing Function |
n. a. for reuse |
Activate Voice Processing Function |
Optional (NOTE 1) |
|
|
Termination heartbeat |
Not defined |
Termination heartbeat indication |
Mandatory |
|
|
Not defined |
Not defined |
TFO Activation |
Optional |
|
|
Not defined |
Not defined |
Codec Modify |
Optional |
|
|
Not defined |
Not defined |
Optimal Codec and Distant List_Notify |
Optional |
|
|
Not defined |
Not defined |
Distant Codec List |
Optional |
|
|
Not defined |
Not defined |
TFO status Notify |
Optional |
|
|
Not defined |
Not defined |
TFO status |
Optional |
|
|
NOTE 1: Mandatory for connections towards SIP-I on Nc. NOTE 2: The existing IMS Connection Point Procedures are functionally similar to these 29.232 procedures as they were derived from the IMS ones. |
||||
Annex B (normative):
Void
Annex C (normative):
Void
Annex D (informative):
Change history
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New |
|
2004-09 |
CN#25 |
Approved in CN#25 |
6.0.0 |
||||
|
2005-03 |
CN#27 |
NP-050045 |
001 |
1 |
Introduction Of Formal Profile |
6.1.0 |
|
|
002 |
1 |
Corrections to Mn Specification |
|||||
|
2005-06 |
CT#28 |
CP-050208 |
0001 |
4 |
Introduction Of Formal Profile |
6.2.0 |
|
|
CP-050208 |
0005 |
Inclusion of Insert Digit Procedure at IMS termination |
|||||
|
2005-09 |
CT#29 |
CP-050442 |
0007 |
3 |
Alignment of Mn Profile with ITU template and Mc interface decisions |
6.3.0 |
|
|
CP-050454 |
0008 |
3 |
Alignment of Mn Profile with TISPAN TMGW |
7.0.0 |
|||
|
2005-12 |
CT#30 |
CP-050630 |
0015 |
3 |
Clean-up of hanging contexts and terminations |
7.1.0 |
|
|
CP-050619 |
0017 |
1 |
Addition of TFO procedure |
||||
|
CP-050630 |
0019 |
2 |
Add virtual media gateway function |
||||
|
CP-050619 |
0022 |
Alignment with TISPAN |
|||||
|
CP-050619 |
0023 |
Open Mn |
|||||
|
2006-03 |
CT#31 |
CP-060077 |
0024 |
1 |
Add the UDPTL/TCPTL transport and mediatype for T.38 |
7.2.0 |
|
|
CP-060077 |
0026 |
2 |
Clarification the SDP used in the BICC termination |
||||
|
CP-060077 |
0028 |
Remove the redundant symbols |
|||||
|
CP-060066 |
0030 |
1 |
Bearer Released Event to Reserve TDM Circuit procedure |
||||
|
CP-060066 |
0032 |
1 |
BICC packages in Mn profile |
||||
|
CP-060066 |
0034 |
Service Change Method "Disconnected" and "Failover" removal from Service Changes sent by MGCF |
|||||
|
2006-06 |
CT#32 |
CP-060314 |
0037 |
1 |
Alignment with TISPAN TGW profile |
7.3.0 |
|
|
CP-060306 |
0036 |
1 |
Corrections to Mn Specification for Inter Vendor Operability |
||||
|
0041 |
Update of Mn profile with packages defined in 29.232 |
||||||
|
0044 |
1 |
Adding of Bearer Released Event to Procedures related to a termination towards IM CN Subsystem |
|||||
|
0046 |
1 |
Mode-change-period support on Mn interface |
|||||
|
2006-09 |
CT#33 |
CP-060401 |
0048 |
1 |
AuditValue procedure |
7.4.0 |
|
|
CP-060410 |
0051 |
Alignment Mn towardsTISPAN Endorsement |
|||||
|
CP-060410 |
0052 |
2 |
Removal of duplicated functionality in body of specification |
||||
|
CP-060401 |
0053 |
1 |
Definition of the use of mandatory and optional in Mn Profile Template |
||||
|
CP-060401 |
0054 |
1 |
Missing Procedures Towards IMS |
||||
|
CP-060410 |
0055 |
2 |
Correction to Terminations chapter |
||||
|
CP-060401 |
0058 |
1 |
Corrections to Profile Description: Descriptors |
||||
|
CP-060401 |
0060 |
Corrections to Profile Description: Command API |
|||||
|
CP-060401 |
0062 |
1 |
Corrections to Profile Description: Packages |
||||
|
2006-12 |
CT#34 |
CP-060570 |
0068 |
1 |
Alignment of Mn towards TISPAN Endorsement |
7.5.0 |
|
|
CP-060570 |
0069 |
1 |
Setting of 3GPP manadatory parameters to conditional |
||||
|
CP-060570 |
0074 |
CR miss implementation Call independent procedures and packages |
|||||
|
CP-060570 |
0075 |
2 |
Removal of TBD for Number of Commands Per Transaction |
||||
|
CP-060570 |
0080 |
Missing Procedures Towards IMS |
|||||
|
CP-060725 |
0071 |
1 |
Profile registration procedure |
||||
|
CP-060725 |
0073 |
2 |
Rules for SDP equivalents |
||||
|
CP-060725 |
0077 |
3 |
Codec Parameters |
||||
|
2007-03 |
CT#35 |
CP-070013 |
0081 |
1 |
Further Alignment of Mn Towards TISPAN Endorsement |
7.6.0 |
|
|
2007-06 |
CT#36 |
CP-070323 |
0087 |
1 |
Addition of missing references and text corrections |
7.7.0 |
|
|
CP-070434 |
0088 |
3 |
Multimedia interworking Mn procedures |
||||
|
CP-070323 |
0089 |
1 |
Wrong implementation of CP-060401 / C4-060998 (CR 0048r1 29.332 Rel-7) |
||||
|
CP-070315 |
0091 |
RFC 3309 for SCTP checksum |
|||||
|
2007-09 |
CT#37 |
CP-070538 |
0092 |
1 |
Corrections to Multimedia Interworking |
7.8.0 |
|
|
0094 |
3 |
Service Change Methods and Reasons |
|||||
|
0095 |
Correction to Package Ids |
||||||
|
0097 |
Priority Indicator in Context Attributes |
||||||
|
0099 |
1 |
H.248 Message Encoding |
|||||
|
0101 |
2 |
Correction to Reuse of Procedures |
|||||
|
0103 |
1 |
Correction to Signals Descriptor |
|||||
|
0105 |
1 |
Correction to Events Descriptor |
|||||
|
0107 |
1 |
Clarification of Message Identifier |
|||||
|
010 |
1 |
IP realm connection indication |
|||||
|
011 |
2 |
Correction of parameter in Sending H.245 Message |
|||||
|
0112 |
2 |
Mn profile corrections |
|||||
|
0117 |
1 |
Corrections to maxptime syntax in SDP of encoding of AMR codec |
|||||
|
2007-12 |
CT#38 |
CP-070742 |
0123 |
1 |
Properties returned in commands |
7.9.0 |
|
|
CP-070746 |
0119 |
1 |
Inactivity timout procedures – Alignment to Mc profile |
||||
|
CP-070746 |
0125 |
1 |
Audit of individual TDM terminations |
||||
|
2007-12 |
CT#38 |
CP-070757 |
0118 |
Termination heartbeat – Alignment to Mc profile |
8.0.0 |
||
|
2008-03 |
CT#39 |
CP-080023 |
0126 |
IP version in SDP_C |
8.1.0 |
||
|
CP-080012 |
0129 |
1 |
Correction on the Mn profile: BNC Release event |
||||
|
2008-06 |
CT#40 |
CP-080272 |
0130 |
Updating Mn interface profile "threegimscsiw" to version 3 |
8.2.0 |
||
|
2008-09 |
CT#41 |
CP-080469 |
0131 |
2 |
Mona H.248 package definitions |
8.3.0 |
|
|
CP-080454 |
0134 |
Service Change Reason in (G)MSC Server Out of Service |
|||||
|
2008-12 |
CT#42 |
CP-080704 |
0135 |
1 |
Mona H.248 package definitions update |
8.4.0 |
|
|
CP-080704 |
0136 |
Mn profile update for Mona H.248 package definitions |
|||||
|
CP-080701 |
0137 |
1 |
Clarification of RTCP messages usage in the interworking gateways |
||||
|
CP-080686 |
0138 |
3 |
Alignment of stage 3 MGCF-IM_MGW protocol with Stage 2 for SIP-I on Nc interworking to IMS |
||||
|
2009-03 |
CT#43 |
CP-090031 |
0139 |
1 |
Mn profile update for H.245 and RTCP Interactions H.248 package definitions |
8.5.0 |
|
|
0140 |
Updating H.248.12 amendment 2 to reference list |
||||||
|
2009-06 |
CT#44 |
CP-090298 |
0141 |
1 |
Update of stage 3 MONA to newest H.248.72 (ex. H.248.MONA) draft |
8.6.0 |
|
|
0142 |
Update of MONA stage 3 due to MONA procedures stage 2 changes |
||||||
|
2009-12 |
CT#46 |
CP-090967 |
0147 |
Correction to Profile for Commands marked optional |
8.7.0 |
||
|
CP-090763 |
0148 |
Commands Using IP Interface Type |
|||||
|
2009-12 |
CT#46 |
Upgraded unchanged from Rel-8 |
9.0.0 |
||||
|
2010-03 |
CT#47 |
CP-100028 |
0152 |
MONA H.248 package update |
9.1.0 |
||
|
CP-100028 |
0154 |
1 |
ASN.1 encoding of RTCP Feedback Message package |
||||
|
CP-100028 |
0157 |
MONA alignments to H.324 |
|||||
|
CP-100037 |
0150 |
1 |
Global Text Telephony Interworking between IMS and Circuit Switched |
||||
|
CP-100037 |
0155 |
1 |
Resolution of External TISPAN Referencing |
||||
|
2010-09 |
CT#47 |
CP-100450 |
0159 |
– |
ITU-T H.248.71 and H.248.72 publication |
9.2.0 |
|
|
2011-03 |
CT#51 |
CP-110276 |
0160 |
10 |
ECN Support in Mn Interface |
10.0.0 |
|
|
CP-110070 |
0161 |
1 |
Complete Inactivity Timeout Indication Procedure |
||||
|
CP-110058 |
0163 |
1 |
Handling of rtcp-fb SDP attribute and SDP attribute for RTCP APP feedback messages |
||||
|
2011-06 |
CT#52 |
CP-110352 |
0168 |
1 |
Missing Tone Completed procedures |
10.1.0 |
|
|
CP-110368 |
0165 |
1 |
ECN Failure improvements |
||||
|
CP-110368 |
0170 |
1 |
Alignment of 3GPP profiles with SG16 ECN package definition |
||||
|
2011-09 |
CT#53 |
CP-110568 |
0171 |
1 |
Solving Incorrect references |
10.2.0 |
|
|
2011-12 |
CT#54 |
CP-110798 |
0172 |
– |
Explicit Congestion Notification |
||
|
CP-110789 |
0173 |
1 |
Reference update: 26.114 |
10.3.0 |
|||
|
2012-06 |
CT#56 |
CP-120226 |
0175 |
1 |
Reference update: draft-ietf-avtcore-ecn-for-rtp |
10.4.0 |
|
|
Editorial fix to history table |
10.4.1 |
||||||
|
2012-09 |
CT#57 |
CP-120443 |
0181 |
– |
Reference alignment for RTP Payload Format for AMR and AMR-WB Audio Codecs |
10.5.0 |
|
|
2012-09 |
CT#57 |
CP-120478 |
0176 |
3 |
Support of Multimedia Priority Service (MPS) over Mn Interface – Stage 3 |
11.0.0 |
|
|
CP-120684 |
0178 |
1 |
Support of T.38 related SDP attributes |
||||
|
2012-12 |
CT#58 |
CP-120723 |
0185 |
– |
Mn interface updates of ECN Support Package |
11.1.0 |
|
|
CP-120738 |
0186 |
– |
T.38 default version |
||||
|
2013-03 |
CT#59 |
CP-130013 |
0192 |
1 |
Support of RTCP-FB for MTSI |
11.2.0 |
|
|
2013-06 |
CT#60 |
CP-130294 |
0188 |
2 |
ECN relying reference change |
11.3.0 |
|
|
2014-06 |
CT#64 |
CP-140248 |
0193 |
2 |
ICE support in Mn interface |
12.0.0 |
|
|
2014-06 |
CT#66 |
CP-140788 |
0194 |
1 |
Adding support for EVS codec |
12.1.0 |
|
|
2015-09 |
CT#69 |
CP-150430 |
0196 |
1 |
Correction on SDP for Real-Time Text |
13.0.0 |
|
|
2016-03 |
CT#71 |
CP-160048 |
0197 |
– |
Removal of references to TS 26.236 |
13.1.0 |
|
|
2016-03 |
CT#71 |
CP-160034 |
0198 |
1 |
Support of enhanced bandwidth negotiation mechanism for MTSI sessions |
13.1.0 |
|
|
2016-03 |
CT#71 |
CP-160021 |
0199 |
1 |
Mn stage 3 to support SDP Capability Negotiation |
13.1.0 |
|
|
2016-06 |
CT#72 |
CP-160229 |
0200 |
– |
Rate adaptation clarification |
13.2.0 |
|
|
2016-06 |
CT#72 |
CP-160229 |
0201 |
– |
Clarifications related to the rate adaptation for media endpoints |
13.2.0 |
|
|
2017-03 |
CT#75 |
– |
– |
– |
Update to Rel-14 version (MCC) |
14.0.0 |
|
|
2018-06 |
CT#80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
CT#88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
CT#95e |
CP-220052 |
0202 |
– |
B |
Update of IETF references for ICE |
17.0.0 |