Content for TR 23.886 Word version: 10.0.0
5 Architecture model and reference points
6 Key Issues
7 Assessment of the solutions
8 Conclusion
$ Change history
5 Architecture model and reference points p. 8
5.1 General p. 8
5.2 Reference architecture p. 8
5.3 Impact on functional entities p. 9
5.3.1 UE p. 9
5.3.2 eNode-B/Node-B p. 9
5.3.3 MME/SGSN p. 9
5.3.4 MSC Server enhanced for vSRVCC p. 9
5.3.5 SCC AS p. 9
5.4 Reference points p. 10
6 Key Issues p. 10
6.1 Key issue 1: Video Codec negotiation p. 10
6.1.1 Alternative 1- Two step approach for transferring video-call with vSRVCC p. 10
6.1.1.1 Functional description p. 10
6.1.1.2 Information flows p. 11
6.1.1.3 Evaluation of the alternative p. 11
6.1.2 Alternative 2: 3G-324M pre-negotiation scheme for vSRVCC domain transfer p. 12
6.1.2.1 Functional description p. 12
6.1.2.2 Information flows p. 13
6.1.2.3 Evaluation of the alternative p. 14
6.1.3 Alternative 3: Two step procedure with UE initiated multimedia call establishment (without need of SCUDIF) p. 14
6.1.3.1 Functional description p. 14
6.1.3.2 Information flows p. 15
6.1.3.3 Evaluation of the alternative p. 17
6.1.4 Alternative 4: Basic approach for transferring video-call with vSRVCC p. 17
6.1.4.1 Functional description p. 17
6.1.4.2 Information flow p. 18
6.1.4.3 Evaluation of the alternative p. 19
6.1.5 Alternative 5: Consolidated approach for transferring video-call with vSRVCC p. 19
6.1.5.1 Functional description p. 19
6.1.5.2 Information flow p. 21
6.1.5.3 Evaluation of the alternative p. 23
6.1.6 Alternative 6: IMS based 3G-324M pre-negotiation scheme for vSRVCC domain transfer p. 23
6.2 Key issue 2: Bearer identification for vSRVCC handover p. 27
6.2.1 Alternative 1: Using dedicated QCI for the video bearer associated with a video call application p. 27
6.2.2 Alternative 2: Using bearer correlation method p. 28
6.2.2.1 Functional description p. 28
6.2.2.2 Information flows p. 29
6.2.2.3 Evaluation of the alternative p. 30
6.2.3 Alternative 3: Not requiring bearer identification for vSRVCC p. 30
6.3 Key issue 3: Requirement for vSRVCC indication towards the MME and the MSC server p. 31
7 Assessment of the solutions p. 32
8 Conclusion p. 32
$ Change history p. 33
