Method for enhanced discontinuous reception configuration in mobile communications

Abstract

Various solutions for enhanced discontinuous reception （DRX） configuration / operation for extended reality （XR） and cloud gaming traffic with respect to user equipment and network apparatus in mobile communications are proposed. An apparatus may receive a configuration from a network node. The apparatus may activate an on-duration timer for an on-duration of a DRX cycle. The apparatus may determine whether downlink （DL） data are received from the network node. The apparatus may stop the on-duration timer according to the configuration in an event that the DL data are received.

Description

[Technical Field]

[0001] This invention relates generally to mobile communications, and more specifically, to enhanced discontinuous reception (DRX) configuration / operation for extended reality (XR) and cloud gaming services in relation to user equipment and network devices in mobile communications. [Previous Technology]

[0002] Unless otherwise stated, the methods described in this section are not prior art to the claims listed below, and are not considered prior art by virtue of their inclusion in this section.

[0003] In the current New Radio (NR) framework, 3GPP Release 15 (Rel-15) and Release 16 (Rel-16) specify connected mode discontinuous reception (cDRX) operation. This operation allows UE power to be saved by disabling the UE transmit (Tx) / receive (Rx) chain when there is no data to be received from the base station or transmitted by the UE. The UE can be configured to include DRX cycles with periodic on and off durations. The UE can wake up during the on duration to receive / transmit data and enter sleep mode during the off duration to save power. One of the limitations / challenges of the Rel-15 / Rel-16 cDRX design when applied to XR / cloud gaming services is the inconsistency between the existing cDRX cycle and the augmented reality (AR) / virtual reality (VR) cycle. The release of data for AR / VR services may not match the duration of the DRX cycle.

[0004] Furthermore, AR / VR service modeling introduces jitter, meaning that services are not entirely periodic but arrive randomly within specific jitter intervals (e.g., [-4, +4] milliseconds (ms) for downlink (DL) AR / VR). Some data may arrive early, and some may arrive late. A straightforward but costly solution is to force the UE to wake up more frequently, but this would compromise power gain. The UE may waste power due to uncertainty. Power performance and user experience would deteriorate.

[0005] Therefore, how to improve DRX operation to accommodate audio / video streams for XR and / or cloud gaming services has become an important issue for UE power saving in newly developed wireless communication networks. Therefore, it is necessary to provide appropriate solutions for performing DRX operation for XR and / or cloud gaming applications. [Summary of the Invention]

[0006] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, key points, benefits, and advantageous effects of the novel and non-obvious techniques described herein. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0007] The purpose of this invention is to provide a solution or method to address the aforementioned enhanced DRX configuration / operation problems related to user equipment and network devices in mobile communications for XR and cloud gaming services.

[0008] In one aspect, a method may include a device receiving configuration from a network node. The method may further include the device starting an enable duration timer for an enable duration of a DRX cycle. The method may further include the device determining whether DL data has been received from the network node. The method may further include the device stopping the enable duration timer according to the configuration if DL data has been received.

[0009] In one aspect, a method may include an apparatus receiving from a network node at least one DRX configuration configuring an enabled duration bundle pattern. The method may further include the apparatus enabling the enabled duration bundle pattern based on an instruction from the network node. The method may further include the apparatus monitoring the physical downlink control channel (PDCCH) transmitted from the network node based on the enabled duration bundle pattern.

[0010] In one aspect, a method may include means receiving a plurality of DRX configurations. The method may further include means receiving an indication indicating at least one of the plurality of DRX configurations. The method may further include means activating at least one of the DRX configurations according to the indication. The method may further include means monitoring a physical downlink control channel (PDCCH) transmitted from a network node according to at least one activated DRX configuration.

[0011] In one aspect, a method may include a device measuring at least one of latency and jitter in data packets. The method may further include the device reporting the measurement results of at least one of latency and jitter to a network node.

[0013] It is worth noting that while the description provided herein includes content related to specific radio access technologies, networks, and network topologies, such as, but not limited to, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR), XR, cloud gaming, Internet of Things (IoT), narrowband IoT (NB-IoT), and Industrial Internet of Things (IIoT), as well as 6G (sixth generation), the proposed concepts, solutions, and any variations / derivatives thereof can be implemented in, used in, or through any other type of radio access technology, network, and network topology. Therefore, the scope of the invention is not limited to the examples described herein.

Implementation Method

[0015] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be implemented in various forms. Moreover, the invention can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of the invention comprehensive and complete, and to fully convey the scope of the invention to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview

[0016] Embodiments of the present invention relate to various techniques, methods, solutions, and / or methods for enhanced DRX configuration / operation for XR and cloud gaming services in relation to user equipment and network devices in mobile communications. According to the present invention, a plurality of possible solutions may be implemented individually or in combination. That is, although such solutions are described separately below, two or more of such possible solutions may be implemented in one combination or another combination.

[0017] Figure 1 illustrates an example scenario 100 under an embodiment of the present invention. Scenario 100 includes at least a UE and a network node, wherein the network node can be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network). The UE is configured with a DRX configuration by the network node. The DRX configuration can include a DRX period and an on / off duration. The DRX period includes an on / off duration / start-up time and a shutdown duration. The UE can be further configured to receive XR / cloud gaming services quasi-periodicly. Quasi-periodic means that the service is not precisely periodic. The service may sometimes arrive earlier and sometimes later. This depends on the scenario of the XR / cloud gaming application. There is no clear / specific / fixed boundary for the service arrival time.

[0018] One problem when applying DRX operations to XR services is the mismatch between the DRX period and the quasi-periodic XR service. As shown in Figure 1, the traditional DRX period value does not match the quasi-period of the XR service. The quasi-period of the XR service can be longer or shorter than the DRX period. Over time, the difference will gradually increase, and the duration of the DRX period may completely exceed (i.e., out of sync) the burst arrival period. The burst may arrive during the DRX period's shutdown. The UE may partially or completely miss the burst.

[0019] Figure 2 illustrates an example scenario 200 under an embodiment of the present invention. Scenario 200 includes at least a UE and a network node, wherein the network node can be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network). The UE is configured with DRX by the network node. Another problem when applying DRX operation to XR services is that jitter can occupy a large time interval (e.g., [-4, +4] ms for XR services). Jitter is the time interval that may be reached. Since the data packets of video / audio streams are large, the transmitter (e.g., an XR server / network node) needs to perform data compression to reduce the data packet size. This data compression may result in different data packet delay times. Therefore, the jitter time period can be long and uncertain.

[0020] Therefore, even if the DRX cycle mismatch issue is resolved, using the on-time duration to cover the entire jitter cycle will still significantly impact UE power consumption. The UE needs a longer wake-up time to cover the entire jitter cycle, which leads to significant UE power consumption. On the other hand, if the on-time duration is shorter than the jitter, some DL data may be delayed until the next on-time duration. Data reception performance will become worse. Therefore, some DRX operation enhancement schemes are needed for XR / cloud gaming services.

[0021] In view of the above, the present invention proposes several solutions for enhanced DRX configuration / operation related to user equipment and network devices in mobile communications for XR and cloud gaming services. According to the solutions of the present invention, some enhancements to DRX operation can be introduced to solve the above-mentioned problems. For example, the duration timer for DRX operation can be stopped earlier. Furthermore, a bundle of start-up durations can be configured. On the other hand, multiple DRX configurations can be applied to the UE simultaneously. The UE can further provide some auxiliary information to the network node to help adjust DRX parameters. Therefore, DRX operation can adapt to the uncertainties of XR / cloud gaming services. Therefore, enhanced DRX operation can effectively control UE power consumption without affecting data reception / transmission performance. User experience and UE power performance can be improved.

[0022] The DRX start time can be determined according to the definition in 3GPP. For example, when configuring DRX, the start time for serving cells in a DRX group includes the following times: when the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; when the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running in any serving cell in the DRX group; when the ra-ContentionResolutionTimer or msgB-ResponseWindow is running; when a scheduling request is sent on the physical uplink control channel (PUCCH) and is pending; or when, after successfully receiving a random access response, no new transmission of the Cell-RadioNetworkTemporaryIdentifier (C-RNTI) indicating addressing to the Media Access Control (MAC) entity has been received, where the random access response is for a random access preamble not selected by the MAC entity in a contention-based random access preamble.

[0023] Figure 3 illustrates an example scenario 300 under an embodiment of the present invention. Scenario 300 includes at least a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 3 illustrates an example of an on-duration timer for early termination of DRX operation. The UE may receive configuration from the network node. The UE may start an on-duration timer for the on-duration of the DRX cycle. The on-duration timer defines the duration from the start of the DRX cycle. The UE may determine whether DL data has been received from the network node. The DL data may be carried on a physical downlink shared channel (PDSCH) and may include at least one of XR streams, cloud gaming streams, and video / audio streams. The UE may stop the on-duration timer according to the configuration if DL data is received.

[0024] This configuration may include an indication for controlling (e.g., enabling / disabling) the early stopping of the start duration timer. The UE may be configured to receive at least one of the following from a network node: radio resource control (RRC) configuration, downlink control information (DCI), and DL MAC media access control (MAC) control element (CE). The UE may obtain the configuration from at least one of the RRC configuration, DCI, and DL MAC CE. The UE may enable / disable the early stopping of the start duration timer according to the indication.

[0025] As shown in Figure 3, the UE can be configured with an on-duration DRX configuration. Typically, the UE needs to monitor DL ​​data (e.g., monitor the PDCCH) throughout the on-duration. However, if no DL data is scheduled during the on-duration, the UE may waste power monitoring the PDCCH. Therefore, using the enhanced DRX operation proposed in this invention, the UE can be configured to determine whether DL data has been received. The UE can stop the on-duration timer earlier when DL data is received. Then, the UE can start a non-start timer for monitoring. The non-start timer defines the duration after the PDCCH timing, where the PDCCH timing indicates a new UL or DL ​​transmission. The non-start timer is used to monitor the PDCCH for the next data packet in the same DL transmission cluster. If the next data packet is received, the UE can restart the non-start timer to continue monitoring for the presence of the next data packet. If no data packet is received and the non-start timer expires, the UE can be configured to stop the on-duration and switch to a off-duration for power saving. Therefore, the on-duration timer can be stopped before the on-duration ends. The UE does not need to monitor the PDCCH for the remainder of the enabled duration.

[0026] This can be useful in scenarios where the burst duration is very short (e.g., compared to the jitter / on duration). For example, in some XR / cloud gaming scenarios, data bursts may be concentrated. DL data may arrive within a short period of the on duration. If the UE can determine that the DL data was successfully received, the UE does not need to monitor the entire on duration. This can reduce the UE's power consumption.

[0027] Figure 4 illustrates an example scenario 400 under an embodiment of the present invention. Scenario 400 includes at least a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Figure 4 illustrates an example of enhanced DRX configuration / operation using a bundle of on-duration timings. The UE can receive at least one DRX configuration configuring an on-duration timing bundle mode from the network node. The UE can enable the on-duration timing bundle mode based on an instruction from the network node. The UE can monitor the PDCCH based on the continuous on-duration timing bundle mode. The on-duration timing bundle mode may include a plurality of on-duration timings.

[0028] The UE can be configured to receive at least one of RRC configuration, DCI, and DL MAC CE from the network node. The UE can obtain an on-duration binding mode from at least one of RRC configuration, DCI, and DL MAC CE. The UE can further dynamically enable / disable on-duration timing based on indications from the network node (e.g., bit fields).

[0029] As shown in Figure 4, groups or bundles of on-time durations or time periods can be defined. A bundle of on-time durations can include multiple on-time durations. The duration bundling pattern can include a regular distribution of on-time durations with the same length or an irregular distribution of on-time durations with different lengths. On-time duration bundles can be configured using a period aligned with the quasi-period of the XR / cloud gaming service. The length of the on-time duration bundle can also be consistent with the jitter of the XR / cloud gaming service.

[0030] Utilizing the on-duration bundle mode, if the UE receives DL data during at least one on-duration period, the UE can stop monitoring other on-duration periods within the same bundle. For example, the UE determines that the DL data was received during the first on-duration period. Then, the UE can stop monitoring the second and third on-duration periods within the same bundle.

[0031] The duration bundling mode can be further updated by the network node. For example, the number / position of start moments within the bundle can be updated. Each start duration moment can be dynamically enabled / disabled via bit fields. Updates can be signaled by the network node. The UE can be configured to receive DCI or DL ​​MAC CE from the network node. The UE can update the start duration bundling mode based on the DCI or DL ​​MAC CE.

[0032] On the other hand, the activation duration bundle mode can be updated based on the position of the activation duration timing using the DL data within the current activation duration bundle. For example, the subsequent activation duration bundle mode can be updated based on the timing when DL data is present in the current bundle. The network node and / or UE can update the activation duration bundle mode according to the position of the activation duration timing with DL data.

[0033] In some implementations, the on-duration bundle can be implemented alternatively through multiple DRX configurations. The on-duration bundle mode can be configured / assembled using multiple DRX configurations. The UE can receive multiple DRX configurations. The UE can determine the on-duration bundle mode based on the multiple DRX configurations. Data received during the on-duration / start-up time of a DRX configuration in the DRX configuration set may affect the UE's use of other DRX configurations within the set. For example, if the UE receives DL data during the on-duration / start-up time of a DRX configuration, the UE may skip monitoring the PDCCH for a period of time using other DRX configurations. This can be achieved by stopping / canceling other DRX timers used for other DRX configurations (e.g., on-duration timers, non-start timers, etc.).

[0034] Another DRX operation enhancement scheme is to use multiple DRX configurations for the UE. Figure 5 illustrates an example scenario 500 under an embodiment of the present invention. Scenario 500 includes at least a UE and a network node, wherein the network node may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). The UE may be configured with multiple DRX configurations by the network node. Each DRX configuration may include a DRX period, a period, and timer parameters. The timer parameters may include at least one of the following: enabled duration timer, not enabled timer, hybrid automatic repeat request (HARQ) round trip time (RTT) timer, and retransmission timer.

[0035] A network node (e.g., an XR server or base station) can configure a plurality of DRX configurations for the UE. Specifically, the UE can receive a plurality of DRX configurations. The UE can receive an indication indicating at least one of the plurality of DRX configurations. The UE can activate at least one of the DRX configurations according to the indication. The UE can receive a DCI or DL ​​MAC CE and obtain an indication from the DCI or DL ​​MAC CE. Then, the UE can monitor the PDCCH sent from the network node according to at least one of the activated DRX configurations. The PDCCH can indicate DL data of a stream. The stream may include at least one of an XR stream, a cloud gaming stream, and a video / audio stream.

[0036] Specifically, network nodes can dynamically signal to the UE which DRX configuration to use by considering factors such as latency, jitter, packet error rate (PER), channel conditions, and UE power consumption. New DCI fields, DCI formats, or MAC CEs can be introduced to signal the DRX configuration to be used. The DRX configuration can be associated with at least one of the following: a permitted configuration, a semi-persistent scheduling (SPS) configuration, a set of permitted configurations, and a set of SPS configurations. The DRX configuration can also be associated with at least one of UL services (e.g., gesture / control information) and DL services (e.g., video data).

[0037] In some implementations, two or more simultaneous DRX configurations can be initiated for a plurality of service priorities. At least one of the initiated DRX configurations can correspond to a service priority. For example, one DRX configuration can be used for I-frames, and another DRX configuration can be used for P-frames. Different service types (e.g., I-frames and P-frames) can be applied through different DRX configurations with different periods, different on-time durations, and no timer activation, etc. In another example, one DRX configuration can be used for audio, and another DRX configuration can be used for video. Depending on the location of the XR / cloud gaming server, different DRX settings may be determined. For example, because data packets are not segmented and jitter is less, edge servers require shorter on-time durations.

[0038] On the other hand, the UE can assess its power consumption and report the preferred DRX configuration for each DRX configuration, each subset of DRX configurations, or each data stream (e.g., video, audio, etc.). The UE can be configured to report the preferred DRX configuration / setting to the network node. The DRX configuration can be adjusted based on UE feedback information (e.g., game commands, gesture information, etc.). For example, the UE can automatically switch to a different / another DRX configuration / setting after a specific UL transmission. The UE can switch to another DRX configuration after sending an I-frame request. Alternatively, the network node can configure another DRX configuration for the UE after receiving an I-frame request. In some implementations, the UE can signal the network node to switch (e.g., via UL control information, MAC CE, etc.). The UE can be configured to send signals to the network node to switch DRX configurations.

[0039] In some implementations, the DRX start offset for the on-duration period can be enabled / disabled or configured based on the DRX configuration. For example, the DRX start offset can be configured for a DRX configuration associated with DL services (e.g., with jitter) but not for a DRX configuration associated with UL services (e.g., without jitter). The UE can dynamically adjust the start time of the on-duration period of the DRX cycle based on the DRX start offset.

[0040] Another DRX operation enhancement scheme is to provide UE-assisted information to the network to help dynamically adjust DRX parameters. Specifically, the UE can measure at least one of latency and jitter in data packets. The stream can include at least one of XR streams, cloud gaming streams, and video / audio streams. The UE can report the measurement results of at least one of latency and jitter to the network node. For example, for UL services, the UE can indicate the arrival time pattern of the UL service (e.g., regarding the on-time duration). To perform the measurement, the UE can receive a reference packet from the network node. The UE can measure at least one of latency and jitter based on the reference packet. In some implementations, other UE-assisted information can be provided to the network node. The network node can dynamically adjust / update DRX parameters / configurations based on the UE-assisted information. Illustrative Implementation

[0041] Figure 6 illustrates an example communication system 600 having at least an example communication device 610 and an example network device 620 according to an embodiment of the present invention. Each of the communication device 610 and the network device 620 can perform various functions to implement solutions, techniques, processes, and methods relating to enhanced DRX configuration / operation for XR and cloud gaming services in relation to user equipment and network devices in wireless communication, including the above-described scenarios / solutions and processes 700, 800, 900, and 1000 described below.

[0042] The communication device 610 may be part of an electronic device, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 610 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. The communication device 610 may also be part of a machine-type device, such as an IoT, NB-IoT, or IIoT device, such as a fixed or static device, a home device, a wired communication device, or a computing device. For example, the communication device 610 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center.

[0043] Alternatively, the communication device 610 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. The communication device 610 includes at least a portion of the components shown in Figure 6, such as processor 612. The communication device 610 further includes one or more other components (e.g., internal power supply, display device, and / or user peripheral devices) unrelated to the solution proposed in this invention, but for simplicity and brevity, these other components in the communication device 610 are not described in Figure 6, nor are they described below.

[0044] Network device 620 may be part of an electronic device, such as a base station, cell, router, or gateway, etc. For example, network device 620 may be implemented in an eNodeB of an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB of a 5G, NR, IoT, NB-IoT, or IIoT network. Network device 620 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. Network device 620 includes at least some of the components shown in Figure 6, such as processor 622. Network device 620 further includes one or more other components (e.g., internal power supply, display device, and / or user peripheral devices) unrelated to the solution proposed in this invention, but for simplicity and brevity, these other components in network device 620 are not described in Figure 6, nor are they described below.

[0045] In one aspect, each of processors 612 and 622 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though the singular term "processor" is used herein to refer to processors 612 and 622, according to the present invention, each of processors 612 and 622 may include a plurality of processors in some embodiments and a single processor in other embodiments. In another aspect, each of processors 612 and 622 may be implemented as hardware (and, optionally, firmware) having electronic components, which may include, but are not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more variable capacitors configured and arranged for a particular purpose according to the present invention. In other words, according to the various embodiments of the present invention, at least in some embodiments, each of processors 612 and 622 can be a dedicated machine specially designed, configured and arranged to perform specific tasks, including configuration / operation of enhanced DRX for XR and cloud gaming services in relation to user equipment and network devices in mobile communications, according to various embodiments of the present invention.

[0046] In some embodiments, the communication device 610 may further include a transceiver 616 coupled to the processor 612, and the transceiver 616 is capable of wirelessly transmitting and receiving data. In some embodiments, the communication device 610 may further include a memory 614 coupled to the processor 612 and accessible by the processor 612 and storing data therein. In some embodiments, the network device 620 may further include a transceiver 626 coupled to the processor 622 and capable of wirelessly transmitting and receiving data. In some embodiments, the network device 620 may further include a memory 624 coupled to the processor 622 and accessible by the processor 622 and storing data therein. Therefore, the communication device 610 and the network device 620 can wirelessly communicate with each other via transceiver 616 and transceiver 626, respectively. To aid in a better understanding, the following description of the operation, function, and capabilities of each of the communication device 610 and the network device 620 is provided in the context of a mobile communication environment, wherein the communication device 610 is implemented as a communication device or a UE, and the network device 620 is implemented in a network node of a communication network or as a network node of a communication network.

[0047] In various proposed schemes according to the present invention regarding enhanced DRX configuration / operation for XR and cloud gaming services, processor 612 can receive configuration from network node device 620 via transceiver 616. Processor 612 can start an on-duration timer for the on-duration of the DRX cycle. Then, processor 612 can determine whether DL data has been received from network device 620. If DL data is received, processor 612 can stop the on-duration timer according to the configuration.

[0048] In some embodiments, the processor 612 may receive at least one of RRC configuration, DCI and DL MAC CE and obtain configuration from at least one of RRC configuration, DCI and DL MAC CE.

[0049] In some embodiments, the processor 612 may start or not start a timer to monitor the PDCCH for the next data packet.

[0050] In some embodiments, the processor 612 can stop DL data monitoring without initiating a timer that expires. The timer can expire before the end of its duration.

[0051] In various proposed embodiments of the present invention concerning enhanced DRX configuration / operation for XR and cloud gaming services, processor 612 may receive, via transceiver 616, at least one DRX configuration for configuring an enabled duration-bundling mode from network device 620. Processor 612 may enable the enabled duration-bundling mode according to an instruction from network device 620. Then, processor 612 may monitor PDCCH via transceiver 616 according to the enabled duration-bundling mode.

[0052] In some implementations, the activation duration binding mode may include a plurality of activation duration timings.

[0053] In some embodiments, the processor 612 may receive DCI or DL ​​MAC CE from the network device 620 via transceiver 616, and update the start duration binding mode according to DCI or DL ​​MAC CE.

[0054] In some embodiments, the processor 612 may receive DL data at at least one open duration moment in the bundle via the transceiver 616 and stop monitoring other open duration moments in the bundle.

[0055] In some embodiments, the processor 612 may update the activation duration binding mode based on the location of the activation duration timing with DL data.

[0056] In some embodiments, the duration of the activation time can be the same or different.

[0057] In some implementations, enabling the duration binding mode can be configured by multiple DRX configurations.

[0058] In various proposed schemes according to the present invention regarding enhanced DRX configuration / operation for XR and cloud gaming services, processor 612 may receive a plurality of DRX configurations via transceiver 616. Processor 612 may receive, via transceiver 616, an instruction indicating at least one of the plurality of DRX configurations. Then, processor 612 may activate at least one of the plurality of DRX configurations according to the instruction. Processor 612 may monitor PDCCH transmitted from network device 620 via transceiver 616 according to at least one activated DRX configuration.

[0059] In some embodiments, the processor 612 may receive DCI or DL ​​MAC CE via transceiver 616 and obtain instructions from DCI or DL ​​MAC CE.

[0060] In some embodiments, the processor 612 may report a preferred DRX configuration to the network device 620 via the transceiver 616. The processor 612 may send signals to the network device 620 via the transceiver 616 to switch the DRX configuration.

[0061] In some embodiments, at least one of the plurality of DRX configurations is associated with at least one of the following: a configuration license configuration, an SPS configuration, a set of configuration license configurations, and a set of SPS configurations.

[0062] In some embodiments, at least one of the plurality of DRX configurations is associated with at least one of UL service and DL service.

[0063] In some embodiments, the processor 612 may automatically switch to another DRX configuration after a particular UL transmission.

[0064] In some implementations, at least one of the initiated DRX configurations may correspond to a service priority order.

[0065] In various proposed schemes of the present invention concerning enhanced DRX configuration / operation for XR and cloud gaming services, processor 612 may measure at least one of latency and jitter of data packets via transceiver 616. Then, processor 612 may report the measurement results of at least one of latency and jitter to network device 620 via transceiver 616.

[0066] In some embodiments, processor 612 may receive reference packets from network device 620 via transceiver 616. Processor 612 may measure at least one of latency and jitter based on the reference packets via transceiver 616. Illustrative Flow

[0067] Figure 7 illustrates an example flow 700 according to an embodiment of the present invention. Flow 700 may be an example implementation of the above-described solution, relating in part or in whole to an enhanced DRX configuration / operation for XR and cloud gaming services according to the present invention. Flow 700 may represent one aspect of an implementation of the functional features of communication device 610. Flow 700 may include one or more of the operations, actions, or functions shown in blocks 710, 720, 730, and 740. Although the shown blocks are discrete, depending on the desired implementation, the blocks in flow 700 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks of flow 700 may be executed in the order shown in Figure 7 or in a different order. Flow 700 may be implemented by communication device 610 or any UE or machine-type device. Flow 700 is described below within the content of communication device 610 for illustrative purposes only and is not intended to be limiting. Flow 700 may begin at block 710.

[0068] In block 710, process 700 may include the processor 612 of device 610 receiving configuration from a network node. Process 700 proceeds from block 710 to block 720.

[0069] In block 720, process 700 may include processor 612 starting an on-duration timer for the on-duration of the DRX cycle. Process 700 proceeds from block 720 to block 730.

[0070] In block 730, process 700 may include processor 612 determining whether DL data has been received from the network node. Process 700 proceeds from block 730 to block 740.

[0071] In block 740, process 700 may include processor 612 stopping the start of duration timer according to configuration upon receiving DL data.

[0072] In some embodiments, process 700 may include processor 612 receiving DC and obtaining configuration from DCI.

[0073] In some embodiments, process 700 may include processor 612 receiving DL MAC CE and obtaining DRX start offset from DL MAC CE.

[0074] In some embodiments, process 700 may include processor 612 receiving at least one of RRC configuration, DCI and DL MAC CE and obtaining configuration from at least one of RRC configuration, DCI and DL MAC CE.

[0075] In some embodiments, process 700 may include processor 612 starting or not starting a timer to monitor the PDCCH for the next data packet.

[0076] In some embodiments, process 700 may include processor 612 stopping DL data monitoring without initiating a timer that has expired. The timer may expire before the start duration ends.

[0077] Figure 8 is an example flow 800 described according to an embodiment of the present invention. Flow 800 may be an example implementation of the above-described solution, relating in part or in whole to an enhanced DRX configuration / operation for XR and cloud gaming services according to the present invention. Flow 800 may represent one aspect of an implementation of the functional features of communication device 610. Flow 800 may include one or more of the operations, actions, or functions shown in blocks 810, 820, and 830. Although the various blocks shown are discrete, depending on the desired implementation, the blocks in flow 800 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks of flow 800 may be executed in the order shown in Figure 8 or in a different order. Flow 800 may be implemented by communication device 610 or any UE or machine-type device. Flow 800 is described below within the content of communication device 610 for illustrative purposes only and is not intended to be limiting. Flow 800 may begin at block 810.

[0078] In 810, process 800 may include the processor 612 of the communication device 610 receiving at least one DRX configuration for configuring an enabled duration-based bundling mode from a network node. Process 800 proceeds from 810 to 820.

[0079] In 820, process 800 may include processor 612 enabling a duration-based binding mode based on instructions from the network node. Process 800 proceeds from 820 to 830.

[0080] In 830, process 800 may include processor 612 monitoring PDCCH according to the on-duration binding mode.

[0081] In some embodiments, process 800 may include processor 612 receiving DCI or DL ​​MAC CE from network node via transceiver 616, and updating the start duration binding mode according to DCI or DL ​​MAC CE.

[0082] In some embodiments, process 800 may include processor 612 receiving DL data at at least one on-duration timing within the bundle. Process 800 may also include processor 612 stopping monitoring other on-duration timings within the bundle.

[0083] In some embodiments, process 800 may include processor 612 updating the on-duration binding mode based on the location of the on-duration timing with DL data.

[0084] Figure 9 is an example flow 900 described according to an embodiment of the present invention. Flow 900 may be an example implementation of the above-described solution, relating in part or in whole to an enhanced DRX configuration / operation for XR and cloud gaming services according to the present invention. Flow 900 may represent one aspect of an implementation of the functional features of communication device 610. Flow 900 may include one or more of the operations, actions, or functions shown in blocks 910, 920, 930, and 940. Although the various blocks shown are discrete, depending on the desired implementation, the blocks in flow 900 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks of flow 900 may be executed in the order shown in Figure 9 or in a different order. Flow 900 may be implemented by communication device 610 or any UE or machine-type device. Flow 900 is described below within the content of communication device 610 for illustrative purposes only and is not intended to be limiting. Flow 900 may begin at block 910.

[0085] In 910, process 900 may include the processor 612 of the communication device 610 receiving a plurality of DRX configurations. Process 900 proceeds from 910 to 920.

[0086] In 920, process 900 may include processor 612 receiving an indication indicating at least one of a plurality of DRX configurations. Process 900 proceeds from 920 to 930.

[0087] In 930, process 900 may include processor 612 initiating at least one of a plurality of DRX configurations according to instructions. Process 900 proceeds from 930 to 940.

[0088] In 940, process 900 may include processor 612 monitoring at least one PDCCH sent from network nodes in accordance with the initiated DRX configuration.

[0089] In some embodiments, process 900 may include processor 612 receiving DCI or DL ​​MAC CE and obtaining instructions from DCI or DL ​​MAC CE.

[0090] In some embodiments, process 900 may include processor 612 reporting a preferred DRX configuration to network nodes.

[0091] In some embodiments, process 900 may include processor 612 sending a signal to a network node to switch DRX configuration.

[0092] In some embodiments, process 900 may include processor 612 automatically switching to another DRX configuration after a particular UL transmission.

[0093] Figure 10 illustrates an example flow 1000 according to an embodiment of the present invention. Flow 1000 may be an example implementation of the above-described solution, relating in part or in whole to an enhanced DRX configuration / operation for XR and cloud gaming services according to the present invention. Flow 1000 may represent one aspect of an implementation of the functional features of communication device 610. Flow 1000 may include one or more of the operations, actions, or functions shown in blocks 1010 and 1020. Although the shown blocks are discrete, depending on the desired implementation, the blocks in flow 1000 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks of flow 1000 may be executed in the order shown in Figure 10 or in a different order. Flow 1000 may be implemented by communication device 610 or any UE or machine-type device. Flow 1000 is described below within the context of communication device 610 and is not intended to be limiting. Process 1000 can begin at block 1010.

[0094] In 1010, process 1000 may include the processor 612 of the communication device 610 measuring at least one of the latency and jitter of the data packets. Process 1000 proceeds from 1010 to 1020.

[0095] In 1020, process 1000 may include processor 612 reporting to network nodes a measurement of at least one of latency and jitter.

[0096] In some embodiments, process 1000 may include processor 612 receiving a reference packet from a network node. Process 1000 may include processor 612 measuring at least one of latency and jitter based on the reference packet. Additional Notes

[0097] The topics described herein sometimes illustrate different components included within or connected to other components. However, it should be understood that the architectures depicted are merely examples, and many other architectures that implement the same functionality can actually be implemented. Conceptually, any arrangement of components that implement the same functionality is effectively "associated" to enable the desired functionality. Therefore, regardless of the architecture or intermediate components, any two components combined herein to implement a particular functionality can be considered "associated" with each other to enable the desired functionality. Similarly, any two components so associated can also be considered "operationally connected" or "operationally coupled" to each other to achieve the desired functionality, and any two components so associated can also be considered "operationally connected" to each other to achieve the desired functionality. Specific examples of operationally coupled components include, but are not limited to, physically mating and / or physically interacting components and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0098] Furthermore, regarding any plural and / or singular terms used herein, those skilled in the art may, where appropriate, convert from plural to singular and / or from singular to plural for the content and / or application. For clarity, various singular / plural interchanges may be explicitly stated herein.

[0099] Furthermore, those skilled in the art will understand that, generally, the terms used herein, and especially in the appended claims (e.g., the body of the appended claims), are generally meant as "open-ended" terms. For example, the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "at least having," the term "comprising" should be interpreted as "including but not limited to," and so on. Those skilled in the art will also understand that if the specific number listed in the appended claims is intentional, such intention will be explicitly listed in the claims, and such intention will not exist in the absence of such listing. For example, to aid understanding, the appended claims may include the use of the introductory phrases "at least one" and "one or more." However, the use of such phrases should not be construed as implying that the introduction of the indefinite article "a" or "one" limits any particular patent application that includes such an introduced patent application to only one implementation of such an introduction, even when the same patent application includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "one," for example, "a and / or one" should be interpreted as meaning "at least one" or "one or a plurality of," and this also applies to the use of definite articles used to introduce patent application listings. Furthermore, even when a specific number of introduced patent application listings is explicitly listed, those skilled in the art will recognize that such a listing should be interpreted as meaning at least the number listed; for example, in the absence of other modifiers, an unobscured listing of "two listings" means at least two listings or two or a plurality of listings. Furthermore, when using a convention similar to "at least one of A, B, and C," those skilled in the art will understand the meaning of this convention, which generally means such an interpretation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together). When using a convention similar to "at least one of A, B, or C," those skilled in the art will understand the meaning of this convention, which generally means such an interpretation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together).Those skilled in the art will also understand that any transitional words and / or phrases, whether in the specification, the claims, or the accompanying drawings, that actually represent two or more options should be understood to include the possibility of including one of those options, either one of those options, or both of those options. For example, the phrase "A or B" will be understood to include the possibility of including "A" or "B" or "A and B".

[0100] As can be seen from the above, it is understood that various embodiments of the present invention have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of the invention. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are determined by the appended claims. [Simplified Explanation of the Diagram]

[0014] The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this invention. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. It is understood that, in order to clearly illustrate the concepts of the invention, the drawings are not necessarily drawn to scale, and some components shown may be shown at a scale greater than that of the actual embodiments. Figure 1 shows a schematic diagram of an example scenario according to an embodiment of the invention. Figure 2 shows a schematic diagram of an example scenario according to an embodiment of the invention. Figure 3 shows a schematic diagram of an example scenario according to an embodiment of the invention. Figure 4 shows a schematic diagram of an example scenario according to an embodiment of the invention. Figure 5 shows a schematic diagram of an example scenario according to an embodiment of the invention. Figure 6 is a block diagram of an example communication system according to an embodiment of the invention. Figure 7 is a flowchart of an example process according to an embodiment of the invention. Figure 8 is a flowchart of an example process according to an embodiment of the invention. Figure 9 is a flowchart of an example process according to an embodiment of the invention. Figure 10 is a flowchart of an example process according to an embodiment of the invention.

Claims

1. A method comprising: A processor of a device receives a configuration from a network node; the processor starts an on-duration timer for an on-duration of a discontinuous reception period; the processor determines whether downlink data is received from the network node; if the downlink data is received, the processor stops the on-duration timer according to the configuration.

2. The method as described in request item 1, wherein, The processor further includes: receiving at least one of a radio resource control configuration, downlink control information, and a control element of downlink medium access control; and obtaining the configuration from at least one of the radio resource control configuration, the downlink control information, and the control element of downlink medium access control.

3. The method as described in request item 1, wherein, Further includes: The processor starts a non-start timer to monitor the physical downlink control channel for the next data packet.

4. The method as described in request item 3, wherein, Further includes: The processor stops downlink data monitoring if the non-start timer expires.

5. A method comprising: A processor of an apparatus receives at least one discontinuous reception configuration from a network node to configure an enabled duration bonding mode; the processor enables the enabled duration bonding mode based on an instruction from the network node; and the processor monitors a physical downlink control channel based on the enabled duration bonding mode.

6. The method as described in claim 5, wherein, This on-duration binding mode can include multiple on-duration timings.

7. The method as described in request item 5, wherein, Further including: the processor receiving downlink control information and downlink media access control control elements from the network node; and the processor updating the activation duration binding mode based on the downlink control information or the downlink media access control control elements.

8. The method as described in request item 5, wherein, Further includes: the processor receiving downlink data during at least one on-duration period in a bundle; and the processor ceasing to monitor other on-duration periods in the bundle.

9. The method as described in claim 8, wherein, Further includes: The processor updates the on-duration bundling mode based on a position of the on-duration timing with the downlink data.

10. The method as described in claim 5, wherein, The duration of the activation can be the same or different.

11. The method as described in claim 5, wherein, Enabling duration binding mode can be configured by multiple discontinuous receive configurations.

12. A method comprising: A processor in a device receives a plurality of discontinuous reception configurations; The processor receives an indication that indicates at least one of the plurality of discontinuous reception configurations; The processor initiates at least one of the plurality of discontinuous reception configurations according to the instruction; and the process monitors a physical downlink control channel transmitted from a network node according to at least one of the initiated discontinuous reception configurations.

13. The method as described in claim 12, wherein, Further including: the processor receiving downlink control information and downlink media access control control elements from the network node; and the processor obtaining the instruction from the downlink control information or the downlink media access control control elements.

14. The method as described in claim 12, wherein, Further including: the processor reporting a preferred discontinuous reception configuration to the network node; or the processor sending a signal to the network node to switch the discontinuous reception configuration.

15. The method as described in claim 12, wherein, At least one of the plurality of discontinuous reception configurations is associated with at least one of a permission configuration of a configuration, a semi-persistent scheduling configuration, a set of permission configurations, and a set of semi-persistent scheduling configurations.

16. The method as described in claim 12, wherein, At least one of the plurality of discontinuous reception configurations is associated with at least one of the uplink service and the downlink service.

17. The method as described in claim 12, wherein, Further includes: The processor automatically switches to another discontinuous receive configuration after a specific uplink transmission.

18. The method as described in claim 12, wherein, At least one of the discontinuous reception configurations initiated can correspond to a service priority order.

19. A method comprising: A processor of a device measures at least one of a delay and a jitter in a data packet; The processor also reports a measurement of at least one of the latency and the jitter to a network node.

20. The method as described in claim 19, wherein, Further includes: the processor receiving a reference packet from the network node; and the processor measuring at least one of the delay and the jitter based on the reference packet.

Images