E.2 Gateway Relocation with MIPv4 FACoA on S2a

23.4023GPPArchitecture enhancements for non-3GPP accessesRelease 18TS

Figure E.2-1: Gateway Relocation when MIPv4 FACoA mode MM mechanism is used over S2a

When the Gateway Relocation procedure occurs in the Non-Roaming case (Figure 4.2.2-1), the vPCRF is not involved.

In the case of Roaming (Figure 4.2.3-1) and Local Breakout (Figure 4.2.3-4), the vPCRF is employed to forward messages from the hPCRF in the home PLMN, by way of the vPCRF in the VPLMN to the non-3GPP access.

1) A gateway relocation is triggered, to be initiated by the UE. This trigger is outside the scope of 3GPP standardization.

2) The UE sends a Registration Request (RRQ) RFC 5944 [12] message to the FA. Reverse Tunnelling shall be requested. This ensures that all traffic will go through the PDN GW. The RRQ message shall include the NAI-Extension RFC 2794 [34] and the Home Agent Address.

3) The Trusted non-3GPP access initiates the Gateway Control Session Establishment Procedure with the PCRF, as specified in TS 23.203 [19]. The Trusted non-3GPP access provides the information to the PCRF to correctly associate it with the IP CAN session to be established in Step 9 and also to convey subscription related parameters to the PCRF.

4) The FA processes the message according to RFC 5944 [12] and forwards a corresponding RRQ message to the PDN GW.

5) The PDN GW allocates an IP address for the UE and sends a Registration Reply (RRP) RFC 5944 [12] to the FA, including the IP address allocated for the UE.

6) The Trusted Non-3GPP Access Network initiates the Gateway Control Session Termination Procedure with the PCRF as specified in TS 23.203 [19]. The Trusted Non-3GPP Access Network no longer applies QoS policy to service data flows for this UE.

7) The FA processes the RRP according to RFC 5944 [12] and sends a corresponding RRP message to the UE.

8) IP connectivity from the UE to the PDN GW is now setup. A MIP tunnel is established between the FA in the Trusted Non-3GPP IP Access and the PDN GW.

Annex F (informative):
Deployment of Non-3GPP Trusted WLAN Access on S2a

WLAN networks may be deployed such that separate SSIDs are used for EPC-routed and non-seamless WLAN offload, e.g. <ssid_a> and <ssid_b>.

WLAN networks may also be deployed such that the same SSID in a WLAN Access Point provides different type of network access to different users attached to this Access Point. For example, a given SSID <ssid_x> may provide EPC-routed access for subscriber A and only allow non-seamless WLAN offload for subscriber B. In such a deployment it is up to the operator to provide network configuration that supports different user access preferences, subscriptions and UE configurations.

It is recommended that the UE can be configured to apply different behavior when connected to different SSIDs, e.g. allow or prevent the usage of certain applications on specific SSIDs. For example, for the SSIDs used for EPC access through S2a over Trusted WLAN, the UE can be configured to disable applications that require local connectivity (e.g. DLNA applications) and enable applications that require EPC connectivity to the default APN used for access through S2a over Trusted WLAN. Such kind of special behavior for SSIDs used for EPC access through S2a over Trusted WLAN can improve the user experience and prolong the UE battery life.

NOTE: A UE can be configured to apply different behavior when connected to different SSIDs by means which are outside the scope of this document. For example, the UE can be configured over-the-air, by means of a downloadable application, or manually.

Annex G (informative):
Change History

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2014-12

SP-66

SP-140693

1329

2

B

TWAN release cause for Trusted WLAN

13.0.0

2015-03

SP-67

SP-150027

1339

1

B

GTP-C overload control from TWAN/ePDG to PGW

13.1.0

2015-03

SP-67

SP-150020

1342

1

A

SPExclusionList in WLANSP

13.1.0

2015-03

SP-67

SP-150027

1343

2

B

Support prefix delegation in PMIP-based S5/S8

13.1.0

2015-03

SP-67

SP-150027

1344

2

F

PMIP Prefix Delegation reference correction

13.1.0

2015-03

SP-67

SP-150016

1346

1

A

Adding description of missing S2a system architecture alternative

13.1.0

2015-03

SP-67

SP-150027

1355

1

F

Removing incorrect references to I-WLAN specifications

13.1.0

2015-03

SP-67

SP-150020

1356

A

Prioritized PreferredSSIDList

13.1.0

2015-06

SP-68

SP-150239

1360

1

F

Clarification of Impacts when Gxx is not used for eHRPD Access

13.2.0

2015-06

SP-68

SP-150239

1366

2

F

Session/bearer release cause over S2b

13.2.0

2015-09

SP-69

SP-150503

1368

3

B

ePDG selection for emergency bearer services

13.3.0

2015-09

SP-69

SP-150503

1380

2

B

Introduction of the Support of Emergency services over WLAN access to EPC

13.3.0

2015-09

SP-69

SP-150505

1376

4

C

Revision of ePDG selection procedures

13.3.0

2015-12

SP-70

SP-150613

1391

2

F

Corrections to ePDG selection

13.4.0

2015-12

SP-70

SP-150613

2902

F

Correction to handover between ePDGs

13.4.0

2015-12

SP-70

SP-150613

2906

5

F

Supporting Location reporting for IMS sessions over S2b.

13.4.0

2015-12

SP-70

SP-150602

2908

1

A

Clarification of S2a architecture

13.4.0

2015-12

SP-70

SP-150617

2909

1

F

Conveying to the EPC the IMEI of devices accessing a trusted or untrusted WLAN

13.4.0

2015-12

SP-70

SP-150613

2910

2

F

Transfer of User Location Information at Create Session Request over S2b

13.4.0

2015-12

SP-70

SP-150613

2912

2

F

ePDG supporting emergency services only

13.4.0

2015-12

SP-70

SP-150613

2916

4

F

Keeping WLAN Location Information up to date

13.4.0

2015-12

SP-70

SP-150615

2917

2

B

Addition of LWA support

13.4.0

2015-12

SP-70

SP-150615

2918

2

B

Addition of CRLWI support

13.4.0

2015-12

SP-70

SP-150615

2920

4

C

Corrections to ePDG selection procedure

13.4.0

2015-12

SP-70

SP-150615

2921

1

F

Clarifications on the ePDG Delete Session procedure

13.4.0

2016-03

SP-71

SP-160162

2922

4

F

Clarification on ANDSF precedence

13.5.0

2016-03

SP-71

SP-160160

2925

1

F

Correction to ePDG selection for emergency bearer services

13.5.0

2016-03

SP-71

SP-160160

2926

F

Sending an Emergency-Indication to the 3GPP AAA Server over S6b

13.5.0

2016-03

SP-71

SP-160162

2933

3

C

Updated ePDG Selection Procedure

13.5.0

2016-03

SP-71

SP-160162

2934

3

F

Coexistence between ANDSF and LWA

13.5.0

2016-06

SP-72

SP-160285

2928

2

A

Clarification on TWAN authorization

13.6.0

2016-06

SP-72

SP-160298

2941

1

F

Correction of UICC precedence

13.6.0

2016-06

SP-72

SP-160298

2942

2

F

Corrections for ePDG selection fallback

13.6.0

2016-06

SP-72

SP-160298

2943

1

F

Corrections to ePDG selection procedure for UE determined location

13.6.0

2016-06

SP-72

SP-160300

2944

1

B

IMEI check for EPC access via untrusted WLAN

14.0.0

2016-06

SP-72

SP-160300

2945

2

B

IMEI check for EPC access via trusted WLAN

14.0.0

2016-06

SP-72

SP-160301

2948

1

B

Support of EAP Re-authentication for WLAN Interworking

14.0.0

2016-06

SP-72

SP-160302

2949

4

B

Revision of S2b GTP procedure for ES for UE without valid IMSI

14.0.0

2016-06

SP-72

SP-160302

2950

1

B

Introduction of ES based on FS_SEW2 results

14.0.0

2016-06

SP-72

SP-160300

2951

1

F

IMEI check for S2b GTP

14.0.0

2016-06

SP-72

SP-160302

2952

1

B

Determining Location and Country for IMS Emergency Session over WLAN access

14.0.0

2016-06

SP-72

SP-160302

2953

1

B

User identification for emergency services over WLAN

14.0.0

2016-06

SP-72

SP-160302

2955

2

C

ePDG Selection for Emergency Services

14.0.0

2016-09

SP-73

SP-160644

2956

A

Source TCP port provided over S2b

14.1.0

2016-09

SP-73

SP-160652

2958

2

F

Clarifications of ePDG Selection for Emergency Services

14.1.0

2016-09

SP-73

SP-160652

2961

3

F

Initial Attach procedure for ES for S2a GTP

14.1.0

2016-09

SP-73

SP-160652

2964

2

B

Support of emergency services when UE attached to regular services for untrusted WLAN

14.1.0

2016-09

SP-73

SP-160652

2965

2

B

Introduction of emergency services for trusted WLAN and roaming cases

14.1.0

2016-09

SP-73

SP-160652

2966

4

B

Support of emergency services continuity between WLAN and 3GPP access

14.1.0

2016-12

SP-74

SP-160817

2967

3

F

Correction of emergency services continuity between WLAN and 3GPP access

14.2.0

2017-03

SP-75

SP-170047

2969

F

Conditions for issuing emergency session via WLAN

14.3.0

2017-06

SP-76

SP-170367

2970

1

F

Emergency sessions in trusted WLAN with unauthenticated UE

14.4.0

2017-06

SP-76

SP-170363

2975

1

A

PGW selection for WLAN with deployed DCNs

14.4.0

2017-06

SP-76

SP-170377

2971

3

B

Support for e2e QoS over untrusted WLAN

15.0.0

2017-06

SP-76

SP-170377

2972

3

B

Support for e2e QoS over trusted WLAN

15.0.0

2017-09

SP-77

SP-170731

2976

2

F

Support for multiple bearers in a single request

15.1.0

2017-09

SP-77

SP-170721

2978

1

A

Solving ambiguities on whether to consider UEs without UICC

15.1.0

2017-12

SP-78

SP-170923

2979

F

Correction to ePDG handling of multiple IPSEC SA for untrusted WLAN

15.2.0

2017-12

SP-78

SP-170919

2980

1

B

OI#19 – 5GC-EPC interworking: PGW selection for 5GC UE for connectivity via untrusted access

15.2.0

2017-12

SP-78

SP-170916

2982

A

ePDG and TWAN emergency configuration data

15.2.0

2017-12

SP-78

SP-170919

2983

3

B

Transfer of PCO over untrusted acess

15.2.0

2018-03

SP-79

SP-180094

2984

B

Enabling ePDG selection using 5GS TAI information

15.3.0

2018-03

SP-79

SP-180087

2986

A

Emergency ePDG selection for UE without UICC

15.3.0

2018-03

SP-79

SP-180083

2990

A

Correction to 4G non-3GPP location issue

15.3.0

2019-06

SP-84

SP-190399

2994

1

F

Moving 5GS Interworking aspects to 5GS Specifications

16.0.0

2021-03

SP-91E

SP-210087

2996

1

D

Inclusive language review

17.0.0

2022-12

SP-98E

SP-221087

2997

1

B

Support of Non-3GPP access for SNPN

18.0.0