EP2428094B1 - System, methods and apparatuses for facilitating discontinuous reception in a multi-carrier wireless communication system - Google Patents

System, methods and apparatuses for facilitating discontinuous reception in a multi-carrier wireless communication system Download PDF

Info

Publication number
EP2428094B1
EP2428094B1 EP10718384.0A EP10718384A EP2428094B1 EP 2428094 B1 EP2428094 B1 EP 2428094B1 EP 10718384 A EP10718384 A EP 10718384A EP 2428094 B1 EP2428094 B1 EP 2428094B1
Authority
EP
European Patent Office
Prior art keywords
drx
frequency carriers
discontinuous reception
frequency
inactivity
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
EP10718384.0A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2428094A1 (en
Inventor
Peter Gaal
Jelena M. Damnjanovic
Juan Montojo
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 EP2428094A1 publication Critical patent/EP2428094A1/en
Application granted granted Critical
Publication of EP2428094B1 publication Critical patent/EP2428094B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2647—Arrangements specific to the receiver only
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the following description relates to wireless communications, in general, and to facilitating discontinuous reception in multicarrier wireless communication systems, in particular.
  • Wireless communication systems are widely deployed to provide various types of communication. For instance, voice and/or data can be provided via such wireless communication systems.
  • a typical wireless communication system, or network can provide multiple users access to one or more shared resources (e.g ., bandwidth, transmit power).
  • shared resources e.g ., bandwidth, transmit power.
  • a system can use a variety of multiple access techniques such as Frequency Division Multiplexing (FDM), Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), Orthogonal Frequency Division Multiplexing (OFDM), and others.
  • FDM Frequency Division Multiplexing
  • TDM Time Division Multiplexing
  • CDM Code Division Multiplexing
  • OFDM Orthogonal Frequency Division Multiplexing
  • wireless multiple-access communication systems can simultaneously support communication for multiple user equipments (UEs).
  • UEs user equipments
  • Each UE can communicate with one or more base stations (BSs) via transmissions on forward and reverse links.
  • the forward link or downlink (DL)
  • DL downlink
  • UL uplink
  • This communication link can be established via a single-in-single-out, multiple-in-single-out or a multiple-in-multiple-out (MIMO) system.
  • MIMO multiple-in-multiple-out
  • MIMO systems commonly employ multiple ( N T ) transmit antennas and multiple ( N R ) receive antennas for data transmission.
  • a MIMO channel formed by the N T transmit and N R receive antennas can be decomposed into N S independent channels, which can be referred to as spatial channels, where N S ⁇ ⁇ N T , N R ⁇ .
  • Each of the N S independent channels corresponds to a dimension.
  • MIMO systems can provide improved performance (e.g. , increased spectral efficiency, higher throughput and/or greater reliability) if the additional dimensionalities created by the multiple transmit and receive antennas are utilized.
  • MIMO systems can support various duplexing techniques to divide forward and reverse link communications over a common physical medium.
  • frequency division duplex (FDD) systems can utilize disparate frequency regions for forward and reverse link communications.
  • time division duplex (TDD) systems forward and reverse link communications can employ a common frequency region so that the reciprocity principle allows estimation of the forward link channel from reverse link channel.
  • Wireless communication systems oftentimes employ one or more BSs to provide a coverage area.
  • a typical BS can transmit multiple data streams for broadcast, multicast and/or unicast services, wherein a data stream may be a stream of data that can be of independent reception interest to a UE.
  • An UE within the coverage area of such BS can be employed to receive one, more than one, or all the data streams carried by the composite stream.
  • a UE can transmit data to the BS or to another UE.
  • the 3GPP TSG-RAN WG2 #66 draft R2-092029 corresponding to a conference with the earliest conference date of May 4, 2009 - which is the priority date of the present invention - relates to DRX with carrier aggregation in LTE-Advanced. Said draft proposes to perform DRX independently for each component carriers.
  • the TSG-RAN WGi #53bis draft R1-082468 relates to carrier aggregation in LTE-Advanced in general. Said draft inter alia suggests to rely on DRX per component carrier.
  • the present invention provides a solution according to the subject matter of the independent claims.
  • a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and/or the computing device can be a component.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer-readable media having various data structures stored thereon.
  • the components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g ., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
  • a signal having one or more data packets (e.g ., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier-frequency division multiple access
  • a CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1220, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.
  • CDMA1220 covers IS-1220, IS-95 and IS-856 standards.
  • An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 122.11 (Wi-Fi), IEEE 122.16 (WiMAX), IEEE 122.20, Flash-OFDM, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 122.16
  • Flash-OFDM Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3GPP Long Term Evolution (LTE) is an upcoming release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA1220 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 122.xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA utilizes single carrier modulation and frequency domain equalization.
  • SC-FDMA can have similar performance and essentially the same overall complexity as those of an OFDMA system.
  • a SC-FDMA signal can have lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA can be used, for instance, in uplink communications where lower PAPR greatly benefits UEs in terms of transmit power efficiency.
  • SC-FDMA can be implemented as an uplink multiple access scheme in 3GPP Long Term Evolution (LTE) or Evolved UTRA.
  • LTE Long Term Evolution
  • Evolved UTRA 3GPP Long Term Evolution
  • An UE can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, user device or access terminal.
  • An UE can be 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, computing device, or other processing device connected to a wireless modem.
  • SIP Session Initiation Protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a BS can be utilized for communicating with UEs and can also be referred to as an access point, Node B, Evolved Node B (eNodeB, eNB) or some other terminology.
  • the term "or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B.
  • the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form.
  • Computer-readable media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying codes and/or instruction(s) and/or data.
  • System 100 includes a BS 102 that can include multiple antenna groups.
  • one antenna group can include antennas 104, 106, another group can comprise antennas 108, 110, and an additional group can include antennas 112, 114.
  • Two antennas are illustrated for each antenna group; however, more or fewer antennas can be utilized for each group.
  • BS 102 can additionally include a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas), as will be appreciated by one skilled in the art.
  • BS 102 can communicate with one or more UEs such as UE 116, 122. However, it is to be appreciated that BS 102 can communicate with substantially any number of UEs similar to UEs 116, 122.
  • UEs 116, 122 can be, for example, cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable device for communicating over wireless communication system 100.
  • UE 116 is in communication with antennas 112, 114, where antennas 112, 114 transmit information to UE 116 over DL 118 and receive information from UE 116 over a UL 120.
  • UE 122 is in communication with antennas 104, 106, where antennas 104, 106 transmit information to UE 122 over a DL 124 and receive information from UE 122 over a UL 126.
  • DL 118 can utilize a different frequency band than that used by UL 120
  • DL 124 can employ a different frequency band than that employed by UL 126, for example.
  • TDD time division duplex
  • DL 118 and UL 120 can utilize a common frequency band and DL 124 and UL 126 can utilize a common frequency band.
  • Each group of antennas and/or the area in which they are designated to communicate can be referred to as a sector of BS 102.
  • antenna groups can be designed to communicate to UEs in a sector of the areas covered by BS 102.
  • the transmitting antennas of BS 102 can utilize beamforming to improve signal-to-noise ratio of DLs 118, 124 for UEs 116, 122.
  • BS 102 utilizes beamforming to transmit to UEs 116, 122 scattered randomly through an associated coverage
  • UEs 116, 122 in neighboring cells can be subject to less interference as compared to a BS transmitting through a single antenna to all its UEs.
  • system 100 can facilitate DRX by providing DRX configuration information over UL 126 to UE 122 from BS 102.
  • the DRX configuration information can be for controlling DRX based on time and frequency parameters.
  • Embodiments of the UE 122 and BS 102, systems, methods, computer program products and means for facilitating DRX will be described in further detail below.
  • FIG. 2 is an illustration of an example of a wireless network environment for facilitating DRX in accordance with various aspects set forth herein.
  • the wireless communication system 200 depicts one BS 210 and one UE 250 for sake of brevity.
  • system 200 can include more than one BS and/or more than one UE, wherein additional BSs and/or UEs can be substantially similar or different from example BS 210 and UE 250 described below.
  • BS 210 and/or UE 250 can employ the methods (e.g., FIGs. 13-16 ), apparatus (e.g., FIGs. 6 and 7 ) and/or systems (e.g., FIGs. 1 , 2 , 3 , 5 and 8-12 ) described below to facilitate DRX.
  • traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.
  • TX data processor 214 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.
  • the coded data for each data stream can be multiplexed with pilot data using orthogonal frequency division multiplexing (OFDM) techniques. Additionally or alternatively, the pilot symbols can be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM).
  • the pilot data is typically a known data pattern that is processed in a known manner and can be used at UE 250 to estimate channel response.
  • the multiplexed pilot and coded data for each data stream can be modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)) selected for that data stream to provide modulation symbols.
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • the data rate, coding, and modulation for each data stream can be determined by instructions performed or provided by processor 230.
  • the modulation symbols for the data streams can be provided to a TX MIMO processor 220, which can 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. In various embodiments, 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.
  • 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. Further, N T modulated signals from transmitters 222a through 222t are transmitted from N T antennas 224a through 224t, respectively.
  • the transmitted modulated signals are received by N R antennas 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r.
  • Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.
  • An RX data processor 260 can receive and process 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.
  • RX data processor 260 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream.
  • the processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at BS 210.
  • a processor 270 can periodically determine which available technology to utilize as discussed above. Further, processor 270 can formulate a reverse link message comprising a matrix index portion and a rank value portion.
  • the reverse link message can comprise various types of information regarding the communication link and/or the received data stream.
  • the reverse link message can be 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 BS 210.
  • the modulated signals from UE 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 reverse link message transmitted by UE 250. Further, processor 230 can process the extracted message to determine which precoding matrix to use for determining the beamforming weights.
  • Processors 230 and 270 can direct (e.g., control, coordinate, manage) operation at BS 210 and UE 250, respectively. Respective processors 230 and 270 can be associated with memory 232 and 272 that store program codes and data. Processors 230 and 270 can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.
  • Logical Control Channels can include a Broadcast Control Channel (BCCH), which is a DL channel for broadcasting system control information. Further, Logical Control Channels can include a Paging Control Channel (PCCH), which is a DL channel that transfers paging information. Moreover, the Logical Control Channels can include a Multicast Control Channel (MCCH), which is a Point-to-multipoint DL channel used for transmitting Multimedia Broadcast and Multicast Service (MBMS) scheduling and control information for one or several Multicast Traffic Channels (MTCHs).
  • BCCH Broadcast Control Channel
  • PCCH Paging Control Channel
  • MCCH Multicast Control Channel
  • MBMS Multimedia Broadcast and Multicast Service
  • the Logical Control Channels can include a Dedicated Control Channel (DCCH), which is a Point-to-point bi-directional channel that transmits dedicated control information and can be used by UEs having a RRC connection.
  • DCCH Dedicated Control Channel
  • the Logical Traffic Channels can comprise a Dedicated Traffic Channel (DTCH), which is a Point-to-point bi-directional channel dedicated to one UE for the transfer of user information.
  • DTCH Dedicated Traffic Channel
  • the Logical Traffic Channels can include an MTCH for Point-to-multipoint DL channel for transmitting traffic data.
  • Transport Channels are classified into DL and UL.
  • DL Transport Channels can include a Broadcast Channel (BCH), a Downlink Shared Data Channel (DL-SDCH) and a Paging Channel (PCH).
  • BCH Broadcast Channel
  • DL-SDCH Downlink Shared Data Channel
  • PCH Paging Channel
  • the PCH can support UE power saving (e.g., Discontinuous Reception (DRX) cycle can be indicated by the network to the UE) by being broadcasted over an entire cell and being mapped to Physical layer (PHY) resources that can be used for other control/traffic channels.
  • the UL Transport Channels can comprise a Random Access Channel (RACH), a Request Channel (REQCH), an Uplink Shared Data Channel (UL-SDCH) and a plurality of PHY channels.
  • RACH Random Access Channel
  • REQCH Request Channel
  • UL-SDCH Uplink Shared Data Channel
  • the PHY channels can include a set of DL channels and UL channels.
  • the DL PHY channels can include: Common Pilot Channel (CPICH); Synchronization Channel (SCH); Common Control Channel (CCCH); Shared DL Control Channel (SDCCH); Multicast Control Channel (MCCH); Shared UL Assignment Channel (SUACH); Acknowledgement Channel (ACKCH); DL Physical Shared Data Channel (DL-PSDCH); UL Power Control Channel (UPCCH); Paging Indicator Channel (PICH); and/or Load Indicator Channel (LICH).
  • CPICH Common Pilot Channel
  • SCH Common Control Channel
  • CCCH Common Control Channel
  • SDCCH Shared DL Control Channel
  • MCCH Multicast Control Channel
  • SUACH Shared UL Assignment Channel
  • ACKCH Acknowledgement Channel
  • DL-PSDCH DL Physical Shared Data Channel
  • UPCH UL Power Control Channel
  • PICH Paging Indicator Channel
  • LICH Load Indicator Channel
  • the UL PHY Channels can include: Physical Random Access Channel (PRACH); Channel Quality Indicator Channel (CQICH); Acknowledgement Channel (ACKCH); Antenna Subset Indicator Channel (ASICH); Shared Request Channel (SREQCH); UL Physical Shared Data Channel (UL-PSDCH); and/or Broadband Pilot Channel (BPICH).
  • PRACH Physical Random Access Channel
  • CQICH Channel Quality Indicator Channel
  • ACKCH Acknowledgement Channel
  • ASICH Antenna Subset Indicator Channel
  • SREQCH Shared Request Channel
  • UL-PSDCH UL Physical Shared Data Channel
  • BPICH Broadband Pilot Channel
  • FIG. 3 illustrates an example of a block diagram of a system for facilitating DRX in accordance with various aspects set forth herein.
  • the system 100' can include a DRX network control unit 302 and a UE 122' communicatively coupled to one another.
  • the DRX network control unit 302 can transmit information to the UE 122', such as the message 316 including DRX configuration information shown in FIG. 3 and discussed in more detail below. While only one UE 122' is shown in FIG. 3 , in other embodiments, any number of UEs (and/or UEs 122, 122", 122''', 122'''' described herein) can receive information from the DRX network control unit 302.
  • UE 122' is shown and described, it is to be understood that the same or substantially similar structure and/or functionality of UE122' can be provided in UE 122 (described with reference to FIG. 1 ) and/or UE 122", 122''', 122'''' (later-described with reference to FIGs. 5 , 6 , and 7 , respectively).
  • the DRX network control unit 302 can be any hardware, software, or a combination thereof, adapted to generate DRX configuration information, based on time and frequency carrier information, for controlling the DRX operation of the UE 122'.
  • the DRX network control unit 302 can include a communication unit 306, a DRX configuration information generation unit 308, an inactivity period and carrier frequency traffic evaluation unit 310, and a memory 312 configured to store the DRX configuration information 314.
  • One or more of the components of the DRX network control unit 302 can be communicatively coupled to one another for generating the message 316 transmitted to the UE 122'.
  • the DRX configuration information generation unit 308 can be or include any hardware, software or combination thereof for generating DRX configuration information 314 for use by the UE 122'.
  • the DRX configuration information 314 can include information indicative of parameters associated with both time and frequency.
  • the time and frequency parameters can be associated with one another for controlling the DRX of the UE 122' on one or more frequency carriers based on inactivity periods of time at the UE 122'.
  • the one or more frequency carriers can be selected and can dynamically change based on the inactivity period. Further, there can be more than one inactivity period.
  • the parameter associated with time can be the duration of the inactivity period at the UE 122'.
  • the parameter associated with frequency can be the type or number of frequency carriers on which the UE 122' is to perform DRX.
  • the DRX configuration information 314 can be indicative of two-dimensional information (that includes both time and frequency factors) based upon which the UE 122' will perform DRX.
  • the DRX configuration information 314 can include multiple combinations of time and frequency DRX such that the DRX configuration information 314 can represent multiple levels of DRX at the UE 122'.
  • a first level of DRX can correspond to a first inactivity period and a corresponding first set of frequency carriers or types of frequency carriers while a second level of DRX can correspond to a second inactivity period and a corresponding second set of frequency carriers or types of frequency carriers.
  • the DRX configuration information generation unit 308 can generate the DRX configuration information 314 by determining a length of an inactivity period that can occur at the UE 122'.
  • the term "inactivity period” is used herein to mean "the length of time when data is not being received at the UE 122', and the UE 122' does not have data to transmit.”
  • the values representing the length of time for the inactivity period can be selected randomly by the DRX configuration information generation unit 308, based on information from the UE 122' and/or based on information from the multicarrier wireless communication system 100' in which the DRX network control unit 302 and the UE 122' operate.
  • the DRX configuration information generation unit 308 can determine a length of a DRX cycle that corresponds to the length of the inactivity period.
  • the DRX cycle can include an awake period, during which the UE 122' can receive data, and a sleep period, during which the UE 122' cannot receive data.
  • the DRX cycle length can be chosen such that the DRX cycle length increases with an increase in an inactivity period, and decreases with a decrease in an inactivity period.
  • the length of the sleep period within the DRX cycle increases with an increase in an inactivity period, and decreases with a decrease in an inactivity period.
  • FIG. 4 illustrates an example of a graph displaying time and frequency aspects of levels of DRX in accordance with various aspects set forth herein. While the description of FIG. 4 is provided with reference to FIG. 3 and corresponding UE 122', it is to be understood that the description can apply to UE 122 (as described with reference to FIG. 1 ) and/or UE 122", 122"', 122"" (as later-described with reference to FIGs. 5 , 6 and 7 , respectively).
  • the DRX cycle lengths determined by the DRX configuration information generation unit 308, and which the UE 122' performs DRX in accordance with, can differ.
  • the DRX cycle lengths can differ according to the inactivity periods determined by the DRX configuration information generation unit 308.
  • each inactivity period experienced at the UE 122' can cause the UE 122' to transition to a new state defined by new DRX operation.
  • more than one inactivity period can cause the UE 122' to transition to the same state.
  • the DRX configuration information generation unit 308 can also determine one or more frequency carriers on which the UE 122' will perform DRX for each of the determined DRX cycle lengths.
  • the inactivity period and carrier frequency traffic evaluation unit 310 can determine the one or more frequency carriers or the one or more inactivity periods and provide the information to the DRX configuration information generation unit 308.
  • the UE 122' for a selected DRX cycle length, only one or a selected number (or a selected type) of frequency carriers are monitored by the UE 122' during the awake period of the DRX cycle. For example, instead of the UE 122' monitoring each of the frequency carriers on which it is configured to receive data, whenever the UE 122' is in the awake period, the UE 122' can monitor only a single frequency carrier.
  • the DRX cycle is performed to monitor and receive data on fewer carriers.
  • the DRX configuration information generation unit 308 can generate the DRX configuration information 314 such that the UE 122' monitors and is capable of receiving data on each of the frequency carriers.
  • the DRX configuration information generation unit 308 can generate the DRX configuration information 314 such that the UE 122' monitors and is capable of receiving data on only a single frequency carrier.
  • the DRX configuration information generation unit 308 can generate the DRX configuration information 314 such that the UE 122' monitors and is capable of receiving data also on only a single frequency carrier.
  • the frequency carrier for the second inactivity period can differ or be the same as the frequency carrier for the third inactivity period.
  • the frequency carrier corresponding to the second inactivity period is determined to be the anchor carrier.
  • the DRX configuration information generation unit 308 can generate the DRX configuration information 314 such that the UE 122' continuously monitors and/or receives data on the anchor carrier, and/or DRX is only performed on one or more of the non-anchor frequency carriers.
  • an exemplary graph displaying time and frequency aspects of levels of DRX at UE 122' is shown.
  • the one or more frequency carriers that the DRX configuration information generation unit 308 determines for a DRX cycle length (which can correspond to an inactivity period), and which the UE 122' performs DRX in accordance with, can differ.
  • the type of frequency carrier e.g., anchor carrier, non-anchor carrier
  • Tables 1-4 are exemplary relative values of inactivity periods, P, DRX cycle lengths, L and/or carriers, f, that can be embodied in the DRX configuration information 314, and by which the UE 122' can perform DRX.
  • Table 1 illustrates DRX based on time parameters. While Tables 2, 3 and 4 are based on a combination of time and frequency parameters.
  • Time- and Frequency-Based DRX Single Frequency Carrier
  • Time- and Frequency-Based DRX Multiple Frequency Carriers, Specified by Frequency Carrier
  • Time- and Frequency-Based DRX Multiple Frequency Carriers, Specified by Number of Frequency Carriers
  • the DRX configuration information 314 can be stored in the memory 312 and retrieved for re-transmission to the UE 122' in some embodiments.
  • the communication unit 306 can transmit (or re-transmit) the DRX configuration information 314 to the UE 122'.
  • the UE 122' can be any hardware, software, or a combination thereof, adapted to receive DRX configuration information 314, based on time and frequency carrier information, and perform DRX operation on one or more frequency carriers based on the received DRX configuration information 314.
  • the UE 122' can be a mobile device, including, but not limited to, a cell phone, personal digital assistant (PDA) and/or a laptop.
  • the UE 122' can be a computer, facsimile machine, printer and/or copier.
  • the UE 122' includes a communication unit 318, a DRX control unit 320, and a memory 328 configured to store the received DRX configuration information 330.
  • the received DRX configuration information 330 is the same as the DRX configuration information 314 generated by DRX configuration generation unit 308.
  • the DRX control unit 322 can be any hardware, software, or a combination thereof, adapted to control the time- and frequency-based DRX operation of the UE 122' based on the DRX configuration information 314.
  • the DRX control unit 320 includes an inactivity period evaluation unit 326 configured to monitor and determine the length of the inactivity period experienced at the UE 122', an awake-sleep period control unit configured to determine the corresponding awake period and sleep period that should combine to create a DRX operation being or to be performed by the UE 122', and a frequency carrier selection unit 322 configured to cause the UE 122' to select various frequency carriers to monitor and receive data according to the DRX operation of the UE 122'. Accordingly, the DRX control unit 320 controls the DRX operation of the UE 122' according to the DRX configuration information 314 received from the DRX network control unit 302.
  • FIG. 5 illustrates another example of a block diagram of a system for facilitating DRX in accordance with various aspects set forth herein.
  • the system 100" can include a control unit 502 having a processor unit 504 and memory 506; and UE 122" having a processor unit 510 and memory 412.
  • control unit 502 can be configured to generate DRX control information based on time and frequency parameters and output the generated DRX control information.
  • the DRX control information can correspond to a plurality of levels of DRX.
  • the UE 122" can be capable of performing multicarrier reception of data.
  • the UE 122" can be communicatively coupled to the control unit 502, and configured to: receive the output DRX control information.
  • the UE 122" can also be configured to perform DRX, on one or more frequency carriers on which the UE 122" can be configured to perform multicarrier reception according to one of the plurality of levels of DRX.
  • control unit 502 is a BS.
  • the BS can be the BS 102 described with reference to FIG. 1 .
  • control unit 502 is a DRX network control unit 302 described with reference to FIG. 3 .
  • the UE 122" can be further configured to perform continuous reception on a selected frequency carrier during a time interval over which the UE 122" performs DRX.
  • the selected frequency carrier can be an anchor carrier.
  • FIG. 6 illustrates an example of a block diagram of UE for facilitating DRX in accordance with various aspects set forth herein.
  • the UE 122''' can include a control unit 602 including a processor unit 604; and a memory unit 608.
  • the UE 122''' can also include a communication unit 606.
  • one or more of the aforementioned units can be communicatively coupled for facilitating DRX.
  • control unit 602 can be configured for performing DRX based, at least, on parameters indicative of: one or more inactivity periods of the apparatus; and one or more sets of frequency carriers at which the apparatus is configured to monitor and receive data.
  • the control unit 602 can also be configured for, after a first one of the one or more inactivity periods, operating in a first state corresponding to monitoring a first one of the one or more sets of frequency carriers; and, after a second one of the one or more inactivity periods, operating in a second state corresponding to monitoring a second one of the one or more sets of frequency carriers.
  • control unit 602 can also be configured for performing continuous reception on a frequency carrier corresponding to an anchor carrier of the UE 122'''.
  • the communication unit 606 can be configured for receiving DRX configuration information generated at a network control unit (not shown) communicatively coupled to the control unit 602.
  • the network control unit can be a BS 102 described with reference to FIG. 1 or the DRX network control unit 302 described with reference to FIG. 3 .
  • FIG. 7 illustrates another example of a block diagram of UE for facilitating DRX in accordance with various aspects set forth herein.
  • the UE 122'''' can include a control unit 702 including a processor unit 704; a multicarrier receiver 717; and a memory unit 710.
  • a control unit 702 including a processor unit 704; a multicarrier receiver 717; and a memory unit 710.
  • one or more of the aforementioned units can be communicatively coupled for facilitating DRX.
  • the multicarrier receiver 717 can be configured for concurrently receiving data on selected one or more frequency carriers after a selected inactivity period of the multicarrier receiver 717.
  • the receiving of the data can be based on DRX configuration information including parameters indicative of the selected one or more frequency carriers and indicative of the selected inactivity period of the multicarrier receiver 717.
  • FIGs. 8-12 each illustrate an example of a block diagram of a system for facilitating DRX in accordance with various aspects set forth herein.
  • system 800 can reside within a UE, including, but not limited to, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively. It is to be appreciated that system 800 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, hardware, software, firmware, or combination thereof. System 800 can include an electrical component 802 for performing DRX based, at least, on parameters indicative of: one or more inactivity periods of the apparatus; and one or more sets of frequency carriers at which the apparatus is configured to monitor and receive data.
  • the electrical component 802 can also be for, after a first one of the one or more inactivity periods, operating in a first state corresponding to monitoring a first one of the one or more sets of frequency carriers and, after a second one of the one or more inactivity periods, operating in a second state corresponding to monitoring a second one of the one or more sets of frequency carriers.
  • the electrical component 802 can also be for performing continuous reception on a frequency carrier corresponding to an anchor carrier of the apparatus.
  • the electrical component 802 can also include an electrical component for communicating (not shown).
  • the electrical component for communicating can be for receiving DRX configuration information generated at an electrical component for controlling DRX (not shown) communicatively coupled to the electrical component 802 for DRX.
  • the electrical component 802 can include, but is not limited to, a receiver, transceiver, the UE 122, 122', 122", 122"', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, the communication unit 606 described with reference to FIG. 6 or the multicarrier receiver 717 described with reference to FIG. 7 .
  • the system 800 can include an electrical component 804 for storing code and/or instructions for executing functions associated with electrical component 802.
  • the electrical component 804 can include, but is not limited to, a memory, a computer-readable medium and/or the memory 312, 328 described with reference to FIG. 3 , the memory 506, 512 described with reference to FIG. 5 , the memory unit 608 described with reference to FIG. 6 and/or the memory unit 710 described with reference to FIG. 7 . While shown as being external to the electrical component for storing 804, it is to be understood that electrical component 802 can be included within the electrical component for storing 804.
  • system 900 can reside within a UE, including, but not limited to, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively. It is to be appreciated that system 900 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, hardware, software, firmware, or combination thereof. System 900 can include an electrical component 902 for performing DRX according to DRX configuration information that included time-based and frequency-based parameters.
  • the electrical component 902 can include, but is not limited to, a receiver, transceiver, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, the communication unit 606 described with reference to FIG. 6 or the multicarrier receiver 717 described with reference to FIG. 7 .
  • the system 900 can include an electrical component 904 for storing code and/or instructions for executing functions associated with electrical component 902.
  • the electrical component 904 can include, but is not limited to, a memory, a computer-readable medium and/or the memory 312, 328 described with reference to FIG. 3 , the memory 506, 512 described with reference to FIG. 5 , the memory unit 608 described with reference to FIG. 6 and/or the memory unit 710 described with reference to FIG. 7 . While shown as being external to the electrical component for storing 904, it is to be understood that electrical component 902 can be included within the electrical component for storing 904.
  • system 1000 can reside within a UE, including, but not limited to, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively. It is to be appreciated that system 1000 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, hardware, software, firmware, or combination thereof. System 1000 can include an electrical component 1002 for concurrently receiving data on selected one or more frequency carriers after a selected inactivity period of the electrical component for concurrently receiving.
  • the receiving can be based on DRX configuration information including parameters indicative of the selected one or more frequency carriers and indicative of the selected inactivity period of the electrical component 1002 for concurrently receiving.
  • the electrical component 1002 for concurrently receiving can include, but is not limited to, a receiver, transceiver, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, the communication unit 606 described with reference to FIG. 6 or the multicarrier receiver 717 described with reference to FIG. 7 .
  • the system 1000 can include an electrical component 1004 for storing code and/or instructions for executing functions associated with electrical component 1002.
  • the electrical component 1004 can include, but is not limited to, a memory, a computer-readable medium and/or the memory 312, 328 described with reference to FIG. 3 , the memory 506, 512 described with reference to FIG. 5 , the memory unit 608 described with reference to FIG. 6 and/or the memory unit 710 described with reference to FIG. 7 . While shown as being external to the electrical component for storing 1104, it is to be understood that electrical component 1002 can be included within the electrical component for storing 1004.
  • system 1100 can reside within a UE, including, but not limited to, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively. It is to be appreciated that system 1100 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, hardware, software, firmware, or combination thereof. System 1100 can include a logical grouping 1102 of electrical components that can act in conjunction. For instance, logical grouping 1102 can include an electrical component for generating DRX control information based on time and frequency parameters.
  • the generated DRX control information can correspond to a plurality of levels of DRX 1104.
  • the electrical component for generating DRX control information 1104 can include, but is not limited to, BS 102 described with reference to FIG. 1 , DRX network control unit 302 described with reference to FIG. 3 or control unit 502 described with reference to FIG. 5 .
  • logical grouping 1102 can include an electrical component for outputting the generated DRX control information 1106.
  • the electrical component 1106 can include, but is not limited to, a transmitter, transceiver or communication unit 306 described with reference to FIG. 3 .
  • logical grouping 1102 can include an electrical component for communicating 1108.
  • the electrical component for communicating 1104 can be capable of performing multicarrier reception of data.
  • the electrical component for communicating can be communicatively coupled to the means for generating 1104 DRX control information.
  • the electrical component for communicating 1104 can be configured to receive the output DRX control information from the electrical component for outputting 1106.
  • the electrical component for communicating 1104 can also be configured to perform DRX on one or more frequency carriers on which the electrical component for communicating 1104 is configured to perform multicarrier reception according to one of the plurality of levels of DRX.
  • the selected frequency carrier can be an anchor carrier.
  • the electrical component for communicating 1104 can be further configured to perform continuous reception on a selected frequency carrier during a time interval over which the electrical component for communicating 1104 performs DRX.
  • the electrical component for communicating 1108 can include, but is not limited to, a receiver, transceiver or the UE 122, 122', 122", 122"', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, or the communication unit 606 described with reference to FIG. 6 .
  • the system 1100 can include an electrical component 1110 for storing code and/or instructions for executing functions associated with electrical components 1104, 1106 and/or 1108.
  • the electrical component 1110 can include, but is not limited to, a memory, a computer-readable medium and/or the memory 312, 328 described with reference to FIG. 3 , the memory 506, 512 described with reference to FIG. 5 , the memory unit 608 described with reference to FIG. 6 and/or the memory unit 710 described with reference to FIG. 7 . While shown as being external to the electrical component for storing 1114, it is to be understood that one or more of electrical components 1104, 1106 and/or 1108 can be included within the electrical component for storing 1110.
  • system 1200 can reside within a UE, including, but not limited to, the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively. It is to be appreciated that system 1200 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, hardware, software, firmware, or combination thereof.
  • System 1200 can include a logical or physical grouping 1202 of electrical components for performing DRX. The electrical component can act in conjunction. For instance, logical or physical grouping 1202 can include an electrical component for receiving content 1204.
  • the electrical component for receiving content 1204 can be for receiving data on one or more frequency carriers and for receiving DRX configuration information.
  • the electrical component for electrical component for receiving content 1204 can include, but is not limited to, a receiver, transceiver or the UE 122, 122', 122", 122"', 122"” described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, the communication unit 606 described with reference to FIG. 6 or the multicarrier receiver 717 described with reference to FIG. 7 .
  • logical or physical grouping 1202 can include an electrical component for selecting one or more frequency carriers on which to receive the data 1206.
  • the electrical component 1206 can include, but is not limited to, the frequency carrier selection unit 322 described with reference to FIG. 3 , the UE 122, 122', 122", 122''', 122''' described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, the communication unit 606 described with reference to FIG. 6 or the multicarrier receiver 717 described with reference to FIG. 7 .
  • logical or physical grouping 1202 can include an electrical component 1208 for controlling an awake period and a sleep period of the logical or physical grouping 1202.
  • the electrical component 1208 can include, but is not limited to, the awake-sleep period control unit 324 described with reference to FIG. 3 , the UE 122 described with reference to FIGs. 1 , 2 , 3 or 5 or the communication unit 606 described with reference to FIG. 6 .
  • logical or physical grouping 1202 can include an electrical component 1210 for evaluating an inactivity period of the logical or physical grouping 1202.
  • the electrical component 1210 can include, but is not limited to, the inactivity period described with reference to FIG. 3 , the UE 122, 122', 122", 122"', 122"” described with reference to FIGs. 1 , 3 , 5 , 6 and 7 , respectively, or the communication unit 606 described with reference to FIG. 6 .
  • the system 1200 can include an electrical component 1212 for storing received DRX configuration information, code and/or instructions, for executing functions associated with logical or physical grouping 1202 and/or electrical components 1204, 1206, 1208 and/or 1210.
  • the electrical component 1212 can include, but is not limited to, a memory, a computer-readable medium and/or the memory 312, 328 described with reference to FIG. 3 , the memory 506, 512 described with reference to FIG. 5 , the memory unit 608 described with reference to FIG. 6 and/or the memory unit 710 described with reference to FIG. 7 . While shown as being external to the electrical component for storing 1114, it is to be understood that one or more of electrical components 1204, 1206, 1208 and/or 1210 can be included within the electrical component for storing 1212.
  • the DRX configuration information can include information indicative of an inactivity period and a corresponding one or more frequency carriers for receiving the information at the electrical component for receiving content 1204.
  • the electrical component for receiving content 1204 can be UE communicatively coupled to a BS for receiving the data and for receiving the DRX configuration information.
  • FIGs. 13-16 each illustrate an example of a method for facilitating DRX in accordance with various aspects set forth herein.
  • the method 1300 can include generating, at a first apparatus, DRX control information based on time and frequency parameters 1302.
  • the generated DRX control information can correspond to a plurality of levels of DRX.
  • the method 1300 can also include: outputting the generated DRX control information 1304; and receiving, at a second apparatus capable of performing multicarrier reception of data, the output DRX control information 1306.
  • the method 1300 can also include performing DRX, on one or more frequency carriers on which the second apparatus is configured to perform multicarrier reception according to one of the plurality of levels of DRX 1308.
  • the method can include employing a processor for executing computer executable instructions to provide one or more DRX cycles respectively corresponding to one or more inactivity periods 1402.
  • data can be received on respective ones of one or more frequency carriers.
  • the respective ones of one or more frequency carriers can be anchor or non-anchor carriers.
  • the one or more DRX cycles can include a first DRX cycle and a second DRX cycle, and the one or more inactivity periods can include a first inactivity period and a second inactivity period. In some embodiments, the first inactivity period can be shorter than the second inactivity period.
  • a length of an inactivity period can be a multiple of a length of another inactivity period.
  • a length of the second inactivity period can be a multiple of a length of the first inactivity period (or vice versa).
  • the inactivity period for each frequency carrier can increase or decrease based on the activity on the frequency carrier.
  • Activity can be considered to be on a frequency carrier if there is data flow on the frequency carrier.
  • the inactivity period for each frequency carrier can increase or decrease based on an amount of data flow on the respective frequency carrier.
  • the increase or decrease of the inactivity period can be different for the different frequency carriers.
  • the new inactivity period for the frequency carrier (which can be the inactivity period for the frequency carrier after increasing or decreasing the previous inactivity period for the frequency carrier) can be a multiple of the initial, or baseline, inactivity period for the frequency carrier.
  • one or more DRX cycles include a first DRX cycle. In some embodiments, during an awake period of the first DRX cycle, each of one or more frequency carriers can be monitored. In some embodiments of method 1400, the one or more DRX cycles can include a first DRX cycle. In some embodiments, during an awake period of the first DRX cycle, only one frequency carrier is monitored. In some embodiments of method 1400, during an awake period of the first DRX cycle, each of one or more frequency carriers are monitored and during the awake period of the second DRX cycle, only one frequency carrier is monitored.
  • a first number of frequency carriers can be monitored and during the awake period of the second DRX cycle, a second number of frequency carriers can be monitored.
  • the first number of frequency carriers can be greater than the second number of frequency carriers.
  • the method can also include employing the processor to provide continuous reception on one of a plurality of frequency carriers.
  • the one of the plurality of frequency carriers can correspond to an anchor carrier.
  • FIG. 15 illustrates an exemplary methodology that facilitates providing levels of DRX at a UE in a multicarrier wireless communication system.
  • a current inactivity period is determined.
  • a DRX cycle length corresponding to the inactivity period is determined.
  • determination of the DRX cycle length can include determination of the awake period and/or the sleep period associated with the DRX cycle length.
  • the frequency carriers corresponding to the DRX cycle length can be selected.
  • the selected frequency carriers can be monitored, and any data thereon can be received, during the awake period corresponding to the DRX cycle length.
  • the aforementioned method can be performed at the UE 122'.
  • the aforementioned method can be performed at any UE described herein, including, but not limited to, the UE 122, 122", 122"', 122''' described with reference to FIGs. 1 , 5 , 6 and 7 , respectively.
  • Another method for DRX at a UE 122, 122', 122", 122''', 122''' can be as follows. After each of a first, second and third inactivity period, respectively, the UE 122, 122', 122", 122"', 122"" transitions to a first, second or third respective state wherein the UE 122 operates according to a first, second or third respective DRX cycle, and monitors a first, second or third respective set of one or more frequency carriers during the awake period corresponding to the DRX cycle.
  • the first, second and third inactivity periods can have increasing lengths and the first, second and third DRX cycles can also have increasing lengths such that the first DRX cycle can be shorter than the second DRX cycle and the second DRX cycle can be shorter than the third DRX cycle.
  • the DRX operation can include monitoring and receiving data on each of the frequency carriers, during the awake period corresponding to the first DRX cycle.
  • a transition in state can occur such that the DRX operation includes monitoring and receiving data on only a single frequency carrier, during the awake period corresponding to the second DRX cycle.
  • the single frequency carrier is the anchor carrier.
  • a transition in state can occur such that the DRX operation includes monitoring and receiving data also on only a single frequency carrier, during the awake period corresponding to the third DRX cycle.
  • the single frequency carrier is a non-anchor carrier.
  • a transition in state can occur such that the DRX operation includes monitoring and receiving data also on only a subset of the set of frequency carriers, during the awake period corresponding to the DRX cycle.
  • the subset can be determined by the UE 122' and/or by the DRX network control unit 302 in various embodiments. In other embodiments, the subset can be determined by the UE 122, 122", 122''', 122"".
  • the method 1600 can include, in response to a first inactivity period, operating in a first state wherein a first DRX cycle is provided and a first one or more of a plurality of frequency carriers of the multicarrier wireless system is monitored to receive data during an awake period of the first DRX cycle 1602.
  • the method 1600 can also include, in response to a second inactivity period, operating in a second state wherein a second DRX cycle is provided and a second one or more of the plurality of frequency carriers of the multicarrier wireless system is monitored to receive data during an awake period of the second DRX cycle 1604.
  • the method 1600 can also include, in response to a third inactivity period, operating in a third state wherein a third DRX cycle is provided and a third one or more of the plurality of frequency carriers of the multicarrier wireless system is monitored to receive data during an awake period of the third DRX cycle 1606.
  • the first inactivity period can be shorter than the second inactivity period, and/or the second inactivity period can be shorter than the third inactivity period.
  • the first DRX cycle can be shorter than the second DRX cycle, and/or the second DRX cycle can be shorter than the third DRX cycle.
  • a first computer program product can be provided.
  • the computer program product can include a computer-readable medium.
  • the computer-readable medium can include code for providing one or more DRX cycles respectively corresponding to one or more inactivity periods. During respective awake periods of the one or more DRX cycles, respective ones of one or more frequency carriers can be monitored for data reception. In some embodiments, the respective ones of one or more frequency carriers can be anchor or non-anchor carriers.
  • the one or more DRX cycles can include a first DRX cycle and a second DRX cycle
  • the one or more inactivity periods can include a first inactivity period and a second inactivity period.
  • the first inactivity period can be shorter than the second inactivity period.
  • the one or more DRX cycles can include a first DRX cycle. During an awake period of the first DRX cycle, each of one or more frequency carriers can be monitored. In some embodiments, the one or more DRX cycles can include a first DRX cycle. In these embodiments, during an awake period of the first DRX cycle, only one frequency carrier is monitored.
  • each of one or more frequency carriers can be monitored and during the awake period of the second DRX cycle, in some embodiments, only one frequency carrier is monitored.
  • a first number of frequency carriers can be monitored and during the awake period of the second DRX cycle, a second number of frequency carriers can be monitored.
  • the first number of frequency carriers can be greater than the second number of frequency carriers.
  • the computer-readable medium can also include code for providing continuous reception on one of a plurality of frequency carriers.
  • the one of the plurality of frequency carriers can correspond to an anchor carrier.
  • a computer program product can include a computer-readable medium.
  • the computer-readable medium can include code for, in response to a first inactivity period, operating in a first state.
  • a first DRX cycle can be provided and a first one or more of a plurality of frequency carriers of the multicarrier wireless system can be monitored to receive data during an awake period of the first DRX cycle.
  • the computer-readable medium can also include code for, in response to a second inactivity period, operating in a second state.
  • a second DRX cycle can be provided and a second one or more of the plurality of frequency carriers of the multicarrier wireless system can be monitored to receive data during an awake period of the second DRX cycle.
  • the computer-readable medium can also include code for, in response to a third inactivity period, operating in a third state.
  • a third DRX cycle can be provided and a third one or more of the plurality of frequency carriers of the multicarrier wireless system can be monitored to receive data during an awake period of the third DRX cycle.
  • the first inactivity period can be shorter than the second inactivity period, and the second inactivity period can be shorter than the third inactivity period.
  • the first DRX cycle can be shorter than the second DRX cycle, and the second DRX cycle can be shorter than the third DRX cycle.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof.
  • the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors and/or other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, micro-controllers, microprocessors and/or other electronic units designed to perform the functions described herein, or a combination thereof.
  • a code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements.
  • a code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.
  • the techniques described herein can be implemented with modules (e.g ., procedures, functions, and so on) that perform the functions described herein.
  • the software codes can be stored in memory units and executed by processors.
  • the memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP10718384.0A 2009-05-04 2010-05-04 System, methods and apparatuses for facilitating discontinuous reception in a multi-carrier wireless communication system Active EP2428094B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US17540009P 2009-05-04 2009-05-04
US12/764,590 US8655395B2 (en) 2009-05-04 2010-04-21 Systems, methods and apparatus for facilitating discontinuous reception
PCT/US2010/033611 WO2010129597A1 (en) 2009-05-04 2010-05-04 Systems, methods and apparatus for facilitating discontinuous reception in a multi-carrier wireless communication system

Publications (2)

Publication Number Publication Date
EP2428094A1 EP2428094A1 (en) 2012-03-14
EP2428094B1 true EP2428094B1 (en) 2019-09-18

Family

ID=42320784

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10718384.0A Active EP2428094B1 (en) 2009-05-04 2010-05-04 System, methods and apparatuses for facilitating discontinuous reception in a multi-carrier wireless communication system

Country Status (7)

Country Link
US (1) US8655395B2 (ja)
EP (1) EP2428094B1 (ja)
JP (2) JP5524329B2 (ja)
KR (1) KR101378126B1 (ja)
CN (1) CN102415201B (ja)
TW (1) TW201130362A (ja)
WO (1) WO2010129597A1 (ja)

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101358608B1 (ko) * 2009-06-15 2014-02-04 블랙베리 리미티드 롱텀 에볼루션 어드밴스트 캐리어 집적을 위한 불연속 수신 동작 방법 및 시스템
US20120099439A1 (en) * 2009-06-29 2012-04-26 Robert Baldemair Method and Device for Component Carrier Activation and Reconfiguration in a Mobile User Equipment
JP5990464B2 (ja) * 2010-01-08 2016-09-14 インターデイジタル パテント ホールディングス インコーポレイテッド マルチキャリア／マルチセル動作のための不連続受信および／または不連続送信を実行する方法および装置
US20120069782A1 (en) * 2010-09-22 2012-03-22 Richard Lee-Chee Kuo Method and apparatus for improving drx in a wireless communication system
US9271281B2 (en) * 2011-05-06 2016-02-23 Innovation Sonic Corporation Method and apparatus to improve inter-band carrier aggregation (CA) in TDD (time division duplex) mode
US9787397B2 (en) 2011-07-26 2017-10-10 Abl Ip Holding Llc Self identifying modulated light source
US9723676B2 (en) 2011-07-26 2017-08-01 Abl Ip Holding Llc Method and system for modifying a beacon light source for use in a light based positioning system
US8334898B1 (en) 2011-07-26 2012-12-18 ByteLight, Inc. Method and system for configuring an imaging device for the reception of digital pulse recognition information
US8964016B2 (en) 2011-07-26 2015-02-24 ByteLight, Inc. Content delivery based on a light positioning system
US8416290B2 (en) 2011-07-26 2013-04-09 ByteLight, Inc. Method and system for digital pulse recognition demodulation
US9418115B2 (en) 2011-07-26 2016-08-16 Abl Ip Holding Llc Location-based mobile services and applications
US9444547B2 (en) 2011-07-26 2016-09-13 Abl Ip Holding Llc Self-identifying one-way authentication method using optical signals
US8774804B2 (en) * 2011-10-31 2014-07-08 Intel Corporation Context-retention controller and method for context retention in wirless access networks
US9681382B2 (en) 2012-05-11 2017-06-13 Intel Corporation Radio coexistence in wireless networks
KR102078180B1 (ko) * 2012-10-27 2020-04-07 삼성전자주식회사 무선 단말에서의 동작 모드 제어장치 및 방법
US9992021B1 (en) 2013-03-14 2018-06-05 GoTenna, Inc. System and method for private and point-to-point communication between computing devices
US9705600B1 (en) 2013-06-05 2017-07-11 Abl Ip Holding Llc Method and system for optical communication
WO2015077767A1 (en) 2013-11-25 2015-05-28 Daniel Ryan System and method for communication with a mobile device via a positioning system including rf communication devices and modulated beacon light sources
CN105359604B (zh) * 2014-02-28 2020-02-14 华为技术有限公司 一种使用非授权频谱通信的方法、设备及系统
WO2015139026A2 (en) 2014-03-14 2015-09-17 Go Tenna Inc. System and method for digital communication between computing devices
US9374781B2 (en) * 2014-07-14 2016-06-21 Amazon Technologies, Inc. Method for discontinuous reception (DRX) in dual connectivity
US20160081020A1 (en) * 2014-09-16 2016-03-17 Telefonaktiebolaget L M Ericsson (Publ) Drx cycle configuration in dual connectivity
CN106664683B (zh) * 2015-06-30 2020-10-09 华为技术有限公司 一种数据传输方法及装置
CN106488460B (zh) * 2015-08-28 2020-06-23 苏州恩泽迅扬节能科技有限公司 无线通信方法及其对应的主设备、从设备和无线通信系统
WO2017216613A1 (en) 2016-06-17 2017-12-21 Telefonaktiebolaget Lm Ericsson (Publ) Soft discontinuous reception (soft drx)
US11012905B2 (en) * 2016-12-19 2021-05-18 Apple Inc. Wireless communication using an anchor carrier and flexible data carriers
CN108616969B (zh) * 2016-12-20 2020-07-21 华为技术有限公司 数据发送方法、数据接收方法及设备
CN111917528B (zh) * 2017-01-22 2022-04-29 华为技术有限公司 传输数据的方法、设备和通信系统
WO2018166584A1 (en) * 2017-03-14 2018-09-20 Huawei Technologies Co., Ltd. User node, network node and methods for allocating and using resources for control signals
KR102313704B1 (ko) * 2017-05-04 2021-10-18 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 불연속 수신을 위한 방법과 장치
CN111278171B (zh) * 2019-01-31 2022-05-17 维沃移动通信有限公司 一种非连续接收drx配置方法及终端
US11082344B2 (en) 2019-03-08 2021-08-03 GoTenna, Inc. Method for utilization-based traffic throttling in a wireless mesh network
EP3886498A1 (en) * 2020-03-27 2021-09-29 Nokia Technologies Oy Carrier selection in wireless network
US11612012B1 (en) 2020-09-18 2023-03-21 T-Mobile Innovations Llc DRX control for wireless user equipment
CN115022902B (zh) * 2022-05-30 2024-06-14 南通领讯信息技术有限公司 一种高频带利用率的无线通信方法及使用该方法的基站

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090207790A1 (en) * 2005-10-27 2009-08-20 Qualcomm Incorporated Method and apparatus for settingtuneawaystatus in an open state in wireless communication system
US8526377B2 (en) * 2008-03-25 2013-09-03 Telefonaktiebolaget Lm Ericsson (Publ) DRX functionality in multi-carrier wireless networks
EP2415305A1 (en) * 2009-03-31 2012-02-08 Telefonaktiebolaget LM Ericsson (publ) Methods and arrangements in a telecommunication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
JP2014131303A (ja) 2014-07-10
US20110105069A1 (en) 2011-05-05
JP2012526463A (ja) 2012-10-25
TW201130362A (en) 2011-09-01
CN102415201B (zh) 2015-04-01
KR20120006568A (ko) 2012-01-18
CN102415201A (zh) 2012-04-11
US8655395B2 (en) 2014-02-18
JP5524329B2 (ja) 2014-06-18
KR101378126B1 (ko) 2014-03-27
WO2010129597A1 (en) 2010-11-11
EP2428094A1 (en) 2012-03-14

Similar Documents

Publication Publication Date Title
EP2428094B1 (en) System, methods and apparatuses for facilitating discontinuous reception in a multi-carrier wireless communication system
US10033500B2 (en) Efficiently identifying system waveform in uplink transmission
US8175050B2 (en) Resource release and discontinuous reception mode notification
AU2008268310B2 (en) Channel interleaving structure for a wireless communication system
US8522101B2 (en) Physical HARQ indicator channel (PHICH) resource assignment signaling in a wireless communication environment
JP5685644B2 (ja) Ｆｄｄキャリアアグリゲーションのためのｄａｉ設計
EP2486755B1 (en) Mbsfn subframe generation and processing for unicast
US20130229965A1 (en) Paging during connected mode discontinuous reception (drx) operations
US20100232311A1 (en) Concurrent transmission of ack/nack, cqi and cqi from user equipment
US20100034147A1 (en) Systems, methods and apparatus for facilitating buffer status report robustness
WO2010025261A1 (en) Control of access terminal operation based on interference information

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: 20111109

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 SE SI SK SM TR

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

Effective date: 20130816

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/02 20090101ALN20181122BHEP

Ipc: H04W 76/28 20180101ALN20181122BHEP

Ipc: H04W 76/00 20180101AFI20181122BHEP

INTG Intention to grant announced

Effective date: 20181205

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/00 20180101AFI20181122BHEP

Ipc: H04W 52/02 20090101ALN20181122BHEP

Ipc: H04W 76/28 20180101ALN20181122BHEP

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602010061096

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0076040000

Ipc: H04W0076000000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTC Intention to grant announced (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/02 20090101ALN20190417BHEP

Ipc: H04W 76/00 20180101AFI20190417BHEP

Ipc: H04W 76/28 20180101ALN20190417BHEP

INTG Intention to grant announced

Effective date: 20190506

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

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 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: DE

Ref legal event code: R096

Ref document number: 602010061096

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1182839

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190918

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

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: 20191218

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: 20190918

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: 20190918

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: 20190918

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: 20191218

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: 20190918

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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: 20190918

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: 20191219

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: 20190918

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1182839

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190918

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

Ref country code: ES

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

Effective date: 20190918

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: 20190918

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: 20200120

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: 20190918

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: 20190918

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: 20190918

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: 20190918

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: 20190918

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

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: 20200224

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: 20190918

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: 20190918

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: 20190918

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010061096

Country of ref document: DE

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

PG2D Information on lapse in contracting state deleted

Ref country code: IS

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

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: 20190918

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: 20200119

26N No opposition filed

Effective date: 20200619

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: 20190918

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

Ref country code: CH

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

Effective date: 20200531

Ref country code: LI

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

Effective date: 20200531

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: 20190918

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200531

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

Ref country code: LU

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

Effective date: 20200504

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: 20200504

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

Ref country code: BE

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

Effective date: 20200531

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

Ref country code: TR

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

Effective date: 20190918

Ref country code: MT

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: 20190918

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: 20190918

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: 20190918

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

Ref country code: GB

Payment date: 20240411

Year of fee payment: 15

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

Ref country code: DE

Payment date: 20240226

Year of fee payment: 15

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

Ref country code: FR

Payment date: 20240415

Year of fee payment: 15