EP2661846B1 - Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput - Google Patents

Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput Download PDF

Info

Publication number
EP2661846B1
EP2661846B1 EP11808111.6A EP11808111A EP2661846B1 EP 2661846 B1 EP2661846 B1 EP 2661846B1 EP 11808111 A EP11808111 A EP 11808111A EP 2661846 B1 EP2661846 B1 EP 2661846B1
Authority
EP
European Patent Office
Prior art keywords
packets
rate
data
parameters
tcp
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.)
Active
Application number
EP11808111.6A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2661846A1 (en
Inventor
Navid Ehsan
Thomas Klingenbrunn
Gang A. Xiao
Jon J. Anderson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2661846A1 publication Critical patent/EP2661846A1/en
Application granted granted Critical
Publication of EP2661846B1 publication Critical patent/EP2661846B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/19—Flow control; Congestion control at layers above the network layer
    • H04L47/193—Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • aspects of the present disclosure generally relate to wireless communication and, more particularly, downlink flow control based on limitations at a user equipment (UE).
  • UE user equipment
  • Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, 3 rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, and Orthogonal Frequency Division Multiple Access (OFDMA) systems.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • OFDMA Orthogonal Frequency Division Multiple Access
  • a wireless multiple-access communication system can simultaneously support communication for multiple wireless terminals.
  • Each terminal communicates with one or more base stations via transmissions on the forward and reverse links.
  • the forward link (or downlink) refers to the communication link from the base stations to the terminals
  • the reverse link (or uplink) refers to the communication link from the terminals to the base stations.
  • the forward communication link and the reverse communication link may be established via a single-input single-output, multiple-input single-output or a multiple-input multiple-output system.
  • a wireless multiple-access communication system can support a time division duplex (TDD) and frequency division duplex (FDD) systems.
  • TDD time division duplex
  • FDD frequency division duplex
  • the forward and reverse link transmissions are on the same frequency region so that the reciprocity principle allows the estimation of the forward link channel from the reverse link channel. This enables the access point to extract transmit beamforming gain on the forward link when multiple antennas are available at the access point.
  • the 3GPP LTE represents a major advance in cellular technology and it is a next step forward in cellular 3 rd generation (3G) services as a natural evolution of Global System for Mobile Communications (GSM) and Universal Mobile Telecommunications System (UMTS).
  • the LTE provides for an uplink speed of up to 75 megabits per second (Mbps) and a downlink speed of up to 300 Mbps, and brings many technical benefits to cellular networks.
  • the LTE is designed to meet carrier needs for high-speed data and media transport as well as high-capacity voice support.
  • the bandwidth may be scalable from 1.25 MHz to 20 MHz. This suits the requirements of different network operators that have different bandwidth allocations, and also allows operators to provide different services based on spectrum.
  • the LTE is also expected to improve spectral efficiency in 3G networks, allowing carriers to provide more data and voice services over a given bandwidth.
  • Physical layer (PHY) of the LTE standard is a highly efficient means of conveying both data and control information between an enhanced base station (eNodeB) and mobile user equipment (UE).
  • the LTE PHY employs advanced technologies that are new to cellular applications. These include Orthogonal Frequency Division Multiplexing (OFDM) and Multiple Input Multiple Output (MIMO) data transmission.
  • OFDM Orthogonal Frequency Division Multiplexing
  • MIMO Multiple Input Multiple Output
  • the LTE PHY uses OFDMA on the downlink and Single Carrier - Frequency Division Multiple Access (SC-FDMA) on the uplink. OFDMA allows data to be directed to or from multiple users on a subcarrier-by-subcarrier basis for a specified number of symbol periods.
  • SC-FDMA Single Carrier - Frequency Division Multiple Access
  • 3GPP LTE Release 8 specifications provide a set of frequency bands on which an LTE system can be deployed.
  • the usage of bands can vary from country to country based on prevalent frequency allocation policies.
  • an actual carrier frequency being utilized can also vary from one service provider to another.
  • the 3GPP USIM UMTS Subscriber Identity Module
  • PLMN IDs Public Land Mobile Network Identifications
  • MCC Mobile Country Code
  • NCC Network Color Code
  • the PLMN ID may not provide an indication about a band to be used, and, also, it may not comprise information about a specific carrier frequency on which a desired service provider exists.
  • User equipment (UE) operating in the LTE system may be supposed to learn and maintain an adaptive list of carrier frequencies and band information as it successfully acquires services in various countries and service providers. Hence, the UE may be required to always perform a frequency scan when attempting initial acquisition.
  • EP2077688 (A2 ) which describes a control method in a mobile communication system with a buffer unit for temporarily storing packet data to be sent, includes dropping the packet data stored in the buffer unit before sending when a drop timer corresponding to the packet data before sending reaches a given value or when a drop condition required by a drop mechanism accompanying the buffer unit is satisfied, and dropping the packet data stored in the buffer unit after sending when a drop timer corresponding to the packet data after sending reaches a given value.
  • a PDCP layer sets a timer and discards a PDCP SDU upon expiration of the timer.
  • the timer may be set upon receiving the PDCP SDU from an upper layer or upon submitting the PDCP SDU to a lower layer for transmission.
  • the timer and a radio link control (RLC) discard timer may be coordinated.
  • the PDCP layer may discard the PDCP SDL1 based on a notification from an RLC layer or based on a PDCP status report.
  • a sender transmits a network packet to a receiver.
  • the receiver selectively delays sending an acknowledgement to the sender for the received network packet.
  • the selective delay is based on the priority of the sender vis-à-vis other senders or based on a desired transmission rate for the sender.
  • the sender transmits another network packet after receiving the acknowledgment.
  • internet protocol data is generated at a data source device.
  • the generated data is communicated to one or more network devices and received at the one or more network devices. Portions of the generated data are selectively deleted based on specified criteria in order to effect improved data flow of the generated data.
  • the specified criteria selected from the group consisting of time since last drop, number of packets since last dropped, packet protocol, packet size and combinations thereof.
  • the generated data is communicated via flow controllable interface.
  • a method for wireless communications generally includes monitoring, by a user equipment (UE), one or more parameters related to the UE, and selectively dropping received packets based on the one or more parameters in order to trigger a rate control mechanism in the UE.
  • UE user equipment
  • an apparatus for wireless communications generally includes means for means for monitoring, by a user equipment (UE), one or more parameters related to the UE, and means for selectively dropping received packets based on the one or more parameters in order to trigger a rate control mechanism in the UE.
  • UE user equipment
  • an apparatus for wireless communications generally includes at least one processor and a memory coupled to the at least one processor.
  • the at least one processor is generally configured to monitor, by a user equipment (UE), one or more parameters related to the UE, and selectively drop received packets based on the one or more parameters in order to trigger a rate control mechanism in the UE.
  • UE user equipment
  • a computer-program product for wireless communications generally includes a non-transitory computer-readable medium having code stored thereon.
  • the code is generally executable by one or more processors for monitoring, by a user equipment
  • UE one or more parameters related to the UE, and selectively dropping received packets based on the one or more parameters in order to trigger a rate control mechanism in the UE.
  • aspects of the present disclosure use system triggers such as, for example, temperature of a device, available memory, and/or processing power to trigger downlink flow control at a user equipment (UE).
  • IP internet protocol
  • PDCP packet data convergence protocol
  • TCP transmission control protocol
  • aspects of the present disclosure allow a UE to reduce a downlink data rate in an effort to enhance user experience and free resources.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • SC-FDMA Single-Carrier FDMA
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR).
  • CDMA2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM®, etc.
  • E-UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunication System (UMTS).
  • LTE Long Term Evolution
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • CDMA2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • An access point may comprise, be implemented as, or known as NodeB, Radio Network Controller (“RNC”), eNodeB (“eNB”), Base Station Controller (“BSC”), Base Transceiver Station (“BTS”), Base Station (“BS”), Transceiver Function (“TF”), Radio Router, Radio Transceiver, Basic Service Set (“BSS”), Extended Service Set (“ESS”), Radio Base Station (“RBS”), or some other terminology.
  • RNC Radio Network Controller
  • eNB eNodeB
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • BS Base Station
  • Transceiver Function TF
  • Radio Router Radio Transceiver
  • BSS Basic Service Set
  • ESS Extended Service Set
  • RBS Radio Base Station
  • An access terminal may comprise, be implemented as, or known as an access terminal, a subscriber station, a subscriber unit, a mobile station, a remote station, a remote terminal, a user terminal, a user agent, a user device, user equipment ("UE"), a user station, or some other terminology.
  • an access terminal may comprise a cellular telephone, a cordless telephone, a Session Initiation Protocol ("SIP”) phone, a wireless local loop (“WLL”) station, a personal digital assistant (“PDA”), a handheld device having wireless connection capability, a Station (“STA”), or some other suitable processing device connected to a wireless modem.
  • SIP Session Initiation Protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • STA Station
  • a phone e.g., a cellular phone or smart phone
  • a computer e.g., a laptop
  • a portable communication device e.g., a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music or video device, or a satellite radio), a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • the node is a wireless node.
  • Such wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link.
  • An access point 100 may include multiple antenna groups, one group including antennas 104 and 106, another group including antennas 108 and 110, and an additional group including antennas 112 and 114. In FIG. 1 , only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group.
  • Access terminal 116 may be in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118.
  • Access terminal 122 may be in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal 122 over forward link 126 and receive information from access terminal 122 over reverse link 124.
  • communication links 118, 120, 124 and 126 may use different frequency for communication.
  • forward link 120 may use a different frequency than that used by reverse link 118.
  • Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access point.
  • each antenna group may be designed to communicate to access terminals in a sector of the areas covered by access point 100.
  • the transmitting antennas of access point 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 124. Also, an access point using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access point transmitting through a single antenna to all its access terminals.
  • FIG. 2 illustrates a block diagram of an aspect of a transmitter system 210 (also known as the access point) and a receiver system 250 (also known as the access terminal) in a multiple-input multiple-output (MIMO) system 200.
  • a transmitter system 210 also known as the access point
  • a receiver system 250 also known as the access terminal
  • MIMO multiple-input multiple-output
  • traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.
  • TX transmit
  • each data stream may be transmitted over a respective transmit antenna.
  • TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
  • the coded data for each data stream may be multiplexed with pilot data using OFDM techniques.
  • the pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response.
  • the multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols.
  • a particular modulation scheme e.g., BPSK, QSPK, M-PSK, or M-QAM
  • the data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.
  • TX MIMO processor 220 may further process the modulation symbols (e.g., for OFDM).
  • TX MIMO processor 220 then provides N T modulation symbol streams to N T transmitters (TMTR) 222a through 222t.
  • TMTR TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
  • Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel.
  • N T modulated signals from transmitters 222a through 222t are then transmitted from N T antennas 224a through 224t, respectively.
  • the transmitted modulated signals may be received by N R antennas 252a through 252r and the received signal from each antenna 252 may be provided to a respective receiver (RCVR) 254a through 254r.
  • Each receiver 254 may condition (e.g., filters, amplifies, and downconverts) a respective received signal, digitize the conditioned signal to provide samples, and further process the samples to provide a corresponding "received" symbol stream.
  • An RX data processor 260 then receives and processes the N R received symbol streams from N R receivers 254 based on a particular receiver processing technique to provide N T "detected" symbol streams.
  • the RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream.
  • the processing by RX data processor 260 may be complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.
  • a processor 270 periodically determines which pre-coding matrix to use.
  • Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.
  • the reverse link message may comprise various types of information regarding the communication link and/or the received data stream.
  • the reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to transmitter system 210.
  • the modulated signals from receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250.
  • Processor 230 determines which pre-coding matrix to use for determining the beamforming weights, and then processes the extracted message.
  • FIG. 3 illustrates various components that may be utilized in a wireless device 302 that may be employed within the wireless communication system from FIG. 1 .
  • the wireless device 302 is an example of a device that may be configured to implement the various methods described herein.
  • the wireless device 302 may be an access point 100 from FIG. 1 or any of access terminals 116, 122.
  • the wireless device 302 may include a processor 304 which controls operation of the wireless device 302.
  • the processor 304 may also be referred to as a central processing unit (CPU).
  • Memory 306 which may include both read-only memory (ROM) and random access memory (RAM), provides instructions and data to the processor 304.
  • a portion of the memory 306 may also include non-volatile random access memory (NVRAM).
  • the processor 304 typically performs logical and arithmetic operations based on program instructions stored within the memory 306.
  • the instructions in the memory 306 may be executable to implement the methods described herein.
  • the wireless device 302 may also include a housing 308 that may include a transmitter 310 and a receiver 312 to allow transmission and reception of data between the wireless device 302 and a remote location.
  • the transmitter 310 and receiver 312 may be combined into a transceiver 314.
  • a single or a plurality of transmit antennas 316 may be attached to the housing 308 and electrically coupled to the transceiver 314.
  • the wireless device 302 may also include (not shown) multiple transmitters, multiple receivers, and multiple transceivers.
  • the wireless device 302 may also include a signal detector 318 that may be used in an effort to detect and quantify the level of signals received by the transceiver 314.
  • the signal detector 318 may detect such signals as total energy, energy per subcarrier per symbol, power spectral density and other signals.
  • the wireless device 302 may also include a digital signal processor (DSP) 320 for use in processing signals.
  • the wireless device 302 may include one or more monitors, for example, a temperature monitor 321.
  • the temperature monitor 321 is configured to measure the temperatures of one or more components of the wireless device 302 (e.g., a power amplifier, not shown). While the monitor is shown as a temperature monitor 321 in FIG. 3 , it is contemplated that certain aspects of the present disclosure may utilize other suitable monitors, including but not limited to a CPU monitor and a memory monitor, having one or more corresponding sensor components for detecting one or more UE parameters or metrics.
  • the various components of the wireless device 302 may be coupled together by a bus system 322, which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus.
  • a bus system 322 may include a power bus, a control signal bus, and a status signal bus in addition to a data bus.
  • the frequency scan may be performed without any prior acquisition information at the mobile device, which may be referred to as Full Frequency Scan (FFS).
  • the frequency scan may be performed using prior successful acquisition information stored at the mobile device, which may be referred to as List Frequency Scan (LFS).
  • FLS List Frequency Scan
  • the 3GPP LTE system may be deployed using either frequency division duplex (FDD) mode or time division duplex (TDD) mode.
  • the proposed frequency scan algorithms i.e., the FFS and LFS
  • downlink flow control may be desirable to regulate how an applications subsystem receives and processes data packets.
  • System triggers such as, for example, memory size, processing power, and/or acceptable device temperature may be used to trigger downlink flow control.
  • the UE may selectively drop packets to control the transmission control protocol (TCP) throughput, in an effort to free resources at the UE.
  • TCP transmission control protocol
  • packets may be selectively dropped at a packet data convergence protocol (PDCP) layer, before the packets are transferred to an applications layer.
  • PDCP packet data convergence protocol
  • a UE may implement active buffer management to trigger a rate control mechanism in an effort to control downlink flow.
  • Rate control may be performed by threshold based methods, which may include centralized flow control.
  • buffer management may be performed closer to the source of congestion and may allow downlink rate control without using additional network resources.
  • FIG. 4 illustrates an example system architecture 400 according to aspects of the present disclosure.
  • An eNB 402 may transmit packets to a modem processor 404 of a UE via a communication link, such as an LTE link 406.
  • Modem processor 404 may transmit packets to an applications processor 408.
  • a TCP client 410 may transmit TCP acknowledgments and/or negative acknowledgments to a TCP server 412.
  • While the applications processor 408 may receive packets at any rate, in certain scenarios, it may not be able to process the received packets as quickly as they are arriving on the LTE link 406.
  • downlink flow control methods described herein may be implemented to help free resources at a UE. For example, it may be desirable to set thresholds for buffers in an effort to avoid data loss in bursts and temporary timing out of the TCP. Buffer thresholds may depend on a rate at which the applications processor 408 processes received data.
  • the UE may provide an interface for the applications processor 408 to determine a desired rate.
  • an applications programming interface API may allow the applications processor 408 to provide the modem processor 404 with a desired processing rate.
  • the desired rate may be used to tune one or more buffer thresholds and/or a packet dropping rate.
  • a UE may implement centralized downlink flow control. Centralized flow control may be triggered based on a memory-related parameter, for example, if the UE begins to run out of global memory. A UE may begin to run out of memory, for example distributed shared memory (DSM) items, when the UE has too much data stored in uplink and downlink buffers.
  • DSM distributed shared memory
  • the UE may drop TCP packets. For example, the UE may periodically drop TCP packets based on a default time period. The default time period may be dictated by a dynamic algorithm which will be described in more detail below.
  • FIG. 5 illustrates an example of threshold based flow control 500 in accordance with aspects of the present disclosure.
  • Downlink packets received by a UE may reach the PDCP layer 502 of the modem subsystem 508.
  • the applications subsystem 504 may be unable to process the received packets (e.g., packets successfully received by the PDCP layer 502).
  • one or more thresholds may be set such that delay on the receive path is below a threshold.
  • a threshold may ensure that the delay between the radio link control (RLC) and applications subsystem 504 is less than a value (e.g., 80 msec).
  • RLC radio link control
  • the UE may periodically drop packets in order to reduce a TCP window size.
  • the PDCP layer 502 may selectively drop received packets. According to aspects, selectively dropping packets may occur prior to transferring the packets from a modem to an applications processor. Dropped packets will not be received at the applications subsystem 504 or the TCP client. Thus, dropped packets at the applications layer may indicate that the TCP layer may need to reduce its rate.
  • the TCP client may transmit a TCP negative acknowledgement (NACK) when it does not receive a dropped packet and/or duplicate acknowledgments for previously received packets to the TCP server.
  • NACK TCP negative acknowledgement
  • Such negative acknowledgments and/or duplicate acknowledgments for previously received packets may cause a reduction in the TCP window size thereby reducing the TCP throughput. Accordingly, a load on the PDCP layer may be reduced.
  • FIG. 6 illustrates an example 600 of centralized downlink flow control based parameters monitored at a UE.
  • a UE may monitor one or more parameters including a temperature-related parameter, processing power-related parameter and/or memory-related parameter.
  • a temperature monitor 602 may observe the temperature of one or more devices at the UE including, for example, a modem and a battery. Since battery temperature is typically related to an uplink transmit power, according to aspects, the temperature monitor 602 may observe the battery temperature after the uplink data rate has reached a rate (e.g., a maximum or minimum rate).
  • a DSM monitor 604 may observe the available global memory at a UE by observing DSM item availability.
  • a centralized flow control module (CFM) 606 may determine whether to trigger downlink flow control based on the one or more parameters received from one or more monitors or sensors, for example, the temperature monitor 602 and DSM monitor 604. As described above with reference to FIG. 5 , the PDCP layer 502 may periodically drop packets in order to reduce a TCP window size based on the observed parameters.
  • CFM centralized flow control module
  • the CFM 606 may indicate to the PDCP layer 502 to adjust a rate at which packets are dropped. Adjusting the rate at which packets are dropped may trigger a rate control mechanism at the UE. For example, a high battery or modem temperature and/or a limited number of DSM items may indicate that the PDCP layer should increase the rate at which packets are dropped in an effort to reduce downlink flow. Consequently, UE TCP NACKs and/or duplicate acknowledgements may increase which may cause a reduction in TCP window size thereby providing downlink rate flow control.
  • the packet drop rate may be updated based on a received indication from the CFM 606.
  • the updated drop rate may adjust the rate at which packets are dropped from the PDCP layer and, consequently, adjust the rate at which packets are buffered, at 610.
  • PDCP packets greater than a predetermined size may be selectively dropped when the CFM 606 triggers downlink flow control.
  • the predetermined size may be selected to be greater than a size of expected control packets. Selectively dropping only packets larger than, for example, 200 bytes may ensure that TCP acknowledgments are not dropped. By not dropping packets which are below the predetermined threshold, including TCP acknowledgments, the UE may ensure dropped packets have an effect on the downlink flow control.
  • FIG. 7 illustrates an example downlink flow control method 700, according to aspects of the present disclosure.
  • the applications processor 408 may provide the modem with a desired rate for receiving data.
  • An API may allow the applications processor 408 to provide the modem subsystem with a desired processing rate.
  • the desired rate may be used to tune a buffer threshold and packet dropping rate.
  • the applications processor 408 may determine a desired target rate 702 and transmit the rate to the PDCP layer 502 of the modem subsystem.
  • the UE may not need to dynamically adjust a drop rate of PDCP packets. Instead, the UE may adjust the buffering of packets based on the desired output target rate of the applications processor 408.
  • the first threshold T1 may be calculated based on the desired output rate of the applications processor and the TCP round trip time (rtt).
  • the TCP round trip time may not be available at the PDCP layer.
  • the UE may determine the round trip time based on, for example, a cumulative distributive function of TCP round trip time.
  • the round trip time may be set to a worst case rtt.
  • the rtt may not exceed a value, such as 200 ms, and may be set to, for example, 60 msec.
  • other values may be employed.
  • the UE may determine a number of packets n that may be dropped, after reaching the threshold T1, based on the rate provided by the applications processor, TCP rtt, and a maximum TCP segment size (MSS).
  • the MSS may be set to a value, such as 1400 bytes. However, other values may be employed.
  • threshold T2 after reaching a second threshold T2, all incoming packets may be dropped.
  • the second threshold T2 may indicate a maximum amount of data that may be stored in a buffer. Thus, after reaching threshold T2, all incoming packets may be dropped.
  • a buffer may reach threshold T2, for example, if previous flow control methods did not free up enough resources at the UE.
  • threshold T2 may be any value larger (e.g., sufficiently larger) than threshold T1.
  • a target rate may be selected based on available information at the UE.
  • the selected target rate may be used to calculate T1, T2, and/or n .
  • FIG. 8 illustrates an example 800 buffer threshold based flow control, according to aspects of the present disclosure.
  • a target output rate of an applications processor may be tracked. The rate may be determined by the applications processor and transmitted to the modem, or may be estimated based on available information at the UE.
  • parameters for downlink flow control, T1, T2, and/or n may be calculated at 804.
  • T1 may be calculated using some delay D
  • n may be calculated using a coefficient K1
  • T2 may be calculated using a coefficient K2.
  • thresholds T1 and T2 may be used as thresholds to trigger downlink flow control at the PDCP layer. For example, when a buffer reaches threshold T1, one out of n packets may be dropped. The packets may be dropped prior to transferring them from a modem to an applications processor. If a buffer threshold T2 is reached, all incoming packets from the modem may be dropped.
  • Packets that are passed from the modem to the applications processor may be buffered at 810.
  • the average delay observed by packets in the PDCP buffer 810 may be used to trigger downlink flow control. If, for example, the PDCP layer observes that a packet remains in the PDCP buffer for 300 ms, downlink flow control may be triggered.
  • the average rate at which the applications processor reads data from the PDCP buffer 810 may be used to trigger downlink flow control.
  • the amount of unread data in a buffer used to transfer data from a PDCP layer to an applications processor may be used to trigger downlink flow control.
  • the UE may dynamically adjust the buffer size and/or packet dropping rate to achieve a desired target rate at the applications processor.
  • an amount of time unread data is in the buffer may be used to trigger downlink flow control.
  • FIG. 9 illustrates example operations 900 which may be performed for downlink flow control, for example by a UE, according to aspects of the present disclosure.
  • a UE may monitor one or more parameters related to the UE.
  • the UE may selectively drop received packets based on the one or more parameters in order to trigger a rate control mechanism in the UE.
  • the packets may be dropped at a PDCP layer, prior to being transmitted to an applications layer.
  • aspects of the present disclosure provide techniques for downlink flow control based on parameters observed at a UE.
  • packets may be selectively dropped at a PDCP layer in an effort to reduce a corresponding TCP layer throughput. Packets dropped at a PDCP layer will not reach the applications processor. Accordingly, a TCP client may send negative acknowledgments to a TCP server and/or duplicate acknowledgments for previously received packets, to trigger downlink flow control.
  • downlink flow control may be triggered by one or more parameters related to a UE, including, for example, temperature of one or more devices at a UE, available global memory, delay observed by packets in the PDCP buffer, and/or a rate at which the applications processor processes data from the PDCP layer. Based on these parameters, the UE may adjust the rate at which packets are dropped at the PDCP layer.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.
  • ASIC application specific integrated circuit
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members.
  • "at least one of: a , b , or c" is intended to cover: a , b , c , a-b , a-c , b-c , and a-b-c.
  • any suitable means capable of performing the operations such as various hardware and/or software component(s), circuits, and/or module(s).
  • any operations illustrated in the Figures may be performed by corresponding functional means capable of performing the operations.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array signal
  • PLD programmable logic device
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available 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.
  • a software module may reside in any form of storage medium that is known in the art. Some examples of storage media that may be used include random access memory (RAM), read only memory (ROM), flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM and so forth.
  • RAM random access memory
  • ROM read only memory
  • flash memory EPROM memory
  • EEPROM memory EEPROM memory
  • registers a hard disk, a removable disk, a CD-ROM and so forth.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • a storage medium may be coupled to a 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 methods disclosed herein comprise one or more steps or actions for achieving the described method.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray ® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
  • the computer program product may include packaging material.
  • Software or instructions may also be transmitted over a transmission medium.
  • a transmission medium For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of transmission medium.
  • DSL digital subscriber line
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
EP11808111.6A 2011-01-07 2011-12-22 Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput Active EP2661846B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201161430895P 2011-01-07 2011-01-07
US13/333,553 US8824290B2 (en) 2011-01-07 2011-12-21 Downlink flow control using packet dropping to control transmission control protocol (TCP) layer throughput
PCT/US2011/066809 WO2012094168A1 (en) 2011-01-07 2011-12-22 Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput

Publications (2)

Publication Number Publication Date
EP2661846A1 EP2661846A1 (en) 2013-11-13
EP2661846B1 true EP2661846B1 (en) 2016-04-20

Family

ID=46455137

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11808111.6A Active EP2661846B1 (en) 2011-01-07 2011-12-22 Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput

Country Status (7)

Country Link
US (1) US8824290B2 (ko)
EP (1) EP2661846B1 (ko)
JP (1) JP5847842B2 (ko)
KR (1) KR101521740B1 (ko)
CN (1) CN103283277B (ko)
TW (1) TW201234905A (ko)
WO (1) WO2012094168A1 (ko)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9510242B2 (en) * 2013-05-17 2016-11-29 Nvidia Corporation Reducing superfluous traffic in a network
US9124673B2 (en) * 2013-09-30 2015-09-01 Intel IP Corporation Transmission control protocol (TCP) based video streaming
WO2015066849A1 (zh) * 2013-11-06 2015-05-14 华为终端有限公司 一种降低功耗的方法及系统、调制解调器
JP6394249B2 (ja) * 2014-09-30 2018-09-26 ブラザー工業株式会社 画像処理装置
US10432798B1 (en) * 2018-05-25 2019-10-01 At&T Intellectual Property I, L.P. System, method, and apparatus for service grouping of users to different speed tiers for wireless communication
US10419943B1 (en) 2018-06-15 2019-09-17 At&T Intellectual Property I, L.P. Overlay of millimeter wave (mmWave) on citizens broadband radio service (CBRS) for next generation fixed wireless (NGFW) deployment
US10798537B2 (en) 2018-07-09 2020-10-06 At&T Intellectual Property I, L.P. Next generation fixed wireless qualification tool for speed-tier based subscription
CN112188553B (zh) * 2019-07-01 2022-03-25 大唐移动通信设备有限公司 一种5g系统的数据传输方法及装置
EP4282098A1 (en) * 2021-01-19 2023-11-29 QUALCOMM Incorporated Techniques for transmission control protocol (tcp) packet loss recovery

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080291833A1 (en) * 2007-05-25 2008-11-27 Gustav Gerald Vos Method for buffer control for network device
WO2010009768A1 (en) * 2008-07-25 2010-01-28 Telefonaktiebolaget L M Ericsson (Publ) Thinning of packet-switched video data

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3434231B2 (ja) * 1999-02-25 2003-08-04 日本電信電話株式会社 Ｔｃｐ制御方法
US6606301B1 (en) * 1999-03-01 2003-08-12 Sun Microsystems, Inc. Method and apparatus for early random discard of packets
US7349337B1 (en) 2003-12-12 2008-03-25 Novell, Inc. Techniques for shaping data transmission rates
US7571181B2 (en) * 2004-04-05 2009-08-04 Hewlett-Packard Development Company, L.P. Network usage analysis system and method for detecting network congestion
JP2006121550A (ja) * 2004-10-25 2006-05-11 Hitachi Kokusai Electric Inc 無線通信装置
JP4664243B2 (ja) 2006-06-29 2011-04-06 富士通株式会社 通信装置
JP5108261B2 (ja) * 2006-07-11 2012-12-26 株式会社リコー 情報処理装置およびデータ通信装置
US7697519B2 (en) * 2006-10-31 2010-04-13 Hewlett-Packard Development Company, L.P. Packet processing
KR100996069B1 (ko) 2006-11-27 2010-11-22 삼성전자주식회사 이동통신 시스템에서 라디오 링크 제어 계층의 데이터 전송 방법 및 장치
AU2008308944B2 (en) 2007-10-01 2012-07-26 Interdigital Patent Holdings, Inc. Method and apparatus for PCDP discard
KR101178263B1 (ko) 2007-12-20 2012-08-30 가부시키가이샤 엔티티 도코모 이동국, 기지국장치, 통신제어방법 및 이동통신시스템
JP4952586B2 (ja) 2008-01-07 2012-06-13 富士通株式会社 パケットデータの廃棄方法、無線通信装置、移動通信システム
CN101527674B (zh) * 2008-03-04 2011-04-27 中国移动通信集团公司 一种数据处理的方法及装置
US8325608B2 (en) 2008-08-07 2012-12-04 Qualcomm Incorporated Efficient packet handling for timer-based discard in a wireless communication system
US8644338B2 (en) 2009-01-07 2014-02-04 Qualcomm Incorporated Unbundling packets received in wireless communications
JP5391830B2 (ja) 2009-05-25 2014-01-15 富士通株式会社 無線基地局装置、通信システムおよびデータ転送方法
US9584416B2 (en) 2009-06-08 2017-02-28 Qualcomm Incorporated Systems and methods to provide flow control for mobile devices
US8300703B2 (en) * 2009-09-22 2012-10-30 Texas Instruments Incorporated System and method for adaptively allocating resources in a transcoder
JP2013512603A (ja) 2009-12-23 2013-04-11 エヌイーシー ヨーロッパ リミテッド ワイヤレスネットワークにおけるリソース管理方法およびワイヤレスネットワーク
US8630169B2 (en) * 2010-02-25 2014-01-14 Nokia Corporation Method and apparatus for controlling a temperature of a packet communications device
US8750207B2 (en) * 2010-10-15 2014-06-10 Apple Inc. Adapting transmission to improve QoS in a mobile wireless device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080291833A1 (en) * 2007-05-25 2008-11-27 Gustav Gerald Vos Method for buffer control for network device
WO2010009768A1 (en) * 2008-07-25 2010-01-28 Telefonaktiebolaget L M Ericsson (Publ) Thinning of packet-switched video data

Also Published As

Publication number Publication date
KR20130109230A (ko) 2013-10-07
JP2014509101A (ja) 2014-04-10
KR101521740B1 (ko) 2015-05-19
TW201234905A (en) 2012-08-16
US8824290B2 (en) 2014-09-02
US20120176898A1 (en) 2012-07-12
EP2661846A1 (en) 2013-11-13
JP5847842B2 (ja) 2016-01-27
WO2012094168A1 (en) 2012-07-12
CN103283277A (zh) 2013-09-04
CN103283277B (zh) 2016-08-10

Similar Documents

Publication Publication Date Title
EP2661846B1 (en) Downlink flow control using packet dropping to control transmission control protocol (tcp) layer throughput
EP2578040B1 (en) Uplink data throttling by modifying a buffer status report
KR102158904B1 (ko) 무선 통신에서 동적 디바이스 능력 시그널링을 위한 방법 및 장치
JP5735074B2 (ja) ダウンリンクフロー制御
AU2008318568B2 (en) Service data unit discard timers
US9729467B2 (en) Method and apparatus for managing congestion in a wireless system
US20160219458A1 (en) Methods and apparatus for radio link control switching
US10594612B2 (en) Threshold for reduced latency mechanisms
CN101911567B (zh) 无线通信网络中的方法和装置
TW201016059A (en) Buffer status report triggers in wireless communications
US9246637B2 (en) Communication terminal device and method for operating a communication terminal device
WO2017000131A1 (en) Http streaming aware cross-layer optimization and application-aware ran signaling
WO2016164278A1 (en) Techniques for retransmissions and initialization of radio link control reset
US20120176922A1 (en) Downlink flow control by adding noise to a receiver to reduce physical layer throughput
US11646852B2 (en) Uplink transport protocol acknowledgment shaping and downlink data shaping at a user equipment
CN106100714B (zh) 基于动态接收分集的方法和设备

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130806

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20140731

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011025738

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012560000

Ipc: H04L0012700000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/70 20130101AFI20151002BHEP

INTG Intention to grant announced

Effective date: 20151026

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 793491

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160515

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011025738

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 793491

Country of ref document: AT

Kind code of ref document: T

Effective date: 20160420

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20160420

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

Ref country code: PL

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

Effective date: 20160420

Ref country code: FI

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

Effective date: 20160420

Ref country code: LT

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

Effective date: 20160420

Ref country code: NL

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

Effective date: 20160420

Ref country code: NO

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

Effective date: 20160720

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

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

Ref country code: AT

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

Effective date: 20160420

Ref country code: HR

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

Effective date: 20160420

Ref country code: ES

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

Effective date: 20160420

Ref country code: PT

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

Effective date: 20160822

Ref country code: RS

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

Effective date: 20160420

Ref country code: LV

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

Effective date: 20160420

Ref country code: GR

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

Effective date: 20160721

Ref country code: SE

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

Effective date: 20160420

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

Ref country code: IT

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

Effective date: 20160420

Ref country code: BE

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

Effective date: 20160420

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011025738

Country of ref document: DE

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

Ref country code: SK

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

Effective date: 20160420

Ref country code: CZ

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

Effective date: 20160420

Ref country code: RO

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

Effective date: 20160420

Ref country code: EE

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

Effective date: 20160420

Ref country code: DK

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

Effective date: 20160420

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: SM

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

Effective date: 20160420

26N No opposition filed

Effective date: 20170123

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

Ref country code: SI

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

Effective date: 20160420

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Ref country code: MC

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

Effective date: 20160420

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

Ref country code: LI

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

Effective date: 20161231

Ref country code: LU

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

Effective date: 20161222

Ref country code: CH

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

Effective date: 20161231

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

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

Ref country code: IE

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

Effective date: 20161222

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

Ref country code: CY

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

Effective date: 20160420

Ref country code: HU

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

Effective date: 20111222

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

Ref country code: MK

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

Effective date: 20160420

Ref country code: IS

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

Effective date: 20160420

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

Ref country code: BG

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

Effective date: 20160420

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

Ref country code: MT

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

Effective date: 20161222

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

Ref country code: AL

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

Effective date: 20160420

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

Ref country code: TR

Payment date: 20211201

Year of fee payment: 11

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

Ref country code: GB

Payment date: 20231108

Year of fee payment: 13

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

Ref country code: FR

Payment date: 20231108

Year of fee payment: 13

Ref country code: DE

Payment date: 20231108

Year of fee payment: 13

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

Ref country code: TR

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

Effective date: 20221222