Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.704  Word version:  13.0.0

Top   Top   Up   Prev   Next
1…   5…   6…

 

5  Scenariosp. 10

5.1  CS Handover to UTRAN/GERAN Scenariosp. 10

5.2  PS Handover to UTRAN/GERAN Scenariosp. 22

5.2.1  GERAN MOCN, non-DTM, no combined update proceduresp. 22

5.2.2  Pool Centric: PS Handover to GERAN with no DTM support, user is SGs registered in the target network, no change of MSC poolp. 23

5.2.3  Operator Centric: PS Handover to a GERAN without DTM support, user is SGs registered in the target networkp. 24

5.2.4  GERAN MOCN, non-DTM combined update proceduresp. 25

5.2.5  GERAN GWCN, non-DTM, no combined update proceduresp. 26

5.2.6  GERAN GWCN, non-DTM, combined update proceduresp. 28

5.2.7  UTRAN/GERAN MOCN, no combined update proceduresp. 29

5.2.8  Pool Centric: PS Handover to UTRAN or GERAN with DTM support, user is SGs registered in the target network, no change of MSC poolp. 30

5.2.9  Operator Centric: PS Handover to a UTRAN or GERAN with DTM support, user is SGs registered in the target networkp. 31

5.2.10  UTRAN/GERAN MOCN, combined update proceduresp. 31

5.2.11  UTRAN/GERAN GWCN, no combined update proceduresp. 32

5.2.12  UTRAN/GERAN GWCN, combined update proceduresp. 34

5.3  SRVCC with SGs registration scenariosp. 35

5.4  CS Fallback scenariosp. 35

5.5  PLMN selection at handover based on UE capabilityp. 44

5.5.1  PLMN selection at handover to GERAN based on UE capabilityp. 45

5.5.2  PLMN selection at handover from E-UTRAN to UTRAN based on UE capabilityp. 45

5.5.3  PLMN selection at handover from UTRAN/GERAN to UTRAN, based on UE capability.p. 46

5.5.3.1  General descriptionp. 46

5.5.3.2  PLMN selection at concurrent CS and PS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, non-combined update procedurep. 47

5.5.3.3  PLMN selection at concurrent CS and PS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, combined update procedurep. 49

5.5.3.4  PLMN selection at concurrent CS and PS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, non-combined update procedurep. 50

5.5.3.5  PLMN selection at concurrent CS and PS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, combined update procedurep. 52

5.5.3.6  PLMN selection at PS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, non-combined update procedurep. 55

5.5.3.7  PLMN selection at PS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, combined update procedurep. 57

5.5.3.8  PLMN selection at PS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, non-combined update procedurep. 58

5.5.3.9  PLMN selection at PS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, combined update procedurep. 60

5.5.3.10  PLMN selection at CS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, non-combined update procedurep. 62

5.5.3.11  PLMN selection at CS handover from UTRAN/GERAN to UTRAN, based on UE capability, MOCN, combined update procedurep. 64

5.5.3.12  PLMN selection at CS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, non-combined update procedurep. 66

5.5.3.13  PLMN selection at CS handover from UTRAN/GERAN to UTRAN, based on UE capability, GWCN, combined update procedurep. 68

5.6  Concurrent CS and PS Handover from UTRAN/GERAN to UTRAN/GERAN Scenariosp. 70

5.7  Cell reselection scenariosp. 78

5.8  Redirection scenariosp. 82

5.9  EUTRAN to UTRAN/GERAN mobility for SGs registered and non-SGs registered users scenariop. 86

5.10  PS Attach after CS mobilityp. 96


Up   Top   ToC