Content for TR 23.705 Word version: 13.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Assumptions and architectural requirements
...
...
1 Scope p. 6
The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101.
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document.
2 References p. 6
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] Void.
[3]
TS 22.101: "Service aspects; Service principles".
[4]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[5]
TR 23.800: "Study on Application Based Charging (ABC); Stage 2".
[6]
TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
[7]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[8]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[9]
TR 22.805: "Feasibility study on user plane congestion management".
[10]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[11]
TS 23.203: "Policy and charging control architecture".
[12]
draft-quinn-nsh: "Network Service Header". Work in progress.
[13]
TS 29.303: "Domain Name System Procedures".
[14]
TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
RAN user plane congestion:
RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a period of time. RAN user plane congestion leads, for example, to packet drops or delays, and may or may not result in degraded end-user experience.
User-impacting congestion:
User-impacting congestion occurs when a service that is delivered to a user over the default bearer or a dedicated bearer does not meet the user's expected service experience due to RAN user plane congestion. The expectation for a service delivery is highly dependent on the particular service or application. The expected service experience may also differ between subscriber groups (e.g. a premium subscriber may have higher expectations than a subscriber with the cheapest subscription). RAN resource shortage where the RAN can still fulfil the user expectations for a service delivery is not considered to be user-impacting congestion; it is rather an indication for full RAN resource utilization, and as such a normal mode of operation.
Unattended traffic:
see definition for "Unattended Data Traffic" in TS 22.101. See also the discussion in clause 4.9.1 in TR 22.805.
Attended traffic:
see definition for "Attended Data Traffic" in TS 22.101. See also the discussion in clause 4.9.1 in TR 22.805.
3.2 Abbreviations p. 7
4 Assumptions and architectural requirements p. 7
Void.
