Discontinuous reception mode configuration

Abstract

Various example embodiments of the present disclosure relate to discontinuous reception (DRX) mode configuration. A terminal device sends a request for DRX mode configuration of a DRX mode including a plurality of DRX cycles to a network device. A terminal device receives a DRX mode configuration including a first parameter and a second parameter from a network device. The first parameter indicates a number of the plurality of DRX cycles, and the second parameter indicates an amount of time added to or subtracted from at least one DRX cycle of the plurality of DRX cycles. Some example embodiments of the present disclosure can allow the terminal device to perform rapid adaptation of the DRX cycle, thereby avoiding misalignment between an integer DRX cycle and a non-integer XR service.

Description

Technical Field

[0001] Various example embodiments relate generally to the field of communications, and more particularly to terminal devices, network devices, methods, apparatuses, and computer-readable storage media configured for a discontinuous reception (DRX) mode. Background Art

[0002] Extended reality (XR) traffic exhibits quasi-periodic and multimodal burst patterns with high data rates, and can generally be categorized into two burst types by their size according to Technical Reports (TR) 38.838 and TR 38.835. Traffic periodicity is due to the three-dimensional (3D) video generation process, which creates a sequence of video frames per eye at a given sampling rate. Typical examples of sampling rates are 30, 60, 90, and 120 frames per second (fps). These frame rate values ​​correspond to traffic pattern periods with non-integer periods (e.g., 16.66 ms for 60 fps and 11.11 ms for 90 fps).

[0003] DRX is a basic technology that allows the configuration of DRX cycles in user equipment (UE). For LTE and 5G NR, the DRX cycle consists of an active period (drx-OnDuration) and an inactive period. During the active period, the UE monitors the control channel (e.g., the Physical Downlink Control Channel (PDCCH)). During the inactive period, the UE shuts down its circuits to save power. Summary of the Invention

[0004] In general, exemplary embodiments of the present disclosure provide a terminal device, network device, method, apparatus, and computer-readable storage medium for discontinuous reception (DRX) mode configuration. Specifically, exemplary embodiments of the present disclosure provide a solution for DRX mode configuration that allows a terminal device to quickly adapt the DRX cycle, thereby avoiding misalignment between integer DRX cycles and non-integer XR services.

[0005] In a first aspect, a terminal device is provided. The terminal device may include one or more transceivers; and one or more processors communicatively coupled to the one or more transceivers, and the one or more processors are configured to cause the terminal device to: send a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles to a network device; and receive the DRX mode configuration including a first parameter and a second parameter from the network device, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0006] In a second aspect, a network device is provided. The network device may include one or more transceivers; and one or more processors communicatively coupled to the one or more transceivers, and the one or more processors are configured to cause the network device to: receive a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles from a terminal device; and send the DRX mode configuration including a first parameter and a second parameter to the terminal device, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0007] In a third aspect, a method is provided. The method may include: sending, at a terminal device, a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles to a network device; and receiving, at the terminal device, from the network device, the DRX mode configuration including a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0008] In a fourth aspect, a method is provided. The method may include: receiving, at a network device, a request from a terminal device for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles; and sending, at the network device, to the terminal device, the DRX mode configuration including a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0009] In a fifth aspect, an apparatus is provided. The apparatus may include: means for sending, at a terminal device, a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles to a network device; and means for receiving, at the terminal device, from the network device, the DRX mode configuration including a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0010] In a sixth aspect, an apparatus is provided. The apparatus may include: means for receiving, at a network device, from a terminal device, a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles; and means for sending, at the network device, to the terminal device, the DRX mode configuration including a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to at least perform the method according to the third or fourth aspect.

[0012] In an eighth aspect, a computer program is provided, comprising instructions which, when executed by an apparatus, cause the apparatus to at least: send a request to a network device for a DRX mode configuration for a DRX mode comprising a plurality of discontinuous reception (DRX) cycles; and receive, at a terminal device, a DRX mode configuration from the network device comprising a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles and the second parameter indicates an amount of time added to or subtracted from at least one of the plurality of DRX cycles.

[0013] In a ninth aspect, a computer program is provided, comprising instructions which, when executed by an apparatus, cause the apparatus to at least: receive a request from a terminal device for a DRX mode configuration of a DRX mode comprising a plurality of discontinuous reception (DRX) cycles; and send, at a network device, a DRX mode configuration comprising a first parameter and a second parameter to the terminal device, wherein the first parameter indicates the number of the plurality of DRX cycles and the second parameter indicates an amount of time added to or subtracted from at least one of the plurality of DRX cycles.

[0014] In a tenth aspect, a terminal device is provided. The terminal device includes: a transmitting circuit configured to send a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles to a network device; and a receiving circuit configured to receive the DRX mode configuration including a first parameter and a second parameter from the network device, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0015] In an eleventh aspect, a network device is provided. The network device includes: a receiving circuit configured to receive a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles from a terminal device; and a transmitting circuit configured to transmit the DRX mode configuration including a first parameter and a second parameter to the terminal device, wherein the first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0016] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood 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] Figure 1A shows an example network environment in which example embodiments of the present disclosure may be implemented;

[0019] Figure 1B shows example time / clock drift between integer periods of a DRX cycle and non-integer periods of a frame relevant to some embodiments of the present disclosure;

[0020] Figure 2 shows an example signaling procedure for DRX mode configuration according to some embodiments of the present disclosure;

[0021] Figure 3 Another example signaling procedure for DRX mode configuration according to some embodiments of the present disclosure is shown;

[0022] Figure 4 An example flow chart for applying DRX mode configuration according to some embodiments of the present disclosure is shown;

[0023] Figure 5 An example flow chart of a method implemented at a terminal device according to some example embodiments of the present disclosure is shown;

[0024] Figure 6 An example flow chart illustrating a method implemented at a network device according to some example embodiments of the present disclosure is shown;

[0025] Figure 7 An example simplified block diagram illustrating a device suitable for implementing embodiments of the present disclosure is shown; and

[0026] Figure 8 An example block diagram illustrating an example computer-readable medium according to some embodiments of the present disclosure;

[0027] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0028] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways except for the manner described below.

[0029] 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 skill in the art to which this disclosure belongs.

[0030] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, whether or not explicitly described, it is understood that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments.

[0031] It will be understood that although the terms "first" and "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0032] The terms used herein are only used to describe the purpose of specific embodiments and are not intended to limit example embodiments. As used herein, the singular "one", "an" and "the" are also intended to include plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "comprises", "has", "has", "contains" and / or "contains" specify the existence of stated features, elements and / or components when used in this article, but do not exclude the existence or addition of one or more other features, elements, components and / or their combinations. As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar wording (wherein the list of two or more elements is combined 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 elements.

[0033] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementation only (such as implementation in purely analog circuits and / or digital circuits); and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions; and (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but which may not be present when the software is not required for operation.

[0034] This definition of circuitry applies to all uses of the term in this application, including any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit, or a processor (or multiple processors), or a 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 a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0035] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocol, including but not limited to third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols and / or subsequent protocols. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communications, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned systems.

[0036] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a 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 known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, pico, etc.).

[0037] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded equipment (LEEs), laptop mounted equipment (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercials, relay nodes, integrated access and backhaul (IAB) nodes, and / or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0038] As used herein, the terms "resource," "transmission resource," "resource block," "physical resource block" (PRB), "uplink (UL) resource," or "downlink (DL) resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, a resource in a combination of more than one domain, or any other resource that enables communication. Hereinafter, some example embodiments of the present disclosure will be described using resources in the time domain (e.g., subframes) as an example of transmission resources. Note that the example embodiments of the present disclosure are also applicable to other resources in other domains.

[0039] As mentioned above, DRX was introduced to save power and extend the battery life of the UE. If no scheduling occurs during the active period, the UE enters inactive mode at the end of the drx-OnDuration and waits until the end of the DRX cycle to wake up and monitor the control channel again. In contrast, if the UE is scheduled, it remains in active mode during a configurable period controlled by an inactivity timer that is started or restarted each time the UE is scheduled, and switches to sleep mode only when the timer expires. This mechanism can avoid the UE entering sleep mode too quickly, i.e., when there is still data to be sent or received, and increasing latency. Hybrid Automatic Repeat Request (HARQ) is supported during the DRX active period by configuring retransmission timers for DL ​​and UL, which are started after a packet is erroneously received, and their expiration can wake up the UE to enable it to receive a retransmission.

[0040] The current specification allows for at most two DRX configurations per UE, i.e., a short DRX cycle and a long DRX cycle. This limitation is inefficient for XR applications because it hardly allows the DRX configuration to fit the XR traffic pattern, and thus leads to energy waste and potential data loss due to the non-integer periodicity of XR traffic.

[0041] In particular, the current DRX configuration does not support non-integer periodicity for XR traffic. The difference between DRX integer and XR non-integer periods results in clock / time drift between the start of the DRX cycle's drx-OnDuration and the arrival of XR traffic. Reconfiguring the DRX cycle based on the XR frame pattern can be a rather slow process, as this change requires RRC signaling / procedures.

[0042] The current DRX specification, as described in Section 5.7 of TR 38.321 (for 5G NR), only allows for integer discontinuous reception cycles. This results in inefficient configuration of the DRX cycle for XR applications, as it does not fit the typical XR traffic periodicity. Reconfiguring the DRX cycle according to the XR frame pattern can be a rather slow process, as such changes require RRC signaling or procedures.

[0043] Therefore, the present disclosure proposes a solution for DRX mode configuration. According to an embodiment of the present disclosure, a terminal device sends a request for DRX mode configuration for a DRX mode including multiple DRX cycles to a network device. The terminal device receives a DRX mode configuration including a first parameter and a second parameter from the network device, wherein the first parameter indicates the number of multiple DRX cycles and the second parameter indicates the amount of time added to at least one DRX cycle of the multiple DRX cycles or the amount of time subtracted from at least one DRX cycle. It should be understood that the above process steps can work together, partially work together, or work independently of each other in the operation flow as described in the next section.

[0044] The solution for DRX alignment of services with non-integer periods provided in this disclosure extends and enhances the DRX mechanism to adapt the parameters of the DRX cycle configuration to suit the service patterns of XR applications. This solution provides a new DRX mode (also known as DRX super mode) for the UE to adapt the DRX cycle under the control of the gNB. Specifically, it allows the UE to perform fast adaptation of the DRX cycle, thereby avoiding misalignment between integer DRX cycles and non-integer XR services. Note that in this disclosure, the terms "DRX super mode" and "DRX mode" are both used to refer to the DRX mode proposed in this disclosure.

[0045] Using some example embodiments of the present disclosure, the relevant content of the corresponding 3GPP specifications can be updated as follows. Known TRs are TR 38.838 v.17.0.0, TR 38.835 v.1.0.1, and TR 38.321 v.17.3.0. This can be a DRX super-mode configuration for non-integer periodicity, which may require the following enhancements to the DRX-Config IE defined in TS 38.331. DRX-Config Information Element

[0046] With some example embodiments of the present disclosure, the relevant content of the corresponding 3GPP specification may be updated as follows: DRX super mode may require enhancements to the DRX procedure as defined in TS 38.321 clause 5.7 as follows.

[0047] For the purpose of illustration, reference will be made to FIG. Figure 8 However, it should be noted that these embodiments are given to enable those skilled in the art to understand the inventive concept of the present disclosure and implement the solutions proposed herein, and are not intended to limit the scope of the present application in any way.

[0048] refer to Figure 1A , which shows an example network environment 100A in which example embodiments of the present disclosure may be implemented. The network environment 100A may be part of a communication network and includes a terminal device 110 and a network device 120.

[0049] like Figure 1AAs shown, terminal device 110 may also be referred to as user equipment 110 or UE 110. Network device 120 may also be referred to as gNB 120. In some example embodiments, terminal device 110 may use a DRX super mode under the control of network device 120 to adapt the DRX cycle.

[0050] In some example embodiments, DRX super mode configuration may require extensions to the RRC connection establishment and reconfiguration procedures, as well as extensions to the DRX configuration information elements (IEs) exchanged via RRC configuration messages. These extensions and enhancements are used to adapt the parameters of the DRX cycle configuration to suit the traffic patterns of XR applications.

[0051] In some example embodiments, enhancements to the signaling process and control messages exchanged between network device 120 and terminal device 110 are used to dynamically adapt the DRX cycle according to the traffic pattern and / or the state of the terminal device. This requires, for example, defining a new MAC CE command to modify the DRX configuration to be used for the next burst.

[0052] refer to Figure 1B , which shows an example time / clock drift 100B between an integer periodicity of a DRX cycle and a non-integer periodicity of a frame relevant to some embodiments of the present disclosure. According to TR 38.838 and TR 38.835, a typical frame rate for XR applications is equal to 60 fps, which corresponds to an average inter-arrival time 128 (or periodicity) of video frames equal to 16.66 ms. Assuming that the network has configured a long DRX cycle 130 with drx-onDurationTimer=3, drx-InactivityTimer=2, drx-LongCycle=10 and drx-StartOffset=6 (no short DRX cycle is configured), this means that the UE monitors the PDCCH for at least 5 ms every 16 ms, depending on whether the service is scheduled to be transmitted after the expiration of the drx-onDurationTimer.

[0053] If no control message is received before the drx-onDurationTimer expires, the terminal device 110 enters the sleep mode. Figure 1BAs shown, when the terminal device 110 is scheduled and remains active for 5 ms per DRX cycle (i.e., assuming that the drx-InactivityTimer is triggered only once per DRX cycle), after eight frames (frames 102, 104, 106, 108, 112, 114, 116, and 118), the terminal device 110 will not detect the control message for the new video frame transmission (i.e., frame 122) because the cumulative gap 132 between the non-integer XR periodicity and the DRX cycle is 5.33 ms (0.667*8) (which is greater than 5 ms). Frame 122 is lost or delayed in the case of 60 fps. The network device 120 can detect this mismatch and trigger an RRC reconfiguration, but a period reconfiguration is necessary to resynchronize the DRX cycle with the XR periodicity, and the RRC reconfiguration introduces additional delay in the transmission.

[0054] refer to Figure 2 , which shows an example signaling process 200 for DRX mode configuration according to some embodiments of the present disclosure. As shown, the terminal device 110 sends (202) a request 206 for DRX mode configuration for a DRX mode including multiple DRX cycles to the network device 120. The network device 120 receives (204) the request 206 for DRX mode configuration for a DRX mode including multiple DRX cycles from the terminal device 110.

[0055] The network device 120 sends (210) a DRX mode configuration 212 including a first parameter and a second parameter to the terminal device 110. The first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles. The terminal device 110 receives (208) the DRX mode configuration 212 including the first parameter and the second parameter from the network device 120.

[0056] In some example embodiments, the network device 120 sends (210) a DRX mode configuration 212 comprising a first parameter, a second parameter and an optional third parameter to the terminal device 110 without receiving an explicit request 206 from the terminal device 110 for a DRX mode configuration for a DRX mode comprising a plurality of DRX cycles.

[0057] By achieving Figure 2 , a solution for DRX mode configuration can be provided. In this way, the DRX mode configuration including the first parameter and the second parameter can allow the terminal device to perform fast adaptation of the DRX cycle, thereby avoiding misalignment between integer DRX cycles and non-integer XR services.

[0058] In some example embodiments, the proposed configuration type to be applied in the present disclosure may be an extension of currently available DRX-related RRC signaling, or a separate configuration signaling that may be used to design, monitor, and optimize a super mode of a DRX cycle.

[0059] In some exemplary embodiments, the DRX hyper mode configuration parameters sent by the network device 120 to the terminal device 110 may include a hyper period, which may be referred to as drx-HyperPeriod (also referred to as a first parameter). drx-HyperPeriod may indicate the number of DRX cycles constituting the hyper period.

[0060] As an example, for a hyper pattern consisting of four DRX cycles with a duration in the set {10, 11, 11, 11}, drx-HyperPeriod is equal to four. As another example, for a hyper pattern consisting of three DRX cycles with a duration in the set {17, 16, 17}, drx-HyperPeriod is equal to three.

[0061] In some example embodiments, the DRX hyper mode configuration parameters sent by network device 120 to terminal device 110 may include a hyper drift, which may be referred to as drx-HyperDrift (also referred to as a second parameter). drx-HyperDrift may indicate the amount of time that is added to or subtracted from the drx-LongCycle parameter for certain DRX cycles. Certain DRX cycles may constitute a hyper period.

[0062] In some exemplary embodiments, the DRX hyper mode configuration parameters sent by the network device 120 to the terminal device 110 may include a hyper offset, which may be referred to as drx-HyperOffset (also referred to as a third parameter). The drx-HyperOffset may indicate the DRX cycle within the hyper period to which the hyper drift is applied.

[0063] In some example embodiments, drx-HyperOffset may be used by terminal device 110 and network device 120 to track DRX iterations with an internal counter (i.e., an internal variable) to verify whether an update condition holds for applying drx-HyperDrift. In some example embodiments, drx-HyperOffset may be zero. In some example embodiments, drx-HyperOffset may also be specified to always apply the drift to the first or last cycle within a timeout period.

[0064] In some example embodiments, the terminal device 110 may derive the variable drx-HyperPeriodDuration based on the configuration.The terminal device 110 may maintain the variables drx-HyperCounter and drx-Counter for DRX operation.

[0065] In some example embodiments, terminal device 110 may determine the hyperduration drx-HyperPeriodDuration by determining the sum of the durations of the periods comprising the timeout period.

[0066] In some example embodiments, formula (1) may be used to determine the variable drx-HyperPeriodDuration: drx-HyperPeriodDuration=DRX period x drx-HyperPeriod+drx-HyperDrift (1)

[0067] In some example embodiments, drx-HyperDrift may be negative. In some example embodiments, depending on the sign and absolute value of drx-HyperDrift, formula (1) may add or subtract drx-HyperDrift from the DRX cycle. As an example, a hyper mode may consist of four DRX cycles with durations in the set {10, 11, 11, 11}, then drx-HyperPeriodDuration = 11 x 4 - 1 = 43.

[0068] In some example embodiments, terminal device 110 may determine a hyper DRX counter (referred to as a variable drx-HyperCounter). drx-HyperCounter may be incremented every drx-HyperPeriod. In some example embodiments, drx-HyperCounter may be incremented every timeout period.

[0069] In some example embodiments, the start of a new timeout period may be detected when condition (a) is true: [(SFNx10) + subframe number - drx-HyperPeriodDuration] = drx-StartOffset (a) SFN represents the system frame number.

[0070] In some example embodiments, terminal device 110 may determine a binary variable drx-ApplyHyperDrift. When condition (b) is true, drx-ApplyHyperDrift may be set to one: (drx-Counter)modulo(drx-HyperPeriod)=drx-HyperOffset (b) If the above condition is not true, drx-ApplyHyperDrift may be set to zero.

[0071] In some example embodiments, the terminal device 110 may determine a DRX counter drx-Counter. The drx-Counter may be incremented every DRX cycle. In some example embodiments, the terminal device 110 may increment the drx-Counter every DRX cycle. The start of a new DRX cycle may be detected when condition (c) is met: [(SFNx10)+subframe number-drx-HyperCounter x drx-HyperPeriodDuration+drx-ApplyHyperDrift xdrx-HyperDrift] modulo (drx-LongCycle + drx-ApplyHyperDrift x drx-HyperDrift)=0 (c)

[0072] In some example embodiments, conditions (b) and (c) may implement condition (d): If [(drx-Counter) modulo (drx-HyperPeriod) = drx-HyperOffset], the terminal device 110 may apply drx-HyperDrift to the DRX formula (1) to detect the start of the DRX cycle by setting drx-ApplyHyperDrift to 1. If not, the terminal device 110 will not apply drx-HyperDrift to the DRX formula (1) to detect the start of the DRX cycle by setting drx-ApplyHyperDrift to 0. (d)

[0073] In some example embodiments, if the terminal device 110 is configured with both a short DRX cycle and a long DRX cycle, different configurations may be configured for the short cycle and the long cycle, and the above formula (1) and conditions (a) to (d) operate independently for the short cycle and the long cycle, respectively.

[0074] In some example embodiments, terminal device 110 may implement condition (e) for starting a DRX OnDruration timer. In some example embodiments, terminal device 110 may determine condition (e) for detecting when an OnDuration timer may be started: [(SFNx10)+subframe number-drx-HyperCounter x drx-HyperPeriodDuration+drx-ApplyHyperDrift xdrx-HyperDrift] modulo (drx-LongCycle+drx-ApplyHyperDrift x drx-HyperDrift)=drx-StartOffset(e)

[0075] In some example embodiments, conditions (e) and (c) may implement condition (f): If (drx-Counter) modulo (drx-HyperPeriod) = drx-HyperOffset, the terminal device 110 may apply drx-HyperDrift to the DRX formula (1) to decide whether to start DRX OnDuration. If not, the terminal device 110 will not apply drx-HyperDrift to the DRX formula (1) to decide whether to start DRX OnDuration. (f)

[0076] In some example embodiments, a new signal format integrated with Layer 1 (L1) or Layer 2 (L2) signaling (such as MAC CE) may be used to trigger an update of the DRX super mode. In some example embodiments, the signal format may be defined by network device 120 to directly trigger an update of the current super mode.

[0077] In some example embodiments, the number of bits in the bitmap may be associated with drx-HyperPeriod. In some example embodiments, this may be a MAC CE with only a header and no payload. Upon receiving this MAC CE, terminal device 110 uses drx-HyperDrift to adjust the subsequent DRX cycle. Therefore, network device 120 can dynamically adjust this value whenever needed.

[0078] In some example embodiments, the bitmap may be determined by various criteria, such as evaluating the results after performing a super offset on the current DRX cycle. If L1 signaling is utilized, the bitmap may be applied to the next timeslot. If MAC CE is utilized, the bitmap may be applied after an ACK is sent (or after an ACK is sent, the offset in network processing time may also be considered). In some example embodiments, other related parameters may also be configured.

[0079] An example of a DRX configuration with hyper mode parameters and variables is a DRX hyper mode that includes four DRX cycles with durations {10, 11, 11, 11}. The main parameters for implementing the hyper mode DRX configuration may be: drx-LongCycle = 11, drx-HyperPeriod = 4, drx-HyperDrift = -1, and drx-HyperOffset = 0. The main DRX variable for implementing the hyper mode may be: drx-HyperPeriodDuration = 43.

[0080] Another example of a DRX configuration with hyper mode parameters and variables is a DRX hyper mode that includes three DRX cycles with durations {17, 16, 17}. The main parameters for implementing the hyper mode DRX configuration may be: drx-HyperPeriod = 3, drx-HyperDrift = -1, and drx-HyperOffset = 1. The main DRX variable for implementing the hyper mode may be: drx-HyperPeriodDuration = 50.

[0081] In some example embodiments, a bitmap may be used to indicate the drx-HyperPeriod. The size of the bitmap may indicate the duration of the drx-HyperPeriod, and each bit of the bitmap may indicate whether drx-HyperDrift is applied at the drx-HyperOffset.

[0082] As an example, a bitmap "0111" may be sent by network device 120 to terminal device 110 so that a DRX super mode {10, 11, 11, 11} may be applied when the legacy DRX cycle is 11 ms, and a bitmap "010" may be sent by network device 120 to terminal device 110 so that a DRX super mode {17, 16, 17} may be applied when the legacy DRX cycle is 17 ms. In some example embodiments, network device 120 may use a new MAC CE command containing the bitmap "0111" to control or force terminal device 110 to apply super mode adjustment.

[0083] refer to Figure 3 , which shows another example signaling process 300 for DRX mode configuration according to some embodiments of the present disclosure. It should be understood that Figure 3 The example signaling process 300 in can be considered as Figure 2 An example of the signaling process 200 in FIG. Figure 3 The UE 302 is Figure 2 An example of a terminal device 110 in . Figure 3 The gNB 304 in Figure 2An example of a network device 120 in FIG.

[0084] In some example embodiments, UE 302 exchanges (306) capabilities with gNB 304 via RRC configuration or reconfiguration. gNB 304 exchanges (308) capabilities with UE 302 via RRC configuration or reconfiguration. In some example embodiments, legacy DRX-related parameters may be determined for operation by UE 302. In some example embodiments, the RRC configuration or reconfiguration signaling may include DRX configuration 310.

[0085] In some example embodiments, UE 302 may request (312) one or more signaling configurations 316 from gNB 304 to be used for performing DRX hyper mode related procedures. In some example embodiments, the requested configuration signaling message may include drx-HyperPeriod, drx-HyperDrift, and drx-HyperOffset. In some example embodiments, gNB 304 may receive (314) request 312.

[0086] In some example embodiments, the signaling channel to be used or the protocol layer to be used may be RRC. The requested configuration signaling message may be an extension of the available DRX configuration or a separate signaling. In some example embodiments, the requested configuration signaling message may include other parameters.

[0087] In some example embodiments, gNB 304 may send one or more signaling configurations for performing DRX super mode related procedures as requested from UE 302. The requested or determined configuration messages may be transmitted to UE 302 for subsequent DRX super mode related procedures.

[0088] In some example embodiments, gNB 304 may send one or more signaling configurations for performing DRX super mode related procedures without an explicit request from UE 302. The determined configuration message may be transmitted to UE 302 for subsequent DRX super mode related procedures.

[0089] In some example embodiments, gNB 304 may determine whether to enable the MAC CE indication message to trigger a hyper mode update using the bitmap and drx-HyperDrift. The bitmap information may be converted into a hyper mode parameter set {drx-HyperPeriod, drx-HyperDrift, drx-HyperOffset}. In some example embodiments, the same signaling channel or protocol layer as in 306 or 308 may be used, such as RRC.

[0090] In some example embodiments, a frame (such as an XR frame) may arrive 324 at gNB 304 for transmission. In some example embodiments, block 326 illustrates an example embodiment. UE 302 may check or verify 328 the time or evaluate a DRX iteration condition. In some example embodiments, the DRX iteration condition may be conditions (c) and (d) as described above.

[0091] In some example embodiments, UE 302 may monitor 330 the current DRX cycle to apply the configured super mode of the DRX cycle. In some example embodiments, UE 302 may only be allowed to statically apply the configured DRX super mode throughout the setup, and updates to the super mode may be determined via RRC reconfiguration. In some example embodiments, gNB 304 may not control forced updates to the configured super mode.

[0092] In some example embodiments, block 332 illustrates another example embodiment. gNB 304 may send (334) a DRX hypermode adjustment indication signal 338 to UE 302 upon arrival of a frame at the RAN. UE 302 may receive (336) indication signal 338. In some example embodiments, a signal format for a hypermode adjustment trigger may be defined depending on a configured timeout period drx-HyperPeriod. As an example, if the configured timeout period drx-HyperPeriod = 4, a four-bit indication may be generated and sent to UE 302. In some example embodiments, L1 / L2 signaling (e.g., MAC CE) may be used to trigger UE 302 to perform subsequent adaptation.

[0093] In some example embodiments, UE 302 may monitor 340 the current hyper-mode of the DRX cycle. In some example embodiments, gNB 304 may control UE 302 to update the hyper-mode of the DRX cycle by means of a bitmap indication. The bitmap indication may be appropriately converted into a set of parameters {drx-HyperPeriod, drx-HyperDrift, drx-HyperOffset, drx-HyperPeriodDuration}. Thus, additional flexibility is introduced at the network.

[0094] In some example embodiments, a frame (such as an XR frame) may be transmitted (342). In some example embodiments, UE 302 and gNB 304 may perform a result evaluation by applying the current adjustments (344). In some example embodiments, the desired key performance indicator (KPI) for evaluation for a given period may be at least one of: successful or unsuccessful reception of a frame, quality of service (QoS) requirements, power saving gains, cell throughput, and capacity loss. In some example embodiments, the predefined KPIs may be evaluated jointly or individually. In some example embodiments, depending on the evaluation results, gNB 304 may be facilitated to generate a new bitmap indication via a MAC CE to adjust the current settings at 334 or 336. In some example embodiments, the process may return to 320 for RRC reconfiguration.

[0095] In some example embodiments, UE 302 may send (346) a result feedback indication 350 to gNB 304. gNB 304 may receive (348) the result feedback indication 350. In some example embodiments, the gNB may store (352) the evaluation result for post-processing.

[0096] refer to Figure 4 , which shows an example flow chart for applying DRX mode configuration 400 according to some embodiments of the present disclosure. It should be understood that Figure 4 The example flow chart of DRX mode configuration 400 in FIG. 4 can be considered as Figure 3 An example of the signaling process 300 in FIG. Figure 4 Reference will be made to UE 302 and gNB 304.

[0097] In some example embodiments, at 402, UE 302 may receive hyper mode related configuration parameters for DRX from gNB 304 upon receiving a legacy DRX configuration via RRC. The message may include drx-HyperPeriod, drx-HyperDrift, and drx-HyperOffset.

[0098] In some example embodiments, UE 302 may apply configured legacy DRX settings for operation from the gNB at 404. The legacy static DRX configuration may include drx-LongCycleStartOffset, drx-onDurationTimer, drx-InactivityTimer, and drx-SlotOffset.

[0099] In some example embodiments, UE 302 may start DRX using the current counter i at 406. In some example embodiments, depending on the configuration at 402, UE 302 may also start using DRX super mode and start a counter j.

[0100] In some example embodiments, at 408, the UE may begin directly applying and updating or not applying and updating the DRX super mode, depending on whether new MAC CE information is received at the UE 302. In some example embodiments, the gNB 304 may be allowed to control and trigger the updating of the DRX super mode based on a bitmap indication.

[0101] In some example embodiments, if new MAC CE information is received at UE 302, the process may continue to 414. In some example embodiments, if new MAC CE information is not received at UE 302, the process may continue to 410.

[0102] In some example embodiments, UE 302 may evaluate a condition as to whether it is the right time to perform an update based on the current hyper mode related parameters at 410. In some example embodiments, UE 302 may evaluate condition (c) (also referred to as a first predefined condition) to verify whether it is time to apply the current hyper mode.

[0103] In some example embodiments, if condition (c) is met, the process may continue to 412. If condition (c) is not met, the process may continue to 424. At 412, UE 302 may evaluate condition (d) (also referred to as a second predefined condition) to verify whether it is time to apply super drift. In some example embodiments, if condition (d) is met, the process may continue to 414. If condition (d) is not met, the process may continue to 424.

[0104] In some example embodiments, at 414, UE 302 may directly apply the indicated DRX super mode based on the bitmap indication of the MAC CE. In some example embodiments, UE 302 may reset the DRX super counter j=0. This is supported because UE 302 may be configured to perform a DRX super mode update, thereby requiring a reset of the counter.

[0105] In some example embodiments, at 416, UE 302 may monitor the current DRX cycle based on received hyper mode parameters or MAC CE indications. As an example, the indication may be parameter-based. For parameter-based indications, UE 302 may receive DRX hyper mode related parameters including drx-HyperPeriod=4, drx-HyperDrift=-1, drx-HyperOffset=0, drx-HyperPeriodDuration=43, and drx-LongCycle=11. These parameters may result in a hyper mode of {10, 11, 11, 11}.

[0106] In some example embodiments, it may be a MAC CE indication. For the MAC CE indication, it may be a bitmap. As an example, a bitmap of "0111" may be received at UE 302. When the legacy DRX cycle is configured with drx-LongCycle=11 and drx-HyperDrift=-1, the bitmap of "0111" may result in a hyper pattern of {10, 11, 11, 11}.

[0107] In some example embodiments, at 418, UE 302 may check whether the end of the superduration drx-HyperPeriodDuration has been reached. If the end of the superduration drx-HyperPeriodDuration has been reached, the process may continue to 420. In some example embodiments, at 420, UE 302 may increment a DRX superduration counter j=j+1. If the end of the superduration drx-HyperPeriodDuration has not been reached, the process may continue to 422. In some example embodiments, at 422, UE 302 may reset a DRX counter i=0. In some example embodiments, at 424, UE 302 may increment a DRX counter i=i+1.

[0108] refer to Figure 5 , which shows an example flow chart of a method 500 implemented at a terminal device according to some example embodiments of the present disclosure. Figure 1A For reference.

[0109] At 502, the terminal device 110 sends a request for a DRX mode configuration of a DRX mode including a plurality of DRX cycles to the network device 120. At 504, the terminal device 110 receives the DRX mode configuration including a first parameter and a second parameter from the network device 120. The first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0110] In some example embodiments, the DRX pattern configuration may include a third parameter indicating at least one DRX cycle to which the time amount is applied. In some example embodiments, the terminal device 110 may determine that the time amount is applied to a first DRX cycle of the plurality of DRX cycles based on determining that the DRX pattern configuration does not include the third parameter indicating at least one DRX cycle to which the time amount is applied.

[0111] In some example embodiments, the amount of time may be predefined to be applied to at least one of the plurality of DRX cycles.In some example embodiments, the terminal device 110 may determine the period duration of the DRX mode based on at least one of: the DRX cycle, the first parameter, or the second parameter.

[0112] In some example embodiments, the terminal device 110 may, upon detecting the start of a period of the DRX mode, increment a DRX period counter for the DRX mode. In some example embodiments, the start of the period of the DRX mode may be determined based on at least one of: a system frame number, a subframe number, a period duration of the DRX mode, or a DRX start offset.

[0113] In some example embodiments, the terminal device 110 may, upon detecting the start of the DRX cycle, increment a DRX cycle counter for the DRX cycle. In some example embodiments, the start of the DRX cycle may be determined based on at least one of the following: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, the third parameter, a long DRX cycle, or a short DRX cycle.

[0114] In some example embodiments, the DRX mode configuration of the DRX mode may be configured for one of the long DRX cycle or the short DRX cycle of the terminal device 110. In some example embodiments, different DRX mode configurations for different DRX modes may be configured for the other of the long DRX cycle or the short DRX cycle of the terminal device 110.

[0115] In some example embodiments, the terminal device 110 may start the DRXOnDuration timer based on at least one of the following: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter is applied, the second parameter, a third parameter, a long DRX cycle, a short DRX cycle, or a DRX start offset.

[0116] In some example embodiments, the binary variable may be determined based on at least one of: a DRX cycle counter for the DRX cycle, the first parameter, or the third parameter.

[0117] In some example embodiments, the DRX mode configuration of the DRX mode may be a first DRX mode configuration of the first DRX mode, and the terminal device 110 may receive an indication from the network device 120 to apply the second DRX mode configuration of the second DRX mode instead of the first DRX mode configuration of the first DRX mode.

[0118] In some example embodiments, the indication may include at least one of: a bitmap, wherein the number of bits is determined based on at least one of the first parameter and the third parameter; or a medium access control (MAC) control element (CE) having a header but no payload.

[0119] In some example embodiments, the indication may be received via at least one of layer 1 signaling or layer 2 signaling. In some example embodiments, terminal device 110 may apply the second DRX mode configuration in the next time slot based on determining that the indication was received via layer 1 signaling. In some example embodiments, terminal device 110 may apply the second DRX mode configuration based on sending an acknowledgement (ACK) to network device 120 based on determining that the indication was received via layer 2 signaling.

[0120] In some example embodiments, a bitmap may be used to indicate the first parameter. In some example embodiments, a size of the bitmap may indicate a duration of a DRX mode period. In some example embodiments, a bit of the bitmap may indicate whether the second parameter is applied to a DRX cycle in a plurality of DRX cycles.

[0121] In some exemplary embodiments, the terminal device 110 may apply the second DRX mode configuration according to the second DRX mode configuration determined based on the indication to directly apply the second DRX mode, and may reset the DRX period counter for the second DRX mode.

[0122] In some exemplary embodiments, the terminal device 110 may determine, based on the second DRX mode configuration, whether a first predefined condition related to the start of a DRX mode period is met based on determining an indication of a second DRX mode configuration for not directly applying the second DRX mode, and increment a DRX cycle counter for the DRX cycle based on determining that the first predefined condition is not met.

[0123] In some exemplary embodiments, the terminal device 110 may determine whether a second predefined condition is satisfied based on determining that the first predefined condition is satisfied, where the second predefined condition is related to whether the second parameter is applied.

[0124] In some example embodiments, the terminal device 110 may increment a DRX cycle counter for the DRX cycle based on determining that the second predefined condition is not met.

[0125] In some example embodiments, the terminal device 110 may reset the DRX period counter for the second DRX mode based on determining that the second predefined condition is satisfied.

[0126] In some example embodiments, the terminal device 110 may monitor the DRX cycle based on at least one of the second DRX mode configuration or an indication received from the network device 120 after resetting the DRX period counter for the second DRX mode.

[0127] In some exemplary embodiments, the terminal device 110 may increment a DRX period counter for the second DRX mode based on determining that the end of the period of the second DRX mode has been reached.

[0128] In some example embodiments, the terminal device 110 may reset the DRX cycle counter based on determining that the end of the period has not been reached.

[0129] In some example embodiments, terminal device 110 may determine an evaluation result of a second DRX mode configuration to apply the second DRX mode, and may send the evaluation result to network device 120 .

[0130] In some example embodiments, the evaluation result may be based on at least one of: successful or unsuccessful reception of a frame, quality of service (QoS) requirements, power saving gains, cell throughput, or capacity loss.

[0131] In some example embodiments, the DRX mode configuration of the DRX mode may be received via at least one of: a bare DRX configuration message, a separate configuration message distinct from the DRX configuration message, or a configuration message defined for the DRX mode.

[0132] In some example embodiments, at least one of the first parameter, the second parameter, and the third parameter may be included in a DRX configuration information element (IE).

[0133] refer to Figure 6 , which shows an example flow chart of a method 600 implemented at a network device according to some example embodiments of the present disclosure. Figure 1A For reference.

[0134] At 602, the network device 120 receives a request for a DRX mode configuration including a plurality of discontinuous reception (DRX) cycles from the terminal device 110. At 604, the network device 120 sends the DRX mode configuration including a first parameter and a second parameter to the terminal device 110. The first parameter indicates the number of the plurality of DRX cycles, and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0135] In some example embodiments, the DRX pattern configuration may include a third parameter indicating at least one DRX cycle to which the time amount is applied. In some example embodiments, where the DRX pattern configuration does not include a third parameter indicating at least one DRX cycle to which the time amount is applied, the time amount may be applied to a first DRX cycle of the plurality of DRX cycles.

[0136] In some example embodiments, the amount of time may be predefined to be applied to at least one of the plurality of DRX cycles.In some example embodiments, network device 120 may determine the period duration of the DRX pattern based on at least one of: the DRX cycle, the first parameter, or the second parameter.

[0137] In some example embodiments, network device 120 may increment a DRX period counter for the DRX mode based on detecting the start of a period of the DRX mode.

[0138] In some example embodiments, the start of the period of the DRX mode may be determined based on at least one of: a system frame number, a subframe number, a period duration of the DRX mode, or a DRX start offset.

[0139] In some example embodiments, network device 120 may, upon detecting the start of the DRX cycle, increment a DRX cycle counter for the DRX cycle. In some example embodiments, the start of the DRX cycle may be determined based on at least one of: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, the third parameter, a long DRX cycle, or a short DRX cycle.

[0140] In some example embodiments, the DRX mode configuration of the DRX mode may be configured for one of the long DRX cycle or the short DRX cycle of the terminal device 110. In some example embodiments, different DRX mode configurations for different DRX modes may be configured for the other of the long DRX cycle or the short DRX cycle of the terminal device 110.

[0141] In some example embodiments, network device 120 may increment a DRX period counter for the DRX mode based on detecting the start of a period of the DRX mode.

[0142] In some example embodiments, the start of the period of the DRX mode may be determined based on at least one of: a system frame number, a subframe number, a period duration of the DRX mode, or a DRX start offset.

[0143] In some example embodiments, network device 120 may, upon detecting the start of the DRX cycle, increment a DRX cycle counter for the DRX cycle. In some example embodiments, the start of the DRX cycle may be determined based on at least one of: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, the third parameter, a long DRX cycle, or a short DRX cycle.

[0144] In some example embodiments, the DRX mode configuration of the DRX mode may be configured for one of the long DRX cycle or the short DRX cycle of the terminal device 110. In some example embodiments, different DRX mode configurations for different DRX modes may be configured for the other of the long DRX cycle or the short DRX cycle of the terminal device 110.

[0145] In some example embodiments, network device 120 may start the DRXOnDuration timer based on at least one of the following: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, a third parameter, a long DRX cycle, or a short DRX cycle.

[0146] In some example embodiments, the DRX mode configuration of the DRX mode may be configured for one of the long DRX cycle or the short DRX cycle of the terminal device 110. In some example embodiments, different DRX mode configurations for different DRX modes may be configured for the other of the long DRX cycle or the short DRX cycle of the terminal device 110.

[0147] In some example embodiments, the network device 120 may start the DRXOnDuration timer based on at least one of the following: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, a third parameter, a long DRX cycle, a short DRX cycle, or a DRX start offset.

[0148] In some example embodiments, the binary variable may be determined based on at least one of: a DRX cycle counter for the DRX cycle, the first parameter, or the third parameter.

[0149] In some example embodiments, the DRX mode configuration of the DRX mode may be a first DRX mode configuration of the first DRX mode, and the network device 120 may send an indication to the terminal device 110 to apply the second DRX mode configuration of the second DRX mode instead of the first DRX mode configuration of the first DRX mode.

[0150] In some example embodiments, the indication comprises at least one of: a bitmap in which the number of bits is determined based on at least one of the first parameter and the third parameter, or a medium access control (MAC) control element (CE) having a header but no payload.

[0151] In some example embodiments, the indication may be transmitted via at least one of layer 1 signaling or layer 2 signaling. In some example embodiments, a bitmap may be used to indicate the first parameter. In some example embodiments, a size of the bitmap may indicate a period duration of the DRX mode. In some example embodiments, a bit of the bitmap may indicate whether the second parameter is applied to a DRX cycle in a plurality of DRX cycles.

[0152] In some example embodiments, network device 120 may receive an evaluation result of applying the second DRX mode configuration of the second DRX mode from terminal device 110. In some example embodiments, network device 120 may send an indication to terminal device 110 to apply a third DRX mode configuration of the third DRX mode instead of the second DRX mode configuration of the second DRX mode based on the evaluation result.

[0153] In some example embodiments, network device 120 may store the evaluation result and may perform post-processing on the evaluation result. In some example embodiments, the evaluation result may be based on at least one of: successful or unsuccessful reception of a frame, quality of service (QoS) requirements, power saving gains, capacity loss, or cell throughput.

[0154] In some example embodiments, the DRX mode configuration of the DRX mode may be transmitted via at least one of: an extension of a DRX configuration message, a separate configuration message different from the DRX configuration message, or a configuration message defined for the DRX mode.

[0155] In some example embodiments, at least one of the first parameter, the second parameter, and the third parameter may be included in a DRX configuration information element (IE).

[0156] In some embodiments, an apparatus capable of executing method 500 (e.g., terminal device 110) may include components for executing corresponding steps of method 500. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0157] In some embodiments, the apparatus may include: a component for sending a request for a DRX mode configuration of a discontinuous reception (DRX) mode including a plurality of DRX cycles to a network device; and a component for receiving a DRX mode configuration including a first parameter and a second parameter from the network device, wherein the first parameter indicates the number of the plurality of DRX cycles and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0158] In some embodiments, the DRX pattern configuration further comprises a third parameter indicating at least one DRX cycle to which the amount of time is applied.

[0159] In some embodiments, the apparatus may include means for determining that the amount of time is applied to a first DRX cycle of the plurality of DRX cycles based on determining that the DRX pattern configuration does not include a third parameter indicating at least one DRX cycle to which the amount of time is applied.

[0160] In some embodiments, the amount of time is predefined to be applied to at least one DRX cycle of the plurality of DRX cycles.

[0161] In some embodiments, the apparatus may include means for determining a period duration of the DRX mode based on at least one of: a DRX cycle, a first parameter, or a second parameter.

[0162] In some embodiments, the apparatus may include means for incrementing a DRX period counter for the DRX mode based on detecting the start of a period of the DRX mode.

[0163] In some embodiments, the start of the period of the DRX mode may be determined based on at least one of: a system frame number, a subframe number, a duration of the period of the DRX mode, or a DRX start offset.

[0164] In some embodiments, the apparatus may include means for incrementing a DRX cycle counter for the DRX cycle based on detecting the start of the DRX cycle.

[0165] In some embodiments, the start of the DRX cycle can be determined based on at least one of the following: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter is applied, the second parameter, a third parameter, a long DRX cycle, or a short DRX cycle.

[0166] In some embodiments, the DRX mode configuration of the DRX mode can be configured for one of the long DRX cycle or the short DRX cycle of the terminal device; and different DRX mode configurations of different DRX modes are configured for the other of the long DRX cycle or the short DRX cycle of the terminal device.

[0167] In some embodiments, the apparatus may include a component for starting a DRXOnDuration timer based on at least one of: a system frame number, a subframe number, a DRX period counter for a DRX mode, a period duration of the DRX mode, a binary variable indicating whether to apply a second parameter, a second parameter, a third parameter, a long DRX cycle, a short DRX cycle, or a DRX start offset.

[0168] In some embodiments, the binary variable may be determined based on at least one of: a DRX cycle counter for the DRX cycle, the first parameter, or a third parameter.

[0169] In some embodiments, the DRX mode configuration of the DRX mode may be a first DRX mode configuration of the first DRX mode.

[0170] In some embodiments, the apparatus may include means for receiving an indication from the network device to apply a second DRX mode configuration of the second DRX mode instead of the first DRX mode configuration of the first DRX mode.

[0171] In some embodiments, the indication comprises at least one of: a bitmap in which the number of bits is determined based on at least one of the first parameter and the third parameter; or a medium access control (MAC) control element (CE) having a header but no payload.

[0172] In some embodiments, the indication may be received via at least one of layer 1 signaling or layer 2 signaling.

[0173] In some embodiments, the apparatus may include means for applying a second DRX mode configuration in the next time slot based on determining that an indication is received via layer 1 signaling.

[0174] In some embodiments, the apparatus may include means for applying the second DRX mode configuration based on sending an acknowledgement (ACK) to the network device based on determining that the indication is received via layer 2 signaling.

[0175] In some example embodiments, the first parameter may be indicated using a bitmap. In some example embodiments, the size of the bitmap may indicate a period duration of the DRX mode. In some example embodiments, the bits of the bitmap may indicate whether the second parameter is applied to a DRX cycle in a plurality of DRX cycles.

[0176] In some embodiments, the apparatus may include: a component for applying the second DRX mode configuration according to the second DRX mode configuration determined to directly apply the second DRX mode based on the indication; and a component for resetting a DRX period counter for the second DRX mode.

[0177] In some embodiments, the apparatus may include: a component for determining, based on the second DRX mode configuration, whether a first predefined condition related to the start of a period of the DRX mode is satisfied, according to a second DRX mode configuration that determines based on an indication that the second DRX mode is not directly applied; and a component for incrementing a DRX cycle counter for the DRX cycle based on a determination that the first predefined condition is not satisfied.

[0178] In some embodiments, the apparatus may include: a component for determining whether a second predefined condition related to whether to apply a second parameter is satisfied based on determining that the first predefined condition is satisfied; and a component for incrementing a DRX cycle counter for a DRX cycle based on determining that the second predefined condition is not satisfied; and a component for resetting a DRX period counter for a second DRX mode based on determining that the second predefined condition is satisfied.

[0179] In some embodiments, the apparatus may include means for monitoring the DRX cycle based on at least one of the second DRX mode configuration or an indication received from the network device after resetting the DRX period counter for the second DRX mode.

[0180] In some embodiments, the apparatus may include means for incrementing a DRX period counter for the second DRX mode based on determining that an end of the period of the second DRX mode has been reached.

[0181] In some embodiments, the apparatus may include means for resetting the DRX cycle counter based on determining that the end of the time period has not been reached.

[0182] In some embodiments, the apparatus may include a component for determining whether a first predefined condition related to the start of a DRX mode period is met based on the second DRX mode configuration according to determining not to directly apply the second DRX mode based on the indication.

[0183] In some embodiments, the apparatus may include means for incrementing a DRX cycle counter for the DRX cycle based on determining that the first predefined condition is not met.

[0184] In some embodiments, the apparatus may include means for determining whether a second predefined condition related to whether to apply the second parameter is satisfied based on determining that the first predefined condition is satisfied.

[0185] In some embodiments, the apparatus may include means for incrementing a DRX cycle counter for the DRX cycle based on determining that the second predefined condition is not met.

[0186] In some embodiments, the apparatus may include means for resetting a DRX period counter for the second DRX mode based on determining that the second predefined condition is met.

[0187] In some embodiments, the apparatus may include means for monitoring the DRX cycle based on at least one of the second DRX mode configuration or an indication received from the network device after resetting the DRX period counter for the second DRX mode.

[0188] In some embodiments, the apparatus may include means for incrementing a DRX period counter for the second DRX mode based on determining that an end of the period of the second DRX mode has been reached.

[0189] In some embodiments, the apparatus may include means for resetting the DRX cycle counter based on determining that the end of the time period has not been reached.

[0190] In some embodiments, the apparatus may include: a component for determining an evaluation result of a second DRX mode configuration for applying a second DRX mode; and a component for sending the evaluation result to the network device.

[0191] In some embodiments, the evaluation result may be based on at least one of: successful or unsuccessful reception of a frame, quality of service (QoS) requirements, power saving gain, cell throughput, or capacity loss.

[0192] In some example embodiments, the DRX mode configuration of the DRX mode is received via at least one of: an extension of a DRX configuration message; a separate configuration message different from the DRX configuration message; or a configuration message defined for the DRX mode.

[0193] In some example embodiments, at least one of the first parameter, the second parameter, and the third parameter is included in a DRX configuration information element (IE).

[0194] In some example embodiments, the apparatus further comprises means for performing other steps of some example embodiments of method 500. In some example embodiments, the means comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause execution of the apparatus.

[0195] In some embodiments, an apparatus capable of executing method 600 (e.g., network device 120) may include components for executing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or a software module.

[0196] In some example embodiments, the apparatus may include: a component for receiving, from a terminal device, a request for a DRX mode configuration for a DRX mode including a plurality of discontinuous reception (DRX) cycles; and a component for sending, to the terminal device, the DRX mode configuration including a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles and the second parameter indicates an amount of time to be added to or subtracted from at least one of the plurality of DRX cycles.

[0197] In some example embodiments, the DRX pattern configuration may include a third parameter indicating at least one DRX cycle to which the time amount is applied. In some example embodiments, if the DRX pattern configuration does not include the third parameter indicating at least one DRX cycle to which the time amount is applied, the time amount may be applied to a first DRX cycle of the plurality of DRX cycles. In some example embodiments, the time amount may be predefined to be applied to at least one DRX cycle of the plurality of DRX cycles.

[0198] In some example embodiments, the apparatus may include means for determining a period duration of the DRX mode based on at least one of: a DRX cycle, a first parameter, or a second parameter.

[0199] In some example embodiments, the apparatus may comprise means for incrementing a DRX period counter for the DRX mode based on detecting the start of a period of the DRX mode.

[0200] In some example embodiments, the start of the period of the DRX mode is determined based on at least one of: a system frame number, a subframe number, a duration of the period of the DRX mode, or a DRX start offset.

[0201] In some example embodiments, the apparatus may comprise means for incrementing a DRX cycle counter for the DRX cycle based on detecting the start of the DRX cycle.

[0202] In some example embodiments, the start of the DRX cycle may be determined based on at least one of: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether the second parameter applies, the second parameter, a third parameter, a long DRX cycle, or a short DRX cycle.

[0203] In some example embodiments, the DRX mode configuration of the DRX mode may be configured for one of a long DRX cycle or a short DRX cycle of the terminal device. In some example embodiments, different DRX mode configurations of different DRX modes may be configured for the other of a long DRX cycle or a short DRX cycle of the terminal device.

[0204] In some example embodiments, the apparatus may include means for starting a DRXOnDuration timer based on at least one of: a system frame number, a subframe number, a DRX period counter for the DRX mode, a period duration of the DRX mode, a binary variable indicating whether to apply the second parameter, the second parameter, a third parameter, a long DRX cycle, a short DRX cycle, or a DRX start offset.

[0205] In some example embodiments, the binary variable may be determined based on at least one of: a DRX cycle counter for the DRX cycle, the first parameter, or a third parameter.

[0206] In some example embodiments, the DRX mode configuration of the DRX mode may be a first DRX mode configuration of the first DRX mode. In some example embodiments, the apparatus may include: means for sending an indication to the terminal device to apply the second DRX mode configuration of the second DRX mode instead of the first DRX mode configuration of the first DRX mode.

[0207] In some example embodiments, the indication may include at least one of: a bitmap, wherein the number of bits is determined based on at least one of the first parameter and the third parameter; or a medium access control (MAC) control element (CE) having a header but no payload.

[0208] In some example embodiments, the indication may be transmitted via at least one of layer 1 signaling or layer 2 signaling. In some example embodiments, the first parameter may be indicated using a bitmap; the size of the bitmap indicates the duration of the period of the DRX mode; and the bits of the bitmap indicate whether the second parameter is applied to a DRX cycle in the plurality of DRX cycles.

[0209] In some example embodiments, the apparatus may include: a component for receiving an evaluation result of a second DRX mode configuration for applying a second DRX mode from a terminal device; and a component for sending an indication to the terminal device of a third DRX mode configuration for applying a third DRX mode instead of the second DRX mode configuration of the second DRX mode based on the evaluation result.

[0210] In some example embodiments, the apparatus may include: a component for storing the evaluation result; and a component for post-processing the evaluation result.

[0211] In some example embodiments, the evaluation result may be based on at least one of: successful or unsuccessful reception of a frame; quality of service (QoS) requirements; power saving gain; capacity loss; or cell throughput.

[0212] In some example embodiments, the DRX mode configuration of the DRX mode is sent via at least one of: an extension of a DRX configuration message; a separate configuration message different from the DRX configuration message; or a configuration message defined for the DRX mode.

[0213] In some example embodiments, at least one of the first parameter, the second parameter, and the third parameter is included in a DRX configuration information element (IE).

[0214] In some example embodiments, the apparatus further comprises means for performing other steps of some example embodiments of method 600. In some example embodiments, the means comprises at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause execution of the apparatus.

[0215] refer to Figure 7 , which shows an example simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1A The terminal device 110 is shown. As shown, the device 700 includes one or more processors 710, one or more memories 720 can be coupled to the processor 710, and one or more communication modules 740 can be coupled to the processor 710.

[0216] The communication module 740 is used for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary to communicate with other network elements, for example, the communication interface can be wireless or wired to other network elements, or a software-based interface for communication.

[0217] As non-limiting examples, processor 710 can be of any type suitable for a local technology network and can include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0218] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during a power outage.

[0219] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in ROM 724. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0220] The embodiments of the present disclosure can be implemented with the aid of a program so that the device 700 can execute the following steps: Figures 2 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware, or by a combination of software and hardware.

[0221] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (e.g., memory 720) or other storage device accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium into the RAM 722 for execution. The computer-readable medium may include any type of tangible, non-volatile storage device, such as a ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 is shown in the form of a CD or DVD. The computer readable medium has a program 730 stored thereon.

[0222] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0223] 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 computer executable instructions, such as instructions included in a program module, executed in a device on a target real or virtual processor to perform the above-referenced Figure 5 or Figure 6 Method 500 or 600 described herein. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. Machine-executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0224] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0226] The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include an electrical connection with one or more wires, a portable computer disk, 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. As used herein, the term "non-transient" is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation on data storage persistence (e.g., RAM versus ROM).

[0227] In addition, although the operation is described in a specific order, this should not be understood as requiring the specific order shown or to perform such operation in a sequential order, or to perform all operations shown to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure, but should be interpreted as describing the features that can be specific to a particular embodiment. Some features described in the context of a separate embodiment also can be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment also can be realized in multiple embodiments individually or in any suitable subcombination.

[0228] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the 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

1. A terminal device, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: sending a request for a discontinuous reception (DRX) mode configuration including a plurality of DRX cycles to a network device; and The DRX mode configuration includes a first parameter and a second parameter, wherein the first parameter indicates the number of the plurality of DRX cycles and the second parameter indicates an amount of time added to or subtracted from at least one DRX cycle in the plurality of DRX cycles. 2 . The terminal device according to claim 1 , wherein the DRX mode configuration further comprises a third parameter indicating the at least one DRX cycle to which the amount of time is applied.

3. The terminal device according to claim 1, wherein the terminal device is further configured to: Based on determining that the DRX pattern configuration does not include a third parameter indicating the at least one DRX cycle to which the amount of time is applied, determining that the amount of time is applied to a first DRX cycle of the plurality of DRX cycles. 4 . The terminal device of claim 1 , wherein the amount of time is predefined to be applied to at least one DRX cycle of the plurality of DRX cycles.

5. The terminal device according to any one of claims 1 to 4, wherein the terminal device is further caused to determine the period duration of the DRX mode based on at least one of the following: DRX cycle, the first parameter, or the second parameter.

6. The terminal device according to any one of claims 1 to 5, wherein the terminal device is further configured to: Based on detecting the start of a period of the DRX mode, a DRX period counter for the DRX mode is incremented.

7. The terminal device according to claim 6, wherein the start of the period of the DRX mode is determined based on at least one of the following: System frame number, Subframe number, The duration of the DRX mode period, or DRX start offset.

8. The terminal device according to any one of claims 1 to 7, wherein the terminal device is further configured to: Based on detecting the start of the DRX cycle, a DRX cycle counter for the DRX cycle is incremented.

9. The terminal device according to claim 8, wherein the start of the DRX cycle is determined based on at least one of the following: System frame number, Subframe number, A DRX period counter for the DRX mode, The duration of the DRX mode period, A binary variable indicating whether the second parameter should be applied. The second parameter, The third parameter, Long DRX cycle, or Short DRX cycle.

10. The terminal device according to any one of claims 1 to 9, wherein: The DRX mode configuration of the DRX mode is configured for one of a long DRX cycle or a short DRX cycle of the terminal device; and Different DRX mode configurations of different DRX modes are configured for the other of the long DRX cycle or the short DRX cycle of the terminal device.

11. The terminal device according to any one of claims 1 to 10, wherein the terminal device is further caused to start a DRX OnDuration timer based on at least one of the following: System frame number, Subframe number, A DRX period counter for the DRX mode, The duration of the DRX mode period, A binary variable indicating whether the second parameter should be applied. The second parameter, The third parameter, Long DRX cycle, Short DRX cycle, or DRX start offset.

12. The terminal device according to claim 9 or 11, wherein the binary variable is determined based on at least one of the following: DRX cycle counter for the DRX cycle, the first parameter, or The third parameter.

13. The terminal device according to any one of claims 1 to 12, wherein the DRX mode configuration of the DRX mode is a first DRX mode configuration of a first DRX mode, and the terminal device is further caused to: An indication is received from the network device to apply a second DRX mode configuration of a second DRX mode instead of the first DRX mode configuration of the first DRX mode.

14. The terminal device according to claim 13, wherein the indication comprises at least one of the following: a bitmap, wherein the number of bits is determined based on at least one of the first parameter and the third parameter; or A Medium Access Control (MAC) Control Element (CE) has a header but no payload.

15. The terminal device of claim 13, wherein the indication is received via at least one of layer 1 signaling or layer 2 signaling.

16. The terminal device according to claim 15, wherein the terminal device is further configured to perform at least one of the following: Applying the second DRX mode configuration in a next time slot based on determining that the indication is received via the layer 1 signaling; or Based on determining that the indication is received via the layer 2 signaling, applying the second DRX mode configuration based on sending an acknowledgement (ACK) to the network device.

17. The terminal device according to any one of claims 1 to 16, wherein: The first parameter is indicated using a bitmap; The size of the bitmap indicates the duration of the period of the DRX mode; and The bits of the bitmap indicate whether the second parameter is applied to a DRX cycle in the plurality of DRX cycles.

18. The terminal device according to claim 13, wherein the terminal device is further configured to: Applying the second DRX mode configuration according to the second DRX mode configuration determined to directly apply the second DRX mode based on the indication; and Reset the DRX period counter for the second DRX mode.

19. The terminal device according to claim 13, wherein the terminal device is further configured to: determining, based on the second DRX mode configuration that the second DRX mode is not directly applied based on the indication, whether a first predefined condition related to a start of a period of the DRX mode is satisfied; and Based on determining that the first predefined condition is not satisfied, a DRX cycle counter for the DRX cycle is incremented.

20. The terminal device according to claim 19, wherein the terminal device is further configured to: determining whether a second predefined condition related to whether to apply the second parameter is satisfied based on determining that the first predefined condition is satisfied; Based on determining that the second predefined condition is not satisfied, incrementing the DRX cycle counter for the DRX cycle; as well as Based on determining that the second predefined condition is satisfied, resetting a DRX period counter for the second DRX mode.

21. The terminal device according to claim 18 or 20, wherein the terminal device is further configured to: After resetting the DRX period counter for the second DRX mode, a DRX cycle is monitored based on at least one of the second DRX mode configuration or the indication received from the network device.

22. The terminal device according to claim 21, wherein the terminal device is further configured to perform at least one of the following: Based on determining that the end of the period of the second DRX mode has been reached, incrementing the DRX period counter for the second DRX mode; or Based on determining that the end of the time period has not been reached, resetting the DRX cycle counter.

23. The terminal device according to any one of claims 13 to 22, wherein the terminal device is further configured to: Determining an evaluation result of the second DRX mode configuration for applying the second DRX mode; and The evaluation result is sent to the network device.

24. The terminal device according to claim 23, wherein the evaluation result is based on at least one of the following: Successful or unsuccessful reception of a frame; Quality of Service (QoS) requirements; Power saving gain; cell throughput; or Capacity loss.

25. The terminal device according to any one of claims 1 to 24, wherein the DRX mode configuration of the DRX mode is received via at least one of: Extension of DRX configuration message; a separate configuration message different from the DRX configuration message; or A configuration message for the DRX mode definition.

26. The terminal device according to claim 25, wherein at least one of the first parameter, the second parameter and the third parameter is included in a DRX configuration information element (IE).

27. A network device comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the network device to at least: receiving, from a terminal device, a request for a discontinuous reception (DRX) mode configuration including a plurality of DRX cycles; and The DRX mode configuration including a first parameter and a second parameter is sent to the terminal device, wherein the first parameter indicates the number of the multiple DRX cycles, and the second parameter indicates the amount of time added to at least one DRX cycle in the multiple DRX cycles or the amount of time subtracted from the at least one DRX cycle.

28. The network device of claim 27, wherein the DRX mode configuration further comprises a third parameter indicating the at least one DRX cycle to which the amount of time is applied.

29. The network device according to claim 27, wherein: In case the DRX mode configuration does not include a third parameter indicating the at least one DRX cycle to which the time amount is applied, the time amount is applied to a first DRX cycle of the plurality of DRX cycles.

30. The network device of claim 27, wherein the amount of time is predefined to be applied to at least one DRX cycle of the plurality of DRX cycles.

31. The network device according to any one of claims 27 to 30, wherein the network device is further configured to determine a period duration of the DRX mode based on at least one of: DRX cycle, the first parameter, or the second parameter.

32. The network device according to any one of claims 27 to 31, wherein the network device is further configured to: Based on detecting the start of a period of the DRX mode, a DRX period counter for the DRX mode is incremented.

33. The network device of claim 32, wherein the start of the period of the DRX mode is determined based on at least one of: System frame number, Subframe number, The duration of the DRX mode period, or DRX start offset.

34. The network device according to any one of claims 27 to 33, wherein the network device is further configured to: Based on detecting the start of the DRX cycle, a DRX cycle counter for the DRX cycle is incremented.

35. The network device of claim 34, wherein the start of the DRX cycle is determined based on at least one of: System frame number, Subframe number, A DRX period counter for the DRX mode, The duration of the DRX mode period, A binary variable indicating whether the second parameter should be applied. The second parameter, The third parameter, Long DRX cycle, or Short DRX cycle.

36. The network device according to any one of claims 27 to 35, wherein: The DRX mode configuration of the DRX mode is configured for one of a long DRX cycle or a short DRX cycle of the terminal device; and Different DRX mode configurations of different DRX modes are configured for the other of the long DRX cycle or the short DRX cycle of the terminal device.

37. The network device according to any one of claims 27 to 36, wherein the network device is further caused to start a DRX OnDuration timer based on at least one of: System frame number, Subframe number, A DRX period counter for the DRX mode, The duration of the DRX mode period, A binary variable indicating whether the second parameter should be applied. The second parameter, The third parameter, Long DRX cycle, Short DRX cycle, or DRX start offset.

38. The network device according to claim 35 or 37, wherein the binary variable is determined based on at least one of: DRX cycle counter for the DRX cycle, the first parameter, or The third parameter.

39. The network device according to any one of claims 27 to 38, wherein the DRX mode configuration of the DRX mode is a first DRX mode configuration of a first DRX mode, and the network device is further caused to: An indication is sent to the terminal device to apply a second DRX mode configuration of a second DRX mode instead of the first DRX mode configuration of the first DRX mode.

40. The network device of claim 39, wherein the indication comprises at least one of the following: a bitmap, wherein the number of bits is determined based on at least one of the first parameter and the third parameter; or A Medium Access Control (MAC) Control Element (CE) has a header but no payload.

41. The network device of claim 39, wherein the indication is transmitted via at least one of layer 1 signaling or layer 2 signaling.

42. The network device according to any one of claims 27 to 41, wherein: The first parameter is indicated using a bitmap; The size of the bitmap indicates the duration of the period of the DRX mode; and The bits of the bitmap indicate whether the second parameter is applied to a DRX cycle in the plurality of DRX cycles.

43. The network device according to any one of claims 39 to 42, wherein the network device is further configured to: receiving, from the terminal device, an evaluation result of the second DRX mode configuration for applying the second DRX mode; and Based on the evaluation result, an indication is sent to the terminal device to apply a third DRX mode configuration of a third DRX mode instead of the second DRX mode configuration of the second DRX mode.

44. The network device of claim 43, wherein the network device is further caused to: storing the evaluation results; and The evaluation results are post-processed.

45. The network device according to claim 43 or 44, wherein the evaluation result is based on at least one of the following: Successful or unsuccessful reception of a frame; Quality of Service (QoS) requirements; Power saving gain; loss of capacity; or Cell throughput.

46. ​​The network device according to any one of claims 27 to 45, wherein the DRX mode configuration of the DRX mode is sent via at least one of: Extension of DRX configuration message; a separate configuration message different from the DRX configuration message; or A configuration message for the DRX mode definition.

47. The network device of claim 46, wherein at least one of the first parameter, the second parameter, and the third parameter is included in a DRX configuration information element (IE).

48. A method comprising: sending, at the terminal device, to the network device, a request for a discontinuous reception (DRX) mode configuration including a plurality of DRX cycles; as well as The DRX mode configuration including a first parameter and a second parameter is received from the network device at the terminal device, wherein the first parameter indicates the number of the multiple DRX cycles and the second parameter indicates an amount of time added to at least one DRX cycle of the multiple DRX cycles or an amount of time subtracted from the at least one DRX cycle.

49. A method comprising: receiving, at a network device, from a terminal device, a request for a discontinuous reception (DRX) mode configuration for a DRX mode including a plurality of DRX cycles; as well as The DRX mode configuration including a first parameter and a second parameter is sent to the terminal device at the network device, wherein the first parameter indicates the number of the multiple DRX cycles and the second parameter indicates the amount of time added to at least one DRX cycle of the multiple DRX cycles or the amount of time subtracted from the at least one DRX cycle.

50. A non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least perform the method according to claim 48 or 49.

Images