CONTROL OF TRAFFIC FROM APPLICATIONS WHEN THIRD PARTY SERVERS ENCOUNTER PROBLEMS

• US 20170201456A1
• Filed: 06/16/2015
• Published: 07/13/2017
• Est. Priority Date: 08/07/2014
• Status: Abandoned Application

• Current Assignee: Intel IP Corporation (Intel Corporation)
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Jain, Puneet, Pinheiro, Ana Lucia A., Martinex Tarradell, Marta, Venkatachalam, Muthaiah Muthu, Chin, Chen-Ho, Siow, Eric
• Application Number:
  US15/324,515
• Publication Number:
  US 20170201456A1
• Time in Patent Office: Days
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04W 28/0289 Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 8/183 Processing at user equipment or user record carrier

Abstract

Control of Applications when Third Party Servers encounter difficulties (CATS) is discussed. An example network server that facilitates CATS comprises a processor and a transmitter circuit. The processor is configured to determine a status associated with a third party server and a network load level of a network associated with the network server, select a CATS level that defines one or more restrictions on network traffic associated with the third party server for the third party server based on the third party server status and the network load level, and implement the one or more restrictions on network traffic toward the third party server. The interface is configured to transmit an indicator of the CATS level for the third party server.

Claims

1. A network server that facilitates Control of one or more Applications when Third party Servers encounter difficulties (CATS), comprising:

a processor configured to;

determine a status associated with a third party server;

determine a network load level of a network associated with the network server;

select a CATS level for the third party server based at least in part on the status associated with the third party server and the network load level, wherein the CATS level defines one or more restrictions on network traffic associated with the third party server; and

implement the one or more restrictions on network traffic toward the third party server; and

an interface configured to transmit an indicator of the CATS level for the third party server.

2. The network server of claim 1, wherein the processor being configured to implement the one or more restrictions on network traffic toward the third party server comprises the processor being configured to prevent an attempted packet data network (PDN) connection between a first user equipment (UE) and the third party server based at least in part on the CATS level.

3. The network server of claim 1, wherein the one or more restrictions comprise at least one restriction based on a user equipment (UE) subscription status with an operator of the network server.

4. The network server of claim 1, wherein the one or more restrictions comprise at least one restriction based on a subscription status with an operator of the third party server.

5. The network server of claim 1, wherein the one or more restrictions comprise at least one restriction associated with a first application or a first function of the third party server.

6. The network server of claim 1, wherein the one or more restrictions comprise at least one restriction associated with a current amount of network traffic over an existing packet data network (PDN) connection with the third party server.

7. The network server of claim 1, wherein the one or more restrictions comprise at least one restriction associated with a current aggregate amount of network traffic associated with a user equipment (UE).

8. The network server of claim 1, wherein the processor is further configured to disconnect at least one existing packet data network (PDN) connection with the third party server based at least in part on the one or more restrictions.

9. The network server of claim 1, wherein the network server is collocated with a mobile management entity (MME), and wherein the transmitter circuit is configured to transmit the indicator of the CATS level via a non-access stratum.

10. The network server of claim 1, wherein the network server is collocated with a access network discovery and selection function (ANDSF), and wherein the transmitter circuit is configured to transmit the indicator of the CATS level via an Open Mobile Alliance (OMA) Device Management (DM) protocol.

11. A non-transitory machine readable medium comprising instructions that, when executed, cause at least one server to:

determine a status of a third party server;

select a level of Control of one or more Applications when Third party Servers encounter difficulties (CATS) based at least in part on the status of the third party server; and

transmit an indication of the level of CATS, wherein the level of CATS defines one or more restrictions on network traffic toward the third party server, wherein at least one of the one or more restrictions is based on a subscription status.

12. The non-transitory machine readable medium of claim 11, wherein the instructions, when executed, cause the at least one server to determine the status of the third party server based at least in part on an absence of successful connection attempts with the third party server for at least a threshold period of time.

13. The non-transitory machine readable medium of claim 11, wherein the instructions, when executed, cause the at least one server to determine the status of the third party server based at least in part on congestion data received from the third party server.

14. The non-transitory machine readable medium of claim 11, wherein the instructions, when executed, cause the at least one server to determine the status of the third party server based at least in part on a number of rejected connection attempts with the third party server during a predetermined period of time.

15. The non-transitory machine readable medium of claim 11, wherein the instructions, when executed, cause the at least one server to determine the status of the third party server based at least in part on a number of consecutive rejected connection attempts with the third party server exceeding a threshold number.

16. The non-transitory machine readable medium of claim 11, at least one restriction on network traffic toward the third party server identifies at least one restricted content type, wherein the at least one restricted content type comprises at least one of a video content, an audio content, or an image content.

17. The non-transitory machine readable medium of claim 11, at least one restriction on network traffic toward the third party server identifies at least one restricted service associated with the third party server.

18. The non-transitory machine readable medium of claim 11, wherein the instructions, when executed, cause the server to prevent at least one attempted packet data network (PDN) connection with the third party server based at least in part on the one or more restriction.

19. A user equipment (UE) that facilitates Control of one or more Applications when Third party Servers encounter difficulties (CATS), comprising:

a receiver circuit configured to receive an indication of a CATS level associated with at least one third party server, wherein the CATS level is associated with at least one restriction on network traffic between the UE and the third party server;

a processor operably coupled to the receiver circuit and configured to;

identify one or more applications associated with the at least one third party server based at least in part on the indication; and

at least one of delay or prevent at least one transmission associated with at least one of the one or more applications based on the at least one restriction.

20. The UE of claim 19, wherein the indication of the CATS level is received via at least one of a non-access spectrum (NAS) signal or a radio resource control (RRC) signal.

21. The UE of claim 19, wherein the CATS level is associated with a subscription level of the UE with a radio access network (RAN).

22. The UE of claim 19, wherein the CATS level is associated with a subscription level of the UE with the third party server.

23. The UE of claim 22, wherein the subscription level is stored by the UE in a universal subscriber identity module (USIM) elementary file (EF).

24. The UE of claim 19, wherein the indication of the CATS level is received via a paging channel.

25. The UE of claim 19, wherein the indication of the CATS level is received via at least one of a broadcast transmission or a multicast transmission.