WO2010059299A2 - Synchronisation pour des communications par satellite maillées - Google Patents

Synchronisation pour des communications par satellite maillées Download PDF

Info

Publication number
WO2010059299A2
WO2010059299A2 PCT/US2009/059722 US2009059722W WO2010059299A2 WO 2010059299 A2 WO2010059299 A2 WO 2010059299A2 US 2009059722 W US2009059722 W US 2009059722W WO 2010059299 A2 WO2010059299 A2 WO 2010059299A2
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
gateway
satellite
signals
timing
Prior art date
Application number
PCT/US2009/059722
Other languages
English (en)
Other versions
WO2010059299A3 (fr
Inventor
Anil Agarwal
Original Assignee
Viasat, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Viasat, Inc. filed Critical Viasat, Inc.
Publication of WO2010059299A2 publication Critical patent/WO2010059299A2/fr
Publication of WO2010059299A3 publication Critical patent/WO2010059299A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851—Systems using a satellite or space-based relay
    • H04B7/18513—Transmission in a satellite or space-based system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/204—Multiple access
    • H04B7/212—Time-division multiple access [TDMA]
    • H04B7/2125—Synchronisation

Definitions

  • the present invention relates to synchronization for communications in general and, in particular, to synchronization for mesh satellite communication networks.
  • a gateway may serve as the master, and the user terminals may use communications received from the gateway for synchronization. For example, each user terminal may receive one or more signals from a gateway and, based on a reception time from the gateway to the user terminal or other received information, identify start points for the transmission of frames to, or reception of frames from, the gateway.
  • gateway-based synchronization schemes are inadequate.
  • Traditional gateway-based synchronization may not be sufficient to set up timing for user terminal to user terminal mesh communication, as such schemes may not provide adequate timing information for the relevant link between each user terminal and the satellite (e.g., instead timing the gateway to user terminal links). It may, therefore, be desirable to identify novel synchronization techniques to address these timing issues in mesh communications systems wherein timing control is to some extent gateway- based.
  • Novel synchronization techniques for mesh satellite communications are described.
  • Systems, devices, and methods are described to implement such synchronization techniques in a range of embodiments.
  • the arrival time of the gateway signal (or other control signal) may be used to set a start of receive frame time for a terminal.
  • a received control signal from the gateway may then be used to set a start of transmit frame time for the terminal.
  • the distance between the satellite and the gateway may change.
  • ephemeris data is used to modify the start of transmit frame or start of receive frame settings for the terminal or gateway to achieve synchronization for mesh communications.
  • the issue is addressed by using various collections of terminal measurements to modify the start of transmit frame and start of receive frame settings for the terminal or gateway to achieve synchronization for satellite mesh communications.
  • a burst from a terminal is used to set a start of receive frame at a terminal for mesh communications. This burst may be a broadcast burst by a master terminal or self-sync burst.
  • FIG. l is a block diagram of a satellite communications system configured according to various embodiments of the invention.
  • FIG. 2 is a block diagram of a terminal and a gateway in a satellite communications system according to various embodiments of the invention.
  • FIG. 3 is a timing diagram illustrating synchronization methods used according to various embodiments of the invention.
  • FIGS. 4A, 4B, and 4C are timing diagrams illustrating synchronization issues addressed according to various embodiments of the invention.
  • FIGS. 5 A and 5B are timing diagrams illustrating the use of ephemeris data to address synchronization issues according to various embodiments of the invention.
  • FIGS. 6A and 6B are timing diagrams illustrating an alternative use of ephemeris data to address synchronization issues according to various embodiments of the invention.
  • FIG. 7 is a block diagram illustrating components of one or more devices using ephemeris data for mesh synchronization in a satellite communications system according to various embodiments of the invention.
  • FIG. 8 is a flowchart illustrating a method of using ephemeris data to provide for synchronized mesh satellite communications in a system including a gateway and a terminal communicating via satellite.
  • FIG. 9 is a flowchart illustrating a method of synchronizing a satellite communications system for mesh communications using ephemeris data.
  • FIG. 10 is a flowchart illustrating a method 1000 of using ephemeris data for synchronizing a satellite communications system for mesh communications by delaying a transmission time for control signals to be used to set start of receive frame timing.
  • FIG. 11 is a flowchart illustrating a method of using ephemeris data for synchronizing a satellite communications system for mesh communications by adjusting transmission times for control signals to be used to set start of frame timing at a user terminal.
  • FIGS. 12A-12C are timing diagrams illustrating the use of terminal to satellite timing data to address synchronization issues according to various embodiments of the invention.
  • FIGS. 13A-13C are timing diagrams illustrating the use of terminal to satellite timing data to address synchronization issues according to various embodiments of the invention.
  • FIG. 14 is a block diagram illustrating components of one or more devices using terminal to satellite timing data for mesh synchronization in a satellite communications system according to various embodiments of the invention.
  • FIG. 15 is a block diagram illustrating an alternative configuration of components of one or more devices using terminal to satellite timing data for mesh synchronization in a satellite communications system according to various embodiments of the invention.
  • FIG. 16 is a flowchart illustrating a method of using terminal to satellite timing data to provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • FIG. 17 is a flowchart illustrating a method of calculating a changed distance between a gateway and satellite to synchronize a satellite communications system for mesh communications according to various embodiments of the invention.
  • FIG. 18 is a flowchart illustrating a method of calculating a changed transmit time between a gateway and satellite to synchronize the system for mesh communications according to various embodiments of the invention.
  • FIG. 19 is a flowchart illustrating a method of calculating a changed distance between a gateway and satellite, the changed distance used for synchronizing a satellite communications system for mesh communications according to various embodiments of the invention.
  • FIGS. 20A-20B are timing diagrams illustrating the use of a master terminal to set start of receive frame timing for mesh satellite communications according to various embodiments of the invention.
  • FIGS. 21 A-21B are timing diagrams illustrating the use of terminal to terminal timing data to set start of receive frame timing for mesh satellite communications according to various embodiments of the invention.
  • FIG. 22 is a block diagram illustrating components of one or more devices using terminal to terminal timing data for mesh synchronization in a satellite communications system according to various embodiments of the invention.
  • FIG. 23 is a block diagram illustrating an alternative configuration of components of one or more devices using terminal to terminal timing data for mesh synchronization in a satellite communications system according to various embodiments of the invention.
  • FIG. 24 is a flowchart illustrating a method of using terminal to terminal timing data to provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • FIG. 25 is a flowchart illustrating a method of self-synchronization for a terminal for mesh satellite communications according to various embodiments of the invention.
  • FIG. 26 is a flowchart illustrating a method of using a master terminal for synchronization for mesh satellite communications according to various embodiments of the invention.
  • FIG. 27 is a flowchart illustrating a method of using timing for a mesh communication path for synchronizing a satellite communications system according to various embodiments of the invention.
  • the arrival time of the gateway signal may be used to set a start of receive frame time for a terminal.
  • a received control signal from the gateway may then be used to set a start of transmit frame time for the terminal.
  • the distance between the satellite and the gateway may change.
  • ephemeris data may be used to modify start of transmit frame and start of receive frame settings for the terminal or gateway to achieve synchronization for mesh communications.
  • various collections of terminal measurements may be used to modify such start of transmit frame and start of receive frame settings.
  • a transmission from a terminal is used to set start of receive frame timing at a terminal for mesh communications. This transmission may be a self-sync burst or a broadcast burst from a master terminal.
  • FIG. 1 a block diagram is shown illustrating a satellite communications system 100 with various links 120. As shown in the illustrated embodiment, these may be mesh links 120-b. However, there may be star links 120-a as well, and thus in certain embodiments the system 100 is a mesh/star hybrid.
  • the system 100 includes a satellite 105, in communication with a gateway 110 and other user terminals 115 (which may be fixed, communications on the move (COTM), or other mobile or partially mobile terminals).
  • COTM communications on the move
  • MF-TDMA bursts from user terminals 115 to a gateway 110 may be set to arrive at specific times on certain frequencies.
  • the user terminals 115 transmissions are often synchronized to a master gateway 110, the synchronization based on control signals from the gateway terminal 110.
  • Different user terminals 115 may be located in different geographic locations, and be different distances from satellite 105.
  • user terminal 115 signals may have to travel for different amounts of time to reach the gateway 110 at the same time.
  • satellite 105 position changes may vary, causing the time delays between a gateway 110 and satellite 105 and between a satellite 105 and user terminals 115 to change.
  • synchronization updates for user terminals 115 may occur on a regular basis (e.g., every 10 minutes, every hour, every four hours, or adaptively).
  • DVB-RCS networks specify network timing procedures for a return link, where initial coarse timing established may be established for user terminals 115 based on geo- location of terminals 110, 115 and the satellite 105. Fine timing may based be on closed loop feedback procedure, where a gateway 110 monitors burst arrival times from a user terminal 115, and sends timing corrections back to a user terminal 115. To add mesh, a user terminal 115 -a could communicate with another user terminal 115-b also using return channel format (e.g., the same MF-TDMA channelization and timing as the return link). Thus, in such instances, bursts between user terminals 115 may need to be synchronized to ensure that time slots can be properly allocated and arrive at precise times.
  • the gateway-centric scheme measuring time between a gateway 110 and user terminal 115 of a DVB-RCS network, standing alone, may not be capable of such synchronization without additional information.
  • terminals 110, 115 include “sync modules,” which may be integrated processing units allowing a terminal 110, 115 to set or modify sync time for the timing of start of transmit frames or start of receive frames at a user terminal 115 or gateway 110.
  • start of receive frame may, but need not, be referred to as "SORF”
  • start of transmit frame may, but need not, be referred to as "SOTF”.
  • FIG. 2 a block diagram is shown illustrating an example configuration 200 for certain devices of the satellite communications system 100 of FIG. 1. While the example configuration illustrates communication between a COTM terminal 115 and gateway 110, those skilled in the art will recognize that similar components may be used between other links for the same or other types of terminals, or between a satellite and a terminal.
  • the sync modules 220, 245 may be used for a range of synchronization alternatives described below. This configuration may be used throughout this description to illustrate the different synchronization options.
  • an initiating terminal 205 transmits data via a network 210 (e.g., the Internet or a wireless local area network (LAN)) to the COTM terminal 115-b.
  • the data is received by the COTM terminal 115-b.
  • the COTM terminal 115-b is made up of a network layer processing module 215, a terminal frame timing module 220, a data link layer processing module 225, an RF frontend 230, and other components known in the art.
  • the received data may, for example, be a data packet carried by a wireless signal.
  • the data may be processed by a network layer processing module 215, and then forwarded to the data link layer processing module 225, where a data link protocol (e.g., HDLC) is applied.
  • the terminal frame timing module 220 may then set the timing for the transmission, perhaps based on synchronization messages (or other control signals) received from the gateway 110 and on a time slot allocation from the gateway 110. Note that the terminal frame timing module 220 may set the timing for receiving frames, based on different synchronization messages (or other control signals) received from the gateway 110.
  • the terminal frame timing module 220 may locally adjust expected receive or transmit times based on synchronization messages (or other control signals) received from the gateway 110.
  • synchronization messages may be generally referred to herein as control signals, and may include both synchronization specific control signals, and any other gateway transmission signals which are used to set or adjust timing.
  • the link layer packet is then processed by RF frontend 230, and transmitted via a wireless signal through the satellite 105 to the gateway 110 at the time specified by the terminal frame timing module 220.
  • the gateway 110 receives the signal.
  • the gateway 110 in this embodiment is made up of an RF frontend 235, data link layer processing module 240, gateway frame timing module 245, and network layer processing module 250.
  • Its RF frontend 235 may downconvert, amplify, and demodulate the signal, thereby reproducing the link layer packet from the COTM terminal 115-b.
  • the gateway frame timing module 245 may serve as the master for synchronization purposes, sending synchronization messages to the COTM terminal 115-b to control, receive, and transmit timing to and from the gateway.
  • the gateway frame timing module 245 may monitor arrival times of packets from the COTM terminal 115-b, and send control signals to correct the start of transmit time for the COTM terminal 115-b.
  • the gateway frame timing module 245 may also allocate time slots on the return link.
  • the gateway frame timing module 245 may set timing and send signals that may be used by the COTM terminal 115-b to adjust their receive times.
  • the data link layer processing module 240 of the gateway 110 may process the received packet, as known in the art, to produce the IP packet for the network layer processing module 250.
  • the data which originated at initiating terminal 205, and was routed through the COTM terminal 115-b, satellite 105, and fixed terminal 110, may then be passed through a network 210 to an end terminal 255. A similar process may occur for communications in the gateway to user terminal direction.
  • This set-up may synchronize properly when all communication between terminals 115 flows through the gateway 110. However, without certain additional information, the timing between user terminals 115 through the satellite 105 may not be known. In some embodiments, techniques are described for gateway and terminal frame timing modules to sync up so as to provide timing information for mesh communication.
  • a timing diagram 300 may be used to illustrate certain issues.
  • a user terminal 115 may be addressed as a "terminal” or “terminal 115”
  • a gateway 110 may be referred to as “gateway” or “gateway 110”
  • the satellite 105 may be referred to as "sat”, “sat 105”, or “satellite 105”.
  • the timing diagram 300 illustrates how the arrival time 305 at the gateway 110 of a terminal burst may be used by the gateway 110 to create a control message to be later sent to a terminal 115 to correct the start of transmit frame at the terminal 115.
  • the arrival time 310 at the terminal 115 of a gateway transmission may be used to locally adjust the start of receive frame time.
  • Terminal 115 start of receive frame and start of transmit frame may be established based on NCR value received from gateway 110.
  • timing for mesh transmissions between terminals 115 through a satellite 105 may not be able to be determined based solely on the above measurements.
  • the gateway 110 to terminal 115 times, standing alone, may not provide sufficient information to synchronize timing at the satellite 105 to provide for mesh communications.
  • One way to synchronize a terminal 115 for mesh transmissions is to coordinate the arrival of a mesh transmission at a satellite 105 with the arrival of a downstream transmission from the gateway 110 at the satellite 105. If points (for example, start of frame points ) may be coordinated at the satellite 315, the mesh communications timing problems may be addressed. However, there are a number challenges which may make this difficult or complex.
  • a timing diagram 400 illustrates how certain issues may arise for mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-f do not change.
  • the gateway 110 signal arrives 410 at terminal 115-f d ⁇ s earlier.
  • the travel time for a terminal 1 15-f signal sent to itself via a mesh link would not change.
  • a timing diagram 425 illustrates how synchronization operations could lead to timing errors in such situations.
  • a terminal 115-f may locally move 405 SORF left 430 by d ⁇ s because of the earlier arrival time of the gateway 110 transmission.
  • Gateway 110 may measure the offset of a terminal signal arrival and may send a correction to terminal 115-f, causing the terminal 115-f to move SOTF right 435 by d ⁇ s.
  • distance changes between satellite 105 and terminals 115 might be handled this way, and this is a standard DVB-RCS procedure.
  • a terminal to terminal mesh signal arrives at the terminal 2d ⁇ s late 440, as the terminal-to-terminal burst timing is off. If a gateway 110 receives its own signal from a satellite 105, these problems could be addressed to some extent using this information. It may be assumed that gateway 110, therefore, cannot receive its own signal or does not solve the problem with this information.
  • a timing diagram 450 illustrates how synchronization operations could lead to error in other situations.
  • Satellite 105 moves 455 toward terminal 115-f by d ⁇ s, while the distance between gateway 110 and terminal 115-f remains unchanged.
  • Gateway 110 signal arrival time at the terminal 115-f does not change, and terminal 115-f signal arrival time at gateway 110 does not change. So, according to certain traditional implementations, terminal 115-f SORF and SOTF would not change.
  • terminal 115-f signal arrives at terminal 115-f early 460 by 2d ⁇ s.
  • the gateway 110 may not be able to detect this condition by gateway 110 to terminal 115-f timing alone, and thus a design that uses gateway-terminal timing measurements only may not work. Even if a gateway 110 receives its own signal from a satellite 105, these problems may not be able to be addressed using that information alone.
  • gateway signals may be used to set start of receive frame timing and start of transmit frame timing for the terminal.
  • the distance between the satellite and the gateway may change.
  • ephemeris data is used to modify start of receive frame timing and start of transmit frame timing settings for the terminal or gateway to achieve synchronization for mesh communications.
  • a timing diagram 500 illustrates certain issues that may arise for mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-g do not change (as illustrated in FIG. 4A).
  • the gateway 110 signal arrives at terminal 115-g d ⁇ s earlier.
  • the travel time for a terminal 115-g signal sent to itself via a mesh link would not change.
  • a timing diagram 525 illustrates how certain synchronization techniques may avoid timing errors in some embodiments.
  • a satellite 105 or other source may transmit ephemeris data to the gateway 110.
  • This data may include latitude, longitude, height above the earth, or other information indicating the spatial position of the satellite 105 (perhaps relative to a gateway 110 or terminal 115).
  • a gateway 110 may use this ephemeris data to move its SOTF (the SOTF for the gateway) right 505 by d ⁇ s.
  • the gateway 110 may use the ephemeris data to determine when the signal from terminal 115-g arrives at the satellite 510, and move 505 its SOTF accordingly (so there is a common reference point 510 at the satellite).
  • the gateway 110 may use the ephemeris data to move its SORF left 520 by d ⁇ s. By doing so, the gateway 110 will not need to send correction directions to terminal 115-g, and instead will deem the arrival time of the terminal 115-g signal to be correct. According to one embodiment, therefore, the terminal 115-g timing does not change.
  • a timing diagram 600 again illustrates certain issues that may arise for synchronization with mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-h does not change (as illustrated in FIG. 4A).
  • the gateway 110 signal arrives at terminal 115-h d ⁇ s earlier.
  • the travel time for n terminal 115- h signal sent to itself via a mesh link would not change.
  • a timing diagram 625 illustrates how modified synchronization operations may avoid timing errors in some embodiments.
  • a satellite 105 or other source may transmit ephemeris data to the gateway 110, as described above.
  • a gateway 110 may use this ephemeris data, but in one embodiment does not move its SOTF (the SOTF for the gateway 110) right by d ⁇ s. Instead, the gateway 110 uses the ephemeris data to move its expected SORF left 605 by 2d ⁇ s.
  • Terminal 115-h may locally determine to move terminal SORF left 610 by d ⁇ s (e.g., because its local timing indicates that the signal from the gateway 110 is arriving d ⁇ s early).
  • the gateway 110 may measure and send a correction to terminal 115-h, for a terminal SOTF left move 615 by d ⁇ s (e.g., because after the gateway 110 SORF is moved left 605 by 2d ⁇ s, the gateway 110 thinks the signal received from the terminal 115-h is d ⁇ s late, and will send a correction signal accordingly).
  • the ephemeris data for the synchronization described with reference to FIGS. 5B and 6B may be generated and processed by the gateway 110, terminal 115, or other device or set of devices. A variety of other schemes may be used with the retrieved ephemeris data to adjust the timing for mesh communications. It is also worth noting the processing related to the ephemeris data may be performed by the gateway frame timing module 245 or terminal frame timing module 220 of FIG. 2, and may be used in the system 100 of FIG. 1 to achieve the synchronization of burst mesh communications with the downstream signal of the gateway 110.
  • the gateway 110 or terminal 115 may perform timing operations (e.g., various ping operations) on transmissions to the satellite, and the principles discussed with reference to FIGS. 5B and 6B may be applied thereto.
  • timing operations e.g., various ping operations
  • FIG. 7 a block diagram is shown illustrating an example configuration 700 of a gateway timing module 245-a and a transmission module 720 that may provide synchronization for mesh satellite communications according to various embodiments of the invention.
  • This configuration 700 may be implemented in the gateway 110 of FIG. 1 or 2.
  • These modules 245-a and 720 may, therefore, be the gateway frame timing module 245, data link layer processing module 240, and RF frontend 235 in the gateway 110 of FIG. 2. However, some or all of the functionality of these modules may be implemented in other devices or sets of devices.
  • the illustrated embodiment includes a memory module 705, a location determination module 710, a synchronization module 715, and a transmission module 720.
  • the memory module 705, location determination module 710, and synchronization module 715 may together make up the gateway timing module 245-a.
  • the modules illustrated in FIG. 7 may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • ASICs Application Specific Integrated Circuits
  • each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • the memory module 705 may be configured to store ephemeris data identifying the location of the satellite.
  • This ephemeris data may include coarse orbital parameters for a satellite (e.g. satellite 105 of FIG. 1).
  • the ephemeris data may include very precise orbital and clock information for the satellite as necessary for precise positioning.
  • the memory module may receive ephemeris data in substantially real-time from the satellite.
  • the ephemeris data indicating a location of the satellite may be received for a future period of time (e.g., an upcoming week, or month).
  • the memory module 705 may also be configured to store location data for a user terminal or gateway, reflecting real-time or forward-looking location data. This location data may include latitude, longitude, altitude, and any other information indicating the spatial position.
  • the location determination module 710 may use the stored ephemeris data and the stored location data for a gateway and user terminal to determine respective positions for the user terminal, gateway, and satellite. These may be the user terminal 115, gateway 110, and satellite 105 of FIG. l or 2.
  • the synchronization module 715 may use the ephemeris data and location data for a gateway and user terminal to set coarse start of transmit frame timing and start of receive frame timing at the gateway and the user terminal.
  • the timing may be set to establish a common point of reference at the satellite for frames transmitted by the gateway and the user terminal.
  • a set of control signals including timing information generated by the synchronization module 715 may be transmitted by transmission module 720 to a user terminal to refine the start of receive frame timing at the user terminal.
  • This set of control signals may be sent to all, or a subset, of the downstream terminals to set each terminal's start of receive frame timing.
  • a user terminal may use the receive time of the transmitted signals to set start of receive frame timing at the user terminal.
  • the set of control signals may simply be a standard downstream transmission, or may be formatted with the specific purpose of setting or adjusting receive frame timing at a receiving user terminal. In other embodiments, other forms of control signals may be used.
  • a set of signals may be transmitted (e.g., according to the coarse settings) from the user terminal via the satellite and received, for example, at the gateway.
  • the configuration 700 or, more specifically, the synchronization module 715 may use the receive time of the signals to determine refinements to the start of transmit frame timing at the user terminal.
  • the synchronization module 715 may generate a second set of control signals with information to refine the start of the transmit frame timing at the user terminal. This second set may be distributed to the user terminal by transmission module 720.
  • the coarse settings and refinements may be set to establish a common point of reference at the satellite for frames transmitted by the gateway and the user terminal, to allow for mesh satellite communications .
  • the ephemeris data may then be used by the location determination module 710 to identify an increase or a decrease in distance between the gateway and the satellite.
  • the location determination module 710 may also identify an increase or decrease in distance between the satellite and the user terminal.
  • the synchronization module 715 is configured to signal a change to the start of transmit frame timing and/or the start of receive frame timing at the user terminal or gateway when there is a differential in the changes in distances.
  • the synchronization module 715 is configured to signal a change to the start of transmit frame timing and/or the start of receive frame timing at the user terminal or gateway when there is simply a change in distance between the gateway and the satellite.
  • the synchronization module 715 may coordinate the changes to create a common point of reference and thereby maintain or set up a synchronized arrival, at the satellite, of frames or other signals transmitted from the user terminal and the gateway. This coordination may set up synchronization at the satellite for mesh satellite communications.
  • the synchronization module 715 may generate a set of control signals to be transmitted by transmission module 720 to a user terminal to change the start of receive frame timing at the user terminal.
  • the adjustment may be to set earlier start of receive frame timing (e.g., in the event that the gateway to satellite distance decreases), later start of receive frame timing (e.g., in the event that the gateway to satellite distance decreases), or simply maintain current start of receive frame timing.
  • This set of control signals may be sent to all, or a subset, of the downstream terminals.
  • Each user terminal may use the receive time of the transmitted signals to set start of receive frame timing at the user terminal. In such cases, the set of control signals may simply be a standard downstream broadcast transmission.
  • control signals may be formatted with the specific information directing the user terminal in setting or adjusting receive frame timing at the receiving user terminal. In other embodiments, other forms of control signals may be used.
  • the synchronization module 715 may generate an adjusted set of control signals to be transmitted by transmission module 720 to a user terminal to change the start of transmit frame timing at the user terminal.
  • a set of signals may first be transmitted from the user terminal according to a current start of transmit frame setting at the user terminal, and the transmission may be directed to the gateway via the satellite.
  • the configuration 700 or, more specifically, the synchronization module 715 may use the receive time of the signals from the user terminal, along with change of distance information from the ephemeris data, to determine an adjustment to the start of transmit frame timing (which may be earlier, later, or same timing) at the user terminal.
  • the synchronization module 715 may generate an adjusted set of control signals with information to change or maintain the start of the transmit frame timing at the user terminal based on the information in the adjusted set of control signals. This adjusted set may be transmitted to the user terminal by transmission module 720.
  • the refinements may be set to establish a common point of reference at the satellite for frames transmitted by the gateway and the user terminal, to allow for mesh satellite communications.
  • the synchronization module 715 may make the changes to the start of transmit frame timing and start of receive frame timing at the user terminal to create a common point of reference and thereby maintain (or set up) a synchronized arrival, at the satellite, of frames or other signals transmitted from the user terminal and the gateway. This may be done to allow for mesh communications to be facilitated within a star communications system.
  • the start of transmit frame timing at the gateway corresponds to the start of receive frame timing at the user terminals.
  • the start of transmit frame timing at the user terminals may correspond to the start of receive frame timing at the gateway.
  • timing changes may occur at the gateway (either in the start of transmit frame timing or start of receive frame timing, or both) in order to maintain timing at the user terminal (either in the start of transmit frame timing or start of receive frame timing, or both). This may be done to create a common point of reference at the satellite and thereby maintain (or set up) a synchronized arrival, at the satellite, of frames (or other signals) transmitted from the user terminal and the gateway.
  • FIG. 8 is a flowchart illustrating a method 800 of using ephemeris data to provide for synchronized mesh satellite communications in a system including a gateway and a terminal communicating via satellite, according to various embodiments of the invention.
  • the method 800 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the arrival time of the signal transmitted from the gateway to the terminal is used to set the start of receive frame timing at the terminal.
  • a control signal transmitted from the gateway is used to set the start of transmit frame timing at the terminal.
  • the distance between the satellite and the gateway changes.
  • ephemeris data is used to modify the start of transmit frame or the start of transmit frame settings for the terminal or gateway.
  • FIG. 9 is a flowchart illustrating a method 900 of synchronizing a satellite communications system for mesh communications using ephemeris data according to various embodiments of the invention.
  • the method 900 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 900 may be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 700 illustrated in FIG. 7.
  • a first set of control signals is transmitted to set a start of receive frame for a user terminal.
  • a second set of control signals is transmitted to set a start of transmit frame for the user terminal.
  • ephemeris data identifying a change in distance between the gateway and the satellite is received.
  • transmission timing is adjusted for one or more signals of the first or second set to account for the change in distance between the gateway and the satellite.
  • FIG. 10 is a flowchart illustrating a method 1000 of using ephemeris data for synchronizing a satellite communications system for mesh communications by delaying a transmission time for control signals to be used to set terminal start of receive frame timing, according to various embodiments of the invention.
  • the method 1000 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 1000 may also be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 700 illustrated in FIG. 7.
  • ephemeris data indicating the location of the satellite for a future period of time is received and stored.
  • a first set of control signals is transmitted to set start of receive frame timing for a user terminal during a first portion of the future period.
  • a second set of control signals is transmitted to set start of transmit frame timing for the user terminal during a first portion of the future period.
  • the ephemeris data is used to identify a decrease in distance between the gateway and the satellite during a second portion of the future period.
  • Block 1025 during the second portion of the future period, the transmission of additional control signals to set the start of receive frame timing for a user terminal is delayed, to thereby synchronize arrival at the satellite of frames from the user terminal and the gateway.
  • Block 1025 may be performed in conjunction with setting an earlier start of receive frame time at the gateway to account for the earlier arrival time at the gateway of signals from the user terminal.
  • FIG. 11 is a flowchart illustrating a method 1100 of using ephemeris data for synchronizing a satellite communications system for mesh communications by adjusting transmission times for control signals to be used to set start of frame timing at a user terminal, according to various embodiments of the invention.
  • the method 1100 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 1100 may also be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 700 illustrated in FIG. 7.
  • ephemeris data indicating the location of the satellite for a future period of time is received and stored.
  • coarse start of transmit frame timing and start of receive frame timing are set at the gateway and the user terminal based on ephemeris data and location data for a gateway and user terminal, the timing set to establish a common point of reference for frames transmitted by the gateway and the terminal.
  • a first set of signals is transmitted from the gateway to a user terminal to refine the start of receive frame timing at the user terminal.
  • a second set of signals is received at the gateway from a user terminal.
  • a third set of signals is transmitted from the gateway to the user terminal to refine the start of the transmit frame timing at the user terminal based on the arrival time of the second set of signals.
  • the ephemeris data is used to identify a decrease in distance between the gateway and the satellite during the future period, wherein there is a smaller decrease in distance between the satellite and the user terminal.
  • a transmission time for a fourth set of signals is delayed from the gateway to a user terminal to change the start of receive frame timing at the user terminal.
  • information in a fifth set of signals transmitted from the gateway to a user terminal is changed to adjust the start of transmit frame timing at the user terminal to an earlier time; based on the ephemeris data, wherein the delay (at block 1135) and the adjustment (at block 1140) are set to maintain the common point of reference.
  • gateway signals may be used to set start of receive frame timing and start of transmit frame timing for the terminal.
  • the distance between the satellite and the gateway may change.
  • various collections of terminal measurements may be used to modify such start of transmit frame and start of receive frame settings.
  • a user terminal e.g. user terminal 115
  • the user terminal may then transmit the time measurement identifying a transmit time between the user terminal and the satellite (which may, for example, be a one way or round trip time from the user terminal to the satellite and back to the user terminal on the mesh link).
  • the gateway may receive the time measurement identifying transmit time between the user terminal and the satellite. It may use the received time measurement to calculate a changed distance between the gateway and the satellite (e.g., by comparing it to measured transmit time between the gateway and user terminal). The gateway may then adjust, responsive to the change in distance between the gateway and the satellite, one or more control signals to be transmitted to set start of receive frame timing or start of transmit frame for the user terminal. The adjustment may be set to synchronize timing for mesh satellite communications.
  • a timing diagram 1200 illustrates how the timing issues may arise for synchronization with mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-i do not change (as illustrated in FIG. 4A).
  • the gateway 110 signal arrives at terminal 115-i d ⁇ s earlier.
  • the travel time for a terminal 115-i signal sent to itself via a mesh link would not change.
  • a timing diagram 1225 illustrates the first stages of a synchronization operation which may produce timing errors.
  • Terminal 115-i locally adjusts its SORF left 1230 by d ⁇ s, based on measurements of the signal received from the gateway 110, as would be done in prior art solutions.
  • Gateway 110 measures the received timing of signals received from terminal 115- i, and sends control signals to direct terminal 115-i to move its SOTF right 1235 by d ⁇ s.
  • a timing diagram 1250 illustrates how modified synchronization operations may avoid such timing errors in some embodiments.
  • one or more terminals 115 may measure the timing and/or offset of received terminal to terminal bursts (e.g., the offset for terminal 115-i is 2d ⁇ s).
  • the gateway 110 may be configured to collect such timing measurements and/or offsets from one or more terminals 115 (e.g., by querying terminals 115, or simply collecting information sent from terminals 115).
  • the gateway 110 may average timing measurements and/or offset values for the collected measurements, and compute d ⁇ s.
  • the gateway 110 may then attempt to realign the burst timing at the satellite 105 with the downstream signal at the satellite 105. To do so, in one embodiment, the gateway 110 moves its SOTF right 1255 by d ⁇ s, and moves its SORF left 1260 by d ⁇ s. Terminal 115-i would then locally adjust its SORF right 1265 by d ⁇ s, based on measurements of the signal received from the gateway 110. Gateway 110 measures the received timing of signals received from terminal 115-i, and sends control signals to direct terminal 115-i to move its SOTF left 1270 by d ⁇ s. The burst timing at the satellite 105 would thereby be realigned 1275 with the downstream signal at the satellite 105.
  • a timing diagram 1300 again illustrates certain issues that may arise for synchronization with mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-j do not change (as illustrated in FIG. 4A).
  • the gateway 110 signal arrives at terminal 115-j d ⁇ s earlier.
  • the travel time for a terminal 115-i signal sent to itself via a mesh link would not change.
  • a timing diagram 1325 illustrates the first stages of a synchronization operation which could produce timing errors.
  • terminal 115-j locally adjusts its SORF left 1330 by d ⁇ s, based on measurements of the signal received from the gateway 110, as would be done in prior art solutions.
  • Gateway 110 measures the received timing of signals received from terminal 115- j, and sends control signals to direct terminal 115-j to move its SOTF right 1335 by d ⁇ s.
  • a timing diagram 1350 illustrates how modified synchronization operations may avoid timing errors in some embodiments.
  • one or more terminals 115 may perform time measurements and/or offset measurements of received terminal to terminal bursts (e.g., the offset for terminal 115-j 2d ⁇ s).
  • the gateway 110 may be configured to collect one or more of such time measurements and/or offsets from one or more terminals 115 (e.g., by querying terminals 115, or simply collecting information sent from terminals 115).
  • the gateway 110 may average these values for the collected measurements and compute d ⁇ s.
  • the gateway 110 may then attempt to realign the burst timing at the satellite 105 with the downstream signal at the satellite 105. To do so, the gateway 110 does not move its SOTF, and instead moves its SORF left 1355 by 2 d ⁇ s based on the collected measurements. Terminal 115-j would not need to locally adjust its SORF, as based on measurements of the signal received from the gateway 110 the timing remains synchronized. However, gateway 110 measures the received timing of signals received from terminal 115-j, and sends control signals to direct terminal 115-j to move its SOTF left 1360 by Id ⁇ s (to compensate for the gateway SORF move left 1355 by Id ⁇ s). The burst timing at the satellite 105 would thereby be realigned 1365 with the downstream signal at the satellite 105. This is a variation on the synchronization set forth in FIGS. 7A-7C.
  • the terminal 115 measurement for the synchronization described with reference to FIGS. 12C and 13C may be processed by the gateway 110, a master terminal 115, or other device or set of devices. A variety of other schemes may be used with the collected terminal 115 measurements to adjust the timing for mesh communications. It is also worth noting the processing and adjustments related to the collected terminal 115 measurements may be performed by the gateway frame timing module 245 and/or terminal frame timing module 220 of FIG. 2, and be used in the system 100 of FIG. 1, to achieve the synchronization of burst mesh communications with the downstream signal of the gateway 110.
  • the gateway 110 or terminal 115 may perform timing operations (e.g., various ping operations) on transmissions to the satellite, and the principles discussed with reference to FIGS. 12C and 13C may be applied thereto.
  • timing operations e.g., various ping operations
  • the term "time measurement" for terminal-to-terminal bursts may include round-trip time, one way time, or simply the offset time, as well as any number of other schemes as evident to those skilled in the art.
  • FIG. 14 a block diagram is shown illustrating an example configuration 1400 of a gateway timing module 245-b and a transmission module 1420 that may provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • This configuration 1400 may be implemented in the gateway 110 of FIG. 1 or 2.
  • These modules 245 -a and 1420 may, therefore, be the gateway frame timing module 245, data link layer processing module 240, and RF frontend 235 in the gateway 110 of FIG. 2. However, some or all of the functionality of these modules may be implemented in other devices or sets of devices.
  • the illustrated embodiment includes a memory module 1405, a distance determination module 1410, a synchronization module 1415, and a transmission module 1420.
  • the memory module 1405, distance determination module 1410, and synchronization module 1415 may together make up the gateway timing module 245-b.
  • the memory module 1405 may receive and store a first time measurement corresponding to a transmit time between the user terminal and the satellite (e.g., the time measurement may be received via the satellite from the user terminal, and may be a one way or round trip time).
  • the memory module 1405 may receive and store a second time measurement corresponding to a transmit time between the gateway and the user terminal via the satellite (e.g., the time measurement may be measured at the gateway or user terminal, and may be a one way or round trip time).
  • the memory module 1405 may also be configured to store other location data for the satellite, user terminal, or gateway, reflecting real-time or forward looking location data. This location data may include latitude, longitude, altitude, and any other information indicating the spatial position.
  • the distance determination module 1410 may use the timing measurements and the stored location data to determine respective positions for the user terminal, gateway, and satellite. These may be the user terminal 115, gateway 110, and satellite 105 of FIG. 1 or 2.
  • the synchronization module 1415 may use the timing measurements and location data for a gateway and user terminal to set coarse start of transmit frame timing and start of receive frame timing at the gateway and the user terminal, and then perform refinements as described above.
  • the timing may be set to establish a common point of reference at the satellite for frames transmitted by the gateway and the user terminal.
  • the distance determination module 1410 may be configured to calculate a changed distance between the gateway and the satellite based at least in part on a series of the first and second timing measurements (e.g., by comparing the first and second time measurement at different times).
  • the synchronization module 1415 may be configured to adjust, responsive to the change in distance between the gateway and the satellite, one or more control signals to be transmitted to set start of receive frame timing and/or set start of transmit frame timing for the user terminal. The adjustments may be made to synchronize timing for mesh satellite communications, setting or maintaining a common point of reference at the satellite.
  • the transmission module 1420 may be configured to transmit the adjusted one or more signals.
  • FIG. 15 a block diagram is shown illustrating an example configuration 1500 of a receiver module 1505, a gateway timing module 245-c, and a transmission module 1420-a that may provide synchronization for mesh satellite communications according to various embodiments of the invention.
  • This configuration 1500 may be the configuration 1400 of FIG. 14, and may be implemented in the gateway 110 of FIG. 1 or 2. However, some or all of the functionality of these modules may be implemented in other devices or sets of devices.
  • the receiver module 1505 may receive, from the user terminal, a first time measurement corresponding to the transmit time between the user terminal and the satellite, the first time measurement calculated by the user terminal. This first time measurement may be stored in UT-UT table 1515 of the memory module 1405-a in the synchronization module 245-c. This UT-UT table 1515 of the memory module 1405-a may store additional time measurements, received from a number of additional user terminals, corresponding to the transmit time between each respective user terminal and the satellite.
  • the receiver module 1505 may also receive round trip or other signals from the user terminal. Using these signals, a GW-UT timing determination module 1510 may perform a second time measurement corresponding to the transmit time between the user terminal and the gateway (which may be a one way or round trip transit time). This second time measurement may be stored in GW-UT table 1520 of the memory module 1405-a.
  • a GW-Sat timing determination module 1525 may receive and compare the first time measurement to the second time measurement from the memory module 1405-a, and use the comparison to calculate a changed distance between the gateway and the satellite based at least in part of the first and second timing measurements.
  • the calculation of a changed distance may be a time or distance metric, as evident to those skilled in the art.
  • the synchronization module 1415-a may be configured to adjust, responsive to the change in distance between the gateway and the satellite, one or more control signals to be transmitted to set a start of receive frame timing and/or set a start of transmit frame timing for the user terminal.
  • the synchronization module 1415-a may include a terminal SOTF module 1530 to generate control signals to set a start of transmit frame timing for the user terminal, and a terminal SORF module 1535 to generate control signals to set start of receive frame timing at the user terminal.
  • the adjusted signals may be transmitted to the user terminal by the transmission module 1420-a.
  • the GW-Sat timing determination module 1525 may identify an increase or a decrease in distance between the gateway and the satellite. There may also be a related increase or decrease in distance between the satellite and the user terminal. As noted above, there may be issues when the changes in distance differ.
  • the synchronization module 1415-a is configured to signal a change to the start of transmit frame timing and/or the start of receive frame timing at the user terminal or gateway when there is a differential in the changes in distances. In other embodiments, the synchronization module 1415-a is configured to signal a change to the start of transmit frame timing and/or the start of receive frame timing at the user terminal or gateway when there is simply a change in distance between the gateway and the satellite.
  • the adjustment to the start of transmit frame timing may be set by the terminal SOTF module 1530 and the adjustment to the start of receive frame timing may be set by the terminal SORF module
  • the synchronization module 1415-a may coordinate the changes to create a common point of reference and thereby maintain or set up a synchronized arrival, at the satellite, of frames or other signals transmitted from the user terminal and the gateway. This coordination may set up synchronization at the satellite for mesh satellite communications.
  • the terminal SORF module 1535 may generate a set of control signals to be transmitted by transmission module 1420-a to a user terminal to change the start of receive frame timing at the user terminal.
  • the adjustment may be to set earlier start of receive frame timing (e.g., in the event that the gateway to satellite distance decreases), later start of receive frame timing (e.g., in the event that the gateway to satellite distance decreases), or simply maintain current start of receive frame timing.
  • This set of control signals may be sent to all, or a subset, of the downstream terminals.
  • Each user terminal may use the receive time of the transmitted signals to set start of receive frame timing at the user terminal. In such cases, the set of control signals may simply be a standard downstream broadcast transmission.
  • control signals may be formatted with the specific information directing the user terminal in setting or adjusting receive frame timing at the receiving user terminal. In other embodiments, other forms of control signals may be used.
  • the terminal SOTF module 1530 may generate an adjusted set of control signals to be transmitted by transmission module 1420-a to a user terminal to change the start of transmit frame timing at the user terminal.
  • a set of signals may initially be transmitted from the user terminal according to a current start of transmit frame timing setting at the user terminal, the set of signals transmitted to the gateway via satellite.
  • the configuration 1500 or, more specifically, the terminal SOTF module 1530 may use the receive time of the signals from the user terminal, along with changed distance information from the measurement data, to determine an adjustment to the start of transmit frame timing (which may be earlier, later, or same timing) at the user terminal.
  • components of the synchronization module 1415-a may generate an adjusted set of control signals with information to change or maintain the start of the transmit frame timing at the user terminal based on the information in the adjusted set of control signals.
  • This adjusted set may be transmitted to the user terminal by transmission module 1420-a.
  • the refinements may be set to establish a common point of reference at the satellite for frames transmitted by the gateway and the user terminal, to allow for mesh satellite communications.
  • the synchronization module 1415-a may make the changes to the start of transmit frame timing and start of receive frame timing at the user terminal to create a common point of reference and thereby maintain (or set up) a synchronized arrival, at the satellite, of frames or other signals transmitted from the user terminal and the gateway. This may be done to allow for mesh communications to be facilitated within a star communications system.
  • the start of transmit frame timing at the gateway corresponds to the start of receive frame timing at the user terminals.
  • the start of transmit frame timing at the user terminals may correspond to the start of receive frame timing at the gateway. Therefore, while much of the discussion above relates to control signals sent by the gateway to change timing at the user terminal, note that there may in these embodiments be corresponding changes to the start of transmit frame and start of receive frame timing at the gateway (e.g., a later start of transmit frame timing at the user terminal may correspond to a later start of receive frame timing at the gateway, or an earlier start of receive frame timing at the user terminal may correspond to an earlier start of transmit frame timing at the gateway).
  • timing changes may occur at the gateway (either in the start of transmit frame timing or start of receive frame timing, or both) in order to maintain timing at the user terminal (either in the start of transmit frame timing or start of receive frame timing, or both). This may be reversed, as well. This may be done to create a common point of reference at the satellite and thereby maintain (or set up) a synchronized arrival, at the satellite, of frames (or other signals) transmitted from the user terminal and the gateway.
  • the modules illustrated in FIG. 14 and FIG. 15 may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs Application Specific Integrated Circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi- Custom ICs), which may be programmed in any manner known in the art.
  • the functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • FIG. 16 is a flowchart illustrating a method 1600 of using terminal to satellite timing data to provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • the method 1600 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the arrival time of a signal transmitted from the gateway is used to set the start of receive frame timing at the terminal.
  • a control signal transmitted from the gateway is used to set the start of transmit frame timing at the terminal.
  • the distance between the satellite and the gateway changes.
  • a time measurement corresponding to the terminal to satellite transit time is used to modify the start of receive frame or the start of transmit frame settings for the terminal.
  • the time measurement corresponding to the terminal to satellite transit time may be subtracted from the terminal to gateway transmit time to establish the gateway to satellite transmit time.
  • the gateway to satellite transmit time may be used to set a common reference point for frames from the terminal and the gateway at the satellite, and thereby facilitate mesh communications.
  • FIG. 17 is a flowchart illustrating a method 1700 of calculating a changed distance between a gateway and satellite for synchronizing a satellite communications system for mesh communications according to various embodiments of the invention.
  • the method 1700 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 1700 may also be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 1400 illustrated in FIG. 14 or configuration 1500 illustrated in FIG. 15.
  • first data is identified corresponding to a first distance between a user terminal and a satellite, the first data calculated based on a terminal-to-terminal communication via satellite on a mesh communication path.
  • second data is identified corresponding to a second distance between a gateway and the user terminal via the satellite.
  • the first data and the second data may be time and/or distance measurements, or in some embodiments may be other metrics.
  • the first data and the second data are used to calculate data corresponding to a changed distance between the gateway and the satellite.
  • one or more signals to set start of receive frame or start of transmit frame settings for the user terminal are adjusted, the adjustment in response to the calculated data.
  • FIG. 18 is a flowchart illustrating a method 1800 of calculating a changed transmit time between a gateway and satellite for purposes of synchronizing a satellite communications system for mesh communications according to various embodiments of the invention.
  • the method 1800 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 1800 may also be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 1400 illustrated in FIG. 14 or configuration 1500 illustrated in FIG. 15.
  • a first time measurement corresponding to a transmit time between the user terminal and the satellite is stored.
  • a second time measurement corresponding to a transmit time between the gateway and the user terminal via the satellite is stored.
  • a decreased transmit time between the gateway and the satellite is calculated based at least in part of the first and second time measurements.
  • the decreased transmit time calculation is used to identify a decrease in distance between the gateway and the satellite.
  • a transmission time is delayed for additional control signals used to set start of receive frame timing for the user terminal, to thereby synchronize arrival at the satellite of frames from the user terminal and the gateway.
  • FIG. 19 is a flowchart illustrating a method 1900 of calculating a changed distance between a gateway and satellite, the changed distance used for synchronizing a satellite communications system for mesh communications according to various embodiments of the invention.
  • the method 1900 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 1900 may also be performed by the gateway 110 of FIG 1 or 2 or, more specifically, by the configuration 1400 illustrated in FIG. 14 or configuration 1500 illustrated in FIG. 15.
  • first time measurements identifying a transmit time between a gateway and one or more user terminals via a satellite are calculated at the gateway.
  • each user terminal calculates second time measurements identifying a transmit time between each respective user terminal and the satellite.
  • the second time measurements from each of the one or more user terminals are received at the gateway via transmissions from the user terminals.
  • a series of comparisons are performed between the first time measurements and the second time measurements for one or more of the user terminals to monitor the distance between the gateway and the satellite.
  • a decrease in distance between the gateway and the satellite is identified based on the monitoring, wherein there is a smaller decrease in distance between the satellite and user terminal.
  • a transmission time is delayed for a set of signals transmitted from the gateway to a user terminal and used to change the start of receive frame timing at the user terminal.
  • an adjustment is made for a set of signals to be transmitted from the gateway to a user terminal, the adjustment made to set an earlier transmission time for the start of transmit frame timing at the user terminal, where the delay (at block 1930) and the adjustment (at block 1935) are set to maintain a common point of reference for transmission to the satellite, based on the changed distance between the gateway and the satellite.
  • Novel synchronization techniques for mesh satellite communications using terminal self-synchronization are described.
  • various gateway signals may be used at a terminal to set start of receive frame timing for communications from the gateway and set start of transmit frame timing for the terminal for communications to the gateway and to other terminals.
  • the distance between the satellite and the gateway may change.
  • a terminal self-synchronization process may be used to modify start of receive frame settings for mesh communications received from the other terminals.
  • a gateway e.g., gateway 110
  • the gateway may transmit a second set of signals to set a start of transmit frame timing for the user terminal for communications to the gateway and communications to other user terminals.
  • the user terminal may receive (via satellite) and use the first set of signals to set start of receive frame timing for communications received at the user terminal from the gateway.
  • the user terminal may receive (via satellite) and use the second set of signals to set a start of transmit frame timing for the user terminal for communications to the gateway and communications to other user terminals via the satellite.
  • the user terminal may receive and use a third set of signals to set start of receive frame timing for mesh communications received at the user terminal from other user terminals via the satellite.
  • the gateway may maintain its start of receive frame and start of transmit frame settings, even in the face of a change in distance between the gateway and satellite.
  • the gateway will, instead, transmit control signals to the user terminals that will adjust the relevant start of receive frame and start of transmit frame settings at the user terminal.
  • the user terminal will, in such embodiments, use terminal to terminal bursts to set start of receive frame timing for mesh communications.
  • a timing diagram 2000 again illustrates issues that may arise for synchronization with mesh communications.
  • the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-k does not change (as illustrated in FIG. 4A).
  • the gateway 110 signal arrives at terminal 115-k d ⁇ s earlier.
  • the travel time for a terminal 115- k signal sent to itself via a mesh link would not change.
  • a timing diagram 2025 illustrates how modified synchronization operations may avoid timing errors in some embodiments.
  • gateway 110 does not make any local adjustments to its SOTF or SORF timing.
  • Gateway 110 measures the received timing of signals received from terminal 115-k, and sends control signals to direct terminal 115-k to move its SOTF right 2030 by d ⁇ s.
  • terminal 115-k makes a correction (note that in other embodiments, the correction 2030 may be based on other correction schemes).
  • Terminal 115-k moves its SOTF right 2030 by d ⁇ s.
  • Terminal 115-k may then track SORF mesh timing based on the arrival of a special mesh burst from another terminal 115.
  • This monitored burst may be a special, modified terminal to terminal burst, and not the gateway 110 signal.
  • This burst is transmitted in accordance with SOTF timing for the terminal 115-k return link (as modified).
  • it may be arranged for one terminal to serve as a "master terminal” for mesh communications, and periodically transmit this special broadcast burst, which may then be received by all other mesh terminals 115. All the receiving mesh terminals 115 may then adjust 2035 their SORF timing for mesh communications off this burst. This designation may be made by gateway 110 or by devices other than the gateway 110, or may be set in advance.
  • a terminal 115-k may have two distinct SORF times: one 2040 for the downstream transmissions from the gateway 110 and one 2045 for mesh communications.
  • This master terminal mesh synchronization broadcast scheme may be configured to work for satellite 105 - terminal 115 distance changes also.
  • a timing diagram 2100 illustrates issues that may arise for synchronization with mesh communications. Assume that the gateway 110 and satellite 105 move 405 closer together by d ⁇ s, while the distance between the satellite 105 and the terminal 115-1 do not change (as illustrated in FIG. 4A). In this instance, the gateway 110 signal arrives at terminal 115-1 d ⁇ s earlier. The travel time for a terminal 115-1 signal sent to itself via a mesh link would not change. [0124] Continuing the discussion from FIG. 21 A, and turning to FIG. 21B, a timing diagram 2125 illustrates how modified synchronization operations may avoid timing errors in some embodiments.
  • gateway 110 does not make any local adjustments to its SOTF or SORF timing.
  • Gateway 110 measures the received timing of signals received from terminal 115-1, and sends control signals to direct terminal 115-1 to move its SOTF right 2130 by d ⁇ s.
  • terminal 115-1 makes a correction (note, however, that in other embodiments, the correction 2130 may be based on other correction schemes).
  • Terminal 115-1 moves its SOTF right 2130 by d ⁇ s.
  • Terminal 115-1 may then track SORF mesh timing based on arrival of its own burst.
  • This burst may be a special, modified terminal to terminal burst, and not the gateway 110 signal.
  • This burst is transmitted in accordance with the same timing as the terminal 115-1 SOTF timing for the return link (as modified).
  • the gateway 110 may arrange for each terminal 115 to send and receive its own sync bursts.
  • the mesh terminals 115 may then adjust 2135 their SORF timing for mesh communications off their own burst. This differs from certain embodiments described above, where the mesh timing is achieved by synchronization with the downstream gateway transmissions.
  • a terminal 115-1 may have two distinct SORF times: one 2140 for the downstream transmissions from the gateway 110 and one 2145 for mesh communications.
  • This terminal self-sync scheme for mesh synchronization may be configured to work for satellite 105 - terminal 115 distance changes also.
  • the control of the terminal broadcast sync described with reference to FIG. 2OB and terminal self-sync described with reference to FIG. 21B may be undertaken by the gateway 110, a master terminal 115, another device or set of devices, or any combination thereof. It is also worth noting the synchronization and adjustments related to the terminal broadcast sync of FIG. 2OB or self-sync may be performed by the terminal frame timing module 220 of FIG. 2, and be used in the system 100 of FIG. 1, to achieve the synchronization of burst mesh communications.
  • FIG. 22 a block diagram is shown illustrating an example configuration 2200 that may provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • This configuration 2200 includes a receiver 2220 and a synchronization module 2205, which may be implemented in the user terminal 115 of FIG. 1 or 2. These modules 2220 and 2205 may, therefore, be the terminal frame timing module 220, and RF frontend 230 in the terminal 115-a of FIG. 2.
  • the illustrated embodiment includes a star receiver module 2210 and a mesh receiver module 2215 which may together make up a portion of the receiver 2220. However, some or all of the functionality of the modules of configuration 2200 may be implemented in other devices or sets of devices.
  • the synchronization module 2205 may receive and use a first set of signals to identify first start of receive frame timing for communications received at the user terminal via satellite from a gateway.
  • the first set of signals may be generated at and transmitted from the gateway, and be received by receiver 2220 and forwarded to the frame synchronization module 2205.
  • the synchronization module 2205 may receive and use a second set of signals to identify a second start of receive frame timing for communications received at the user terminal via satellite from other user terminals.
  • the second set of signals may be generated at and transmitted from a terminal (e.g., a master terminal sending a broadcast burst, or a user terminal that sends a burst to itself via satellite), and be received by receiver 2220 and forwarded to the synchronization module 2205.
  • the receiver 2220 may include a star receiver module 2210 configured to receive communications from the gateway via satellite according to the first start of receive frame timing.
  • the synchronization module 2205 may set the start of receive frame timing (using the first set of signals) for the star receiver module 2210 for communications from the gateway.
  • the receiver 2220 may also include a mesh receiver module 2215 configured to receive communications from the other user terminals according to the second start of receive frame timing.
  • the synchronization module 2205 may set the start of receive frame timing (using the second set of signals) for the mesh receiver module 2215 for communications from other terminals.
  • FIG. 23 a block diagram is shown illustrating an alternative example configuration 2300 that may provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • This configuration 2300 includes a receiver 2220-a, a synchronization module 2205-a, and a transmission module 2320, which may be implemented in the terminal 115 of FIG. 1 or 2.
  • These modules 2220-a, 2205-a, and 2320 may, therefore, be the terminal frame timing module 220, and RF frontend 230 in the terminal 115-a of FIG. 2.
  • the illustrated embodiment includes a star receiver module 2210-a and a mesh receiver module 2215-a which may together make up a portion of the receiver 2220-a.
  • the illustrated embodiment also includes a transmission sync module 2305, star receiver sync module 2310, and mesh receiver sync module 2315 which may together make up a portion of the synchronization module 2205-a.
  • the star receiver sync module 2310 may receive and use a first set of signals to identify first start of receive frame timing for communications received at the user terminal via satellite from a gateway (e.g., via a star communications link).
  • the first set of signals may be generated at and transmitted from the gateway, and may be received by the star receiver module 2210-a and forwarded to the star receiver sync module 2310.
  • the mesh receiver sync module 2315 may receive and use a second set of signals to identify second start of receive frame timing for mesh communications received at the user terminal via satellite from other user terminals.
  • the second set of signals may be generated at and transmitted from a terminal (e.g., a terminal sending a broadcast burst, or a user terminal that sends a burst to itself via satellite), and may be received by the mesh receiver module 2215-a and forwarded to the mesh receiver sync module 2315.
  • the transmission sync module 2305 may receive and use a third set of signals to set the start of transmit frame timing for communications transmitted from the user terminal via satellite to either the gateway or other user terminals.
  • the third set of signals may be generated at and transmitted from the gateway, and be received by the star receiver module 2210-a and forwarded to the transmission sync module 2305.
  • the receiver 2220-a may include a star receiver module 2210-a configured to receive communications from the gateway via satellite.
  • the star receiver sync module 2310 may set the start of receive frame timing (using the first set of signals) for the star receiver module 2210-a for communications from the gateway.
  • the receiver 2220-a may also include a mesh receiver module 2215 -a configured to receive communications from the other user terminals.
  • the mesh receiver sync module 2315 may set the start of receive frame timing (using the second set of signals) for the mesh receiver module 2215-a for communications from other terminals.
  • the transmission module 2320 may transmit both star communication signals (transmission to the gateway via satellite) and mesh communication signals (transmission directly to other user terminals via satellite).
  • the transmission sync module 2305 may set the start of transmit frame timing (using the third set of signals) for the transmission module 2320.
  • the transmission module 2320 may send a terminal-to-terminal broadcast burst (e.g., the second set of signals) according to the start of transmit frame timing, the burst setting the start of receive frame timing for mesh communications at other terminals.
  • the gateway may (but need not) maintain its start of receive frame and start of transmit frame settings, even in the face of a change in distance between the gateway and satellite.
  • user terminals each implement the components of the configuration 2400 of FIG. 24.
  • the gateway may transmit the first set of signals to the user terminals to adjust the start of receive frame settings at each user terminal for communications from the gateway (while the start of transmit frame settings at the gateway are maintained).
  • the first set of signals (e.g., received via the star receiver module 2210-a) may set start of receive frame timing at the user terminal based on a reception time of the first set of signals at the user terminal.
  • the gateway may also transmit the third set of signals to user terminals to adjust the start of transmit frame settings at the user terminal (while the start of receive frame settings at the gateway are maintained).
  • the third set of signals (received via the star receiver module 2210-a) may adjust the start of transmit frame timing at the user terminal.
  • the third set of signals may be generated and transmitted by the gateway in response to reception time at the gateway of signals transmitted from the transmission module 2320.
  • a user terminal implementing the components of FIG. 23 may use terminal to terminal bursts to set start of receive frame timing for mesh communications.
  • the second set of signals (received via the mesh receiver module 2215-a) may set start of receive frame timing at the user terminal based on a reception time of the transmissions from the user terminal itself, or from another terminal (e.g., from a master terminal).
  • the modules illustrated in FIG. 22 and FIG. 23 may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.
  • ASICs Application Specific Integrated Circuits
  • the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits.
  • other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi- Custom ICs), which may be programmed in any manner known in the art.
  • the functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.
  • FIG. 24 is a flowchart illustrating a method 2400 of using terminal to terminal timing data to provide for synchronized mesh satellite communications according to various embodiments of the invention.
  • the method 2400 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the arrival time of a signal transmitted from the gateway is used to set the start of receive frame timing at a receiving terminal for communications from the gateway.
  • the arrival time of a signal transmitted from a transmitting terminal (the receiving terminal may, but need not, be different from the transmitting terminal) is used to set the start of receive frame timing at the receiving terminal for mesh communications from the terminals.
  • the distance between the satellite and the gateway changes.
  • the arrival time of the signal transmitted from the transmitting terminal is used after the distance changes to adjust the timing for the start of receive frame at the receiving terminal for mesh communications.
  • FIG. 25 is a flowchart illustrating a method 2500 of self-synchronization for a terminal for mesh satellite communications according to various embodiments of the invention.
  • the method 2500 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 2500 may also be performed by the terminal 115 of FIG 1 or 2 or, more specifically, by the configuration 2200 illustrated in FIG. 22 or configuration 2300 illustrated in FIG. 23.
  • a first set of signals is received from the gateway to set the start of receive frame timing at a user terminal for communications from the gateway.
  • a second set of signals is received from the gateway to set the start of transmit frame timing for the user terminal for both communications to the gateway and communications to other user terminals.
  • a third set of signals transmitted by the user terminal via a mesh communication path is received at the user terminal to set the start of receive frame timing at the user terminal for mesh communications from other user terminals.
  • the distance between the satellite and the gateway changes.
  • the third set of signals is used to adjust the start of receive frame timing at the user terminal for mesh communications from other user terminals.
  • FIG. 26 is a flowchart illustrating a method 2600 of using a master terminal for synchronization for mesh satellite communications according to various embodiments of the invention.
  • the method 2600 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 2600 may also be performed by the terminal 115 of FIG 1 or 2 or, more specifically, by the configuration 2200 illustrated in FIG. 22 or configuration 2300 illustrated in FIG. 23.
  • a first set of signals is received from the gateway to set the start of receive frame timing at a user terminal for communications from the gateway.
  • a second set of signals is received from the gateway to set a start of transmit frame timing for the user terminal for both communications to the gateway and communications to other user terminals.
  • a master terminal transmits bursts via a satellite to set the start of receive frame timing at a number of user terminals for mesh communications.
  • the distance between the satellite and the gateway changes.
  • the bursts received from the master terminal via a mesh communication path are used to adjust the start of receive frame timing at the user terminal for mesh communications from other user terminals.
  • FIG. 27 is a flowchart illustrating a method 2700 of using timing for a mesh communication path for synchronization for mesh satellite communications according to various embodiments of the invention.
  • the method 2700 may, for example, be performed within the system 100 of FIG. 1 or system 200 of FIG. 2.
  • the method 2700 may also be performed by the terminal 115 of FIG 1 or 2 or, more specifically, by the configuration 2200 illustrated in FIG. 22 or configuration 2300 illustrated in FIG. 23.
  • the gateway transmits a first set of signals to set the start of receive frame timing at a user terminal of a number of terminals for communications from the gateway.
  • the gateway transmits a second set of signals to set a start of transmit frame timing for terminals for both communications to the gateway and communications to other user terminals.
  • the terminals receive the second set of signals to set the start of transmit frame timing for the terminals for both communications to the gateway and mesh communications to other user terminals.
  • one of the number of terminals transmits, according to the transmission frame timing set with the second set of signals, a series of signals to set the start of receive frame timing at the user terminal for mesh communications from other user terminals.
  • a user terminal receives the first set of signals to set the start of receive frame timing at a user terminal for communications from the gateway.
  • the user terminal uses a first subset of the series of signals to set the start of receive frame timing at the user terminal for mesh communications.
  • the distance between the satellite and the gateway changes.
  • a user terminal uses a second subset of the series of signals received after the distance changes to set the start of receive frame timing at the user terminal for mesh communications.
  • gateway 110 or gateway frame timing module 245), user terminal 115 (or terminal frame timing module 220), or satellite 105 discussed in FIGS. 1-27 may be implemented, in whole or in part, in hardware. Thus, they may each be made up of one, or more, Application Specific Integrated Circuits (ASICs) adapted to perform a subset of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing modules (or cores), on one or more integrated circuits.
  • ASICs Application Specific Integrated Circuits
  • Integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art.
  • FPGAs Field Programmable Gate Arrays
  • Semi-Custom ICs may be programmed in any manner known in the art.
  • Each may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application specific processors.
  • the embodiments may be described as a process which is depicted as a flow diagram or block diagram. Although each may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure.
  • the term “memory” or “memory module” may represent one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices, or other computer-readable mediums for storing information.
  • ROM read-only memory
  • RAM random access memory
  • magnetic RAM magnetic RAM
  • core memory magnetic disk storage mediums
  • optical storage mediums flash memory devices
  • computer-readable mediums includes, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, a sim card, other smart cards, and various other mediums capable of storing, containing, or carrying instructions or data.
  • embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
  • the program code or code segments to perform the necessary tasks may be stored in a computer-readable medium such as a storage medium. Processors may perform the necessary tasks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Radio Relay Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

L’invention concerne des procédés, des systèmes et des dispositifs pour une synchronisation dans des communications par satellite maillées. Le temps d’arrivée du signal de passerelle peut être utilisé afin d’établir un temps de trame de début de réception pour un terminal. Un signal de commande reçu depuis la passerelle peut ensuite être utilisé afin d’établir un temps de trame de début de transmission pour le terminal utilisateur. La distance entre le satellite et la passerelle peut changer. Des données d’éphémérides, diverses collections de mesures de terminal, ou des rafales de synchronisation de terminal peuvent être utilisées en vue de modifier les paramètres de trame de début de transmission ou de trame de début de réception pour le terminal ou la passerelle.
PCT/US2009/059722 2008-10-06 2009-10-06 Synchronisation pour des communications par satellite maillées WO2010059299A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10316508P 2008-10-06 2008-10-06
US61/103,165 2008-10-06

Publications (2)

Publication Number Publication Date
WO2010059299A2 true WO2010059299A2 (fr) 2010-05-27
WO2010059299A3 WO2010059299A3 (fr) 2010-08-05

Family

ID=42075743

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/059722 WO2010059299A2 (fr) 2008-10-06 2009-10-06 Synchronisation pour des communications par satellite maillées

Country Status (2)

Country Link
US (3) US8233840B2 (fr)
WO (1) WO2010059299A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU172333U1 (ru) * 2016-07-26 2017-07-04 федеральное государственное автономное образовательное учреждение высшего образования "Самарский национальный исследовательский университет имени академика С.П. Королева" Программно-аппаратный комплекс для измерения метрик производительности IP-сетей

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8233840B2 (en) * 2008-10-06 2012-07-31 Viasat, Inc. Ephemeris-based synchronization for mesh satellite communications
US8879982B2 (en) * 2010-10-26 2014-11-04 Emc Satcom Technologies, Llc Automatic uplink power control in interference cancellation based spectral reuse
US8954000B2 (en) * 2012-11-01 2015-02-10 Hughes Network Systems, Llc Real-time signal validation method and system
CN105577309B (zh) * 2015-12-10 2017-11-24 成都国恒空间技术工程有限公司 一种卫星通信系统全网时钟同步方法
US10805001B2 (en) 2016-10-19 2020-10-13 Lockheed Martin Corporation State transfer among spaceborne and airborne devices
US10530468B2 (en) * 2016-10-19 2020-01-07 Vector Launch Inc. State transfer among virtualized nodes in spaceborne or airborne systems
US10057869B2 (en) 2016-11-17 2018-08-21 Electronics And Telecommunications Research Institute Network synchronization apparatus and method of time division multiple access (TDMA)-based mesh network satellite communication system
KR101954074B1 (ko) * 2017-06-27 2019-03-06 (주) 에이샛 Dvb-rcs 시스템에서 위성 드리프트와 이동체 간의 동기 보상 방법 및 장치
US10491710B2 (en) 2017-07-19 2019-11-26 Vector Launch Inc. Role-specialization in spaceborne and airborne computing platforms
US10749959B2 (en) 2018-02-09 2020-08-18 Lockheed Martin Corporation Distributed storage management in a spaceborne or airborne environment
US10931365B2 (en) 2018-05-11 2021-02-23 Dish Network L.L.C. Timing advance for satellite-based communications using a satellite with enhanced processing capabilities
US10624052B2 (en) * 2018-05-11 2020-04-14 Dish Network L.L.C. Timing advance for satellite-based communications
US11156705B2 (en) 2020-03-10 2021-10-26 Raytheon Company System and method for mitigating platform motion in a communications system
US11196497B2 (en) * 2020-03-11 2021-12-07 Raytheon Company System and method for mitigating platform motion in a communications system
CN113708870B (zh) * 2021-08-24 2023-03-31 四川安迪科技实业有限公司 低轨卫星tdma动中通系统的返向突发发送时间估计方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5581390A (en) * 1995-08-01 1996-12-03 Motorola, Inc. Apparatus and method for conveying frame timing, data timing, and data
US5790939A (en) * 1995-06-29 1998-08-04 Hughes Electronics Corporation Method and system of frame timing synchronization in TDMA based mobile satellite communication system
US6084864A (en) * 1993-02-09 2000-07-04 Teledesic Llc Traffic routing for satellite communication system
US20040198394A1 (en) * 2001-12-12 2004-10-07 Jari Syrjarinne Method, apparatus and system for synchronizing a cellular communication system to GPS time

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0738606B2 (ja) * 1992-10-30 1995-04-26 日本電気株式会社 衛星通信方式
GB2321831B (en) * 1994-07-22 1999-02-17 Int Mobile Satellite Org Satellite communication method and apparatus
US5850392A (en) * 1996-04-10 1998-12-15 Ericsson Inc. Spread spectrum random access systems and methods for time division multiple access radiotelephone communication systems
US5910945A (en) * 1996-04-30 1999-06-08 Trw Inc. Method and apparatus for synchronizing communications in a satellite based telecommunications system
US5923648A (en) * 1996-09-30 1999-07-13 Amsc Subsidiary Corporation Methods of dynamically switching return channel transmissions of time-division multiple-access (TDMA) communication systems between signalling burst transmissions and message transmissions
US6236359B1 (en) * 1998-05-14 2001-05-22 Nortel Networks Limited Cellular terminal location using GPS signals in the cellular band
US6278402B1 (en) * 1998-09-28 2001-08-21 Vxt, L.L.C. Hybrid system and method for golf course distance determination using GPS navigation signals
US20040198386A1 (en) * 2002-01-16 2004-10-07 Dupray Dennis J. Applications for a wireless location gateway
US7013165B2 (en) * 2000-08-16 2006-03-14 Samsung Electronics Co., Ltd. Antenna array apparatus and beamforming method using GPS signal for base station in mobile telecommunication system
JP2002071782A (ja) * 2000-08-31 2002-03-12 Hitachi Ltd 測位機能付き情報端末
US6687501B2 (en) * 2000-10-10 2004-02-03 Qualcomm Incorporated System and method of dynamically calibrating based station timing using location information
US20020089946A1 (en) * 2001-01-05 2002-07-11 Hutchings Jonathon M. System and method for providing a timing reference for data transmissions in a satellite-based communications network
US6850732B2 (en) * 2001-03-30 2005-02-01 Wengen Wireless Llc Scalable satellite data communication system that provides incremental global broadband service using earth-fixed cells
JP2003070051A (ja) * 2001-08-29 2003-03-07 Denso Corp 移動通信端末装置およびそのプログラム
US7499710B2 (en) * 2001-08-30 2009-03-03 Alcatel-Lucent Usa Inc. Integrity monitoring for geo-location systems
US6684057B2 (en) * 2001-09-14 2004-01-27 Mobile Satellite Ventures, Lp Systems and methods for terrestrial reuse of cellular satellite frequency spectrum
US7127257B2 (en) * 2001-12-27 2006-10-24 Qualcomm Incorporated Use of mobile stations for determination of base station location parameters in a wireless mobile communication system
US7499712B2 (en) * 2002-09-05 2009-03-03 Qualcomm Incorporated Position computation in a positioning system using synchronization time bias
JP2004159026A (ja) * 2002-11-06 2004-06-03 Nec Access Technica Ltd 携帯電話機及びそれに用いる測位切替方法並びにそのプログラム
US7831263B2 (en) * 2002-11-08 2010-11-09 Qualcomm Incorporated Apparatus and method for determining the location of a repeater
EP1440855A1 (fr) * 2003-01-24 2004-07-28 Komatsu Ltd. Système de libération pour un dispositif mobile
EP1441077B1 (fr) * 2003-01-24 2011-03-16 Komatsu Ltd. Dispositif de communication d'un corps mobile
US7146192B2 (en) * 2003-06-10 2006-12-05 Lucent Technologies Inc. Base station for mobile telecommunications, an antenna assembly, and a method of determining the location of an antenna assembly
WO2005027373A1 (fr) * 2003-09-08 2005-03-24 Wells Loren L Systeme et procede de commande d'acces multiple dans un systeme de communications par satellite
US7321776B2 (en) * 2003-09-25 2008-01-22 Sony Ericsson Mobile Communications Ab Estimating GPS time at cellular terminals based on timing of information from base stations and satellites
US7394780B1 (en) * 2003-11-26 2008-07-01 Idirect Incorporated Method, apparatus, and system for downstream recovery in a communication network
US7215652B1 (en) * 2003-11-26 2007-05-08 Idirect Incorporated Method, apparatus, and system for calculating and making a synchronous burst time plan in a communication network
US20050239479A1 (en) * 2004-04-22 2005-10-27 Bednasz Kenneth M Hands-free reminder for a wireless communications terminal
US7315536B2 (en) * 2004-08-09 2008-01-01 Telefonaktiebolaget Lm Ericsson (Publ) Uplink synchronization in a radio telecommunication system
JP4258471B2 (ja) * 2005-01-13 2009-04-30 セイコーエプソン株式会社 時刻誤差情報提供システム、端末装置、端末装置の制御方法、端末装置の制御プログラム、端末装置の制御プログラムを記録したコンピュータ読み取り可能な記録媒体
FR2881008B1 (fr) * 2005-01-20 2007-04-20 Thales Sa Recepteur de positionnement par satellite a integrite et continuite ameliorees
US20070236386A1 (en) * 2005-05-12 2007-10-11 Ofer Harpak Device and Method for Exchanging Information Over Terrestrial and Satellite Links
WO2006123418A1 (fr) * 2005-05-20 2006-11-23 Fujitsu Limited Dispositif de communication radio, dispositif terminal mobile, procede de communication radio
JP4787544B2 (ja) * 2005-05-30 2011-10-05 富士通株式会社 移動通信システム、同システムにおけるコンプレストモード制御方法並びに同システムにおける基地局及び移動局
US7974261B2 (en) * 2005-06-13 2011-07-05 Qualcomm Incorporated Basestation methods and apparatus for supporting timing synchronization
US7574224B2 (en) * 2005-06-13 2009-08-11 Qualcomm Incorporated Methods and apparatus for performing timing synchronization with base stations
DE602005008982D1 (de) * 2005-09-30 2008-09-25 Alcatel Lucent Vorrichtung und Verfahren zur Systemparameteranpassung für funkbasierte Kommunikationssysteme
EP1804399B1 (fr) * 2005-12-30 2014-02-12 Alcatel Lucent Procédé de synchronisation de stations de base d'un réseau de communication céllulaire terrestre
US7769375B2 (en) * 2006-02-09 2010-08-03 Eagle River Holdings Llc System and method for communication utilizing time division duplexing
CN101416556B (zh) * 2006-04-07 2011-04-06 艾利森电话股份有限公司 用于在蜂窝电信系统中随机接入的方法、用户设备和无线电基站
US20070252761A1 (en) * 2006-04-27 2007-11-01 Havish Koorapaty Method and arrangement for base station location, base station synchronization, and mobile station location
US8032073B2 (en) * 2006-05-03 2011-10-04 Stm Networks, Inc. Satellite communication with multiple active gateways
JP4989112B2 (ja) * 2006-05-31 2012-08-01 株式会社エヌ・ティ・ティ・ドコモ サーバ装置、移動端末及び測位方式選択方法
US20080025249A1 (en) * 2006-07-28 2008-01-31 Qualcomm Incorporated 1xEVDO WIRELESS INTERFACE TO ENABLE COMMUNICATIONS VIA A SATELLITE RELAY
JP4952782B2 (ja) * 2007-03-08 2012-06-13 富士通株式会社 無線通信装置及び移動無線通信制御方法及び無線局
JP2008236516A (ja) * 2007-03-22 2008-10-02 Hitachi Ltd ノード位置測定方法、ノード位置測定システム及びサーバ
US8068448B1 (en) * 2007-06-15 2011-11-29 Vt Idirect, Inc. Apparatus, system, and computer program for synchronizing communications
US20110116441A1 (en) * 2008-05-16 2011-05-19 O3B Limited Systems and methods for satellite communication
US8233840B2 (en) * 2008-10-06 2012-07-31 Viasat, Inc. Ephemeris-based synchronization for mesh satellite communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6084864A (en) * 1993-02-09 2000-07-04 Teledesic Llc Traffic routing for satellite communication system
US5790939A (en) * 1995-06-29 1998-08-04 Hughes Electronics Corporation Method and system of frame timing synchronization in TDMA based mobile satellite communication system
US5581390A (en) * 1995-08-01 1996-12-03 Motorola, Inc. Apparatus and method for conveying frame timing, data timing, and data
US20040198394A1 (en) * 2001-12-12 2004-10-07 Jari Syrjarinne Method, apparatus and system for synchronizing a cellular communication system to GPS time

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU172333U1 (ru) * 2016-07-26 2017-07-04 федеральное государственное автономное образовательное учреждение высшего образования "Самарский национальный исследовательский университет имени академика С.П. Королева" Программно-аппаратный комплекс для измерения метрик производительности IP-сетей

Also Published As

Publication number Publication date
US20100085909A1 (en) 2010-04-08
WO2010059299A3 (fr) 2010-08-05
US8233840B2 (en) 2012-07-31
US8675635B2 (en) 2014-03-18
US20100087141A1 (en) 2010-04-08
US20100085908A1 (en) 2010-04-08
US8675634B2 (en) 2014-03-18

Similar Documents

Publication Publication Date Title
US8233840B2 (en) Ephemeris-based synchronization for mesh satellite communications
CN107197517B (zh) 基于ta分组的lte卫星上行链路同步方法
US10361772B2 (en) Timing synchronization for a beam hopping satellite
US9077468B2 (en) Methods and apparatus for communication synchronization
CN106899371B (zh) 时间同步方法和装置
WO2021058186A1 (fr) Équipement utilisateur et station de base impliqués dans un transfert intercellulaire
EP3371902B1 (fr) Technique d'alignement d'une référence de synchronisation de trames d'interface radio dans un groupe de dispositifs de commande d'équipement radio
WO2016165353A1 (fr) Procédé et dispositif de réglage d'heure
US8086249B1 (en) Ranging of wireless communication networks with distant wireless links
JP2003298630A (ja) 時刻同期方法
WO2023124403A1 (fr) Procédé, appareil et système de synchronisation d'horloge
US7035669B2 (en) Mobile communications system, radio base station control system, and radio base station control method
CN114158128B (zh) 同步轨道卫星隐蔽通信的非对称动态时隙通信方法和装置
WO2021028739A1 (fr) Ajustement de synchronisation de liaison descendante de nœud de raccordement d'accès intégré en présence d'un décalage de fréquence
US20020089946A1 (en) System and method for providing a timing reference for data transmissions in a satellite-based communications network
JP5477743B2 (ja) 通信装置及び通信方法
KR20090059471A (ko) 시간 동기를 위한 이동통신 시스템
US20240179654A1 (en) Methods, terminal, base station, circuitry and system for a non-terrestrial network
KR101029099B1 (ko) 위성 통신 시스템의 상하향 시간 동기 획득 방법 및 이를 이용한 위성 통신 시스템
US20240137878A1 (en) Adjusted UE TX Power Ramping for Initial Access for Support of NR Over NTN
WO2023035276A1 (fr) Procédé et appareil de transmission en liaison montante, dispositif et support de stockage
US20230224112A1 (en) Terminal, base station, and communication method
JP2011114616A (ja) 同期システム、同期情報供給装置、同期装置、および同期方法
CN115942449A (zh) 通过改进标识响应信号的目标来减少争用
CN117063546A (zh) 传输定时的调整方法、确定方法和终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09827933

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09827933

Country of ref document: EP

Kind code of ref document: A2