Timer activation upon collision during drx

Abstract

Embodiments of the present disclosure relate to a timer during discontinuous reception (DRX). In an aspect, a terminal device detects a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. The terminal device starts a timer based on detecting the collision. The terminal device monitors scheduling information while the timer is running.

Description

TIMER DURING DRXCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority from, and the benefit of, US Provisional Application No. 63 / 703403, filed October 4, 2024, which is hereby incorporated by reference in its entirety.FIELD

[0002] Various example embodiments relate to the field of communication and in particular, to methods, devices, apparatuses and a computer readable storage medium for timer during discontinuous reception (DRX).BACKGROUND

[0003] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network.

[0004] Such communication networks operate in accordance with standards, such as those promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of such standards include the so-called 5G (5th Generation) standard or other standards promulgated by 3GPP.SUMMARY

[0005] In general, example embodiments of the present disclosure provide a solution for mitigating the impact of the interruption and scheduling collision. With this solution, a timer for monitoring scheduling information is started based on detecting the collision, thereby improving the performance of communication with the discontinuous reception (DRX).

[0006] In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the terminal device at least to detect a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. The terminal device is further caused to start a timer based on detecting the collision. The terminal device is further caused to monitor scheduling information while the timer is running.

[0007] In a second aspect, there is provided a network device. The network device comprises at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the network device at least to receive, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and ascheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision. The network device is further caused to, based on ACK / NACK of a scheduled transmission is not received, retransmit the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0008] In a third aspect, there is provided a method implemented at a terminal device. The method comprises detecting a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. The method further comprises starting a timer based on detecting the collision. The method further comprises monitoring scheduling information while the timer is running.

[0009] In a fourth aspect, there is provided a method implemented at a network device. The method comprises receiving, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision. The method further comprises based on ACK / NACK of a scheduled transmission is not received, retransmitting the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0010] In a fifth aspect, there is provided an apparatus. The apparatus comprises means for means for detecting a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. The apparatus further comprises means for means for starting a timer based on detecting the collision. The apparatus further comprise means for monitoring scheduling information while the timer is running.

[0011] In a sixth aspect, there is provided an apparatus. The apparatus comprises means for means for receiving, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision. The apparatus further comprises means for based on ACK / NACK of a scheduled transmission is not received, retransmitting the scheduling information to the terminal device if the UE capability support the collision detecting.

[0012] In a seventh aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above third and fourth aspects.

[0013] In an eighth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform at least the method according to any one of the above third and fourth aspects.

[0014] In a ninth aspect, there is provided a terminal device. The terminal device comprises detecting circuitry configured to detect a collision between an interruption and a scheduling occasion during an on- duration of discontinuous reception, DRX. The terminal device further comprises starting circuitry configured to start a timer based on detecting the collision. The terminal device further comprises monitoring circuitryconfigured to monitor scheduling information while the timer is running.

[0015] In a tenth aspect, there is provided a network device. The network device comprises receiving circuitry configured to receive, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision. The network device further comprises retransmitting circuitry configured to, based on ACK / NACK of a scheduled transmission is not received, retransmit the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0016] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0018] FIG. 1A illustrates an example communication network in which embodiments of the present disclosure may be implemented;

[0019] FIG. 1 B illustrates the usage of the parameters of DRX;

[0020] FIG. 1 C illustrates an example of the PDCCH occasions during DRX on-duration;

[0021] FIG. 1 D illustrates example of scheduling during DRX on-duration;

[0022] FIG. 1 E illustrates measurements performed by a UE with gaps;

[0023] FIG. 1 F illustrates measurements performed by a UE with NCSG;

[0024] FIG. 1 G illustrates the message sequence chart for signalling of gap / NCSG support;

[0025] FIG. 1 H illustrates what happens if an interruption collides with the PDCCH reception;

[0026] FIG. 2 illustrates a flowchart illustrating an example of process 200 for mitigating a collision between an interruption and a scheduling occasion according to some embodiments of the present disclosure;

[0027] FIG. 3 illustration of mitigating a collision between an interruption and a scheduling occasion;

[0028] FIG. 4 illustrates a flowchart of a method implemented at a terminal device according to some other embodiments of the present disclosure;

[0029] FIG. 5 illustrates a flowchart of a method implemented at a network device according to some other embodiments of the present disclosure

[0030] FIG. 6 illustrates a simplified block diagram of an apparatus that is suitable for implementing embodiments of the present disclosure; and

[0031] FIG. 7 illustrates a block diagram of an example computer readable medium in accordance withsome embodiments of the present disclosure.

[0032] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION

[0033] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

[0034] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0035] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0036] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0037] The terminology used herein is for describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0038] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0039] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0040] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1 G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the future fifth generation (5G) and the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0041] As used herein, the term “network device” and “access network device” refer to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a transmission reception point (TRP), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a lowpower node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

[0042] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehiclemounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0043] FIG. 1 A illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented. As shown in FIG. 1A, the communication network 100 may include a terminal device 110, a network device 120, and a network device 122.

[0044] It is to be understood that the number of network devices and terminal devices is only for the purpose of illustration without suggesting any limitations. The system 100 may include any suitable number of network devices and terminal devices adapted for implementing embodiments of the present disclosure.

[0045] Communications in the communication system 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols of the first generation (1 G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G) and the sixth generation (6G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0046] FIG. 1 B illustrates the usage of the parameters of DRX. As shown in FIG. 1 B, the UE listens to the PDCCH every long DRX long cycle for the duration of the on-duration time period. The on-duration timeperiod may hold one or more PDCCH occasions. If the UE is scheduled during the on-duration period, the in-activity timer is started. The UE will continue to monitor the PDCCH during the period the in-activity timer is running. If the UE is scheduled during the running of the in-activity timer, the in-activity timer is re-started. If the UE is configured with short DRX cycles as well as long DRX cycles and if the UE has been scheduled in a long DRX cycle on-duration, the UE will also monitor the on-duration defined by the short DRX cycle on- duration. More than one short DRX periods may be defined for each long DRX cycle, the number of periods is part of the configuration.

[0047] FIG. 1 C illustrates an example of the PDCCH occasions during DRX on-duration. The PDCCH may hold the DCI, which may or may not schedule the UE for downlink and potentially uplink data scheduling occasions.

[0048] FIG. 1 D illustrates example of scheduling during DRX on-duration. The scheduling means the UE will start the DRX-lnactivityTimer, during which it will also listen for PDCCH during the DRX-lnactivityTimer.

[0049] FIG. 1 E illustrates measurements performed by a UE with gaps. As part of the RAN4 requirements, 3 gap types are Pre-configured MG (Pre-MG), Concurrent MG and NCSG. Measurement with gaps (Pre-MG, Concurrent MG) are performed when the gNB configures a measurement gap pattern (MGP) for the UE to perform measurements on serving (intra-frequency measurements) or non-serving carrier (inter-frequency measurements) as shown in FIG 1 E. Measurement gaps are configured by the network based on the UE indication on the need for measurement gaps. Gaps can be defined as a time window in which the UE is not expected to receive from nor transmit to the network, including PDCCH, PDSCH, PUCCH, PUSCH and reference signals such as PRS and SRS. The measurement gaps are configured by RRC. The configuration of a measurement gap, the MGP, includes the measurement gap repetition period, the measurement gap length, the gap offset and the measurement gap timing advance. Measurement gap length can be as short as 1.5 ms or as long as 20 ms, and the gap repetition period can be as short as 20 ms and as long as 160 ms. As an example, if the UE is performing SSB based L3 measurements, a typical SSB-burst length would be 5 ms, with a repetition of about 20 ms, and the network can configure a gap of 5.5 ms length with 80 ms repetition to match the fourth successive occurrence of that SSB-burst. Hence, a measurement gap has to cover the SSBs to be measured in the SSB burst but does not necessarily have to cover all available SSBs of that SSB burst.

[0050] FIG. 1 F illustrates measurements performed by a UE with NCSG. As shown in FIG. 1 E, the UE may also perform measurements with NCSG. NCSGs were developed to consider the UE that has a spare RF chain which can be used for measurements on given target carrier(s). During the measurement window (ML), the UE configured with NCSG can be scheduled in the serving cell to receive DL data or transmit UL data, while there is scheduling restriction in two small gaps before and after the measurement window (ML) covering the SMTC window, which are called visible interruption length (VIL). VIL is 1 ms for FR1 and 0.75 ms for FR2.

[0051] FIG. 1 G illustrates the message sequence chart for signalling of gap / NCSG support. The signaling associated with those 3 types of gaps includes RRC configuration and response messages. In Rel-16, the feature needForGaps was introduced for NR. One way that this feature can be configured, is during the RRCReconfiguration procedure, where the Network sends an RRCReconfiguration message 132 including the Information Element, IE, needForGapsConfigNR, which includes the NR bands for which the UE is requested to report the gap information. In response, the UE sends an RRCReconfigurationComplete message 134 including IE needForGapsInfoNR, which includes the list of Intra-Frequency cells for which a measurement gap is needed. The UE indicates that information including the gaplndication-r16 to indicate whether “gap” or “no-gap” is required. It also includes the list of inter-frequency bands for which a measurement gap is needed. In addition to the Rel-16 needForGaps, in Rel-17 needForNCSG was introduced in a similar manner, in which the UE indicates the need of NSCG gaps. In the case of NCSG, the UE includes additional information as part of the needForNCSG IE indicating “gap”, “ncsg”, “nogap-noncsg”. The network transmits the RRCReconfiguration message 136 to U with preConfiglnd-r17 and nscglnd-r17. The UE transmits RRCReconfigurationComplete message 134 to the network.

[0052] In 3GPP, it is agreed that interruptions are not allowed during DRX ON duration except the following scenarios. The first one is the time is extended due to drx-inactivityTime. The second one is there is SMTC occasion within a time period starting [4ms] before the starting point of the DRX ON duration and ending [4ms] after the ending point of the DRX ON duration. So there is the collision between interruptions because of measurements (or MUSIM procedures), with or without gaps, and DRX-ON periods.

[0053] FIG. 1 H illustration of what happens if an interruption collides with the PDCCH reception of the device while it is being scheduled by the network. If the PDCCH occasion is missed because of an interruption, the network has no means of knowing whether this is because of an interruption or because of bad radio conditions. As shown in FIG. 1 H, if the UE performs an interruption on top of a PDCCH scheduling data, the device will not receive the scheduling in the DCI provided in the PDCCH and for this reason do not receive the PDSCH data in the downlink. The device will therefore also not transmit either ACK or NACK in the uplink scheduling occurrence. Additionally, since the device missed the scheduling DCI, it will not be aware that the network is expecting it to listen to DL during the DRX-I nactivityTimer. As the DRX-ON period has expired, the UE is no longer monitoring the PDCCH for a re-scheduling and therefore, the next possibility for the NW to schedule the device is after a full DRX cycle.

[0054] According to some embodiments of the present disclosure, there is provided a solution to overcome those issues mentioned above and mitigate the impact of the interruption and PDCCH scheduling collision. Principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0055] FIG. 2 illustrates a flowchart illustrating an example of process 200 for mitigating a collision between an interruption and a scheduling occasion according to some embodiments of the present disclosure. For thepurpose of discussion, the process 200 will be described with reference to FIG. 1 A. The process 200 may involve the terminal device 110, the network device 120 as illustrated in FIG. 1A. It would be appreciated that although the process 200 for link has been described in the communication system 100 of FIG. 1A, this process may be likewise applied to other communication scenarios where different network devices are jointly deployed.

[0056] In some embodiments, the network device 120 may receive 202 from the terminal device 110, capability information indicating that the terminal device is capable of detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and starting a timer based on detecting the collision. The terminal device 110 detects 204 a collision between an interruption and a scheduling occasion during an on-duration of DRX. The terminal device 110 starts 206 a timer based on detecting the collision. The terminal device 110 monitors 208 scheduling information while the timer is running. Based on ACK / NACK of a scheduled transmission is not received, the network device 120 retransmits the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0057] With the solution of the process, those issues mentioned above are solved and the solution of mitigating the impact of the interruption and scheduling collision, thereby improving the performance of communication with DRX.

[0058] FIG. 3 illustration of mitigating a collision between an interruption and a scheduling occasion. As shown in FIG. 3, the UE starts a timer DRX-lnterruptionTimer if there is a collision between a PDCCH / scheduling occasion and an interruption caused by the UE. During the DRX-lnterruptionTimer, the UE should be awake and monitoring PDCCH transmission from the network. The purpose of the DRX- lnterruptionTimer is to allow for further scheduling opportunities in case of interruptions during DRX-ON, so the configuration will give the opportunity for the network to re-schedule the device or send retransmissions. In the example of FIG. 3, after the retransmission the DRX-lnactivity timer is started, and normal DRX operation is resumed.

[0059] In some embodiments, the DRX-lnterruptionTimer is the same as the DRX-lnactivityTimer or another timer (for example, an existing timer) that extends the time where the UE is monitoring PDCCH.

[0060] In some embodiments, for the UE and network to both be aligned on the opportunity, the device and network must exchange a capability about the device detecting the collision and starting the DRX- lnterruptionTimer. If they are both not aligned, one of two situations might occur. In the first the network attempts to re-schedule the UE after the DRX ON, but the UE is back to sleep mode. In that case the scheduling resources are wasted when the UE is not awake. In the second situation, the network does not attempt to retransmit the UE and the UE extends the activity timer. In this case, increased energy consumption would be experienced by the UE. The missing of a scheduling occasion may also be because of bad radio conditions. In this case, the UE will not receive the re-scheduling. It is important that the device and the network are aligned on the behavior. There are several solutions to align.

[0061] In some embodiments, the terminal device 110 transmits to the network device 120 capability information that the terminal device 110 is capable of extending the DRX-ON in case the collision occurs. Specifically, the terminal device 110 can send a capability about the ability to extend the DRX-ON in cases where the DRX-ON collides with one or more interruption(s). This is then assumed to be the case from registration onwards

[0062] In some embodiments, the capability information is transmitted in a response to a DRX configuration. Specifically, the terminal device 110 can respond the capability as a response to the DRX configuration, meaning the terminal device 110 have the opportunity to evaluate the configuration and then respond on whether it can keep the DRX-ON periods free of interruptions.

[0063] In some embodiments, the capability information is included in assistance information of the terminal device 110. Specifically, the terminal device 110 can add the information to UE Assistance Information.

[0064] In some embodiments, the timer suggested in FIG. 3 is the DRX-I nactivityTimer, which gives the advantage that it is guaranteed there will be a PDCCH before it expires. But the solution is not limited to that. In some embodiments, the timer in FIG. 3 is a new timer defined in, for example, the DRX configuration or any other configuration message or structure. In some embodiments, the timer in FIG. 3 is any of the other DRX defined timers. In some embodiments, the timer in FIG. 3 is a factor, multiplied to any of the DRX timers, for example, existing DRX timers.

[0065] In view of the above description of the various embodiments of the present disclosure, these embodiments of the present disclosure provide the advantage of mitigate the impact of the interruption and scheduling collision and reducing delay in re-scheduling. Then the performance of communication with DRX is improved.

[0066] FIG. 4 shows a flowchart of an example method 400 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.

[0067] At block 410, the terminal device 110 detects a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. At block 420, the terminal device 110 starts a timer based on detecting the collision. At block 430, the terminal device 110 monitors scheduling information while the timer is running.

[0068] In some embodiments, the timer is configured by a DRX configuration. In some embodiments, the timer is determined by applying a factor to a DRX timer configured for the DRX. In some embodiments, the terminal device 110 transmits, to the network device 120, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs. In some embodiments, the capability information is transmitted in a response to a DRX configuration. In some embodiments, the capability information is included in assistance information of the terminal device. In some embodiments, thecapability information is included in generic capabilities of the terminal device exchanged during registration.

[0069] FIG. 5 shows a flowchart of an example method 500 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the network device 120 with reference to FIG. 1A.

[0070] At block 510, the network device 120 receive, from a terminal device, capability information indicating that the terminal device is capable of detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and starting a timer based on detecting the collision. At block 520, the network device 120 based on ACK / NACK of a scheduled transmission is not received, retransmits the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0071] In some embodiments, the timer is configured by a DRX configuration. In some embodiments, the timer is determined by applying a factor to a DRX timer configured for the DRX. In some embodiments, the network device 120 receives, from the terminal device 110, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs. In some embodiments, the capability information is received in a response to a DRX configuration. In some embodiments, the capability information is included in assistance information of the terminal device. In some embodiments, the capability information is included in generic capabilities of the terminal device exchanged during registration.

[0072] In some embodiments, an apparatus capable of performing any of the method 400 (for example, the terminal device 110) may comprise means for performing the respective steps of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0073] In some embodiments, the apparatus comprises means for detecting a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX. The apparatus comprises means for starting a timer based on detecting the collision. The apparatus comprises means for monitoring scheduling information when the timer is running.

[0074] In some embodiments, the timer is configured by a DRX configuration. In some embodiments, the timer is determined by applying a factor to a DRX timer configured for the DRX. In some embodiments, the apparatus comprises mean for transmitting, to the network device, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs. In some embodiments, the capability information is transmitted in a response to a DRX configuration. In some embodiments, the capability information is included in assistance information of the terminal device. In some embodiments, the capability information is included in generic capabilities of the terminal device exchanged during registration.

[0075] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 400. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0076] In some embodiments, an apparatus capable of performing any of the method 500 (for example, the network device 120) may comprise means for performing the respective steps of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0077] In some embodiments, the apparatus comprises means for receiving, from a terminal device, capability information indicating that the terminal device is capable of detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and starting a timer based on detecting the collision. The apparatus comprises means for based on ACK / NACK of a scheduled transmission is not received, retransmits the scheduling information to the terminal device if the UE capability supports the collision detecting.

[0078] In some embodiments, the timer is configured by a DRX configuration. In some embodiments, the timer is determined by applying a factor to a DRX timer configured for the DRX. In some embodiments, the apparatus comprises means for receiving, from the terminal device, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs. In some embodiments, the capability information is received in a response to a DRX configuration. In some embodiments, the capability information is included in assistance information of the terminal device. In some embodiments, the capability information is included in generic capabilities of the terminal device exchanged during registration.

[0079] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 500. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0080] FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure. The device 600 may be provided to implement the communication device, for example the terminal device 110, the network device 120 as shown in FIG. 1A. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.

[0081] The communication module 640 is for bidirectional communications. The communication module 640 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.

[0082] The processor 610 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0083] The memory 620 may include one or more non-volatile memories and one or more volatilememories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.

[0084] A computer program 630 includes computer executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 624. The processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 622.

[0085] The embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 5. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0086] In some embodiments, the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600. The device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. FIG. 7 shows an example of the computer readable medium 700 in form of CD or DVD. The computer readable medium has the program 630 stored thereon.

[0087] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0088] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computerexecutable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 400-500 as described above with reference to FIGS. 4-5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired invarious embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0089] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0090] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0091] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non- transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0092] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0093] Although the present disclosure has been described in languages specific to structural featuresand / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:1 . A terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: detect a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX; start a timer based on detecting the collision; and monitor scheduling information while the timer is running.

2. The terminal device of claim 1 , wherein the timer is configured by a DRX configuration.

3. The terminal device of claim 1 or 2, wherein the timer is determined by applying a factor to a DRX timer configured for the DRX.

4. The terminal device of any of claims 1 -3, wherein the terminal device is further caused to: transmit, to a network device, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs.

5. The terminal device of claim 4, wherein the capability information is transmitted in a response to a DRX configuration.

6. The terminal device of claim 4, wherein the capability information is included in assistance information of the terminal device.

7. The terminal device of claim 5 or 6, wherein the capability information is included in generic capabilities of the terminal device exchanged during registration.

8. A network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: receive, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision; andbased on ACK / NACK of a scheduled transmission is not received, retransmit the scheduling information to the terminal device if the UE capability supports the collision detecting.

9. The network device of claim 8, wherein the timer is determined and part of the DRX configuration.

10. The network device of claim 8 or 9, wherein the timer is determined by applying a factor to a DRX timer configured for the DRX.11 . The network device of any of claims 8-10, wherein the network device is further caused to: receive, from a terminal device, capability information that the terminal device is capable of extending the on-duration of the DRX in case the collision occurs.

12. The network device of claim 11 , wherein the information of the capability is received in a response to a DRX configuration.

13. The network device of claim 11 , wherein the capability information is included in assistance information of the terminal device.

14. The network device of claim 12 or 13, wherein the capability information is included in generic capabilities of the terminal device exchanged during registration.

15. A method comprising: detecting a collision between an interruption and a scheduling occasion during an on-duration of discontinuous reception, DRX; starting a timer based on detecting the collision; and monitoring scheduling information while the timer is running.

16. A method comprising: receiving, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision; and based on ACK / NACK of a scheduled transmission is not received, retransmitting the scheduling information to the terminal device if the UE capability supports the collision detecting.

17. An apparatus comprising: means for detecting a collision between an interruption and a scheduling occasion during an on- duration of discontinuous reception, DRX; means for starting a timer based on detecting the collision; and means for monitoring scheduling information while the timer is running.

18. An apparatus comprising: means for receiving, from a terminal device, capability information indicating that the terminal device is capable of (i) detecting a collision between an interruption and a scheduling occasion during an on-duration of DRX and (ii) starting a timer based on detecting the collision; and means for based on ACK / NACK of a scheduled transmission is not received, retransmitting the scheduling information to the terminal device if the UE capability support the collision detecting.

19. A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method of claim 15 or 16.

Images