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  TR 23.834  Word version:  10.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  4 Architectural requirements 
...

 

1  Scope  p. 5

The objective of this feasibility study is to investigate solutions and benefits for supporting a new GTP option for S2b network based mobility.
The study will develop the stage 2 message flows necessary to support S2b based on GTP and mobility between S5/S8 based on GTP and S2b based on GTP.

2  References  p. 5

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]
TR 41.001: "GSM Release specifications".
→ to date, withdrawn by 3GPP
[3]
TS 23.401: "GPRS Enhancements for E-UTRAN Access".
[4]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[5]
TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[6]
TS 23.002: "Network architecture".
[7]
TS 23.203: "Policy and Charging Control Architecture".
Up

3  Definitions and abbreviations  p. 5

3.1  Definitions  p. 5

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.

3.2  Abbreviations  p. 5

For the purposes of the present document, the abbreviations given in TR 21.905 apply.

4  Architectural requirements  p. 5

Applying GTP based S2b as opposed to PMIP based S2b shall have no impact to the UE.
The impacts to the existing functionalities and to the EPC shall be minimized. The protocol design on S2b should aim at keeping S2b GTP operations similar to those supported on GTP-based S5/S8 as much as possible.
The GTP S2b option is expected to be functionally equivalent to the already existing PMIP S2b option.

Up   Top   ToC