SYSTEM AND METHOD FOR MAINTAINING DATA CONNECTIVITY OVER A SATELLITE LINK

• US 20130051249A1
• Filed: 08/31/2011
• Published: 02/28/2013
• Est. Priority Date: 08/31/2011
• Status: Active Grant

• Current Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Original Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Inventors: Bartlett, Nigel, Gagne, Louis, Volkman, Thomas
• Granted Patent: US 8,842,583 B2
• Time in Patent Office: Days
• US Class Current: 370/246
• CPC Class Codes: H04B 7/18589 Arrangements for controlling an end to end session, i.e. for initialising, synchronising or terminating an end to end link
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

A system for maintaining data connectivity in a satellite communications system including a satellite terminal with a ping mechanism, a satellite ground station, and a ping server, where the ping mechanism pings the ping server and restores data connectivity between the satellite terminal and the satellite ground station.

Claims

1. A system for maintaining data connectivity in a satellite communications system comprising:

a satellite terminal comprising a ping mechanism;

a satellite ground station; and

a ping server;

wherein the ping mechanism is configured to ping the ping server and restore data connectivity between the satellite terminal and the satellite ground station.

2. The system of claim 1, wherein the ping server is configured to return a ping message from the satellite terminal upon receiving the ping message.

3. The system of claim 1, wherein the ping mechanism is configured to restart a communications stack of the satellite terminal when a ping message sent to the ping server is not returned by the ping server.

4. The system of claim 3, wherein the satellite terminal comprises a RAB error monitor.

5. The system of claim 4, wherein the ping mechanism is configured to restart the communications stack of the satellite terminal when the RAB error monitor detects a configured number of consecutive data errors.

6. The system of claim 5, wherein the ping mechanism is configured to reboot the satellite terminal when the communications stack fails to restart.

7. The system of claim 1, wherein the ping server is co-located with a data server.

8. The system of claim 1, wherein the ping mechanism is configured to ping the ping server when a timer expires.

9. The system of claim 4, wherein the ping mechanism is configured to ping the ping server when the ping mechanism receives a restart message from the RAB error monitor.

10. The system of claim 8, wherein the ping mechanism is configured to ping the ping server when a timer expires and when a ping required is set.

11. The system of claim 10, wherein the timer is set to count down from a time greater than a typical interval between data transmissions between the satellite ground station and the satellite terminal.

12. A method for maintaining data connectivity in a satellite communications system comprising:

starting a timer;

sending a ping message to a ping server on expiration of the timer;

determining if the ping message was returned by the ping server; and

if the message was returned by the ping server, resetting the timer, and

if the message was not returned by the ping server, restarting a communications stack.

13. The method of claim 12, further comprising sending a message to a ping server on expiration of the timer only if there has been no successful sending of data to or receiving of data from a satellite ground station within a configured amount of time.

14. The method of claim 12, further comprising:

receiving a restart message from an RAB error monitor; and

restarting the communication stack.

15. The method of claim 12, further comprising:

determining if the communications stack was previously restarted; and

if the communications stack was previously restarted, rebooting a satellite terminal, and

if the communications stack was not previously restarted, restarting the communications stack.

16. The method of claim 12, further comprising, when a PDP context is not active and was not active and has not failed more than configured number of times, transitioning to an idle state to allow time for the PDP context to be restarted.

17. The method of claim 16, wherein the PDP context is restarted by an active always-on scan.

18. The method of claim 12, wherein the timer is set to count down from an interval greater than typical interval between data transmission to and from a satellite ground station.