Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.885  Word version:  11.0.0

Top   Top   Up   Prev   None
1…   5…

 

5  Architecture model and reference pointsp. 10

6  Solutionsp. 12

6.1  Solution 1: Session transfer initiated on E-UTRAN/HSPAp. 12

6.2  Solution 2: Session transfer initiated on E-UTRAN/HSPAp. 20

6.3  Solution 3+5: Media anchoring in serving network with Access Transfer Control Functionalityp. 25

6.3.1  Architecture Reference Modelp. 25

6.3.2  Functional Entitiesp. 26

6.3.3  Message Flowsp. 28

6.3.3.1  General principlesp. 28

6.3.3.2  GERAN/UTRAN Attach procedurep. 29

6.3.3.3  E-UTRAN attach procedurep. 29

6.3.3.3a  Informing the source RAN about the possibility to perform rSRVCCp. 29

6.3.3.4  Codec and transport address related procedurep. 30

6.3.3.5  Establish a session over CSp. 30

6.3.3.6  CS - PS Access Transfer Overviewp. 33

6.3.3.7  Access Transfer Preparationp. 34

6.3.3.8  IMS Session Continuity procedurep. 45

6.3.3.9  Identification of serving PS nodep. 48

6.3.4  IMS registration Considerationsp. 50

6.4  Solution 4: Session transfer by local anchoring with Indirect Forwardingp. 53

6.5  Solution 5: IMS procedure is initiated by MSC Server to ATCFp. 59

7  Assessment of the solutionsp. 73

8  Conclusionp. 77

A  Mechanisms to re-enable E-UTRAN capabilityp. 78

B  Mechanisms for GERAN/UTRAN sending Handover/Relocation Required messagep. 82

$  Change historyp. 83


Up   Top