tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top        in Index        Prev        Next

TR 22.818 (SA1)
Feasibility Study on
Control of Applications
when Third party Servers encounter difficulties

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V14.0.0    2015/06    26 p.


Rapporteur:  Ms. Yoshida, Eriko
See also:  –


With the spread of applications on UEs (also known as "smart phones"), coupled with the rapidly growing number of UEs designed for usage with little or no human involvement (machine type communications), the potential for issues to occur in the overall "system" involving these applications and the third party entities they interact with increases. When these third party entities experience difficulties, they may be able to manage their problems without undue impact on operator networks, but there will be times when they are not able to do so.

When a third party server becomes congested or fails, the communication by the UE applications that make use of that server need to be controlled so that excessive use of 3GPP network resources is avoided while not affecting other applications and their associated servers that are functioning normally.

The 3GPP network needs to be able to detect or receive an indication from a third party server of its congestion status or failure status and control UE applications (or their traffic in the 3GPP network) that make use of a third party server that has encountered difficulties. HTTP and other third party (possibly proprietary) protocols can have status codes but these can be insufficient as they cannot provide a suitable indication to the UE application of the nature of the issue and therefore could result in frequent retries even when these will fail, thus burdening the network with connection attempts that will fail.

The present document identifies potential requirements that will enable the 3GPP network to detect or receive an indication from a third party server of its congestion status or failure status and control the traffic of individual UE applications (or their traffic in the 3GPP network) when the 3GPP network becomes aware that a third party server has run into difficulties. This will make it possible to
  • Reduce or avoid unproductive traffic in 3GPP network (i.e., traffic that the 3rd party server is not able to receive) by blocking it either in the UE or in the 3GPP network (primary objective)
  • Allow 3GPP network to help 3rd party servers to handle overload and recover from failures (secondary objective)


 

Here        Top

 

 

1   Scope   Word-p. 6
2   References
3   Definitions and abbreviations
4   Use cases
4.1   Third Party Server Reports Congestion or Failure
4.2   Third Party Server Fails
4.3   Combating a DDOS Attack from a Virus
4.4   Using Phased CATS to Gracefully Restore Service
4.5   Coexistence of ACDC and CATS   Word-p. 11      Up
4.6   Activation and Control of CATS Using 3GPP Network Subscription Profiles
4.7   Activation and Control of CATS Using Third Party Service Subscription Profiles
4.8   Activation and Control of CATS when a Third Party Server Supports Multiple Applications
4.9   Relationship to Access Class 11-15   Word-p. 17
4.10   Charging between CATS activation and deactivation      Up
5   Considerations
6   Potential requirements
7   Conclusions and Recommendations   Word-p. 20
A   CATS Conceptual Approaches   Word-p. 21
B   Mapping of potential requirements.   Word-p. 25
C   Change history

Up        Top