Tech-invite  3GPPspecsRELsGlossariesSIP

Top   in Index   Prev   Next

TR 22.806SA1
Study on Application-specific Congestion Control
for Data Communication

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V13.1.0 (Wzip)  2014/09  40 p.

WI Acronym:  FS_ACDC
Rapporteur:  Mr. Minokuchi, AtsushiNTT DOCOMO INC.

UEs on which user can easily download applications from web sites are rapidly increasing in the world and a wide variety of applications are constantly created and installed on the UEs. Specific applications can (intentionally or unintentionally) cause congestion over RAN/CN. While network is congested, it is not desirable to allow these applications to access the network in order to protect the network resources. Several SDOs identified key issues related to network inefficiencies caused by such UEs and by the variety of applications.
On the other hand, for example in Japan, after the severe earthquake on March 11th, 2011, the packet based communication applications that users can invoke to confirm the safety of their relatives are recognized as important applications (e.g. Disaster Message Board (DMB) service, Disaster voice messaging service) when disaster occurs. Therefore, Japanese government strongly expects Japanese operators to provide the connectivity at least for such services even when the network is highly congested, while other services are barred to free up the resources for important services.
This TR provides a study on Application specific Congestion control for Data Communication (ACDC). This Study investigates the following aspects:
  • Identify the use cases and potential requirements to allow/restrict the communication initiation of particular applications defined by operator, subject to regional regulations;
  • Gap analysis with existing access control mechanisms.

full Table of Contents for  TR 22.806  Word version:   13.1.0

Here   Top
1  ScopeWord-p. 7
2  References
3  Definitions and abbreviations
4  OverviewWord-p. 8
5  Use Cases
5.1  Use Case 1 - ACDC activation for UE-initiated applications
5.2  Use Case 2 - preferred handling of DMB
5.3  Use Case 3 - relationship to Access Class 11-15
5.4  Use Case 4 - Non-roaming regional (local) difference in ACDC
5.5  Use Case 5 - Roaming regional (local) difference in ACDC
5.6  Use Case 6 - Categories in ACDC
5.7  Use Case 7 - interaction with other forms of access control - ACB
5.8  Use Case 8 - control range and proportionality
5.9  Use Case 9 - Secure ACDC list provisioning
5.10  Use Case 10 - Control of ACDC
5.11  Use Case 11 - Roaming compatibility when ACDC categorization is honoured in roaming UEsWord-p. 21
5.12  Use Case 12 - ACDC Categorization Not Honoured by VPLMNWord-p. 23
5.13  Use Case 13 - Network sharing in ACDC
5.14  Use Case 14 - interaction with other forms of access control - EAB
6  Analysis
7  Potential requirementsWord-p. 30
8  Conclusion
A  Mapping of potential requirementsWord-p. 32
B  Key issues for considerationWord-p. 33
C  ACDC Background InformationWord-p. 34
D  Change historyWord-p. 40

Up   Top