US 9,949,164 B2Grant
Discontinuous reception (DRX) enhancements in LTE systems
Issue Date:2018-04-17
•11 Claims
•11 Drawing Sheets
Abstract
Embodiments of a system and method for providing DRX enhancements in LTE systems are generally described herein. In some embodiments, a system control module is provided for controlling communications via a communications interface. A processor is coupled to the system control module and is arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for control signals, the processor further monitoring subframes after the active time.
Metadata
Assignee
- Intel Corporation
Inventors
- Youn Hyoung Heo
- Yujian Zhang
- Jong-Kae Fwu
Application Information
Application Number:US 14/757,660
Filing Date:2015-12-23
Priority Date:2012-09-28
Art Unit:2471
Classifications
IPC:
H04W28/02H04W48/14H04W72/04H04W76/04H04L29/06H04W52/02H04W40/00H04W76/06H04B5/00H04W4/00H04W40/24H04W52/04H04W36/08H04W48/18
Field of Search:
H04W 72/0413H04B 17/318
Patent Drawings (11 sheets)
Description
RELATED APPLICATIONS
[0001] This application is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 14/125,749, filed on Dec. 12, 2013, which is a U.S. National Stage Filing under 35 U.S.C. 371 from International Application No. PCT/US2013/062210, filed on Sep. 27, 2013, and published as WO 2014/052774 A1 on Apr. 3, 2014, which claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Ser. No. 61/707,784, filed Sep. 28, 2012, and entitled “ADVANCED WIRELESS COMMUNICATION SYSTEMS AND TECHNIQUES,” which are hereby incorporated by reference in their entireties.
BACKGROUND
[0002] In LTE Release-11, discontinuous reception (DRX) is used as the time domain multiplexing (TDM) solution to solve in-device coexistence problem. In UE assistance information sent from UE to eNB, UE can report DRX starting offset, which is useful to reduce or avoid WiFi beacon collision. However, reporting a single DRX starting offset value has the problem that there is restriction on eNB scheduling flexibility. For example, if eNB already uses the same DRX starting offset for many other UEs, then using the same DRX starting offset results in that many subframes are overloaded while other subframes are underloaded.
[0003] In LTE Release-11, Enhanced Physical Downlink Control Channel (EPDCCH) is introduced. In E-PDCCH, each DCI is transmitted over one subframe. This is different from PDCCH which transmits within a first few symbols in a subframe. User equipment (UE) may monitor UE specific search space in ePDCCH when ePDCCH is configured. However, the UE also monitors common search space in PDCCH.
[0004] In LTE, an inactivity timer is started at the subframe when the UE receives initial DL and UL grant and counts from the next subframe. The PDCCH decoding may finish before the next subframe. However, if ePDCCH is introduced, the UE starts ePDCCH decoding in the end of the subframe because the UE needs to receive the subframe to decode the ePDCCH DCI message. Even if the UE decoding time is very short, the UE would not be able to complete the ePDCCH decoding in the next subframe at the earliest. Therefore, the UE could not determine whether the initial DL or UL grant is received in the next subframe. Due to the latency with ePDCCH decoding, the UE may not able to start the inactivity timer at the subframe.
[0005] If the next subframe is an active subframe, there is no problem even if the UE cannot start inactivity timer in the subframe in which the UE receives initial DL or UL grant. However, if the next subframe is an inactive subframe, the UE cannot monitor PDCCH or ePDCCH even if the active time is extended with inactivity timer because the decoding in ePDCCH has not completed.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] FIG. 1 schematically illustrates a high-level example of a network system comprising a UE and an eNB, in accordance with various embodiments;
[0007] FIG. 2 illustrates a radio frame structure according to an embodiment;
[0008] FIG. 3 illustrates a discontinuous reception (DRX) according to an embodiment;
[0009] FIGS. 4a-b illustrate the handling of an inactivity timer according to an embodiment;
[0010] FIG. 5 illustrates the state transitions for DRX according to an embodiment;
[0011] FIGS. 6a-c shows operation of DRX active time according to an embodiment;
[0012] FIG. 7 illustrates DRX enhancements in LTE systems according to an embodiment;
[0013] FIG. 8 illustrates parameters for DRX control according to an embodiment;
[0014] FIG. 9 schematically illustrates an example system that may be used to practice various embodiments described herein; and
[0015] FIG. 10 illustrates a block diagram of an example machine for providing DRX enhancements in LTE systems according to an embodiment.
DETAILED DESCRIPTION
[0016] Embodiments described herein provide DRX enhancements in LTE systems. A system control module is provided for controlling communications via a communications interface. A processor is coupled to the system control module and is arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for control signals, the processor further monitoring subframes after the active time.
[0017] FIG. 1 schematically illustrates a wireless communication network 100 in accordance with various embodiments. Wireless communication network 100 (hereinafter “network 100”) may be an access network of a 3GPP LTE network such as evolved universal terrestrial radio access network (“E-UTRAN”). The network 100 may include an eNB 105, configured to wirelessly communicate with a UE 110.
[0018] As shown in FIG. 1 , the UE 110 may include a transceiver module 120. The transceiver module 120 may be further coupled with one or more of a plurality of antennas 125 of the UE 110 for communicating wirelessly with other components of the network 100, e.g., eNB 105. The antennas 125 may be powered by a power amplifier 130 which may be a component of the transceiver module 120, as shown in FIG. 1 , or may be a separate component of the UE 110. In one embodiment, the power amplifier provides the power for transmissions on the antennas 125. In other embodiments, there may be multiple power amplifiers on the UE 110. Multiple antennas 125 allow the UE 110 to use transmit diversity techniques such as spatial orthogonal resource transmit diversity (SORTD).
[0019] FIG. 2 illustrates a radio frame structure 200 according to an embodiment. In FIG. 2 , the radio frame 200 has an overall length of 10 ms 214. This is then divided into a total of 20 individual slots 210. Each subframe 212 includes of two slots 210 of length 0.5 ms, and each slot 210 contains a number of OFDM symbols, Nsymb 220. Thus, there are 10 subframes 212 within frame 200. Subframe #18 is shown expanded with reference to a subcarrier (frequency) axis 216 and an OFDM symbol (time) axis 218.
[0020] A resource element (RE) 230 is the smallest identifiable unit of transmission and includes a subcarrier 232 for an OFDM symbol period 234. Transmissions are scheduled in larger units called resource blocks (RBs) 240 which comprise a number of adjacent subcarriers 232 for a period of one 0.5 ms timeslot. Accordingly, the smallest dimensional unit for assigning resources in the frequency domain is a “resource block” (RB) 240, i.e., a group of NscRB adjacent subcarriers 232 constitute a resource block (RB) 240. Each subframe 212 includes “NRB” resource blocks, i.e., the total number of the subcarriers within subframe NRB×NscRB 250.
[0021] FIG. 3 illustrates a discontinuous reception (DRX) 300 according to an embodiment. Normally, user equipment (UE) is used to read PDCCH for allocations in the subframes. However, an inactivity timer is used to time the duration in downlink subframes that the UE waits to successfully decode a PDCCH, from the last successful decoding of a PDCCH. If the timer fails, the UE will re-enter a discontinuous reception (DRX) mode.
[0022] In FIG. 3 , subframes 310 are received by a UE. The subframes may be characterized as part of a continuous reception 320, a long DRX cycle 330 or a short DRX cycle 340. UE checks for scheduling message 350, which may be indicated by a C-RNTI on the PDCCH during the on duration 352. The on duration 352 may be for a long DRX cycle 330 or a short DRX cycle 340 depending on the current active cycle. The on duration 352 is the duration in downlink subframes 310 that the UE waits for, after waking up from DRX to receive PDCCHs. If the UE successfully decodes a PDCCH, the UE stays awake and starts an inactivity timer.
[0023] When a scheduling message 350 is received during an on duration 352, the UE starts the DRX inactivity timer and monitors the PDCCH in the subframes 310. During this monitoring period, the UE may be in a continuous reception mode 320. If a scheduling message 350 is received and the DRX inactivity timer is running, the DRX inactivity timer is restarted by the UE. When the inactivity timer expires 360, the UE moves into a short DRX cycle 340 and a DRX short cycle timer is initiated. The short DRX cycle 340 may be initiated by a media access control (MAC) control element. When the short DRX cycle expires 370, the UE moves into a long DRX cycle 330.
[0024] FIGS. 4a-b illustrate the handling of an inactivity timer 400 according to an embodiment. In FIG. 4a , two subframes 410, 412 are shown. A PDCCH 420 is decoded. The UE restarts the inactivity timer 430 following the successful decoding of a PDCCH 420 for a first transmission, i.e., not for retransmissions. The PDCCH decoding 420 may finished before the next subframe.
[0025] FIG. 4b shows an ePDCCH 440 is provided in a subframe 410. The UE starts ePDCCH decoding 420 at the end of the subframe because the UE needs to receive the subframe to decode the ePDCCH DCI message. Even if the UE decoding time is very short, the UE may not be able to complete the ePDCCH before the start of the next subframe 412. Therefore, the UE cannot determine whether the initial DL or UL grant is received in the next subframe. Due to the latency with ePDCCH decoding, the UE may not able to start the inactivity timer 450 at the subframe 412.
[0026] If the next subframe 412 is an active subframe, there is no problem even if the UE cannot start the inactivity timer in the subframe 410 in which the UE receives initial DL or UL grant. However, if the next subframe 412 is an inactive subframe, the UE cannot monitor PDCCH or ePDCCH even if the active time is extended with the inactivity timer because the decoding in ePDCCH has not completed.
[0027] FIG. 5 illustrates the state transitions for DRX 500 according to an embodiment. In FIG. 5 , states corresponding to the long DRX cycle 510, the short DRX cycle 520, and the continuous reception mode 530 are entered when certain criterion is met. The UE moves from continuous reception mode 530 to a short DRX cycle 520, from the short DRX cycle 520 to a long DRX cycle 510, and from the long DRX cycle 510 to continuous reception mode 530. However, the UE may move between the continuous reception mode 530 and one of the short DRX cycle 520 or the long DRX cycle 510. Transition may be controlled either by timers or by explicit commands from the eNB.
[0028] The inactivity timer starts when the UE is in the continuous reception mode 530. If the UE does not receive any new resource allocation information until the expiry of the inactivity timer 540, 570, the UE transits to the next level of the DRX cycle; that is, it transits to a short DRX cycle 520 if configured, and transits 570 to a long DRX cycle 510 otherwise.
[0029] When the UE moves into a short DRX cycle 520, the UE starts the short cycle timer. The UE stays in the short DRX cycle 520 until the expiry of the short cycle timer 550, and moves to a long DRX cycle 510 at the expiry of the short cycle timer 550. If the UE receives any resource allocation information 560 while the short cycle timer is running, the UE moves from the short DRX cycle 520 to continuous reception mode 530. More specifically, the UE immediately moves back to continuous reception mode 530 when the UE receives resource allocation information 560, 562 indicating a new transmission during any of the DRX cycle 510, 520.
[0030] In continuous reception mode 530, the UE is monitoring the PDCCH in the subframes. Thus, the continuous reception mode 530 may be matched to the time when the inactivity timer is running. In the short DRX cycle 520 and the long DRX cycle 510, the UE monitors the PDCCH for some of the subframes out of the available subframes. The UE's power consumption can be reduced because the UE monitors a small portion of the possible subframes.
[0031] Referring again to FIG. 3 , the on duration 380, 352 and the DRX periods 382 are shown. The PDCCH monitoring time in each DRX cycle, continuous reception 320, long DRX cycle 330 and short DRX cycle 340 is called the on duration 380. The on duration 380, 352 is located in the first part of each DRX cycle. More specifically, a DRX cycle includes an on duration during which the UE monitors the PDCCH and the DRX period 382 during which the UE is allowed not to monitor the PDCCH.
[0032] The number of subframes or the length of time that a UE uses to monitor the PDCCH in one DRX cycle is controlled by an on duration timer. At the beginning of each DRX cycle, the UE starts the on duration timer and monitors the PDCCH while the on duration timer is running. The length of the on duration timer controls the scheduling flexibility of the eNB. If the length of the on duration timer is one subframe 310, the eNB can send a resource allocation message during that one subframe 310. However, if the length of the on duration timer is more than one subframe, the eNB can select one of the available subframes to send the resource allocation information. This is beneficial to the eNB especially when the PDCCH is heavily loaded. Thus, depending on the length of the on duration timer, the eNB can have flexibility regarding when to send resource allocation information. However, this comes at a cost to the UE, because monitoring of one more subframe means more consumption of the UE's battery.
[0033] FIGS. 6a-c shows operation of DRX active time 600 according to an embodiment. In FIG. 6a , the original active time 610 is shown. The active time 610 is the time when a UE monitors the PDCCH for possible resource allocation information. This active time 610 includes the time period when timers such as inactivity timer, retransmission timer, and on duration timer are running. Regardless of the DRX cycle used, the UE monitors the PDCCH during an on duration.
[0034] FIG. 6b shows the extension of the active time according to an embodiment. When resource allocation information is received during the active time, the UE starts or restarts the inactivity timer and monitors for receipt of PDCCH signaling 620 in a subframe while the inactivity timer 622 is running. Thus, resource allocation information received during the active time effectively causes an extension of the active time 630.
[0035] FIG. 6c illustrates the end of the active time according to an embodiment. At the expiry of the inactivity timer or on receipt of a DRX Command 640, e.g., MAC CE, the UE stops the active time 650 and moves into a short DRX cycle 660. Alternative, a long DRX cycle (not shown in FIG. 6c ) may be entered. The UE monitors for PDCCH during the duration on periods 662.
[0036] FIG. 7 illustrates DRX enhancements in LTE systems 700 according to an embodiment. In FIG. 7 , subframes 710 are shown with an active time 720 set for monitoring a group of the subframes 730. For ePDCCH support, the controller module 732 of the UE monitors PDCCH or ePDCCH in the group of subframes 730 and then also monitors subframes after the active time 720 until the UE knows whether the active time 720 has been extended. This means that the UE receives PDCCH or ePDCCH in the subframe regardless of the decoding time used for the control channel including PDCCH and ePDCCH if the associated subframe is within the active time 720.
[0037] For example, assuming that the end of the active time is subframe (n) 740, the system controller 732 of the UE monitors PDCCH or ePDCCH in the subframe (n+1) 742, (n+2) 744, . . . , (n+k) 746. Herein, k is a number that is determined based on the UE processing time for ePDCCH. The time for ePDCCH decoding time may be around 0.5 ms. Therefore, the UE monitors PDCCH or ePDCCH in the subframe (n+1), where the subframe (n) 740 is the end of active time 720. The UE finishes decoding ePDCCH of subframe (n) 740 within the time period of subframe (n+1) 742. The UE may need to actually decode ePDCCH of subframe (n+1) 742, although ePDCCH there is no initial grant to the UE in the subframe (n) 740 after the decoding.
[0038] FIG. 8 illustrates parameters for DRX control 800 according to an embodiment. In FIG. 8 , the DRX configuration 810 includes parameters for setting the on duration timer 820, the inactivity timer 830, the retransmission timer 840, the long DRX cycle start offset 850 and the short DRX cycle timer 860. A coexistence-friendly value 852 is added for the long DRX cycle 850 for LTE+ Bluetooth voice scenario parameter to support 70 ms long DRX cycle values. For the long DRX cycle start offset 850, a value 852 of 70 ms may be used to support 70 ms long DRX cycle values. A long DRX cycle of 70 ms, for example, is beneficial because, for LTE TDD UL/DL Configuration 0, the HARQ timing period is 70 ms. If 70 ms long DRX cycle value is not supported, then the HARQ timing will be broken for the TDD UL/DL Configuration 0.
[0039] FIG. 9 schematically illustrates an example system 900 that may be used to practice various embodiments described herein. FIG. 9 illustrates, for one embodiment, an example system 900 having one or more processor(s) 905, system control module 910 coupled to at least one of the processor(s) 905, system memory 915 coupled to system control module 910, non-volatile memory (NVM)/storage 920 coupled to system control module 910, and one or more communications interface(s) 925 coupled to system control module 910.
[0040] In some embodiments, the system 900 may be capable of functioning as the UE 110 as described herein. In other embodiments, the system 900 may be capable of functioning as the eNB 95 depicted in the embodiment shown in FIG. 1 or any one of the other described embodiments. In some embodiments, the system 900 may include one or more computer-readable media (e.g., system memory or NVM/storage 920) having instructions and one or more processors (e.g., processor(s) 905) coupled with the one or more computer readable media and configured to execute the instructions to implement a module to perform actions described herein. System control module 910 for one embodiment may include any suitable interface controllers to provide for any suitable interface to at least one of the processor(s) 905 and/or to any suitable device or component in communication with system control module 910. Processor(s) 905 may be arranged to implement an on duration timer 940, an inactivity timer 942, a retransmission timer 944, a long DRX cycle timer 946 and a short DRX cycle timer 948.
[0041] System control module 910 may include memory controller module 930 to provide an interface to system memory 915. The memory controller module 930 may be a hardware module, a software module, and/or a firmware module.
[0042] System memory 915 may be used to load and store data and/or instructions, for example, for system 900. System memory 915 for one embodiment may include any suitable volatile memory, such as suitable DRAM, for example. In some embodiments, the system memory 915 may include double data rate type four synchronous dynamic random-access memory (DDR4 SDRAM). System control module 910 for one embodiment may include one or more input/output (I/O) controller(s) to provide an interface to NVM/storage 920 and communications interface(s) 925.
[0043] The NVM/storage 920 may be used to store data and/or instructions, for example. NVM/storage 920 may include any suitable non-volatile memory, such as flash memory, for example, and/or may include any suitable non-volatile storage device(s), such as one or more hard disk drive(s) (HDD(s)), one or more compact disc (CD) drive(s), and/or one or more digital versatile disc (DVD) drive(s), for example. The NVM/storage 920 may include a storage resource physically part of a device on which the system 900 is installed or it may be accessible by, but not necessarily a part of, the device. For example, the NVM/storage 920 may be accessed over a network via the communications interface(s) 925.
[0044] Communications interface(s) 925 may provide an interface for system 900 to communicate over one or more network(s) and/or with any other suitable device. The system 900 may wirelessly communicate with the one or more components of the wireless network in accordance with any of one or more wireless network standards and/or protocols.
[0045] For one embodiment, at least one of the processor(s) 905 may be packaged together with logic for one or more controller(s) of system control module 910, e.g., memory controller module 930. For one embodiment, at least one of the processor(s) 905 may be packaged together with logic for one or more controllers of system control module 910 to form a System in Package (SiP). For one embodiment, at least one of the processor(s) 905 may be integrated on the same die with logic for one or more controller(s) of system control module 910. For one embodiment, at least one of the processor(s) 905 may be integrated on the same die with logic for one or more controller(s) of system control module 910 to form a System on Chip (SoC).
[0046] In various embodiments, the system 900 may be, but is not limited to, a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, the system 900 may have more or less components, and/or different architectures. For example, in some embodiments, the system 900 includes one or more of a camera, a keyboard, liquid crystal display (LCD) screen (including touch screen displays), non-volatile memory port, multiple antennas, graphics chip, application-specific integrated circuit (ASIC), and speakers.
[0047] FIG. 10 illustrates a block diagram of an example machine 1000 for providing DRX enhancements in LTE systems according to an embodiment upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. In alternative embodiments, the machine 1000 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate in the capacity of a server machine and/or a client machine in server-client network environments. In an example, the machine 1000 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 1000 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
[0048] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, at least a part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors 1002 may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on at least one machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
[0049] Accordingly, the term “module” is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform at least part of any operation described herein. Considering examples in which modules are temporarily configured, a module need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor 1002 configured using software; the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. The term “application,” or variants thereof, is used expansively herein to include routines, program modules, programs, components, and the like, and may be implemented on various system configurations, including single-processor or multiprocessor systems, microprocessor-based electronics, single-core or multi-core systems, combinations thereof, and the like. Thus, the term application may be used to refer to an embodiment of software or to hardware arranged to perform at least part of any operation described herein.
[0050] Machine (e.g., computer system) 1000 may include a hardware processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1004 and a static memory 1006, at least some of which may communicate with others via an interlink (e.g., bus) 1008. The machine 1000 may further include a display unit 1010, an alphanumeric input device 1012 (e.g., a keyboard), and a user interface (UI) navigation device 1014 (e.g., a mouse). In an example, the display unit 1010, input device 1012 and UI navigation device 1014 may be a touch screen display. The machine 1000 may additionally include a storage device (e.g., drive unit) 1016, a signal generation device 1018 (e.g., a speaker), a network interface device 1020, and one or more sensors 1021, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 1000 may include an output controller 1028, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR)) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
[0051] The storage device 1016 may include at least one machine readable medium 1022 on which is stored one or more sets of data structures or instructions 1024 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 1024 may also reside, at least partially, additional machine readable memories such as main memory 1004, static memory 1006, or within the hardware processor 1002 during execution thereof by the machine 1000. In an example, one or any combination of the hardware processor 1002, the main memory 1004, the static memory 1006, or the storage device 1016 may constitute machine readable media.
[0052] While the machine readable medium 1022 is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that configured to store the one or more instructions 1024.
[0053] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 1000 and that cause the machine 1000 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0054] The instructions 1024 may further be transmitted or received over a communications network 1026 using a transmission medium via the network interface device 1020 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks ((e.g., channel access methods including Code Division Multiple Access (CDMA), Time-division multiple access (TDMA), Frequency-division multiple access (FDMA), and Orthogonal Frequency Division Multiple Access (OFDMA) and cellular networks such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), CDMA 2000 1×* standards and Long Term Evolution (LTE)), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802 family of standards including IEEE 802.11 standards (WiFi), IEEE 802.16 standards (WiMax®) and others), peer-to-peer (P2P) networks, or other protocols now known or later developed.
[0055] For example, the network interface device 1020 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1026. In an example, the network interface device 1020 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 1000, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
Additional Notes & in Examples
[0056] In Example 1 includes subject matter (such as a device, apparatus, client or system) for a serving node, including a system control module for controlling communications via a communications interface and a processor, coupled to the system control module, the processor arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for control signals, the processor further monitoring subframes after the active time.
[0057] In Example 2 the subject matter of Example 1 may optionally include, wherein the processor detects and initiates decoding of a control signal received on the PDCCH during a time period associated with the subframe providing the control signal, the processor determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0058] In Example 3 the subject matter of any one or more of Examples 1-2 may optionally include, wherein the processor continues to monitor subsequent frames after the active time to determine whether a link grant is received in the subsequent frame while decoding the control signal.
[0059] In Example 4 the subject matter of any one or more of Examples 1-3 may optionally include, wherein the processor initiates the inactivity timer after decoding the control signal.
[0060] In Example 5 the subject matter of any one or more of Examples 1-4 may optionally include, wherein the control signal is received in a subframe during a continuous reception mode.
[0061] In Example 6 the subject matter of any one or more of Examples 1-5 may optionally include, wherein the control signal is received in a subframe during an on-duration period of a short discontinuous reception cycle.
[0062] In Example 7 the subject matter of any one or more of Examples 1-6 may optionally include, wherein the control signal is received in a subframe during an on-duration period of a long discontinuous reception cycle.
[0063] In Example 8 the subject matter of any one or more of Examples 1-7 may optionally include, wherein the processor is further arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for resource allocations, the processor further arranged to implement a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle, wherein the long discontinuous reception cycle is set to seventy milliseconds to allow monitoring during a HARQ timing period.
[0064] In Example 9 includes subject matter (such as a device, apparatus, client or system) for a serving node, including a system control module for controlling communications via a communications interface and a processor, coupled to the system control module, the processor arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for resource allocations, the processor further arranged to implement a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle, wherein the long discontinuous reception cycle is set to seventy milliseconds to allow monitoring during a HARQ timing period.
[0065] In Example 10 the subject matter of Example 9 may optionally include, wherein the processor is further arranged to implement an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for resource allocations, the processor further monitoring subframes after the active time.
[0066] In Example 11 the subject matter of any one or more of Examples 9-10 may optionally include, wherein the processor detects and initiates decoding of a control signal received on the PDCCH during a time period associated with the subframe providing the control signal, the processor determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0067] In Example 12 the subject matter of any one or more of Examples 9-11 may optionally include, wherein the processor continues to monitor subsequent frames after the active time to determine whether a link grant is received in the subsequent frame while decoding the control signal.
[0068] In Example 13 the subject matter of any one or more of Examples 9-12 may optionally include, wherein the processor initiates the inactivity timer after decoding the control signal.
[0069] In Example 14 the subject matter of any one or more of Examples 9-13 may optionally include, wherein the control signal is received in a subframe during a continuous reception mode.
[0070] In Example 15 the subject matter of any one or more of Examples 9-14 may optionally include, wherein the control signal is received in a subframe during an on-duration period of a short discontinuous reception cycle.
[0071] In Example 16 the subject matter of any one or more of Examples 9-15 may optionally include, wherein the control signal is received in a subframe during an on-duration period of a long discontinuous reception cycle.
[0072] In Example 17 may include subject matter (such as a method or means for performing acts) including, implementing an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for control signals, receiving a control signal in a subframe received on the physical downlink control channel, initiating decoding of the control signal during a time period associated with the subframe, determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent subframes for control signals received on the physical downlink control channel after the active time.
[0073] In Example 18 the subject matter of Example 17 may optionally include further comprises determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0074] In Example 19 the subject matter of any one or more of Examples 17-18 may optionally include, wherein the continuing to monitor subsequent subframes for control signals received on the physical downlink control channel after the active time comprises determining whether a link grant is received in the subsequent frame while decoding the control signal.
[0075] In Example 20 the subject matter of any one or more of Examples 17-19 may optionally include, wherein the receiving the control signal in the subframe received on the physical downlink control channel further comprises receiving the control signal in a subframe during a continuous reception mode.
[0076] In Example 21 the subject matter of any one or more of Examples 17-20 may optionally include, further comprising implementing a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle and setting a start offset of the long discontinuous reception cycle to seventy milliseconds to allow monitoring during a HARQ timing period.
[0077] In Example 22 the subject matter of any one or more of Examples 17-21 may optionally include, determining an active time for monitoring subframes on the physical downlink control channel for resource allocations based on an inactivity timer and on-duration timer, implementing a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle, and setting a start offset of the long discontinuous reception cycle to seventy milliseconds to allow monitoring during a HARQ timing period.
[0078] In Example 23 the subject matter of any one or more of Examples 17-22 may optionally include, further comprising monitoring subframes after the active time.
[0079] In Example 24 the subject matter of any one or more of Examples 17-23 may optionally include, further comprising detecting a control signal received on the PDCCH during a time period associated with the subframe providing the control signal, decoding the control signal, determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0080] Example 25 may include subject matter (such as means for performing acts or machine readable medium including instructions that, when executed by the machine, cause the machine to perform acts) including implementing an inactivity timer and an on-duration timer for determining an active time for monitoring subframes on the physical downlink control channel for control signals, receiving a control signal in a subframe received on the physical downlink control channel, initiating decoding of the control signal during a time period associated with the subframe, determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent subframes for control signals received on the physical downlink control channel after the active time.
[0081] In Example 26 the subject matter of Example 25 may optionally include determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0082] In Example 27 the subject matter of any one or more of Examples 25-26 may optionally include, wherein the continuing to monitor subsequent subframes for control signals received on the physical downlink control channel after the active time comprises determining whether a link grant is received in the subsequent frame while decoding the control signal.
[0083] In Example 28 the subject matter of any one or more of Examples 25-27 may optionally include, wherein the receiving the control signal in the subframe received on the physical downlink control channel further comprises receiving the control signal in a subframe during a continuous reception mode.
[0084] In Example 29 the subject matter of any one or more of Examples 25-28 may optionally include, implementing a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle and setting a start offset of the long discontinuous reception cycle to seventy milliseconds to allow monitoring during a HARQ timing period.
[0085] Example 30 may include subject matter (such as means for performing acts or machine readable medium including instructions that, when executed by the machine, cause the machine to perform acts) including determining an active time for monitoring subframes on the physical downlink control channel for resource allocations based on an inactivity timer and on-duration timer, implementing a continuous reception mode, a short discontinuous reception cycle and a long discontinuous reception cycle and setting a start offset of the long discontinuous reception cycle to seventy milliseconds to allow monitoring during a HARQ timing period.
[0086] In Example 31 the subject matter of Example 30 may optionally include, monitoring subframes after the active time.
[0087] In Example 32 the subject matter of any one or more of Examples 30-31 may optionally include, detecting a control signal received on the PDCCH during a time period associated with the subframe providing the control signal, decoding the control signal, determining whether the decoding of the control signal has been completed at the end of the subframe and continuing to monitor subsequent frames after the active time.
[0088] The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as “examples.” Such examples may include elements in addition to those shown or described. However, also contemplated are examples that include the elements shown or described. Moreover, also contemplate are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
[0089] Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
[0090] In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.
[0091] The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure, for example, to comply with 37 C.F.R. §1.72(b) in the United States of America. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth features disclosed herein because embodiments may include a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example. Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A user equipment (UE) comprising:
transceiver circuitry arranged to:
receive discontinuous reception (DRX) parameters from an evolved Node-B (eNB), the DRX parameters including a long DRX cycle parameter and a long DRX cycle start offset parameter,
the long DRX cycle start offset parameter to configure the UE to support one of a plurality of long DRX cycles that includes a long DRX cycle of seventy subframes; and
processing circuitry arranged to monitor a control channel in subframes as indicated by the DRX parameters.
2. The UE of claim 1, wherein the long DRX cycle start offset parameter configures the UE to a long DRX cycle of seventy subframes responsive to a UE indication of support for in-device coexistence (IDC).
3. The UE of claim 1, further comprising two or more antennas.
4. The UE of claim 1, wherein the transceiver circuitry is further arranged to communicate using Bluetooth communication.
5. The UE of claim 4, wherein the transceiver circuitry is configured to operate in a time division duplex (TDD) uplink/downlink (UL/DL) configuration 0.
6. The UE of claim 1, wherein:
the UE is configurable to support the long DRX cycle and a short DRX cycle, the DRX parameters further comprising a short DRX cycle parameter and a short DRX cycle start offset parameter, and
to monitor the control channel, the processing circuitry is arranged to decode downlink control information (DCI) of the PDCCH for a Cell Radio Network Temporary Identifier (C-RNTI) of the UE at a subframe dependent on which of the short or long DRX cycle the UE is in.
7. Baseband processing circuitry of a user equipment (UE), the baseband processing circuitry comprising:
transceiver circuitry arranged to:
receive discontinuous reception (DRX) parameters from an evolved Node-B (eNB), the DRX parameters including a long DRX cycle parameter and a long DRX cycle start offset parameter, the long DRX cycle start offset parameter to configure the UE to support one of a plurality of long DRX cycles that includes a long DRX cycle of seventy subframes for operation in time division duplex (TDD) uplink/downlink (UL/DL) configuration 0; and
processing circuitry arranged to monitor a control channel in subframes as indicated by the DRX parameters.
8. The baseband processing circuitry of claim 7, wherein the processing circuitry is further arranged to provide an indication that the UE supports in-device co-existence (DC).
9. The baseband processing circuitry of claim 7 wherein the baseband processing circuitry is configured as part of a user station configured for communication with a base station of the 3GPP LTE network.
10. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user station to configure the user station to perform operations to:
receive discontinuous reception (DRX) parameters from an evolved Node-B (eNB), the DRX parameters including a long DRX cycle parameter and a long DRX cycle start offset parameter,
the long DRX cycle start offset parameter to configure the UE to support one of a plurality of long DRX cycles that includes a long DRX cycle of up to seventy subframes; and
processing circuitry arranged to monitor a control channel in subframes as indicated by the DRX parameters.
11. The non-transitory computer-readable storage medium of claim 10, wherein the long DRX cycle start offset parameter is set to seventy subframes responsive to a UE indication of support for in-device coexistence (IDC).
Patent Citations (27)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2009/0181670(A1) | 2009-07-01 | Tseng | Applicant |
| US2010/0110896(A1) | 2010-05-01 | Tseng | Examiner |
| US2010/0110897(A1) | 2010-05-01 | Chun et al. | Applicant |
| US2010/0118815(A1) | 2010-05-01 | Kim | Examiner |
| US2011/0002281(A1) | 2011-01-01 | Terry et al. | Applicant |
| US2011/0199910(A1) | 2011-08-01 | Oh | Examiner |
| US2012/0120828(A1) | 2012-05-01 | Anderson et al. | Applicant |
| US2012/0188907(A1) | 2012-07-01 | Dayal | Examiner |
| US2012/0257522(A1) | 2012-10-01 | Adachi | Examiner |
| US2013/0100871(A1) | 2013-04-01 | Vujcic | Applicant |
| US2013/0121220(A1) | 2013-05-01 | Virtej et al. | Applicant |
| US2013/0301420(A1) | 2013-11-01 | Zhang | Examiner |
| US2014/0293973(A1) | 2014-10-01 | Lin et al. | Applicant |
| US2015/0109982(A1) | 2015-04-01 | Futaki | Applicant |
| US2015/0117286(A1) | 2015-04-01 | Kim et al. | Applicant |
| US2015/0305083(A1) | 2015-10-01 | Heo et al. | Applicant |
| CN101860946(A) | 2010-10-01 | Applicant | |
| CN102625421(A) | 2012-08-01 | Applicant | |
| CN102638880(A) | 2012-08-01 | Applicant | |
| EP2485540(A1) | 2012-08-01 | Applicant | |
| EP2901740(A1) | 2015-08-01 | Applicant | |
| JP2009171580(A) | 2009-07-01 | Applicant | |
| JP2012507971(A) | 2012-03-01 | Applicant | |
| KR1020150064016(A) | 2015-06-01 | Applicant | |
| KR101828887(B1) | 2018-02-01 | Applicant | |
| WO-2012109542(A1) | 2012-08-01 | Applicant | |
| WO-2014052774(A1) | 2014-04-01 | Applicant |
Non-Patent Literature (27)
- “U.S. Appl. No. 14/125,749, Corrected Notice of Allowance dated Feb. 9, 2016”, 2 pgs.Applicant
- “U.S. Appl. No. 14/125,749, Non Final Office Action dated Sep. 10, 2015”, 10 pgs.Applicant
- “U.S. Appl. No. 14/125,749, Notice of Allowance dated Dec. 24, 2015”, 10 pgs.Applicant
- “U.S. Appl. No. 14/125,749, Preliminary Amendment filed Dec. 12, 2013”, 8 pgs.Applicant
- “U.S. Appl. No. 14/125,749, Response filed Dec. 9, 2015 to Non Final Office Action dated Sep. 10, 2015”, 10 pgs.Applicant
- “Chinese Application Serial No. 201380044760.6, Voluntary Amendment filed Jan. 7, 2016”, W/ English claims, 5 pgs.Applicant
- “European Application Serial No. 13841346.3, Amendment filed Mar. 16, 2015”, 18 pgs.Applicant
- “European Application Serial No. 13841346.3, Extended European Search Report dated Mar. 3, 2016”, 8 pgs.Applicant
- “HARQ-ACK PUCCH Resources in Response to ePDCCH Detections”, R1-122259, 3GPP TSG RAN WG1 #69. Prague, Czech Republic. Samsung., (May 21, 2012), 2 pgs.Applicant
- “International Application Serial No. PCT/US2013/062210, International Preliminary Report on Patentability dated Apr. 9, 2015”, 15 pgs.Applicant
- “International Application Serial No. PCT/US2013/062210, International Search Report dated Feb. 28, 2014”, 4 pgs.Applicant
- “International Application Serial No. PCT/US2013/062210, Invitation to Pay Additional Fees and Partial Search Report dated Dec. 16, 2013”, 7 pgs.Applicant
- “International Application Serial No. PCT/US2013/062210, Written Opinion dated Feb. 28, 2014”, 13 pgs.Applicant
- “Japanese Application Serial No. 2015-528730, Office Action dated Nov. 4, 2015”, W/ English Translation, 11 pgs.Applicant
- “PUCCH resource for ePDCCH”, R1-123266, 3GPP TSG RAN WG1 Meeting #70. Qingdao, China. Sharp., [Online] retrieved from the internet<URL:http://www.3gpp.org/ftp/tsg_ranAA/G1 RL1/TSGR1_70/Docs/>, (Aug. 13, 2012), 8 pgs.Applicant
- “Japanese Application Serial No. 2016-030724, Examiners Decision of Final Refusal dated Aug. 22, 2017”, W/ English Translation, 11 pgs.Applicant
- “CR on the addition of the stage-2 agreements on IDC”, 3GPP TSG- RAN WG2 Meeting #79, Version 11.20, R2-124311, (Aug. 13-17, 2012), 7 pgs.Applicant
- “Japanese Application Serial No. 2016-030724, Office Action dated Apr. 11, 2017”, With English Translation, 12 pgs.Applicant
- “Japanese Application Serial No. 2016-030724, Office Action dated Dec. 6, 2016”, W/ English Translation, 10 pgs.Applicant
- “Korean Application Serial No. 10-2015-7005276, Office Action dated May 15, 2017”, W/ English Translation, 5 pgs.Applicant
- “Korean Application Serial No. 10-2015-7005276, Office Action dated Oct. 21, 2016”, with English Translation, 7 pgs.Applicant
- “Open issues of in-device coexistence”, 3GPP TSG RAN WG2 Meeting #79bis, R2-124968, (Oct. 8-12, 2012), 2 pgs.Applicant
- “RAN2 CR for REL-11 WI Core part: Signalling and procedure for interference avoidance for in-device coexistence”, 3GPP TSG-RAN Meeting #57, RP-121379, (Sep. 4-7, 2012), 1 pg.Applicant
- “Report of email discussion [78#49] LTE/IDC: IDC Indication”, Huawei, 3GPP TSG RAN WG2 Meeting #79, R2-123534, (Aug. 7, 2012), 41 pgs.Applicant
- “Report of email discussion [78#50] LTE/IDC: TDM DRX Details”, Ericsson, 3GPP TSG-RAN WG2#79 meeting, R2-123718, [Online] Retrieved from the Internet :<http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_79/Docs/>, (Aug. 7, 2012), 7 pgs.Applicant
- Huawei, et al., “36.331 CR introducing In-Device Coexistence (IDC)”, 3GPP TSG-RAN?57 RP-121404, [Online]. Retrieved from the Internet: <http://www.3gpp.org/ftp/tsg_ran/TSG_RAN/TSGR_57/Docs/RP-121404.zip>, (Sep. 5, 2012), 32 pgs.Applicant
- “Chinese Application Serial No. 201380044760.6, Office Action dated Feb. 5, 2018”, With/English Translation, 18 pgs.Applicant