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 points

6  Solutions

6.1  Solution 1: Session transfer initiated on E-UTRAN/HSPA

6.2  Solution 2: Session transfer initiated on E-UTRAN/HSPAWord‑p. 20

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

6.3.1  Architecture Reference Model

6.3.2  Functional EntitiesWord‑p. 26

6.3.3  Message Flows

6.3.3.1  General principles

6.3.3.2  GERAN/UTRAN Attach procedureWord‑p. 29

6.3.3.3  E-UTRAN attach procedure

6.3.3.3a  Informing the source RAN about the possibility to perform rSRVCC

6.3.3.4  Codec and transport address related procedureWord‑p. 30

6.3.3.5  Establish a session over CS

6.3.3.6  CS - PS Access Transfer OverviewWord‑p. 33

6.3.3.7  Access Transfer Preparation

6.3.3.8  IMS Session Continuity procedureWord‑p. 45

6.3.3.9  Identification of serving PS nodeWord‑p. 48

6.3.4  IMS registration ConsiderationsWord‑p. 50

6.4  Solution 4: Session transfer by local anchoring with Indirect ForwardingWord‑p. 53

6.5  Solution 5: IMS procedure is initiated by MSC Server to ATCFWord‑p. 59

7  Assessment of the solutionsWord‑p. 73

8  ConclusionWord‑p. 77

A  Mechanisms to re-enable E-UTRAN capabilityWord‑p. 78

B  Mechanisms for GERAN/UTRAN sending Handover/Relocation Required messageWord‑p. 82

$  Change historyWord‑p. 83


Up   Top