In a wireless telecommunications system, radio channels provide a physical link between communications units. The equipment in such a system typically includes a base station processor in communication with a network such as the Public Switched Telephone Network (PSTN), in the case of voice communications, or a data network, in the case of data communications, and one or more access terminals in communication with a plurality of end user computing devices, such as user PCs. The combination of an access terminal and computing device(s) may be referred to as a field unit. The wireless channels include forward channels, for message transmission from the base station processor to the subscriber access units, and reverse channels, for message transmission to the base station processor from the field units.
In the case of a wireless data system such as may be used to provide wireless Internet access, each base station processor typically serves many access terminals, which in turn serve many end user computing devices. The wireless channels, however, are a limited resource, and are therefore allocated by a scheduler among the field units served by the base station processor. The scheduler allocates the wireless channels among the field units on a traffic demand basis.
One way of supporting on-demand access among multiple users is referred to as Time Division Multiple Access (TDMA), where each of the wireless channels are allocated to specific connections only for certain predetermined time intervals or time slots. A second way of supporting on-demand access among multiple users is referred to as Code Division Multiple Access (CDMA), which allows multiple users to share the same radio spectrum. Instead of dividing a Radio Frequency (RF) spectrum into narrow channels (e.g. 30 kHz each in analog wireless systems), CDMA spreads many channels over a broad spectrum (1.25 MHZ in the case of the North American CDMA standard known as IS-95). To separate a particular channel from the other channel using the same spectrum at the same time, a unique digital code called a pseudo-random (i.e., pseudo-noise or PN) code is assigned to each user. Many users (up to 64 for IS-95) share the same spectrum, each using their unique code, and decoders separate the codes at each end in a process similar to a tuner that separates different frequencies in more conventional systems.
The PN codes used for communication channel definitions typically have a defined code repeat period or code epoch. For each such epoch duration (also called a slot), a base station central controlling system or processor can further schedule assignments of forward traffic channels (forward slot allocations or “FSAs”) and reverse traffic channels (reverse slot allocations or “RSAs”) to active mobile units for each epoch. This is typically done in such a way that all channels are assigned to active users as much as possible. It typically takes a predetermined amount of time for the allocation command to be received and to configure the demodulators before receiving the new code channel. In particular, when a PN code is reassigned to a different user connection, it typically takes a determined period of time for the code demodulators in the receiver to lock in the new code. This in turn introduces latency in the reception of the data packets that must travel on the coded channel.
To coordinate traffic channels, the base station processor communicates with a given field unit in the following manner. First, the base station processor checks to make sure there is an available channel. Second, the base station processor sends a message to the given field unit to set up the available channel. The given field unit processes the message (2-3 epochs) to set-up the channel and sends an acknowledgment (1-2 epochs) confirming set-up complete. To tear down the channel, the base station processor sends a message to the given field unit, which processes the command (1-2 epochs) and sends back an acknowledgment (1-2 epochs).
A communications system employing the principles of the present invention reduces packet latency, which, in turn, improves response time for setting up traffic channels in a communications system, such as an on-demand access, packet switched, CDMA communications system. These improvements apply to both forward and reverse traffic channels.
Channel code assignments are pipelined from a base transceiver station (BTS) down to all of the mobile units in a cell zone associated with the BTS so the actual transmission of traffic data can begin, within about two epochs after the channel assignments. Keeping this delay to a minimum is what improves the latency.
There are at least three features that help in keeping this delay short: (i) dividing a control channel, such as the paging channel, into control subchannels, such as two control subchannels or half-channels (optionally referred to as a forward half-channel and reverse half-channel), where, in the case of two control subchannels, the new split paging channels may be less than or equal to about half the duration of the standard control channels (e.g., half an epoch), (ii) staggering the forward and reverse traffic channels by about half an epoch, and eliminating the acknowledgment returned to the BTS, since the slot allocation/deallocation commands are redundant (i.e., sent multiple times for a contiguous slot allocation). Forward and reverse slot allocation data may be transmitted in objects less than or equal to about a half epoch duration and transmitted from the base station processor to the field units in respective forward and reverse subchannels, e.g., paging subchannels.
These two features can improve latency by one or two epochs per forward and reverse channel allocation. This, in turn, shows up as a noticeable improvement in response time to the user.
In one embodiment, the present invention may be used in link layer software on the base station and field units to improve channel latency and can be used by any system using a CDMA packet switched communications system.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.
A description of embodiments of the invention follows.
The field units 15a-15d are in wireless communication with a base station processor (BSP) 16 via a wireless link 26. The wireless link 26 conforms to a wireless protocol such as IS-95 or another wireless protocol which supports communications via an RF medium.
The base station processor 16 is also connected to a public access network 28, such as the Internet, via an internetworking gateway 18. The internetworking gateway 18 is typically a bridge, router, or other connection to a network backbone and may be provided by a remote provider, such as an Internet Service Provider (ISP). In this manner, an end user at the PC 12 is provided a wireless connection to a public access network 28 via the AT 14 and the base station processor 16.
Typically, a user PC 12 sends a message over a wired link 20, such as a local area network or bus connection, to the field unit 14. The field unit 14 sends a message via the wireless link 26 to the base station processor 16. The base station processor 16 sends the message to the public access network 28 via the internetworking gateway 18 for delivery to a remote node 30 located on the network 28. Similarly, the remote node 30 located on the network can send a message to the field unit 14 by sending it to the base station processor 16 via the internetworking gateway 18. The base station processor 16 sends the message to the access terminal 14 serving the PC 12 via the wireless link 26. The access terminal 14 sends the message to the PC 12 via the wired link 20. The PC 12 and the base station processor 16 can therefore be viewed as endpoints of the wireless link 26.
As indicated above, there are typically many more field units 15 than there are available wireless channel resources. For this reason, the wireless channels are allocated according to some type of demand-based multiple access technique to make maximum use of the available radio channels. Multiple access is often provided in the physical layer or by techniques that manipulate the radio frequency signal, such as Time Division Multiple Access (TDMA) or Code Division Multiple Access (CDMA) techniques. In any event, the nature of the radio spectrum is such that it is a medium that is expected to be shared. This is quite dissimilar from the traditional wired environment for data transmission in which a wired medium, such as a telephone line or network cabling, is relatively inexpensive to obtain and to keep open all the time.
In a typical wireless transmission, a send message often results in a return acknowledgment message. A wireless channel is allocated to send the message, and a second wireless channel is allocated in the opposite direction to send the return message. Wireless channel allocation can occur by a variety of methods well known in the art.
The timing diagram 30 is separated horizontally into four epochs 32-1 through 32-4 and vertically into a sequence of steps used to transmit and activate the forward channels. A first step 34 is provided in which the base station processor 16 loads forward slot allocations into a paging/F buffer object. The paging/F buffer object includes typical overhead information as a standard buffer object of the prior art, but only includes traffic channel allocation data for the forward traffic channels and, thus, is only a half epoch in duration. A second step 36 is provided in which the paging/F buffer object is transmitted by the base station processor 16 to the field unit 15 and demodulated by the field unit 15. In a third step 38, the field unit 15 decodes the paging/F buffer object, extracts forward channel assignments, and configures its receiver(s) for the forward channels. In a fourth step 40, a half epoch after decoding the paging/F buffer object, the field unit 15 decodes data traffic on the forward channels.
The paging channel may be split into two subchannels, such as one for transmitting forward slot allocation data and one for transmitting reverse slot allocation data. Each subchannel may be less than or equal to about half an epoch long and may be referred to as a “forward” half-channel and a “reverse” half-channel.
It should be understood that the paging channel may be further subdivided into smaller slotted subchannels of less than or equal to about 1/n.sup.th of an epoch long, where n is the number of subchannels. Further, the lengths of the subchannels may be different, so long as the combined length is less than or equal to an epoch. It should also be understood that the subdivided channel may be a channel other than the paging channel, such as a maintenance channel or an unused traffic channel.
The rest of the discussion assumes the paging channel is split into two subchannels, referred to as half-channels.
As shown in
Referring to
The reverse epoch 52 may be staggered by half an epoch to close up the amount of delay between sending Reverse Slot Allocations (step 56) and actually transmitting reverse traffic (step 60). This means the reverse channel assignment can be transmitted in the reverse half-channel in one epoch 52-2 and, in the following epoch 52-3, reverse traffic data can be sent up the reverse channel defined by the reverse slot allocation data.
Splitting the paging channel into two channels of half-epoch duration and independently transmitting the paging/F buffer objects and paging/R objects saves an extra epoch in time that would normally be needed to demodulate a full, standard, paging channel having the paging/F buffer objects and paging/R objects concatenated and transmitted together in a full epoch. Also, by making the paging/R object only ½ epoch, the base station processor 16 can delay loading the Reverse Slot Allocations by half an epoch (e.g., start the loading at the start of the first reverse epoch 52-1 rather than at the start of the first forward epoch 32-1), which allows late requests get into the allocations that normally would need to wait another epoch.
This system can be improved even further if the base station processor 16 delays the loading of the Reverse Slot Allocations 54a until after the first forward epoch 32-1, as defined by a loading step 54b in the timing diagram 50 of
It is assumed that the Slot allocations arrive at the physical layer and are sent between the base station processor 16 and field unit 15 in one epoch. This results in another one-half epoch improvement on latency overall.
It should be understood that the process described herein may be provided by software, firmware, or hardware. The software may be stored in RAM, ROM, optical or magnetic disk, or other storage media. The software is loaded and executable by a processor that interacts with devices capable of providing wire or wireless communication functions described herein or known to operate in the system 10 of
While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.
This application is a continuation of U.S. patent application Ser. No. 15/417,831 filed Jan. 27, 2017, which is a continuation of U.S. patent application Ser. No. 13/867,163 filed Apr. 22, 2013, which issued as U.S. Pat. No. 9,648,611 on May 9, 2017, which is a continuation of U.S. patent application Ser. No. 12/402,813, filed Mar. 12, 2009, which issued as U.S. Pat. No. 8,432,876 on Apr. 30, 2013, which is a continuation of U.S. patent application Ser. No. 10/350,308, filed Jan. 22, 2003, which issued as U.S. Pat. No. 7,512,102 on Mar. 31, 2009, which claims the benefit of U.S. Provisional Application Ser. No. 60/350,835, filed Jan. 22, 2002, the contents of which are hereby incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
5150361 | Wieczorek et al. | Sep 1992 | A |
5193091 | Crisler et al. | Mar 1993 | A |
5513183 | Kay et al. | Apr 1996 | A |
5559807 | Van den Heuvel et al. | Sep 1996 | A |
5657358 | Panech et al. | Aug 1997 | A |
6031827 | Rikkinen et al. | Feb 2000 | A |
6052364 | Chalmers | Apr 2000 | A |
6351461 | Sakoda | Feb 2002 | B1 |
6421540 | Gilhousen et al. | Jul 2002 | B1 |
6516189 | Frangione | Feb 2003 | B1 |
6563808 | Cox et al. | May 2003 | B1 |
6804252 | Johnson | Oct 2004 | B1 |
6819930 | Laroia et al. | Nov 2004 | B1 |
6973064 | Terry et al. | Dec 2005 | B2 |
7433340 | Proctor, Jr. | Oct 2008 | B1 |
7580713 | McBeath et al. | Aug 2009 | B2 |
7580715 | Gorsuch | Aug 2009 | B2 |
7599334 | Odenwalder et al. | Oct 2009 | B2 |
8280377 | Lee et al. | Oct 2012 | B2 |
8676240 | Lindoff et al. | Mar 2014 | B2 |
8681711 | Balasubramanian | Mar 2014 | B2 |
8711785 | Gholmieh et al. | Apr 2014 | B2 |
8730924 | Kazmi et al. | May 2014 | B2 |
20020015388 | Kim | Feb 2002 | A1 |
20020015393 | Pan | Feb 2002 | A1 |
20020080816 | Spinar | Jun 2002 | A1 |
20020085523 | Kim | Jul 2002 | A1 |
20020141479 | Garcia-Luna-Aceves | Oct 2002 | A1 |
20020163894 | Alapuranen et al. | Nov 2002 | A1 |
20020191579 | Terry | Dec 2002 | A1 |
20030012174 | Bender et al. | Jan 2003 | A1 |
20030036358 | Pan | Feb 2003 | A1 |
20030060224 | Nelson, Jr. et al. | Mar 2003 | A1 |
20030086383 | Bremer et al. | May 2003 | A1 |
20030119518 | Cleveland et al. | Jun 2003 | A1 |
20040258084 | Laroia et al. | Dec 2004 | A1 |
20050136923 | Alapuranen et al. | Jun 2005 | A1 |
20050176437 | Mir | Aug 2005 | A1 |
20060013182 | Balasubramanian et al. | Jan 2006 | A1 |
20060098655 | Zeira | May 2006 | A1 |
20070064589 | Fruhauf et al. | Mar 2007 | A1 |
20070135143 | Butler et al. | Jun 2007 | A1 |
20090175235 | Spinar | Jul 2009 | A1 |
20090274086 | Petrovic et al. | Nov 2009 | A1 |
20170230936 | Stanwood | Aug 2017 | A1 |
20180098221 | Zimmerman | Apr 2018 | A1 |
Number | Date | Country |
---|---|---|
101127556 | Feb 2008 | CN |
2 028 868 | Feb 2009 | EP |
2 343 340 | Apr 2001 | GB |
100281096 | Nov 2000 | KR |
2001-0075225 | Aug 2001 | KR |
9519079 | Jul 1995 | WO |
98028867 | Jul 1998 | WO |
0158043 | Aug 2001 | WO |
0186837 | Nov 2001 | WO |
Entry |
---|
Duet, “An Assessment of Duplexing Methods for the Radio Links of Personal Communication Systems,” Proceedings of the 1st International Conference on Universal Personal Communications, pp. 131-135 (Sep. 29,-Oct. 1, 1992). |
U-Blox Ag et al., v. Interdigital, Inc. et al., Complaint for: (1) Breach of Contract; (2) Promissory Estoppel; (3) Declaratory Judgment; (4) Antitrust Monopolization in Violation of Section 2 of the Sherman Act; (5) Declaratory Judgment of Non-Infringement of U.S. Pat. No. 8.432, 876; and (6) Declaratory Judgment of Non-Infringment of U.S. Pat. No. 8,953,548, Case No: 18cv2912-AJB-BLM (Jan. 1, 2019). |
Huawei, “Carrier aggregation in Advanced E-UTRA,” 3GPP TSG RAN WG1#53bis, R1-082448, Warsaw, Poland (Jun. 30,-Jul. 4, 2008). |
Lucent Technologies, “Basis for Comparing HS-SCCH Coding Schemes,” 3GPP TSG-RAN WG1#23, R1-01-0071, Korpilampi, Finland (Jan. 8-11, 2002). |
Motorola, “High Speed Downlink Packet Access (HSDPA)—Overall Description,” TSG-RAN Working Group 1 #21, Turin, Italy, TSGR1#22(01)0787 (Aug. 27-31, 2001). |
NTT Docomo, “Initial Access Procedure for Asymmetric Wider Bandwidth in LTE-Advanced,” 3GPP TSG RAN WG1 Meeting #54bis, R1-083680, Prague, Czech Republic (Sep. 29-Oct. 3, 2008). |
Panasonic, “Transport block mapping and PDCCH signaling for carrier aggregation,” 3GPP TSG-RAN WG1 Meeting #54, R1-082995, Jeju, Korea (Aug. 18-22, 2008). |
Qualcomm Europe, “Dual Carrier operation for CELL_DCH,” 3GPP TSG-RAN WG1 #52bis, R1-081438, Shenzhen, China (Mar. 31-Apr. 4, 2008). |
Telecommunications Industry Association, “TIA/EIA Standard, Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems, TlA/ElA-95-B (Upgrade and Revision of TIA/EIA-95-A),” (Mar. 1999). |
Third Generation Partnership Project, “Technical Specification Group GSM/EDGE Radio Access Network; Multiplexing and multiple access on the radio path (Release 5),” 3GPP TS 45.002 V5.7.0 (Nov. 2002). |
Third Generation Partnership Project, “Technical Specification Group Geran; Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path (Release 4),” 3GPP TS 45.002 v4.1.1 (Nov. 2000). |
Third Generation Partnership Project, “Technical Specification Group GSM/EDGE Radio Access Network; Multiplexing and multiple access on the radio path (Release 5),” 3GPP TS 45.002 V5.3.0 (Nov. 2001). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 8),” 3GPP TS 36.331 V8.30 (Sep. 2008). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 8),” 3GPP TS 36.331 V1.0.0 (Nov. 2007). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.7.0 (Sep. 2002). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.3.0 (Dec. 2001). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 5),” 3GPP TS 25.331 V5.2.0 (Sep. 2002). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 7),” 3GPP TS 25.331 V7.5.0 (Jun. 2007). |
European Telecommunications Standards Institute, “Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP 25.331 version 8.0.0 Release 8),” ETSI TS 125 331 V8.0.0 (Jan. 2008). |
Number | Date | Country | |
---|---|---|---|
20190394774 A1 | Dec 2019 | US |
Number | Date | Country | |
---|---|---|---|
60350835 | Jan 2002 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15417831 | Jan 2017 | US |
Child | 16561959 | US | |
Parent | 13867163 | Apr 2013 | US |
Child | 15417831 | US | |
Parent | 12402813 | Mar 2009 | US |
Child | 13867163 | US | |
Parent | 10350308 | Jan 2003 | US |
Child | 12402813 | US |