EP1452052B1 - Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base - Google Patents

Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base Download PDF

Info

Publication number
EP1452052B1
EP1452052B1 EP02780682A EP02780682A EP1452052B1 EP 1452052 B1 EP1452052 B1 EP 1452052B1 EP 02780682 A EP02780682 A EP 02780682A EP 02780682 A EP02780682 A EP 02780682A EP 1452052 B1 EP1452052 B1 EP 1452052B1
Authority
EP
European Patent Office
Prior art keywords
buffer
packet
data
flow indication
indication message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP02780682A
Other languages
German (de)
English (en)
Other versions
EP1452052A1 (fr
Inventor
Sanjay Kamath
Michael A. Kongelf
Leif Woodahl
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to EP09005104A priority Critical patent/EP2083596B1/fr
Publication of EP1452052A1 publication Critical patent/EP1452052A1/fr
Application granted granted Critical
Publication of EP1452052B1 publication Critical patent/EP1452052B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present invention generally relates to the field of wireless communication systems, and more specifically to flow control between a base station controller and a base transceiver station.
  • High Data Rate (“HDR”) technology is a high-speed, high-capacity wireless technology optimized for packet data services. Using a single, data-dedicated 1.25 MHz channel for operation, HDR can deliver data at a peak data rate of 2.4 Mbps, which is significantly faster than many accesses provided over landline networks. Thus, the advantages of HDR include, among others, high-speed data transmission and high spectral efficiency.
  • HDR is the basis for the 1x Evolution Data Only (1xEV-DO) standard, which has been standardized by the Telecommunications Industry Association as TIA/EIA/IS-856.
  • HDR is designed to be interoperable with existing wireless communication systems, for example a code division multiple access (“CDMA") system.
  • CDMA code division multiple access
  • each signal is separated from those of other users by coding the signal.
  • Each user uniquely encodes its information signal into a transmission signal, which is then transmitted over a 1.25 MHz channel.
  • the intended receiver knowing the code sequences of the user, can decode the transmission signal to receive the information.
  • the fact that a CDMA channel is 1.25 MHz simplifies the integration of HDR technology into the present CDMA framework.
  • HDR technology can utilize existing CDMA infrastructure and architecture, including CDMA base station controllers ("BSC") and base transceiver stations ("BTS").
  • BSC base station controllers
  • BTS base transceiver stations
  • data downloaded from the Internet by a user is routed through the BSC to the BTS, which transmits the data to the user via a data-dedicated 1.25 MHz channel or air-link.
  • the BSC packetizes the stream of data it receives into individual 128-byte HDR packets (or "data packets”) before transmitting the data packets to the BTS.
  • the data packets are received by the BTS and placed in a buffer (or "queue") of fixed size to be transmitted to the user using an HDR protocol.
  • One conventional method for flow control between the BSC and the BTS involves the BTS advertising its window size to the BSC at certain, preset, buffer capacity threshold points. For example, when the buffer nears capacity and reaches a preset high watermark threshold, the flow control mechanism is triggered, and the BTS sends a signal informing the BSC to stop transmitting additional data packets so as not to overrun the buffer. Overrunning the buffer can lead to problems such as data packets being dropped and lost at the buffer and having to be retransmitted, leading to less reliable data transmission. Further, having to retransmit dropped or lost data means incurring more overhead and slowing of communication.
  • the flow control mechanism is triggered, and the BTS sends a signal telling the BSC to send more data packets.
  • An empty buffer translates to wasted system resources, because it can result in frames of unused air-link that could be utilized to transmit data from the buffer.
  • a drawback to the conventional flow control mechanism described above is that feedback signals may not be received by the BSC in time to prevent overrunning and/or starving the buffer. For instance, by the time the BSC receives a signal from the BTS to stop sending more data, the BSC may have already put too much data "in flight" to avoid overrunning the buffer, leading to data packets being dropped at the buffer. In the case of an emptying buffer, a signal to send more data may not be received by the BSC in time for it to get data to the buffer before the buffer is completely empty, resulting in wasted air-link frames. Further, a flow control mechanism which is triggered by buffer capacity threshold points may result in the transmission of a high number of feedback signals which puts more strain on the system and increases system overhead.
  • US 2001/0036820 relates to an arrangement for distributed buffer management in a high data rate wireless network.
  • a base station controller supports a centralised buffer and each base station includes a distributed buffer.
  • a mobile station Upon a successful receipt of a block of data, a mobile station transmits a confirmation to the serving base station, wherein the confirmation identifies the block of data received.
  • the serving base station When the sequence number of the block exceeds an initial sequence number by a threshold value, the serving base station notifies the base station controller.
  • the base station controller downloads blocks of data from its centralised buffer to each base station.
  • GB 2 361 392 relates to an arrangement for controlling data flow in a radio access network. Control messages are generated at a node and sent to a radio network controller. Each control message may specify an amount of data which the radio network controller can send to the node, to ensure that the node's buffers do not become too large. Successfully transmitted protocol data units are identified in the control messages using sequence numbers.
  • Embodiments disclosed herein address the above stated needs by tying the flow of data between a base station controller and a base transceiver station directly to the rate of data transmitted from the base transceiver station to a wireless receiving unit such as a mobile unit.
  • a flow indication counter responsible for tracking the rate of data flowing out of a buffer at a base transceiver station is incremented each time a data packet is transmitted from the buffer. For example, the updated number of data packets transmitted from the buffer is compared to a threshold number which can be fifty. When the updated number of packets transmitted equals or exceeds the threshold number, the buffer window size is determined, and a flow indication message comprising the buffer window size is generated and transmitted to the base station controller.
  • the buffer window size which represents the amount of buffer space available for receiving more data, is used by the base station controller to determine the amount of data to transmit to the base transceiver station.
  • the flow indication message can further comprise a data packet ID of the last data packet received by the buffer, and this data packet ID is used by the base station controller to determine the proper order of data packets to transmit next.
  • a timer keeps track of an elapsed time since the transmission of the last message and triggers the generation and transmission of a flow indication message when the elapsed time equals or exceeds a threshold time interval.
  • the threshold time interval can be, for example, 0.5 seconds. In this manner, the timer ensures that a flow indication message is sent at least every threshold time interval independently of the number of data packets transmitted from the buffer.
  • a system for flow control can be constructed comprising a flow indication counter module configured to provide an updated number of data packets transmitted from a buffer at a base station.
  • the system can further comprise a window size monitoring module which determines the buffer window size when the updated number of data packets transmitted from the buffer equals or exceeds a threshold number.
  • the threshold number can be set at fifty.
  • the buffer window size is used by a message generating module which generates a flow indication message comprising the window size. Subsequently, the flow indication message is transmitted to a base station controller which uses the buffer window size to determine the amount of data to transmit to the base transceiver station.
  • FIG. 1 is a block diagram of an exemplary wireless communication system in accordance with one embodiment of the invention.
  • FIG. 2 is an illustrative representation of a buffer used to illustrate example Implementations of the invention.
  • FIG. 3 is a block diagram of a flow control module in accordance with one embodiment of the invention.
  • FIG. 4 is a flowchart of a process for flow control between a base station controller and a base transceiver station in accordance with one embodiment of the invention.
  • the present invention is directed to a method and system for flow control between a base station controller and a base transceiver station.
  • FIG. 1 illustrates an exemplary wireless communication system in accordance with one embodiment.
  • Exemplary wireless communication system 100 shown in FIG. 1 can comprise, for example, part of a code division multiple access (“CDMA") communication system configured to be interoperable with High Data Rate (“HDR”) technology.
  • CDMA code division multiple access
  • HDR High Data Rate
  • CDMA communication systems and in particular the general principles for generation of spread spectrum signals for transmission over a communication channel is described in U.S. patent 4,901,307 entitled "Spread Spectrum Multiple Access Communication System Using Satellite or Terrestrial Repeaters" and assigned to the assignee of the present invention.
  • U.S. patent 4,901,307 entitled "Spread Spectrum Multiple Access Communication System Using Satellite or Terrestrial Repeaters" and assigned to the assignee of the present invention.
  • patent 5,103,459 entitled “System and Method for Generating Signal Waveforms in a CDMA Cellular Telephone System” and assigned to the assignee of the present invention discloses principles related to PN spreading, Walsh covering, and techniques to generate CDMA spread spectrum communication signals. Further, the present invention utilizes time multiplexing of data and various principles related to "high data rate” communication systems, and the present invention can be used in "high data rate” communication systems, such as that disclosed in U.S. patent application entitled “Method and Apparatus for High Rate Packet Data Transmission” Serial No. 08/963,386 filed on November 3, 1997 , and assigned to the assignee of the present invention.
  • exemplary wireless communication system 100 comprises components generally found in wireless communication systems, including a wireless receiving unit such as mobile unit 110, base transceiver station (“BTS”) 116, base station controller (“BSC”) 122, "internet” 124, and data server 126.
  • Mobile unit 110 and BTS 116 further comprise, respectively, antenna 112 and antenna 114.
  • BTS 116 serves as a radio link between mobile unit 110 and the rest of the system.
  • wireless communication systems may comprise other components such as a mobile switching center and a public switched telephone network which are not shown in any of the FIG.s in order to not obscure the invention.
  • Exemplary wireless communication system 100 illustrates how Internet data can be communicated to mobile unit 110 by being routed from data server 126 through Internet 124 and BSC 122, and to BTS 116 which transmits the data to mobile unit 110 via, for example, a 1.25 MHz air-link channel.
  • Data server 126 can be, for example, an HTTP or FTP server.
  • the Internet data can be transmitted from BTS 116 to mobile unit 110 using an HDR protocol.
  • BTS 116 further comprises buffer 118 and flow control module 120.
  • data received at BSC 122 is packetized into discrete 128-byte HDR data packets before being sent to BTS 116.
  • BTS 116 receives the 128-byte data packets and places the data packets in buffer 118.
  • Buffer 118 which is of a fixed-size, is used for temporarily storing the data for processing, or, in a streaming media application, to compensate for any delays in the arrival of related data packets, prior to transmission of the data packets to mobile unit 110.
  • a base transceiver station such as BTS 116 can include several buffers, for example transmit, retransmit and signaling buffers, and that each type of buffer is configured to receive and process different types of data for transmission to various wireless receiver units.
  • flow control module 120 monitors the rate of data "flowing out" of buffer 118. For example, flow control module 120 can count the number of data packets transmitted from buffer 118 to mobile unit 110. At the same time, flow control module 120 also monitors the window size of buffer 118, which is the amount of unoccupied space available at buffer 118 for receiving more data from BSC 122.
  • flow control module 120 utilizes the number of data packets transmitted from buffer 118 to determine an appropriate time to send feedback to BSC 122. It is noted that the feedback sent from flow control module 120 to BSC 122 is also referred to as a "flow indication message" in the present application. As an example, flow control module 120 can be configured to send a flow indication message after the transmission of every fifty data packets from buffer 118. However, it is apparent to a person of ordinary skill in the art that the threshold number of data packets transmitted from buffer 118 needed to trigger the transmission of a flow indication message can be set to some number other than fifty, depending on the requirements and resources of the system.
  • the flow indication message advertises to BSC 122 how much data should be transmitted to buffer 118, based on the window size of buffer 118. In this manner, the control of how much data BSC 122 transmits to BTS 116 is based on how quickly data is transmitted from buffer 118.
  • FIG. 1 illustrates a wireless communication system wherein the flow control between the BSC and the BTS is directly tied to how fast data is being transmitted from the buffer.
  • FIG. 2 shows an exemplary buffer used to illustrate one embodiment.
  • Exemplary buffer 200 shown in FIG. 2 constitutes part of a base transceiver station in a wireless communication system such as a CDMA system configured to be interoperable with HDR technology, as described in FIG. 1 .
  • Buffer 200 can correspond, for example, to buffer 118 of base transceiver station 116 of wireless communication system 100 in FIG. 1 .
  • Buffer 200 can be a transmit buffer, for example, configured to queue bulk Internet data prior to transmission of the data to a wireless mobile unit, such as mobile unit 110 in FIG. 1 .
  • buffer 200 has a fixed size or data capacity (i.e. buffer size 206), which can be, for example, approximately 50 Kbytes for a typical transmit buffer. Further, buffer 200 comprises data 208 with data size 210, which represents the amount of data queued at buffer 200 for transmission to wireless mobile units, and window 212 with window size 214, which represents the unused space available for receiving more data at buffer 200.
  • the relative sizes of data 208 and window 212 are a function of the rate of data flow through buffer 200.
  • data flows into buffer 200 from a base station controller as shown by arrow 202, and flows out of buffer 200 to a wireless access terminal, such as a mobile unit, as shown by arrow 204.
  • a wireless access terminal such as a mobile unit
  • data packet 216 data packet 216.
  • a typical 50 Kbyte transmit buffer can queue approximately 400 data packets, and a wireless communication system utilizing HDR technology operating at a peak data rate of 2.4 Megabits/second can transmit approximately 2,400 data packets each second.
  • data packet 216 constitutes one of a plurality of similarly packetized data packets of data 208 queued in buffer 200.
  • Data packet 216 is enlarged in FIG. 2 to facilitate further discussion.
  • data packet 216 comprises data, i.e. data 218 and a packet ID, i.e. packet ID 220.
  • Packet ID 220 is an identification tag "stamped" on data 218 by the base station controller and is unique to data packet 216. Packet ID 220 can be used, for example, to track the movement of data packet 216 as it moves through the communication system in a manner known in the art.
  • the unique packet ID of the last data packet received by the buffer i.e. the data packet received most recently, is included in the flow indication message transmitted to the base station controller.
  • the packet ID of the data packet received most recently is also referred to as a "least packet ID" in the present application.
  • the flow indication message is transmitted after a threshold number of data packets have been transmitted from the buffer.
  • the flow indication message can also comprise the buffer window size in addition to the last packet ID.
  • the base station controller can utilize the information in such a flow indication message to determine not only how much data to send to the base transceiver station based on the buffer window size, but also the correct sequence of data packets to send next based on the last packet ID. In this manner, the flow of data from the base station controller to the base transceiver station is regulated by both the buffer window size and the identification of the last data packet received by the buffer.
  • FIG. 2 shows an exemplary buffer used to illustrate one embodiment wherein the buffer window size and the packet ID of the last data packet received by the buffer are included in a flow indication message to refine the flow control between the BSC and the BTS.
  • FIG. 3 illustrates an exemplary flow control module in accordance with one embodiment.
  • Flow control module 300 shown in FIG. 3 constitutes part of a base transceiver station in a wireless communication system, for example a CDMA system configured to be interoperable with HDR technology.
  • Flow control module 300 can correspond, for example, to flow control module 120 in base transceiver station 116 of wireless communication system 100 in FIG. 1 .
  • Flow control module 300 comprises flow indication counter module 302, data packet ID monitoring module 304, window size monitoring module 306, timer 308, and message generating module 310.
  • the flow of information into, between, and from the modules is indicated in the block diagram of FIG. 3 by arrows which also indicate the direction of information flow.
  • flow indication counter module 302 monitors the flow of data transmitted from a buffer which can be, for example, a transmit buffer such as buffer 200 in FIG. 2 , which in turn corresponds to buffer 118 in FIG. 1 .
  • flow indication counter module 302 keeps an updated count of the number of data packets transmitted from the buffer and compares the updated count to a threshold number.
  • the threshold number can be fifty, but can alternatively be some other value, depending on the requirements and resources of the system.
  • flow indication counter module 302 sends a signal to message generating module 310, triggering message generating module 310 to generate a flow indication message.
  • flow indication counter module 302 is responsible for keeping track of the flow of data out of the buffer and for triggering the flow control mechanism when the number of data packets transmitted from the buffer equals or exceeds a threshold number.
  • data packet ID monitoring module 304 also receives information from the buffer.
  • Data packet ID monitoring module 304 monitors the reception of each data packet by the buffer and reads the packet ID of the data packets. Using FIG. 2 for illustrative purposes, data packet ID monitoring module 304 can read packet ID 220 corresponding to data packet 216 as data packet 216 is received by buffer 200. The packet ID of each subsequent data packet received by the buffer is similarly read by packet ID monitoring module 304.
  • Data packet ID monitoring module 304 provides message generating module 310 with the packet ID of the data packet received most recently by the buffer. Message generating module 310 can store the packet ID of the data packet received most recently for subsequent processing.
  • window size monitoring module 306 is configured to monitor the window size of the buffer.
  • the window size which represents the amount of buffer space available for receiving additional data, is directly proportional to the rate of data flowing into and out of the buffer.
  • An example of a window size in a buffer was shown as window size 214 in buffer 200 in FIG. 2 .
  • the window size such as window size 214, is reduced as the buffer receives more data packets from the base station controller, and conversely, the window size is increased as data packets are transmitted from the buffer to wireless access terminals or wireless mobile units.
  • Window size monitoring module 306 monitors the buffer window size and provides message generating module 310 with the window size.
  • message generating module 310 The information received by message generating module 310 from flow indication counter module 302, data packet ID monitoring module 304 and window size monitoring module 306, is utilized by message generating module 310 to generate a flow indication message.
  • Message generating module 310 is triggered by flow indication counter module 302 when a threshold number of data packets has been transmitted from the buffer. Once triggered, message generating module 310 generates a flow indication message comprising the buffer window size and the packet ID of the data packet received most recently by the buffer.
  • the flow indication message is then transmitted to the base station controller which utilizes the information, i.e. the buffer window size and the packet ID, to determine how much data it can transmit to the buffer and which data packet should be transmitted next. Transmission of the flow indication message can be performed, for example, by a transmit module at the base station. It is noted that the base station transmit module is not shown in any of the FIG.s. Further, message generating module 310 notifies flow indication counter module 302 each time a flow indication message is transmitted so that flow indication counter module 302 can reset the updated number of data packets transmitted from the buffer to zero. By tying the flow control mechanism directly to the rate of data flowing out of the buffer, the present embodiment provides a more reliable method for flow control than conventional flow control methods. Further, the possibility of overrunning the buffer is reduced because the base station controller receives information on the rate of data leaving the buffer and can adjust the amount of data it sends to the buffer accordingly.
  • the base station controller receives information on the rate of data leaving the buffer and can adjust the amount of data it sends to the buffer
  • message generating module 310 is triggered to generate and transmit a flow indication message after a threshold time interval has elapsed since the transmission of a last flow indication message, even if the threshold number of data packets transmitted from the buffer has not been reached, i.e. even if flow indication counter module 302 does not trigger message generating module 310.
  • Timer 308 in flow control module 300 keeps track of the elapsed time between flow indication messages sent from message generating module 310. If a threshold time interval elapses without a flow indication message being sent, timer 308 triggers message generating module 310 to generate and transmit a flow indication message.
  • the threshold time interval can be 0.5 seconds.
  • the flow indication message can comprise information message generating module 310 receives from data packet ID monitoring module 304, i.e. the last packet ID, and window size monitoring module 306, i.e. the buffer window size. Thus, timer 308 triggers message generating module 310 to send a flow indication message independently of the number of data packets transmitted from the buffer.
  • timer 308 is important in situations where the buffer has space available for receiving more data but the base station controller is not transmitting any data. This situation can occur, for instance, when flow indication messages notifying the base station controller of available buffer space are lost or dropped at the base station controller - the base station controller is, in effect, not aware that the buffer can receive more data. Consequently, once the buffer is emptied of data and additional data packets are not received form the base station controller, the flow control mechanism could become "gridlocked" since no data packet is being transmitted from the buffer to trigger the flow control mechanism. In other words, flow indication counter module 302 would not trigger message generating module 310 since the threshold number of data packets transmitted needed would not be reached.
  • timer 308 triggers message generating module 310 independently of the number of data packets transmitted from the buffer, timer 308 ensures that flow indication messages are sent even if the buffer is empty and no data packet is being transmitted from the buffer. In this manner, gridlock of the flow control mechanism is prevented. Further, because a flow indication message is sent at least every preset time interval, the possibility of starving the buffer is greatly reduced.
  • FIG. 3 illustrates an exemplary flow control module which generates and transmits flow indication messages after a threshold number of data packets has been transmitted from a buffer in accordance with one embodiment. Further, FIG. 3 illustrates a safeguard component that triggers the generation and transmission of flow indication messages independently of the number of data packets transmitted from the buffer.
  • FIG. 4 shows flowchart 400 describing an exemplary process for flow control between a base station controller and a base transceiver in accordance with one embodiment.
  • Flowchart 400 shown in FIG. 4 describes a process which can be performed at a base transceiver station in a wireless communication system, for example a CDMA system configured to be interoperable with HDR technology.
  • the process shown in flowchart 400 can be performed by a flow control module such as flow control module 300 in FIG. 3 .
  • flow control module 300 such as flow control module 300 in FIG. 3
  • the process shown in flowchart 400 will be described in the context of flow control module 300 in FIG. 3 .
  • the flow control process begins when a connection is made between a base station controller and a base transceiver station in which a flow control module such as flow control module 300 is housed.
  • a flow indication message is transmitted to the base station controller.
  • the flow indication message can be transmitted by message generating module 310 and can comprise the window size of a buffer at the base transceiver station.
  • the buffer can be a transmit buffer such as buffer 118 in FIG. 1 .
  • the purpose of sending this initial flow indication message is to advertise to the base station controller the amount of buffer space available for receiving data.
  • a threshold time interval has elapsed since the last flow indication message was sent.
  • the threshold time interval which can be 0.5 seconds, for example, is also referred to as "time T" in the present application. Tracking of the elapsed time can be performed by a timer such as timer 308 in flow control module 300 in a manner known in the art.
  • step 404 it is determined whether or not a new or "next" data packet has been transmitted from the buffer. This determination can be performed by software in a flow indication counter module such as flow indication counter module 302. When a next data packet has not been transmitted, then the process returns to step 404 to determine again whether time T has elapsed since the last flow indication message was sent. In this manner, i.e. looping back to step 404 when a next data packet has not been transmitted from the buffer, a safeguard mechanism is available to make certain that flow indication messages will be sent at least every time T.
  • step 406 If it is determined at step 406 that a next data packet has been sent, then the process proceeds to step 408, and the flow indication counter, such as flow indication counter module 302, is incremented to update the number of data packets transmitted from the buffer.
  • the updated number of data packets transmitted from the buffer can be stored in a memory device in the flow indication module.
  • the updated number of data packets transmitted from the buffer is compared to a threshold number of data packets transmitted.
  • the threshold number of data packet transmitted which can be set at 50, for example, is also referred to as a "threshold number" in the present application. Comparison of the updated number of data packets transmitted with the threshold number can be performed, for example, by software in flow indication counter 302.
  • the process returns to step 404. By looping back to step 404 when the updated number of data packets transmitted is less than the threshold number, the process makes certain that flow indication messages are sent at least every time T, even when the flow of data out of the buffer is relatively slow, and the time interval before the threshold number is reached is increased.
  • a flow indication message is generated and sent to the base station controller.
  • the flow indication message can comprise the buffer window size and the packet ID of the last data packet received by the buffer, i.e. last packet ID.
  • the flow indication message can be generated and sent by message generating module 310 which receives the buffer window size from window size monitoring module 306 and the last packet ID from packet ID monitoring module 304.
  • the steps of generating and transmitting the flow indication message to the base station controller are also referred to as "advertising" in the present application.
  • the flow indication message advertises the information to the base station controller which uses the information to determine how much data to transmit to the buffer, as well as the proper sequence of data packets to transmit next.
  • FIG. 4 shows an example process for flow control between a base station controller and a base transceiver station in accordance with one embodiment.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two.
  • the software module also called a computer program in the present application, may contain a number of source code or object code segments and may reside in any computer readable medium such as a RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, a DVD-ROM or any other form of computer readable medium known in the art.
  • An exemplary computer readable medium is coupled to the processor where the processor can read information from, and write information to, the computer readable medium.
  • the computer readable medium may be integral to the processor.
  • the processor and the computer readable medium may reside in an Application Specific Integrated Circuit ("ASIC").
  • the processor and the computer readable medium may reside in a flow control module.
  • the processor and the computer readable medium may reside as discrete components in the flow control module

Abstract

Dans un mode de réalisation, un compteur d'indication de flux subit une incrémentation à chaque fois qu'un paquet de données est transmis d'une mémoire tampon (408). Lorsque le nombre de paquets de données transmis atteint une valeur égale ou supérieure à un nombre seuil (410), un message d'indication de flux contenant la taille de la fenêtre tampon est élaboré et transmis à l'unité de commande de station de base (412). Par ailleurs, les messages d'indication de flux peuvent être élaborés et transmis à chaque d'intervalle de temps seuil, indépendamment du nombre de paquets de données transmis, en vue de garantir la transmission des messages d'indication de flux au moins à chaque intervalle de temps préréglé. L'invention permet également de mettre au point un système de commande de flux doté d'un module de compteur d'indication de flux (302) qui permet de fournir le nombre à jour des paquets de données transmis. Ce système comprend également un module de surveillance de la taille de la fenêtre (306) qui détermine la taille de la fenêtre tampon, et un module d'élaboration de messages qui élabore un message d'indication de flux contenant la taille de la fenêtre tampon (310).

Claims (21)

  1. Procédé de commande de flux entre un contrôleur de station de base (122) et une station émettrice-réceptrice de base (116), caractérisé par:
    l'incrémentation (408) d'un compteur d'indication de flux indiquant un nombre mis à jour de paquets de données transmis depuis un tampon (118);
    lorsque le nombre mis à jour de paquets de données transmis depuis ledit tampon (118) est supérieur ou égal à un nombre seuil:
    la détermination d'une taille de fenêtre (214) dudit tampon (118); et
    la génération (412) d'un message d'indication de flux, ledit message d'indication de flux indiquant ladite taille de fenêtre (214);
    le suivi (404) d'un temps écoulé depuis la transmission du message d'indication de flux; et
    la génération (412) d'un autre message d'indication de flux lorsque ledit temps écoulé est supérieur ou égal à un intervalle de temps de seuil.
  2. Procédé selon la revendication 1, comprenant en outre:
    la détermination d'un identifiant de paquet (220) d'un paquet de données (216) reçu par ledit tampon (118) avant ladite génération.
  3. Procédé selon la revendication 2, dans lequel ledit identifiant de paquet (220) est un identifiant de dernier paquet.
  4. Procédé selon la revendication 2, dans lequel ledit message d'indication de flux comprend en outre ledit identifiant de paquet (220).
  5. Procédé selon la revendication 1 ou 4, comprenant en outre:
    la transmission dudit message d'indication de flux.
  6. Procédé selon la revendication 1, comprenant en outre:
    la détermination d'un identifiant de paquet (220) d'un paquet de données (216) reçu par ledit tampon (118); et
    la transmission dudit message d'indication de flux, dans lequel:
    ledit message d'indication de flux comprend ladite taille de fenêtre (214).
  7. Procédé selon la revendication 6, dans lequel ledit identifiant de paquet (220) est un identifiant de dernier paquet.
  8. Procédé selon la revendication 7, dans lequel ledit message d'indication de flux comprend en outre ledit identifiant de paquet (220).
  9. Procédé selon la revendication 1, comprenant en outre:
    la réception d'une pluralité de paquets de données provenant d'un contrôleur de station de base (122);
    le placement de ladite pluralité de paquets de données dans le tampon (118);
    la transmission d'un certain nombre de ladite pluralité de paquets de données à partir dudit tampon;
    la détermination d'un identifiant de paquet (220) de l'un de ladite pluralité de paquets de données; et
    la transmission dudit message d'indication de flux audit contrôleur de station de base (122),
    dans lequel ledit message d'indication de flux comprend en outre ledit identifiant de paquet.
  10. Procédé selon la revendication 1, 6 ou 9, dans lequel ledit nombre seuil est de cinquante.
  11. Procédé selon la revendication 9, dans lequel ledit identifiant de paquet (220) est un identifiant de dernier paquet.
  12. Procédé selon la revendication 9, comprenant en outre:
    le suivi d'un temps écoulé depuis la transmission d'un dernier message;
    l'annonce de ladite taille de fenêtre (214) lorsque ledit temps écoulé est supérieur ou égal à un intervalle de temps de seuil.
  13. Procédé selon la revendication 1 ou 12, dans lequel ledit intervalle de temps de seuil est de 0,5 seconde.
  14. Support lisible par ordinateur comprenant des instructions qui, lorsqu'elles sont exécutées par un ordinateur approprié, amènent l'ordinateur à exécuter le procédé de l'une quelconque des revendications précédentes.
  15. Système de commande de flux entre un contrôleur de station de base (122) et une station émettrice-réceptrice de base (116), caractérisé par:
    un moyen (302) pour incrémenter un compteur d'indication de flux indiquant un nombre mis à jour de paquets de données transmis depuis un tampon (118);
    un moyen (306) pour déterminer une taille de fenêtre (214) dudit tampon (118) lorsque ledit nombre mis à jour de paquets de données transmis depuis ledit tampon (118) est supérieur ou égal à un nombre seuil;
    un moyen (310) pour générer un message d'indication de flux, ledit message d'indication de flux comprenant ladite taille de fenêtre (214); et
    un moyen (308) pour suivre un temps écoulé depuis la transmission d'un dernier message d'indication de flux,
    dans lequel ledit moyen (310) pour générer un message d'indication de flux est utilisable pour générer un autre message d'indication de flux lorsque ledit temps écoulé est supérieur ou égal à un intervalle de temps de seuil.
  16. Système selon la revendication 15, dans lequel ledit nombre seuil est de cinquante.
  17. Système selon la revendication 15, comprenant en outre:
    un moyen (304) pour déterminer un identifiant de paquet (220) d'un paquet de données (216) reçu par ledit tampon.
  18. Système selon la revendication 17, dans lequel ledit identifiant de paquet (220) est un identifiant de dernier paquet.
  19. Système selon la revendication 17, dans lequel ledit message d'indication de flux comprend en outre ledit identifiant de paquet (220).
  20. Système selon la revendication 15 ou 19, comprenant en outre:
    un moyen pour transmettre ledit message d'indication de flux.
  21. Système selon la revendication 15, dans lequel ledit intervalle de temps de seuil est de 0,5 seconde.
EP02780682A 2001-12-05 2002-11-12 Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base Expired - Lifetime EP1452052B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP09005104A EP2083596B1 (fr) 2001-12-05 2002-11-12 Procédé et système de contrôle de débit entre un contrôleur de station de base et une station d'émetteur-récepteur de base

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10990 2001-12-05
US10/010,990 US7237007B2 (en) 2001-12-05 2001-12-05 Method and system for flow control between a base station controller and a base transceiver station
PCT/US2002/036642 WO2003051078A1 (fr) 2001-12-05 2002-11-12 Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP09005104A Division EP2083596B1 (fr) 2001-12-05 2002-11-12 Procédé et système de contrôle de débit entre un contrôleur de station de base et une station d'émetteur-récepteur de base

Publications (2)

Publication Number Publication Date
EP1452052A1 EP1452052A1 (fr) 2004-09-01
EP1452052B1 true EP1452052B1 (fr) 2009-07-15

Family

ID=21748378

Family Applications (2)

Application Number Title Priority Date Filing Date
EP09005104A Expired - Lifetime EP2083596B1 (fr) 2001-12-05 2002-11-12 Procédé et système de contrôle de débit entre un contrôleur de station de base et une station d'émetteur-récepteur de base
EP02780682A Expired - Lifetime EP1452052B1 (fr) 2001-12-05 2002-11-12 Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP09005104A Expired - Lifetime EP2083596B1 (fr) 2001-12-05 2002-11-12 Procédé et système de contrôle de débit entre un contrôleur de station de base et une station d'émetteur-récepteur de base

Country Status (16)

Country Link
US (2) US7237007B2 (fr)
EP (2) EP2083596B1 (fr)
JP (2) JP2005512475A (fr)
KR (1) KR100971102B1 (fr)
CN (2) CN102497653B (fr)
AU (1) AU2002343721A1 (fr)
BR (1) BR0214692A (fr)
CA (1) CA2468939A1 (fr)
DE (1) DE60232990D1 (fr)
IL (1) IL162360A0 (fr)
MX (1) MXPA04005440A (fr)
NO (1) NO20042795L (fr)
RU (1) RU2298881C2 (fr)
TW (1) TWI298228B (fr)
UA (1) UA80102C2 (fr)
WO (1) WO2003051078A1 (fr)

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7237007B2 (en) * 2001-12-05 2007-06-26 Qualcomm Incorporated Method and system for flow control between a base station controller and a base transceiver station
US7289509B2 (en) * 2002-02-14 2007-10-30 International Business Machines Corporation Apparatus and method of splitting a data stream over multiple transport control protocol/internet protocol (TCP/IP) connections
JP3629008B2 (ja) * 2002-04-19 2005-03-16 松下電器産業株式会社 データ受信装置及びデータ配信システム
TWI540863B (zh) * 2002-05-10 2016-07-01 無線創新信號信託公司 以容量分佈為基礎之認識流控制
DE10224994A1 (de) * 2002-06-05 2003-12-18 Siemens Ag Verfahren und System zum Übertragen von Datenpaketen
EP1383281A1 (fr) * 2002-07-19 2004-01-21 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Méthode pour le calcul de la taille d'une fenêtre de transmission
US7190670B2 (en) * 2002-10-04 2007-03-13 Nokia Corporation Method and apparatus for multimedia streaming in a limited bandwidth network with a bottleneck link
US7961617B2 (en) * 2002-10-29 2011-06-14 Telefonaktiebolaget Lm Ericsson (Publ) System and method for wireless network congestion control
US8407358B1 (en) * 2002-12-18 2013-03-26 Intel Corporation Buffer management for streaming data
CN100539542C (zh) * 2002-12-20 2009-09-09 国际商业机器公司 无线自组织网络中的最大生存时间路由
US7606928B2 (en) * 2003-03-21 2009-10-20 Nokia Corporation Method and device for controlling receiver buffer fullness level in multimedia streaming
US7603475B2 (en) * 2003-03-31 2009-10-13 Alcatel-Lucent Usa Inc. Method for flow control in a communication system
US8977763B1 (en) * 2003-04-25 2015-03-10 Aol Inc. Systems and methods for distributing streams and stream metadata
US20070115815A1 (en) * 2003-06-11 2007-05-24 Nec Corporation Receiver, transmitter and transmission/reception system for media signal
KR20050012064A (ko) * 2003-07-24 2005-01-31 유티스타콤코리아 유한회사 이브이-디오 시스템에서 제어국과 기지국간 에이티엠트래픽 채널 패스 설정 방법
CN100531433C (zh) * 2003-08-08 2009-08-19 三菱电机株式会社 通信终端和通信系统
KR100604597B1 (ko) * 2004-02-20 2006-07-24 주식회사 팬택앤큐리텔 이동 통신 단말기
US7821940B2 (en) * 2004-04-05 2010-10-26 Alcatel-Lucent Usa Inc. Transmission of maintenance information of an active packet connection through employment of packets communicated over the active packet connection
JPWO2006006208A1 (ja) * 2004-07-08 2008-04-24 三菱電機株式会社 無線基地局
US7590064B1 (en) * 2004-07-20 2009-09-15 Nortel Networks Limited Method and system of flow control in multi-hop wireless access networks
US8255598B2 (en) * 2004-12-22 2012-08-28 Bank Of America Corporation Method and apparatus for managing item sequence numbers in an item processing system
JP4643330B2 (ja) * 2005-03-28 2011-03-02 ソニー株式会社 通信処理装置、データ通信システム、および通信処理方法、並びにコンピュータ・プログラム
DE102005058878B4 (de) * 2005-12-09 2007-08-09 Infineon Technologies Ag Datentransfervorrichtung und Verfahren zum Senden von Daten
US7965633B2 (en) * 2005-12-12 2011-06-21 Alcatel-Lucent Usa Inc. Method of downlink rate control
CN100459586C (zh) * 2006-08-25 2009-02-04 华为技术有限公司 数据流量控制装置与流量控制方法
US8954045B2 (en) * 2006-09-29 2015-02-10 Qualcomm Incorporated Method and apparatus for managing resources at a wireless device
JP4901681B2 (ja) * 2007-10-05 2012-03-21 株式会社東芝 無線通信装置及び無線通信方法
US20090094358A1 (en) * 2007-10-05 2009-04-09 Davis Gregg A Data Bridge Maintenance Utilizing Data Traffic Log Change
FR2923118B1 (fr) * 2007-10-30 2016-04-01 Canon Kk Procede, dispositif et programme d'ordinateur pour la gestion de la quantite de donnees emises par un dispositif d'emission
US7773519B2 (en) * 2008-01-10 2010-08-10 Nuova Systems, Inc. Method and system to manage network traffic congestion
US20090238070A1 (en) * 2008-03-20 2009-09-24 Nuova Systems, Inc. Method and system to adjust cn control loop parameters at a congestion point
US8325687B2 (en) * 2008-05-09 2012-12-04 Qualcomm Incorporated Techniques for enhanced backhaul flow control
CN101471876B (zh) * 2008-07-16 2010-07-07 华为技术有限公司 一种实现分组微波数据流量整形的方法、装置和系统
WO2010008252A2 (fr) * 2008-07-18 2010-01-21 Lg Electronics Inc. Appareil pour gérer une ressource et procédé associé
US8599734B1 (en) * 2008-09-30 2013-12-03 Meru Networks TCP proxy acknowledgements
US7817655B1 (en) * 2008-10-30 2010-10-19 Xilinx, Inc. Determining sizes of FIFO buffers between functional blocks in an electronic circuit
CN101404811B (zh) * 2008-11-17 2010-12-08 中兴通讯股份有限公司 一种小区短信的流量控制方法及系统
WO2010117358A1 (fr) * 2009-04-07 2010-10-14 Cisco Technology, Inc. Procédé et système pour gérer un encombrement de trafic de réseau
US9391853B2 (en) 2009-12-23 2016-07-12 Apple Inc. Efficient service advertisement and discovery in a peer-to-peer networking environment with dynamic advertisement and discovery periods based on operating conditions
US20110283014A1 (en) * 2010-05-14 2011-11-17 Rahul Malik Distribution of Multimedia Content over a Network
US8693355B2 (en) * 2010-06-21 2014-04-08 Motorola Solutions, Inc. Jitter buffer management for power savings in a wireless communication device
US8660132B2 (en) * 2010-06-28 2014-02-25 Avaya Inc. Control plane packet processing and latency control
US8964562B2 (en) * 2012-12-31 2015-02-24 Verizon Patent And Licensing Inc. Flow control methods and systems for use with a wireless network
EP3066801A1 (fr) * 2013-11-06 2016-09-14 Calgary Scientific Inc. Appareil et procédé pour commande de flux côté client dans un environnement d'accès à distance
US20150256577A1 (en) * 2014-03-05 2015-09-10 Nicepeopleatwork S.L. Directing Fragmented Content
JP6208870B2 (ja) * 2014-07-11 2017-10-04 株式会社日立製作所 ストレージシステム、記憶制御方法及び中継装置
KR102176653B1 (ko) * 2014-09-04 2020-11-09 삼성전자주식회사 무선 통신 시스템에서 전송 제어를 위한 방법 및 장치
JP2017027196A (ja) * 2015-07-17 2017-02-02 株式会社リコー 通信装置、電力制御方法、及び電力制御プログラム
ES2781782T3 (es) * 2016-04-11 2020-09-07 Nokia Technologies Oy Gestión de flujo de sub-servicio accionado por aplicación de QoS/QoE en sistema 5G
US11805034B1 (en) 2016-12-07 2023-10-31 Reservoir Labs, Inc. Systems and methods for detecting large network flows
CN110391991B (zh) 2018-04-18 2022-04-29 华为技术有限公司 一种流量控制的方法及相关装置
CN112019447A (zh) * 2020-08-19 2020-12-01 博锐尚格科技股份有限公司 数据流量控制方法、装置、系统、电子设备、及存储介质
US11720424B2 (en) * 2021-03-12 2023-08-08 Salesforce, Inc. Single flow execution
WO2024020732A1 (fr) * 2022-07-25 2024-02-01 Apple Inc. Planification adaptative basée sur l'écoute vocale

Family Cites Families (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4901307A (en) * 1986-10-17 1990-02-13 Qualcomm, Inc. Spread spectrum multiple access communication system using satellite or terrestrial repeaters
US4843264A (en) * 1987-11-25 1989-06-27 Visic, Inc. Dynamic sense amplifier for CMOS static RAM
US5193151A (en) * 1989-08-30 1993-03-09 Digital Equipment Corporation Delay-based congestion avoidance in computer networks
US5063562A (en) * 1990-05-23 1991-11-05 International Business Machines Corporation Flow control for high speed networks
US5103459B1 (en) * 1990-06-25 1999-07-06 Qualcomm Inc System and method for generating signal waveforms in a cdma cellular telephone system
JPH077975B2 (ja) * 1990-08-20 1995-01-30 インターナショナル・ビジネス・マシーンズ・コーポレイション データ伝送を制御するためのシステムおよび方法
US5197127A (en) * 1990-09-24 1993-03-23 International Business Machines Corporation Expert system method for performing window protocol-based data flow analysis within a data communication network
US5696903A (en) * 1993-05-11 1997-12-09 Norand Corporation Hierarchical communications system using microlink, data rate switching, frequency hopping and vehicular local area networking
US5581703A (en) * 1993-06-29 1996-12-03 International Business Machines Corporation Method and apparatus for reserving system resources to assure quality of service
US5592627A (en) * 1994-10-11 1997-01-07 Emprise Technologies, L.P. Pipelined, sliding-window, flow control for end-to-end communication sessions
US5695864A (en) * 1995-09-28 1997-12-09 International Business Machines Corporation Electronic device using magnetic components
US5933603A (en) * 1995-10-27 1999-08-03 Emc Corporation Video file server maintaining sliding windows of a video data set in random access memories of stream server computers for immediate video-on-demand service beginning at any specified location
US5784559A (en) 1995-11-06 1998-07-21 Sun Microsystems, Inc. Full duplex flow control for ethernet networks
US5748901A (en) * 1996-05-21 1998-05-05 Ramot University Authority Ltd. Flow control algorithm for high speed networks
US5862337A (en) * 1996-07-12 1999-01-19 Microsoft Corporation Determining throughput dynamically
US6038216A (en) * 1996-11-01 2000-03-14 Packeteer, Inc. Method for explicit data rate control in a packet communication environment without data rate supervision
US5913041A (en) * 1996-12-09 1999-06-15 Hewlett-Packard Company System for determining data transfer rates in accordance with log information relates to history of data transfer activities that independently stored in content servers
US5974518A (en) * 1997-04-10 1999-10-26 Milgo Solutions, Inc. Smart buffer size adaptation apparatus and method
US6076113A (en) * 1997-04-11 2000-06-13 Hewlett-Packard Company Method and system for evaluating user-perceived network performance
US6105064A (en) * 1997-05-30 2000-08-15 Novell, Inc. System for placing packets on network for transmission from sending endnode to receiving endnode at times which are determined by window size and metering interval
US6167027A (en) * 1997-09-09 2000-12-26 Cisco Technology, Inc. Flow control technique for X.25 traffic in a high speed packet switching network
US6058106A (en) * 1997-10-20 2000-05-02 Motorola, Inc. Network protocol method, access point device and peripheral devices for providing for an efficient centrally coordinated peer-to-peer wireless communications network
US6075769A (en) * 1997-11-26 2000-06-13 Cisco Systems, Inc. Method and apparatus for network flow control
JPH11239163A (ja) 1998-02-23 1999-08-31 Nippon Telegr & Teleph Corp <Ntt> Ｌａｎ間フロー制御方法及びスイッチ
US6205120B1 (en) * 1998-03-13 2001-03-20 Packeteer, Inc. Method for transparently determining and setting an optimal minimum required TCP window size
EP0948168A1 (fr) * 1998-03-31 1999-10-06 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Méthode et dispositif pour le contrÔle du flux de données
JP2000216811A (ja) 1999-01-22 2000-08-04 Chokosoku Network Computer Gijutsu Kenkyusho:Kk フロ―制御方法
US6560243B1 (en) * 1999-04-30 2003-05-06 Hewlett-Packard Development Company System and method for receiver based allocation of network bandwidth
US6788704B1 (en) * 1999-08-05 2004-09-07 Intel Corporation Network adapter with TCP windowing support
FR2805112B1 (fr) * 2000-02-11 2002-04-26 Mitsubishi Electric Inf Tech Procede et unite de controle de flux d'une connexion tcp sur un reseau a debit controle
US6674717B1 (en) * 2000-03-30 2004-01-06 Network Physics, Inc. Method for reducing packet loss and increasing internet flow by feedback control
US20010036820A1 (en) * 2000-04-12 2001-11-01 Mo-Han Fong Distributed buffer management in a high data rate wireless network
US6894974B1 (en) * 2000-05-08 2005-05-17 Nortel Networks Limited Method, apparatus, media, and signals for controlling packet transmission rate from a packet source
JP3740953B2 (ja) * 2000-06-13 2006-02-01 株式会社日立製作所 無線位置測定端末および無線位置測定システム
US6928054B1 (en) * 2000-09-20 2005-08-09 Nortel Networks Limited Apparatus, method, media and signals for connection-class parameter control of packet flow
JP2002152308A (ja) * 2000-11-09 2002-05-24 Nec Corp データ通信システム、その通信方法及びその通信プログラムを記録した記録媒体
GB2361392B (en) * 2000-12-13 2003-07-23 Ericsson Telefon Ab L M Flow control in a radio access network
US7142508B2 (en) * 2000-12-22 2006-11-28 Radiance Technologies, Inc. System and method for controlling data transfer rates on a network
US6934256B1 (en) * 2001-01-25 2005-08-23 Cisco Technology, Inc. Method of detecting non-responsive network flows
US7116636B2 (en) * 2001-05-15 2006-10-03 Northrop Grumman Corporation Data rate adjuster using transport latency
US7237007B2 (en) 2001-12-05 2007-06-26 Qualcomm Incorporated Method and system for flow control between a base station controller and a base transceiver station
JP2003348642A (ja) * 2002-05-30 2003-12-05 Yuji Oie 無線通信装置および無線通信方法

Also Published As

Publication number Publication date
CN1618244A (zh) 2005-05-18
EP2083596B1 (fr) 2012-07-11
NO20042795L (no) 2004-09-03
IL162360A0 (en) 2005-11-20
JP4965523B2 (ja) 2012-07-04
MXPA04005440A (es) 2004-10-11
DE60232990D1 (de) 2009-08-27
CN102497653B (zh) 2017-06-13
KR20040058367A (ko) 2004-07-03
JP2005512475A (ja) 2005-04-28
KR100971102B1 (ko) 2010-07-20
RU2004120298A (ru) 2006-02-27
US7237007B2 (en) 2007-06-26
EP2083596A1 (fr) 2009-07-29
EP1452052A1 (fr) 2004-09-01
US9826433B2 (en) 2017-11-21
UA80102C2 (en) 2007-08-27
TW200304288A (en) 2003-09-16
TWI298228B (en) 2008-06-21
WO2003051078A1 (fr) 2003-06-19
RU2298881C2 (ru) 2007-05-10
JP2009022014A (ja) 2009-01-29
CA2468939A1 (fr) 2003-06-19
CN102497653A (zh) 2012-06-13
AU2002343721A1 (en) 2003-06-23
US20030103460A1 (en) 2003-06-05
US20070223383A1 (en) 2007-09-27
BR0214692A (pt) 2004-11-30

Similar Documents

Publication Publication Date Title
EP1452052B1 (fr) Procede et systeme de commande de flux entre une unite de commande de station de base et une station emettrice-receptrice de base
US20070019553A1 (en) Minimizing Padding for Voice Over Internet Protocol-Type Traffic Over Radio Link Control
US20130250765A1 (en) Delay based active queue management for uplink traffic in user equipment
US20040228285A1 (en) Packet communications system
US10439940B2 (en) Latency correction between transport layer host and deterministic interface circuit
KR100415115B1 (ko) 통신시스템의 데이터 혼잡 통보 방법 및 장치
KR101017532B1 (ko) 통신 시스템에서 흐름 제어 방법
CN105264798A (zh) 通过无线电水平反馈增强抖动缓冲区性能
US20060209687A1 (en) Communication rate control method and device
US20030139145A1 (en) Data transmitting method and apparatus for guaranteeing quality of service in a data communication system
US7561552B2 (en) Method for adaptive channel signaling
CN101005336A (zh) 一种适合卫星网络的自适应拥塞控制方法及系统
WO2019062589A1 (fr) Procédé et appareil de commande de flux
US9917752B1 (en) Optimization of contention paramaters for quality of service of VOIP (voice over internet protocol) calls in a wireless communication network
US9906650B2 (en) Voice adaptation for wireless communication
CA2408238C (fr) Attribution de voie sans fil dans une unite de traitement de station de base
US8014327B2 (en) Optimizing requested downlink data by adjusting frame number by measuring actual transmission delay

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20040624

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

17Q First examination report despatched

Effective date: 20070320

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60232990

Country of ref document: DE

Date of ref document: 20090827

Kind code of ref document: P

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091026

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091015

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091115

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

26N No opposition filed

Effective date: 20100416

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091130

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091016

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091130

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091112

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20101109

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091112

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090715

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20120731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20111130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20201013

Year of fee payment: 19

Ref country code: GB

Payment date: 20201029

Year of fee payment: 19

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60232990

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20211112

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211112

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220601