Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 29.863
Word version: 8.2.0
1…
2…
2
References
3
Definitions and abbreviations
4
Basic Multimedia calls inter-working between the IMS and CS Networks scenarios
5
Control plane inter-working
6
User plane interworking
7
MGCF and IM-MGW interactions
8
Conclusions and recommendations
$
Change history
2
References
p. 7
3
Definitions and abbreviations
p. 8
3.1
Definitions
p. 8
3.2
Abbreviations
p. 9
4
Basic Multimedia calls inter-working between the IMS and CS Networks scenarios
p. 9
4.1
Overview of Relevant CS-Domain Protocols
p. 9
4.2
Overview of Relevant PS-Domain Protocols
p. 10
5
Control plane inter-working
p. 11
5.1
General
p. 11
5.2
Functionalities required in the MGCF for multimedia calls support
p. 11
5.3
IM CN subsystem originated session
p. 11
5.3.1
Preconditions used at IMS side
p. 11
5.3.1.1
Interactions between H.245 or MONA and SIP/SDP
p. 11
5.3.1.2
Early media at the CS side through-connected
p. 13
5.3.1.2.1
Void
5.3.1.2.2
Void
5.3.1.3
Early media at the CS side not through-connected
p. 14
5.3.1.3.1
BICC with SCUDIF
p. 14
5.3.1.3.2
Non-SCUDIF case (ISUP or BICC without SCUDIF)
p. 15
5.3.2
Preconditions not used at IMS side
p. 17
5.3.2.1
Interactions between H.245 or MONA and SIP/SDP
p. 17
5.3.2.2
Early media at the CS side through-connected
p. 19
5.3.2.2.1
Void
5.3.2.2.2
Void
5.3.2.3
Early media at the CS side not through-connected
p. 20
5.3.2.3.1
BICC with SCUDIF
p. 20
5.3.2.3.2
Non-SCUDIF case (ISUP or BICC without SCUDIF)
p. 21
5.4
CS network originated session
p. 23
5.4.1
Interactions between SIP/SDP and H.245 or MONA
p. 23
5.4.1.1
Normal Call setup
p. 23
5.4.1.2
Call setup if multimedia call can not be recognized in an unambiguous manner
p. 24
5.4.2
Preconditions used by IMS terminal
p. 24
5.4.2.1
Early media at the CS side through-connected
p. 24
5.4.2.1.1
Void
5.4.2.1.2
Void
5.4.2.2
Early media at the CS side not through-connected
p. 25
5.4.2.2.1
BICC with SCUDIF
p. 25
5.4.2.2.2
Non-SCUDIF case (ISUP or BICC without SCUDIF)
p. 26
5.4.3
Preconditions not used by IMS terminal
p. 28
5.4.3.1
Early media at the CS side through-connected
p. 28
5.4.3.1.1
Void
5.4.3.1.2
Void
5.4.3.2
Early media at the CS side not through-connected
p. 29
5.4.3.2.1
BICC with SCUDIF
p. 29
5.4.3.2.2
Non-SCUDIF case (ISUP or BICC without SCUDIF)
p. 30
5.4.4
CS originated - IM CN transit - CS terminated
p. 32
5.5
Service change
p. 33
5.5.1
SCUDIF
p. 33
5.5.1.1
IM CN subsystem originated change
p. 33
5.5.1.1.1
Change from multimedia to speech
p. 33
5.5.1.1.2
Change from speech to multimedia
p. 34
5.5.1.2
CS network originated change
p. 35
5.5.1.2.1
Change from multimedia to speech
p. 35
5.5.1.2.2
Change from speech to multimedia
p. 35
5.5.2
Non-SCUDIF case (ISUP or BICC without SCUDIF)
p. 36
5.5.2.1
Change from multimedia to speech
p. 36
5.5.2.2
Change from speech to multimedia
p. 37
5.6
Call release
p. 38
5.6.1
Call release initiated from the IM CN subsystem side
p. 38
5.6.2
Call release initiated from the CS network side
p. 39
5.6.3
Call release initiated from the interworking node
p. 39
6
User plane interworking
p. 40
6.1
Functionalities required in the IM-MGW for multimedia calls support
p. 40
7
MGCF and IM-MGW interactions
p. 40
7.1
H.248 Context Model
p. 40
7.1.1
Context model comparison
p. 42
7.1.1.1
Context with separate H.248 RTP Terminations (T3 + T4)
p. 42
7.1.1.2
Context with combined H.248 RTP Termination (T3)
p. 42
7.1.1.3
Comparison conclusion
p. 43
7.2
H.245 Termination at the IM-MGW
p. 43
7.2.1
Conveying H.245 related information over the Mn interface
p. 43
7.2.1.1
Call establishment procedure
p. 43
7.2.1.2
Procedure of H.245 indication message
p. 45
7.2.1.2.1
Function Not Understood / Function Not Supported message
p. 45
7.2.1.2.2
Jitter Indication message
p. 46
7.2.1.2.3
User Input Indication message
p. 46
7.2.1.3
Procedure of H.245 Command message
p. 47
7.2.1.3.1
Flow control command
p. 47
7.2.1.3.2
End Session Command
p. 48
7.2.1.4
Advantages of H.245 Termination at the IM-MGW and Conveying H.245 related information over the Mn interface
p. 48
7.2.1.5
Mn procedure for ending the H.245 session
p. 49
7.2.1.5.1
H.245 session end initiated from the MGCF
p. 49
7.2.1.5.2
H.245 session end initiated from the CS network side
p. 49
7.2.2
Conveying selected H.245 messages over the Mn interface
p. 49
7.2.2.1
Conclusion on this proposal
p. 50
7.2.3
Mn packages
p. 50
7.3
H.245 Termination at the MGCF
p. 50
7.3.1
Transport of H.245 messages between the MGCF and IM-MGW
p. 50
7.3.1.1
Conveying H.245 messages over the Mn interface
p. 50
7.3.1.1.1
From MGCF to IM-MGW
p. 50
7.3.1.1.2
From IM-MGW to MGCF
p. 51
7.3.1.2
Conveying H.245 messages using separate SCTP association
p. 51
7.3.1.3
Comparison conclusion
p. 51
7.3.2
Mn packages
p. 51
7.3.3
Procedure for H.245 termination at the MGCF
p. 52
7.3.3.1
Call establishment procedure
p. 52
7.3.3.2
Procedure of H.245 indication message
p. 54
7.3.3.2.1
Function Not Understood / Function Not Supported message
p. 54
7.3.3.2.2
Jitter Indication message
p. 55
7.3.3.2.3
User Input Indication message
p. 55
7.3.3.3
Procedure of H.245 Command message
p. 56
7.3.3.3.1
Flow control command
p. 56
7.3.3.3.2
End Session Command
p. 57
7.3.3.4
Advantages of H.245 termination at the MGCF
p. 58
7.3.3.5
Mn procedure for ending the H.245 session
p. 58
7.4
Media Oriented Negotiation Acceleration (MONA)
p. 58
7.4.1
Overview
p. 58
7.4.2
Mn Interactions for MONA preference messages
p. 60
7.4.3
Mn Interactions for MONA MPCs
p. 63
7.4.4
Mn Interactions for MONA SPCs
p. 64
7.4.4.1
General
p. 64
7.4.4.2
Transport from MGCF to IM-MGW
p. 64
7.4.4.3
Transport from IM-MGW to MGCF
p. 65
7.4.5
Mn Interactions for fallback from MONA procedures to standard H.324 setup
p. 66
8
Conclusions and recommendations
p. 67
$
Change history
p. 68