WO1998057447A1

WO1998057447A1 - Multi-tier satellite system and method of operation

Info

Publication number: WO1998057447A1
Application number: PCT/US1998/010830
Authority: WO
Inventors: William Frank Zancho; Michael William Krutz; Gregory Barton Vatt
Original assignee: Motorola Inc.
Priority date: 1997-06-12
Filing date: 1998-05-28
Publication date: 1998-12-17
Also published as: TW372383B; FR2764755B1; US6208625B1; IT1299506B1; FR2764755A1; DE19882462T1; GB9929342D0; ITRM980375A1; JP4423410B2; AU7698898A; GB2344970A; ITRM980375A0; JP2002507345A

Abstract

A system for increasing call-handling capacity employs a multi-tier satellite network which includes one or more geosynchronous (GEO) satellites (12) and non-geosynchronous satellites (14). The GEO satellites (12) transfer non delay-sensitive data through the system, while the non-geosynchronous satellites (14) predominantly transfer delay-sensitive data through the system. In a preferred embodiment, a non-geosynchronous satellite (14) receives (102) a data packet, determines (112) whether or not the data packet is delay-sensitive, routes (114) a delay-sensitive data packet through the LEO network, and routes (116) a non delay-sensitive data packet to a GEO satellite (12).

Description

MULTI-TIER SATELLITE SYSTEM AND METHOD OF OPERATION

Field of the Invention

This invention relates generally to satellite communications and, more particularly, to routing delay- sensitive and non delay-sensitive data through satellites.

Background of the Invention

Prior-art satellite communications networks use either low-earth orbit (LEO), medium-earth orbit (MEO), or geosynchronous orbit (GEO) satellites to transfer data from a data source to a destination. Such data can include, for example, delay-sensitive data such as voice data communicated during a phone conversation. Voice data is particularly delay-sensitive because long, delay-imposed pauses during oral communications can make communication quality poor. Data requiring transfer through a network also can include non delay-sensitive data such as, for example, system overhead data including: call setup information; TT&C data (telemetry, tracking, and control); routing information; billing information; and short messages (e.g., pages).

LEO satellites are better suited than GEO satellites for communication of delay-sensitive data. Because GEO satellites are located at a substantially greater distance than LEO satellites from the earth-based equipment with which they communicate, significantly longer signal propagation delays are inherent in communications between GEO satellites and earth- based equipment. Because of the delay issues associated with GEO satellites, many prior-art satellite communication networks designed for voice communications use LEO satellites to communicate delay-sensitive data traffic.

The call-handling capacity of a LEO satellite network is inversely proportional to the amount of system overhead data which must be routed through the network. Because system overhead data is routed through the LEO satellites in prior-art systems, the satellites cannot provide as many traffic channels as they would be able to in the absence of such system overhead data.

Because high-capacity systems are highly desirable, what is needed is a method and apparatus which increases the traffic carrying capacity of a satellite network by reducing the effect of transferring system overhead data throughout a system.

Brief Description of the Drawings

FIG. 1 illustrates a satellite communication system which includes GEO and non-GEO satellites in accordance with a preferred embodiment of the present invention; FIG. 2 illustrates a flowchart of a method for routing data through the system in accordance with a preferred embodiment of the present invention;

FIG. 3 illustrates a flowchart of a method for performing location registration of a communication unit in accordance with a preferred embodiment of the present invention;

FIG. 4 illustrates a flowchart of a method for setting up a call between a source device and a destination device in accordance with a preferred embodiment of the present invention;

FIG. 5 illustrates a simplified block diagram of a non-GEO satellite in accordance with a preferred embodiment of the present invention; and

FIG. 6 illustrates a simplified block diagram of a GEO satellite in accordance with a preferred embodiment of the present invention.

Detailed Description of the Drawings

The method and apparatus of the present invention increases the traffic carrying capacity of a satellite network while providing the ability to communicate system overhead data throughout a system. This is achieved using a multi-tier satellite system, where a "satellite tier" includes a group of one or more satellites. In a preferred embodiment, two satellite tiers are used, a first tier including non-GEO satellites and a second tier including GEO satellites. The non-GEO satellites receive and route delay-sensitive data through the non-GEO network. In addition, the non-GEO satellites receive non delay- sensitive data which the non-GEO satellites route to a GEO satellite. Thus, some or all of the non delay-sensitive data is not routed through the non-GEO network, which effectively increases the system capacity by enabling more of the non-GEO communication resources to be used for communication of delay- sensitive data (e.g., voice data).

The method and apparatus of the present invention could be used, for example, as a backbone network for terrestrial networks (e.g., terrestrial cellular and PCS wireless systems). Such terrestrial networks could set up their global call delivery and routing through the non-real time satellite tier (e.g., GEO satellites) and route the real-time traffic (e.g., voice) through the real-time satellite tier (e.g., non-GEO satellites). FIG. 1 illustrates a satellite communication system which includes GEO and non-GEO satellites in accordance with a preferred embodiment of the present invention. System 10 includes one or more GEO satellites 12 and one or more non-GEO satellites 14. In a preferred embodiment, non-GEO satellites 14 are LEO satellites. LEO satellites 14 communicate with equipment 20, 22, 24 located at, below, or above the surface of the earth. For example, LEO satellites 14 communicate over link 30 with a fixed or mobile communication unit 20 which can be a portable, hand-held telephone, pager, or data device. Communication unit 20 could be located anywhere on or above the surface of the earth. In some applications, communication unit 20 also could be located underwater or underground. In addition, communication unit 20 could interface with a LEO satellite 14 through a single communication channel, or could be a communication unit that interfaces with a LEO satellite 14 using multiple communication channels. LEO satellites 14 communicate over link 32 with gateway (GW) 22 which functions to interface system 10 with other communication systems 26 (e.g., public switched telephone networks or terrestrial cellular systems). In a preferred embodiment, gateway 22 also assists in performing functions such as call setup, billing, and other user services. LEO satellites 14 also communicate over link 34 with system control facility (SCF) 24. System control facility 24 could be incorporated into a gateway 22 or could exist as a stand-alone facility. System control facility 24 desirably receives telemetry information from satellites 14 and performs system control functions necessary for the operation of system 10.

In a preferred embodiment, GEO satellites 12 and LEO satellites 14 also communicate between each other over LEO crosslinks 40, LEO-GEO links 42, and GEO crosslinks 44. LEO crosslinks 40 between LEO satellites 14 are used, in a preferred embodiment, to carry delay-sensitive data such as user voice information created during a call. When a LEO satellite 14 receives such information from equipment 20 or 22, for example, LEO satellite 14 would, when appropriate, either route the delay- sensitive data back to equipment on the ground or would route the delay-sensitive data over a LEO crosslink 40. In an alternate embodiment, LEO satellites 14 could transfer data between themselves using bent-pipe links through ground equipment, rather than by using links 40.

LEO-GEO links 42 exist between LEO satellites 14 and GEO satellites 12. In a preferred embodiment, links 42 would carry non delay-sensitive data. When LEO satellites 14 receive such non delay-sensitive data, LEO satellites 14 would, when appropriate, either route the non delay-sensitive data back to equipment on the ground or would route that data over links 42 to GEO satellites 12, rather than routing the data over LEO crosslinks 40. Except for that non delay-sensitive data which is destined for ground equipment with which a LEO satellite 14 can directly communicate, the LEO satellite 14 routes some or, preferably, all non delay-sensitive data through GEO satellites 12.

Prior-art systems route all data, regardless of its type, through LEO crosslinks, thus reducing the available capacity for delay-sensitive data to be routed through LEO crosslinks. By reducing or eliminating the quantity of non delay-sensitive data sent through LEO crosslinks, the method and apparatus of the present invention allows most or all of the LEO crosslink capacity to be used for delay-sensitive data, thus effectively increasing the system capacity by a substantial amount.

In an alternate embodiment, non delay-sensitive data could be sent directly from equipment 20, 22, 24 to GEO satellites 12, rather than being routed through LEO satellites 14. In such an embodiment, equipment 20, 22, 24 would be required to have transmission power levels and equipment sufficient to communicate with GEO satellites 12. Such equipment could be more expensive than equipment necessary to communicate with LEO satellites 12, making direct communication with GEO satellites 12 less desirable. In a preferred embodiment, links 44 exist between GEO satellites 12, although links 44 are not essential to achieve the advantages of the present invention. Links 44 are convenient where non delay-sensitive data received by a first GEO satellite 12 from a first LEO satellite 14 should be routed through a second LEO satellite 14 which does not communicate directly with the first GEO satellite 12, but does communicate directly with a second GEO satellite 12. Such data could be routed from the first LEO satellite 14, to the first GEO satellite 12, over link 44 to the second GEO satellite 12, and to the second LEO satellite 14. In an alternate embodiment, GEO satellites 12 could transfer data between themselves using bent-pipe links through LEO satellites 14 or ground-based equipment, rather than using links 44. In another alternate embodiment, MEO satellites could be used in the system rather than, or in addition to, the LEO satellites or GEO satellites. For illustration purposes only, FIG. 1 shows two GEO satellites 12, nine LEO satellites 14, one communication unit 20, one gateway 22, and one system control facility 24. A system incorporating the method and apparatus of the present invention could have one or any number of GEO satellites 12, LEO satellites 14, gateways 22, and system control facilities 24. In addition, such a system could support numerous communication units 20 of various types and degrees of mobility.

FIG. 2 illustrates a flowchart of a method for routing data through the system in accordance with a preferred embodiment of the present invention. The method begins, in step 102, when a first LEO satellite receives a data packet. The data packet could originate from another LEO satellite, a GEO satellite, a communication unit, a gateway, or a control facility, for example. In step 104, the LEO satellite determines the destination of the data packet, for example, by evaluating the packet's header information. A determination is made, in step 106, whether the first LEO satellite is the destination of the data packet. If so, the first LEO satellite consumes or stores the information and the procedure ends. If not, a determination is made, in step 108, whether a ground-based device (e.g., a communication unit, gateway, or control facility) that currently is or is capable of being linked to the LEO satellite is the destination. If so, the LEO satellite sends the data packet to the linked ground device in step 110 and the procedure ends.

If a linked ground device is not the destination, then a determination is made whether the data packet includes delay- sensitive data in step 112. This determination could be made, for example, by examining a bit in the packet header which indicates whether or not the data is delay-sensitive. Alternatively, the data packet header could include a field which indicates the type of packet. For example, if the type field indicates that the packet includes voice data, the packet could be deemed to include delay- sensitive data. The source or destination of the data packet also might be used to make the determination. If the packet is destined for a control facility, for example, it could be deemed to be non delay-sensitive. Any number of criteria could be used to determine whether or not a packet is delay-sensitive.

If the data packet does include delay-sensitive data, the data packet is routed, in step 114, through the LEO network (e.g., over a LEO crosslink) to the packet's ultimate destination. When a LEO satellite is a destination of the packet, the packet would be routed over LEO crosslinks to the destination LEO. In an alternate embodiment, the packet could be routed over bent-pipe links through ground transceivers. When ground-based equipment is the destination, the packet would be routed over LEO crosslinks to a LEO satellite which is capable of communicating with the destination equipment. That LEO satellite would then route the packet to the equipment. The procedure then ends.

If step 112 determines that the data packet does not include delay-sensitive data, the data packet is routed, in step 116, to the GEO network (e.g., over a LEO-GEO link). The GEO network then routes the data packet to its ultimate destination. If a GEO satellite is the ultimate destination, the packet would be routed over GEO crosslinks, if possible, to the destination GEO. In alternate embodiments, the packed could be routed along bent- pipe links through ground transceivers or other satellites. If a LEO satellite (or a ground device serviced by a particular LEO satellite) is the ultimate destination, the data packet is routed through the GEO network to the GEO satellite that is capable of communicating with the destination LEO satellite. That GEO satellite would then route the packet to the LEO satellite (which in turn would route the packet to the destination device, if necessary). The procedure then ends.

Although a preferred embodiment routes packetized data (e.g., voice, data, and/or control-routing information), the method and apparatus of the present invention also could be used to support circuit-switched routing as well.

FIG. 3 illustrates a flowchart of a method for performing location registration of a communication unit in accordance with a preferred embodiment of the present invention. Location registration requires messages to be passed between a communication unit and a registration facility (e.g., a gateway) via a satellite network. The registration facility stores registration information for the communication unit. For purposes of illustration, this location registration example assumes that the registration facility is not in communication contact with the same LEO satellite which that communication unit is currently communicating with. In other words, the registration facility is located some distance from the communication unit, making it necessary to route the registration information from the communication unit to the registration facility through more than one LEO satellite.

Location registration, for example, illustrates one area where non delay-sensitive data is to be routed through a system. Thus, in accordance with the present invention, the location registration data can be routed through the GEO network, rather than routing it exclusively through the LEO network. Prior-art systems would route the data through the LEO network, thus consuming valuable bandwidth resources which could be better utilized for delay-sensitive data. The method begins, in step 302, when a communication unit initiates a location registration procedure. A location registration procedure can be initiated upon power up, at periodic intervals, or when the communication unit has moved a certain re-registration distance, for example. In step 304, the communication unit sends registration information to a LEO satellite with which the communication unit can communicate. Registration information, for example, could include a communication unit identification number and location information obtained through a geolocation process or from a Global Positioning System (GPS) receiver. Alternatively, location information could simply describe a cell or a geographic area within which the communication unit is located.

After receiving the registration information, the LEO satellite sends the registration information to the GEO network in step 306. The LEO satellite knows to send the registration information to a GEO satellite (rather than to a LEO) based on the LEO satellite's determination that the data packet is not delay- sensitive.

In step 308, the GEO satellite network routes the registration information to the registration facility. Where the registration facility is ground based, the GEO network would route the information to the ground-based facility either directly, or through another LEO satellite which is capable of communicating with the registration facility. In an alternate embodiment, the registration facility could be satellite-based, whereupon the GEO network would route the information to an appropriate GEO or LEO satellite. The procedure then ends.

FIG. 4 illustrates a flowchart of a method for setting up a call between a source device and a destination device in accordance with a preferred embodiment of the present invention. The described method will illustrate the routing of both delay- sensitive and non delay-sensitive data through the system in accordance with a preferred embodiment of the present invention. The description of the method assumes that the call setup information is non delay-sensitive, but that the call ultimately will consist of the exchange of delay-sensitive data (e.g., voice data).

The method begins in step 402, when a gateway receives an incoming call request from a source communication unit. The call request can be received directly from the communication unit, or via a satellite. The gateway determines with which other gateway it must communicate in order to exchange call setup information. Assuming the other gateway is located a substantial distance from the first gateway, in step 404, the first gateway initiates the exchange of call setup data with the other gateway through the GEO network. In a preferred embodiment, the data is routed from the first gateway, through a LEO satellite, through the GEO network, through another LEO satellite, and down to the other gateway. In an alternate embodiment, one or both gateways could communicate directly with the GEO network and the LEO satellites could be bypassed. A determination is made, in step 406, whether call setup is complete. If not, the procedure iterates as shown in FIG. 4. If so, then the exchange of delay-sensitive call data begins through the LEO satellite network in step 408. During the call, in a preferred embodiment, all delay-sensitive data will be exchanged through the LEO network, and all non delay-sensitive data will be exchanged through the GEO network.

FIG. 5 illustrates a simplified block diagram of a non-GEO satellite in accordance with a preferred embodiment of the present invention. Non-GEO satellite 500 includes processor 502, uplink transceiver 506, downlink transceiver 504, and crosslink transceivers 508-512. Uplink transceiver 506 supports a LEO- GEO link, downlink transceiver 504 supports a downlink to a ground device (e.g., a communication unit, gateway, or control facility), and crosslink transceivers 508-512 support LEO crosslinks with other LEO satellites.

Non-GEO satellite 500 can receive a data packet via any one of transceivers 504-512. After receipt of a data packet, processor 502 determines the data packet destination and determines how to route the packet. The routing decision depends on the data packet type. Unless non-GEO satellite 500 or a linked ground device is the packet destination, non delay-sensitive data packets are routed through a GEO network via uplink transceiver 506. Delay-sensitive data packets are routed through the non- GEO network via one of crosslink transceivers 508-512.

Although FIG. 5 illustrates one downlink transceiver 504, one uplink transceiver 506, and three crosslink transceivers 508- 512, any number of each type of transceiver could be used, depending on the number of downlinks, uplinks, and crosslinks, respectively, which are to be provided.

FIG. 6 illustrates a simplified block diagram of a GEO satellite in accordance with a preferred embodiment of the present invention. GEO satellite 600 includes processor 602, downlink transceivers 604-608, and crosslink transceivers 610- 612. Downlink transceivers 604-608 support LEO-GEO links and crosslink transceivers 610-612 support crosslinks with other GEO satellites (if any).

GEO satellite 600 can receive a data packets via any one of transceivers 604-612. After receipt of a data packet, processor 602 determines the data packet destination and determines how to route the packet. Unless GEO satellite 600 is the packet destination, the data packet is routed either through the GEO network via one of crosslink transceivers 610-612 or is routed to an appropriate LEO satellite in the LEO network via one of downlink transceivers 604-608. In an alternate embodiment, downlink transceivers 604-608 could support links directly to ground devices.

Although FIG. 6 illustrates three downlink transceivers 604-608 and two crosslink transceivers 610-612, any number of each type of transceiver could be used, depending on the number of downlinks and crosslinks, respectively, which are to be provided.

In summary, the method and apparatus of the present invention enable the call-handling capacity of a communication system to be increased by routing non delay-sensitive data through a first satellite tier of the system (e.g., one or more GEO satellites) while routing delay-sensitive data through a second satellite tier of the system (e.g., LEO satellites). While the principles of the invention have been described above in connection with specific apparatus, it is to be clearly understood that this description is made only by way of example and not as a limitation on the scope of the invention.

For example, although the description describes a system using both LEO and GEO satellites, MEO satellites or satellites in other orbits could also or alternatively be used. Any combination of satellites in different orbits could make up the multi-tier network. For example, the multi-tier network could include LEO and MEO satellite tiers, or MEO and GEO satellite tiers, or two LEO satellite tiers where some LEO satellites are predominantly for carrying delay-sensitive data, and some LEO satellites are predominantly for carrying non delay-sensitive data. In other embodiments, instead of routing non delay-sensitive data through the LEO network to the GEO network, ground equipment which has the appropriate capabilities could send and receive non delay- sensitive data directly to and from the GEO satellites. These and other changes and modifications which are obvious to those skilled in the art are intended to be included within the scope of the present invention.

Claims

CLAIMSWhat is claimed is:

1 . A satellite communication system for communicating delay-sensitive data and non delay-sensitive data, the satellite communication system comprising: at least one geosynchronous satellite capable of interfacing with non-geosynchronous satellites in order to send and receive the non delay-sensitive data; and said non-geosynchronous satellites capable of communicating with the at least one geosynchronous satellite, wherein a non-geosynchronous satellite routes the non delay-sensitive data to the at least one geosynchronous satellite and the non-geosynchronous satellite receives delay-sensitive data from a device and routes the delay-sensitive data through at least one other of the non-geosynchronous satellites but not through the at least one geosynchronous satellite.

2. A satellite communication system for communicating delay-sensitive data and non delay-sensitive data, the satellite communication system comprising: a first satellite tier having at least one first-tier satellite capable of communicating with the at least one second- tier satellite, wherein a first-tier satellite routes non delay-sensitive data to the at least one second-tier satellite and the first-tier satellite receives delay- sensitive data from a device and routes the delay- sensitive data through at least one other first-tier satellite but not through the at least one second-tier satellite; and a second satellite tier having said at least one second-tier satellite for sending and receiving the non delay- sensitive data.

3. A first-tier satellite of a communication system, the first- tier satellite comprising: a receiver capable of receiving a data packet; a processor, coupled to the receiver, capable of evaluating routing information contained within the data packet, wherein when the data packet is a non delay-sensitive data packet, the routing information indicates that the data packet is to be routed to a second-tier satellite of the communication system, wherein the second-tier satellite is dedicated to routing non delay-sensitive data packets; and a transmitter, coupled to the processor, for routing the data packet to the second-tier satellite when the routing information so indicates.

4. A satellite of a communication system, the satellite comprising: a receiver capable of receiving a data packet from a first- tier satellite, wherein the data packet is a non delay- sensitive data packet and the satellite is a second-tier satellite dedicated to routing non delay-sensitive data packets; and a processor, coupled to the receiver, capable of identifying a destination of the non delay-sensitive data packet, and processing the non delay-sensitive data packet according to the destination.

5. A method for routing data through a satellite communication system, the method comprising the steps of: receiving a data packet by a first-tier satellite of the satellite communication system; determining, by the first-tier satellite, whether the data packet is a delay-sensitive data packet or a non delay- sensitive data packet; when the data packet is a delay-sensitive data packet, routing the data packet to another first-tier satellite which is capable of delivering the data packet to a destination device of the data packet; and when the data packet is a non delay-sensitive data packet, routing the data packet to a second-tier satellite of the satellite communication system.

6. A method for routing data through a satellite communication system, the method comprising the steps of: sending, by a communication device, a delay-sensitive data packet to a first satellite located in a first tier of the satellite communication system; and sending, by the communication device, a non delay-sensitive data packet to a second satellite located in a second tier of the satellite communication system, wherein the second satellite is dedicated to routing non delay- sensitive data packets but not to routing delay- sensitive data packets.

7. The method as claimed in claim 6, wherein the step of sending the non delay-sensitive data packet comprises a step of sending the non delay-sensitive data packet to the second satellite through a satellite located in the first tier.

8. A method for routing data through a satellite communication system, the method comprising the steps of: receiving a data packet by a first-tier satellite of the satellite communication system; evaluating, by the first-tier satellite, routing information contained within the data packet, wherein when the data packet is a non delay-sensitive data packet, the routing information indicates that the data packet is to be routed to a second-tier satellite; and routing the data packet to the second-tier satellite when the routing information so indicates.

9. A method for routing data through a satellite communication system including a first satellite tier, the method comprising the steps of: receiving a data packet by a second-tier satellite from a first-tier satellite of the satellite communication system, wherein the data packet is a non delay- sensitive data packet which was sent to the second-tier satellite after the first-tier satellite determined that the data packet was the non-delay data packet; determining a destination of the non delay-sensitive data packet; and processing the non delay-sensitive data packet according to the destination.

10. The method as claimed in claim 9, wherein the processing step comprises the steps of: determining whether the destination is another second-tier satellite; when the destination is another second-tier satellite, routing the non delay-sensitive data packet toward the another second-tier satellite; when the destination is not another second-tier satellite, determining whether the second-tier satellite is in communication range of a destination first-tier satellite which is the destination or is capable of communicating with the destination; when the second-tier satellite is in the communication range, sending the non delay-sensitive data packet to the destination first-tier satellite; and when the second-tier satellite is not in the communication range, routing the non delay-sensitive data packet toward a different second-tier satellite which is in communication range of the destination first-tier satellite .