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… 
6 Functional Description and Procedures for Trusted Non-3GPP IP Accesses  6.1 Control and User Plane Protocol Stacks  6.1.1 Protocol Stacks for S2a  6.1.2 Protocol Stacks for S2c over Trusted Non-3GPP IP Accesses 
...

 

6  Functional Description and Procedures for Trusted Non-3GPP IP Accesses  p. 115

6.1  Control and User Plane Protocol Stacks  p. 115

6.1.1  Protocol Stacks for S2a  p. 115

The following protocols shall be supported on S2a:
  • PMIPv6.
  • MIPv4 FA mode.
  • GTP based protocol for Trusted WLAN as specified in clause 16.
The figures below illustrate the control planes for Mobility Management (MM) and the user planes for each protocol option.
Copy of original 3GPP image for 3GPP TS 23.402, Fig. 6.1.1-1: Protocols for MM control and user planes of S2a for the PMIPv6 option
Figure 6.1.1-1: Protocols for MM control and user planes of S2a for the PMIPv6 option
(⇒ copy of original 3GPP image)
Up
Legend:
  • According to terms defined in PMIPv6 specification, RFC 5213, the functional entities terminating both the control and user planes are denoted MAG in the non-3GPP IP access and LMA in the Gateway. LMA includes also the function of a Home Agent.
  • The MM control plane stack is PMIPv6 specification, RFC 5213, over IPv6/IPv4.
  • The user plane carries remote IPv4/v6 packets over either an IPv4 or an IPv6 transport network.
  • The tunnelling layer implements GRE encapsulation applicable for PMIPv6.
  • IPv4/IPv6: This refers to network layer protocols. On the Trusted Non-3GPP IP Access MAG this includes termination of the UE-MAG link-local protocols (e.g. IPv6 Router Solicitation/Advertisement) and forwarding of user plane IP packets between the UE-MAG point-to-point logical link and the S2a tunnel for the UE.
Copy of original 3GPP image for 3GPP TS 23.402, Fig. 6.1.1-2: Protocols for MM control and user planes of S2a for the MIPv4 FA mode option
Figure 6.1.1-2: Protocols for MM control and user planes of S2a for the MIPv4 FA mode option
(⇒ copy of original 3GPP image)
Up
Legend:
  • According to terms defined in MIPv4 RFC 5944, the functional entities terminating both the control and user planes are denoted MN (Mobile Node) in the UE, FA (Foreign Agent) in the non-3GPP IP access, and HA (Home Agent) in the Gateway.
  • The MM control plane stack is MIPv4 RFC 5944 over UDP over IPv4.
  • The user plane carries remote IPv4 packets over an IPv4 transport network.
  • The tunnelling layer implements IP encapsulation applicable for MIPv4 as defined in RFC 5944. In some cases the tunnelling layer may be transparent.
  • IPv4: This refers to network layer protocols. On the Trusted Non-3GPP IP Access FA user plane this includes termination of the UE-FA link-local protocols (e.g. ARP messages) and forwarding of user plane IP packets between the UE-FA point-to-point logical link and the S2a tunnel for the UE.
Up

6.1.2  Protocol Stacks for S2c over Trusted Non-3GPP IP Accesses  p. 117

The following protocol shall be supported on S2c over Trusted Non-3GPP IP Accesses:
  • DSMIPv6, with IPsec and IKEv2 used to secure mobility signalling, as specified in RFC 4877
The Figure below illustrates the control plane for Mobility Management (MM) and the user plane.
Copy of original 3GPP image for 3GPP TS 23.402, Fig. 6.1.2-1: Protocols for MM control and user planes of S2c for the DSMIPv6 option
Figure 6.1.2-1: Protocols for MM control and user planes of S2c for the DSMIPv6 option
(⇒ copy of original 3GPP image)
Up
Legend:
  • According to terms defined in DSMIPv6, RFC 5555, the functional entities terminating both the control and user planes are denoted MN (Mobile Node) in the UE, and HA (Home Agent) in the Gateway.
  • The MM control plane stack is DSMIPv6, RFC 5555 over IPv6/IPv4.
  • The user plane carries remote IPv4/v6 packets over either an IPv4 or an IPv6 transport network.
  • The tunnelling layer implements IP encapsulation applicable for MIPv6 as defined in DSMIPv6, RFC 5555. In some cases the tunnelling layer may be transparent.
Up

Up   Top   ToC