Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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…

 

4.2.2  Non-roaming Architectures for EPSp. 22

The following considerations apply to interfaces where they occur in figures in this and the next clause:
  • S5, S2a and S2b can be GTP-based or PMIP-based.
  • Gxc is used only in the case of PMIP variant of S5 or S8.
  • Gxa is used when the Trusted non-3GPP Access network is owned by the same operator.
  • Gxb is used only in the case of PMIP variant of S2b.
  • S9 is used instead of Gxa to the Trusted non-3GPP Access network not owned by the same operator.
  • Gxa or S9 are terminated in the Trusted non-3GPP Accesses if supported.
  • S2c is used only for DSMIPv6 bootstrapping and DSMIPv6 De-Registration (Binding Update with Lifetime equals zero) when the UE is connected via 3GPP access. Dashed lines are used in Figure 4.2.2-2, Figure 4.2.3-3 and Figure 4.2.3-5 to indicate this case.
Reproduction of 3GPP TS 23.402, Fig. 4.2.2-1: Non-Roaming Architecture within EPS using S5, S2a, S2b
Up
Reproduction of 3GPP TS 23.402, Fig. 4.2.2-2: Non-Roaming Architecture within EPS using S5, S2c
Up

Up   Top   ToC