Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.402  Word version:  18.3.0

Top   Top   None   None   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…

 

0  Introductionp. 11

Guidance to Readers of this Specification
In order to reduce the number of procedures in this specification certain editorial practices have been adopted. Though there are many independent factors, such as variants of S5/S8/S2b and attachment cases, these are in essence quite similar. So, rather than presenting the permutations of these factors separately and thereby needlessly repeating normative text, conventions have been adopted to combine this information in single procedures.
The S5 and S8 reference points in the EPC architecture have been defined to have both a GTP and PMIP variant. The GTP variant is documented in TS 23.401, while the PMIP variant is documented in this specification. Every effort has been made to eliminate duplication of normative text common to both specifications. Many figures in this specification refer to procedures in TS 23.401 to achieve this end. Common procedures between TS 23.401 and TS 23.402 (this specification), are represented in this specification in figures by text in shaded box(es) that reference the appropriate figure and steps in TS 23.401. The details of the common steps are only captured in TS 23.401.
The S2b reference point in the EPC architecture has also been defined to have both a GTP and PMIP variant. Both variants are documented in this specification. Every effort has been made to eliminate duplication of normative text common to both variants. Figures for the GTP variant of S2b refer to figures defined for the PMIP variant of S2b to achieve this end. Common procedures for both variants are represented in figures for GTP based S2b by text in shaded box(es) that reference the appropriate figure and steps defined for PMIP based S2b. The details of the common steps are only captured for the PMIP variant of S2b.
Attachment cases (as discussed in clauses 6.2.1 and 7.2.1) have been combined in a single figure. The different attachment cases can be accommodated by including optional items in the flows, for instance, a vPCRF that is only employed during when a roaming case or LBO is specified.
Multiple APN interactions may occur for many of the procedures defined in this specification. These interactions complicate the flows by introducing certain operations that may occur multiple times. Rather than produce unique flows for this purpose, we indicate where this possibility may occur in text.
Up

1  Scopep. 12

This document specifies the stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP Packet Switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the Evolved 3GPP PS Domain where the protocols between its Core Network elements are IETF-based.
ITU-T Recommendation I.130 [2] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [3] defines stage 2 of the method.
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses.
TS 23.401 covers architecture aspects common to the Evolved 3GPP Packet Switched domain.
The procedures defined in the present document for WLAN access selection and PLMN selection replace the corresponding I-WLAN procedures specified in TS 23.234.
Interworking with 5GS is only supported for untrusted non-3GPP access using GTP-based S2b. Enhancements to support interworking with 5GS are captured in TS 23.501 and TS 23.502.
The WLAN Selection Policy specified in clause 4.8.2.1.6 also covers UEs operating in SNPN access mode as defined in TS 23.501.
Up

2  Referencesp. 12

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
ITU-T Recommendations I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
[3]
ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities".
[4]
TS 23.401: "General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[5]
TS 23.234: "3GPP System to Wireless Local Area Network (WLAN) Interworking; System Description".
[6]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description Stage 2".
[7]  Void.
[8]
RFC 5213:  "Proxy Mobile IPv6".
[9]
RFC 7296:  "Internet Key Exchange Protocol Version 2 (IKEv2)".
[10]
RFC 5555:  "Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)".
[11]
RFC 3748:  "Extensible Authentication Protocol (EAP)".
[12]
RFC 5944:  "IP Mobility Support for IPv4, revised".
[13]  Void.
[14]  Void.
[15]
RFC 4282:  "The Network Access Identifier".
[16]
TS 23.003: "Numbering, addressing and identification".
[17]
RFC 5844:  "IPv4 Support for Proxy Mobile IPv6".
[18]
RFC 4555:  "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
[19]
TS 23.203: "Policy and Charging Control Architecture".
[20]
TS 22.278: "Service requirements for evolution of the system architecture".
[21]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[22]
RFC 4877:  "Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture".
[23]
RFC 2784:  "Generic Routing Encapsulation (GRE)".
[24]
RFC 2890:  "Key and Sequence Number Extensions to GRE".
[25]
RFC 3543:  "Registration Revocation in Mobile IPv4".
[26]  Void.
[27]  Void.
[28]
RFC 2131:  "Dynamic Host Configuration Protocol".
[29]
RFC 4039:  "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)".
[30]
RFC 3736:  "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6".
[31]  Void.
[32]
3GPP2 C.S0024-A v2.0: "cdma2000 High Rate Packet Data Air Interface Specification".
[33]  Void.
[34]
RFC 2794:  "Mobile IP Network Access Identifier Extension for IPv4".
[35]  Void.
[36]  Void.
[37]  Void.
[38]
RFC 4861:  "Neighbor Discovery for IP Version 6 (IPv6)".
[39]
RFC 5446:  "Service Selection for Mobile IPv4".
[40]
RFC 5026:  "Mobile IPv6 bootstrapping in split scenario".
[41]
RFC 6611:  "Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario".
[42]  Void.
[43]
RFC 5779:  "Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server".
[44]
RFC 5447:  "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction".
[45]
TS 33.402: "3GPP System Architecture Evolution: Security aspects of non-3GPP accesses".
[46]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[47]
TS 22.011: "Service accessibility".
[48]
RFC 3948:  "UDP Encapsulation of IPsec ESP Packets".
[49]
3GPP2 C.S0087-0: "E-UTRAN - HRPD and CDMA2000 1x Connectivity and Interworking: Air Interface Aspects".
[50]
RFC 4739:  "Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol".
[51]
3GPP2 X.S0057-B: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[52]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[53]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[54]  Void.
[55]
TS 23.261: "IP Flow Mobility and seamless WLAN offload; Stage 2".
[56]
RFC 6276:  "DHCPv6 Prefix Delegation for Network Mobility (NEMO)".
[57]
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[58]
RFC 4862:  "IPv6 Stateless Address Autoconfiguration".
[59]  Void.
[60]
TS 23.221: "Architectural requirements".
[61]
TS 32.240: "Charging architecture and principles".
[62]
TS 32.251: "Charging management; Packet Switched (PS) domain charging".
[63]
TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
[64]
IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[65]
IEEE Std 802.1X-2004: "IEEE Standard for Local and Metropolitan Area Networks: Port-Based Network Access Control".
[66]
RFC 791:  "Internet Protocol".
[67]
RFC 2460:  "Internet Protocol, Version 6 (IPv6) Specification".
[68]
RFC 6106:  "IPv6 Router Advertisement Options for DNS Configuration".
[69]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[70]
TS 29.276: "3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3".
[71]
RFC 768:  "User Datagram Protocol".
[72]
RFC 5448:  "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')".
[73]
TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
[74]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[75]
WiFi Alliance Technical Committee, Hotspot 2.0 Technical Task Group: "Hotspot 2.0 (Release 2) Technical Specification", 2013-04-09.
[76]
TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC".
[77]
ETSI ES 282 004 v3.4.1 (2010): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)".
[78]
TS 25.331: "Universal Terrestrial Radio Access (UTRA); Radio Resource Control (RRC); Protocol specification".
[79]
TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[80]
TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[81]
RFC 3633:  "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6".
[82]
RFC 7148:  "Prefix Delegation Support for Proxy Mobile IPv6".
[83]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[84]
TS 36.463: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Wireless LAN (WLAN); Xw application protocol (XwAP)".
[85]
RFC 6696:  "EAP Extensions for the EAP Re-authentication Protocol (ERP)".
[86]
WFA: "Wi-Fi Multimedia Technical Specification, version 1.2.0".
[87]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[88]
TS 23.502: "Procedures for the 5G System; Stage 2".
Up

3  Definitions, Symbols and Abbreviationsp. 15

3.1  Definitionsp. 15

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
SectorID or Sector Address Identifier:
This identifier is defined in 3GPP2 C.S0024-A v2.0 [32] and is used to identify an HRPD AN. The Network operator shall set the value of the SectorID according to the rules specified in clause 14.9 of 3GPP2 C.S0024-A v2.0 [32].
IFOM capable UE:
A UE that is capable of routing different IP flows to the same PDN connection through different access networks (see TS 23.261).
Inter-APN routing capable UE:
A UE that is capable of routing IP flows across multiple simultaneously active IP interfaces, each one associated with a specific APN. These interfaces may be linked to different access networks or to the same access network.
NG-RAN:
A radio access network that connects to 5GC, as defined in TS 23.501.
Non-seamless WLAN offload capable UE:
A UE that is capable of non-seamless WLAN offload as defined in clause 4.1.5.
MAPCON capable UE:
A UE that is capable of routing different simultaneously active PDN connections through different access networks.
Transparent Single-Connection mode:
A communication mode between a UE and a trusted WLAN (TWAN) where the TWAN may set up non-seamless WLAN offload or an S2a tunnel without explicit request from the UE.
Single-Connection mode:
A communication mode that is capable to support only a single connection at a time between a UE and a trusted WLAN (TWAN) . This connection can be used either for Non-Seamless WLAN Offload (as defined in clause 4.1.5) or for PDN connectivity. The use of the Single-Connection mode and the associated parameters of the connection (e.g. for NSWO, for PDN connectivity, APN, etc.) can be negotiated during authentication over TWAN.
Multi-Connection mode:
A communication mode that is capable to support a single or multiple connections at a time between a UE and a trusted WLAN. One connection can be used for Non-Seamless WLAN Offload (as defined in clause 4.1.5) and one or more simultaneous connections can be used for PDN connectivity. The use of the Multi-Connection mode can be negotiated during authentication over TWAN and the requested PDN connection can be setup with the WLCP protocol for PDN connectivity.
Up

3.2  Abbreviationsp. 16

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GC
5G Core Network
ANDSF
Access Network Discovery and Selection Function
DSMIPv6
Dual-Stack MIPv6
CPICH
Common Pilot Channel
DMNP
Delegated Mobile Network Prefix
EAP
Extensible Authentication Protocol
EPC
Evolved Packet Core
ePDG
Evolved Packet Data Gateway
EPS
Evolved Packet System
FACoA
Foreign Agent Care-of-Address
FQDN
Fully Qualified Domain Name
GW
Gateway
H-ANDSF
Home-ANDSF
HBM
Host-based Mobility
HRPD
High Rate Packet Data
HS-GW
HRPD Serving Gateway
IFOM
IP Flow Mobility
IKEv2
Internet Key Exchange version 2
IPMS
IP Mobility management Selection
LMA
Local Mobility Anchor
LWA
LTE-WLAN Radio Level Aggregation
LWIP
LTE-WLAN Radio Level Integration with IPsec Tunnel
MAG
Mobile Access Gateway
MAPCON
Multi Access PDN Connectivity
MIPv4
Mobile IP version 4
MIPv6
Mobile IP version 6
MME
Mobility Management Entity
MTC
Machine-Type Communications
NBM
Network-based Mobility
NSWO
Non-seamless WLAN Offload
OPI
Offload Preference Indicator
P-GW
PDN Gateway
PMIP/PMIPv6
Proxy Mobile IP version 6
RIM
RAN Information Management
RCLWI
RAN Controlled WLAN Interworking
RSRP
Reference Signal Received Power
RSSI
Received Signal Strength Indicator
SectorID
Sector Address Identifier
S-GW
Serving-GW
SON
Self-Configuring and self-Optimizing network
TWAP
Trusted WLAN AAA Proxy
TWAG
Trusted WLAN Access Gateway
TWAN
Trusted WLAN Access Network
UICC
Universal Integrated Circuit Card
UWAN
Untrusted WLAN Access Network
V-ANDSF
Visited-ANDSF
WiMAX
Worldwide Interoperability for Microwave Access
WLCP
WLAN Control Protocol
WMM
Wifi Multimedia
Up

Up   Top   ToC