CA2475161A1 - Adaptive measurement of round-trip time in automatic retransmission request (arq) protocols using an abort timer started at receipt of a negative acknowledgement (nak) - Google Patents
Adaptive measurement of round-trip time in automatic retransmission request (arq) protocols using an abort timer started at receipt of a negative acknowledgement (nak) Download PDFInfo
- Publication number
- CA2475161A1 CA2475161A1 CA002475161A CA2475161A CA2475161A1 CA 2475161 A1 CA2475161 A1 CA 2475161A1 CA 002475161 A CA002475161 A CA 002475161A CA 2475161 A CA2475161 A CA 2475161A CA 2475161 A1 CA2475161 A1 CA 2475161A1
- Authority
- CA
- Canada
- Prior art keywords
- data
- packet
- rlp
- received
- abort
- 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.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/38—TPC being performed in particular situations
- H04W52/48—TPC being performed in particular situations during retransmission after error or non-acknowledgment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1809—Selective-repeat protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04K—SECRET COMMUNICATION; JAMMING OF COMMUNICATION
- H04K3/00—Jamming of communication; Counter-measures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
- H04L1/1838—Buffer management for semi-reliable protocols, e.g. for less sensitive applications such as streaming video
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
-
- 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
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
- Communication Control (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
For efficient communications of data across various protocol layers in an ARQ
communication system (100), a base station (101) receives radio link protocol (RLP) packets (509) of data. A processor (401) assembles received RLP packets (509) of data. The processor (401) is configured for determining whether a received RLP packet (509) of data is received out of sequence in a series of RLP packet (509) of data, starting an abort timer associated with a transmitted negative acknowledgment (NAK) for measuring an elapsed time of the abort timer, determining whether the elapsed time of said abort timer exceeds an abort period of time dynamic threshold that is based on statistical data of periods of time measured for previously received successful retransmissions of RLP packet (509) of data.
communication system (100), a base station (101) receives radio link protocol (RLP) packets (509) of data. A processor (401) assembles received RLP packets (509) of data. The processor (401) is configured for determining whether a received RLP packet (509) of data is received out of sequence in a series of RLP packet (509) of data, starting an abort timer associated with a transmitted negative acknowledgment (NAK) for measuring an elapsed time of the abort timer, determining whether the elapsed time of said abort timer exceeds an abort period of time dynamic threshold that is based on statistical data of periods of time measured for previously received successful retransmissions of RLP packet (509) of data.
Description
ADAPTIVE MEASUREMENT OF ROUND-TRIP TIME IN AUTOMATIC RETRANSMISSION
REQUEST (ARQ) PROTOCOLS USING AN ABORT TIMER STARTED AT RECEIPT OF A NEGATIVE
ACKNOWLEDGEMENT (NAK) Field [1001] The present invention relates generally to the field of communications, and more particularly, to data communications in a communication system.
Background [1002] In a communication system, unnecessary and excessive transmission by a user may cause interference for other users in addition to reducing the system capacity. The unnecessary and excessive transmission may be caused by inefficient flow of data in the communication system. The data communicated between two end users may pass through several layers of protocols for assuring proper flow of data through the system. The proper delivery of data in at least one aspect is assured through a system of checking for error in each packet of data, and requesting a retransmission of the same packet of data if an unacceptable error is detected in the packet of data.
Passing data from one protocol layer to another may be performed for a group of data packets at a time. Passing a group of data packets from one protocol layer to another may not take place until the process for retransmission of the selected packets of data in the group in the lower protocol layer has been completed. As a result, the retransmission process at one protocol layer may slow down flow of data between different protocol layers in the system. In addition, the higher layer of protocol may request for retransmission of all the packets of data in the group, resulting in a very inefficient use of communication resources when flow of data from one protocol layer to another is slow.
[1003 To this end as well as others, there is a need for a method and apparatus to efficiently control flow of data in a communication system.
SUMMARY
[1004] A system and various methods and apparatus for efficient communications of data across various protocol layers are disclosed. A base station receives radio link protocol (RLP) packets of data over a physical layer protocol. A processor keeps track of the received in-sequence RLP packet data. A network is coupled to the base station for routing data to a destination in accordance with at least one protocol layer including a TCP protocol layer.
The processor is configured for determining whether a received RLP packet of data is received out of sequence in a series of RLP packets of data. The processor starts an abort timer associated with a transmitted negative acknowledgment for measuring an elapsed time from the time when the request for the re-transmission is sent. The abort timer determines whether the elapsed time of the abort timer exceeds an abort period of time dynamic threshold, and passes, to a protocol layer above the RLP, the received in-sequence RLP
packets of data without waiting for receiving the retransmission of the missing RLP packets of data when the abort timer exceeds the abort period of time dynamic threshold. The processor is configured for determining the abort timer dynamic threshold based on statistical data obtained from measuring the periods of time between the time that the request for re-transmission is sent and the time that the requested re-transmission is received. The processor is configured for recording and accumulating data associated with a period of time for completing each successful retransmission of RLP packets for a number of retransmission processes and determining the statistical data based on the accumulated data of the period of times.
BRIEF DESCRIPTION OF THE DRAWINGS
[1005] The features, objects, and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:
[1006] FIG. 1 illustrates a communication system capable of operating in accordance with various embodiments of the invention;
[1007] FIG. 2 illustrates a communication system receiver for receiving and decoding received packets of data at a data rate in accordance with various aspects of the invention;
[1008] FIG. 3 illustrates a communication system transmitter for transmitting data packets at a scheduled data rate in accordance with various aspects of the invention;
[1009] FIG. 4 illustrates a transceiver system capable of operating in accordance with various embodiments of the invention;
[1010] FIG. 5 illustrates a stack of protocol layers for controlling flow of data in a communication system;
[1011] FIG. 6 illustrates a process for retransmission of a missing packet of data;
REQUEST (ARQ) PROTOCOLS USING AN ABORT TIMER STARTED AT RECEIPT OF A NEGATIVE
ACKNOWLEDGEMENT (NAK) Field [1001] The present invention relates generally to the field of communications, and more particularly, to data communications in a communication system.
Background [1002] In a communication system, unnecessary and excessive transmission by a user may cause interference for other users in addition to reducing the system capacity. The unnecessary and excessive transmission may be caused by inefficient flow of data in the communication system. The data communicated between two end users may pass through several layers of protocols for assuring proper flow of data through the system. The proper delivery of data in at least one aspect is assured through a system of checking for error in each packet of data, and requesting a retransmission of the same packet of data if an unacceptable error is detected in the packet of data.
Passing data from one protocol layer to another may be performed for a group of data packets at a time. Passing a group of data packets from one protocol layer to another may not take place until the process for retransmission of the selected packets of data in the group in the lower protocol layer has been completed. As a result, the retransmission process at one protocol layer may slow down flow of data between different protocol layers in the system. In addition, the higher layer of protocol may request for retransmission of all the packets of data in the group, resulting in a very inefficient use of communication resources when flow of data from one protocol layer to another is slow.
[1003 To this end as well as others, there is a need for a method and apparatus to efficiently control flow of data in a communication system.
SUMMARY
[1004] A system and various methods and apparatus for efficient communications of data across various protocol layers are disclosed. A base station receives radio link protocol (RLP) packets of data over a physical layer protocol. A processor keeps track of the received in-sequence RLP packet data. A network is coupled to the base station for routing data to a destination in accordance with at least one protocol layer including a TCP protocol layer.
The processor is configured for determining whether a received RLP packet of data is received out of sequence in a series of RLP packets of data. The processor starts an abort timer associated with a transmitted negative acknowledgment for measuring an elapsed time from the time when the request for the re-transmission is sent. The abort timer determines whether the elapsed time of the abort timer exceeds an abort period of time dynamic threshold, and passes, to a protocol layer above the RLP, the received in-sequence RLP
packets of data without waiting for receiving the retransmission of the missing RLP packets of data when the abort timer exceeds the abort period of time dynamic threshold. The processor is configured for determining the abort timer dynamic threshold based on statistical data obtained from measuring the periods of time between the time that the request for re-transmission is sent and the time that the requested re-transmission is received. The processor is configured for recording and accumulating data associated with a period of time for completing each successful retransmission of RLP packets for a number of retransmission processes and determining the statistical data based on the accumulated data of the period of times.
BRIEF DESCRIPTION OF THE DRAWINGS
[1005] The features, objects, and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:
[1006] FIG. 1 illustrates a communication system capable of operating in accordance with various embodiments of the invention;
[1007] FIG. 2 illustrates a communication system receiver for receiving and decoding received packets of data at a data rate in accordance with various aspects of the invention;
[1008] FIG. 3 illustrates a communication system transmitter for transmitting data packets at a scheduled data rate in accordance with various aspects of the invention;
[1009] FIG. 4 illustrates a transceiver system capable of operating in accordance with various embodiments of the invention;
[1010] FIG. 5 illustrates a stack of protocol layers for controlling flow of data in a communication system;
[1011] FIG. 6 illustrates a process for retransmission of a missing packet of data;
[1012] FIG. 7 illustrates various steps for controlling flow of data packets in a communication system in accordance with various aspects of the invention;
[1013] FIG. 8 illustrates various steps for controlling flow of data packets in a communication system in accordance with various aspects of the invention.
Detailed Description of the Preferred Embodiments) [1014] Various embodiments of the invention may be incorporated in a wireless communication system operating in accordance with the code division multiple access (CDMA) technique which has been disclosed and described in various standards published by the Telecommunication Industry Association (TIA) and other standards organizations. Such standards include the TIA/EIA-95 standard, TIA/EIA-IS-2000 standard, IMT-2000 standard, UMTS and WCDMA standard, all incorporated by reference herein. A system for communication of data is also detailed in the "TIA/EIA/IS-856 cdma2000 High Rate Packet Data Air Interface Specification," incorporated by reference herein.
A copy of the standards may be obtained by accessing the world wide web at the address: http://www.3gpp2.ora, or by writing to TIA, Standards and Technology Department, 2500 Wilson Boulevard, Arlington, VA 22201, United States of America. The standard generally identified as UMTS standard, incorporated by reference herein, may be obtained by contacting 3GPP Support Office, 650 Route des Lucioles-Sophia Antipolis, Valbonne-France.
[1015] Generally stated, a novel and improved method and apparatus provide for efficient use of communication resources in a CDMA communication system by efficiently determining proper flow of data from one communication protocol layer to another. One or more exemplary embodiments described herein are set forth in the context of a digital wireless data communication system. While use within this context is advantageous, different embodiments of the invention may be incorporated in different environments or configurations.
In general, the various systems described herein may be formed using software-controlled processors, integrated circuits, or discrete logic. The data, instructions, commands, information, signals, symbols, and chips that may be referenced throughout the application are advantageously represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or a combination thereof. In addition, the blocks shown in each block diagram may represent hardware or method steps.
[1016] FIG. 1 illustrates a general block diagram of a communication system 100 capable of operating in accordance with any of the code division multiple access (CDMA) communication system standards while incorporating various embodiments of the invention. Communication system 100 may be for communications of voice, data or both. Generally, communication system 100 includes a base station 101 that provides communication links between a number of mobile stations, such as mobile stations 102-104, and between the mobile stations 102-104 and a public switch telephone and data network 105.
The mobile stations in FIG. 1 may be referred to as data access terminals (AT) and the base station as data access network (AN) without departing from the main scope and various advantages of the invention. Base station 101 may include a number of components, such as a base station controller and a base transceiver system. For simplicity, such components are not shown. Base station 101 may be in communication with other base stations, for example base station 160. A mobile switching center (not shown) may control various operating aspects of the communication system 100 and in relation to a back-haul 199 between network 105 and base stations 101 and 160.
[1017] Base station 101 communicates with each mobile station that is in its coverage area via a forward link signal transmitted from base station 101.
The forward link signals targeted for mobile stations 102-104 may be summed to form a forward link signal 106. Each of the mobile stations 102-104 receiving forward link signal 106 decodes the forward link signal 106 to extract the information that is targeted for its user. Base station 160 may also communicate with the mobile stations that are in its coverage area via a forward link signal transmitted from base station 160. Mobile stations 102-104 communicate with base stations 101 and 160 via corresponding reverse links.
Each reverse link is maintained by a reverse link signal, such as reverse link signals 107-109 for respectively mobile stations 102-104. The reverse link signals 107-109, although may be targeted for one base station, may be received at other base stations.
[1018] Base stations 101 and 160 may be simultaneously communicating to a common mobile station. For example, mobile station 102 may be in close proximity of base stations 101 and 160, which can maintain communications with both base stations 101 and 160. On the forward link, base station 101 transmits on forward link signal 106, and base station 160 on the forward link signal 161. On the reverse link, mobile station 102 transmits on reverse link signal 107 to be received by both base stations 101 and 160. For transmitting a packet of data to mobile station 102, one of the base stations 101 and 160 may be selected to transmit the packet of data to mobile station 102. On the reverse link, both base stations 101 and 160 may attempt to decode the traffic data transmission from the mobile station 102.
[1019] FIG. 2 illustrates a block diagram of a receiver 200 used for processing and demodulating the received CDMA signal. Receiver 200 may be used for decoding the information on the reverse and forward links signals.
Received (Rx) samples may be stored in RAM 204. Receive samples are generated by a radio frequency/intermediate frequency (RF/IF) system 290 and an antenna system 292. The RF/IF system 290 and antenna system 292 may include one or more components for receiving multiple signals and RF/IF
processing of the received signals for taking advantage of the receive diversity gain. Multiple received signals propagated through different propagation paths may be from a common source. Antenna system 292 receives the RF signals, and passes the RF signals to RF/IF system 290. RF/IF system 290 may be any conventional RF/IF receiver. The received RF signals are filtered, down-converted and digitized to form RX samples at base band frequencies. The samples are supplied to a demultiplexer (demux) 202. The output of demux 202 is supplied to a searcher unit 206 and finger elements 208. A control unit 210 is coupled thereto. A combiner 212 couples a decoder 214 to finger elements 208. Control unit 210 may be a microprocessor controlled by software, and may be located on the same integrated circuit or on a separate integrated circuit. The decoding function in decoder 214 may be in accordance with a turbo decoder or any other suitable decoding algorithms.
[1020] During operation, received samples are supplied to demux 202.
Demux 202 supplies the samples to searcher unit 206 and finger elements 208.
Control unit 210 configures finger elements 208 to perform demodulation and despreading of the received signal at different time offsets based on search results from searcher unit 206. The results of the demodulation are combined.
and passed to decoder 214. Decoder 214 decodes the data and outputs the decoded data. Despreading of the channels is performed by multiplying the received samples with the complex conjugate of the PN sequence and assigned Walsh function at a single timing hypothesis and digitally filtering the resulting samples, often with an integrate and dump accumulator circuit (not shown).
Such a technique is commonly known in the art. Receiver 200 may be used in a receiver portion of base stations 101 and 160 for processing .the received reverse link signals from the mobile stations, and in a receiver portion of any of the mobile stations for processing the received forward link signals.
[1021] FIG. 3 illustrates a block diagram of a transmitter 300 for transmitting the reverse and forward link signals. The channel data for transmission are input to a modulator 301 for modulation. The modulation may be according to any of the commonly known modulation techniques such as QAM, PSK or BPSK. The data is encoded at a data rate in modulator 301. The data rate may be selected by a data rate and power level selector 303. The data rate selection may be based on feedback information received from a receiving destination. The receiving destination may be a mobile station or a base station. The feedback information may include the maximum allowed data rate. The maximum allowed data rate may be determined in accordance with various commonly known algorithms. The maximum allowed data rate very often is based on the channel condition, among other considered factors. The data rate and power level selector 303 accordingly selects the data rate in modulator 301. The output of modulator 301 passes through a signal spreading operation and amplified in a block 302 for transmission from an antenna 304.
The data rate and power level selector 303 also selects a power level for the amplification level of the transmitted signal in accordance with the feedback information. The combination of the selected data rate and the power level allows proper decoding of the transmitted data at the receiving destination. A
pilot signal is also generated in a block 307. The pilot signal is amplified to an appropriate level in block 307. The pilot signal power level may be in accordance with the channel condition at the receiving destination. The pilot signal is combined with the channel signal in a combiner 308. The combined signal may be amplified in an amplifier 309 and transmitted from antenna 304.
The antenna 304 may be in any number of combinations including antenna arrays and multiple input multiple output configurations.
(1022] FIG. 4 depicts a general diagram of a transceiver system 400 for incorporating receiver 200 and transmitter 300 for maintaining a communication link with a destination. The transceiver 400 may be incorporated in a mobile station or a base station. A processor 401 may be coupled to receiver 200 and transmitter 300 to process the received and transmitted data. Various aspects of the receiver 200 and transmitter 300 may be common, even though receiver 200 and transmitter 300 are shown separately. In one aspect, receiver 200 and transmitter 300 may share a common local oscillator and a common antenna system for RF/IF receiving and transmitting. Transmitter 300 receives the data for transmission on input 405. Transmit data processing block 403 prepares the data for transmission on a transmit channel. Received data, after being decoded in decoder 214, are received at processor 400 at an input 404.
Received data are processed in received data processing block 402 in processor 401. The processing of the received data generally includes checking for error in the received packets of data. For example, if a received packet of data has error at an unacceptable level, the received data processing block 402 sends an instruction to transmit data processing block 403 for making a request for retransmission of the packet of data. The request is transmitted on a transmit channel. Various operations of processor 401 may be integrated in a single or multiple processing units. The transceiver 400 may be connected to another device. The transceiver 400 may be an integral part of the device.
The device may be a computer or operates similar to a computer. The device may be connected to a data network, such as Internet. In case of incorporating the transceiver 400 in a base station, the base station through several connections may be connected to a network, such as Internet.
[1023) The flow of data between two end points may be controlled via several protocol layers. An exemplary stack of the protocol layers 500 is shown in FIG. 5 for controlling flow of data between two end points. For example, one end point may be a source connected to Internet through the network 105. The other end point may be a data processing unit such as a computer coupled to a mobile station or integrated in a mobile station. The protocol layers 500 may have several other layers or each layer may have several sub-layers. A
detailed stack of protocol layers is not shown for simplicity. The stack of protocol layers 500 may be followed for flow of data in a data connection from one end point to another. At the top layer, a TCP layer 501 controls the TCP
packets 506. TCP packets 506 may be generated from a much larger data file.
The data file may be partitioned into several TCP packets 506. The data file may include text message data, video data, picture data or voice data. The size of the TCP packets 506 may be different at different times. At the Internet Protocol layer (IP) layer 502, a header is added to the TCP packets 506 to produce data packet 507. The header may identify a port number for proper routing of the packets of data to the appropriate application. At a point-to-point protocol (PPP) layer 503, PPP header and trailer data are added to data packet 507 to produce data packet 508. The PPP data may identify the point-to-point connection addresses for proper routing of a packet of data from a source connection point to a destination connection point. A radio link protocol (RLP) layer 504 provides a mechanism for retransmission and duplication of data packets. At RLP layer 504, the data packet 508 is divided into several RLP
packets 509A-N. Each of the RLP packets 509A-N is processed independently and assigned a sequence number. The sequence number is added to the data in each RLP packet of data for identifying the RLP packet of data among the RLP packets 509A-N. One or more of the RLP packets 509A-N is placed into a physical layer packet of data 510. The size of the payload of the packet of data 510 may vary from time to time. A physical layer 505 controls the channel structure, frequency, power output, and modulation specification for data packet 510. The data packet 510 is transmitted to a destination. The size of data packet 510 may be different from time to time based on the channel condition and the selected communication data rate.
[1024] On a receiving destination, the data packet 510 is received and processed. The received packet 510 is passed on to RLP layer 504. The RLP
layer 504 attempts to reconstruct the RLP packets 509A-N from the received packets of data. In order to reduce the packet error rate seen by the higher layer of protocol, such as PPP layer 503 and IP layer 502, the RLP layer 504 implements an automatic retransmission request (ARQ) mechanism by requesting re-transmission for the missing RLP packets. The RLP protocol re-assembles packets 509A-N to form a complete packet 508. The process may take some time to completely receive all the RLP packets 509A-N. Several transmissions of data packet 510 may be needed to completely send all the RLP packets 509A-N. When an RLP packet of data is received out of sequence, the RLP layer 504 sends a negative acknowledgement (NAK) message to the transmitting destination. In response, the transmitting destination retransmits the missing RLP data packet.
[1025] Referring to FIG. 6, a message flow 600 is shown to provide an exemplary flow of data at the physical layer 505. The RLP packets with sequence numbers "01" to "07" are sent from a source to a destination, for example. The source and destination may be, respectively, either a base station and a mobile station or a mobile station and a base station. At the RLP
layer 504, the RLP packets 509A-N are accumulated to complete the packet 508. Once all the RLP packets are received, the RLP packets 509A-N are passed on to a higher level. One or more RLP packets may be combined into a common payload and sent on one data packet 510. In the exemplary message flow 600, the RLP packet identified as RLP packet "03", for example does not get to the destination. The failure may be due to many factors including disruption of the radio link between the source and the destination. After the destination receives RLP packet "04", the RLP layer 504 detects an out of sequence reception of the RLP packets. The RLP layer 504 sends a NAK
message identifying RLP packet "03" as missing in the communication. At the same time RLP layer 504 begins a timer. The timer counts the lapsed amount of time after sending the NAK message. If the timer expires, for example after 500 mSec, before receiving the missing RLP packet "03", the destination RLP
504 may assume that the retransmission of the missing packet has failed and the destination RLP may deliver to the upper layer the RLP packets that have been received in sequence up to the next missing RLP packet. If there is no other missing RLP packet, the RLP may deliver all the received in-sequence packets. The source may limit the number of retransmission of an RLP packet only to one time. Therefore, in such a situation, sending another NAK message may not help because the source may have retransmitted the missing RLP
packet "03" without being received at the destination. Once the missing RLP
packet "03" is received, the timer terminates.
[1026] The TCP layer 501 also has a similar retransmission process. If the TCP layer 501 at the receiving destination does not receive an expected TCP 506 for some time, the TCP layer 501 at the transmitting source re-transmits the TCP packet. The process of sending a NAK message and waiting to receive the missing RLP data packet at the RLP layer 504 may take some time. During this time, RLP layer 504 holds off delivery of data to the upper layer. The delivery of the RLP packets that have been received correctly is prevented if at least one of the correctly received RLP packets has a sequence number that is higher than the sequence number of the missing RLP packet.
Since the RLP layer 504 waits for example at least 500 mSec to receive a missing RLP packet, passing the RLP packets that have been received correctly may get delayed for a substantial amount of time. The RLP layer 504 normally does not send up an incomplete set of RLP packets 509A-N to a higher level. As a result, the TCP layer 501 at the transmitting source may initiate a retransmission of the entire IP data-gram 506 which is much larger than a single RLP packet, therefore, causing unnecessary and excessive retransmission in the communication system and reduction in the size of the TCP congestion window (cwnd). The retransmission process at the RLP layer 504 may take an amount of time long enough for triggering the retransmission process at the TCP layer 501. However, the flow of data in the system may have been limited by the process at RLP layer 504 for retransmission of a single RLP packet. The size of TCP packet 506 is much larger than the size of RLP
packets 509A-N. Retransmission of a TCP packet 506 takes away a large amount of communication resources at all levels. The retransmission of a TCP
packet 506 also adversely effects the communication resources at the physical layer 505 for taking up the resources to transmit a large number of RLP
packets that complete the requested TCP packet 506. The TCP layer 501 may determine that failure to receive an expected TCP packet 506 may be due to the network congestion. As a result, to relieve possible network congestion, the TCP layer 501 also may slow down the data flow activity in the network. As a result, the flow of data to other users may also slow down due to the delay of the process at the RLP layer 504 of a single user.
(1027] Various components of the communication system 100 may control various aspects of the stack of protocol layers 500. For example, a computer server or a collection of computers, not shown, connected to network 105 may control TCP layer 501, IP layer 502 and PPP layer 503. The RLP
layer 504 and physical layer 505 may be controlled by processor 401 through operations of the received and transmit data processing units 402 and 403.
Therefore, processor 401 may not be able to control the behavior at the TCP
layer 501 to prevent TCP layer 501 from making a retransmission of a TCP
packet 506 when the processor 401 is attempting to process the retransmission of the missing RLP packets.
[1028] In accordance with various aspects of the invention, processor 401 may control the amount of time the retransmission timer is allowed to lapse before terminating the retransmission process. The physical layer communications may be performed at various data rates. The selected data rate depends on the channel condition. At high data rate, a large number of RLP packets may be communicated between a mobile station and a base station in a short period of time. A successful retransmission process also takes a short time to complete depending on the channel condition. In case of a need for retransmission, the retransmission process may limit the number of NAK
transmissions for a missing RLP packet of data. The channel conditions of the forward and reverse link may not be the same. Therefore, transmission of a NAK message, once or twice over a period of time, in one direction may fail to arrive at the destination even though the channel condition for transmitting the RLP packet in the other direction is acceptable. In another case, the channel condition for transmission of a NAK massage may be acceptable but the channel condition for receiving a RLP packet of data may not be acceptable.
[1029] In accordance with various aspects of the invention, the retransmission process for an RLP packet may be concluded, whether in success or failure, in a period of time that may vary in length of time from time to time depending on the channel condition. Therefore, in accordance with various aspects of the invention, the retransmission timer is controlled in a manner that prevents excessive and unnecessary wait time while allowing the retransmission process to conclude for a channel condition. An abort timer dynamic threshold is set to the least amount of time that is necessary for the destination receiver to send a request for re-transmission and for the source transmitter to re-transmit the requested RLP packets) plus some margin to account for variation in delays. A long threshold may cause re-transmission of bigger blocks of data by the layers above the RLP layer. Retransmission at the higher layer may be wasteful because at RLP layer 504 a large portion of the higher layer data may have been received and only a small piece corresponding to the missing the RLP packet is missing. When the value of the threshold for the abort timer is set too short, the retransmission process may be aborted pre-maturely without allowing adequate time for transmitting a NAK message and receiving a retransmission of the missing RLP packet. The receiver may discard the received re-transmitted RLP packets after aborting pre-maturely causing wasteful use of the communication resources. The processor is configured for determining the abort timer dynamic threshold based on statistical data obtained from measuring the periods of time between the time that the request for re-transmission of a missing packet is sent and the time that the requested re-transmission of the missing packet is received. The processor is configured for recording and accumulating data associated with a period of time for completing each successful retransmission of RLP packets for a number of retransmission processes and determining the statistical data based on the accumulated data of the period of times.
[1030] Referring to FIG. 7, a flow chart 700 depicts various steps that may be incorporated for processing of data at the RLP layer 504 in accordance with various aspects of the invention. The processor 401 through operations of received data processing block 402 and transmit data processing block 403 may perform various steps of flow chart 700. At step 701, received data processing block 402 may detect receiving an out of sequence RLP packet of data. The missing RLP packet of data may be the RLP packet "03" as shown in the example in FIG. 6. At step 702, transmit data processing block 403 transmits a NAK message for retransmission of the missing RLP packet of data.
At the same time, an internal timer in processor 401 starts an abort timer at step 703. The abort time is associated with the transmitted NAK message for keeping the lapsed amount of time after transmitting the NAK message. At step 707, the processor 401 determines whether a retransmission of the missing RLP packet is received. At step 704, the elapsed time of the abort timer is compared to an abort period of time dynamic threshold to determine whether the elapsed time has exceeded the dynamic threshold. If the elapsed period of time has exceeded the dynamic threshold, the process flow 700 moves to step 705; otherwise, the process flow continues at step 707. At step 707, the processor 401 may determine that the missing RLP packet has arrived at the destination. In this case, the abort timer associated with the missing MAC
packet terminates and the process flow 700 moves to step 706. At step 705, the processor 401 may consider the missing RLP packet as received when the elapsed time of the abort timer exceeds the abort period of time dynamic threshold at step 704. At step 706, the received in-sequence RLP packets of data are passed on to a higher level of protocol layer. The higher protocol layer may be the PPP protocol layer 503. In accordance with various aspects of the invention, the abort period of time dynamic threshold is determined for controlling flow of data in a manner consistent with an efficient flow of data at all protocol layers including the TCP layer 501. Even though, the processor 401 has no direct control over the process at TCP layer 501, by incorporating various steps of the flow chart 700 an unnecessary retransmission of TCP
packet 506 may be prevented.
(1031] Referring to FIG. 8, a flow chart 800 provides various steps for determining the abort period of time dynamic threshold for controlling flow of data in a manner consistent with an efficient flow of data at all protocol layers.
At step 801, a period of time for completing a successful retransmission process of an RLP packet is recorded. A successful retransmission period may be the elapsed time of the abort timer for a completed successful RLP packet retransmission. At step 802, the period of time for a number of successfully completed retransmissions of RLP packets are accumulated. At step 803, the statistical data, such as average and standard deviation, of the accumulated data are determined. At step 804, the abort period of time dynamic threshold is determined based on the determined statistical data. For example, the dynamic threshold may be set approximately equal to the determined statistical average plus a margin equal to one or two standard deviations. The determined dynamic threshold is used at step 704 for determining whether the elapsed time of the abort timer exceeds the dynamic threshold. The determined dynamic threshold may change from time to time. The change may be due to many factors including the channel condition between the transmitting source and the destination receiver.
[1032] In at least one aspect, when successful retransmission periods become shorter in duration, perhaps due to favorable channel condition, the abort period of time dynamic threshold becomes smaller. The number of NAK
transmissions for a missing MAC packet of data may be restricted to a limited number, such as one or two. After sending the maximum allowed number of NAK messages, the retransmission process has to finish either in success or failure. When the abort period of time dynamic threshold is used at step 704 and determined based on the statistical data at step 804, the retransmission process is concluded within a statistical time period that most likely is possible to lead to a successful retransmission process. If the retransmission process is not concluded within the abort period of time dynamic threshold, the extra wait time may not and most likely would not lead to a successful conclusion of the retransmission process. As such, the retransmission process is controlled in an efficient manner for controlling flow of data from one protocol layer to another.
An unnecessary retransmission of a TCP packet of data may be prevented as a result. Processing data at the RLP protocol layer 504 is made efficient in respect to the ARQ process and flow of data to the higher level protocol layers.
[1033] Those of skill in the art would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
[1034] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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.
[1035] 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. A software module may reside in RAM memory, flash memory, ROM memory, EPROM
memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
[1036] The previous description of the preferred embodiments is provided to enable any person skilled in the art to make or use the present invention.
The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of the inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[1037] What is claimed is:
[1013] FIG. 8 illustrates various steps for controlling flow of data packets in a communication system in accordance with various aspects of the invention.
Detailed Description of the Preferred Embodiments) [1014] Various embodiments of the invention may be incorporated in a wireless communication system operating in accordance with the code division multiple access (CDMA) technique which has been disclosed and described in various standards published by the Telecommunication Industry Association (TIA) and other standards organizations. Such standards include the TIA/EIA-95 standard, TIA/EIA-IS-2000 standard, IMT-2000 standard, UMTS and WCDMA standard, all incorporated by reference herein. A system for communication of data is also detailed in the "TIA/EIA/IS-856 cdma2000 High Rate Packet Data Air Interface Specification," incorporated by reference herein.
A copy of the standards may be obtained by accessing the world wide web at the address: http://www.3gpp2.ora, or by writing to TIA, Standards and Technology Department, 2500 Wilson Boulevard, Arlington, VA 22201, United States of America. The standard generally identified as UMTS standard, incorporated by reference herein, may be obtained by contacting 3GPP Support Office, 650 Route des Lucioles-Sophia Antipolis, Valbonne-France.
[1015] Generally stated, a novel and improved method and apparatus provide for efficient use of communication resources in a CDMA communication system by efficiently determining proper flow of data from one communication protocol layer to another. One or more exemplary embodiments described herein are set forth in the context of a digital wireless data communication system. While use within this context is advantageous, different embodiments of the invention may be incorporated in different environments or configurations.
In general, the various systems described herein may be formed using software-controlled processors, integrated circuits, or discrete logic. The data, instructions, commands, information, signals, symbols, and chips that may be referenced throughout the application are advantageously represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or a combination thereof. In addition, the blocks shown in each block diagram may represent hardware or method steps.
[1016] FIG. 1 illustrates a general block diagram of a communication system 100 capable of operating in accordance with any of the code division multiple access (CDMA) communication system standards while incorporating various embodiments of the invention. Communication system 100 may be for communications of voice, data or both. Generally, communication system 100 includes a base station 101 that provides communication links between a number of mobile stations, such as mobile stations 102-104, and between the mobile stations 102-104 and a public switch telephone and data network 105.
The mobile stations in FIG. 1 may be referred to as data access terminals (AT) and the base station as data access network (AN) without departing from the main scope and various advantages of the invention. Base station 101 may include a number of components, such as a base station controller and a base transceiver system. For simplicity, such components are not shown. Base station 101 may be in communication with other base stations, for example base station 160. A mobile switching center (not shown) may control various operating aspects of the communication system 100 and in relation to a back-haul 199 between network 105 and base stations 101 and 160.
[1017] Base station 101 communicates with each mobile station that is in its coverage area via a forward link signal transmitted from base station 101.
The forward link signals targeted for mobile stations 102-104 may be summed to form a forward link signal 106. Each of the mobile stations 102-104 receiving forward link signal 106 decodes the forward link signal 106 to extract the information that is targeted for its user. Base station 160 may also communicate with the mobile stations that are in its coverage area via a forward link signal transmitted from base station 160. Mobile stations 102-104 communicate with base stations 101 and 160 via corresponding reverse links.
Each reverse link is maintained by a reverse link signal, such as reverse link signals 107-109 for respectively mobile stations 102-104. The reverse link signals 107-109, although may be targeted for one base station, may be received at other base stations.
[1018] Base stations 101 and 160 may be simultaneously communicating to a common mobile station. For example, mobile station 102 may be in close proximity of base stations 101 and 160, which can maintain communications with both base stations 101 and 160. On the forward link, base station 101 transmits on forward link signal 106, and base station 160 on the forward link signal 161. On the reverse link, mobile station 102 transmits on reverse link signal 107 to be received by both base stations 101 and 160. For transmitting a packet of data to mobile station 102, one of the base stations 101 and 160 may be selected to transmit the packet of data to mobile station 102. On the reverse link, both base stations 101 and 160 may attempt to decode the traffic data transmission from the mobile station 102.
[1019] FIG. 2 illustrates a block diagram of a receiver 200 used for processing and demodulating the received CDMA signal. Receiver 200 may be used for decoding the information on the reverse and forward links signals.
Received (Rx) samples may be stored in RAM 204. Receive samples are generated by a radio frequency/intermediate frequency (RF/IF) system 290 and an antenna system 292. The RF/IF system 290 and antenna system 292 may include one or more components for receiving multiple signals and RF/IF
processing of the received signals for taking advantage of the receive diversity gain. Multiple received signals propagated through different propagation paths may be from a common source. Antenna system 292 receives the RF signals, and passes the RF signals to RF/IF system 290. RF/IF system 290 may be any conventional RF/IF receiver. The received RF signals are filtered, down-converted and digitized to form RX samples at base band frequencies. The samples are supplied to a demultiplexer (demux) 202. The output of demux 202 is supplied to a searcher unit 206 and finger elements 208. A control unit 210 is coupled thereto. A combiner 212 couples a decoder 214 to finger elements 208. Control unit 210 may be a microprocessor controlled by software, and may be located on the same integrated circuit or on a separate integrated circuit. The decoding function in decoder 214 may be in accordance with a turbo decoder or any other suitable decoding algorithms.
[1020] During operation, received samples are supplied to demux 202.
Demux 202 supplies the samples to searcher unit 206 and finger elements 208.
Control unit 210 configures finger elements 208 to perform demodulation and despreading of the received signal at different time offsets based on search results from searcher unit 206. The results of the demodulation are combined.
and passed to decoder 214. Decoder 214 decodes the data and outputs the decoded data. Despreading of the channels is performed by multiplying the received samples with the complex conjugate of the PN sequence and assigned Walsh function at a single timing hypothesis and digitally filtering the resulting samples, often with an integrate and dump accumulator circuit (not shown).
Such a technique is commonly known in the art. Receiver 200 may be used in a receiver portion of base stations 101 and 160 for processing .the received reverse link signals from the mobile stations, and in a receiver portion of any of the mobile stations for processing the received forward link signals.
[1021] FIG. 3 illustrates a block diagram of a transmitter 300 for transmitting the reverse and forward link signals. The channel data for transmission are input to a modulator 301 for modulation. The modulation may be according to any of the commonly known modulation techniques such as QAM, PSK or BPSK. The data is encoded at a data rate in modulator 301. The data rate may be selected by a data rate and power level selector 303. The data rate selection may be based on feedback information received from a receiving destination. The receiving destination may be a mobile station or a base station. The feedback information may include the maximum allowed data rate. The maximum allowed data rate may be determined in accordance with various commonly known algorithms. The maximum allowed data rate very often is based on the channel condition, among other considered factors. The data rate and power level selector 303 accordingly selects the data rate in modulator 301. The output of modulator 301 passes through a signal spreading operation and amplified in a block 302 for transmission from an antenna 304.
The data rate and power level selector 303 also selects a power level for the amplification level of the transmitted signal in accordance with the feedback information. The combination of the selected data rate and the power level allows proper decoding of the transmitted data at the receiving destination. A
pilot signal is also generated in a block 307. The pilot signal is amplified to an appropriate level in block 307. The pilot signal power level may be in accordance with the channel condition at the receiving destination. The pilot signal is combined with the channel signal in a combiner 308. The combined signal may be amplified in an amplifier 309 and transmitted from antenna 304.
The antenna 304 may be in any number of combinations including antenna arrays and multiple input multiple output configurations.
(1022] FIG. 4 depicts a general diagram of a transceiver system 400 for incorporating receiver 200 and transmitter 300 for maintaining a communication link with a destination. The transceiver 400 may be incorporated in a mobile station or a base station. A processor 401 may be coupled to receiver 200 and transmitter 300 to process the received and transmitted data. Various aspects of the receiver 200 and transmitter 300 may be common, even though receiver 200 and transmitter 300 are shown separately. In one aspect, receiver 200 and transmitter 300 may share a common local oscillator and a common antenna system for RF/IF receiving and transmitting. Transmitter 300 receives the data for transmission on input 405. Transmit data processing block 403 prepares the data for transmission on a transmit channel. Received data, after being decoded in decoder 214, are received at processor 400 at an input 404.
Received data are processed in received data processing block 402 in processor 401. The processing of the received data generally includes checking for error in the received packets of data. For example, if a received packet of data has error at an unacceptable level, the received data processing block 402 sends an instruction to transmit data processing block 403 for making a request for retransmission of the packet of data. The request is transmitted on a transmit channel. Various operations of processor 401 may be integrated in a single or multiple processing units. The transceiver 400 may be connected to another device. The transceiver 400 may be an integral part of the device.
The device may be a computer or operates similar to a computer. The device may be connected to a data network, such as Internet. In case of incorporating the transceiver 400 in a base station, the base station through several connections may be connected to a network, such as Internet.
[1023) The flow of data between two end points may be controlled via several protocol layers. An exemplary stack of the protocol layers 500 is shown in FIG. 5 for controlling flow of data between two end points. For example, one end point may be a source connected to Internet through the network 105. The other end point may be a data processing unit such as a computer coupled to a mobile station or integrated in a mobile station. The protocol layers 500 may have several other layers or each layer may have several sub-layers. A
detailed stack of protocol layers is not shown for simplicity. The stack of protocol layers 500 may be followed for flow of data in a data connection from one end point to another. At the top layer, a TCP layer 501 controls the TCP
packets 506. TCP packets 506 may be generated from a much larger data file.
The data file may be partitioned into several TCP packets 506. The data file may include text message data, video data, picture data or voice data. The size of the TCP packets 506 may be different at different times. At the Internet Protocol layer (IP) layer 502, a header is added to the TCP packets 506 to produce data packet 507. The header may identify a port number for proper routing of the packets of data to the appropriate application. At a point-to-point protocol (PPP) layer 503, PPP header and trailer data are added to data packet 507 to produce data packet 508. The PPP data may identify the point-to-point connection addresses for proper routing of a packet of data from a source connection point to a destination connection point. A radio link protocol (RLP) layer 504 provides a mechanism for retransmission and duplication of data packets. At RLP layer 504, the data packet 508 is divided into several RLP
packets 509A-N. Each of the RLP packets 509A-N is processed independently and assigned a sequence number. The sequence number is added to the data in each RLP packet of data for identifying the RLP packet of data among the RLP packets 509A-N. One or more of the RLP packets 509A-N is placed into a physical layer packet of data 510. The size of the payload of the packet of data 510 may vary from time to time. A physical layer 505 controls the channel structure, frequency, power output, and modulation specification for data packet 510. The data packet 510 is transmitted to a destination. The size of data packet 510 may be different from time to time based on the channel condition and the selected communication data rate.
[1024] On a receiving destination, the data packet 510 is received and processed. The received packet 510 is passed on to RLP layer 504. The RLP
layer 504 attempts to reconstruct the RLP packets 509A-N from the received packets of data. In order to reduce the packet error rate seen by the higher layer of protocol, such as PPP layer 503 and IP layer 502, the RLP layer 504 implements an automatic retransmission request (ARQ) mechanism by requesting re-transmission for the missing RLP packets. The RLP protocol re-assembles packets 509A-N to form a complete packet 508. The process may take some time to completely receive all the RLP packets 509A-N. Several transmissions of data packet 510 may be needed to completely send all the RLP packets 509A-N. When an RLP packet of data is received out of sequence, the RLP layer 504 sends a negative acknowledgement (NAK) message to the transmitting destination. In response, the transmitting destination retransmits the missing RLP data packet.
[1025] Referring to FIG. 6, a message flow 600 is shown to provide an exemplary flow of data at the physical layer 505. The RLP packets with sequence numbers "01" to "07" are sent from a source to a destination, for example. The source and destination may be, respectively, either a base station and a mobile station or a mobile station and a base station. At the RLP
layer 504, the RLP packets 509A-N are accumulated to complete the packet 508. Once all the RLP packets are received, the RLP packets 509A-N are passed on to a higher level. One or more RLP packets may be combined into a common payload and sent on one data packet 510. In the exemplary message flow 600, the RLP packet identified as RLP packet "03", for example does not get to the destination. The failure may be due to many factors including disruption of the radio link between the source and the destination. After the destination receives RLP packet "04", the RLP layer 504 detects an out of sequence reception of the RLP packets. The RLP layer 504 sends a NAK
message identifying RLP packet "03" as missing in the communication. At the same time RLP layer 504 begins a timer. The timer counts the lapsed amount of time after sending the NAK message. If the timer expires, for example after 500 mSec, before receiving the missing RLP packet "03", the destination RLP
504 may assume that the retransmission of the missing packet has failed and the destination RLP may deliver to the upper layer the RLP packets that have been received in sequence up to the next missing RLP packet. If there is no other missing RLP packet, the RLP may deliver all the received in-sequence packets. The source may limit the number of retransmission of an RLP packet only to one time. Therefore, in such a situation, sending another NAK message may not help because the source may have retransmitted the missing RLP
packet "03" without being received at the destination. Once the missing RLP
packet "03" is received, the timer terminates.
[1026] The TCP layer 501 also has a similar retransmission process. If the TCP layer 501 at the receiving destination does not receive an expected TCP 506 for some time, the TCP layer 501 at the transmitting source re-transmits the TCP packet. The process of sending a NAK message and waiting to receive the missing RLP data packet at the RLP layer 504 may take some time. During this time, RLP layer 504 holds off delivery of data to the upper layer. The delivery of the RLP packets that have been received correctly is prevented if at least one of the correctly received RLP packets has a sequence number that is higher than the sequence number of the missing RLP packet.
Since the RLP layer 504 waits for example at least 500 mSec to receive a missing RLP packet, passing the RLP packets that have been received correctly may get delayed for a substantial amount of time. The RLP layer 504 normally does not send up an incomplete set of RLP packets 509A-N to a higher level. As a result, the TCP layer 501 at the transmitting source may initiate a retransmission of the entire IP data-gram 506 which is much larger than a single RLP packet, therefore, causing unnecessary and excessive retransmission in the communication system and reduction in the size of the TCP congestion window (cwnd). The retransmission process at the RLP layer 504 may take an amount of time long enough for triggering the retransmission process at the TCP layer 501. However, the flow of data in the system may have been limited by the process at RLP layer 504 for retransmission of a single RLP packet. The size of TCP packet 506 is much larger than the size of RLP
packets 509A-N. Retransmission of a TCP packet 506 takes away a large amount of communication resources at all levels. The retransmission of a TCP
packet 506 also adversely effects the communication resources at the physical layer 505 for taking up the resources to transmit a large number of RLP
packets that complete the requested TCP packet 506. The TCP layer 501 may determine that failure to receive an expected TCP packet 506 may be due to the network congestion. As a result, to relieve possible network congestion, the TCP layer 501 also may slow down the data flow activity in the network. As a result, the flow of data to other users may also slow down due to the delay of the process at the RLP layer 504 of a single user.
(1027] Various components of the communication system 100 may control various aspects of the stack of protocol layers 500. For example, a computer server or a collection of computers, not shown, connected to network 105 may control TCP layer 501, IP layer 502 and PPP layer 503. The RLP
layer 504 and physical layer 505 may be controlled by processor 401 through operations of the received and transmit data processing units 402 and 403.
Therefore, processor 401 may not be able to control the behavior at the TCP
layer 501 to prevent TCP layer 501 from making a retransmission of a TCP
packet 506 when the processor 401 is attempting to process the retransmission of the missing RLP packets.
[1028] In accordance with various aspects of the invention, processor 401 may control the amount of time the retransmission timer is allowed to lapse before terminating the retransmission process. The physical layer communications may be performed at various data rates. The selected data rate depends on the channel condition. At high data rate, a large number of RLP packets may be communicated between a mobile station and a base station in a short period of time. A successful retransmission process also takes a short time to complete depending on the channel condition. In case of a need for retransmission, the retransmission process may limit the number of NAK
transmissions for a missing RLP packet of data. The channel conditions of the forward and reverse link may not be the same. Therefore, transmission of a NAK message, once or twice over a period of time, in one direction may fail to arrive at the destination even though the channel condition for transmitting the RLP packet in the other direction is acceptable. In another case, the channel condition for transmission of a NAK massage may be acceptable but the channel condition for receiving a RLP packet of data may not be acceptable.
[1029] In accordance with various aspects of the invention, the retransmission process for an RLP packet may be concluded, whether in success or failure, in a period of time that may vary in length of time from time to time depending on the channel condition. Therefore, in accordance with various aspects of the invention, the retransmission timer is controlled in a manner that prevents excessive and unnecessary wait time while allowing the retransmission process to conclude for a channel condition. An abort timer dynamic threshold is set to the least amount of time that is necessary for the destination receiver to send a request for re-transmission and for the source transmitter to re-transmit the requested RLP packets) plus some margin to account for variation in delays. A long threshold may cause re-transmission of bigger blocks of data by the layers above the RLP layer. Retransmission at the higher layer may be wasteful because at RLP layer 504 a large portion of the higher layer data may have been received and only a small piece corresponding to the missing the RLP packet is missing. When the value of the threshold for the abort timer is set too short, the retransmission process may be aborted pre-maturely without allowing adequate time for transmitting a NAK message and receiving a retransmission of the missing RLP packet. The receiver may discard the received re-transmitted RLP packets after aborting pre-maturely causing wasteful use of the communication resources. The processor is configured for determining the abort timer dynamic threshold based on statistical data obtained from measuring the periods of time between the time that the request for re-transmission of a missing packet is sent and the time that the requested re-transmission of the missing packet is received. The processor is configured for recording and accumulating data associated with a period of time for completing each successful retransmission of RLP packets for a number of retransmission processes and determining the statistical data based on the accumulated data of the period of times.
[1030] Referring to FIG. 7, a flow chart 700 depicts various steps that may be incorporated for processing of data at the RLP layer 504 in accordance with various aspects of the invention. The processor 401 through operations of received data processing block 402 and transmit data processing block 403 may perform various steps of flow chart 700. At step 701, received data processing block 402 may detect receiving an out of sequence RLP packet of data. The missing RLP packet of data may be the RLP packet "03" as shown in the example in FIG. 6. At step 702, transmit data processing block 403 transmits a NAK message for retransmission of the missing RLP packet of data.
At the same time, an internal timer in processor 401 starts an abort timer at step 703. The abort time is associated with the transmitted NAK message for keeping the lapsed amount of time after transmitting the NAK message. At step 707, the processor 401 determines whether a retransmission of the missing RLP packet is received. At step 704, the elapsed time of the abort timer is compared to an abort period of time dynamic threshold to determine whether the elapsed time has exceeded the dynamic threshold. If the elapsed period of time has exceeded the dynamic threshold, the process flow 700 moves to step 705; otherwise, the process flow continues at step 707. At step 707, the processor 401 may determine that the missing RLP packet has arrived at the destination. In this case, the abort timer associated with the missing MAC
packet terminates and the process flow 700 moves to step 706. At step 705, the processor 401 may consider the missing RLP packet as received when the elapsed time of the abort timer exceeds the abort period of time dynamic threshold at step 704. At step 706, the received in-sequence RLP packets of data are passed on to a higher level of protocol layer. The higher protocol layer may be the PPP protocol layer 503. In accordance with various aspects of the invention, the abort period of time dynamic threshold is determined for controlling flow of data in a manner consistent with an efficient flow of data at all protocol layers including the TCP layer 501. Even though, the processor 401 has no direct control over the process at TCP layer 501, by incorporating various steps of the flow chart 700 an unnecessary retransmission of TCP
packet 506 may be prevented.
(1031] Referring to FIG. 8, a flow chart 800 provides various steps for determining the abort period of time dynamic threshold for controlling flow of data in a manner consistent with an efficient flow of data at all protocol layers.
At step 801, a period of time for completing a successful retransmission process of an RLP packet is recorded. A successful retransmission period may be the elapsed time of the abort timer for a completed successful RLP packet retransmission. At step 802, the period of time for a number of successfully completed retransmissions of RLP packets are accumulated. At step 803, the statistical data, such as average and standard deviation, of the accumulated data are determined. At step 804, the abort period of time dynamic threshold is determined based on the determined statistical data. For example, the dynamic threshold may be set approximately equal to the determined statistical average plus a margin equal to one or two standard deviations. The determined dynamic threshold is used at step 704 for determining whether the elapsed time of the abort timer exceeds the dynamic threshold. The determined dynamic threshold may change from time to time. The change may be due to many factors including the channel condition between the transmitting source and the destination receiver.
[1032] In at least one aspect, when successful retransmission periods become shorter in duration, perhaps due to favorable channel condition, the abort period of time dynamic threshold becomes smaller. The number of NAK
transmissions for a missing MAC packet of data may be restricted to a limited number, such as one or two. After sending the maximum allowed number of NAK messages, the retransmission process has to finish either in success or failure. When the abort period of time dynamic threshold is used at step 704 and determined based on the statistical data at step 804, the retransmission process is concluded within a statistical time period that most likely is possible to lead to a successful retransmission process. If the retransmission process is not concluded within the abort period of time dynamic threshold, the extra wait time may not and most likely would not lead to a successful conclusion of the retransmission process. As such, the retransmission process is controlled in an efficient manner for controlling flow of data from one protocol layer to another.
An unnecessary retransmission of a TCP packet of data may be prevented as a result. Processing data at the RLP protocol layer 504 is made efficient in respect to the ARQ process and flow of data to the higher level protocol layers.
[1033] Those of skill in the art would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
[1034] The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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.
[1035] 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. A software module may reside in RAM memory, flash memory, ROM memory, EPROM
memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
[1036] The previous description of the preferred embodiments is provided to enable any person skilled in the art to make or use the present invention.
The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of the inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[1037] What is claimed is:
Claims (21)
1. In a communication system, a method comprising:
receiving a packet of data;
determining whether said received packet of data is received out of sequence in a series of packets of data;
transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting;
determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
receiving a packet of data;
determining whether said received packet of data is received out of sequence in a series of packets of data;
transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting;
determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
2. The method as recited in claim 1, wherein said packet of data is a radio link protocol (RLP) packet of data, further comprising:
considering as received said missing packet of data when said abort timer exceeds said abort period of time dynamic threshold.
considering as received said missing packet of data when said abort timer exceeds said abort period of time dynamic threshold.
3. The method as recited in claim 2 further comprising:
passing said received in-sequence RLP packets of data to a higher level protocol.
passing said received in-sequence RLP packets of data to a higher level protocol.
4. The method as recited in claim 1 further comprising:
determining said abort period of time dynamic threshold.
determining said abort period of time dynamic threshold.
5. The method as recited in claim 4 wherein said determining said abort period of time dynamic threshold is based on statistical data of periods of time measured for previously received successful retransmissions.
6. The method as recited in claim 5 further comprising:
recording and accumulating a period of time for completing each successful retransmission process for a number of retransmission processes;
determining said statistical data based on said accumulated period of times.
recording and accumulating a period of time for completing each successful retransmission process for a number of retransmission processes;
determining said statistical data based on said accumulated period of times.
7. In a communication system, an apparatus comprising:
a receiver for receiving a packet of data;
a received data processing unit for determining whether said received packet of data is received out of sequence in a series of packets of data;
a transmitter for transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
a processor for starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting and determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
a receiver for receiving a packet of data;
a received data processing unit for determining whether said received packet of data is received out of sequence in a series of packets of data;
a transmitter for transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
a processor for starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting and determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
8. The apparatus as recited in claim 7 wherein said packet of data is a radio link protocol (RLP) packet of data, wherein said processor unit is configured for considering as received said missing packet of data when said abort timer exceeds said abort period of time dynamic threshold.
9. The apparatus as recited in claim 7, wherein said processor is configured for passing, to a higher level protocol, received in-sequence RLP packet of data.
10. The apparatus as recited in claim 7 wherein said processor is configured for determining said abort period of time dynamic threshold.
11. The apparatus as recited in claim 10 wherein said determining said abort period of time dynamic threshold is based on statistical data of periods of time measured for previously received successful retransmissions.
12. The apparatus as recited in claim 11 wherein said processor records and accumulates a period of time for completing a successful retransmission process for a number of retransmission processes and determines said statistical data based on said accumulated period of times.
13. A system for communications of data comprising:
a base station for receiving radio link protocol (RLP) packets of data over a physical layer protocol;
a processor coupled to said base station for passing received in-sequence RLP packets of data;
a network communicatively coupled to said base station for routing data to a destination in accordance with at least one protocol layer including a TCP
protocol layer;
wherein said processor is configured for determining whether a received RLP packet of data is received out of sequence in a series of RLP packets of data and starting an abort timer associated with a transmitted negative acknowledgment for measuring an elapsed time of said abort timer, determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold, considering as received said missing RLP packet of data and performing said passing, to a higher level protocol in said network, said in-sequence RLP packets of data without waiting for receiving retransmission of said missing RLP packet of data when said abort timer exceeds said abort period of time dynamic threshold, thereby preventing at least one of a retransmission of said TCP protocol layer packet of data and scaling back of data traffic in said network
a base station for receiving radio link protocol (RLP) packets of data over a physical layer protocol;
a processor coupled to said base station for passing received in-sequence RLP packets of data;
a network communicatively coupled to said base station for routing data to a destination in accordance with at least one protocol layer including a TCP
protocol layer;
wherein said processor is configured for determining whether a received RLP packet of data is received out of sequence in a series of RLP packets of data and starting an abort timer associated with a transmitted negative acknowledgment for measuring an elapsed time of said abort timer, determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold, considering as received said missing RLP packet of data and performing said passing, to a higher level protocol in said network, said in-sequence RLP packets of data without waiting for receiving retransmission of said missing RLP packet of data when said abort timer exceeds said abort period of time dynamic threshold, thereby preventing at least one of a retransmission of said TCP protocol layer packet of data and scaling back of data traffic in said network
14. The system as recited in claim 13 wherein said processor is configured for determining said abort period of time dynamic threshold based on statistical data of periods of time measured for previously received successful retransmissions of RLP packets of data.
15. The system as recited in claim 14 wherein said processor is configured for recording and accumulating data associated with a period of time for completing each successful retransmission of RLP packets of data for a number of retransmission processes and determining said statistical data based on said accumulated data of said period of times.
16. A processor for use in a data communication system, comprising:
means for determining whether a received packet of data is received out of sequence in a series of packets of data;
means for transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
means for starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting;
means for determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
means for determining whether a received packet of data is received out of sequence in a series of packets of data;
means for transmitting a negative acknowledgment for retransmission of a missing packet of data, wherein said missing packet of data is identified based on said received out of sequence packet of data in said series of packets of data;
means for starting an abort timer associated with said transmitted negative acknowledgment for measuring an elapsed time from a time of said transmitting;
means for determining whether said elapsed time of said abort timer exceeds an abort period of time dynamic threshold.
17. The processor as recited in claim 16, wherein said packet of data is a radio link protocol (RLP) packet of data, further comprising:
means for considering as received said missing packet of data when said abort timer exceeds said abort period of time dynamic threshold.
means for considering as received said missing packet of data when said abort timer exceeds said abort period of time dynamic threshold.
18. The processor as recited in claim 17 further comprising:
means for passing said in-sequence RLP packets of data to a higher level protocol.
means for passing said in-sequence RLP packets of data to a higher level protocol.
19. The processor as recited in claim 16 further comprising:
means for determining said abort period of time dynamic threshold.
means for determining said abort period of time dynamic threshold.
20. The processor as recited in claim 19 wherein said determining said abort period of time dynamic threshold is based on statistical data of periods of time measured for previously received successful retransmissions.
21. The processor as recited in claim 20 further comprising:
recording and accumulating a period of time for completing each successful retransmission process for a number of retransmission processes;
determining said statistical data based on said accumulated period of times.
recording and accumulating a period of time for completing each successful retransmission process for a number of retransmission processes;
determining said statistical data based on said accumulated period of times.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/076,150 | 2002-02-14 | ||
| US10/076,150 US6850769B2 (en) | 2002-02-14 | 2002-02-14 | Method and apparatus for adaptive measurement of round-trip time in ARQ protocols and using the same for controlling flow of data in a communication system |
| PCT/US2003/004795 WO2003069838A1 (en) | 2002-02-14 | 2003-02-13 | Adaptive measurement of round-trip time in automatic retransmission request (arq) protocols and using an abort timer started at receipt of a negative acknowledgement (nak) |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2475161A1 true CA2475161A1 (en) | 2003-08-21 |
Family
ID=27732477
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002475161A Abandoned CA2475161A1 (en) | 2002-02-14 | 2003-02-13 | Adaptive measurement of round-trip time in automatic retransmission request (arq) protocols using an abort timer started at receipt of a negative acknowledgement (nak) |
Country Status (12)
| Country | Link |
|---|---|
| US (1) | US6850769B2 (en) |
| EP (1) | EP1474890A1 (en) |
| JP (2) | JP2005518144A (en) |
| KR (1) | KR20040078160A (en) |
| CN (1) | CN100394715C (en) |
| AU (1) | AU2003217560A1 (en) |
| BR (1) | BR0307640A (en) |
| CA (1) | CA2475161A1 (en) |
| HK (1) | HK1076213A1 (en) |
| MX (1) | MXPA04007873A (en) |
| TW (1) | TWI272810B (en) |
| WO (1) | WO2003069838A1 (en) |
Families Citing this family (69)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7567570B2 (en) * | 2002-03-19 | 2009-07-28 | Network Equipment Technologies, Inc. | Reliable transport of TDM data streams over packet networks |
| US7076717B2 (en) * | 2003-06-13 | 2006-07-11 | Microsoft Corporation | Time-aware best-effort hole-filling retry method and system for network communications |
| DE60311574T2 (en) * | 2003-08-14 | 2007-11-15 | Matsushita Electric Industrial Co., Ltd., Kadoma | Time monitoring of packet re-transmissions during a soft handoff |
| US20050043035A1 (en) * | 2003-08-21 | 2005-02-24 | Diesen Michael J. | Method and apparatus for providing multimedia broadcast multicast service data to a subscriber to a multimedia broadcast multicast service |
| US20050122977A1 (en) * | 2003-12-05 | 2005-06-09 | Microsoft Corporation | Efficient download mechanism for devices with limited local storage |
| US7197026B2 (en) * | 2003-12-23 | 2007-03-27 | Nokia Corporation | Method and system for RLP optimization |
| JP4452983B2 (en) * | 2004-01-08 | 2010-04-21 | ソニー株式会社 | Receiving apparatus and method, program, and recording medium |
| US8018945B2 (en) * | 2004-04-29 | 2011-09-13 | Interdigital Technology Corporation | Method and apparatus for forwarding non-consecutive data blocks in enhanced uplink transmissions |
| US8009586B2 (en) | 2004-06-29 | 2011-08-30 | Damaka, Inc. | System and method for data transfer in a peer-to peer hybrid communication network |
| US7778187B2 (en) * | 2004-06-29 | 2010-08-17 | Damaka, Inc. | System and method for dynamic stability in a peer-to-peer hybrid communications network |
| US7933260B2 (en) | 2004-06-29 | 2011-04-26 | Damaka, Inc. | System and method for routing and communicating in a heterogeneous network environment |
| US7570636B2 (en) | 2004-06-29 | 2009-08-04 | Damaka, Inc. | System and method for traversing a NAT device for peer-to-peer hybrid communications |
| US8050272B2 (en) | 2004-06-29 | 2011-11-01 | Damaka, Inc. | System and method for concurrent sessions in a peer-to-peer hybrid communications network |
| US20070078720A1 (en) * | 2004-06-29 | 2007-04-05 | Damaka, Inc. | System and method for advertising in a peer-to-peer hybrid communications network |
| US7656870B2 (en) | 2004-06-29 | 2010-02-02 | Damaka, Inc. | System and method for peer-to-peer hybrid communications |
| US8437307B2 (en) | 2007-09-03 | 2013-05-07 | Damaka, Inc. | Device and method for maintaining a communication session during a network transition |
| US7623516B2 (en) * | 2004-06-29 | 2009-11-24 | Damaka, Inc. | System and method for deterministic routing in a peer-to-peer hybrid communications network |
| US7623476B2 (en) * | 2004-06-29 | 2009-11-24 | Damaka, Inc. | System and method for conferencing in a peer-to-peer hybrid communications network |
| WO2006073279A1 (en) | 2005-01-06 | 2006-07-13 | Lg Electronics Inc. | Improvements to high speed uplink packet access scheme |
| US7768961B2 (en) * | 2005-05-03 | 2010-08-03 | Interdigital Technology Corporation | Wireless communication method and apparatus for reliably transmitting data |
| US7480510B1 (en) * | 2005-10-24 | 2009-01-20 | Sprint Spectrum L.P. | Method and apparatus for preventing paging channel overload |
| US7792026B2 (en) * | 2006-02-17 | 2010-09-07 | Alcatel-Lucent Usa Inc. | Method of calculating a time period to wait for missing data packets |
| US8462727B2 (en) * | 2006-03-10 | 2013-06-11 | Motorola Mobility Llc | Method and system for streamlined call setup |
| JP4971674B2 (en) * | 2006-04-27 | 2012-07-11 | 日立情報通信エンジニアリング株式会社 | Multilevel encryption communication method and system |
| US20090006910A1 (en) * | 2007-06-27 | 2009-01-01 | Belal Hamzeh | Selective hybrid arq |
| CN101127587B (en) * | 2007-09-25 | 2011-12-28 | 中兴通讯股份有限公司 | A method for triggering automatic retransfer request status report |
| US8862164B2 (en) * | 2007-09-28 | 2014-10-14 | Damaka, Inc. | System and method for transitioning a communication session between networks that are not commonly controlled |
| WO2009070718A1 (en) | 2007-11-28 | 2009-06-04 | Damaka, Inc. | System and method for endpoint handoff in a hybrid peer-to-peer networking environment |
| US8199758B2 (en) * | 2008-02-13 | 2012-06-12 | Qualcomm Incorporated | Variable abort timer |
| EP2173054A1 (en) * | 2008-10-06 | 2010-04-07 | Thomson Licensing | Method for receiving and transmitting data blocks |
| US8725895B2 (en) | 2010-02-15 | 2014-05-13 | Damaka, Inc. | NAT traversal by concurrently probing multiple candidates |
| US8892646B2 (en) | 2010-08-25 | 2014-11-18 | Damaka, Inc. | System and method for shared session appearance in a hybrid peer-to-peer environment |
| US8874785B2 (en) | 2010-02-15 | 2014-10-28 | Damaka, Inc. | System and method for signaling and data tunneling in a peer-to-peer environment |
| US8689307B2 (en) * | 2010-03-19 | 2014-04-01 | Damaka, Inc. | System and method for providing a virtual peer-to-peer environment |
| US9043488B2 (en) | 2010-03-29 | 2015-05-26 | Damaka, Inc. | System and method for session sweeping between devices |
| US9191416B2 (en) | 2010-04-16 | 2015-11-17 | Damaka, Inc. | System and method for providing enterprise voice call continuity |
| US8352563B2 (en) | 2010-04-29 | 2013-01-08 | Damaka, Inc. | System and method for peer-to-peer media routing using a third party instant messaging system for signaling |
| US8446900B2 (en) | 2010-06-18 | 2013-05-21 | Damaka, Inc. | System and method for transferring a call between endpoints in a hybrid peer-to-peer network |
| US8611540B2 (en) | 2010-06-23 | 2013-12-17 | Damaka, Inc. | System and method for secure messaging in a hybrid peer-to-peer network |
| US8468010B2 (en) | 2010-09-24 | 2013-06-18 | Damaka, Inc. | System and method for language translation in a hybrid peer-to-peer environment |
| US8743781B2 (en) | 2010-10-11 | 2014-06-03 | Damaka, Inc. | System and method for a reverse invitation in a hybrid peer-to-peer environment |
| US8503308B1 (en) | 2010-10-29 | 2013-08-06 | Sprint Communications Company L.P. | Page routing system |
| KR101443237B1 (en) * | 2010-11-05 | 2014-09-23 | 텔레콤 이탈리아 소시에떼 퍼 아찌오니 | Measurement on a data flow in a communication network |
| US8761147B2 (en) * | 2011-01-17 | 2014-06-24 | Texas Instruments Incorporated | Selective protection based on sequence numbers in coexisting networks |
| US8407314B2 (en) | 2011-04-04 | 2013-03-26 | Damaka, Inc. | System and method for sharing unsupported document types between communication devices |
| US8885464B2 (en) * | 2011-04-28 | 2014-11-11 | Bio-Signal Group Corp. | Wireless EEG data recovery |
| US8694587B2 (en) | 2011-05-17 | 2014-04-08 | Damaka, Inc. | System and method for transferring a call bridge between communication devices |
| US8478890B2 (en) | 2011-07-15 | 2013-07-02 | Damaka, Inc. | System and method for reliable virtual bi-directional data stream communications with single socket point-to-multipoint capability |
| US10462690B2 (en) | 2011-08-05 | 2019-10-29 | Telefonaktiebolaget Lm Ericsson (Publ) | RLC status reporting for eight-carrier HSDPA |
| WO2014089798A1 (en) | 2012-12-13 | 2014-06-19 | Thomson Licensing | Method and apparatus for error control in 3d video transmission |
| US9027032B2 (en) | 2013-07-16 | 2015-05-05 | Damaka, Inc. | System and method for providing additional functionality to existing software in an integrated manner |
| US9357016B2 (en) | 2013-10-18 | 2016-05-31 | Damaka, Inc. | System and method for virtual parallel resource management |
| WO2016022574A1 (en) | 2014-08-05 | 2016-02-11 | Damaka, Inc. | System and method for providing unified communications and collaboration (ucc) connectivity between incompatible systems |
| US9998360B2 (en) * | 2014-11-17 | 2018-06-12 | Honeywell International Inc. | Minimizining message propagation times when brief datalink interruptions occur |
| US9660719B2 (en) | 2014-11-17 | 2017-05-23 | Honeywell International Inc. | Minimizing propagation times of queued-up datalink TPDUs |
| US9742587B2 (en) | 2015-07-29 | 2017-08-22 | Oracle International Corporation | Negative acknowledgment of tunneled encapsulated media |
| US10608985B2 (en) | 2015-08-14 | 2020-03-31 | Oracle International Corporation | Multihoming for tunneled encapsulated media |
| US10091025B2 (en) | 2016-03-31 | 2018-10-02 | Damaka, Inc. | System and method for enabling use of a single user identifier across incompatible networks for UCC functionality |
| US10153980B2 (en) | 2016-07-19 | 2018-12-11 | Coco Communications Corp | Systems and methods for managing network congestion |
| US10812216B2 (en) | 2018-11-05 | 2020-10-20 | XCOM Labs, Inc. | Cooperative multiple-input multiple-output downlink scheduling |
| US10659112B1 (en) | 2018-11-05 | 2020-05-19 | XCOM Labs, Inc. | User equipment assisted multiple-input multiple-output downlink configuration |
| US10432272B1 (en) | 2018-11-05 | 2019-10-01 | XCOM Labs, Inc. | Variable multiple-input multiple-output downlink user equipment |
| US10756860B2 (en) | 2018-11-05 | 2020-08-25 | XCOM Labs, Inc. | Distributed multiple-input multiple-output downlink configuration |
| US10756795B2 (en) | 2018-12-18 | 2020-08-25 | XCOM Labs, Inc. | User equipment with cellular link and peer-to-peer link |
| US11063645B2 (en) | 2018-12-18 | 2021-07-13 | XCOM Labs, Inc. | Methods of wirelessly communicating with a group of devices |
| US11330649B2 (en) | 2019-01-25 | 2022-05-10 | XCOM Labs, Inc. | Methods and systems of multi-link peer-to-peer communications |
| US10756767B1 (en) | 2019-02-05 | 2020-08-25 | XCOM Labs, Inc. | User equipment for wirelessly communicating cellular signal with another user equipment |
| US11902343B1 (en) | 2021-04-19 | 2024-02-13 | Damaka, Inc. | System and method for highly scalable browser-based audio/video conferencing |
| US11770584B1 (en) | 2021-05-23 | 2023-09-26 | Damaka, Inc. | System and method for optimizing video communications based on device capabilities |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0477055A (en) * | 1990-07-16 | 1992-03-11 | Canon Inc | Still picture transmitter |
| US6088342A (en) * | 1997-05-05 | 2000-07-11 | Nokia Mobile Phones Limited | Dynamic configuration of radio link protocol in a telecommunications system |
| JPH0983775A (en) * | 1995-09-19 | 1997-03-28 | Fuji Xerox Co Ltd | Facsimile equipment |
| US5815667A (en) * | 1995-11-28 | 1998-09-29 | Ncr Corporation | Circuits and methods for intelligent acknowledgement based flow control in a processing system network |
| US6408003B1 (en) * | 1997-06-17 | 2002-06-18 | Qualcomm Incorporated | Method and apparatus for resolving ambiguity in reception of multiple retransmitted frames |
| US6076181A (en) * | 1998-03-03 | 2000-06-13 | Nokia Mobile Phones Limited | Method and apparatus for controlling a retransmission/abort timer in a telecommunications system |
| US6519233B1 (en) * | 1998-06-12 | 2003-02-11 | Nortel Networks, Ltd. | Subscriber unit burst mode reservation in a code division multiple access wireless communication system |
| US6473399B1 (en) * | 1998-11-30 | 2002-10-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for determining an optimum timeout under varying data rates in an RLC wireless system which uses a PDU counter |
| JP2000261496A (en) * | 1999-03-04 | 2000-09-22 | Toshiba Corp | Radio communication equipment |
| KR100416996B1 (en) | 1999-05-10 | 2004-02-05 | 삼성전자주식회사 | Variable-length data transmitting and receiving apparatus in accordance with radio link protocol for a mobile telecommunication system and method thereof |
| US6208620B1 (en) * | 1999-08-02 | 2001-03-27 | Nortel Networks Corporation | TCP-aware agent sublayer (TAS) for robust TCP over wireless |
| EP1077559A1 (en) * | 1999-08-17 | 2001-02-21 | Telefonaktiebolaget Lm Ericsson | Method and device for determining a time-parameter |
| US6608818B1 (en) | 1999-11-10 | 2003-08-19 | Qualcomm Incorporated | Radio link protocol enhancements to reduce setup time for data calls |
| JP2001326965A (en) * | 2000-05-15 | 2001-11-22 | Kobe Steel Ltd | Method and device for wireless data communication |
-
2002
- 2002-02-14 US US10/076,150 patent/US6850769B2/en not_active Expired - Lifetime
-
2003
- 2003-02-13 BR BR0307640-7A patent/BR0307640A/en not_active IP Right Cessation
- 2003-02-13 KR KR10-2004-7012314A patent/KR20040078160A/en active IP Right Grant
- 2003-02-13 MX MXPA04007873A patent/MXPA04007873A/en active IP Right Grant
- 2003-02-13 WO PCT/US2003/004795 patent/WO2003069838A1/en active Application Filing
- 2003-02-13 CN CNB038039834A patent/CN100394715C/en not_active Expired - Fee Related
- 2003-02-13 AU AU2003217560A patent/AU2003217560A1/en not_active Abandoned
- 2003-02-13 CA CA002475161A patent/CA2475161A1/en not_active Abandoned
- 2003-02-13 EP EP03713512A patent/EP1474890A1/en not_active Withdrawn
- 2003-02-13 JP JP2003568832A patent/JP2005518144A/en not_active Withdrawn
- 2003-02-14 TW TW092103085A patent/TWI272810B/en active
-
2005
- 2005-09-20 HK HK05108202.2A patent/HK1076213A1/en not_active IP Right Cessation
-
2010
- 2010-07-02 JP JP2010152222A patent/JP2010283844A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| JP2005518144A (en) | 2005-06-16 |
| MXPA04007873A (en) | 2004-10-15 |
| KR20040078160A (en) | 2004-09-08 |
| TWI272810B (en) | 2007-02-01 |
| TW200307435A (en) | 2003-12-01 |
| WO2003069838A1 (en) | 2003-08-21 |
| US6850769B2 (en) | 2005-02-01 |
| AU2003217560A1 (en) | 2003-09-04 |
| CN1633772A (en) | 2005-06-29 |
| HK1076213A1 (en) | 2006-01-06 |
| JP2010283844A (en) | 2010-12-16 |
| BR0307640A (en) | 2005-02-22 |
| US20030181214A1 (en) | 2003-09-25 |
| CN100394715C (en) | 2008-06-11 |
| EP1474890A1 (en) | 2004-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6850769B2 (en) | Method and apparatus for adaptive measurement of round-trip time in ARQ protocols and using the same for controlling flow of data in a communication system | |
| US6980514B2 (en) | Method and apparatus for controlling flow of data in a communication system | |
| US6920504B2 (en) | Method and apparatus for controlling flow of data in a communication system | |
| AU2008219352B2 (en) | Method and apparatus for augmenting physical layer ARQ in a wireless data communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |