Methods, circuits, devices, systems and associated computer executable code for facilitating access to a content source through a wireless mobile network

• US 9,642,169 B2
• Filed: 04/11/2013
• Issued: 05/02/2017
• Est. Priority Date: 01/11/2012
• Status: Active Grant

• Current Assignee: Saguna Networks Ltd. (COMSovereign Holding Corp.)
• Original Assignee: Saguna Networks Ltd. (COMSovereign Holding Corp.)
• Inventors: Frydman, Daniel Nathan, Fite, Lior
• Primary Examiner(s): Alam, Hosain
• Assistant Examiner(s): ALLEN, NICHOLAS E
• Application Number:
  US13/861,192
• Publication Number:
  US 20130301626A1
• Time in Patent Office: 1,482 Days
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 80/06 Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16

Abstract

Disclosed are methods, circuits, devices, systems and associated computer executable code for providing facilitating communication between a mobile device application and a content source accessible through a mobile communication network having one or more wireless access points. There is disclosed a start of Service Accelerator (“SOSA”) functionally associate with a wireless access point of the mobile communication network, where the SOSA includes: (1) one or more data stream sniffers adapted to detect and extract start of service sequence (SOSS) data associated with a first Mobile Device Application initiating start of service with a given content source; (2) a Data Request Routing & Handshake Cache (DRRHC) adapted to store Network SOSS Entities associated with the given content source; and (3) a Route Request and Handshake Responder (RRHR) adapted to respond to Application SOSS Entities from a second Mobile Device Application which is initiating start of service with the given content source using Network SOSS Entities stored on said DRRHC.

Claims

1. A method of facilitating Start of Service (“

SOS”

) for a client application running on a Mobile Device communicatively coupled to a Wireless Access Point of a Mobile Network, said method comprising;

monitoring first communications of a first mobile device which are passing through the wireless access point;

detecting, within the first communications, start of service sequence (SOSS) data associated with a first Mobile Device Application initiating start of service with a given content source, wherein the SOSS data includes;

(a) Application SOSS Entities generated by the first Mobile Device Application while establishing service with the given content source, and (b) Network SOSS Entities generated by the given content source while establishing service with the first Mobile Device Application;

copying and storing one or more of the Network SOSS Entities;

monitoring second communications passing through the wireless access point;

detecting, within the second communications, a transmission of a second Mobile Device to the given content source, while allowing the transmission to pass to the given content source;

the transmission being a request for start of service from the given content source;

and

responding to the transmission using the stored Network SOSS Entities.

2. The method according to claim 1, wherein detecting includes uplink sniffing and detection of Application SOSS Entities.

3. The method according to claim 1, wherein detecting includes a downlink sniffing and detection of Network SOSS Entities.

4. The method according to claim 1, further comprising a downlink data intercepting to selectively block Network SOSS Entities from reaching a Mobile Device Application.

5. The method according to claim 4, wherein downlink data intercepting blocks Network SOSS Entities from reaching the second Mobile Device.

6. The method according to claim 1, further comprising appending and updating records of a cache with received Network SOSS Entities.

7. The method according to claim 6, wherein appending includes appending one or more records including Network SOSS Entities generated by a target DNS in response to a given set of Application SOSS Entities when records with Network SOSS Entities corresponding to the given set of Application SOSS Entities are not stored.

8. The method according to claim 6, wherein updating includes updating one or more records associated with a given content source with Network SOSS Entities generated by a target DNS when the one or more records are outdated.

9. The method according to claim 1, further comprising HTTP redirection in response to a detected Mobile Device Application HTTP request.

10. The method to claim 9, wherein said HTTP redirection includes responding to the detected Mobile Device Application HTTP request with a stored redirect response.

11. A Start of Service Accelerator (“

SOSA”

) functionally associated with a Wireless Access Point of a Mobile Network, said SOSA comprising;

one or more data stream sniffers communicatively coupled to the access point and adapted to;

i. monitor first communications of a first mobile device which are passing through the wireless access point;

ii. detect, within the first communications, start of service sequence (SOSS) data associated with a first Mobile Device Application initiating start of service with a given content source, wherein the SOSS data includes;

(a) Application SOSS Entities generated by the first Mobile Device Application while establishing service with the given content source, and (b) Network SOSS Entities generated by the given content source while establishing service with the first Mobile Device Application;

a Data Request Routing &

Handshake Cache (DRRHC) adapted to copy and store one or more of the Network SOSS Entities;

one or more second data stream sniffers communicatively coupled to the access point and adapted to;

(a) monitor second communications passing through the wireless access point; and

(b) detect, within the second communications, a transmission of a second Mobile Device to the given content source, while allowing the transmission to pass to the given content source;

the transmission being a request for start of service from the given content source;

and

a Route Request and Handshake Responder (RRHR) adapted to respond to the transmission using Network SOSS Entities stored on said DRRHC.

12. The SOSA according to claim 11, wherein said one or more data stream sniffers includes an uplink sniffer functionally associated with a Route Request and Handshake Detector (RRHD) adapted to detect Application SOSS Entities.

13. The SOSA according to claim 11, wherein said one or more sniffers includes a downlink sniffer functionally associated with a Route Request and Handshake Detector (RRHD) adapted to detect Network SOSS Entities.

14. The SOSA according to claim 11, further comprising a downlink data interceptor adapted to selectively block Network SOSS Entities from reaching a Mobile Device Application.

15. The SOSA according to claim 14, wherein said downlink data interceptor is adapted to block Network SOSS Entities from reaching the second Mobile Device.

16. The SOSA according to claim 11, further comprising a cache updater adapted to append and update records in said DRRHC.

17. The SOSA according to claim 16, wherein said cache updater is adapted to append to said DRRHC one or more records including Network SOSS Entities generated by a target DNS in response to a given set of Application SOSS Entities when records with Network SOSS Entities corresponding to the given set of Application SOSS Entities are not found in said DRRHC.

18. The SOSA according to claim 16, wherein said cache updater is adapted to update one or more records in said DRRHC associated with a given content source with Network SOSS Entities generated by a target DNS when the one or more records in said DRRHC are outdated.

19. The SOSA according to claim 11, further comprising a redirection module adapted to trigger a HTTP redirect in response to a detected Mobile Device Application HTTP request.

20. The SOSA according to claim 19, wherein said HTTP redirection module comprises HTTP redirect logic and an HTTP redirect cache, and wherein said redirection module signals said Route Request and Handshake Responder (RRHR) to respond to the detected Mobile Device Application HTTP request with a redirect response stored in said HTTP redirect cache.

21. A Mobile Communication Network comprising:

one or more Wireless Access Points; and

a Start of Service Accelerator (“

SOSA”

) functionally associated with a Wireless Access Point of said Mobile Communication Network, said SOSA comprising;

(1) one or more data stream sniffers communicatively coupled to the access point and adapted to;

(i) detect, within the first communications, start of service sequence (SOSS) data associated with a first Mobile Device Application initiating start of service with a given content source, wherein the SOSS data includes;

(a) Application SOSS Entities generated by the first Mobile Device Application while establishing service with the given content source, and (b) Network SOSS Entities generated by the given content source while establishing service with the first Mobile Device Application;

(2) a Data Request Routing &

Handshake Cache (DRRHC) adapted to copy and store one or more of the Network SOSS Entities;

(3) one or more second data stream sniffers communicatively coupled to the access point and adapted to;

(a) monitor second communications passing through the wireless access point; and

(b) detect, within the second communications, a transmission of a second Mobile Device to the given content source, while allowing the transmission to pass to the given content source;

the transmission being a request for start of service from the given content source;

and

(4) a Route Request and Handshake Responder (RRHR) adapted to respond to the transmission using Network SOSS Entities stored on said DRRHC.

22. A Mobile Communication Network according to claim 21, wherein said one or more data stream sniffers includes an uplink sniffer functionally associated with a Route Request and Handshake Detector (RRHD) adapted to detect Application SOSS Entities.

23. A Mobile Communication Network according to claim 21, wherein said one or more sniffers includes a downlink sniffer functionally associated with a Route Request and Handshake Detector (RRHD) adapted to detect Network SOS S Entities.

24. A Mobile Communication Network according to claim 21, further comprising a downlink data interceptor adapted to selectively block Network SOSS Entities from reaching a Mobile Device Application.

25. A Mobile Communication Network according to claim 24, wherein said downlink data interceptor is adapted to block Network SOSS Entities from reaching the second Mobile Device.

26. A Mobile Communication Network according to claim 21, further comprising a cache updater adapted to append and update records in said DRRHC.

27. A Mobile Communication Network according to claim 26, wherein said cache updater is adapted to append to said DRRHC one or more records including Network SOSS Entities generated by a target DNS in response to a given set of Application SOSS Entities when records with Network SOSS Entities corresponding to the given set of Application SOSS Entities are not found in said DRRHC.

28. A Mobile Communication Network according to claim 26, wherein said cache updater is adapted to update one or more records in said DRRHC associated with a given content source with Network SOSS Entities generated by a target DNS when the one or more records in said DRRHC are outdated.

29. A Mobile Communication Network according to claim 21, further comprising a redirection module adapted to trigger a HTTP redirect in response to a detected Mobile Device Application HTTP request.

30. A Mobile Communication Network according to claim 29, wherein said HTTP redirection module comprises HTTP redirect logic and an HTTP redirect cache, and wherein said redirection module signals said Route Request and Handshake Responder (RRHR) to respond to the detected Mobile Device Application HTTP request with a redirect response stored in said HTTP redirect cache.