Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.859 Word version: 12.0.1

1… 4…

4 Requirements p. 8

4.1 Scenarios p. 8

4.1.1 General p. 8

4.1.2 Scenarios for SIPTO at the local network p. 8

4.1.2.1 Scenario 1: PDN connection subject to Per APN SIPTO@LN when UE is attached or handed over to a local network supporting SIPTO@LN p. 8

4.1.2.2 Scenario 2: Per APN SIPTO@LN PDN connection status when UE moves out of a local network supporting SIPTO@LN p. 9

4.2 Architectural requirements p. 9

5 Solutions p. 10

5.1 General p. 10

5.2 Support of LIPA mobility p. 10

5.2.1 Key issue #L1: Architecture for LIPA mobility p. 10

5.2.1.1 Architecture solution 1: Stand-alone logical L-GW p. 10

5.2.1.1.1 Overall description p. 10

5.2.1.1.2 Architecture description when Sxx is user plane only p. 13

5.2.1.1.3 Architecture solution 1 variant 2: control plane Sxx p. 14

5.2.1.2 Architecture solution 2: Standalone L-GW on the S1/Iuh path p. 14

5.2.1.2.1 Architecture description p. 14

5.2.1.2.2 Architectural details for the LTE/3G architecture p. 15

5.2.2 Key issue #L2: L-GW selection and addressing p. 16

5.2.2.1 General description p. 16

5.2.2.2 L-GW selection and addressing for Architecture solution 1 (Stand-alone logical L-GW) p. 17

5.2.2.2.1 General p. 17

5.2.2.2.2 Stand-alone L-GW selection p. 17

5.2.2.2.3 Signalling the L-GW@LN address/FQDN and TEID to the H(e)NB p. 17

5.2.2.2.4 Signalling the H(e)NB@LN local address/FQDN and TEID to L-GW p. 18

5.2.2.2.5 Signalling the L-GW@CN address to the SGSN/MME p. 18

5.2.2.2.6 Description of the DNS-based and RAN-based alternatives p. 19

5.2.3 Key issue #L3: Discovery of the LIPA mobility area p. 21

5.2.3.1 Description of the key issue p. 21

5.2.3.2 Option 1: using the L-GW@CN address for architecture solution 1 (Stand-alone logical L-GW) p. 22

5.2.3.2.1 General p. 22

5.2.3.2.2 Handover decision p. 22

5.2.3.2.3 LIPA bearer handling p. 22

5.2.3.3 Option 2: using the LHN-ID for architecture solution 1 (Stand-alone logical L-GW) p. 23

5.2.3.3.1 General p. 23

5.2.3.3.2 LIPA PDN connection management p. 23

5.2.4 Key issue #L4: LIPA deactivation p. 23

5.2.4.1 General p. 23

5.2.4.2 Solutions p. 24

5.2.5 Key issue #L5: H(e)NB providing LIPA support indication to UE p. 24

5.2.5.1 General description p. 24

5.2.5.2 Solution 1: UE configuration p. 24

5.2.5.3 Solution 2: NAS signalling p. 24

5.2.5.4 Solution 3: RRC signalling p. 24

5.2.5.5 Evaluation p. 24

5.2.6 Key issue #L6: Criteria for LIPA activation for the MME/SGSN p. 24

5.2.6.1 General Assumptions p. 24

5.2.6.2 Solution p. 25

5.3 SIPTO above the RAN p. 25

5.3.1 Key issue #S1: Principles for session continuity for SIPTO above the RAN p. 25

5.4 SIPTO at the local network p. 25

5.4.1 Key issue #SL1: Principles for session continuity for SIPTO at the local network p. 25

5.4.1.1 Solution 1: per APN SIPTO@LN re-using Rel-10 SIPTO above the RAN procedures p. 25

5.4.2 Key issue #SL2: SIPTO at the local network permission p. 26

5.4.2.1 General description p. 26

5.4.2.2 Solution 1 p. 26

5.4.2.3 Solution 2 p. 26

5.4.2.4 Evaluation p. 27

5.4.3 Key issue #SL3: Criteria for per APN SIPTO@LN activation by the network p. 27

5.4.3.1 General Assumptions p. 27

5.4.3.2 Solution 1 - per APN SIPTO@LN based on SIPTO@LN indication & APN support p. 27

5.4.4 Key issue #SL4: Architecture for SIPTO@LN p. 28

5.4.4.1 General p. 28

5.4.4.2 Architecture Solution 1: Reusing SIPTO@ above RAN (Standalone GW) p. 28

5.4.4.3 Architecture Solution 2: Reusing LIPA Mobility Architecture 1 p. 30

5.4.4.4 Architecture Solution 3: Reusing Rel-10 LIPA Architecture p. 31

5.4.4.5 Evaluation p. 33

6 Conclusions p. 33

A Evaluation of mobility procedure impacts for architecture 1 p. 34

A.1 Sxx user-plane only Option 1 p. 34

A.1.1 Setup of local connection p. 34

A.1.1.1 E-UTRAN p. 34

A.1.1.2 UTRAN p. 35

A.1.2 Handovers within the local network p. 35

A.1.2.1 X2 handover within enterprise / local network (E-UTRAN) p. 35

A.1.2.2 Intra HNB GW mobility within enterprise / local network (UTRAN) p. 36

A.1.3 S1 handover within enterprise / local network p. 37

A.1.4 S1/Iu release p. 38

A.1.4.1 S1 release p. 38

A.1.4.2 Iu release p. 39

A.1.5 Service request p. 39

A.1.5.1 E-UTRAN p. 39

A.1.5.2 UTRAN p. 40

A.2 Sxx user-plane only Option 2 p. 40

A.2.1 General p. 40

A.2.2 Connection management procedure p. 40

A.2.2.1 LIPA PDN connection establishment p. 40

A.2.2.2 UE triggered Service Request procedure p. 42

A.2.2.3 Network triggered Service Request procedure p. 43

A.2.2.4 S1-Release procedure p. 43

A.2.3 Mobility management procedure p. 43

A.2.3.1 Idle state mobility management procedure p. 43

A.2.3.2 Connected state mobility management procedure p. 44

A.2.3.2.1 Option 1: MME control method p. 44

A.2.3.2.1.1 X2 based handover procedure p. 44

A.2.3.2.1.2 S1 based handover procedure p. 45

A.2.3.2.2 Option 2: HeNB in the target side control method p. 46

A.2.3.2.2.1 X2 based handover procedure p. 46

A.2.3.2.2.2 S1 based handover procedure p. 48

A.2.3.3 Connected state mobility management procedure-Iurh handover p. 49

A.3 Sxx control plane and user plane p. 49

B Architectural details for architecture option 2, standalone L-GW on Iuh/S1 path p. 59

B.1 3G HNB architecture p. 59

B.1.1 Functional entities p. 59

B.1.1.1 HNB Management System (HMS) p. 59

B.1.1.2 Security Gateway (SeGW) p. 59

B.1.1.3 HNB Gateway (HNB-GW) p. 59

B.1.1.4 HNB p. 59

B.1.1.5 Standalone L-GW on Iuh path p. 60

B.1.2 Protocol stacks p. 60

B.1.2.1 Control plane protocol stack p. 60

B.1.2.2 User plane protocol stack p. 61

B.1.3 Procedures p. 61

B.1.3.1 Standalone L-GW registration p. 61

B.1.3.2 HNB registration in case of a L-GW on the Iuh path p. 62

B.1.3.3 UE registration p. 63

B.1.3.4 LIPA PDP Context Activation procedure p. 64

B.1.3.5 LIPA PDP Context Deactivation procedure p. 64

B.1.3.6 HNB to HNB Mobility via Iurh p. 64

B.1.3.7 O&M Provisioning procedure for L-GW p. 66

B.1.3.8 O&M Provisioning procedure for HNB p. 66

$ Change history p. 68