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  TS 23.402  Word version:  18.3.0

Top   Top   Up   Prev   Next
0…   4…   4.2…   4.2.2   4.2.3   4.3…   4.4…   4.5…   4.5.7…   4.6…   4.7…   4.7.2…   4.8…   4.8.2a…   4.9…   5…   5.2…   5.4…   5.5   5.6…   5.7…   5.8…   6…   6.2…   6.3   6.4…   6.4.3…   6.5…   6.6…   6.7…   6.8…   6.10…   6.13…   6.15…   7…   7.2…   7.3   7.4…   7.5…   7.6…   7.8…   7.10…   8…   8.2.1.2   8.2.1.3…   8.2.2   8.2.3…   8.2.6…   8.3…   8.4…   8.5…   9…   9.3…   9.4…   10…   13…   16…   16.1.2…   16.1.6…   16.2…   16.2.1a…   16.3…   16.4…   16.7…   16.8…   16.10…   17…   A…   C…   E… 
16.7 Detach in WLAN on S2a for Multi-connection Mode  16.7.1 Detach in WLAN on GTP S2a  16.7.2 Detach in WLAN on PMIP S2a 
...

 

16.7  Detach in WLAN on S2a for Multi-connection Mode |R12|  p. 283

16.7.1  Detach in WLAN on GTP S2a  p. 283

16.7.1.1  UE/TWAN Initiated Detach Procedure in WLAN on GTP S2a  p. 283

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 16.7.1.1-1: UE/TWAN-Initiated Detach in WLAN on GTP S2a
Figure 16.7.1.1-1: UE/TWAN-Initiated Detach in WLAN on GTP S2a
(⇒ copy of original 3GPP image)
Up
The procedure is similar to in clause 16.3.1.1, with the following differences:
  • Step1: To detach from EPC, the UE can send a disassociation or deauthentication notification according to IEEE Std 802.11-2012 [64]. If there is no traffic received from the UE for a configurable duration and the TWAN detects the UE has left based on unanswered probes (e.g. ARP Request, Neighbor Solicitation message), the TWAN initiates the detach procedure.
  • Step 2 to Step 5 refers to clause 16.9.1.
  • In the case of connectivity with multiple PDNs, the steps 2 to 5 are repeated for each PDN the UE is connected to.
Up

16.7.1.2  HSS/AAA Initiated Detach Procedure in WLAN on GTP S2a  p. 284

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 16.7.1.2-1: HSS/AAA-Initiated Detach in WLAN on GTP S2a
Figure 16.7.1.2-1: HSS/AAA-Initiated Detach in WLAN on GTP S2a
(⇒ copy of original 3GPP image)
Up
The procedure is similar to in clause 16.3.1.2, with the following differences:

16.7.2  Detach in WLAN on PMIP S2a  p. 284

16.7.2.1  UE/TWAN Initiated Detach Procedure in WLAN on PMIP S2a  p. 284

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 16.7.2.1-1: UE/TWAN Initiated Detach in WLAN on PMIP S2a
Figure 16.7.2.1-1: UE/TWAN Initiated Detach in WLAN on PMIP S2a
(⇒ copy of original 3GPP image)
Up
The procedure is similar to GTP based S2a call flows in clause 16.7.1.1, with the following differences:
  • Step 2 is a Proxy Binding Update. The details of the Proxy Binding Update message are described in step 3 in clause 6.4.1.1. Additionally, the Proxy Binding Update includes the current TWAN Identifier as described in clause 16.1.7, the Timestamp of this TWAN-Identifier and the UE Time Zone.
  • Step 5 is a Proxy Binding Acknowledgement. The details of the Proxy Binding Acknowledgement message are described in step 6 in clause 6.4.1.1.
Up

16.7.2.2  HSS/AAA Initiated Detach Procedure in WLAN on PMIP S2a  p. 285

Copy of original 3GPP image for 3GPP TS 23.402, Fig. 16.7.2.2-1: HSS/AAA Initiated Detach in WLAN on PMIP S2a
Figure 16.7.2.2-1: HSS/AAA Initiated Detach in WLAN on PMIP S2a
(⇒ copy of original 3GPP image)
Up
The procedure is similar to GTP S2a call flow in clause 16.3.1.2, the difference is that step 2 refers to Figure 16.7.2.1-1.
Up

Up   Top   ToC