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.401  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2.2…   4.3…   4.3.6…   4.3.8…   4.3.12…   4.3.16…   4.3.20…   4.3.25…   4.4…   4.6…   4.7…   5…   5.1.2…   5.3…   5.3.2…   5.3.3…   5.3.3.2   5.3.3.3…   5.3.4…   5.3.4B…   5.3.5…   5.3.8…   5.3.9…   5.4…   5.4.4…   5.5…   5.5.1.2…   5.5.2…   5.5.2.2…   5.5.2.3…   5.5.2.4…   5.6…   5.7.3…   5.7A…   5.10   5.11…   5.19…   D…   D.3…   D.3.4   D.3.5   D.3.6   D.3.7…   D.3.8…   E   F…   J…   K…   L…   M… 
D Interoperation with Gn/Gp SGSNs  D.1 General Considerations  D.2 Interoperation Scenario 
...

 

D (Normative)  Interoperation with Gn/Gp SGSNs  p. 387

D.1  General Considerations  p. 387

This Annex specifies interworking between the EPS and 3GPP 2G and/or 3G SGSNs, which provide only Gn and Gp interfaces but no S3, S4 or S5/S8 interfaces, i.e. these Gn/Gp SGSNs provide no functionality that is introduced specifically for the EPS or for interoperation with the E-UTRAN.
Interoperation scenarios for operating E-UTRAN with a PLMN maintaining Gn/Gp SGSNs are supported only with a GTP-based S5/S8.
The S5/S8 interface for the Operator with Gn/Gp SGSNs will be GTP-based, but can be changed to PMIP-based S5/S8 when the Gn/Gp SGSNs evolve to S4 SGSNs.
For these interoperation scenarios the GERAN/UTRAN has to support interoperation with E-UTRAN.
TS 23.682 defines the Monitoring Events feature, and TS 23.060 specifies that the Monitoring Events feature for the Gn/Gp SGSN is not supported. Therefore, during interoperation with Gn/Gp SGSNs Monitoring Event information shall not be expected by the MME/S4-SGSN from a Gn/Gp SGSN, nor shall the MME/S4-SGSN or the HSS transfer Monitoring Event information to a Gn/Gp SGSN. This applies to all operations defined in this Annex.
Up

D.2  Interoperation Scenario  p. 387

D.2.1  Roaming interoperation scenario  p. 387

In the roaming scenario the vPLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S-GW for E-UTRAN access. The hPLMN operates a P-GW.
Roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S-GW are enabled by:
  • Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and
  • Gp functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P-GW.
All this Gp and Gn functionality bases on GTP version 1 only.
The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.1-1.
Reproduction of 3GPP TS 23.401, Fig. D.2.1-1: Roaming architecture for interoperation with Gn/Gp SGSN
Figure D.2.1-1: Roaming architecture for interoperation with Gn/Gp SGSN
Up

D.2.2  Non-roaming interoperation scenario  p. 388

In the non-roaming scenario the PLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S-GW for E-UTRAN access.
Intra PLMN roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S-GW are enabled by:
  • Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and
  • Gn functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P-GW.
All this Gn functionality is based on GTP version 1 only.
The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.2-1.
Reproduction of 3GPP TS 23.401, Fig. D.2.2-1: Non-roaming Architecture for interoperation with Gn/Gp SGSNs
Figure D.2.2-1: Non-roaming Architecture for interoperation with Gn/Gp SGSNs
Up

Up   Top   ToC