Discrete outages for predictable traffic

Abstract

A system, method, apparatus, and computer program product for discontinuous outages for predictable traffic are disclosed. One method includes receiving, by a user equipment, a discontinuous outage configuration, and, at the end of an active time, if the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous outage configuration, starting a discontinuous outage timer indicated by the discontinuous outage configuration. The discontinuous outage timer is associated with a discontinuous reception group.

Description

[Technical Field]

[0001] Some exemplary embodiments relate generally to mobile or wireless telecommunications systems, such as Long Term Evolution (LTE), Fifth Generation (5G) Radio Access Technology (RAT), New Radio (NR) access technology, Sixth Generation (6G), and / or other communication systems. For example, certain exemplary embodiments relate to systems and / or methods for discontinuity rest for predictable traffic. [Background technology]

[0002] Examples of mobile or wireless communication systems include radio frequency (RF) 5G RAT, Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE Advanced (LTE-A), LTE-A Pro, NR access technology, and / or MultiFire Alliance. 5G radio system refers to the next generation (NG) of radio systems and network architectures. 5G systems are typically built on 5G NR, but 5G (or NG) networks may also be built on E-UTRA radio. NR is expected to support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-wide communications (mMTC). NR is expected to provide extreme broadband, ultra-robust low-latency connectivity, and large-scale networks to support the Internet of Things (IoT). Next-generation radio access network (NG-RAN) refers to the RAN of 5G and may provide NR, LTE, and LTE-A radio access. It should be noted that a 5G node (e.g., similar to a Node B in UTRAN or an Evolved Node B (eNB) in LTE) that provides radio access functionality to user equipment may be referred to as a Next Generation Node B (gNB) if built with NR radios, or as a Next Generation eNB (NG-eNB) if built with E-UTRA radios. Summary of the Invention

[0003] In some example embodiments, the method may include, by a user equipment, receiving a discontinuous stop configuration. The method may further include, by the user equipment, starting a discontinuous stop timer indicated by the discontinuous stop configuration at the end of an active time when the number of packets transmitted and the number of packets received before expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop configuration. The discontinuous stop timer is associated with a discontinuous reception group.

[0004] In certain exemplary embodiments, the apparatus may include means for receiving a discontinuous stop setting. The apparatus may further include means for starting a discontinuous stop timer indicated by the discontinuous stop setting at the end of the active time when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting. The discontinuous stop timer is associated with the discontinuous reception group.

[0005] In various exemplary embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed on hardware, may perform a method. The method may include receiving a discontinuous stop setting. The method may further include, at the end of an active time, if the number of packets transmitted and the number of packets received before expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting, starting a discontinuous stop timer indicated by the discontinuous stop setting. The discontinuous stop timer is associated with a discontinuous receiving group.

[0006] In some example embodiments, a computer program product may perform a method. The method may include receiving a discontinuous stop setting. The method may further include, at the end of an active time, when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting, starting a discontinuous stop timer indicated by the discontinuous stop setting. The discontinuous stop timer is associated with a discontinuous reception group.

[0007] In certain exemplary embodiments, the device may include at least one processor and at least one memory including computer program code. The at least one memory and computer program code may be configured by the at least one processor to cause the device to at least receive a discontinuous stop setting. The at least one memory and computer program code may be further configured by the at least one processor to cause the device to at least start a discontinuous stop timer indicated by the discontinuous stop setting at the end of the active time when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting. The discontinuous stop timer is associated with a discontinuous receiving group.

[0008] In various exemplary embodiments, the device may include circuitry configured to receive a discontinuous stop setting. The circuitry may be further configured to, at the end of an active time, start a discontinuous stop timer indicated by the discontinuous stop setting when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting. The discontinuous stop timer is associated with a discontinuous reception group.

[0009] According to some example embodiments, the method may include the network entity transmitting a discontinuous stop setting indicating a discontinuous stop timer that starts at the end of an active time associated with the discontinuous reception group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

[0010] In certain exemplary embodiments, the apparatus may comprise means for transmitting a discontinuous stop setting indicating a discontinuous stop timer that will start at the end of an active time associated with a discontinuous reception group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

[0011] In various exemplary embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method that may include transmitting a discontinuous stop setting indicating a discontinuous stop timer that starts at the end of an active time associated with a discontinuous receiving group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

[0012] In some exemplary embodiments, a computer program product may perform a method that may include transmitting a discontinuous stop setting indicating a discontinuous stop timer that starts at the end of an active time associated with a discontinuous receiving group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

[0013] According to an example embodiment, an apparatus may comprise at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code may be configured by the at least one processor to transmit at least a discontinuous stop setting indicating a discontinuous stop timer that starts at the end of an active time associated with a discontinuous receiving group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

[0014] In various exemplary embodiments, the device may include circuitry configured to transmit a discontinuous stop setting indicating a discontinuous stop timer that starts at the end of an active time associated with a discontinuous receiving group when the number of packets transmitted and the number of packets received before the expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting. [Brief explanation of the drawings]

[0015] For a proper understanding of the exemplary embodiments, please refer to the accompanying drawings. [Figure 1] Figure 1 shows an example of extended reality (XR) video traffic. [Figure 2] FIG. 2 is a diagram illustrating an example of matching a discontinuous reception (DRX) on period and a packet arrival jitter range. [Figure 3] FIG. 3 shows an example of discontinuous stop (DRST) applied when a packet arrives after an on-period. [Figure 4] FIG. 4 illustrates an example signaling diagram according to an exemplary embodiment. [Figure 5] FIG. 5 illustrates an example flow diagram of a method according to various exemplary embodiments. [Figure 6] FIG. 6 illustrates another example flow diagram of a method according to various exemplary embodiments. [Figure 7]FIG. 7 is a diagram illustrating an example of parameters of the discontinuous stop timer. [Figure 8] FIG. 8 shows a probability distribution of frame arrivals and a possible example configuration for connected mode DRX (CDRX) using DRST. [Figure 9] 9a-b show the power saving gains of four schemes according to some example embodiments. [Figure 10] FIG. 10 illustrates an example of various network devices in accordance with some exemplary embodiments. [Figure 11] FIG. 11 illustrates an example of a 5G network and system architecture in accordance with certain exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0016] It will be readily understood that the components of the particular exemplary embodiment, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of several exemplary embodiments of systems, methods, apparatuses, and computer program products for discontinuity rest for predictable traffic is not intended to limit the scope of the particular exemplary embodiments, but is instead representative of selected exemplary embodiments.

[0017] As used herein, "at least one of the following <list of two or more elements>" and similar expressions such as "at least one of a <list of two or more elements>" mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements when a list of two or more elements is joined by "and" or "or."

[0018] XR downlink traffic may primarily contain video frames, as shown in Figure 1. Specifically, the arrival process of XR traffic at a base station is characterized as a quasi-periodic process with a period related to the video frame rate and jitter that can be modeled as a truncated Gaussian distribution. For example, for a 60 frames per second (fps) video, the mean inter-arrival time is 1 / 60 fps = 16.67 ms, with jitter having a mean of 0 ms and a standard deviation of 2 ms. The range of the truncated distribution is ±4 ms. Thus, as shown in Figure 1, packets are expected to arrive within an 8 ms window, followed by an 8 ms window of silence.

[0019] DRX and physical downlink control channel (PDCCH) monitoring techniques have been studied for XR and general UE power saving. For example, several techniques for adaptive DRX or dynamic DRX control have been discussed, where the DRX period parameters are dynamically adapted via Layer 1 (L1) and Layer 2 (L2) signaling. UE power saving techniques include using DRX wake-up signals (e.g., Dynamic Clustering Protocol (DCP), Power Save-Radio Network Temporary Identifier (PS-RNTI)-based Cyclic Redundancy Check (CRC)-scrambled Downlink Control Information (DCI), Search Space Set Group (SSSG) switching-based PDCCH monitoring adaptation schemes, and PDCCH monitoring skip indication via DCI).

[0020] However, none of the existing UE power saving techniques are relevant to XR traffic, and many enhancements to XR only consider the possibility of shortening the active period of the DRX cycle when a frame is correctly received. This requires a relatively long on-period that is shortened depending on L1 / L2 signaling and / or conditions. However, a long on-period can waste UE energy because a frame is often delivered completely before the expiration of the jitter range defined by the on-period. Continuous signaling from the network to the UE to shorten the on-period can result in high signaling overhead, as the network must signal when a frame has been completely transmitted.

[0021] A truncated Gaussian distribution may allow for the recognition that packet arrivals occur within the truncated range with a period that depends on the frame arrival rate. Furthermore, XR may have a packet delay budget requirement of 10 ms or 15 ms. Due to packet arrival jitter, the DRX on-period may not be limited without violating the packet delay budget. However, a long on-period may increase the UE's energy consumption because the UE must monitor the PDCCH during the on-period. Figure 2 shows how the on-period can be aligned to the packet arrival jitter so that the network can schedule packets to the UE within the packet delay budget.

[0022] To improve the UE power-saving benefits of DRX for predictable traffic such as XR, a discontinuous stop (DRST) scheme allows the UE to extend the on-period timer if no traffic is received when the on-period timer expires. Certain exemplary embodiments of DRST in this example may have various advantages and / or merits for overcoming the above-mentioned drawbacks. For example, certain exemplary embodiments allow the UE to be configured with a short on-period whenever a video frame arrives within the on-period, thereby saving energy. Furthermore, because the UE automatically extends PDCCH monitoring until it receives a video frame, the base station may not need to predict when the transmission of the video frame is complete. Furthermore, the UE can automatically correct for time drift between DRX and frame arrival times due to the non-integer period of XR traffic. Time drift may eventually cause the on-period to deviate from the expected frame arrival interval, and extending the on-period can avoid frame loss. Therefore, the exemplary embodiments described below are directed to improvements in computer-related technology.

[0023] Some exemplary embodiments in this example may relate to DRST parameters that are applied when packets arrive after an on-period, as shown in FIG. 3. Specifically, the UE and base station may agree to transmit XR traffic according to certain characteristics. One important characteristic is the number of video frames expected to arrive per DRX active time instance, e.g., one video frame per configured DRX cycle. While certain exemplary embodiments in this example are described in terms of XR-type traffic, various exemplary embodiments are generally applicable to traffic with predictable arrival patterns where the UE and NE can agree on the number of packets expected within a time duration.

[0024] 4 shows an example of a signaling diagram depicting discontinuous outages for predictable traffic. UE 430 and NE 440 may be similar to UE 1020 and NE 1010, as shown in FIG. 10, according to certain exemplary embodiments. In various exemplary embodiments, UE 430 can automatically extend PDCCH monitoring based on DRST configuration.

[0025] In 401, the UE 430 and the NE 440 can agree on XR traffic parameters. For example, this can be performed using RRC signaling during an RRC connection setup or RRC reconfiguration procedure. Alternatively, it can be performed by extending the PDU session establishment procedure, where the XR traffic parameters are exchanged between the UE and the AMF during PDU session establishment. Once the PDU session is established, the AMF signals the traffic parameters to the RAN.

[0026] At 402, the NE 440 can transmit to the UE 430 an RRC information element indicating that DRST is active, and / or time-related parameters, and / or a threshold indicating the expected number of packets transmitted and received during a DRX cycle. For example, the time-related parameters may indicate an on-period (e.g., covering ¼ or ½ of the jitter range) and a DRST extension timer value. According to a specific timer value (inactivity timer) and an instruction from the NE 440, the DRST extension timer value can run until a video frame is received (i.e., one slot at a time) or until the next on-period. In an exemplary embodiment, the inactivity timer may not be set or may be limited to a short value when DRST is set.

[0027] As mentioned above, DRST can be implemented as a timer that is triggered when no packets have been received yet, or when the number of received packets is less than the number of packets expected to be transmitted and / or received during a DRX cycle and the drx-OnDuration timer expires. As an example, a MAC may be modified to include DRST to define parameters such as the duration of a "discontinuous stop" timer, its activation / deactivation conditions (e.g., when the number of received packets is less than the expected number of packets transmitted and / or received during a DRX cycle), and interaction with other DRX procedures, similar to the parameters shown in FIG. 7. DRST parameters may be associated with a DRX group; for example, a DRX group may have a single set of DRST parameters or all DRST parameters, with DRST parameters specific to each DRX group. Furthermore, two DRX groups may be associated with two dedicated DRX configurations (i.e., each group has its own DRX parameters, such as on-duration and inactivity timer). DRST parameters may include enable / disable, extension timer, expected number of packets, etc.

[0028] At 403, the UE 430 may apply the received DRX configuration.

[0029] At 404, the UE 430 and the NE 440 may enter a first DRX cycle.

[0030] At 405, the UE 430 may start DRX according to the on-duration parameter. The UE 430 may monitor the PDCCH according to the on-duration.

[0031] At 406, the NE 440 may send a scheduled DL packet to the UE 430 and notify the UE 430 that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in the packet header, may be used to indicate that a packet is the last of a burst.

[0032] In some exemplary embodiments, L1 / L2 signaling (either DCI or MAC CE commands) may be used by the NE 440 to enable and / or disable DRST operation. This may allow the NE 440 to detect the boundaries of a delay-limited burst of packets (e.g., packets belonging to the same video frame). If the packet is the last one of the burst, the NE 440 may inform the UE 430 that no more packets are expected, and the UE 430 may disable the DRST timer. The NE 440 may signal scheduling information on the PDDCH if this is the last packet of a burst (i.e., whether no further transmissions are expected until the next DRX cycle). This information can be used by the UE 430 to increment a counter for the number of received packets, which, together with drx-DiscontinousRestNrRxPdus, the number of transmitted packets, and drx-DiscontinousRestNrTxPdus, can be used to determine whether to start the drx-DiscontinousRestTimer after the drx-onDurationTimer expires.

[0033] In various exemplary embodiments, the NE 440 can use a DCI to trigger a DRST without using scheduling information. For example, the NE 440 may not schedule the UE 430 during the On Period, but if the NE 440 can estimate that data will arrive shortly thereafter, the NE 440 can send a DCI that triggers a DRST (or an inactivity timer, if configured) to ensure that the UE 430 monitors the PDCCH after the On Period expires. Additionally or alternatively, a group common physical downlink control channel (GC-PDCCH) can be used to address multiple UEs for such an extension.

[0034] At 407, the NE 440 may send the forwarded DL packet to the UE 330.

[0035] The UE 430 may enter sleep mode at 408. For example, if a video frame is received within an on period, or if all expected packets are successfully received within an on period, the UE 430 may enter sleep sooner than if there was no on period because the on period is relatively short.

[0036] At 409, the UE 430 and the NE 440 may enter a second DRX cycle.

[0037] At 410, the UE 430 may start DRX according to the on-period parameter. For example, if the UE 430 does not receive a video frame within the on-period, or if the number of packets received within the on-period is less than the number of packets transmitted and received during the DRX cycle, the UE 430 may automatically extend the DRX active time, specifically the DRST, according to a configured extension timer. Furthermore, the NE 440 may monitor how often DRST is needed and adjust the on-period together with the UE 430.

[0038] At 411, the UE 430 may terminate DRX according to the on-duration parameter.

[0039] At 412, the UE 430 may start a "discontinuous stop" timer.

[0040] At 413, the NE 440 may send a Scheduled DL packet to the UE 430 and notify the UE 430 that the Scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit in the packet header, may be used to indicate that a packet is the last of a burst.

[0041] At 414, the NE 440 may send a forward DL packet to the UE 430.

[0042] The UE 430 may enter sleep mode at 415. For example, if a video frame is received within an on period, or if all expected packets are successfully received within an on period, the UE 430 may enter sleep sooner than if there was no on period because the on period is relatively short.

[0043] At 416, the UE 430 and the NE 440 may enter a second DRX cycle.

[0044] At 417, the UE 430 may start DRX according to the on-period parameters. For example, if the UE 430 does not receive a video frame within the on-period, or if the number of packets received within the on-period is less than the expected number of packets transmitted and received during the DRX cycle, the UE 430 may automatically extend the DRX active time, specifically the DRST, according to a configured extension timer.

[0045] At 418, the NE 440 may send a Scheduled DL packet to the UE 430 and notify the UE 430 that the Scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in the packet header, may be used to indicate that a packet is the last of a burst.

[0046] At 419, the NE 440 may send a forward DL packet to the UE 430.

[0047] At 420, the UE 430 may terminate DRX according to the on-duration parameter.

[0048] At 421, the UE 430 may start a "discontinuous stop" timer.

[0049] At 422, the NE 440 may send a Scheduled DL packet to the UE 430, indicating to the UE 430 that the Scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in the packet header, may be used to indicate that the packet is the last of a burst.

[0050] At 423, the NE 440 may send a forwarding DL packet to the UE 430.

[0051] At 424, the UE 430 may enter a sleep mode and forward DL packets may be received according to the XR traffic configuration.

[0052] FIG. 5 illustrates an example flow diagram of a method that may be performed by a UE, such as UE 1020 illustrated in FIG. 10, in accordance with various exemplary embodiments.

[0053] In 501, the method may include agreeing on XR traffic parameters with an NE, such as NE 1010 shown in FIG. 10. For example, this may be performed using RRC signaling during an RRC connection setup or RRC reconfiguration procedure. Alternatively, this may be performed by extending the PDU session establishment procedure, where the XR traffic parameters are exchanged between the UE and the AMF during PDU session establishment. Once the PDU session is established, the AMF notifies the RAN of the traffic parameters.

[0054] At 502, the method may include receiving from the NE an RRC IE indicating that DRST is active, and / or time-related parameters, and / or a threshold indicating the number of packets expected to be transmitted during a DRX cycle. For example, the time-related parameters may indicate an on-period (e.g., covering ¼ or ½ of the jitter range) and a DRST extension timer value. A specific timer value (inactivity timer) and the DRST extension timer value may run until a video frame is received (i.e., one slot at a time) or until the next on-period as instructed by the NE. In an exemplary embodiment, the inactivity timer may not be set or may be limited to a short value when DRST is set.

[0055] As mentioned above, DRST can be implemented as a timer that is triggered when no packets have been received yet, or when the drx-OnDuration timer expires when the number of received packets is less than the number of packets expected to be transmitted and / or received during a DRX cycle. As an example, a MAC may be modified to include a DRST to define parameters such as the duration of the "discontinuous stop" timer, its activation / deactivation conditions (e.g., when the number of received packets is less than the expected number of packets transmitted and / or received during a DRX cycle), and interaction with other DRX procedures, similar to the parameters shown in FIG. 7. The DRST timer may be associated with a DRX group; for example, a DRX group may have a single set of DRST parameters or all DRST parameters, with DRST parameters specific to each DRX group. Furthermore, two DRX groups may be associated with two dedicated DRX configurations (i.e., each group has its own DRX parameters, such as OnDuration and Inactivity Timer). DRST parameters may include enable / disable, extension timer, expected number of packets, etc.

[0056] At 503, the method may include applying the received DRX configuration.

[0057] At 504, the method may include the NE entering a first DRX cycle.

[0058] At 505, the method may include initiating DRX according to the on-duration parameter. The UE may monitor the PDCCH according to the on-duration.

[0059] At 506, the method may include receiving a scheduled DL packet from the NE and receiving a notification from the NE that the scheduled DL packet is the last packet of a burst. An end-of-burst notification, such as a DCI command or a bit carried in a packet header, may be used to indicate that a packet is the last of a burst.

[0060] In some exemplary embodiments, L1 / L2 signaling (either DCI or MAC CE commands) is used by the network to enable and disable DRST operation. This allows the network to detect the boundaries of delay-bounded bursts of packets (e.g., packets belonging to the same video frame). If the packet is the last of the burst, the UE may receive indication from the NE that no further packets are expected, and the UE may disable the DRST timer. If this is the last packet of the burst, the UE may receive scheduling information for the PDDCH from the NE (i.e., whether or not further transmissions are expected until the next DRX cycle). This information may be used by the UE to increment a counter for the number of received packets, which, together with drx-DiscontinousRestNrRxPdus, the number of transmitted packets, and drx-DiscontinousRestNrTxPdus, may be used to determine whether to start the drx-DiscontinousRestTimer after the expiration of the drx-onDurationTimer.

[0061] In various exemplary embodiments, a UE may receive a trigger for DRST from the NE using a DCI without using scheduling information. For example, a UE may not be scheduled by the NE during an On Period, but if the NE estimates that data will arrive shortly thereafter, the UE may receive a DCI that triggers DRST (or an inactivity timer, if configured), causing the UE to monitor the PDCCH after the expiration of the On Period. Additionally or alternatively, the GC-PDCCH may be used to address multiple UEs for such an extension.

[0062] At 507, the method may include receiving a forwarded DL packet from the NE. At 508, the method may include entering a sleep mode. For example, if a video frame is received within an on period, or if all expected packets are successfully received within an on period, the UE may enter sleep sooner than if there is no on period because the on period is relatively short.

[0063] At 509, the method may include the NE entering a second DRX cycle. At 510, the method may include initiating DRX according to an on-duration parameter. For example, if the UE does not receive a video frame within the on-duration, or if the number of packets received within the on-duration is less than the expected number of packets transmitted and received during the DRX cycle, the UE may automatically extend the DRX active time, specifically the DRST, according to a configured extension timer. Furthermore, the NE may monitor how often DRST is needed and adjust the on-duration together with the UE.

[0064] At 511, the method may include terminating DRX according to the on-duration parameter. At 512, the method may include starting a "discontinuous stop" timer. At 513, the method may include receiving a scheduled DL packet from the NE and receiving an indication that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0065] At 514, the method may include receiving a forwarded DL packet from the NE.

[0066] At 515, the method may include entering a sleep mode. For example, if a video frame is received within an on period, or if all expected packets are successfully received within an on period, the UE may enter sleep sooner than if there were no on period because the on period is relatively short.

[0067] At 516, the method may include the NE entering a second DRX cycle.

[0068] At 517, the method may include initiating DRX according to the on-period parameter. For example, if the UE does not receive a video frame within the on-period, or if the number of packets received within the on-period is less than the expected number of packets transmitted and received during the DRX cycle, the UE may automatically extend the DRX active time, specifically the DRST, according to a configured extension timer.

[0069] At 518, the method may include receiving a scheduled DL packet from the NE and receiving a notification that the scheduled DL packet is the last packet of a burst. An end-of-burst notification, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0070] At 519, the method may include receiving a forwarded DL packet from the NE.

[0071] At 520, the method may include receiving a scheduled DL packet from the NE and receiving a notification that the scheduled DL packet is the last packet of a burst. An end-of-burst notification, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0072] At 521, the method may include starting a "discontinuous stop" timer.

[0073] At 522, the method may include receiving a scheduled DL packet from the NE and receiving a notification that the scheduled DL packet is the last packet of a burst. An end-of-burst notification, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0074] At 523, the method may include receiving a forwarded DL packet from the NE.

[0075] At 524, the method may include entering a sleep mode and receiving forwarded DL packets according to the XR traffic setting.

[0076] FIG. 6 illustrates an example flow diagram of a method that may be performed by an NE, such as the NE 1020 shown in FIG. 10, in accordance with various exemplary embodiments.

[0077] At 601, the method may include agreeing on XR traffic parameters with a UE, such as UE 1020 shown in FIG. 10. For example, this may be performed using RRC signaling during an RRC connection setup or RRC reconfiguration procedure. Alternatively, it may be performed by extending the PDU session establishment procedure, where the XR traffic parameters are exchanged between the UE and the AMF during PDU session establishment. Once the PDU session is established, the AMF signals the traffic parameters to the RAN.

[0078] At 602, the method may include transmitting to the UE an RRC information element indicating that DRST is active and / or time-related parameters and / or threshold(s) indicating the expected number of packets to be transmitted / received during a DRX cycle. For example, the time-related parameters may indicate an on-period (e.g., covering ¼ or ½ of the jitter range) and a DRST extension timer value. The DRST extension timer value may run until a video frame is received (i.e., one slot at a time) according to a particular timer value, an inactivity timer, notification to the UE, or until the next on-period. In an exemplary embodiment, the inactivity timer may not be set or may be limited to a short value when DRST is set.

[0079] As mentioned above, DRST may be implemented as a timer that is triggered when no packets have been received yet, or when the number of received packets is less than the number of packets expected to be transmitted and / or received during a DRX cycle and the drx-OnDuration timer expires. As an example, the MAC may be modified to include DRST to define parameters such as the duration of the "discontinuous stop" timer, its activation / deactivation conditions (e.g., when the number of received packets is less than the expected number of packets transmitted and / or received during a DRX cycle), and interaction with other DRX procedures, similar to the parameters shown in FIG. 7. DRST parameters may be associated with a DRX group; for example, a DRX group may have a single set of DRST parameters, or, for all DRST parameters, DRST parameters specific to each DRX group. Furthermore, two DRX groups may be associated with two dedicated DRX configurations (i.e., each group has its own DRX parameters, such as OnDuration and Inactivity Timer). DRST parameters may include enable / disable, extension timer, expected number of packets, etc.

[0080] At 603, the method may include the UE entering a first DRX cycle.

[0081] At 604, the method may include transmitting the scheduled DL packet to the UE and notifying the UE that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0082] In some exemplary embodiments, L1 / L2 signaling (either DCI or MAC CE commands) is used by the network to enable and disable DRST operation. This allows the network to detect the boundaries of delay-bounded bursts of packets (e.g., packets belonging to the same video frame). If the packet is the last of a burst, the NE may inform the UE that no more packets are expected, and the UE may disable the DRST timer. The NE may also inform the UE of scheduling information for the PDDCH if this is the last packet of a burst (i.e., whether or not further transmissions are expected until the next DRX cycle). This information can be used by the UE to increment a counter for the number of received packets, which, together with drx-DiscontinousRestNrRxPdus, the number of transmitted packets, and drx-DiscontinousRestNrTxPdus, are used to determine whether to start the drx-DiscontinousRestTimer after the drx-onDurationTimer expires.

[0083] In various exemplary embodiments, an NE may use a DCI to trigger a DRST without using scheduling information. For example, if the NE does not schedule a UE 430 during an On Period, but estimates that data will arrive soon thereafter, the NE may send a DCI to trigger a DRST (or an inactivity timer, if configured) so that the UE monitors the PDCCH after the On Period expires. Additionally or alternatively, the GC-PDCCH may be used to address multiple UEs for such an extension.

[0084] At 605, the method may include transmitting a forwarded DL packet to the UE.

[0085] At 606, the method may include the UE entering a second DRX cycle.

[0086] At 607, the method may include transmitting the scheduled DL packet to the UE and notifying the UE that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0087] At 608, the method may include transmitting the forwarded DL packet to the UE.

[0088] At 609, the method may include the UE entering a third DRX cycle.

[0089] At 610, the method may include transmitting a scheduled DL packet to the UE and notifying the UE that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0090] At 611, the method may include transmitting a forwarded DL packet to the UE.

[0091] At 612, the method may include transmitting the scheduled DL packet to the UE and notifying the UE that the scheduled DL packet is the last packet of a burst. An end-of-burst indication, such as a DCI command or a bit carried in a packet header, may be used to indicate that the packet is the last of the burst.

[0092] At 613, the method may include transmitting a forwarded DL packet to the UE.

[0093] Figure 8 shows the probability distribution of the frame arrival process (e.g., truncated Gaussian centered on the arrival time) to model random jitter, and three configurations of DRX with DRST. In all three configurations, the long period duration is 16 ms, and the DRX cycle starts at 12 and ends at 28.

[0094] The three configurations include S1, which extends the on-period only when DRST is 30%. XR frames arriving between 12 and 15 are delayed by at most 3 ms. The three configurations also include S2, which does not trigger an on-period extension unless time drift causes the XR frame to fall after the on-period. However, because XR services have limited delay budgets (e.g., 10 ms for AR / VR applications), this setting introduces an extra 6 ms delay for frames arriving at 12 o'clock, potentially preventing HARQ retransmissions in the event of an error.

[0095] The three configurations also include S3. In 86% of cases, the on-period is extended. In 14% of cases, DRST does not need to extend the on-period, so a DRX configuration that starts at 12 and ends at 20 may be beneficial. In this way, DRST adds flexibility to easily configure DRX while considering the trade-off between user satisfaction and power saving. Regarding S2 in Figure 6, DRST rarely extends the on-period.

[0096] As explained above, certain embodiments may be preferable in terms of power saving gains. In one example, 100, 280, and 300 units of power may be consumed by a UE for monitoring each slot of the PDCCH, decoding symbols of the PDSCH, and decoding PDCCH+PDSCH, respectively. Performance may be evaluated corresponding to a subcarrier spacing of 30 kHz and a slot duration of 0.5 ms, and XR traffic may also be modeled. Video frames are generated at a constant frame rate of 60 fps, which corresponds to a period of 16.67 ms between two consecutive frames. To model jitter, a random variable distributed as a truncated Gaussian distribution may also be added to the constant period. The truncated Gaussian distribution has a mean of 0, a standard deviation of 2 ms, and a range of [-4; 4] ms.

[0097] Four methods can be used for analysis: 1) CDRX with LongCycle=16ms and OnDuration=8ms, 2) CDRX with LongCycle=16ms and OnDuration=12ms, 3) CDRX with LongCycle=16ms, OnDuration=4ms and DRST, and 4) CDRX with LongCycle=16ms, OnDuration=6ms and DRST.

[0098] The second CDRX configuration may have an OnDuration greater than the jitter range (i.e., 12 ms > 8 ms) because XR frame arrivals drift away from the CDRX cycle. Also, the XR frame arrival process has an average inter-arrival time of 16.67 ms, but the CDRX LongCycle may be equal to 16 ms. The 0.67 ms offset between XR arrivals and the CDRX cycle may result in a time drift that accumulates over time. Increasing the OnDuration may mitigate the time drift. Furthermore, DRST may only be configured for the third and fourth DRX schemes, which have an OnDuration shorter than the expected interval between frame arrivals (i.e., the jitter range).

[0099] The four schemes can be compared according to the power saving gain relative to an "always on" UE, specifically a UE with all power saving features disabled.

number

[0100] The large power-saving gains of DRST methods 3 and 4 are due to their short OnDuration, which is rarely extended by the DRST mechanism. In fact, a short OnDuration based on the estimated arrival time (i.e., every 16.67 ms) may be the optimal configuration for most video frames. However, DRST can recover from this unlikely event by extending the user's active time beyond the OnDuration.

[0101] 10 illustrates an example of a system in accordance with certain exemplary embodiments. In one exemplary embodiment, the system may include multiple devices, such as, for example, a NE 1010 and / or a UE 1020.

[0102] The NE1010 may be one or more of a base station such as an eNB or gNB, a serving gateway, a server, and / or any other access node or combination thereof.

[0103] The NE 1010 may further include at least one gNB-CU that may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may include at least one F1 interface, at least one X (n) -C interface, and / or at least one NG interface via 5GC.

[0104] The UE 1020 may include one or more of the following: a mobile device such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, or a portable media player; a digital camera, a pocket video camera, a video game console; a navigation device such as a Global Positioning System (GPS) device; a desktop or laptop computer; a single positioning device such as a sensor or smart meter; or any computing device thereof. Additionally, the NE 1010 and / or the UE 1020 may be one or more of a Citizens Broadband Wireless Service Device (CBSD).

[0105] The NE 1010 and / or the UE 1020 may include at least one processor, respectively denoted as 1011 and 1021. The processors 1011 and 1021 may be embodied by any computing or data processing device, such as a central processing unit (CPU), an application specific integrated circuit (ASIC), or equivalent device. The processor may be implemented as a single controller or multiple controllers or processors.

[0106] At least one memory may be provided in one or more devices, as indicated by 1012 and 1022. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. The memories 1012 and 1022 may independently be any suitable computing device, such as a non-transitory computer-readable medium. As used herein, the term "non-transitory" refers to the medium itself (i.e., tangible, not signal) as opposed to the data storage persistent limitation (e.g., RAM vs. ROM). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memory may be combined on a single integrated circuit as the processor or may be separate from one or more processors. Furthermore, the computer program instructions stored in the memory and processed by the processor may be any suitable form of computer program code, such as a compiled or interpreted computer program written in any suitable programming language.

[0107] Processors 1011 and 1021, memories 1012 and 1022, and any subset thereof, may be configured to provide means corresponding to the various blocks of Figures 3-6. Although not shown, the device may also include positioning hardware, such as GPS or microelectromechanical systems (MEMS) hardware, that can be used to determine the device's location. Other sensors are also permitted, such as a barometer, compass, and the like, that may be configured to determine position, altitude, speed, heading, etc.

[0108] As shown in Figure 10, transceivers 1013 and 1023 may be provided, and one or more devices may also include at least one antenna, illustrated as 1014 and 1024, respectively. The devices may have multiple antennas, such as an array of antennas configured for multiple-input multiple-output (MIMO) communications, or multiple antennas for multiple RATs. For example, other configurations of these devices may also be provided. The transceivers 1013 and 1023 may be units or devices configured to transmit, receive, both transmit and receive, or both transmit and receive.

[0109] The memory and computer program instructions, together with a processor for a particular device, may be configured to cause a hardware device, such as a UE, to perform any of the processes described above (i.e., FIGS. 3-6). Thus, in certain exemplary embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process, such as one of the processes in this example. Alternatively, certain exemplary embodiments may be performed entirely in hardware.

[0110] In certain exemplary embodiments, a device may include circuitry configured to perform any of the processes or functions illustrated in Figures 3-6. For example, the circuitry may be a hardware-only circuit implementation, such as analog and / or digital circuitry. In another example, the circuitry may be a combination of analog and / or digital hardware circuitry with software or firmware, and / or a combination of hardware circuitry and software, such as any portion of a hardware processor and software (including a digital signal processor), software, and at least one memory that cooperate to cause the device to perform various processes or functions. In yet another example, the circuitry may be a hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that includes software, such as firmware, for operation. Software within the circuitry may be absent if not necessary for the operation of the hardware.

[0111] FIG. 11 illustrates an example of a 5G network and system architecture according to certain exemplary embodiments. Several network functions are illustrated, which may be implemented as software running as part of network equipment or dedicated hardware, as the network equipment itself or dedicated hardware, or as virtual functions running as network equipment or dedicated hardware. The NE and UE illustrated in FIG. 11 may be similar to NE 1010 and UE 1020, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, data packet routing and forwarding, packet inspection, user plane quality of service (QoS) processing, downlink packet buffering, and / or downlink data notification triggering. The application function (AF) may interconnect with the core network primarily to facilitate application utilization of traffic routing and interact with the policy framework.

[0112] According to certain exemplary embodiments, the processors 1011 and 1021 and memories 1012 and 1022 may be included in or form part of processing or control circuitry. Further, in some exemplary embodiments, the transceivers 1013 and 1023 may be included in or form part of transceiver circuitry.

[0113] In some exemplary embodiments, an apparatus (e.g., the NE 1010 and / or the UE 1020) may include means for performing any of the methods, processes, or variations discussed in this example. Examples of means may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for performing the operations.

[0114] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the use of the phrases "various embodiments," "particular embodiments," "some embodiments," or other similar phrases throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an exemplary embodiment may be included in at least one exemplary embodiment. Thus, the appearances of "various embodiments," "particular embodiments," "some embodiments," or other similar phrases throughout this specification do not necessarily all refer to the same group of exemplary embodiments, but rather that the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

[0115] Moreover, where appropriate, different functions or procedures described above may be performed in different orders and / or concurrently with one another. Moreover, where appropriate, one or more of the described functions or procedures may be optional or combined. As such, the foregoing description should be considered illustrative of the principles and teachings of particular exemplary embodiments, and not limiting thereof.

[0116] Those skilled in the art will readily appreciate that the exemplary embodiments described above may be implemented using a different sequence of steps and / or hardware elements in different configurations than those disclosed. Thus, while several embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while remaining within the spirit and scope of the exemplary embodiments.

[0117] Part of the glossary 3GPP (registered trademark) 3rd Generation Partnership Project 5G (5th Generation) 5GC 5th generation core 6G 6th generation ASIC Application Specific Integrated Circuit BS base station CBSD Citizens Broadband Wireless Service Equipment CDRX Connected Mode Discontinuous Reception CE Control Elements CN Core Network CPU Central Processing Unit CRC Cyclic Redundancy Check DCI Downlink Control Information DCP Dynamic Clustering Protocol DL Downlink DRST (Discontinuous Rest) DRX Discontinuous Reception eMBB Enhanced Mobile Broadband eNB Evolved Node B EPS Evolved Packet System FR Frequency Range GC-PDCCH Group Common Physical Downlink Control Channel gNB Next Generation Node B GPS Global Positioning System HARQ Hybrid Automatic Repeat Request HDD Hard Disk Drive L1 Layer 1 L2 Layer 2 LTE Long Term Evolution LTE-A Long Term Evolution Advanced MAC Media Access Control MEMS Microelectromechanical Systems MIMO Multiple Input Multiple Output MME Mobility Management Entity mMTC Large-scale Machine Type Communication NE Network Entity NG Next generation NG-eNB Next Generation Evolved Node B NG-RAN Next Generation Radio Access Network NR New Radio NR-U New Radio License PDA Personal Digital Assistance PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PS-RNTI Power Saving Radio Network Temporary Identifier RAM Random Access Memory RAN Radio Access Network RAT Radio Access Technology RE Resource Element RF radio frequency RLC Radio Link Control RNTI Radio Network Temporary Identifier RRC Radio Resource Control RS reference signal SMF Session Management Facility SSSG Search Space Set Group TB Transport Block TTI Transmission Time Interval Tx Transmission UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System UPF User Plane Function URLLC: Ultra-reliable, low-latency communication UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network WLAN Wireless Local Area Network XR Augmented Reality

Claims

1. receiving, by a user equipment, a discontinuous stop configuration; the user equipment starting a discontinuous stop timer indicated in the discontinuous stop configuration when, at the end of an active time, the number of packets transmitted and the number of packets received before the end of the active time are less than the corresponding thresholds indicated in the discontinuous stop configuration; Including, the discontinuous stop timer is associated with a discontinuous reception group; method.

2. The method of claim 1 , wherein the discontinuous stop configuration is received as a Layer 1 or Layer 2 signal.

3. The method of claim 2 , wherein the Layer 1 or Layer 2 signal is received in a media access control element command or downlink control information.

4. 4. The method of claim 1, wherein the downlink control information, medium access control element command, or packet header element indicates the last packet of a data burst.

5. The method of claim 4 , wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

6. The method according to claim 1 , wherein the discontinuous stop configuration is received in downlink control information.

7. the user equipment monitoring a downlink control channel when the discontinuous stop timer is running; The method of any one of claims 1 to 6, further comprising:

8. The method of claim 1 , wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

9. a network entity transmitting a discontinuous stop configuration indicating a discontinuous stop timer that is started at the end of an active time associated with a discontinuous receiving group when a number of packets transmitted and a number of packets received before expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop configuration.

10. The method of claim 9 , wherein the discontinuous stop configuration is transmitted as a Layer 1 or Layer 2 signal.

11. 11. The method according to claim 9, wherein the layer 1 or layer 2 signal is carried in a medium access control element command or downlink control information.

12. 12. A method according to any one of claims 9 to 11, wherein the downlink control information, or medium access control element command, or packet header element indicates the last packet of a data burst.

13. The method of claim 12 , wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

14. The method according to any one of claims 9 to 13, wherein the discontinuous stop configuration is transmitted via downlink control information.

15. The method of claim 9 , wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

16. 1. An apparatus comprising: at least one processor; When executed by the at least one processor, the device includes at least: receiving a discontinuous stop setting; at the end of an active time, if the number of packets transmitted and the number of packets received before the expiration of the active time are less than the corresponding thresholds indicated in the discontinuous stop setting, starting a discontinuous stop timer indicated by the discontinuous stop setting; at least one memory storing instructions for executing the Equipped with the discontinuous stop timer is associated with a discontinuous reception group; Device.

17. The apparatus of claim 16 , wherein the discontinuous stop configuration is received as a Layer 1 signal or a Layer 2 signal.

18. 20. The apparatus of claim 17, wherein the Layer 1 or Layer 2 signal is received in a medium access control element command or downlink control information.

19. 19. The apparatus of claim 16, wherein the downlink control information, or medium access control element command, or packet header element indicates the last packet of a data burst.

20. 20. The apparatus of claim 19, wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

21. 21. The apparatus of claim 16, wherein the discontinuous stop configuration is received in downlink control information.

22. The at least one memory and the computer program code are transmitted by the at least one processor to the device, further comprising at least: monitoring a downlink control channel when said discontinuous stop timer is running; 22. Apparatus according to any one of claims 16 to 21, configured to cause the execution of

23. 23. The apparatus of claim 16, wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

24. 1. An apparatus comprising: at least one processor; When executed by the at least one processor, the device includes at least: transmitting a discontinuous stop setting indicating a discontinuous stop timer that is started at the end of an active time associated with a discontinuous reception group if the number of packets transmitted and the number of packets received before expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting; at least one memory storing instructions for executing the An apparatus comprising:

25. 25. The apparatus of claim 24, wherein the discontinuous stop configuration is transmitted as a Layer 1 signal or a Layer 2 signal.

26. 26. The apparatus of claim 24 or 25, wherein the Layer 1 or Layer 2 signal is carried in a medium access control element command or downlink control information.

27. 27. Apparatus according to any of claims 24 to 26, wherein the downlink control information, or medium access control element command, or packet header element indicates the last packet of a data burst.

28. 28. The apparatus of claim 27, wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

29. 29. The apparatus of claim 24, wherein the discontinuous stop configuration is transmitted via downlink control information.

30. 30. The apparatus of claim 24, wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

31. means for receiving a discontinuous stop setting; means for starting a discontinuous stop timer indicated in the discontinuous stop setting at the end of an active time when the number of packets transmitted and the number of packets received before the expiration of the active time are less than the corresponding thresholds indicated in the discontinuous stop setting; Equipped with the discontinuous stop timer is associated with a discontinuous reception group; Device.

32. 32. The apparatus of claim 31, wherein the discontinuous stop configuration is received as a Layer 1 signal or a Layer 2 signal.

33. 33. The apparatus of claim 32, wherein the Layer 1 or Layer 2 signal is received in a medium access control element command or downlink control information.

34. 34. The apparatus of claim 31, wherein the downlink control information, or medium access control element command, or packet header element indicates the last packet of a data burst.

35. 35. The apparatus of claim 34, wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

36. 36. The apparatus of claim 31, wherein the discontinuous stop configuration is received in downlink control information.

37. means for monitoring a downlink control channel when said discontinuous stop timer is running; 37. The apparatus of any of claims 31 to 36, further comprising:

38. 38. The apparatus of claim 31, wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

39. means for transmitting a discontinuous stop setting indicating a discontinuous stop timer that is started at the end of an active time associated with a discontinuous reception group if a number of packets transmitted and a number of packets received before expiration of the active time are less than corresponding thresholds indicated in the discontinuous stop setting.

40. 40. The apparatus of claim 39, wherein the discontinuous stop configuration is transmitted as a Layer 1 signal or a Layer 2 signal.

41. 41. The apparatus of claim 39 or 40, wherein the Layer 1 or Layer 2 signal is carried in a medium access control element command or downlink control information.

42. 42. Apparatus according to any of claims 39 to 41, wherein the downlink control information, or medium access control element command, or element of the packet header indicates the last packet of a data burst.

43. 43. The apparatus of claim 42, wherein the element of the packet header comprises a Layer 1 or Layer 2 packet data unit.

44. 44. The apparatus of any of claims 39 to 43, wherein the discontinuous stop configuration is transmitted via downlink control information.

45. 45. The apparatus of claim 39, wherein the active time comprises an on-duration timer, an inactivity timer, or a retransmission timer.

46. A non-transitory computer readable medium comprising program instructions that, when executed by said device, cause said device to perform at least the method of any of claims 1 to 15.

47. 16. Apparatus comprising circuitry configured to perform the method of any preceding claim.

48. A computer program product encoded with instructions for performing the method of any preceding claim.

Images