Content for TR 22.805 Word version: 12.1.0
0 Introduction
1 Scope
2 References
3 Definitions, symbols and abbreviations
3.1 Definitions
3.2 Symbols
3.3 Abbreviations
...
...
0 Introduction p. 6
Mobile operators are seeing significant increases in user data traffic. For some operators, user data traffic has more than doubled annually for several years. Although the data capacity of networks has increased significantly, the observed increase in user traffic continues to outpace the growth in capacity. This is resulting in increased network congestion and in degraded user service experience. Reasons for this growth in traffic include the rapidly increasing use of "smart phones" and the proliferation of data applications that they support, and the use of USB modem dongles for laptops to provide mobile or nomadic Internet access using 3GPP networks. As the penetration of these terminals increases worldwide, this trend of rapidly increasing data traffic is expected to continue and possibly accelerate.
Network operators continue to invest in additional network capacity (network entities and connectivity resources) attempting to cope with user data traffic increases that cause user plane congestion. This additional investment is becoming increasingly costly due to the rapid and continuing increases in user data traffic. From a CAPEX or OPEX perspective, this approach is not sufficient. In addition, existing QoS and PCC mechanisms are being deployed but the full effect is still to be seen. It is therefore necessary to study approaches and mechanisms to manage user plane congestion.
1 Scope p. 7
This TR considers scenarios and use cases where high usage levels lead to user plane traffic congestion in the RAN, and proposes requirements for handling user plane traffic when RAN congestion occurs. The aim is to make efficient use of available resources to increase the potential number of active users while maintaining the user experience.
Scenarios that will be considered include handling of user plane traffic when RAN congestion occurs based on:
- the subscription of the user;
- the type of application;
- the type of content.
2 References p. 7
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.
3 Definitions, symbols 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.
Network:
remaining part of the "3GPP system" after excluding the UE.
RAN user plane congestion:
the situation where the demand for RAN resources to transfer user data exceeds their capacity to deliver the user data with the expected QoS.
System:
"3GPP system" is defined in TR 21.905.
User plane traffic:
user data to be transferred between entities connected to the 3GPP network but not used by the 3GPP network for purposes such as set-up and release of data sessions.
3.2 Symbols p. 7
Void.
3.3 Abbreviations p. 8
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CDF
Cumulative Distribution Function
DMB
Disaster Message Board
MOCN
Multi-Operator Core Network
OTT
Over-the-Top
