Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.873
Feasibility study for Transport and Control separation in the PS CN domain

3GPP‑Page   ToC  
V4.0.0 (Wzip)  2001/04  91 p.
Rapporteur:
Mr. Ibanez, Juan-Antonio
Ericsson LM

full Table of Contents for  TR 23.873  Word version:  4.0.0

Here   Top

1  ScopeWord‑p. 6

The scope of this Technical Report (TR) is to capture the results of a feasibility study on how to introduce a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference logical architecture for R'00.
With this separation in view, functional elements of the PS CN domain that provide both significant control and transport functions may be decomposed into two separate functional entities: one entity taking care of the control functionality and an other entity handling the payload transport. An exact distribution of the functions currently supported by a single functional entity between new functional entities and other network entities will be defined as the result of this feasibility study, if necessary.
A standard control protocol should be used between the control and transport entities, if applicable, e.g. H.248. The required functionality, e.g. extensions to H.248 or any other protocol which may be chosen for this task, would have to be defined and standardised within 3GPP. This TR will identify and define these extensions, and extensions to other interfaces if applicable.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the PS CN domain. At the end of the feasibility study, the remaining open issues will be reported and their importance will be assessed. An analysis of the benefits and drawbacks of separating the control and transport functions in the PS CN domain will also be performed.
Up

2  ReferencesWord‑p. 7

3  Symbols and AbbreviationsWord‑p. 7

3.1  SymbolsWord‑p. 7

3.2  AbbreviationsWord‑p. 7

4  IntroductionWord‑p. 7

5  Reference Logical ArchitectureWord‑p. 8

6  Alternative 1: SGSN Server - PS Media Gateway ApproachWord‑p. 8

6.1  IntroductionWord‑p. 8

6.2  Logical ArchitectureWord‑p. 9

6.3  H.248 option over MpWord‑p. 12

6.3.1  Mobility Management (H.248 option)Word‑p. 12

6.3.2  Session Management (H.248 option)Word‑p. 27

6.3.3  Charging (H.248 option)Word‑p. 35

6.3.4  CAMEL Considerations (H.248 option)Word‑p. 37

6.3.5  Lawful Interception (H.248 option)Word‑p. 39

6.3.6  QoS Considerations (H.248 option)Word‑p. 40

6.3.7  Abnormal Cases (H.248 option)Word‑p. 40

6.4  GTP-C option over MpWord‑p. 40

6.5  General Lawful Interception ConsiderationsWord‑p. 51

6.6  SecurityWord‑p. 52

6.7  O&MWord‑p. 52

6.8  RAN Considerations (e.g. GERAN)Word‑p. 52

6.9  CompatibilityWord‑p. 52

6.10  Dynamic Allocation of PS-MGW ResourcesWord‑p. 52

6.11  Benefits and DrawbacksWord‑p. 53

6.12  Open IssuesWord‑p. 54

7  Alternative 2: One Tunnel ApproachWord‑p. 54

7.1  IntroductionWord‑p. 54

7.1.1  ApplicabilityWord‑p. 54

7.2  Logical ArchitectureWord‑p. 55

7.2.1  Functional NodesWord‑p. 56

7.2.1.1  2G-SGSNWord‑p. 56

7.2.1.2  3G-SGSN / cSGSNWord‑p. 56

7.2.1.3  GGSN / xGGSNWord‑p. 57

7.2.2  InterfacesWord‑p. 57

7.2.3  User PlaneWord‑p. 58

7.3  Mobility ManagementWord‑p. 59

7.4  Session ManagementWord‑p. 71

7.5  ChargingWord‑p. 77

7.6  CAMEL ConsiderationsWord‑p. 77

7.7  Lawful InterceptionWord‑p. 78

7.8  QoS ConsiderationsWord‑p. 78

7.9  SecurityWord‑p. 79

7.10  O&MWord‑p. 79

7.11  RAN Considerations (e.g. GERAN)Word‑p. 79

7.12  Abnormal CasesWord‑p. 79

7.13  CompatibilityWord‑p. 79

7.14  Benefits and DrawbacksWord‑p. 79

7.15  Open IssuesWord‑p. 80

8  SummaryWord‑p. 80

9  Work PlanWord‑p. 85

A  Combined SGSN and GGSN splitWord‑p. 86

$  Change HistoryWord‑p. 91


Up   Top