Application timeline with unified design for active mode user equipment power saving for devices, systems, and methods

Abstract

The present disclosure relates to application timelines with unified design for active mode user equipment power saving for apparatuses, systems, and methods. A wireless communication system can use downlink control information (DCI) to adjust physical downlink control channel (PDCCH) monitoring behavior. The monitoring behavior change can be skipping or switching. A timeline for applying the switch or skip can be applied after a reference point and a processing time. In some embodiments, the processing time can be based on UE processing, network processing, or a combination.

Description

Technical Field

[0001] This patent application relates in general to wireless communication systems, including scheduling PDCCH skipping and search space set switching. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile equipment. Wireless communication system standards and protocols may include 3GPP Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to by the industry organization as WiMAX; and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In the fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes and NR nodes (also known as next-generation node B or g NodeB (gNB)).

[0003] The RAN uses Radio Access Technology (RAT) to communicate between RAN nodes and UEs. The RAN can include Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provides access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal System for Mobile Communications (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT, and NG-RAN implements the 5G RAT. In some deployments, E-UTRAN may also implement the 5G RAT.

[0004] 5G NR frequency bands can be divided into two distinct frequency ranges. Frequency range 1 (FR1) may include bands operating below 6 GHz, some of which are available for previous standards and can potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include bands from 24.25 GHz to 52.6 GHz. The bands in the millimeter wave (mmWave) range of FR2 may have a smaller range than those in FR1 but potentially higher available bandwidth. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may vary over time or in different regions. Attached Figure Description

[0005] To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0006] Figure 1 The UE monitoring behavior during an example timeline is shown according to one implementation scheme.

[0007] Figure 2A The diagram illustrates a downlink timeline for a skipped UE when PDCCH monitoring is applied after the ACK message is sent and processing time is reached, according to one implementation.

[0008] Figure 2B The downlink timeline of a UE applying SSSG handover after sending an ACK message and processing time is shown according to one implementation scheme.

[0009] Figure 2C The downlink timeline of a UE receiving a DL-scheduled DCI with a skip or handover indication according to one embodiment is shown.

[0010] Figure 3 A flowchart illustrating a method for applying power-saving enhancements using downlink scheduling authorization including DCI in a UE according to one implementation scheme is shown, including skipping and handover.

[0011] Figure 4 A flowchart illustrating a method for applying power-saving enhancements using downlink scheduling authorization including DCI in a network node according to one implementation scheme is shown, including skipping and switching.

[0012] Figure 5 A method for applying power-saving enhancements, including skipping and handover, is illustrated using uplink scheduling authorization including DCI in a UE according to one implementation scheme.

[0013] Figure 6A method for applying energy-saving enhancements, including skipping and handover, is illustrated using uplink scheduling authorization, including DCI, in network nodes according to one implementation scheme.

[0014] Figure 7 A method for applying power-saving enhancements using non-scheduled DCI in a UE according to one implementation is shown, including skipping and handover.

[0015] Figure 8 An exemplary monitoring timeline according to one implementation is shown, in which network nodes send DCI using a sparse configuration during a transition period.

[0016] Figure 9 The timeline is shown according to one embodiment, in which the sparse pattern is not a subset of the dense pattern.

[0017] Figure 10 A system according to one implementation is shown.

[0018] Figure 11 The infrastructure equipment according to one implementation plan is shown.

[0019] Figure 12 A platform based on one implementation scheme is shown. Detailed Implementation

[0020] One goal of network communication is to reduce the power consumption of user equipment (UE). Commonly used power-saving techniques are balanced to minimize the impact on system performance. One method that can be used to enhance UE power efficiency is to reduce or change the UE's monitoring cycle.

[0021] This document describes systems, apparatus, and methods for adjusting Physical Downlink Control Channel (PDCCH) monitoring behavior to reduce UE power consumption. In some embodiments, the network node and UE use Search Space Group (SSSG) handover to alter PDCCH monitoring behavior. In some embodiments, the network node and UE use PDCCH skipping to alter PDCCH monitoring behavior (e.g., Search Space Group (SSSG) handover). For example, the network node may instruct the UE to monitor the PDCCH or skip PDCCH monitoring. Furthermore, the network node may instruct the UE to switch PDCCH monitoring modes or perform an SSSG handover.

[0022] Implementations may include a general design for adapting PDCCH monitoring based on Downlink Control Information (DCI) within the effective time of the Active Bandwidth Part (BWP) to support functionality including SSSG handover and PDCCH skipping for a period of time. In some implementations, a reference point and a delay time are determined for SSSG handover and PDCCH skipping. The reference point refers to a time or time slot at which the UE and network node can time the monitoring behavior change. The delay time may refer to the processing time during which the UE or network node enables SSSG handover or PDCCH skipping. In some implementations, handover or skipping may be applied when an amount of time equal to the delay time (e.g., processing time) has elapsed after the reference point. In other words, the UE and network node apply the monitoring behavior change after the reference point plus the processing time.

[0023] Processing time can include the time the UE processes the handover or skips the handover and the time the network node enables the handover or skips the handover. Several different times are associated with processing time. For the UE to enable search space handover, processing-related time can include the time for decoding the DCI and the time for processing and configuring the individual search space configuration. To simplify the reference to this handover processing time, this document uses T_switching to refer to the time for decoding the DCI and the time for processing and configuring the individual search space configuration. Furthermore, this document uses T_switching_1 to refer to the time for processing and configuring the individual search space configuration without DCI decoding time. In some implementations, T_switching can be hardcoded in both the network node and the UE. For example, T_switching can be three time slots or fewer.

[0024] For a UE to enable skip commands, the processing time can include the time for decoding the DCI and the time for applying the skip command. To simplify the reference to this skip processing time, this document uses T_skipping to refer to the time for decoding the DCI and applying the skip command. Furthermore, this document uses T_skipping_1 to refer to the time for applying the skip command without DCI decoding time. Since there is no processing and configuration of a new search space, T_skipping may be less than T_switching. T_skipping can be hardcoded in both the network node and the UE. For example, T_skipping can be two time slots or less.

[0025] For network nodes, processing time can revolve around the time spent receiving and processing acknowledgments (ACKs) or Physical Uplink Shared Channel (PUSCH) from the UE. ACK reception and processing time can depend on whether Discontinuous Receive Mode (DRX) is configured. In some implementations, when DRX is configured, the drx-HARQ-RTT-TimerDL value can be used to represent the ACK reception and processing time. Drx-HARQ-RTT-TimerDL is a timer that can represent the minimum duration expected by the MAC entity before the DL allocation for HARQ retransmission. When DRX is not configured, it can be assumed that the T_ack time represents the ACK reception and processing time. T_ack can be a hard-coded amount of time (e.g., multiple time slots). For example, in some implementations, T_ack can be configured to three time slots or fewer.

[0026] The network node processing time associated with PUSCH reception and processing can also depend on whether DRX is configured. When DRX is configured, the drx-HARQ-RTT-TimerUL value can be used to represent the PUSCH reception and processing time. Drx-HARQ-RTT-TimerUL is a timer that can represent the minimum duration that a MAC entity expects before a UL HARQ retransmission authorization. When DRX is not configured, it can be assumed that the T_pusch time represents the PUSCH reception and processing time. T_pusch can be a hard-coded amount of time (e.g., multiple time slots). For example, in some implementations, T_pusch can be configured to three time slots or fewer.

[0027] The various operations will be described sequentially as a plurality of discrete operations in a manner most conducive to understanding this disclosure. However, the order of description should not be construed as implying that these operations necessarily depend on a specific order. In particular, these operations do not necessarily need to be performed in the order of presentation.

[0028] Additional details and examples are provided with reference to the following accompanying drawings. Embodiments of this disclosure can be understood with reference to the drawings, wherein similar components are consistently represented by similar numbers. Components of the embodiments of the invention disclosed herein, as generally described and illustrated in the accompanying drawings, can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of embodiments of the systems and methods of this disclosure is not intended to limit the scope of this disclosure as protected by the claims, but rather represents only possible embodiments.

[0029] Figure 1The illustration shows UE monitoring behavior during example timeline 100. In some implementations, a DCI (Distributed Control Information) can be transmitted from the network node to the UE to indicate a change in monitoring behavior. A DCI indicating a skipped period may cause the UE to not monitor certain segments of timeline 100. A DCI indicating a switching period may allow the UE to use a less intensive monitoring mode. By not monitoring for the entire duration, the UE can reduce power consumption.

[0030] In the illustrated implementation, downlink or uplink traffic exists during the first time period 102. During this period, the UE can receive DCI. The DCI can instruct the UE to perform skip, handover, or both during the UE's monitoring behavior. A network node (e.g., gNB) can send a notification to the UE via the DCI to perform a certain number of time slot skips and / or handovers, and then return to monitoring. For example, during the second time period 104, there is no traffic in the downlink or uplink communication channel, so the UE can skip monitoring those time slots. The UE performs the skip and stops monitoring until the third time period 106. During the fourth time period 108, the UE can resume a more intensive monitoring mode.

[0031] A skip value indicates how long the skip period should be and when the skip should be performed. A switch value indicates when and for how long a switch should be applied. Both skip and switch values ​​can be configured Radio Resource Control (RRC). In some implementations, the scheduled DCI can provide a timeline for applying the skip and switch after receiving a DCI indicating a skip. For example, in some implementations, a network node can send a DCI with a skip or switch indication along with the last transport block for downlink / uplink transmission. The skip or switch indication may include one or two bits added to the scheduled DCI. Furthermore, unscheduled DCIs or timers can be used to implement skip or switch DCIs during periods when no traffic is available for scheduling.

[0032] Furthermore, the UE and network node can be configured to synchronously implement skipping or handover. To synchronize monitoring mode changes between the UE and network node, a reference point and processing time can be determined. When an amount of time equal to the processing time has elapsed after the reference point, a change in monitoring behavior can be applied. The following are implementation schemes including various reference points and processing times to synchronize the behavior of the UE and network node.

[0033] Figures 2A to 2CThe diagram illustrates a downlink timeline for monitoring skipped or handedover UEs using PDCCH based on Acknowledgment (ACK) and Negative Acknowledgment (NACK) messages, according to several implementations. As shown, in some implementations, when the DCI is signaled by DL scheduling authorization and the UE responds with a NACK message, the trigger command is eliminated because the network node cannot distinguish between NACK and Discontinuous Receive (DTX). The network node can send a trigger command (i.e., a command for skipping or handover) in the DCI for retransmission authorization. Furthermore, in some implementations, when the DCI is signaled by DL scheduling authorization and the UE responds with an ACK message, the UE applies skip or handover after the ACK transmission plus processing time. The DCI can be DCI formats 1-1 and 1-2.

[0034] Figure 2A The diagram illustrates a downlink timeline 200a for a UE that has skipped PDCCH monitoring after sending ACK message 210 and processing time 204. In this implementation, ACK message 210 is used as a reference point. If the received downlink scheduling DCI 202 includes a skip indication, the UE applies skip 212 to the pre-configured time slot after transmitting ACK message 210 and after processing time 204 occurs.

[0035] As shown in the figure, the network node transmits scheduling DCI 202 during the first time period. The UE receives scheduling DCI 202. In the illustrated embodiment, the UE continues to receive Physical Downlink Shared Channel (PDSCH) 208 from the network node and transmits ACK message 210 to the network node. ACK message 210 indicates that the UE has correctly received downlink scheduling DCI 202. There may be no expected retransmission.

[0036] After sending ACK message 210, the UE can apply skip 212 after the processing time 204 expires. The UE does not perform PDCCH monitoring for a period of time after sending ACK message 210 and after the processing time 204 occurs. The amount of time the UE spends skipping PDCCH monitoring can be a pre-configured number of time slots or a specific time period. During this period, the UE does not monitor the PDCCH and thus saves power. The UE can resume monitoring 206 after the pre-configured skip time slots or time period.

[0037] Figure 2B A downlink timeline 200b is shown for a UE that applies SSSG handover 216 after sending ACK message 218 and processing time 214. In this embodiment, ACK message 218 is used as a reference point. If the received downlink scheduling DCI 202 includes a skip indication, the UE applies handover 216 after the UE transmits ACK message 218 and after processing time 214 occurs.

[0038] As shown in the figure, the network node transmits scheduling DCI 220 during the first time period. The UE receives scheduling DCI 220. In the illustrated implementation, the UE continues to receive PDSCH 222 from the network node and transmits ACK message 218 to the network node. ACK message 218 indicates that the UE has correctly received downlink scheduling DCI 220. There may be no expected retransmission.

[0039] After sending ACK message 218, the UE can apply search space switching 216 after the processing time 214 has expired. In other words, the UE applies a new search space after sending ACK message 218 and after the processing time 214 has occurred.

[0040] Figure 2C A downlink timeline 200c is shown for a UE receiving a DL-scheduled DCI 224 with a skip or handover indication. In this timeline 200c, the UE receives the DL-scheduled DCI 224 with a skip or handover indication. However, the UE fails to execute and send a NACK message 226 correctly. The network node may be unable to distinguish between a NACK (e.g., the UE correctly decoded the DCI but failed to decode only the PDSCH) and a discontinuous transmission (DTX) (e.g., the UE did not decode the DCI). Because the network node may not know whether the DCI was correctly decoded when the feedback is a NACK message 226, the trigger command (e.g., a handover or skip command) is canceled. The network node may send a retransmitted DCI 228. If the UE is able to correctly receive and process the retransmitted DCI 228, the UE will send an ACK message, and the UE and the network node can process the data as follows: Figure 2A and Figure 2B The monitoring behavior of the skip or toggle commands discussed in the article has changed.

[0041] The processing time (i.e., processing time 204 and processing time 214) can be determined in a variety of ways. The processing time can be based on the UE processing time or the network node processing time.

[0042] In the first implementation, the processing time may depend on whether the DCI includes skip triggering or toggle triggering. For example, in Figure 2A In this context, the processing time 204 can be either T_skipping (i.e., the time for decoding the DCI plus the time for applying the skip command) or T_skipping_1 (i.e., the time for applying the skip command), because the PDCCH skip command was triggered. However, in Figure 2BIn this context, the processing time 214 can be either T_switching (i.e., the time for decoding the DCI plus the time for processing and configuring a separate search space configuration) or T_switching_1 (i.e., the time for processing and configuring a separate search space configuration), because a new search space command is triggered.

[0043] In the second implementation, the processing time can be configured to always be T_switching or T_switching_1, regardless of which operation is triggered. For example, Figure 2A Processing time 204 and Figure 2B The processing time of 2^14 can be set to T_switching. For example, Figure 2A Processing time 204 and Figure 2B The processing time of 214 can be set to T_switching_1.

[0044] In the third implementation, the processing time can be set to T_ack time. T_ack time can represent the ACK reception and processing time of a network node. For example, in some implementations, T_ack can be configured to three time slots or less. Therefore, Figure 2A Processing time 204 and Figure 2B The processing time of 214 can be set to T_ack.

[0045] In the fourth implementation, if a timer is configured, the processing time can be set to drx-HARQ-RTT-TimerDL. Drx-HARQ-RTT-TimerDL is a timer that can represent the minimum duration that the MAC entity expects before the DL allocation for HARQ retransmission.

[0046] In the fifth implementation, the processing time can be determined based on one or more factors. For example, the processing time can be the maximum value of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL.

[0047] Figure 3 A flowchart of method 300, in which a UE applies power-saving enhancements using downlink scheduling grants that include a downlink control information (DCI) message, is shown, including skipping and handover. A UE implementing method 300 may receive a downlink scheduling grant 302 that includes a downlink scheduling grant excluding a downlink control information (DCI) message. The DCI message may indicate to the UE that it should apply the monitoring behavior change.

[0048] The UE can send an ACK or NACK based on whether it successfully decodes the 304 DCI. When the UE fails to decode the DCI correctly or when the UE does not decode the PDSCH, the UE can generate and send a 306 NACK message. The handover or skip command from the DCI can be considered cancelled until the UE successfully receives a retransmission of the 308 DCI message instructing the UE to apply the skip or handover command.

[0049] The UE can generate and send a 310 ACK message to indicate that a DCI message has been received and the PDSCH has been correctly decoded. The ACK message can be used as a reference point to determine when to implement a monitoring behavior change. The UE can determine the processing time for the 312 monitoring behavior change. In some implementations, the processing time can be one of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. In some implementations, the processing delay can always be T_switching or T_switching_1, regardless of whether the command is a handover command or a skip command. In some implementations, the processing time can be the maximum of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. When an amount of time equal to the processing time has elapsed since sending the ACK message, the UE can apply the 314 monitoring behavior change.

[0050] Figure 4 A flowchart illustrating method 400, in which a network node applies power-saving enhancements using downlink scheduling authorization including a DCI message, is shown, including skipping and handover. The network node implementing method 400 can transmit 402 a downlink scheduling authorization including a downlink control information (DCI) message. The DCI message can instruct the UE to apply the monitored behavior change.

[0051] Network nodes can receive ACK or NACK based on whether the UE successfully decodes the DCI. When the UE fails to decode the DCI correctly or when the UE does not decode the PDSCH, the network node can receive a 404 NACK message. The handover or skip command from the DCI can be considered cancelled. The network node can transmit a 406 retransmission of the DCI message instructing the UE to apply the skip or handover.

[0052] A network node can receive an ACK message (408) indicating that a DCI message has been received and the PDSCH has been correctly decoded. The ACK message can be used as a reference point to determine when to implement a change in monitoring behavior. The network node can determine (410) the processing time for the change in monitoring behavior. In some implementations, the processing time can be one of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. In some implementations, the processing delay can always be T_switching or T_switching_1, regardless of whether the command is a switching command or a skip command. In some implementations, the processing time can be the maximum value of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. When an amount of time equal to the processing time has elapsed since sending the ACK message, the network node can apply (314) a change in transmission timing to correspond to the change in monitoring behavior.

[0053] Figure 5 and Figure 6 A method for monitoring skipping or switching of PDCCH by uplink scheduling authorization signaling, including DCI, is shown. DCI can be DCI format 0-1 or 0-2. In the new air interface, uplink transmissions do not have ACK / NACK. Instead, asynchronous HARQ retransmissions are used. Therefore, the reference point can be after the PUSCH transmission or after the drx-RetransmissionTimerUL (e.g., a retransmission timer for uplink retransmissions) expires, rather than after the ACK / NACK message.

[0054] Figure 5 The diagram illustrates a method 500 for a UE to apply power-saving enhancements using uplink scheduling grants that include downlink control information (DCI), including skipping and handover. A UE implementing method 500 can receive an uplink scheduling grant 502 that includes a downlink control information (DCI) message. The DCI message can instruct the UE to apply the monitored behavior change. The UE can then determine 504 whether DRX is configured.

[0055] When DRX is configured and the DRX retransmission timer is short, the UE applies a skip or handover command after the timer expires. Otherwise, the UE can apply the skip or handover command after the PUSCH transmission plus processing time. As shown in the figure, the UE can determine the 506drx-RetransmissionTimerUL length and compare this length with a threshold 508. In some implementations, the threshold can be 8 time slots.

[0056] If the drx-RetransmissionTimerUL length is less than a threshold, a 512 skip or switch can be applied after the drx-RetransmissionTimerUL expires to limit the impact of retransmission latency. In some implementations, a processing delay can be added after the timer expires but before applying the skip or switch. The processing delay can be T_switching or T_switching_1, or T_skipping or T_skipping_1, depending on whether the command is a skip or switch command. In some implementations, the processing delay can always be T_switching or T_switching_1, regardless of whether the command is a switch or skip command. In some implementations, the processing time can be the maximum of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL.

[0057] If drx-RetransmissionTimerUL is greater than the threshold, the application 510 of the skip or switch command can occur after the PUSCH transmission and processing delay. In some implementations, the processing time can be one of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. In some implementations, the processing delay can always be T_switching or T_switching_1, regardless of whether the command is a switch command or a skip command. In some implementations, the processing time can be the maximum of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL.

[0058] When DRX is not configured, there may be no retransmission timer for uplink retransmissions. Instead, the UE can apply a 510 skip or handover command after the PUSCH transmission plus processing time. The processing delay can be based on UE processing, network node processing, or a combination of UE processing and network node processing. In some implementations, the processing time can be one of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. In some implementations, the processing delay can always be T_switching or T_switching_1, regardless of whether the command is a handover or skip command. In some implementations, the processing time can be the maximum of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL.

[0059] Figure 6 A method 600 is illustrated whereby a network node applies power-saving enhancements using uplink scheduling grants that include downlink control information (DCI), including skipping and handover. The network node implementing method 600 may transmit, at 602, an uplink scheduling grant including a downlink control information (DCI) message. The DCI message may instruct the UE to apply the monitored behavior change. The network node may then determine, at 604, whether DRX is configured.

[0060] When DRX is configured and the DRX retransmission timer is short, the network node can transmit according to a skip or switch command after the timer expires. Otherwise, the network node can transmit according to the application's skip or switch command after the PUSCH transmission plus processing time. As shown in the figure, the network node can determine the 606drx-RetransmissionTimerUL length and compare this length with a threshold 608. In some implementations, the threshold can be 8 time slots.

[0061] If the drx-RetransmissionTimerUL length is less than the threshold, skip or switch can be applied after the drx-RetransmissionTimerUL expires to limit the impact of retransmission delay. In some implementations, a processing delay can be added after the timer expires but before applying skip or switch. If the drx-RetransmissionTimerUL is greater than the threshold, the application of the skip or switch command 610 can occur after the PUSCH transmission and processing delay. When DRX is not configured, there may be no retransmission timer for uplink retransmissions. Instead, network nodes can transmit according to the skip or switch command 610 after the PUSCH transmission plus the processing time.

[0062] The processing latency can be based on UE processing, network node processing, or a combination of UE processing and network node processing. In some implementations, the processing time can be one of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL. In some implementations, the processing latency can always be T_switching or T_switching_1, regardless of whether the command is a switching command or a skip command. In some implementations, the processing time can be the maximum value of two or more of T_switching, T_switching_1, T_skipping, T_skipping_1, T_ack, and drx-HARQ-RTT-TimerDL.

[0063] Figure 7 A method 700 for a UE to apply power-saving enhancements using unscheduled DCI is illustrated, including skipping and handover. The DCI can be in DCI format 2-0, 2-6, or 1-1. The reference point can be the last symbol of the DCI. The network node can prepare and transmit unscheduled downlink control information (DCI) instructing the UE to apply the monitored behavior change. A UE implementing method 700 can receive unscheduled DCI 702.

[0064] The UE can determine whether a 704 monitoring behavior change is a handover or a skip. The UE can also determine the processing time for a 706 monitoring behavior change based on whether the monitoring behavior change is a handover or a skip. The UE can apply a 708 monitoring behavior change when an amount of time equal to the processing time has elapsed since the last symbol of the unscheduled DCI. Similarly, network nodes can determine when the UE should monitor and adjust future transmissions based on the last symbol of the DCI plus the processing time, depending on when the UE applies a handover or a skip. The processing time can be T_skipping or T_switching.

[0065] For example, when skipping is triggered, a (e.g., skip) command can be applied by adding T_skipping to the last symbol of the DCI. When switching is triggered, a (e.g., switch) command can be applied by adding T_switching to the last symbol of the DCI. In some implementations, when both skipping and switching are triggered using a single command, changes in behavior can be monitored by applying T_switching to the last symbol of the DCI.

[0066] In some implementations, the UE can handle undetected unscheduled DCIs in the following way: The search space configuration can ensure that sparse mode is a subset of dense mode. This allows the use of the same core set and DCI format. In these implementations, when the DCI indicates that the UE should skip or switch from dense mode to sparse mode and the UE loses the DCI, the UE may not experience power-saving gains but will not suffer from the problem of losing the PDCCH.

[0067] However, when a DCI is lost and indicates a switch from sparse mode to dense mode, many subsequent DCIs may be lost due to monitoring mode mismatch. To address this issue, a first implementation can use RRC to configure a handover timer, which, upon timer expiration, causes the UE to fall back to sparse mode, thus limiting the number of lost DCIs. Some implementations allow the UE to send ACKs to DCIs. If no ACK is sent for an unscheduled DCI, the network node can assume the unscheduled DCI is lost and send another. In some implementations, the network node can send new dense search space configurations multiple times to ensure the UE receives them correctly. In some implementations, a transition period for sending DCIs using sparse configurations can be defined.

[0068] For example, Figure 8 An example monitoring timeline 800 is shown, in which network nodes transmit DCI using a sparse configuration during transition period 802. As shown, even though the UE's monitoring behavior has switched to dense mode, network nodes continue to transmit DCI according to the sparse mode during transition period 802. Then, during the second time period 804, DCI can be transmitted according to the dense configuration.

[0069] Figure 9 The timeline shown illustrates where sparse pattern 902 is not a subset of dense pattern 904. In this implementation, sparse pattern 902 is not a subset of dense pattern 904. CoreSet, DCI format, offset, etc., may not have configuration constraints. Periodicity may exist. For example, one search space is sparse, and one search space is dense. This occurs when the total search space is configured within the constraints of the UE characteristics: 3-1 (e.g., 3 SSs per Scell) or 3-8 (e.g., 10 search spaces per Scell). In some implementations, network nodes and UEs can use activation and deactivation of different search spaces instead of switching. For example, SS1 can be 1-1, and SS2 can be 1-2. If SS1 triggers activation and deactivation of SS2 for Ultra Reliable and Low Latency Communication (URLLC) traffic, the UE can use both span and periodicity to create different SS configurations.

[0070] Figure 10 An exemplary architecture of a system 1000 for a network according to various implementations is shown. The following description is provided for an example system 1000 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0071] like Figure 10 As shown, system 1000 includes UE 1022 and UE 1020. In this example, UE 1022 and UE 1020 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device. In some embodiments, UE 1022 and / or UE 1020 may be IoT UEs, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections.

[0072] UE 1022 and UE 1020 can be configured to connect to an access node or radio access node (shown as (R)AN1008), for example, through communication coupling. In implementations, (R)AN 1008 can be an NG RAN or SG RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to (R)AN 1008 operating in an NR or SG system, and the term "E-UTRAN," etc., can refer to (R)AN 1008 operating in an LTE or 4G system. UE 1022 and UE 1020 utilize connections (or channels) (shown as connection 1004 and connection 1002, respectively), each connection including a physical communication interface or layer (discussed in further detail below).

[0073] In this example, connection 1004 and connection 1002 are air interfaces for communication coupling and are compatible with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, SG, NR, and / or any other communication protocols discussed herein. In an implementation, UE 1022 and UE 1020 may also exchange communication data directly via ProSe interface 1010. ProSe interface 1010 may alternatively be referred to as sidelink (SL) interface 110 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0074] UE 1020 is shown configured to access AP 1012 (also known as a "WLAN node", "WLAN", "WLAN terminal", "WT", etc.) via connection 1024. Connection 1024 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 1012 will include Wireless Fibre. Router. In this example, AP 1012 is connected to the Internet but not to the core network of the wireless system (described in further detail below).

[0075] (R)AN 1008 may include one or more AN nodes, such as RAN node 1014 and RAN node 1016, that implement connection 1004 and connection 1002. As used herein, the terms “access node,” “access point,” etc., can describe devices that provide radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms “NG RAN node,” etc., can refer to a RAN node (e.g., gNB) operating in an NR or SG system, while the terms “E-UT RAN node,” etc., can refer to a RAN node (e.g., eNB) operating in an LTE or 4G system 1000. According to various implementation schemes, RAN node 1014 or RAN node 1016 may be implemented as one or more of dedicated physical equipment such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity or higher bandwidth compared to macro cells.

[0076] The PDSCH carries user data and higher-layer signaling to UE 1022 and UE 1020. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 1022 and UE 1020 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 1020 within the cell) can be performed at either RAN node 1014 or RAN node 1016 based on channel quality information fed back from either UE 1022 or UE 1020. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each of UE 1022 and UE 1020.

[0077] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L = 1, 2, 4, or 8) can exist.

[0078] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0079] RAN node 1014 or RAN node 1016 can be configured to communicate with each other via interface 1030.

[0080] In implementations where system 1000 is an SG or NR system (e.g., when CN 1006 is an SGC), interface 1030 may be an Xn interface. The Xn interface is defined between two or more RAN nodes connected to the SGC (e.g., two or more gNBs, etc.), between a RAN node 1014 (e.g., a gNB) connected to the SGC and an eNB, and / or between two eNBs connected to the 5GC (e.g., CN 1006). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 1022 in connected modes (e.g., CM connection) includes functions for managing UE mobility in connected modes between one or more RAN nodes 1014 or RAN nodes 1016. Mobility support may include context transfer from the old (source) serving RAN node 1014 to the new (destination) serving RAN node 1016; and control of the user plane tunnel between the old (source) serving RAN node 1014 and the new (destination) serving RAN node 1016. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0081] (R)AN 1008 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to CN1006. CN1006 may include one or more network elements 1032 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 1022 and UE 1020) connected to CN1006 via (R)AN 1008. Components of CN1006 may be implemented in a single physical node or in separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instantiation of CN1006 may be referred to as a network slice, and a logical instantiation of a portion of CN1006 may be referred to as a network subslice. NFV architectures and infrastructure can be used to virtualize one or more network functions onto physical resources that include a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, proprietary hardware). In other words, NFV systems can be used to perform virtual or reconfigurable concrete implementations of one or more EPC components / functions.

[0082] Generally, application server 1018 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 1018 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 1022 and UE 1020 via EPC. Application server 1018 can communicate with CN 1006 through IP communication interface 1036.

[0083] In this implementation, CN 1006 may be an SGC, and (R)AN 116 may be connected to CN 1006 via NG interface 1034. In this implementation, NG interface 1034 may be divided into two parts: an NG user plane (NG-U) interface 1026, which carries traffic data between RAN node 1014 or RAN node 1016 and the UPF; and an S1 control plane (NG-C) interface 1028, which is the signaling interface between RAN node 1014 or RAN node 1016 and the AMF.

[0084] In one implementation, CN 1006 may be an SG CN, while in other implementations, CN 1006 may be an EPC. When CN 1006 is an EPC, (R)AN 116 may be connected to CN 1006 via S1 interface 1034. In one implementation, S1 interface 1034 may be divided into two parts: an S1 user plane (S1-U) interface 1026, which carries traffic data between RAN node 1014 or RAN node 1016 and the S-GW; and an S1-MME interface 1028, which is the signaling interface between RAN node 1014 or RAN node 1016 and the MME.

[0085] Figure 11 Examples of infrastructure device 1100 according to various implementations are shown. Infrastructure device 1100 may be implemented as a base station, radio head unit, RAN node, AN, application server, and / or any other element / equipment discussed herein. In other examples, infrastructure device 1100 may be in or implemented by a UE.

[0086] Infrastructure device 1100 includes application circuitry 1102, baseband circuitry 1104, one or more radio front-end modules 1106 (RFEM), memory circuitry 1108, a power management integrated circuit (shown as PMIC 1110), a power tee circuitry 1112, network controller circuitry 1114, a network interface connector 1120, satellite positioning circuitry 1116, and user interface circuitry 1118. In some embodiments, infrastructure device 1100 may include additional components, such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be individually included in more than one device for CRAN, vBBU, or other similar specific implementations. Application circuitry 1102 includes circuitry such as, but not limited to, one or more processors (processor cores), cache memory, and one or more of the following: low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I... 2The application circuit 1102 may include a C or general-purpose programmable serial interface module, a real-time clock (RTC), a timer / counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuit 1102 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure device 1100. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory equipment technology, such as those discussed herein.

[0087] The processor of application circuit 1102 may include, for example, one or more processor cores (CPU), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof.

[0088] In some embodiments, application circuitry 1102 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. These hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, programmable processing devices may be one or more field-programmable devices (FPDs), such as field-programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 1102 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as procedures, methods, functions, etc., of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 1102 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuses, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs). Baseband circuitry 1104 may be implemented, for example, as a soldered substrate comprising one or more integrated circuits, a single-package integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0089] User interface circuitry 1118 may include one or more user interfaces designed to enable a user to interact with infrastructure device 1100, or peripheral interface designed to enable peripheral components to interact with infrastructure device 1100. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light-emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio transmitter, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0090] Radio front-end module 1106 may include a millimeter-wave (mmWave) radio front-end module (RFEM) and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-millimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In another embodiment, the radio functions of both millimeter-wave and sub-millimeter-wave are implemented in the same physical radio front-end module 1106 that combines both millimeter-wave antennas and sub-millimeter-wave components.

[0091] The memory circuit 1108 may include one or more of the following: volatile memory including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM); non-volatile memory (NVM) including electrically erasable memory (often referred to as "flash memory"); phase-change random access memory (PRAM); magnetoresistive random access memory (MRAM); and may be combined with other components derived from [the present invention]. and A three-dimensional (3D) XPOINT memory. The memory circuit 1108 can be implemented as one or more of the following: a solder-in packaged integrated circuit, a socket memory module, and an insert memory card.

[0092] PMIC 1110 may include a voltage regulator, surge protector, power alarm detection circuitry, and one or more backup power sources (such as batteries or capacitors). The power alarm detection circuitry can detect one or more of a power outage (undervoltage) and a power surge (overvoltage) condition. Power tee circuit 1112 can provide electrical power drawn from the network cable to provide both power and data connectivity to infrastructure equipment 1100 using a single cable.

[0093] Network controller circuit 1114 can provide connectivity to the network using standard network interface protocols such as Ethernet, GRE-tunneled Ethernet, Multiprotocol Label Switching (MPLS)-based Ethernet, or some other suitable protocol. Network connectivity can be provided to / from infrastructure device 1100 via a physical connection via network interface connector 1120; this physical connection can be an electrical connection (typically referred to as a "copper interconnect"), an optical connection, or a wireless connection. Network controller circuit 1114 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, network controller circuit 1114 may include multiple controllers for providing connectivity to other networks using the same or different protocols. Positioning circuit 1116 includes circuitry for receiving and decoding signals transmitted / broadcast by the positioning network of a global navigation satellite system.

[0094] Figure 12 Examples of platform 1200 according to various embodiments are shown. In embodiments, computer platform 1200 may be adapted to function as a UE, application server, and / or any other element / equipment discussed herein. Platform 1200 may include any combination of the components shown in the examples. Components of platform 1200 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted in computer platform 1200, or may be implemented as components otherwise integrated within the chassis of a larger system. Figure 12 The block diagram is intended to show a high-level view of the components of the computer platform 1200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific embodiments.

[0095] Application circuit 1202 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and LDOs, interrupt controllers, serial interfaces (such as SPI), and I / O pins. 2 The application circuit 1202 may include one or more of the following: a C or general-purpose programmable serial interface module, an RTC, a timer-counter (including interval timers and watchdog timers), general-purpose I / O, a memory card controller (such as an SDMMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 1202 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on platform 1200. In some specific implementations, the memory / storage element may be on-chip memory circuitry that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0096] The processor of application circuit 1202 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, application circuit 1202 may include or may be a dedicated processor / controller for operation according to various embodiments herein.

[0097] In addition to or alternatively, application circuitry 1202 may include circuitry such as, but not limited to, one or more field-programmable devices (FPDs), such as FPGAs; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and so on. In such embodiments, the circuitry of application circuitry 1202 may include logic blocks or logic architectures, and other interconnect resources that can be programmed to perform various functions such as processes, methods, functions, etc., as discussed in the various embodiments herein. In such embodiments, the circuitry of application circuitry 1202 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), fuses, etc.)) for storing logic blocks, logic architectures, data, etc., in lookup tables (LUTs), etc.

[0098] The baseband circuit 1204 can be implemented, for example, as a solderable substrate, which includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0099] The radio front-end module 1206 may include a millimeter-wave (mmWave) radio front-end module (RFEM) and one or more sub-millimeter-wave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-millimeter-wave RFICs may be physically separated from the millimeter-wave RFEM. The RFIC may include connectors to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In another embodiment, the radio functions of both millimeter-wave and sub-millimeter-wave technologies are implemented in the same physical radio front-end module 1206 that combines both millimeter-wave and sub-millimeter-wave technologies.

[0100] The memory circuit 1208 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 1208 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SD RAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 1208 may be developed according to the Joint Electronic Equipment Engineering Committee (JEDEC) design based on low-power double data rate (LPDDR), such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 1208 may be implemented as one or more of the following: solder-in packaged integrated circuit, single-die package (SDP), dual-die package (DDP), or quad-die package (Q17P), socket memory module, dual in-line memory module (DIMM) including micro DIMM or mini DIMM, and / or soldered to a motherboard via ball grid array (BGA). In low-power implementations, the memory circuit 1208 may be an on-chip memory or register associated with application circuit 1202. To provide persistent storage for information such as data, applications, operating systems, etc., the memory circuit 1208 may include one or more mass storage devices, which may include, in particular, solid-state drives (SSDDs), hard disk drives (HDDs), miniature HDDs, resistance-changing memory, phase-change memory, holographic memory, or chemical memory. For example, the computer platform 1200 may be integrated with... and 3D XPOINT memory.

[0101] The removable memory 1226 may include equipment, circuitry, housings, ports, or sockets for coupling portable data storage devices to the platform 1200. These portable data storage devices can be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, MicroSD cards, xD picture cards, etc.), as well as USB flash drives, optical discs, external HDDs, etc.

[0102] Platform 1200 may also include interface circuitry (not shown) for connecting external devices to platform 1200. External devices connected to platform 1200 via this interface circuitry include sensor 1222 and electromechanical components (shown as EMC 1224), as well as a removable memory device coupled to removable memory 1226.

[0103] Sensor 1222 includes equipment, modules, or subsystems designed to detect events or changes in their environment and transmit information (sensor data) about the detected events to other equipment, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, and / or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture equipment (e.g., cameras or lensless aperture devices); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other similar audio capture equipment; etc.

[0104] EMC 1224 includes equipment, modules, or subsystems intended to enable platform 1200 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, EMC 1224 can be configured to generate messages / signaling and send messages / signaling to other components of platform 1200 to indicate the current state of EMC 1224. Examples of EMC 1224 include one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, propellers, pawls, clamps, hooks, and / or other similar electromechanical components. In embodiments, platform 1200 is configured to operate one or more EMC 1224s based on one or more captured events and / or commands or control signals received from a service provider and / or various clients. In some specific implementations, interface circuitry can connect platform 1200 to positioning circuitry 1216.

[0105] In some implementations, this interface circuitry can connect platform 1200 to a near-field communication circuitry (shown as NFC circuitry 1212). NFC circuitry 1212 is configured to provide contactless short-range communication based on radio frequency identification (RFID) standards, wherein a magnetic field sensor is used to enable communication between NFC circuitry 1212 and NFC-enabled devices (e.g., “NFC contacts”) external to platform 1200.

[0106] The drive circuitry 1218 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1200. The drive circuitry 1218 may include various drivers that allow other components of the platform 1200 to interact with or control various input / output (I / O) devices that may be present within or connected to the platform 1200. For example, the drive circuitry 1218 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 1200, a sensor driver for obtaining sensor readings of sensor 1222 and controlling and allowing access to sensor 1222, an EMC driver for obtaining actuator position of EMC 1224 and / or controlling and allowing access to EMC 1224, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0107] A power management integrated circuit (shown as PMIC 1210) (also referred to as a "power management circuit") manages the power supplied to various components of platform 1200. Specifically, relative to baseband circuitry 1204, PMIC 1210 controls power selection, voltage scaling, battery charging, or DC-DC conversion. PMIC 1210 is typically included when platform 1200 can be powered by battery 1214, for example, when equipment is included in a UE.

[0108] In some implementations, the PMIC 1210 can be controlled or otherwise integrated into various power-saving mechanisms of the platform 1200. For example, if the platform 1200 is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the platform 1200 can power down for short intervals to conserve power. If there is no data traffic activity for an extended period, the platform 1200 can transition to the RRC_Idle state, where the equipment is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 1200 enters a very low-power state and performs paging, where the equipment periodically wakes up again to listen to the network and then power down again. The platform 1200 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the equipment to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the equipment is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0109] Battery 1214 can power platform 1200, but in some examples, platform 1200 may be mounted in a fixed location and may have a power source coupled to the grid. Battery 1214 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, battery 1214 may be a typical lead-acid automotive battery.

[0110] In some implementations, battery 1214 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in platform 1200 to track the state of charge (SoCh) of battery 1214.

[0111] A power block coupled to the power grid or other power source can be coupled to the BMS to charge battery 1214. In some examples, a wireless power receiver can replace the power block to wirelessly acquire power, for example, via a loop antenna in computer platform 1200. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuitry chosen may depend on the size of battery 1214 and therefore on the required current. Charging can be performed using aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Radio Power Alliance, or the Rezence charging standard published by the Radio Power Alliance.

[0112] User interface circuitry 1220 includes various input / output (I / O) devices present within or connected to platform 1200, and includes one or more user interfaces designed to enable user interaction with platform 1200 and / or peripheral component interfaces designed to enable interaction with peripheral components of platform 1200. User interface circuitry 1220 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual device for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, particularly one or more simple visual outputs / indicators, such as binary status indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of platform 1200. The output device circuitry may also include speakers or other audio transmitting devices, printers, etc. In some embodiments, sensor 1222 may be used as input device circuitry (e.g., image capture devices, motion capture devices, etc.) and one or more EMCs may be used as output device circuitry (e.g., actuators for providing haptic feedback, etc.). In another example, NFC circuitry may be included for reading electronic tags and / or connecting to another NFC-enabled device, the NFC circuitry including an NFC controller and processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0113] Although not shown, components of platform 1200 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be a proprietary bus / IX, for example, used in a SoC-based system. Other bus / IX systems, such as I... 2 Interfaces include C-type interface, SPI interface, point-to-point interface, and power bus, etc.

[0114] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0115] Example Section

[0116] The following examples relate to other implementation schemes.

[0117] Example 1 is a method for a user equipment (UE), the method comprising: receiving a downlink scheduling grant including downlink control information (DCI), the DCI indicating that the UE should apply a monitoring behavior change; determining a processing time for the monitoring behavior change; sending an acknowledgment (ACK) message to indicate receipt of the DCI; and applying the monitoring behavior change when an amount of time equal to the processing time has elapsed after sending the ACK message.

[0118] Example 2 is the method according to Example 1, wherein the change in monitoring behavior includes switching or skipping.

[0119] Example 3 is the method according to Example 1, further comprising: generating and sending a negative acknowledgment (NACK) message when the UE fails to correctly decode the DCI or when the UE does not decode the physical downlink shared channel (PDSCH); and receiving a retransmission DCI indicating that the UE should apply the skip or the handover.

[0120] Example 4 is the method according to Example 1, wherein the processing time depends on whether the change in the monitoring behavior is a switch or a skip.

[0121] Example 5 is the method according to Example 4, wherein if the change in monitoring behavior is a switch, the processing time includes the time for decoding the DCI and configuring a separate search space.

[0122] Example 6 is the method according to Example 4, wherein if the monitoring behavior change is skipped, the processing time includes the time for decoding the DCI and applying the skip command.

[0123] Example 7 is the method according to Example 1, wherein the processing time includes the time for decoding the DCI and configuring a separate search space, regardless of whether the monitoring behavior change is a switch or a skip.

[0124] Example 8 is the method according to Example 1, wherein the processing time includes the processing time for the network node to process the ACK message.

[0125] Example 9 is the method according to Example 1, wherein the processing time is equivalent to drx-HARQ-RTT-TimerDL.

[0126] Example 10 is the method according to Example 1, wherein determining the processing time includes: determining a time period corresponding to one or more of the following: a first time corresponding to decoding the DCI and configuring a separate search space; a second time corresponding to decoding the DCI and applying a skip command; a third time corresponding to the network node processing the ACK message; a fourth time corresponding to drx-HARQ-RTT-TimerDL; and identifying a maximum value of the time period, wherein the maximum value is the processing time.

[0127] Example 11 is a method for a (User Equipment) UE, the method comprising: receiving an uplink scheduling grant including downlink control information (DCI), the DCI instructing the UE to apply skip or handover to change monitoring behavior; determining whether discontinuous reception mode (DRX) is configured; determining a reference point for the skip or handover based on whether DRX is configured; determining a processing time for the skip or handover; and applying the skip or handover when an amount of time equal to the processing time has elapsed after the reference point.

[0128] Example 12 is the method according to Example 11, wherein when DRX is configured, if drx-RetransmissionTimerUL is less than a threshold, the reference point is after drx-RetransmissionTimerUL expires, and if drx-RetransmissionTimerUL is greater than the threshold, the reference point is after Physical Uplink Shared Channel (PUSCH) transmission.

[0129] Example 13 is the method according to Example 11, wherein the processing time corresponds to one of the following: a first time corresponding to decoding the DCI and configuring a separate search space; a second time corresponding to decoding the DCI and applying a skip command; a third time corresponding to the network node processing the PUSCH message; and a fourth time corresponding to drx-HARQ-RTT-TimerUL.

[0130] Example 14 is the method according to Example 13, wherein the processing time is the maximum value of the first time, the second time, the third time, and the fourth time.

[0131] Example 15 is the method according to Example 11, wherein when DRX is not configured, the reference point is after the PUSCH transmission.

[0132] Example 16 is a method for a (User Equipment) UE, the method comprising: receiving unscheduled downlink control information (DCI), the unscheduled DCI instructing the UE to apply a monitoring behavior change; determining whether the monitoring behavior change is a handover or a skip; determining a processing time for the monitoring behavior change based on whether the monitoring behavior change is a handover or a skip; and applying the monitoring behavior change when an amount of time equal to the processing time has elapsed after the last symbol of the unscheduled DCI.

[0133] Example 17 is the method according to Example 16, wherein if the change in monitoring behavior is a switch, the processing time includes the time for decoding the DCI and configuring a separate search space.

[0134] Example 18 is the method according to Example 16, wherein if the monitoring behavior change is skipped, the processing time includes the time for decoding the DCI and applying the skip command.

[0135] Example 19 is the method according to Example 16, wherein if both skipping and switching are triggered, the processing time includes the time for decoding the DCI and configuring a separate search space.

[0136] Example 20 is the method according to Example 16, further comprising switching from sparse mode to dense mode based on a timer if the UE does not detect the non-scheduled DCI.

[0137] Example 1C may include an apparatus comprising means for performing one or more elements of any of the methods described or associated with any of the above embodiments or any other methods or processes described herein.

[0138] Example 2C may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein as described or associated with any of the above embodiments.

[0139] Example 3C may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing any of the methods described or associated with any of the above embodiments or any other methods or processes described herein.

[0140] Example 4C may include any method, technique, or process, or part or component thereof, that is described in or related to any of the above examples.

[0141] Embodiment 5C may include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0142] Example 6C may include the signal or part or component thereof that is described or associated with any of the above examples.

[0143] Example 7C may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages or parts or components thereof described or associated with any of the above examples, or otherwise described in this disclosure.

[0144] Embodiment 8C may include a data-encoded signal or part or component thereof that is in or related to any of the above embodiments, or otherwise described in this disclosure.

[0145] Embodiment 9C may include signals or portions or components thereof encoded as datagrams, packets, frames, segments, PDUs or messages as described or associated with any of the above embodiments, or otherwise described in this disclosure.

[0146] Example 10C may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0147] Example 11C may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform any of the methods, techniques, or processes or portions thereof described or associated with any of the above embodiments.

[0148] Example 12C may include signals in a wireless network as shown and described herein.

[0149] Example 13C may include methods for communicating in a wireless network as shown and described herein.

[0150] Example 14C may include a system for providing wireless communication as shown and described herein.

[0151] Example 15C may include apparatus for providing wireless communication as shown and described herein.

[0152] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0153] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic equipment). The computer system may include hardware components, including specific logical components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0154] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in another implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0155] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0156] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for a user equipment (UE), the method comprising: Receive downlink scheduling authorization including downlink control information (DCI), the DCI instructing the UE to apply monitoring behavior changes; The processing time for the change in the monitored behavior is determined, wherein the processing time includes the time for the UE to process the handover or skip and the time for the network node to enable the handover or skip; Send an ACK message to indicate that the DCI has been received; as well as The monitoring behavior changes when an amount of time equal to the processing time has elapsed after the ACK message is sent.

2. The method of claim 1, wherein the change in monitoring behavior includes switching or skipping.

3. The method according to claim 1, further comprising: When the UE fails to correctly decode the DCI or when the UE fails to decode the Physical Downlink Shared Channel (PDSCH), a Negative Acknowledgment (NACK) message is generated and sent. as well as The received instruction indicates that the UE should apply the skip or handover retransmission DCI.

4. The method of claim 1, wherein the processing time depends on whether the change in the monitoring behavior is a switch or a skip.

5. The method of claim 4, wherein if the change in monitoring behavior is a switch, the processing time includes the time for decoding the DCI and configuring a separate search space.

6. The method of claim 4, wherein if the monitoring behavior change is skipped, the processing time includes the time for decoding the DCI and applying the skip command.

7. The method of claim 1, wherein the processing time includes the time for decoding the DCI and configuring a separate search space, regardless of whether the monitoring behavior change is a toggle or a skip.

8. The method according to claim 1, wherein the processing time includes the processing time for the network node to process the ACK message.

9. The method according to claim 1, wherein the processing time is equivalent to drx-HARQ-RTT-TimerDL.

10. The method of claim 1, wherein determining the processing time comprises: Determine the time period corresponding to one or more of the following: This corresponds to the first time when the DCI is decoded and a separate search space is configured; This corresponds to the second time when the DCI is decoded and the skip command is applied; This corresponds to the third time when the network node processes the ACK message; Corresponding to the fourth time in drx-HARQ-RTT-TimerDL; and Identify the maximum value of the time period, wherein the maximum value is the processing time.

11. A method for a user equipment (UE), the method comprising: Receive uplink scheduling authorization including downlink control information (DCI), the DCI instructing the UE to apply skip or handover to change the monitoring behavior; Determine if discontinuous reception mode (DRX) is configured; The reference point for skipping or switching is determined based on whether DRX is configured. The processing time for the skip or handover is determined, wherein the processing time includes the time for the UE to process the handover or skip and the time for the network node to enable the handover or skip; as well as When an amount of time equal to the processing time has elapsed after the reference point, the skip or switch is applied.

12. The method of claim 11, wherein when the DRX is configured, If drx-RetransmissionTimerUL is less than the threshold, then the reference point is after drx-RetransmissionTimerUL has expired, and If the drx-RetransmissionTimerUL is greater than the threshold, then the reference point is after the physical uplink shared channel (PUSCH) transmission.

13. The method of claim 11, wherein the processing time corresponds to one of the following: This corresponds to the first time when the DCI is decoded and a separate search space is configured; This corresponds to the second time when the DCI is decoded and the skip command is applied; This corresponds to the third time when a network node processes a PUSCH message; This corresponds to the fourth time in drx-HARQ-RTT-TimerUL.

14. The method of claim 13, wherein the processing time is the maximum value of the first time, the second time, the third time, and the fourth time.

15. The method of claim 11, wherein when DRX is not configured, the reference point is after the PUSCH transmission.

16. A method for a user equipment (UE), the method comprising: Receive unscheduled downlink control information (DCI), the unscheduled DCI instructing the UE to apply a monitoring behavior change; Determine whether the change in monitoring behavior should be switched on or skipped; The processing time for the change in monitoring behavior is determined based on whether the change is a switch or a skip, wherein the processing time includes the time for the UE to process the switch or skip and the time for the network node to enable the switch or skip; as well as The monitoring behavior change is applied when an amount of time equal to the processing time has elapsed since the last symbol of the non-scheduled DCI.

17. The method of claim 16, wherein if the change in monitoring behavior is a switch, the processing time includes the time for decoding the DCI and configuring a separate search space.

18. The method of claim 16, wherein if the monitoring behavior change is skipped, the processing time includes the time for decoding the DCI and applying the skip command.

19. The method of claim 16, wherein if both skipping and switching are triggered, the processing time includes the time for decoding the DCI and configuring a separate search space.

20. The method of claim 16, further comprising switching from sparse mode to dense mode based on a timer if the UE does not detect the unscheduled DCI.

Images