This invention relates to wireless communications systems and methods and more particularly to satellite and terrestrial wireless communications systems and methods.
A satellite radioterminal communications system may use a single satellite antenna pattern (beam or cell) that provides a single communications service region for satellite radioterminals that are served by the system. Alternatively or in combination with the above, in cellular satellite radioterminal communications systems, multiple satellite antenna patterns (beams or cells) are provided, each of which can serve a substantially distinct service region in an overall service region, to collectively provide service to the overall communication service region. Thus, a cellular architecture that is similar to that used in conventional terrestrial cellular radioterminal systems can be implemented in cellular satellite-based systems and methods. The satellite typically communicates with radioterminals over a bidirectional communications pathway, with radioterminal communications signals being communicated from the satellite to the radioterminal over a downlink or forward link (also referred to as forward service link), and from the radioterminal to the satellite over an uplink or return link (also referred to as return service link). In some cases, such as, for example, in broadcasting, the satellite may communicate information to one or more radioterminals unidirectionally. The overall design and operation of cellular satellite radioterminal systems and methods are well known to those having skill in the art, and need not be described further herein.
Terrestrial networks can enhance cellular satellite radioterminal system availability, efficiency and/or economic viability by terrestrially reusing at least some of the frequency bands that are allocated to cellular satellite radioterminal systems. In particular, it is known that it may be difficult for cellular satellite radioterminal systems to reliably serve densely populated areas, because the satellite signal may be blocked by high-rise structures and/or may not penetrate into buildings. As a result, the satellite spectrum may be underutilized or unutilized in such areas. The terrestrial reuse of at least some of the satellite system frequencies can reduce or eliminate this potential problem.
Moreover, the capacity of a hybrid system, comprising terrestrial and satellite-based connectivity and configured to terrestrially reuse at least some of the satellite-band frequencies, may be higher than a corresponding satellite-only system since terrestrial frequency reuse may be much denser than that of the satellite-only system. In fact, capacity may be enhanced where it may be mostly needed, i.e., in densely populated urban/industrial/commercial areas where the connectivity/signal(s) of a satellite-only system may be unreliable. As a result, a hybrid (satellite/terrestrial cellular) system that is configured to reuse terrestrially at least some of the frequencies of the satellite band may become more economically viable, as it may be able to serve more effectively and reliably a larger subscriber base.
One example of terrestrial reuse of satellite frequencies is described in U.S. Pat. No. 5,937,332 to Karabinis entitled Satellite Telecommunications Repeaters and Retransmission Methods, the disclosure of which is hereby incorporated herein by reference in its entirety as if set forth fully herein. As described therein, satellite telecommunications repeaters are provided which receive, amplify, and locally retransmit the downlink/uplink signal received from a satellite/radioterminal thereby increasing an effective downlink/uplink margin in the vicinity of the satellite telecommunications repeater and allowing an increase in the penetration of uplink and downlink signals into buildings, foliage, transportation vehicles, and other objects which can reduce link margin. Both portable and non-portable repeaters are provided. See the abstract of U.S. Pat. No. 5,937,332.
Satellite radioterminal communications systems and methods that may employ terrestrial use and/or reuse of satellite frequencies by an Ancillary Terrestrial Network (ATN) comprising at least one Ancillary Terrestrial Component (ATC) are also described in U.S. Pat. Nos. 6,684,057 to Karabinis, entitled Systems and Methods for Terrestrial Reuse of Cellular Satellite Frequency Spectrum; 6,785,543 to Karabinis, entitled Filters for Combined Radiotelephone/GPS Terminals; 6,856,787 to Karabinis, entitled Wireless Communications Systems and Methods Using Satellite-Linked Remote Terminal Interface Subsystems; 6,859,652 to Karabinis et al., entitled Integrated or Autonomous System and Method of Satellite-Terrestrial Frequency Reuse Using Signal Attenuation and/or Blockage, Dynamic Assignment of Frequencies and/or Hysteresis; and 6,879,829 to Dutta et al., entitled Systems and Methods for Handover Between Space Based and Terrestrial Radioterminal Communications, and For Monitoring Terrestrially Reused Satellite Frequencies At a Radioterminal to Reduce Potential Interference, and in U.S. Pat. Nos. 6,892,068, 6,937,857, 6,999,720 and 7,006,789; and Published U.S. Patent Application Nos. US 2003/0054761 to Karabinis, entitled Spatial Guardbands for Terrestrial Reuse of Satellite Frequencies; US 2003/0054814 to Karabinis et al., entitled Systems and Methods for Monitoring Terrestrially Reused Satellite Frequencies to Reduce Potential Interference; US 2003/0073436 to Karabinis et al., entitled Additional Systems and Methods for Monitoring Terrestrially Reused Satellite Frequencies to Reduce Potential Interference; US 2003/0054762 to Karabinis, entitled Multi-Band/Multi-Mode Satellite Radiotelephone Communications Systems and Methods; US 2002/0041575 to Karabinis et al., entitled Coordinated Satellite-Terrestrial Frequency Reuse; US 2003/0068978 to Karabinis et al., entitled Space-Based Network Architectures for Satellite Radiotelephone Systems; US 2003/0153308 to Karabinis, entitled Staggered Sectorization for Terrestrial Reuse of Satellite Frequencies; and US 2003/0054815 to Karabinis, entitled Methods and Systems for Modifying Satellite Antenna Cell Patterns In Response to Terrestrial Reuse of Satellite Frequencies, and in Published U.S. Patent Application Nos. 2004/0121727, 2004/0142660, 2004/0192395, 2004/0192200, 2004/0192293, 2004/0203742, 2004/0240525, 2005/0026606, 2005/0037749, 2005/0041619, 2005/0064813, 2005/0079816, 2005/0090256, 2005/0118948, 2005/0136836, 2005/0164700, 2005/0164701, 2005/0170834, 2005/0181786, 2005/0201449, 2005/0208890, 2005/0221757, 2005/0227618, 2005/0239457, 2005/0239403, 2005/0239404, 2005/0239399, 2005/0245192, 2005/0260984, 2005/0260947, 2005/0265273, 2005/00272369, 2005/0282542, 2005/0288011, 2006/0040613, 2006/040657 and 2006/0040659; all of which are assigned to the assignee of the present invention, the disclosures of all of which are hereby incorporated herein by reference in their entirety as if set forth fully herein. Various techniques for coordination of operations of satellite and terrestrial components are described in U.S. Patent Application Publication No. 2005/0090256 to Dutta, entitled Systems and Methods for Mobility Management in Overlaid Mobile Communications Systems, and U.S. patent application Ser. No. 11/548,825 to Tronc et al. entitled Systems, Methods and Computer Program Products for Mobility Management in Hybrid Satellite/Terrestrial Wireless Communications Systems, filed Oct. 12, 2006, both of which are assigned to the assignee of the present invention, the disclosures of both of which are hereby incorporated herein by reference in their entirety as if set forth fully herein.
Some embodiments of the present invention provide wireless communications methods. Communications between a terminal and a satellite base station are established through a satellite. A traffic channel is assigned for use by the terminal to transmit data traffic to the satellite for relay to the satellite base station. The traffic channel assignment is retained for use by the terminal while the terminal is idle between data traffic transmissions to the satellite in response to a Type of Service (ToS) designation that is associated with, the terminal.
Because the traffic channel can be pre-assigned to the terminal before it has data traffic that is ready for transmission and the traffic channel can be retained for use by the terminal while the terminal is idle, the terminal may more quickly transition from being idle to transmitting data traffic. The pre-assignment and retention of traffic channels to terminals may be regulated in response to a TOS designation that is associated with the terminals. The TOS designation may, for example, identify which terminals are to be provided reduced latency communication for PTT protocol service, VOIP service, and/or another service. The TOS designations for individual terminals may be controlled by service providers as a way of offering a premium service to subscribers. The number of traffic channels within a spot beam that are pre-assigned and retained for use by registered terminals can be controlled so that a defined number of other traffic channels are available for assignment to terminals responsive to traffic channel requests therefrom.
Some other embodiments of the present invention provide a wireless communication system that includes a satellite base station. The satellite base station is configured to assign a traffic channel for use by a terminal to transmit data traffic to a satellite for relay to the satellite base station, and to retain the traffic channel assignment for use by the terminal while the terminal is idle between data traffic transmissions to the satellite in response to a type of service designation that is associated with the terminal.
Some other embodiments of the present invention provide a wireless communication system that includes a terminal that is configured to receive from a satellite base station a traffic channel assignment for use by the terminal to transmit data traffic to a satellite for relay to the satellite base station and a command that indicates whether traffic channel assignment is to be retained while idle. The terminal is further configured to retain the traffic channel assignment for use by the terminal while the terminal is idle between data traffic transmissions to the satellite in response to the command indicating that the assignment is to be retained while idle.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate certain embodiments of the invention.
Specific exemplary embodiments of the invention now will be described with reference to the accompanying drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. It will be understood that when an element is referred to as being “connected”, “coupled” or “responsive” to another element, it can be directly connected, coupled or responsive to the other element or intervening elements may be present. Furthermore, “connected”, “coupled” or “responsive” as used herein may include wirelessly connected, coupled or responsive.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “comprises,” “including” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
It will be understood that although the terms first and second are used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. Thus, a first element below could be termed a second element, and similarly, a second element may be termed a first element without departing from the teachings of the present invention. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. The symbol “/” is also used as a shorthand notation for “and/or”.
In some alternate implementations, the operations/methods identified in the message flow diagrams may occur out of the identified order. For example, two operations/methods shown in succession may in fact be carried out substantially concurrently or the operations/methods may sometimes be carried out in the reverse order, depending upon the operations/methods involved. Moreover, the functionality of a particular illustrated operation/method may be separated into multiple discrete operations/methods and/or the functionality of two or more discrete operations/methods may be at least partially integrated. Although some of the diagrams include arrows on communication paths to show what may be a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
As used herein, the term “radioterminal” includes any type of user device/equipment that can communicate through radio frequency signaling with a space-based communications network (SBN). A radioterminal may be further configured to terrestrially use/reuse at least some of the frequency bands that are allocated to the SBN for communication with an ancillary terrestrial communications network (ATN), and such a radioterminal can be referred to as an “ancillary terminal (AT)”. A radioterminal may have time-varying or fixed geographic coordinates, and may be portable, transportable, installed in a vehicle (aeronautical, maritime, or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. A “radioterminal” also may be referred to herein as a “terminal,” “wireless terminal,” “subscriber station,” “radiotelephone,” or “wireless user device”.
Furthermore, as used herein, the term “SBN” includes one or more satellites at any orbit (geostationary, substantially geostationary, medium earth orbit, low earth orbit, etc.) and may further include terrestrial components, such as a satellite base station, a serving gateway, and/or network infrastructure. The term “ATN” may include one or more “ancillary terrestrial components (ATCs)”, which may each include a plurality of geographically distributed base stations (e.g., in cellular arrangements), which may be ground installations, vehicle-borne installations, airborne installations and/or ship-borne installations. Some embodiments of the present invention are described in the context of an SBN that is overlaid on an ATN, although the invention is not limited thereto as it may be embodied in any type of SBN.
Various embodiments of the present invention are directed to reducing communication latency for terminals that communicate with a SBN.
Referring to the exemplary embodiment of
The ATN 110 can include one or more base stations (BS) 114 that communicate through associated antennas 116 with the terminals 10 that are located within their respective coverage areas 118. Each BS 114 communicatively connects serviced terminals 10 to ground-based network infrastructure, such as a HSGW 112.
Because communications between a terminal 10 and a BS 114 occur over relatively short distances (e.g., typically less than 50 miles), there is a relatively small communication latency therebetween. In contrast, communications between a terminal 10 and the SBS 124 are relayed through the orbiting satellite 126 and, therefore, occur over significant distances. Consequently, a single round-trip communication between a terminal 10 and the SBS 124 may add up to 700 ms or more latency to any request and response communication sequence therebetween. Such communication latency may be particularly undesirable when carrying out some communication protocols, such as for Push-To-Talk (PTT) voice data communications and Voice Over Internet Protocol (VOIP) communications.
In accordance with some embodiments, when a terminal 10 registers with the network infrastructure, the SBS 124 proceeds with pre-assigning a traffic channel to the terminal 10 without waiting for the terminal 10 to necessarily have data traffic that is ready to be transmitted. The assigned traffic channel is to be used by the terminal 10 to transmit data traffic, if and when data traffic is ready for transmission, through the satellite 126 to the SBS 124. The SBS 124 transmits to the terminal 10 the traffic channel assign and a command that indicates whether the traffic channel assignment is to be retained while idle. The SBS 124 then retains the assigned traffic channel for use by the terminal 10 while the terminal 10 is idle between data traffic transmissions to the SBS 124. The terminal 10 retain the traffic channel assignment for use by the terminal while the terminal is idle between data traffic transmissions to the satellite 126 in response to the command indicating that the assignment is to be retained while idle. The terminal 10 may thereby more quickly transmit data traffic as it is becomes ready by using the assigned traffic channel without incurring a potentially significant transmission delay that may occur if the terminal 10 were required to transmit a traffic channel request (e.g., a Connection Request Message) through the satellite 126 to the SBS 124 and then wait for a responsive traffic channel assignment.
If not constrained, such retention of traffic channels could result in all traffic channels being assigned to idle terminals and with no remaining traffic channels being available for use by other terminals that are ready to transmit data traffic. However, in accordance with some embodiments, the pre-assignment and retention of traffic channels is regulated in response to a Type Of Service (TOS) designation that is associated with terminals. The TOS designation may indicate that a particular terminal is to be provided reduced latency PTT protocol service, reduced latency VOIP service, and/or another reduced latency communication service. The SBN 120 may be configured to respond to a first TOS designation being associated with a terminal by retaining a traffic channel for exclusive use by the terminal while the terminal is idle between data traffic transmissions to the satellite 126 and, in contrast, may respond to a different second TOS designation being associated with the terminal by not assigning a traffic channel for use by the terminal until a traffic channel request is received therefrom and then releasing the assigned traffic channel for use by another terminal in response to the terminal becoming idle between data traffic transmission.
A terminal having the first TOS designation, which has received a command that indicates whether the traffic channel assignment is to be retained while idle, may thereby transmit data traffic through the retained traffic channel assignment without waiting for the system to assign another traffic channel to the terminal. In contrast, a terminal having the second TOS designation, which has not received a pre-assigned traffic channel and/or has not received a command indicating that the traffic channel assignment is to be retained while idle, must transmit a traffic channel request (e.g., transmit a Connection Request Message) to the system and wait for a traffic channel assignment thereto before transmitting data traffic. The first TOS designated terminal may thereby more quickly transition from being idle to transmitting data to the SBS 124 compared to the second TOS designated terminal, and which may be particularly advantageous for PTT protocol service, VOIP service, and/or another communication service that has alternating cycles of the terminal being ready to transmit data traffic and then being idle.
The SBN 120 may control how many terminals within the spot beam 128 have the first TOS designation and/or may change dynamically change the TOS designations associated with particular terminals in order control how many traffic channels are available for assignment to terminals. A SBN operator may thereby offer reduced latency communication services as a premium service for subscribers and/or as an otherwise marketable feature of its system.
For example, when the satellite 126 is able to simultaneously receive signals through 96 active traffic channels within the spot beam 128, the SBN 120 may reserve 16 traffic channels for communications relating to registration of terminals and other access related functionality. Of the 80 remaining traffic channels, the SBN 120 may reserve a portion (e.g., 40 traffic channels) for pre-assignment and retention by terminals so as to provide reduced latency communication services thereto, and may leave the remaining portion (e.g., another 40 traffic channels) available for assignment to other terminals in response to specific traffic channel requests (e.g., Connection Request Messages) from the other terminals. The number of traffic channels that are assigned as reduced latency traffic channels and otherwise available as regular latency traffic channels can be regulated by the SBN 120 responsive to the TOS designation for the terminals and/or other operational characteristics, such as those explained below.
When the number of traffic channels that are available for assignment to second TOS designated terminals falls below a threshold value, the SBN 120 may reduce the number of traffic channels that are available to be pre-assigned and retained by first TOS designated terminals. The SBN 120 may alternatively or additionally release presently assigned traffic channels for use by other terminals by notifying certain idle first TOS designated terminals that they no longer retain a traffic channel and must therefore transmit a traffic channel request and wait for a responsive traffic channel assignment before their next data traffic transmission. For example, the SBN 120 may transmit a command to the certain idle first TOS designated terminals that notifies them that they may no longer retain the previously assigned traffic channels.
In some embodiments, the SBS 124 may release a traffic channel that is presently assigned to first TOS designated terminal for use by another terminal in response to determining that a signal quality of a communication that is received by the satellite 126 from the terminal and/or that is received by the terminal from the satellite 126 is less than a threshold level. Accordingly, bad signal quality, such as due to a terminal entering a building, may trigger cessation of reduced latency communication service for that terminal. The threshold level may be a static value or a value that is controlled responsive to one or more defined parameters, such as a number of actively communicating terminals and/or a number of idle terminals that are registered in the spot beam 128.
In some embodiments, the SBS 124 may release a traffic channel that is presently assigned to first TOS designated terminal for use by another terminal in response to determining that the terminal is moving at greater than a threshold velocity. Because terminal velocity can affect communication signal quality (e.g., higher velocity can result in lower signal quality), the SBS 124 may cease providing reduced latency communication service when the terminal's velocity exceeds the threshold. The threshold velocity may be a static value or a value that is controlled responsive to one or more defined parameters, such as a number of actively communicating terminals and/or a number of idle terminals that are registered in the spot beam 128.
In some embodiments, the SBS 124 may switch from retaining a traffic channel assignment for an idle terminal to releasing the traffic channel assignment upon the terminal becoming idle and, vice versa, to track dynamic changes to a priority level that is assigned to the terminal. The high priority assigned to a terminal may be controllable by a user, such as by activation of an emergency communication mode, and/or it may be controlled by the SBS 124 responsive to an operational mode of the terminal (e.g., PTT mode and/or VOIP mode).
The SBS 124 may alternatively or additionally switch from retaining a traffic channel assignment for an idle terminal to releasing the traffic channel assignment upon the terminal becoming idle and, vice versa, in response to determining that the terminal is located at a defined geographic location, such as within a region that does not have overlapping coverage by the ATN 110 and/or at a defined location such as at a work facility.
The SBS 124 may alternatively or additionally switch from retaining a traffic channel assignment for an idle terminal to releasing the traffic channel assignment upon the terminal becoming idle and, vice versa, in response to occurrence of a time of day and/or a day of week. Accordingly, the SBS 124 may cease retaining a traffic channel assignment for an idle terminal during weekdays and/or within historically higher traffic times of the day.
With further reference to
The PCRF equipment 136 and the IMS 138 may operate in a convention manner defined by, for example, the 3GPP standards, and/or other communication standards that are well known in the art. Alternatively, one or both of those components may be configured to assist in defining the TOS designations and/or otherwise controlling how many traffic channels within the spot beam 128 are available for pre-assignment and retention by terminals to provide reduced latency communication services.
The AAA server 132 may communicate the identified TOS designation in a Differentiated Services Code Point (DSCP) header portion of the data packet which is communicated to the HSGW 130 responsive to the registration request from the AT 10. More particularly, the TOS designation for the AT 10 may be defined by a logic value contained in bit locations 6 and/or 7 of the DSCP header portion of the data packet. The HSGW 130 may thereby determine the TOS designation of the AT 10 by determining the logical value at bit locations 6 and/or 7 of the DSCP header portion of the data packet that is received from the AAA server 132.
The HSGW 130 responds to the TOS designation corresponding to a reduced latency communication service by communicating (block 208) a message to the SBS 124 to carry out Traffic Channel Assignment (TCA). The SBS 124 assigns a traffic channel to the AT 10 and communicates (block 210) a message to the AT 10 that identifies the assigned traffic channel and notifies the AT 10 that the traffic channel will be retained for use by the AT 10 while the AT 10 is idle between data traffic transmissions. In some embodiments, the SBS 124 assigns a carrier frequency of a Frequency Division Multiplex Access (FDMA) channel for use by the AT 10 to transmit data traffic to the satellite 126 for relay to the SBS 124. The assigned carrier frequency is then retained for exclusive use by the AT 10 while the AT 10 is idle between data traffic transmissions to the satellite 126.
In some other embodiments, the SBS 124 assigns a timeslot of a Time Division Multiplex Access (TDMA) channel for use by the AT 10 to transmit data traffic to the satellite 126 for relay to the SBS 124. The assigned timeslot is then retained for exclusive use by the AT 10 while the AT 10 is idle between data traffic transmissions to the satellite 126.
In some other embodiments, the SBS 124 assigns a spreading code of a Code Division Multiplex Access (CDMA) channel for use by the AT 10 to transmit data traffic to the satellite 126 for relay to the SBS 124. The assigned spreading code is then retained for exclusive use by the AT 10 while the AT 10 is idle between data traffic transmissions to the satellite 126.
The AT 10 and the SBS 124 communicate (block 212) to confirm receipt of the TCA and to set up a connection through the SBS 124 and the HSGW 130. For example, a Point-to-Point Protocol (PPP) link layer can be set up (block 214) for the AT 10 through the ground-based network infrastructure (e.g., a core network) as a A10/A11 connection a conventional manner according to one or more of the 3GPP standards, which is well known in the art.
The AT 10 and the SBS 124 may further negotiate and configure (block 216) a Quality of Service (QoS) level for PTT. VOIP, and/or other communications to/from the AT 10. The negotiation and configuration may include QoS queries and responses (blocks 218 to 220) between the SBS 124 and the HSGW 130, and may further include communication with the AAA server 142. The AT 10 may transmit a Reservation on Request message (block 222) that requests access to certain network resources, and the SBS 124 can respond thereto using a Reservation Acceptance message (block 224). A session initiation protocol (SIP) can then be established (block 226) through the ground-based network infrastructure for use in communications by the terminal.
The AT 10 can then enter an idle state 228 if it is does not presently have data traffic that is ready for transmission. In response to ready data traffic, the AT 10 exits the idle state 228 and uses the assigned traffic channel to transmit (block 230) the data traffic to the satellite 126 for relay to the SBS 124. The SBS 124 forwards (block 230) the data traffic through the HSGW 130 to the packet switched network 142. The AT 10 can then return (block 232) to the idle state. In response to subsequently ready data traffic, the AT 10 uses the assigned traffic channel (TCH) to transmit (block 234) the data traffic to the satellite 126 for relay to the SBS 124, and the data traffic is forwarded (block 236) through the HSGW 130 to the packet switched network 142.
The AT 10 is thereby provided reduced latency communication service because of its ability to more immediately transmit data traffic as it becomes ready for transmission, and without be required to transmit a traffic channel request to the SBS 124 and wait for a responsive traffic channel assignment. Reducing communication latency may be particularly desirable for some communication protocol services, such as for PTT voice data communications and VOIP communications where data traffic may be generated responsive to a user's action (e.g., pressing a PTT switch and/or speaking into a microphone).
More particularly, responsive to a user pressing the PTT switch (block 300), the AT 10 transmits (302) voice data to the satellite 126, for relay to the SBS 124, using the assigned traffic channel and without waiting for assignment of another traffic channel to the AT 10. The SBS 124 forwards (block 304) the voice data to the HSGW 130, which forwards (block 306) the voice data to the packet switched network 142. The AT 10 then returns to the idle state 308 in response to not having further data traffic that is ready for transmission. While in the idle state, the SBS 124 retains the assigned traffic channel for exclusive use by the AT 10 (i.e., the assigned traffic channel is not reassigned for use by another AT). Again responsive to the user pressing the PTT switch (block 310), the AT 10 transmits (block 312) the voice data to the satellite 126, for relay to the SBS 124, using the assigned traffic channel and without waiting for assignment of another traffic channel to the AT 10 can. The SBS 124 forwards (block 314) the voice data to the HSGW 130, which forwards (block 316) the voice data to the packet switched network 142. The AT 10 then returns (block 318) to the idle state in response to not having further data traffic that is ready for transmission. While in the idle state, the SBS 124 again retains the assigned TCH for exclusive use by the AT 10.
Accordingly, various embodiments of the present invention may reduce communication latency for terminals that communicate with a SBN. Traffic channels can be pre-assigned and more permanently retained for terminals so they may more quickly transmit data traffic as it is becomes ready for transmission. The pre-assignment and retention of traffic channels may be regulated in response to a TOS designation that is associated with terminals, and the TOS designation can be set to provide reduced latency communication for terminals that communicate using PTT protocol service, VOIP service, and/or another service. The TOS designations for individual terminals may be controlled by service providers as a way of offering a premium service to subscribers. The number of traffic channels within a spot beam that are pre-assigned and retained for use by registered terminals can be controlled so that a defined number of traffic channels remain available for assignment to terminals responsive to their traffic channel requests (e.g., Connection Request Messages).
The present invention was described above with reference to block diagrams and message flow diagrams illustrating methods and apparatus (systems) according to embodiments of the invention. It is understood that operations in the diagrams may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, such as a digital signal processor, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the diagrams. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function/act specified in the diagrams. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the figures.
In the figures and specification, there have been disclosed embodiments of the invention and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention being set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4901307 | Gilhousen et al. | Feb 1990 | A |
5073900 | Mallinckrodt | Dec 1991 | A |
5303286 | Wiedeman | Apr 1994 | A |
5339330 | Mallinckrodt | Aug 1994 | A |
5394561 | Freeburg | Feb 1995 | A |
5446756 | Mallinckrodt | Aug 1995 | A |
5448623 | Wiedeman et al. | Sep 1995 | A |
5511233 | Otten | Apr 1996 | A |
5555257 | Dent | Sep 1996 | A |
5584046 | Martinez et al. | Dec 1996 | A |
5612703 | Mallinckrodt | Mar 1997 | A |
5619525 | Wiedeman et al. | Apr 1997 | A |
5631898 | Dent | May 1997 | A |
5761605 | Tawil et al. | Jun 1998 | A |
5765098 | Bella | Jun 1998 | A |
5812947 | Dent | Sep 1998 | A |
5832379 | Mallinckrodt | Nov 1998 | A |
5835857 | Otten | Nov 1998 | A |
5842125 | Modzelesky et al. | Nov 1998 | A |
5848060 | Dent | Dec 1998 | A |
5852721 | Dillon et al. | Dec 1998 | A |
5878329 | Mallinckrodt | Mar 1999 | A |
5884142 | Wiedeman et al. | Mar 1999 | A |
5907541 | Fairholm et al. | May 1999 | A |
5913164 | Pawa et al. | Jun 1999 | A |
5926745 | Threadgill et al. | Jul 1999 | A |
5926758 | Grybos et al. | Jul 1999 | A |
5930295 | Isley et al. | Jul 1999 | A |
5937332 | Karabinis | Aug 1999 | A |
5940753 | Mallinckrodt | Aug 1999 | A |
5991345 | Ramasastry | Nov 1999 | A |
5995832 | Mallinckrodt | Nov 1999 | A |
6011951 | King et al. | Jan 2000 | A |
6023605 | Sasaki et al. | Feb 2000 | A |
6035039 | Tisdale et al. | Mar 2000 | A |
6052560 | Karabinis | Apr 2000 | A |
6052586 | Karabinis | Apr 2000 | A |
6067442 | Wiedeman et al. | May 2000 | A |
6072430 | Wyrwas et al. | Jun 2000 | A |
6085094 | Vasudevan et al. | Jul 2000 | A |
6091933 | Sherman et al. | Jul 2000 | A |
6097752 | Wiedeman et al. | Aug 2000 | A |
6101385 | Monte et al. | Aug 2000 | A |
6108561 | Mallinckrodt | Aug 2000 | A |
6134437 | Karabinis et al. | Oct 2000 | A |
6157811 | Dent | Dec 2000 | A |
6157834 | Helm et al. | Dec 2000 | A |
6160994 | Wiedeman | Dec 2000 | A |
6169878 | Tawil et al. | Jan 2001 | B1 |
6198730 | Hogberg et al. | Mar 2001 | B1 |
6198921 | Youssefzadeh et al. | Mar 2001 | B1 |
6201967 | Goerke | Mar 2001 | B1 |
6233463 | Wiedeman et al. | May 2001 | B1 |
6240124 | Wiedeman et al. | May 2001 | B1 |
6243580 | Garner | Jun 2001 | B1 |
6253080 | Wiedeman et al. | Jun 2001 | B1 |
6256497 | Chambers | Jul 2001 | B1 |
6278861 | Ward et al. | Aug 2001 | B1 |
6324405 | Young et al. | Nov 2001 | B1 |
6339707 | Wainfan et al. | Jan 2002 | B1 |
6408179 | Stosz et al. | Jun 2002 | B1 |
6418147 | Wiedeman | Jul 2002 | B1 |
6449461 | Otten | Sep 2002 | B1 |
6522865 | Otten | Feb 2003 | B1 |
6529740 | Ganucheau et al. | Mar 2003 | B1 |
6628919 | Curello et al. | Sep 2003 | B1 |
6684057 | Karabinis | Jan 2004 | B2 |
6735437 | Mayfield et al. | May 2004 | B2 |
6775251 | Wiedeman et al. | Aug 2004 | B1 |
6785543 | Karabinis | Aug 2004 | B2 |
6856787 | Karabinis | Feb 2005 | B2 |
6859652 | Karabinis et al. | Feb 2005 | B2 |
6879829 | Dutta et al. | Apr 2005 | B2 |
6892068 | Karabinis et al. | May 2005 | B2 |
6937857 | Karabinis | Aug 2005 | B2 |
6975837 | Santoru | Dec 2005 | B1 |
6999720 | Karabinis | Feb 2006 | B2 |
7006789 | Karabinis et al. | Feb 2006 | B2 |
7031702 | Karabinis et al. | Apr 2006 | B2 |
7039400 | Karabinis et al. | May 2006 | B2 |
7062267 | Karabinis | Jun 2006 | B2 |
7092708 | Karabinis | Aug 2006 | B2 |
7113743 | Karabinis | Sep 2006 | B2 |
7113778 | Karabinis | Sep 2006 | B2 |
7155340 | Churan | Dec 2006 | B2 |
7174127 | Otten et al. | Feb 2007 | B2 |
7181161 | Karabinis | Feb 2007 | B2 |
7203490 | Karabinis | Apr 2007 | B2 |
7218931 | Karabinis | May 2007 | B2 |
7295807 | Karabinis | Nov 2007 | B2 |
7340213 | Karabinis et al. | Mar 2008 | B2 |
7418236 | Levin et al. | Aug 2008 | B2 |
7418263 | Dutta et al. | Aug 2008 | B2 |
7421342 | Churan | Sep 2008 | B2 |
7437123 | Karabinis et al. | Oct 2008 | B2 |
7444170 | Karabinis | Oct 2008 | B2 |
7447501 | Karabinis | Nov 2008 | B2 |
7453396 | Levin et al. | Nov 2008 | B2 |
7453920 | Churan | Nov 2008 | B2 |
7454175 | Karabinis | Nov 2008 | B2 |
7457269 | Grayson | Nov 2008 | B1 |
7558568 | Karabinis | Jul 2009 | B2 |
7574206 | Karabinis | Aug 2009 | B2 |
7577400 | Karabinis et al. | Aug 2009 | B2 |
7587171 | Evans et al. | Sep 2009 | B2 |
7593691 | Karabinis | Sep 2009 | B2 |
7593724 | Karabinis | Sep 2009 | B2 |
7593725 | Karabinis | Sep 2009 | B2 |
7593726 | Karabinis et al. | Sep 2009 | B2 |
7596111 | Karabinis | Sep 2009 | B2 |
7599656 | Karabinis | Oct 2009 | B2 |
7603081 | Karabinis | Oct 2009 | B2 |
7603117 | Karabinis | Oct 2009 | B2 |
7606590 | Karabinis | Oct 2009 | B2 |
7609666 | Karabinis | Oct 2009 | B2 |
7620394 | Good et al. | Nov 2009 | B2 |
7623859 | Karabinis | Nov 2009 | B2 |
7623867 | Karabinis | Nov 2009 | B2 |
7627285 | Karabinis | Dec 2009 | B2 |
7634234 | Karabinis | Dec 2009 | B2 |
7636566 | Karabinis | Dec 2009 | B2 |
8170474 | Karabinis et al. | May 2012 | B2 |
20020013149 | Threadgill et al. | Jan 2002 | A1 |
20020061759 | Maggenti et al. | May 2002 | A1 |
20020122408 | Mullins | Sep 2002 | A1 |
20020133596 | Border et al. | Sep 2002 | A1 |
20020146979 | Regulinski et al. | Oct 2002 | A1 |
20020177465 | Robinett | Nov 2002 | A1 |
20030003815 | Yamada | Jan 2003 | A1 |
20030112878 | Kloper | Jun 2003 | A1 |
20030149986 | Mayfield et al. | Aug 2003 | A1 |
20040072539 | Monte et al. | Apr 2004 | A1 |
20040102156 | Loner | May 2004 | A1 |
20040121727 | Karabinis | Jun 2004 | A1 |
20040203393 | Chen | Oct 2004 | A1 |
20040240525 | Karabinis et al. | Dec 2004 | A1 |
20050041619 | Karabinis et al. | Feb 2005 | A1 |
20050090256 | Dutta | Apr 2005 | A1 |
20050118948 | Karabinis et al. | Jun 2005 | A1 |
20050136836 | Karabinis et al. | Jun 2005 | A1 |
20050164700 | Karabinis | Jul 2005 | A1 |
20050164701 | Karabinis et al. | Jul 2005 | A1 |
20050181786 | Karabinis et al. | Aug 2005 | A1 |
20050201449 | Churan | Sep 2005 | A1 |
20050227618 | Karabinis et al. | Oct 2005 | A1 |
20050239399 | Karabinis | Oct 2005 | A1 |
20050260947 | Karabinis et al. | Nov 2005 | A1 |
20050260984 | Karabinis | Nov 2005 | A1 |
20050265273 | Karabinis et al. | Dec 2005 | A1 |
20050272369 | Karabinis et al. | Dec 2005 | A1 |
20050288011 | Dutta | Dec 2005 | A1 |
20060040613 | Karabinis et al. | Feb 2006 | A1 |
20060094352 | Karabinis | May 2006 | A1 |
20060094420 | Karabinis | May 2006 | A1 |
20060105707 | Karabinis | May 2006 | A1 |
20060111041 | Karabinis | May 2006 | A1 |
20060111056 | Dutta | May 2006 | A1 |
20060135058 | Karabinis | Jun 2006 | A1 |
20060135070 | Karabinis | Jun 2006 | A1 |
20060165120 | Karabinis | Jul 2006 | A1 |
20060189274 | Karabinis | Aug 2006 | A1 |
20060189275 | Karabinis | Aug 2006 | A1 |
20060194576 | Karabinis et al. | Aug 2006 | A1 |
20060205347 | Karabinis | Sep 2006 | A1 |
20060205367 | Karabinis | Sep 2006 | A1 |
20060211371 | Karabinis et al. | Sep 2006 | A1 |
20060211452 | Karabinis | Sep 2006 | A1 |
20060217070 | Karabinis | Sep 2006 | A1 |
20060229090 | LaDue | Oct 2006 | A1 |
20060246838 | Karabinis | Nov 2006 | A1 |
20060252368 | Karabinis | Nov 2006 | A1 |
20060276129 | Karabinis | Dec 2006 | A1 |
20060276167 | Burroughs | Dec 2006 | A1 |
20060292990 | Karabinis et al. | Dec 2006 | A1 |
20070010246 | Churan | Jan 2007 | A1 |
20070015460 | Karabinis et al. | Jan 2007 | A1 |
20070021059 | Karabinis et al. | Jan 2007 | A1 |
20070021060 | Karabinis et al. | Jan 2007 | A1 |
20070037514 | Karabinis | Feb 2007 | A1 |
20070072545 | Karabinis et al. | Mar 2007 | A1 |
20070099562 | Karabinis et al. | May 2007 | A1 |
20070123252 | Tronc et al. | May 2007 | A1 |
20070129019 | Otten et al. | Jun 2007 | A1 |
20070135051 | Zheng et al. | Jun 2007 | A1 |
20070184849 | Zheng | Aug 2007 | A1 |
20070192805 | Dutta et al. | Aug 2007 | A1 |
20070202816 | Zheng | Aug 2007 | A1 |
20070232298 | Karabinis | Oct 2007 | A1 |
20070238442 | Mate et al. | Oct 2007 | A1 |
20070243866 | Karabinis | Oct 2007 | A1 |
20070281612 | Benjamin et al. | Dec 2007 | A1 |
20070293214 | Ansari et al. | Dec 2007 | A1 |
20080008264 | Zheng | Jan 2008 | A1 |
20080032671 | Karabinis | Feb 2008 | A1 |
20080032690 | Karabinis | Feb 2008 | A1 |
20080113666 | Monte et al. | May 2008 | A1 |
20080119190 | Karabinis | May 2008 | A1 |
20080160993 | Levin et al. | Jul 2008 | A1 |
20080182572 | Tseytlin et al. | Jul 2008 | A1 |
20080214207 | Karabinis | Sep 2008 | A1 |
20080268836 | Karabinis et al. | Oct 2008 | A1 |
20090011704 | Karabinis | Jan 2009 | A1 |
20090029696 | Karabinis | Jan 2009 | A1 |
20090040100 | Levin et al. | Feb 2009 | A1 |
20090042509 | Karabinis et al. | Feb 2009 | A1 |
20090042516 | Karabinis | Feb 2009 | A1 |
20090075645 | Karabinis | Mar 2009 | A1 |
20090088151 | Karabinis | Apr 2009 | A1 |
20090104903 | Karabinis | Apr 2009 | A1 |
20090131046 | Karabinis et al. | May 2009 | A1 |
20090137203 | Karabinis et al. | May 2009 | A1 |
20090156154 | Karabinis et al. | Jun 2009 | A1 |
20090170427 | Karabinis | Jul 2009 | A1 |
20090170428 | Karabinis | Jul 2009 | A1 |
20090170429 | Karabinis | Jul 2009 | A1 |
20090186622 | Karabinis | Jul 2009 | A1 |
20090231187 | Churan | Sep 2009 | A1 |
20090285150 | Ravishankar et al. | Nov 2009 | A1 |
20090296628 | Karabinis | Dec 2009 | A1 |
20090305697 | Karabinis et al. | Dec 2009 | A1 |
20090312013 | Karabinis | Dec 2009 | A1 |
20100041418 | Edge et al. | Feb 2010 | A1 |
20100214996 | Santhanam et al. | Aug 2010 | A1 |
20110164554 | Jacks | Jul 2011 | A1 |
Number | Date | Country |
---|---|---|
0 506 255 | Sep 1992 | EP |
0 506 255 | Sep 1992 | EP |
0 597 225 | May 1994 | EP |
0 506 255 | Nov 1996 | EP |
0 748 065 | Dec 1996 | EP |
0 755 163 | Jan 1997 | EP |
0 762 669 | Mar 1997 | EP |
0 762 669 | Mar 1997 | EP |
0 797 319 | Sep 1997 | EP |
0 831 599 | Mar 1998 | EP |
0 831 599 | Mar 1998 | EP |
1 059 826 | Dec 2000 | EP |
1 193 989 | Apr 2002 | EP |
1 944 885 | Jul 2008 | EP |
1 569 363 | Nov 2008 | EP |
WO 0154314 | Jul 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20110164554 A1 | Jul 2011 | US |