Devices and methods using network load data in mobile cloud accelerator context to optimize network usage by selectively deferring content delivery

• US 10,785,155 B2
• Filed: 03/20/2012
• Issued: 09/22/2020
• Est. Priority Date: 12/21/2011
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Damola, Ayodele, Svanbro, Krister
• Primary Examiner(s): Vang, Meng
• Application Number:
  US14/356,926
• Publication Number:
  US 20140310426A1
• Time in Patent Office: 3,108 Days
• Field of Search: 709206
• CPC Class Codes: H04L 12/1489 dependent on congestion
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8027 based on network load situation
• CPC Class Codes: H04M 15/81 Dynamic pricing, e.g. change of tariff during call

Abstract

Network devices, servers, and modules operating within MCA capable to selectively defer delivery of non-time sensitive content are provided. A network device (315) includes a communication interface (410) configured to enable communication with a client device (310), and to receive a request for a content delivery from the client device (310). The network device also includes a processing unit (420) configured to determine whether to defer the request depending on a network load at a time when the request has been received.

Claims

1. A domain name server, comprising:

a communication interface of the domain name server is communicatively coupled with a user equipment so as to receive a request for a content delivery from the user equipment;

a memory of the domain name server stores pairs of domain names and Internet Protocol (IP) addresses; and

a processor of the domain name server is configured to determine whether to defer the request depending on a network load at a time when the request has been received,

wherein if the processor has determined that the request is not deferred, the processor generates and sends a first message to the user equipment via the communication interface, to enable the content delivery,

wherein if the processor has determined that the request is deferred, the processor generates and sends a second message to the user equipment via the communication interface,

wherein the request for the content delivery includes a domain name of a server storing desired content, the first message includes an IP address corresponding to the domain name of the server storing the desired content, and the second message is an HTTP message that does not include the IP address corresponding to the domain name of the server storing the desired content.

2. The domain name server of claim 1, wherein the network load is inferred by comparing the time when the request has been received with daily network load data including peak hours and off-peak hours, wherein if the time when the request has been received corresponds to the peak hours, the processor defers the request.

3. The domain name server of claim 1, wherein the network load is determined based on information extracted from a network load database depending on a time when the request has been received.

4. The domain name server of claim 3, wherein the network load database is a historical database storing data related to past network load.

5. The domain name server of claim 3, wherein the network load database is a near real-time database fed with current network load information by a module configured to perform network traffic analysis.

6. The domain name server of claim 3, wherein the network load database is stored in another network device, and the network device further comprises:

a network load database interface configured to enable communication with another network device to enable extracting the information from the network load database.

7. The domain name server of claim 1, wherein the network load is determined based on latest network load information received from a module configured to perform network traffic analysis, at a time when the request has been received.

8. The domain name server of claim 1, wherein the communication interface is further configured to communicate with a smart pipe controller within a mobile cloud accelerator to determine whether the request is deferred.

9. The domain name server of claim 1, wherein the communication interface is coupled to a smart pipe controller, which assess the network load at the time when the request is received.

10. The domain name server of claim 1, wherein the network load is based on a throughput volume of a cell in which the user equipment is located.

11. A cache server in a mobile network, comprising:

a first communication interface of the cache server is coupled with a wireless client device that submits a request for a delivery of content, wherein the request for content delivery is an HTTP GET;

a second communication interface of the cache server is coupled with a smart pipe controller;

a memory of the cache server is configured to store a content specified in the request; and

a processor of the cache server is configured to send a query to the smart pipe controller via the second communication interface as to whether to proceed with delivering the content depending on a network load and to receive a response from the smart pipe controller via the second communication interface,

wherein if the response to the query is positive, the processor sends the content stored in the memory to the wireless client device via the first communication interface, and

wherein if the response to the query is negative, the processor generates a message to indicate, to the wireless client device, that the request is deferred, and sends the message to the client device via the first communication interface, wherein the message indicating that the request is deferred is an HTTP 503 that includes a time value when the wireless client device can send another request for delivery of the content,

wherein the cache server is a mobile edge server.

12. The cache server of claim 11, wherein the time value included in the second message is an absolute time value or a time interval after the time when the request has been received at which to resubmit the request.

13. The cache server of claim 11, wherein the network load is based on a throughput volume of a cell in which the wireless client device is located.

14. A method performed by a network device, the method comprising:

receiving a request for a content delivery from a wireless client device in the network, wherein the request for content delivery is an HTTP GET;

sending a query to a smart pipe controller as to whether to proceed with delivering the content depending on a network load;

receiving a response from the smart pipe controller as to whether to proceed with delivering the content depending on the network load;

determining whether to defer the request depending on the response received from the smart pipe controller;

sending a first message to the wireless client device if the request is not deferred, wherein the first message includes the content; and

sending a second message to the client if the request is deferred, wherein the second message is an HTTP 503 that includes a time value when the wireless client device can send another request for delivery of the content,

wherein the network device is a mobile edge server operating as a cache server.

15. The method of claim 14, further comprising:

comparing a time when the request has been received with daily network load data including peak hours and off-peak hours; and

deferring the request if the time corresponds to the peak hours.

16. The method of claim 14, further comprising:

determining the network load based on information extracted from a network load database depending on a time when the request has been received.

17. The method of claim 14, wherein the network load is based on a throughput volume of a cell in which the wireless client device is located.

18. A non-transitory computer readable storage medium storing executable codes which, when executed on a network device including a communication interface and a processor, makes the network device perform a method comprising:

receiving a request for a content delivery from a wireless client device in the network, wherein the request for content delivery is an HTTP GET;

sending a query to a smart pipe controller as to whether to proceed with delivering the content depending on a network load;

receiving a response from the smart pipe controller as to whether to proceed with delivering the content depending on the network load;

determining whether to defer the request depending on the response received from the smart pipe controller;

sending a first message to the wireless client device if the request is not deferred, wherein the first message includes the content; and

sending a second message to the client if the request is deferred, wherein the second message is an HTTP 503 that includes a time value when the wireless client device can send another request for delivery of the content,

wherein the network device is a mobile edge server operating as a cache server.

19. The non-transitory computer readable storage medium of claim 18, wherein the network load is based on a throughput volume of a cell in which the wireless client device is located.

20. A method, comprising:

storing, by a domain name server, pairs of domain names and Internet Protocol (IP) addresses;

receiving, by the domain name server from a user equipment, a request for content delivery that includes a domain name of a server storing desired content;

determining, by the domain name server, whether to defer the request depending on a network load at a time when the request is received;

sending, by the domain name server when it is determined that the request is not deferred, a first message to the user equipment to enable the content delivery, wherein the first message includes an IP address corresponding to the domain name of the server storing the desired content,

sending, by the domain name server when it is determined that the request is deferred, a second message to be sent to the user equipment, wherein the second message is an HTTP 503 message that does not include the IP address corresponding to the domain name.

21. The method of claim 20, wherein the determination of whether to defer the request comprises communicating with a smart pipe controller, which assess the network load at the time when the request is received.

22. The method of claim 20, wherein the network load is based on a throughput volume of a cell in which the user equipment is located.