Switching between different scheduling latency assumptions

Abstract

Disclosed herein are systems and methods for transitioning between different scheduling delay hypotheses. In some embodiments, a method performed by a wireless device includes, during a first time slot, monitoring a downlink control channel that includes scheduling downlink control information for transmissions of the wireless device using an assumption of a first scheduling delay that is equal to or exceeds a first value. The method also includes determining that the wireless device is to switch from the assumption of the first scheduling delay to an assumption of a second scheduling delay that is equal to or exceeds a second value, the second value being less than the first value. The method also includes, during one or more later time slots occurring after the first time slot, monitoring a downlink control channel that includes scheduling downlink control information for transmissions of the wireless device using an assumption of the second scheduling delay.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 738,742, filed on September 28, 2018, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a wireless communication system, and in particular, to cross-slot scheduling in a wireless communication system. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) fifth generation (5G) New Radio (NR) includes services such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and machine-type communications (MTC). Each of these services has different technical requirements. For example, the general requirements of eMBB are high data rates with medium latency and medium coverage, while URLLC services require low latency and high reliability transmission while being more accepting of medium data rates.

[0005] One of the solutions for low-latency data transmission is a shorter transmission time interval. In addition to transmission in time slots, NR also includes micro-slot transmission to reduce latency. A micro-slot can include any number of orthogonal frequency division multiplexing (OFDM) symbols from 1 to 14. The concept of time slots and micro-slots is not specific to a particular service, which means that micro-slots can be used for eMBB, URLLC or other services. Figure 1 Exemplary radio resources in NR are shown.

[0006] User Equipment (UE) power consumption is an important metric that needs to be enhanced. Generally speaking, monitoring the Physical Downlink Control Channel (PDCCH) in Long Term Evolution (LTE) based on a discontinuous reception (DRX) setting from the Long Term Evolution (LTE) field log can cost a lot of power. If a similar DRX setting with traffic modeling is used, NR is similar because the UE needs to perform blind detection in its configured control resource set (CORESET) to identify whether there is a PDCCH sent to the UE. Techniques that can reduce unnecessary PDCCH monitoring or enable the UE to go to sleep or wake up only when needed can be advantageous.

[0007] In 3GPP 5G NR, a UE may be configured with up to four carrier bandwidth parts (BWPs) in the downlink, with a single downlink carrier bandwidth part being active at a given time. A UE may be configured with up to four carrier BWPs in the uplink, with a single uplink carrier BWP being active at a given time. If the UE is configured with a supplementary uplink, the UE may additionally be configured with up to four carrier BWPs in the supplementary uplink, with a single supplementary uplink carrier BWP being active at a given time.

[0008] For a given parameter set μ i The carrier BWP defines a set of consecutive physical resource blocks (PRBs), which are numbered from 0 to Where i is the index of the carrier BWP. A resource block (RB) is defined as twelve (12) consecutive subcarriers in the frequency domain.

[0009] Multiple OFDM parameter sets μ are supported in NR, as given in Table 1 below, where the subcarrier spacing Δf and cyclic prefix for the carrier BWP are configured by different higher layer parameters for downlink (DL) and uplink (UL), respectively.

[0010]

[0011] Table 1: Supported transmission parameter sets

[0012] A downlink physical channel corresponds to a set of resource elements that carry information originating from higher layers. The downlink physical channels include the Physical Downlink Shared Channel (PDSCH), the Physical Broadcast Channel (PBCH) and the PDCCH. The PDSCH is the main physical channel used for unicast downlink data transmission, but is also used for the transmission of Random Access Responses (RARs), specific system information blocks and paging information. The PBCH carries basic system information required for the UE to access the network. The PDCCH is used to send Downlink Control Information (DCI), mainly scheduling decisions, which are required for the reception of the PDSCH and for uplink scheduling grants to enable transmissions on the Physical Uplink Shared Channel (PUSCH).

[0013] An uplink physical channel corresponds to a set of resource elements that carry information originating from higher layers. Uplink physical channels include PUSCH, Physical Uplink Control Channel (PUCCH) and Physical Random Access Channel (PRACH). PUSCH is the uplink counterpart of PDSCH. The UE uses PUCCH to send uplink control information, including hybrid automatic repeat request (HARQ) acknowledgment, channel state information report, etc. PRACH is used for random access preamble transmission.

[0014] The following shows an example content of DL DCI 1_0 (ie, DCI format 1_0). The cyclic redundancy check (CRC) is scrambled by the cell radio network temporary identifier (C-RNTI) or the configured scheduling radio network temporary identifier (CS-RNTI). The example content of DL DCI 1_0 is:

[0015] Identifier of DCI format—1 bit: The value of this bit field is always set to 1, indicating the DL DCI format;

[0016] Frequency domain resource allocation— Bit: is the size of the active DL BWP, provided that DCI format 1_0 is monitored in the UE-specific search space and satisfies: the total number of different DCI sizes configured to be monitored for the cell does not exceed four (4) and the total number of different DCI sizes with C-RNTI configured to be monitored for the cell does not exceed three (3); otherwise, Is the size of CORESET 0.

[0017] • Time domain resource allocation—four (4) bits, as defined in subclause 5.1.2.1 of 3GPP Technical Specification (TS) 38.214;

[0018] Virtual Resource Block (VRB) to PRB mapping—one (1) bit, which is according to Table 7.3.1.1.2-33 of 3GPP TS 38.212;

[0019] Modulation and coding scheme—(five) 5 bits, as defined in subclause 5.1.3 of 3GPP TS 38.214;

[0020] New data indicator—(one) 1 bit;

[0021] Redundancy version—(two) 2 bits, as defined in Table 7.3.1.1.1-2 of 3GPP TS 38.212;

[0022] HARQ process number - (four) 4 bits;

[0023] Downlink Allocation Index (DAI) - (two) 2 bits, as defined in subclause 9.1.3 of 3GPP TS 38.213, as a counter DAI;

[0024] • Transmit Power Control (TPC) command for scheduled PUCCH—(two) 2 bits, as defined in subclause 7.2.1 of 3GPP TS 38.213;

[0025] PUCCH resource indicator—(three) 3 bits, as defined in subclause 9.2.3 of 3GPP TS 38.213; and

[0026] • PDSCH to HARQ_feedback timing indicator—(three) 3 bits, as defined in subclause 9.2.3 of 3GPP TS 38.213.

[0027] DRX (such as Figure 2 The simplified DRX operation shown in FIG. 1 enables the UE to transition to a low power state when the UE does not need to receive any transmissions from the base station. There is an "onDuration" in which the UE is in an awake state and monitors the PDCCH. If the UE does not detect the PDCCH, the inactivity timer starts. The UE continues to monitor the PDCCH until a valid PDCCH addressed to the UE is received or the inactivity timer expires. If the UE receives a valid PDCCH, the UE extends the inactivity timer and continues to monitor the PDCCH. If the inactivity timer expires, the UE can stop receiving transmissions from the base station (e.g., without controlling monitoring) until the DRX cycle ends. Typically, DRX parameters are configured by radio resource control (RRC). In addition to those parameters discussed above, RRC also configures some other parameters, such as parameters related to the round trip time (RTT), parameters related to HARQ, etc. The onDuration and the duration when the inactivity timer is running are also commonly referred to as "active time."

[0028] In general, the following terms are often associated with DRX operation:

[0029] • Active Time: Active time refers to the time associated with DRX operation, during which the Medium Access Control (MAC) entity monitors the PDCCH.

[0030] DRX cycle: The DRX cycle is the periodic repetition of onDuration followed by a possible period of inactivity (see Figure 2 ).

[0031] • Inactivity timer: The inactivity timer generally refers to the number of consecutive PDCCH subframes / timeslots that the UE waits before transitioning to the sleep state after the subframe / timeslot in which the PDCCH indicates an initial UL, DL or sidelink user data transmission for the MAC entity.

[0032] MAC entity: The MAC entity is a medium access control entity, and each configured cell group (eg, primary cell group and secondary cell group) has one MAC entity.

[0033] The DRX function is configured by RRC, which usually works at a slower scale than the MAC or physical (PHY) layer. Therefore, DRX parameter settings, etc. cannot be fully adaptively changed through RRC configuration, especially when the UE has mixed traffic types. Summary of the invention

[0034] Disclosed herein are systems and methods for transitioning between two operating modes at a wireless device, wherein the wireless device uses different scheduling delay assumptions. Embodiments of methods performed by a wireless device and corresponding embodiments of the wireless device are disclosed. In some embodiments, a method performed by a wireless device includes monitoring a downlink control channel including downlink control information for scheduling transmissions for the wireless device using an assumption of a first scheduling delay during a first time slot. The first scheduling delay is equal to or exceeds a first value. The method also includes determining that the wireless device is to switch from the assumption of the first scheduling delay to an assumption of a second scheduling delay. The second scheduling delay is equal to or exceeds a second value, wherein the second value is less than the first value. The method also includes monitoring a downlink control channel including downlink control information for scheduling transmissions for the wireless device using an assumption of the second scheduling delay during one or more later time slots occurring after the first time slot. In this manner, the wireless device can save power, for example, by monitoring a downlink control channel using an assumption of a first scheduling delay (e.g., assuming only cross-time slot scheduling) until the wireless device determines that it should transition to an assumption of a second scheduling delay (e.g., assuming possible same-time slot scheduling).

[0035] In some embodiments, monitoring a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay comprises: monitoring, in a particular search space, the downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay. In some embodiments, monitoring a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the second scheduling delay comprises: monitoring, in the particular search space, the downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the second scheduling delay.

[0036] In some embodiments, monitoring a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay comprises: monitoring the downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay in a first search space. Additionally, monitoring the downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the second scheduling delay comprises: monitoring the downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the second scheduling delay in a second search space different from the first search space. In some embodiments, the first search space is associated with a first bandwidth and the second search space is associated with a second bandwidth, wherein the first bandwidth is less than the second bandwidth.

[0037] In some embodiments, determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay comprises: determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay in response to an explicit indication or an implicit indication from a network node. In some embodiments, the explicit indication or implicit indication is an explicit indication included in downlink control information from the network node.

[0038] In some embodiments, during the first time slot, monitoring a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay comprises: during the first time slot, when the wireless device is operating in a first power mode associated with the first scheduling delay, monitoring a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay. Determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay comprises: transitioning from the first power mode to a second power mode associated with the second scheduling delay. In some embodiments, transitioning from the first power mode to the second power mode associated with the second scheduling delay comprises: transitioning from the first power mode to the second power mode associated with the second scheduling delay in response to an indication included in downlink control information from a network node. In some embodiments, transitioning from the first power mode to the second power mode associated with the second scheduling delay comprises: transitioning from the first power mode to the second power mode associated with the second scheduling delay after sending a hybrid automatic repeat request HARQ acknowledgment ACK for a transmission scheduled by the downlink control information included in the downlink control channel detected in the first time slot. In some embodiments, transitioning from the first power mode to a second power mode associated with the second scheduling delay comprises: transitioning from the first power mode to the second power mode associated with the second scheduling delay after expiration of a timer. In some embodiments, expiration of the timer is dependent on not receiving a downlink control channel in a configured number of monitoring opportunities.

[0039] In some embodiments, determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay includes: after sending a HARQ ACK for a transmission scheduled by downlink control information included in a downlink control channel detected in the first time slot, determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption having the second scheduling delay.

[0040] In some embodiments, determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay comprises: determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay after expiration of a timer. In some embodiments, expiration of the timer is dependent on not receiving a downlink control channel for a configured number of monitoring opportunities.

[0041] In some embodiments, the first power mode is a power saving mode (PSM) and the second power mode is a non-PSM, or the first power mode is a non-PSM and the second power mode is a PSM.

[0042] In some embodiments, the first value is a value corresponding to a value greater than or equal to one time slot. In some embodiments, the second value is a value corresponding to a value of zero time slots. In some embodiments, the first value is a value determined based on a wireless device indication that depends only on a physical downlink shared channel parameter set, or depends on a physical downlink control channel parameter set and a physical downlink shared channel parameter set. In some embodiments, the method further comprises: operating in a low power mode during the first time slot when the downlink control channel is not monitored based on an assumption that a downlink schedule detected on the downlink control channel in the first time slot schedules downlink transmissions to the wireless device with the first scheduling delay exceeding the first value. In some embodiments, monitoring the downlink control channel during the first time slot comprises: monitoring the downlink control channel at a beginning portion of the first time slot, and the method further comprises: operating in a low power mode during the first time slot starting from an end of the beginning portion of the first time slot where the downlink control channel is monitored based on the assumption of the first scheduling delay.

[0043] In some embodiments, determining that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay comprises determining that a downlink control channel including downlink control information scheduling transmissions for the wireless device is detected during the first time slot. In some embodiments, the one or more later time slots comprise a second time slot immediately following the first time slot. In some embodiments, the one or more later time slots occur after a time slot in which the wireless device sends a HARQ response for a transmission scheduled by the downlink control information included in the downlink control channel detected in the first time slot. In some other embodiments, the one or more later time slots occur after a time slot in which the wireless device sends a HARQ ACK for a transmission scheduled by the downlink control information included in the downlink control channel detected in the first time slot. In some other embodiments, the one or more later time slots occur after a time slot in which the wireless device detects another downlink control channel including downlink control information scheduling transmissions for the wireless device according to the second scheduling delay. In some embodiments, the method further comprises: monitoring a downlink control channel including downlink control information scheduled for transmission of the wireless device using the first scheduling delay assumption in one or more subsequent time slots after the first time slot and before the one or more later time slots. In some other embodiments, the first time slot is during a discontinuous reception, DRX, on duration, and the one or more later time slots are all time slots that occur later than the first time slot in the DRX on duration. In some other embodiments, the first time slot is during a discontinuous reception, DRX, on duration, and the one or more later time slots are a predefined number of time slots that occur later than the first time slot in the DRX on duration. In some embodiments, the method further comprises: switching to monitoring a downlink control channel including downlink control information scheduled for transmission of the wireless device using the first scheduling delay assumption or using both the first scheduling delay assumption and the second scheduling delay assumption.

[0044] In some embodiments, a wireless device includes a radio front-end circuit and a processing circuit associated with the radio front-end circuit. The processing circuit is configured to cause the wireless device to monitor a downlink control channel including downlink control information scheduled for transmission of the wireless device using an assumption of a first scheduling delay during a first time slot, wherein the first scheduling delay is equal to or exceeds a first value. The processing circuit is also configured to cause the wireless device to determine that the wireless device is to switch from the assumption of the first scheduling delay to an assumption of a second scheduling delay, wherein the second scheduling delay is equal to or exceeds a second value and the second value is less than the first value. The processing circuit is also configured to cause the wireless device to monitor the downlink control channel including downlink control information scheduled for transmission of the wireless device using the assumption of the second scheduling delay during one or more later time slots occurring after the first time slot.

[0045] In some embodiments, in order for the wireless device to determine that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay, the processing circuit is further configured to cause the wireless device to: determine that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay in response to an explicit indication or an implicit indication from a network node. In some embodiments, the explicit indication or the implicit indication is an explicit indication included in downlink control information from the network node.

[0046] In some embodiments, the processing circuit is further configured to cause the wireless device to: during the first time slot, when the wireless device is operating in a first power mode associated with the first scheduling delay, monitor a downlink control channel including downlink control information scheduled for transmission by the wireless device using an assumption of the first scheduling delay. In addition, in order for the wireless device to determine that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay, the processing circuit is further configured to cause the wireless device to: transition from the first power mode to a second power mode associated with the second scheduling delay. In some embodiments, the processing circuit is further configured to cause the wireless device to: transition from the first power mode to the second power mode in response to an indication included in downlink control information from a network node. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0048] Figure 1Exemplary radio resources in New Radio (NR) are shown;

[0049] Figure 2 An example of discontinuous reception (DRX) operation is shown;

[0050] Figure 3 is a block diagram illustrating scheduling possibilities with same-slot scheduling and example user equipment (UE) activities;

[0051] Figure 4 is a block diagram illustrating scheduling possibilities with cross-slot scheduling and example UE activities;

[0052] Figure 5 is a flow chart illustrating the operation of a UE according to some embodiments of the present disclosure;

[0053] Figure 6 Examples of different search spaces (denoted as search spaces X and Y) in which a physical downlink control channel (PDCCH) may be transmitted are shown;

[0054] Figure 7 An example is shown in which search space X only allows cross-slot scheduling and search space Y only allows same-slot scheduling according to some embodiments of the present disclosure.

[0055] Figure 8 is a flowchart illustrating the operation of a UE switching between different working modes using different assumed scheduling delays (i.e., using only cross-slot scheduling or using same-slot scheduling) according to some embodiments of the present disclosure;

[0056] Fig. 9 is a flow chart illustrating operation of a UE in accordance with some embodiments of the present disclosure in which the UE transitions between different power modes using different scheduling delays;

[0057] Fig.10 An example according to an embodiment of the present disclosure is shown, wherein first the search space X only allows cross-slot scheduling (K0>0), the UE receives a physical downlink shared channel (PDSCH) scheduled by downlink control information (DCI) included in a PDCCH detected in the search space X, the UE sends a hybrid automatic repeat request (HARQ) feedback, and then the UE is allowed to be scheduled with same-slot scheduling (K0=0);

[0058] Fig.11 is a flow chart illustrating operation of a UE in which the UE transitions between different power modes using different scheduling delays according to some embodiments of the present disclosure;

[0059] Fig.12 and 13An example with both cross-slot scheduling and limited same-slot scheduling that can reduce power consumption according to some embodiments of the present disclosure is shown;

[0060] Fig.14 The operation of a UE and a network node (e.g., a base station) according to some embodiments of the present disclosure is illustrated, in which the UE provides UE capability information or a UE indication to the network node;

[0061] Fig.15 An example wireless network is shown in which embodiments of the present disclosure may be implemented;

[0062] Fig.16 An embodiment of a UE according to various aspects described herein is shown;

[0063] Fig.17 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0064] Fig.18 A communication system is shown in which embodiments of the present disclosure may be implemented, wherein the communication system comprises a telecommunications network including an access network and a core network;

[0065] Fig.19 Shown according to Fig.18 Example implementations of embodiments of UE, base station and host computer; and

[0066] Fig. 20 , 21 , 22 and 23 are flowcharts illustrating methods implemented in a communication system according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0067] The embodiments set forth below represent information that enables those skilled in the art to practice the embodiments, and illustrate the best mode of practicing the embodiments. When reading the following description according to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize the application of these concepts not particularly mentioned herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0068] Generally, unless different meanings are clearly given and / or different meanings are implied in the context of using the term, all terms used in this article will be interpreted according to their common meanings in the relevant technical field. Unless clearly stated, all references to one / an / the element, device, assembly, part, step, etc. should be publicly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. Unless a step is explicitly described as being after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0069] Certain challenges currently exist, for example, with respect to enabling low power operation of user equipment (UE) in cellular communication networks, such as New Radio (NR). For example, currently in NR, a UE is configured by a single high-layer configuration, by means of which the UE may be scheduled to receive a unicast physical downlink shared channel (PDSCH) using either same-slot scheduling (e.g., minimum K0=0) or cross-slot scheduling (e.g., minimum K0>0). Note that "K0" is a parameter that defines a scheduling delay between downlink control information (DCI) that schedules a PDSCH transmission to a UE and the PDSCH transmission. In this case:

[0070] a) The UE must support same-slot scheduling, which means that the UE must decode the Physical Downlink Control Channel (PDCCH) and determine if there is an associated PDSCH for the UE in the same slot. This reduces the opportunity to reduce power consumption because the UE needs to collect potential PDSCH samples and / or operate in a bandwidth mode suitable for potential PDSCH reception; or

[0071] b) The UE must always receive data in cross-slot scheduling, which means increased latency due to scheduling delays.

[0072] The adaptation between same-slot scheduling and cross-slot scheduling is currently implemented via higher layers such as Radio Resource Control (RRC), which may require a lot of overhead and is quite slow. Therefore, such adaptation is undesirable, resulting in reduced throughput and increased delay.

[0073] Certain aspects of the present disclosure and embodiments described herein can provide solutions to these or other challenges.

[0074] In some embodiments, a method performed by a wireless device includes monitoring a downlink control channel for downlink scheduling information, wherein any received downlink schedule may schedule a downlink transmission to occur after a first scheduling delay. The method also includes receiving first downlink scheduling information for a first data transmission according to the first scheduling delay; receiving the first data transmission at the scheduled time; and monitoring the downlink control channel for the downlink scheduling information, wherein any received downlink schedule may schedule the downlink transmission to occur after a second scheduling delay, and the second scheduling delay is less than the first scheduling delay.

[0075] Specific embodiments include systems and methods that support a first group of K0 values ​​for receiving DCI associated with a PDSCH in a first search space and a second group of K0 values ​​for receiving DCI associated with a PDSCH in a first search space or a second search space. According to the first K0 value of the group, the base station uses the first search space to send DCI including scheduling data to the UE. The scheduling data schedules the PDSCH to the UE, wherein the scheduling delay of the scheduled PDSCH is consistent with the first group of K0 values. The UE monitors the first search space and thereby receives the DCI. The UE receives the scheduled PDSCH from the base station according to the scheduling data, and sends feedback (e.g., hybrid automatic repeat request (HARQ) feedback) to the scheduled PDSCH to the base station. The UE also monitors the DCI in the first or second search space supporting the second group of K0 values ​​to receive data via the DCI. Relative to the case where the second group of K0 values ​​are used to receive data, the first group of K0 values ​​can enable the UE to receive data with reduced power consumption. Only when the feedback for the scheduled data is HARQ acknowledgement (ACK), the UE uses the second set of K0 values ​​to monitor DCI in the first or second search space.The first set of K0 values ​​may represent cross-slot scheduling, while the second set of K0 values ​​may represent same-slot scheduling.

[0076] In general, specific embodiments include: turning on / off delayed PDCCH to PDSCH scheduling based on data arrival for the UE; configuring at least two search spaces for the UE, and the two search spaces have different minimum K0 values ​​(where K0 is the PDCCH to PDSCH scheduling delay), and dynamically switching PDCCH monitoring between these search spaces; and configuring multiple sets of different K0 values ​​for the same search space, and switching between the multiple sets of different K0 values ​​based on implicit or explicit dynamic indications.

[0077] Various embodiments that address one or more of the problems disclosed herein are proposed herein. Certain embodiments may provide one or more of the following technical advantages. For example, certain embodiments reduce UE power consumption by fast, robust, and physical layer-based transitions between a) cross-slot scheduling and b) same-slot scheduling for downlink data scheduling. For sample collection, power consumption reduction may take the form of reduced radio frequency (RF) on time, or for PDCCH monitoring, power consumption reduction may take the form of lower bandwidth (BW) operation, provided that PDSCH may have a wider BW than PDCCH. Details of these embodiments are provided below.

[0078] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0079] Figure 3 is a block diagram showing scheduling possibilities with simultaneous slot scheduling and example UE activities. The UE is configured to monitor PDCCH in multiple time slots n, n+1, n+2, ... . The PDCCH may use PDSCH in the same time slot to allocate data, i.e. K0 may be 0. K0 is generally considered to be the delay between the PDCCH and the start of the PDSCH allocated by the PDCCH. In this example, PDSCH is scheduled for the UE in time slot n+1, but there is no PDSCH scheduled for the UE in time slots n, n+2 and n+3.

[0080] Now consider an example UE activity, where the UE receiver must be "on" (or in a high power consumption state) to receive PDCCH symbols in slot n. Because the UE receiver does not know in advance whether there is a PDSCH allocated by the PDCCH in slot n, the UE receiver needs to continue buffering symbols (or continue to be in an on state) until the UE completes PDCCH monitoring (i.e., decodes all possible PDCCH candidates for slot n). If at the end of PDCCH monitoring the UE determines that there is no allocated PDSCH in the slot (e.g., as shown for slots n, n+2, and n+3), the UE can transition to an off state (or low power or power saving mode (PSM)) for the remainder of the slot. If the UE determines that there is an allocated PDSCH in the slot (e.g., as shown for slot n+1), the UE remains on for the remainder of the slot to buffer all symbols of the expected PDSCH therein.

[0081] Figure 4 is a block diagram showing scheduling possibilities with cross-time slot scheduling and example UE activities. Figure 3In contrast, the scheduling mode is restricted so that PDCCH can only allocate PDSCH using a delay of one slot or even more slots (i.e. K0>1). Note that in these examples K0 is rounded to a slot level value, but more generally the scheduling delay can be expressed in terms of a symbol including slots or some other time unit (e.g. ms or microseconds). Similar to Figure 3 , in slot n+1 there is data for the UE scheduled via the PDCCH. Due to the K0 delay, the data itself is scheduled in slot n+2. In the other slots, there is no PDSCH allocated by the PDCCH. Now considering an example UE activity for this setup, consider slot n+1, the UE needs to be in the on state to receive the PDCCH at the beginning of the slot. For the rest of the slot, the UE can be in the off state because whether PDCCH is allocated for slot n+1 is signaled via PDCCH in slot n, and the UE has already decoded the PDCCH in slot n. However, for all symbols in the slot where PDSCH is allocated (for example in slot n+2), the UE needs to be in the on state because there is data allocated to the UE, assuming in this example that the PDSCH spans the entire slot.

[0082] Figure 3 and 4 The comparison of UE activity in shows that when scheduling is delayed (i.e. K0 is greater than the UE's PDCCH decoding delay), the UE is able to stay turned off for a longer time. This is beneficial for saving UE power consumption. However, delayed scheduling increases latency (e.g. in the above example, PDSCH needs to be delayed from slot n+1 to n+2). This situation needs to be avoided as much as possible.

[0083] Additionally, a relevant UE power saving opportunity for the UE is to receive the PDCCH using a relatively narrower BW receiver, where the BW can be configured based on the search space. However, when the UE is configured for same-slot PDSCH reception, lower BW operation is not feasible because the typical transition time to enter wider BW operation may be about 0.5-1 milliseconds (ms), i.e., at the time slot duration level. When operating in K0>0 mode, the UE may use a BW adaptation mechanism for additional power saving.

[0084] Certain embodiments of the present disclosure dynamically adapt the delayed scheduling described above to achieve UE power saving without unnecessarily increasing scheduling delays.

[0085] Certain embodiments of the present disclosure are based on turning on / off delayed PDCCH to PDSCH scheduling for data arrival at a UE. Figure 5As shown (where optional steps are represented by dashed boxes), in one example, the UE monitors the PDCCH in a first time slot, where it is assumed that the PDCCH can schedule the PDSCH using a first scheduling delay that always exceeds a first value (e.g., minimum K0>1 time slot) (step 500). In other words, during the first time slot, the UE monitors the PDCCH including the DCI for scheduling the PDSCH for the UE, where the UE assumes that the PDCCH in the first time slot can schedule the PDSCH using the first scheduling delay. This assumption enables the UE to take specific actions, such as monitoring in a specific search space allocated for the first scheduling delay and / or entering a low power state to save power. For example, if the first scheduling delay is always greater than or equal to one (1) time slot so that the UE can adopt cross-slot scheduling, the UE monitors the PDCCH in the beginning part of the first time slot (e.g., the first one or several OFDM symbols), and then based on the assumption of cross-slot scheduling, can enter a low power state (off state) for the remaining part of the first time slot (e.g., see Figure 4 time slot n). As described above, this is because the UE does not need to continue buffering PDSCH symbols while processing PDCCH symbols because the UE can assume that the PDCCH received in the first time slot (if any) uses cross-slot scheduling (i.e., schedules the PDSCH for a future time slot). If the UE does not detect a PDCCH that allocates data for the UE to the PDSCH in the first time slot (e.g., using DL-SCH) (step 502, no), then during a later time slot (i.e., a time slot later than the first time slot), the UE continues to monitor the PDCCH, assuming that the PDCCH can schedule the PDSCH using a first scheduling delay (step 504). If the UE detects a PDCCH that allocates data for the UE to the PDSCH in the first time slot (step 502, yes), then the UE monitors the PDCCH in later time slots, assuming that the PDCCH in these later time slots can schedule the PDSCH using a second scheduling delay that always exceeds a second value, where the second value is less than the first value (e.g., K0=0 time slots) (step 506). In other words, during the later time slot, the UE monitors the PDCCH including the DCI for scheduling the PDSCH for the UE, wherein the UE assumes that the PDCCH in the later time slot can schedule the PDSCH using the second scheduling delay. For example, if the second scheduling delay is always greater than or equal to 0 time slots so that the UE cannot assume cross-time slot scheduling (i.e., assuming that there may be simultaneous slot scheduling), the UE monitors the PDCCH at the beginning of the first time slot (e.g., the first one or several orthogonal frequency division multiplexing (OFDM) symbols), and then based on the assumption of possible simultaneous slot scheduling, keeps the PDCCH in the on state to buffer the PDSCH symbols when processing the PDCCH symbols (e.g., see Figure 3Note that the decision in step 502 is also referred to herein as a way of determining whether the UE is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay.

[0086] In step 506, the UE monitors the PDCCH in later time slots, assuming that the PDCCH in these later time slots can schedule the PDSCH using the second scheduling delay. In the above example, these "later time slots" can be time slots that are later than the first time slot and also later than the time slot in which the UE sends a HARQ-ACK response for the PDSCH allocated by the PDCCH in the first time slot. In this case, the UE continues to monitor the PDCCH using the first scheduling delay until the UE sends a HARQ-ACK / negative acknowledgement (NACK) for the PDSCH received by the UE (step 508), and then the UE switches to monitoring the PDCCH using the second scheduling delay (step 506). The advantage of this option is that the HARQ-ACK / NACK serves as a confirmation to the base station (e.g., NR base station (gNB)) that schedules the UE that the base station can now send the PDCCH using the second scheduling delay. The UE may alternatively continue to monitor the PDCCH using the first scheduling delay until the UE sends an ACK as a HARQ response (step 508), and switch to monitoring using the second scheduling delay only after the ACK is sent (i.e., the UE does not switch if a NACK is sent as a HARQ response) (step 506).

[0087] In some cases, such as where the ACK sent by the UE may be lost or erroneously detected at the base station, the UE may instead continue to monitor the PDCCH with both the first and second scheduling delays, even after sending the ACK and until the UE detects one or more PDCCHs from the base station (step 510). In the new PDCCH DCI, if the base station schedules the UE using the second scheduling delay, then at a later opportunity, the UE may monitor the PDCCH with the second scheduling delay (step 506). In the new PDCCH DCI, if the enhanced or evolved Node B (eNB) still schedules the UE using the delay corresponding to the first scheduling delay, then it is most likely that the confirmation ACK sent by the UE is lost or erroneously detected, i.e., retransmission is required accordingly.

[0088] If the UE is configured with DRX, the UE may continue to monitor the PDCCH with the second scheduling delay as long as the UE is in active time, or until the UE returns to DRX. In a subsequent "on duration", the UE falls back to monitoring the PDCCH with the first scheduling delay (step 512).

[0089] If the UE is configured with DRX, after detecting the PDSCH for the first time and sending the HARQ-ACK, the UE may switch to the second scheduling delay and continue to monitor using the second scheduling delay until no PDSCH is received in P consecutive time slots (step 506), after which the UE switches back to monitoring using the first scheduling delay (step 512). The value P may be less than a parameter Q, which represents the number of time slots in which no PDSCH is received, after which the UE returns to DRX.

[0090] Alternatively, after switching to the second scheduling delay in step 506, in some later time slots, the UE may be configured to monitor both delay value sets (step 512). If the UE detects that the first scheduling delay set is used again, the UE switches back to monitoring using the first scheduling delay.

[0091] If the UE is configured to receive an explicit go-to-sleep indication from the network, the UE may continue to monitor the PDCCH with the second scheduling delay until a go-to-sleep indication is received from the network, and each time the UE monitors the PDCCH after receiving the go-to-sleep indication, the UE may fall back to monitoring the PDCCH with the first scheduling delay (step 512).

[0092] In one method related to the above example, taking a first scheduling delay to monitor the PDCCH may correspond to monitoring the PDCCH associated with the first search space, and taking a second scheduling delay to monitor the PDCCH may correspond to monitoring the PDCCH associated with the second search space. In another method related to the above example, taking the first scheduling delay or the second scheduling delay to monitor the PDCCH may correspond to monitoring the PDCCH associated with the same search space.

[0093] When a UE is monitoring a PDCCH that can allocate (or schedule) data for the UE for a PDSCH (e.g., using a downlink shared channel (DL-SCH)), at the same time, the UE can also monitor a PDCCH that can allocate broadcast data for the PDSCH (e.g., using a broadcast channel (BCH), a paging channel (PCH)). In order to monitor a PDCCH that can allocate data for the UE for the PDSCH, the UE can use a specific radio network temporary identifier (RNTI), such as a cell RNTI (C-RNTI). In order to monitor a PDCCH that can allocate broadcast data, the UE can use a paging RNTI (P-RNTI) / random access RNTI (RA-RNTI) / system information RNTI (SI-RNTI) for receiving data related to paging, random access channel (RACH) and system information, respectively. The UE can adopt a fixed or pre-configured scheduling delay to monitor the PDCCH that can allocate broadcast data for the PDSCH (i.e., the PDCCH monitoring related to the broadcast data does not have to be affected by the switching in the PDCCH monitoring related to receiving UE-specific data).

[0094] Certain embodiments include multiple different sets of K0 values ​​for different search spaces. For example, a UE may be configured with a different set of K0 values ​​for different search spaces. A search space may be a UE-specific search space only. Then, if the UE only searches the first search space, the UE may save power if the first set of configured K0 values ​​is allowed for downlink data scheduled from the first search space. If the UE only searches the second search space, the UE may save different amounts of power if a different set of K0 values ​​is allowed for downlink data scheduled from the second search space.

[0095] Figure 6 Examples of search spaces X and Y and PDCCH are shown. Figure 7 An example is shown in which search space X only allows cross-slot scheduling, while search space Y only allows same-slot scheduling. Figure 6 In FIG. 5 , UE power consumption is shown to be similar between a PDCCH monitoring-only duration (or timeslot) and a duration (or timeslot) with PDCCH monitoring and PDSCH reception, but in practice the power levels may be different for these two cases.

[0096] In the above case, if the UE only looks for DCI in search space X (i.e., monitors PDCCH containing DCI only in search space X), the UE can go to sleep immediately after buffering PDCCH in a given time slot, because the UE knows that PDSCH is expected to be scheduled only in the next time slot. Because the UE can fully determine this in advance (e.g., it is not necessary to decode PDCCH and decide to turn off or keep it on), the opportunity to save power can be relatively high.

[0097] In the above situation, if the UE only searches for DCI in search space Y (i.e., only monitors PDCCH containing DCI in search space Y), the UE may not be able to go to sleep immediately after buffering PDCCH in a given timeslot, because the UE must decode the PDCCH and then determine whether to turn off or stay on, and therefore the chance of saving power can be relatively low.

[0098] Alternatively, in some time slots, there may be both search spaces X and Y. The UE first checks search space X. If DCI is found (or all DCI have been found), the UE will stop and not check search space Y. The UE then switches back to using the delay value associated with search space X. In later time slots (where there may be both search spaces X and Y), if the UE finds DCI in search space Y, the UE switches back to using the delay value associated with search space Y. Figure 8 An example of the process is shown. As shown, if a particular time slot has both search space X and search space Y (step 800, yes), the UE monitors search space X to find a PDCCH including a DCI for scheduling a PDSCH for the UE (step 802). If such a PDCCH is detected (step 804, yes), the UE uses a first scheduling delay associated with search space X (step 806). In other words, the UE operates on the assumption that the PDCCH in the later time slot includes a DCI with a first scheduling delay. If no PDCCH is detected in search space X (step 804, no), the UE monitors search space Y to find a PDCCH including a DCI for scheduling a PDSCH for the UE (step 808). If such a PDCCH is detected in search space Y (step 810, yes), the UE uses a second scheduling delay associated with search space X (step 812). In other words, the UE operates on the assumption that the PDCCH in the later time slot includes a DCI with a second scheduling delay. In this way, the UE can switch between cross-slot scheduling and same-slot scheduling operation (eg, between PSM in which only cross-slot scheduling is used and non-PSM in which same-slot scheduling may be used).

[0099] In certain embodiments, the UE may start looking for DCI only in search space X. If the UE is scheduled with PDSCH in search space X, the UE may report certain feedback (e.g., HARQ-ACK), and the UE may start looking for DCI in search space X (and Y) or only in search space Y.

[0100] In some embodiments, the UE is configured with at least two search spaces (search space X and search space Y), and the two search spaces have different minimum K0 values ​​(for PDCCH to PDSCH scheduling). When in PSM, the UE looks for DCI in search space X. In an alternative, when not in PSM, the UE looks for DCI in search space X and search space Y. In another alternative, when not in PSM, the UE looks for DCI in search space Y. Fig. 9 is a flow chart illustrating the operation of the UE in this regard. As shown, the UE enters a first power mode (e.g., PSM) (step 900). When in the first power mode, the UE monitors the PDCCH in a time slot in a first search space (e.g., search space X for PSM) associated with the first power mode (step 902). The first search space is associated with a first minimum K0 value. As described above, the UE assumes that the PDSCH scheduled by the DCI in the PDCCH detected in the first search space has a scheduling delay equal to or greater than the first minimum K0 value, and as described above, the UE can take specific actions that affect power consumption based on this assumption. At some time thereafter, the UE enters (e.g., switches to) a second power mode (e.g., non-PSM) (step 904). The second search space is associated with a second minimum K0 value that is different from the first minimum K0 value. As described below, the UE enters the second power mode after determining that it should transition from the first power mode to the second power mode (e.g., based on any one or any combination of various criteria, as described below). In this way, the UE determines that it is switching from the assumption of a first scheduling delay associated with the first power mode and a second scheduling delay associated with the second power mode. When in the second power mode, the UE monitors the PDCCH in a time slot in a second search space associated with the second power mode (e.g., search space Y for non-PSM) (step 906). As described above, the UE assumes that the PDSCH scheduled by the DCI in the PDCCH detected in the second search space has a scheduling delay equal to or greater than the second minimum K0 value, and as described above, the UE can take specific actions that affect power consumption based on this assumption.

[0101] The UE may be expected to transition from PSM to non-PSM mode (e.g., in steps 900 or 904) based on one or more of the following criteria:

[0102] UE detects the scheduled PDCCH in search space X,

[0103] o The scheduling PDCCH may be for the first transmission of a transport block and / or may even be applied to HARQ retransmissions of a transport block;

[0104] UE sends ACK for PDSCH scheduled by PDCCH in search space X;

[0105] The UE receives a message, such as a DCI command, for transitioning from PSM to normal mode scheduled via search space X;

[0106] After the current DRX cycle ends;

[0107] At the start of Onduration.

[0108] The transition from non-PSM to PSM (e.g., in steps 900 or 904) may be based on:

[0109] • A timer, where the expiry of the timer may depend on the absence of PDCCH reception in a configured number of monitoring occasions. The number of monitoring occasions (after which the transition from non-PSM to PSM is made) may be lower than the number of monitoring slots without PDSCH (after which the UE falls back to DRX).

[0110] • The UE receives a message, such as a DCI command, scheduled via search space Y for transitioning from non-PSM to PSM mode.

[0111] After the current DRX cycle ends or when Onduration starts.

[0112] Starting with connected mode DRX (CDRX) ON in PSM mode is also an option.

[0113] The search space X may be configured to facilitate one or more of the following:

[0114] Lower BW (bandwidth) than search space Y

[0115] Fewer blind decodes than search space Y

[0116] Fewer symbols than the search space Y

[0117] However, search space X and search space Y may also have the same BW, BD or number of symbol parameters.

[0118] Search space X and search space Y may be mapped to the same core resource set (CORESET). Search spaces X and Y may be mapped to different CORESETs. Search space X and search space Y may both be UE-specific search spaces. Search space X is associated with a first set of K0 values, which in one embodiment include values ​​K0>0. Search space Y is associated with a second set of K0 values, which in one embodiment are limited to values ​​K0=0.

[0119] A specific embodiment configures multiple sets of different K0 values ​​for the same search space and transitions based on a dynamic indication. For example, a UE may be configured with a set of different K0 values ​​for the same search space. The search space may be a UE-specific search space only. When the UE first starts looking for DCI only in the search space, the UE is allowed to schedule with the first set of configured K0 values ​​only for downlink data scheduled from the search space. If the UE receives downlink data and sends HARQ feedback (e.g., ACK), the UE is allowed to schedule with the second set of configured K0 values ​​only for downlink data scheduled from the search space.

[0120] Fig.10 An example is shown, where first the search space X only allows cross-slot scheduling (K0>0), the UE receives PDSCH and sends HARQ feedback, and then the UE is allowed to be scheduled with same-slot scheduling (K0=0).

[0121] In the above case, if the UE initially uses the first set of configured K0 values ​​to look up DCI, the UE can go to sleep immediately after buffering the PDCCH in a given timeslot, because the UE knows that the PDSCH is expected to be scheduled only in the next timeslot. Because the UE can fully determine this in advance (e.g., it is not necessary to decode the PDCCH and decide to turn off or keep it on), the opportunity to save power can be relatively high.

[0122] Depending on the base station (e.g., gNB) scheduling decision (e.g., which may be based on traffic / delay requirements / load), once the UE is allowed to use the second set of K0 values, the UE may not be able to go to sleep immediately after buffering the PDCCH in a given timeslot, because the UE must decode the PDCCH and then determine whether to turn off or stay on. Therefore, there may also be an opportunity for energy savings if the UE can complete data transmission and reception faster and return to monitoring only the PDCCH associated with the first set of K0 values.

[0123] In some embodiments, the UE may start looking for DCI in search space X using the first set of K0 values. The UE may be scheduled with PDSCH in search space X, the UE may report specific feedback (e.g., HARQ-ACK), and the UE may start looking for DCI in search space X and may be allowed to use the second set of K0 values.

[0124] In some embodiments, when in PSM mode, the UE uses a first set of K0 values ​​to look up search space X, and when in non-PSM mode, the UE uses a second set of K0 values ​​to look up search space X. The number of monitoring occasions (after which the transition from non-PSM to PSM is made) may be lower than the number of monitoring slots without PDSCH (after which the UE falls back to DRX). Fig.11 is a flow chart illustrating the operation of the UE in this regard. As shown, the UE enters a first power mode (e.g., PSM) (step 1100). While in the first power mode, the UE monitors the PDCCH in a time slot in a specific search space (step 1102). The first power mode is associated with a first minimum K0 value (or, for example, a first set of K0 values ​​defined by the first minimum K0 value). As described above, the UE assumes that the PDSCH scheduled by the DCI in the PDCCH detected in the search space has a scheduling delay equal to or greater than the first minimum K0 value (or, for example, a K0 value in the first set of K0 values ​​defined by the first minimum K0 value), and as described above, the UE can take specific actions that affect power consumption based on this assumption. At some time thereafter, the UE enters (e.g., switches to) a second power mode (e.g., non-PSM) (step 1104). The second power mode is associated with a second minimum K0 value (or, for example, a second set of K0 values ​​defined by the second minimum K0 value) that is different from the first minimum K0 value. As described below, the UE enters the second power mode after determining that it should transition from the first power mode to the second power mode (e.g., based on any one or any combination of various criteria, as described below). In this manner, the UE determines that it is switching from an assumption of a first scheduling delay associated with the first power mode and a second scheduling delay associated with the second power mode. While in the second power mode, the UE monitors the PDCCH in a time slot in the same search space (step 1106). As described above, the UE assumes that the PDSCH scheduled by the DCI in the PDCCH detected in the search space has a scheduling delay equal to or greater than the second minimum K0 value (or, for example, one of the second set of K0 values ​​defined by the second minimum K0 value), and as described above, the UE can take specific actions that affect power consumption based on this assumption.

[0125] The UE may be expected to transition from non-PSM mode to PSM based on one or more of the following criteria:

[0126] UE sends ACK for PDSCH scheduled by PDCCH in synchronization signal (SS) X;

[0127] The UE receives a message scheduled via SSX for transitioning from PSM to normal mode;

[0128] After the current DRX cycle ends;

[0129] At the start of Onduration.

[0130] The transition from non-PSM to PSM may be based on a timer, and the expiration of the timer may depend on the absence of a PDCCH received in a configured number of monitoring occasions. Additional transition criteria may also be used, such as for Figure 7 Describe the guidelines.

[0131] In a particular embodiment, search space X is a UE-specific search space. When in PSM mode, search space X is associated with a first set of K0 values. When in non-PSM mode, search space X is associated with a second set of K0 values.

[0132] When in PSM mode, a first set of K0 values ​​is used to perform PDCCH transmissions according to search space X. When in non-PSM mode, a second set of K0 values ​​is used to perform PDCCH transmissions according to search space X.

[0133] Search space X is associated with a first set of K0 values, and the UE sends an ACK for the DCI in the search space, then the UE looks for the DCI in the search space, and then the search space X is associated with a second set of K0 values. In other words, in some embodiments, the UE monitors the PDCCH in search space X using the assumption of the first set of K0 values. After detecting the PDCCH and receiving the corresponding PDSCH scheduled by the DCI contained in the PDCCH, the UE sends an ACK. Thereafter, the UE monitors the PDCCH in a later time slot in the same search space X using the assumption of the second set of K0 values.

[0134] The UE looks for DCI in search space X and applies only the first set of K0 values, and the UE sends an ACK for the DCI in the search space, and then the UE looks for DCI in the search space and may apply the first and second sets of K0 values ​​for search space X. In other words, in some embodiments, the UE monitors the PDCCH in search space X using the assumption of the first set of K0 values. After detecting the PDCCH and receiving the corresponding PDSCH scheduled by the DCI contained in the PDCCH, the UE sends an ACK. Thereafter, the UE monitors the PDCCH in the later time slot in the same search space X using the assumption of both the first and second sets of K0 values.

[0135] The first set of K0 values ​​may be K0>0. The second set of K0 values ​​may include K0=0. The first set of K0 values ​​may be K0>X, where X may be UE capability signaling, with potential dependency on parameter sets, etc. The second set of K0 values ​​may include K0<=X, where X may be UE capability signaling, with potential dependency on parameter sets, etc.

[0136] The above embodiments can be applied to all scheduling cases. Additionally, PDSCH can be scheduled in symbols where PDCCH is monitored without the above K0>1 restriction when K0>1 is used for other positions of PDSCH relative to PDCCH. Additionally, PDSCH can be scheduled in symbols adjacent to symbols where PDCCH is monitored without the above K0>1 restriction when K0>1 is used for other positions of PDSCH relative to PDCCH. This allows scheduling of low data rate or time-narrow PDSCH without significant additional power consumption, as used for both cases. Fig.12 and 13 shown.

[0137] For the above embodiments, in some scenarios, the UE-side auxiliary information may be beneficial to the network. For example, the UE may describe the UE's preference for a set of preferred K0 values ​​according to a power saving profile.

[0138] The minimum k0 capability that can achieve power savings;

[0139] The preferred K0 value indicated by the UE;

[0140] The slot length indicator value (SLIV) indicated by the UE;

[0141] UE indicated SLIV for Type A PDSCH mapping and / or first CORESET and / or search space configuration;

[0142] • UE indicated SLIV for Type B PDSCH mapping and / or first CORESET and / or search space configuration.

[0143] The K0 value may generally be indicated by SLIV. In a specific case, if the first SLIV set is configured with a first CORESET / search space configuration, the UE may indicate that it may reduce power consumption by value A, and if the second SLIV set is configured with a second CORESET / search space configuration, the UE may reduce power consumption by value B. The UE may indicate multiple such sets, which the gNB may utilize when making its scheduling decisions.

[0144] The UE may indicate a preferred span (consecutive symbols in which the PDCCH is monitored) and information related to the SLIV associated with the preferred span. For example, the UE may indicate that it may prefer one or more of the following configurations to reduce power consumption:

[0145] • First configuration: span is two (2) symbols; monitoring period is fourteen (14) symbols; and SLIV corresponds to K0=0, where the length of the PDSCH allocation = two (2) symbols, and corresponds to K0>1, where the length of the PDSCH is between two (2) and fourteen (14) symbols.

[0146] • Second configuration: the span is one (1) symbol; the monitoring period is fourteen (14) symbols; and SLIV corresponds to K0>1, where the length of the PDSCH is between two (2) and fourteen (14) symbols.

[0147] · Third configuration: the span is three (3) symbols; the monitoring period is fourteen (14) symbols; and SLIV corresponds to K0=1, where the length of the PDSCH allocation = four (4) symbols, and corresponds to K0>1, where the length of the PDSCH is between two (2) and fourteen (14) symbols.

[0148] The UE may also indicate a priority order or additional information, which the network can use to make appropriate scheduling choices taking into account UE power consumption characteristics.

[0149] In a particular embodiment, the first and second sets of K0 values ​​are determined based on a UE indication. The UE indication may include capability signaling indicating a first K0 value threshold corresponding to a first power saving profile and a second K0 value threshold corresponding to the first power saving profile. The capability signaling indication may depend on the supported parameter sets (subcarrier spacing (SCS)), with dependency on a PDSCH parameter set only, or dependency on a PDCCH and PDSCH parameter set.

[0150] in this regard, Fig.14 Operations of a UE and a network node (e.g., a base station) according to some embodiments described herein are shown, wherein the UE provides UE capability information or a UE indication to the network node. As shown, the UE provides UE-side information (e.g., UE capability information or UE indication) to the network node (step 1400). Examples of types of information that can be provided from the UE to the network node are described above and may apply here. According to the above embodiments, the network node uses the UE-side information, for example, to make appropriate scheduling decisions for the UE (step 1402).

[0151] When an uplink grant is sent to a UE in PSM, the UE may remain in PSM mode or may also be configured to switch to non-PSM (eg, according to the embodiments described above for downlink scheduling).

[0152] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Fig.15 For simplicity, Fig.15 The wireless network of FIG. 1 depicts only network 1506, network nodes 1560 and 1560b, and WD 1510, 1510b, and 1510c. In practice, the wireless network may further include any additional units suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, network node 1560 and wireless device (WD) 1510 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0153] A wireless network may include and / or be connected to any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standards; wireless local area network (WLAN) standards, such as IEEE 802.11 standards; and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, and / or ZigBee standards.

[0154] Network 1506 may include one or more backhaul networks, core networks, Internet Protocol (IP) networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks that enable communications between devices.

[0155] The network node 1560 and the WD 1510 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections).

[0156] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, eNBs, and gNBs). Base stations can be classified based on the amount of coverage provided by the base stations (or in other words, their transmit power levels), and then they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station (e.g., a centralized digital unit and / or a remote radio unit (RRU) (sometimes also referred to as a remote radio head (RRH))). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs)), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile positioning centers (E-SMLCs)), and / or minimization of drive tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network by a wireless device or to provide a certain service to a wireless device that has accessed a wireless network.

[0157] exist Fig.15In the embodiment, the network node 1560 includes a processing circuit 1570, a device readable medium 1580, an interface 1590, an auxiliary device 1584, a power supply 1586, a power supply circuit 1587, and an antenna 1562. Fig.15 The network node 1560 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 1560 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium 1580 may include multiple separate hard drives and multiple random access memory (RAM) modules).

[0158] Similarly, the network node 1560 may include multiple physically separated components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In some cases where the network node 1560 includes multiple separate components (e.g., a BTS and a BSC component), one or more separate components may be shared between multiple network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, in some cases, each unique Node B and RNC pair may be considered as a single separate network node. In some embodiments, the network node 1560 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device-readable media 1580 for different RATs), while some components may be reused (e.g., the same antenna 1562 may be shared by the RAT). The network node 1560 may also include multiple groups of various example components for different wireless technologies (e.g., GSM, wideband code division multiple access (WCDMA), LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into the network node 1560. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1560 .

[0159] The processing circuit 1570 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 1570 may include: processing information obtained by the processing circuit 1570, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information; and making a determination as a result of the processing.

[0160] The processing circuit 1570 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide network node 1560 functionality, either alone or in combination with other network node 1560 components (e.g., device readable medium 1580). For example, the processing circuit 1570 may execute instructions stored in the device readable medium 1580 or in a memory within the processing circuit 1570. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 1570 may include a system on a chip (SOC).

[0161] In some embodiments, processing circuitry 1570 may include one or more of RF transceiver circuitry 1572 and baseband processing circuitry 1574. In some embodiments, RF transceiver circuitry 1572 and baseband processing circuitry 1574 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 1572 and baseband processing circuitry 1574 may be on the same chip or chipset, board, or unit.

[0162] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit 1570 executing instructions stored on device-readable medium 1580 or a memory within processing circuit 1570. In alternative embodiments, some or all of the functions may be provided by processing circuit 1570 without the need to execute instructions stored on a separate or separate device-readable medium, such as in a hardwired manner. In any of these embodiments, processing circuit 1570 can be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to processing circuit 1570 or other components of network node 1560, but are enjoyed by network node 1560 as a whole and / or generally by end users and wireless networks.

[0163] Device readable medium 1580 may include any form of volatile or non-volatile computer readable memory, including but not limited to permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data, and / or instructions that can be used by processing circuit 1570. Device readable medium 1580 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by processing circuit 1570 and utilized by network node 1560. Device readable medium 1580 may be used to store any computations performed by processing circuit 1570 and / or any data received via interface 1590. In some embodiments, processing circuit 1570 and device readable medium 1580 may be considered integrated.

[0164] Interface 1590 is used in wired or wireless communication of signaling and / or data between network node 1560, network 1506 and / or WD 1510. As shown, interface 1590 includes port / terminal 1594 to send and receive data from network 1506, for example, via wired connection to network 1506. Interface 1590 also includes radio front-end circuit 1592 that can be coupled to antenna 1562 or as a part of antenna 1562 in some embodiments. Radio front-end circuit 1592 includes filter 1598 and amplifier 1596. Radio front-end circuit 1592 can be connected to antenna 1562 and processing circuit 1570. Radio front-end circuit can be configured to adjust the signal transmitted between antenna 1562 and processing circuit 1570. Radio front-end circuit 1592 can receive digital data that will be sent to other network nodes or WD via wireless connection. Radio front-end circuit 1592 can use the combination of filter 1598 and / or amplifier 1596 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1562. Similarly, when receiving data, antenna 1562 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1592. The digital data may be passed to processing circuit 1570. In other embodiments, the interface may include different components and / or different combinations of components.

[0165] In some alternative embodiments, the network node 1560 may not include a separate radio front end circuit 1592, but rather, the processing circuit 1570 may include the radio front end circuit and may be connected to the antenna 1562 without the separate radio front end circuit 1592. Similarly, in some embodiments, all or part of the RF transceiver circuit 1572 may be considered part of the interface 1590. In other embodiments, the interface 1590 may include one or more ports or terminals 1594, the radio front end circuit 1592, and the RF transceiver circuit 1572 as part of a radio unit (not shown), and the interface 1590 may communicate with the baseband processing circuit 1574, which is part of the digital unit (not shown).

[0166] Antenna 1562 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1562 may be coupled to radio front-end circuit 1592 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1562 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 gigahertz (GHz) and 66GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as multiple input multiple output (MIMO). In some embodiments, antenna 1562 may be separated from network node 1560 and may be connected to network node 1560 via an interface or port.

[0167] Antenna 1562, interface 1590 and / or processing circuit 1570 may be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal may be received from a wireless device, another network node and / or any other network device. Similarly, antenna 1562, interface 1590 and / or processing circuit 1570 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a wireless device, another network node and / or any other network device.

[0168] The power circuit 1587 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 1560 for performing the functions described herein. The power circuit 1587 may receive power from the power supply 1586. The power supply 1586 and / or the power circuit 1587 may be configured to provide power to the various components of the network node 1560 in a form suitable for the various components (e.g., at the voltage and current level required by each corresponding component). The power supply 1586 may be included in the power circuit 1587 and / or the network node 1560 or outside it. For example, the network node 1560 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source provides power to the power circuit 1587. As another example, the power supply 1586 may include a power source in the form of a battery or battery pack connected to the power circuit 1587 or integrated therein. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.

[0169] Alternative embodiments of network node 1560 may include Fig.15 Additional components beyond those shown, which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1560 may include a user interface device to allow information to be input into the network node 1560 and to allow information to be output from the network node 1560. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node 1560.

[0170] As used herein, WD refers to a device that can, is configured, is arranged and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD can be used interchangeably with UE in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, WD may be configured to send and / or receive information without direct human interaction. For example, WD may be designed to send information to the network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop computer built-in devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle installation wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing the third generation partnership project (3GPP) standard for side link communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband IoT (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0171] As shown, wireless device 1510 includes antenna 1511, interface 1514, processing circuit 1520, device readable medium 1530, user interface device 1532, auxiliary device 1534, power supply 1536 and power supply circuit 1537. WD 1510 can include multiple groups of one or more of the components shown for different wireless technologies supported by WD 1510 (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX or Bluetooth wireless technology, to name a few). These wireless technologies can be integrated into the same or different chips or chipsets as other components in WD 1510.

[0172] Antenna 1511 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 1514. In some alternative embodiments, antenna 1511 may be separated from WD 1510 and may be connected to WD 1510 via an interface or port. Antenna 1511, interface 1514 and / or processing circuit 1520 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 1511 may be considered as an interface.

[0173] As shown, the interface 1514 includes a radio front-end circuit 1512 and an antenna 1511. The radio front-end circuit 1512 includes one or more filters 1518 and an amplifier 1516. The radio front-end circuit 1512 is connected to the antenna 1511 and the processing circuit 1520 and is configured to adjust the signal transmitted between the antenna 1511 and the processing circuit 1520. The radio front-end circuit 1512 may be coupled to the antenna 1511 or as part of the antenna 1511. In some embodiments, the WD 1510 may not include a separate radio front-end circuit 1512; instead, the processing circuit 1520 may include a radio front-end circuit and may be connected to the antenna 1511. Similarly, in some embodiments, part or all of the RF transceiver circuit 1522 may be considered as part of the interface 1514. The radio front-end circuit 1512 may receive digital data sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1512 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1518 and / or amplifiers 1516. The radio signal may then be transmitted via antenna 1511. Similarly, when receiving data, antenna 1511 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1512. The digital data may be passed to processing circuit 1520. In other embodiments, the interface may include different components and / or different combinations of components.

[0174] Processing circuit 1520 may include a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide WD 1510 functionality alone or in combination with other WD 1510 components (e.g., device readable medium 1530). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuit 1520 may execute instructions stored in device readable medium 1530 or in a memory within processing circuit 1520 to provide functionality disclosed herein.

[0175] As shown, the processing circuit 1520 includes one or more of the RF transceiver circuit 1522, the baseband processing circuit 1524, and the application processing circuit 1526. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1520 of the WD 1510 may include a SOC. In some embodiments, the RF transceiver circuit 1522, the baseband processing circuit 1524, and the application processing circuit 1526 may be on a separate chip or chipset. In alternative embodiments, part or all of the baseband processing circuit 1524 and the application processing circuit 1526 may be combined into one chip or chipset, and the RF transceiver circuit 1522 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 1522 and the baseband processing circuit 1524 may be on the same chip or chipset, and the application processing circuit 1526 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuit 1522, baseband processing circuit 1524, and application processing circuit 1526 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 1522 may be part of interface 1514. RF transceiver circuit 1522 may condition RF signals for processing circuit 1520.

[0176] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 1520 that executes instructions stored on a device-readable medium 1530 (which may be a computer-readable storage medium in some embodiments). In alternative embodiments, some or all of the functions may be provided by the processing circuit 1520 without the need to execute instructions stored on a separate or separate device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit 1520 can be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit 1520 or other components of the WD 1510, but are enjoyed by the WD 1510 as a whole and / or generally by end users and wireless networks.

[0177] Processing circuit 1520 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by processing circuit 1520 may include: processing information obtained by processing circuit 1520, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 1510, and / or performing one or more operations based on the obtained information or the converted information; and making determinations as a result of the processing.

[0178] Device readable medium 1530 is operable to store computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions executable by processing circuit 1520. Device readable medium 1530 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that may be used by processing circuit 1520. In some embodiments, processing circuit 1520 and device readable medium 1530 may be considered integrated.

[0179] The user interface device 1532 may provide a component that allows a human user to interact with the WD 1510. This interaction may have a variety of forms, such as visual, auditory, tactile, etc. The user interface device 1532 may be operable to generate output to the user and allow the user to provide input to the WD 1510. The type of interaction may vary depending on the type of user interface device 1532 installed in the WD 1510. For example, if the WD 1510 is a smart phone, the interaction may be via a touch screen; if the WD 1510 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1532 may include input interfaces, devices, and circuits and output interfaces, devices, and circuits. The user interface device 1532 is configured to allow information to be input to the WD 1510, and is connected to the processing circuit 1520 to allow the processing circuit 1520 to process the input information. The user interface device 1532 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 1532 is also configured to allow information to be output from the WD 1510, and to allow the processing circuit 1520 to output information from the WD 1510. The user interface device 1532 may include, for example, a speaker, a display, a vibration circuit, a universal serial bus (USB) port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 1532, the WD 1510 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0180] Auxiliary device 1534 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for measuring for various purposes, interfaces for other communication types such as wired communications, etc. The inclusion and type of components of auxiliary device 1534 may vary depending on the embodiment and / or scenario.

[0181] In some embodiments, power supply 1536 can take the form of a battery or battery pack. Other types of power supplies can also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. WD 1510 may also include a power circuit 1537 for delivering power from power supply 1536 to various parts of WD 1510, which require power from power supply 1536 to perform any function described or indicated herein. In some embodiments, power circuit 1537 may include a power management circuit. Power circuit 1537 may additionally or alternatively be operable to receive power from an external power source. In this case, WD 1510 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cord). In some embodiments, power circuit 1537 may also be operable to deliver power from an external power source to power supply 1536. This can be used, for example, to charge power supply 1536. Power circuit 1537 may perform any formatting, conversion, or other modification of power from power supply 1536 to make the power suitable for the corresponding components of WD 1510 to which the power is provided.

[0182] Fig.16 An embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE1600 may be any UE identified by 3GPP, including a NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.16 As shown, UE 1600 is an example of a WD that is configured to communicate according to one or more communication standards promulgated by 3GPP (e.g., 3GPP's GSM, UMTS, LTE and / or 5G standards). As mentioned above, the terms WD and UE can be used interchangeably. Therefore, although Fig.16 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0183] exist Fig.16In the embodiment, UE 1600 includes a processing circuit 1601, which is operatively coupled to an input / output interface 1605, an RF interface 1609, a network connection interface 1611, a memory 1615 (including RAM 1617, ROM 1619, and storage medium 1621, etc.), a communication subsystem 1631, a power supply 1613 and / or any other components or any combination thereof. The storage medium 1621 includes an operating system 1623, an application 1625, and data 1627. In other embodiments, the storage medium 1621 may include other similar types of information. Some UEs may utilize Fig.16 All components shown may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0184] exist Fig.16 In the embodiment of the present invention, the processing circuit 1601 can be configured to process computer instructions and data. The processing circuit 1601 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or DSPs) and appropriate software; or any combination of the above. For example, the processing circuit 1601 can include two CPUs. The data can be information in a form suitable for use by a computer.

[0185] In the depicted embodiment, the input / output interface 1605 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1600 may be configured to use an output device via the input / output interface 1605. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1600 or to provide output from the UE 1600. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1600 may be configured to use an input device via the input / output interface 1605 to allow a user to capture information into the UE 1600. The input device may include a touch-sensitive display or a presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0186] exist Fig.16 In the embodiment of the present invention, the RF interface 1609 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface 1611 can be configured to provide a communication interface to the network 1643a. The network 1643a can include a wired and / or wireless network, such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1643a can include a Wi-Fi network. The network connection interface 1611 can be configured to include a receiver and a transmitter interface, which is used to communicate with one or more other devices through a communication network according to one or more communication protocols (e.g., Ethernet, Transmission Control Protocol (TCP) / IP, Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), etc.). The network connection interface 1611 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or can be implemented separately instead.

[0187] RAM 1617 may be configured to be connected to processing circuit 1601 via bus 1602 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 1619 may be configured to provide computer instructions or data to processing circuit 1601. For example, ROM 1619 may be configured to store unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), booting, receiving keystrokes stored in non-volatile memory from a keyboard). Storage medium 1621 may be configured to include memory such as RAM, ROM, programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium 1621 may be configured to include operating system 1623, application 1625 such as a web browser application, a widget or gadget engine, or another application, and data file 1627. The storage medium 1621 may store any one of various operating systems or a combination of operating systems for use by the UE 1600 .

[0188] The storage medium 1621 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module (SIM) or a removable user identity module (RUIM)), other memory, or any combination thereof. The storage medium 1621 may allow the UE 1600 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture such as utilizing a communication system may be tangibly embodied in the storage medium 1621, which may include a device-readable medium.

[0189] exist Fig.16In the embodiment, the processing circuit 1601 may be configured to communicate with the network 1643b using the communication subsystem 1631. The network 1643a and the network 1643b may be the same network or different networks. The communication subsystem 1631 may be configured to include one or more transceivers for communicating with the network 1643b. For example, the communication subsystem 1631 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE, or a base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.16, code division multiple (CDMA), WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 1633 and / or a receiver 1635 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. Furthermore, the transmitter 1633 and receiver 1635 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0190] In the illustrated embodiment, the communication functions of the communication subsystem 1631 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function, or any combination thereof. For example, the communication subsystem 1631 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1643b may include a wired and / or wireless network, such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1643b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1613 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1600.

[0191] The features, benefits and / or functions described herein may be implemented in one of the components of UE 1600, or may be divided among multiple components of UE 1600. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1631 may be configured to include any component described herein. In addition, the processing circuit 1601 may be configured to communicate with any such component on the bus 1602. In another example, any such component may be represented by a program instruction stored in a memory, which performs the corresponding function described herein when executed by the processing circuit 1601. In another example, the function of any such component may be divided between the processing circuit 1601 and the communication subsystem 1631. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0192] Fig.17 1700 is a schematic block diagram illustrating a virtualized environment 1700 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0193] In some embodiments, some or all of the functionality described herein may be implemented as virtual components performed by one or more virtual machines implemented in one or more virtual environments 1700 hosted by one or more hardware nodes 1730. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0194] These functions may be implemented by one or more applications 1720 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement certain features, functions, and / or benefits of some embodiments disclosed herein. The applications 1720 run in a virtualized environment 1700, which provides hardware 1730 including processing circuitry 1760 and memory 1790. The memory 1790 contains instructions 1795 executable by the processing circuitry 1760, whereby the applications 1720 are operable to provide one or more features, benefits, and / or functions disclosed herein.

[0195] The virtualized environment 1700 includes general-purpose or special-purpose network hardware devices 1730, which include a set of one or more processors or processing circuits 1760, which may be commercial off-the-shelf (COTS) processors, special-purpose ASICs, or any other type of processing circuit including digital or analog hardware components or special-purpose processors. Each hardware device may include a memory 1790-1, which may be a non-persistent memory for temporarily storing instructions 1795 or software executed by the processing circuit 1760. Each hardware device may include one or more network interface controllers (NICs) 1770 (also known as network interface cards), which include a physical network interface 1780. Each hardware device may also include a non-transitory persistent machine-readable storage medium 1790-2 in which software 1795 and / or instructions executable by the processing circuit 1760 are stored. The software 1795 may include any type of software including software for instantiating one or more virtualization layers 1750 (also referred to as hypervisors), software for executing virtual machines 1740, and software that enables them to perform the functions, features and / or benefits associated with some of the embodiments described herein.

[0196] The virtual machine 1740 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and may be run by a corresponding virtualization layer 1750 or hypervisor. Different embodiments of instances of the virtual device 1720 may be implemented on one or more virtual machines 1740 and may be implemented in different ways.

[0197] During operation, processing circuit 1760 executes software 1795 to instantiate a hypervisor or virtualization layer 1750, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1750 may present to virtual machine 1740 a virtual operating platform that appears to be networked hardware.

[0198] like Fig.17As shown, hardware 1730 can be an independent network node with common or specific components. Hardware 1730 can include antenna 1723, and some functions can be implemented via virtualization. Alternatively, hardware 1730 can be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed by management and orchestration (MANO) 1702, which, among other items, oversees the life cycle management of application 1720.

[0199] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises equipment.

[0200] In the context of NFV, a virtual machine 1740 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtual machine. Each virtual machine 1740 and the portion of the hardware 1730 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 1740) form a separate virtual network element (VNE).

[0201] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 1740 on top of the hardware networking infrastructure 1730 and corresponds to Fig.17 Applications in 1720.

[0202] In some embodiments, one or more radio units 1710, each including one or more transmitters 1712 and one or more receivers 1711, may be coupled to one or more antennas 1723. The radio units 1710 may communicate directly with the hardware nodes 1730 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0203] In some embodiments, some signaling may be implemented using a control system 1724 , which may alternatively be used for communications between hardware node 1730 and radio unit 1710 .

[0204] refer to Fig.18According to an embodiment, the communication system includes a telecommunication network 1810 such as a 3GPP type cellular network, which includes an access network 1811 such as a radio access network and a core network 1814. The access network 1811 includes a plurality of base stations 1812a, 1812b, 1812c (e.g., Node B, eNB, gNB) or other types of wireless access points, each defining a corresponding coverage area 1813a, 1813b, 1813c. Each base station 1812a, 1812b, 1812c may be connected to the core network 1814 via a wired or wireless connection 1815. A first UE 1891 located in the coverage area 1813c is configured to be wirelessly connected to or paged by the corresponding base station 1812c. A second UE 1892 in the coverage area 1813a may be wirelessly connected to the corresponding base station 1812a. Although multiple UEs 1891 , 1892 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to the corresponding base station 1812 .

[0205] The telecommunications network 1810 itself is connected to a host computer 1830, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1830 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 1821 and 1822 between the telecommunications network 1810 and the host computer 1830 may extend directly from the core network 1814 to the host computer 1830, or may be via an optional intermediate network 1820. The intermediate network 1820 may be one of a public, private, or managed network, or a combination of more than one thereof; the intermediate network 1820 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1820 may include two or more sub-networks (not shown).

[0206] Overall, Fig.18The communication system of the present invention realizes the connectivity between the connected UE 1891, 1892 and the host computer 1830. The connectivity can be described as an over-the-top (OTT) connection 1850. The host computer 1830 and the connected UE 1891, 1892 are configured to use the access network 1811, the core network 1814, any intermediate network 1820 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 1850. The OTT connection 1850 can be transparent in the sense that the participating communication devices through which the OTT connection 1850 passes do not know the routes of the uplink and downlink communications. For example, the base station 1812 may not be notified or need not be notified of the past routes of the incoming downlink communications with data originating from the host computer 1830 to be forwarded (e.g., handed over) to the connected UE 1891. Similarly, the base station 1812 does not need to know the future routes of the outgoing uplink communications from the UE 1891 to the host computer 1830.

[0207] Now refer to Fig.19 1900, a host computer 1910 includes hardware 1915, which includes a communication interface 1916 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 1900. The host computer 1910 also includes a processing circuit 1918, which may have storage and / or processing capabilities. In particular, the processing circuit 1918 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The host computer 1910 also includes software 1911, which is stored in the host computer 1910 or can be accessed by the host computer 1910 and can be executed by the processing circuit 1918. Software 1911 includes a host application 1912. The host application 1912 is operable to provide services to a remote user, such as a UE 1930 connected via an OTT connection 1950 terminating at the UE 1930 and the host computer 1910. In providing services to the remote user, the host application 1912 may provide user data sent using the OTT connection 1950.

[0208] The communication system 1900 also includes a base station 1920 provided in the telecommunication system, and the base station 1920 includes hardware 1925 that enables it to communicate with the host computer 1910 and the UE 1930. The hardware 1925 may include a communication interface 1926 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 1900, and for establishing and maintaining communication with the coverage area ( Fig.19The communication interface 1926 may be configured to facilitate a connection 1960 with the host computer 1910. The connection 1960 may be direct, or the connection 1960 may be through a core network (eg, a wireless communication network) of the telecommunications system. Fig.19 1920) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1925 of the base station 1920 also includes processing circuitry 1928, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The base station 1920 also has software 1921 stored internally or accessible via an external connection.

[0209] The communication system 1900 also includes the UE 1930 already mentioned. The hardware 1935 of the UE 1930 may include a radio interface 1937, which is configured to establish and maintain a wireless connection 1970 with a base station serving the coverage area where the UE 1930 is currently located. The hardware 1935 of the UE 1930 also includes a processing circuit 1938, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The UE 1930 also includes software 1931 stored in the UE 1930 or accessible by the UE 1930 and executable by the processing circuit 1938. The software 1931 includes a client application 1932. The client application 1932 is operable to provide services to human or non-human users via the UE 1930 with the support of the host computer 1910. In the host computer 1910, the executing host application 1912 can communicate with the executing client application 1932 via the OTT connection 1950 terminated at the UE 1930 and the host computer 1910. When providing services to the user, the client application 1932 can receive request data from the host application 1912 and provide user data in response to the request data. The OTT connection 1950 can transmit both the request data and the user data. The client application 1932 can interact with the user to generate user data provided by the user.

[0210] Notice, Fig.19 The host computer 1910, base station 1920 and UE 1930 shown can be respectively Fig.18 The host computer 1830, one of the base stations 1812a, 1812b, 1812c, and one of the UEs 1891, 1892 may be similar or identical. That is, the internal working principles of these entities may be as follows: Fig.19 shown, and independently, the surrounding network topology can be Fig.18 The surrounding network topology.

[0211] exist Fig.19 In the figure, the OTT connection 1950 has been abstractly drawn to illustrate the communication between the host computer 1910 and the UE 1930 via the base station 1920, without explicit reference to any intermediate devices and the precise routing of the messages via these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the UE 1930 or from the service provider operating the host computer 1910, or both. When the OTT connection 1950 is active, the network infrastructure can further make a decision according to which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0212] The wireless connection 1970 between the UE 1930 and the base station 1920 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to the UE 1930 using the OTT connection 1950 (where the wireless connection 1970 forms the last segment). More specifically, the teachings of these embodiments can improve latency and power consumption, thereby providing benefits such as reduced user waiting time, better responsiveness, and extended battery life.

[0213] A measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function for reconfiguring the OTT connection 1950 between the host computer 1910 and the UE 1930. The measurement process and / or network function for reconfiguring the OTT connection 1950 may be implemented in the software 1911 and hardware 1915 of the host computer 1910 or in the software 1931 and hardware 1935 of the UE 1930, or in both. In an embodiment, a sensor (not shown) may be deployed in a communication device through which the OTT connection 1950 passes or associated with such a communication device; the sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software 1911, 1931 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 1950 may include message formats, retransmission settings, preferred routes, etc. The reconfiguration does not need to affect the base station 1920, and it may be unknown or imperceptible to the base station 1920. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 1910 measurements of throughput, propagation time, latency, etc. The measurements may be achieved because software 1911 and 1931 causes messages, particularly empty or "dummy" messages, to be sent using OTT connection 1950 during its monitoring of propagation time, errors, etc.

[0214] Fig. 20 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.18 and Fig.19 In order to simplify the present disclosure, only the host computers, base stations and UEs described in the present disclosure are included in this section. Fig. 20 In step 2010, the host computer provides user data. In sub-step 2011 of step 2010 (which may be optional), the host computer provides the user data by executing a host application. In step 2020, the host computer initiates a transmission to the UE carrying the user data. In step 2030 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 2040 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0215] Fig.21 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.18 and Fig.19 To simplify the present disclosure, this section only includes the host computers, base stations and UEs described in the present disclosure. Fig.21 . In step 2110 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2120, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be through a base station. In step 2130 (which may be optional), the UE receives the user data carried in the transmission.

[0216] Fig. 22 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.18 and Fig.19 To simplify the present disclosure, this section only includes the host computers, base stations and UEs described in the present disclosure. Fig. 22. In step 2210 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2220, the UE provides user data. In sub-step 2221 (which may be optional) of step 2220, the UE provides user data by executing a client application. In sub-step 2211 (which may be optional) of step 2210, the UE executes a client application, which provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in sub-step 2230 (which may be optional). In step 2240 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0217] Fig.23 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.18 and Fig.19 To simplify the present disclosure, this section only includes the host computers, base stations and UEs described in the present disclosure. Fig.23 In step 2310 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2320 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2230 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0218] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers and other digital hardware that may include DSPs, dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0219] The term "unit" may have a conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc. as described herein.

[0220] Some example embodiments of the present disclosure are as follows:

[0221] Group A Embodiment

[0222] Embodiment 1: A method for cross-time slot scheduling performed by a wireless device, the method comprising: monitoring a downlink control channel for downlink scheduling information, wherein any received downlink scheduling can schedule the downlink transmission to occur after a first scheduling delay; receiving first downlink scheduling information for a first data transmission according to the first scheduling delay; receiving the first data transmission at the scheduled time; and monitoring the downlink control channel for the downlink scheduling information, wherein any received downlink scheduling can schedule the downlink transmission to occur after a second scheduling delay, the second scheduling delay being less than the first scheduling delay.

[0223] Embodiment 2: The method according to embodiment 1, wherein taking a first scheduling delay to monitor the downlink control channel includes monitoring a first search space, and taking a second scheduling delay to monitor the downlink control channel includes monitoring a second search space.

[0224] Embodiment 3: The method according to any one of embodiments 1 to 2, wherein adopting a second scheduling delay to monitor the downlink control channel is performed after sending a HARQ response to the first received data transmission.

[0225] Embodiment 4: The method of embodiment 3, wherein adopting a second scheduling delay to monitor the downlink control channel is performed after sending a HARQ ACK response to the first received data transmission.

[0226] Embodiment 5: The method according to any one of embodiments 1 to 4 further includes: after adopting the second scheduling delay to monitor the downlink control channel within a threshold amount of time, reverting to adopting the first scheduling delay to monitor the downlink control channel.

[0227] Embodiment 6: The method of embodiment 5, wherein the threshold amount of time corresponds to an end of the DRX onDuration.

[0228] Embodiment 7: The method according to any one of embodiments 1 to 6, wherein the first scheduling delay is greater than one time slot and the second scheduling delay is the same time slot.

[0229] Embodiment 8: The method according to any of the preceding embodiments further comprises: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0230] Group B Example

[0231] Embodiment 9: A method for cross-time slot scheduling performed by a base station, the method comprising: sending first downlink scheduling information to a wireless device, the first downlink scheduling information comprising a first scheduling delay; sending a first data transmission to the wireless device according to the first scheduling information; and sending second downlink scheduling information to the wireless device, the second downlink scheduling information comprising a second scheduling delay, the second scheduling delay being less than the first scheduling delay.

[0232] Embodiment 10: The method according to embodiment 9, wherein sending the first downlink scheduling information includes sending the first downlink scheduling information in a first search space, and sending the second downlink scheduling information includes sending the second downlink scheduling information in a second search space.

[0233] Embodiment 11: The method according to any one of embodiments 9 to 10, wherein sending the second downlink scheduling information is performed after receiving a HARQ response to the first data transmission.

[0234] Embodiment 12: The method according to embodiment 11, wherein sending the second downlink scheduling information is performed after receiving a HARQ ACK response to the first data transmission.

[0235] Embodiment 13: The method according to any one of embodiments 1 to 6, wherein the first scheduling delay is greater than one time slot and the second scheduling delay is the same time slot.

[0236] Embodiment 14: The method according to any one of the preceding embodiments further comprises: obtaining user data; and forwarding the user data to a host computer or a wireless device.

[0237] Group C Example

[0238] Embodiment 15: A wireless device for cross-time slot scheduling, the wireless device comprising: a processing circuit configured to perform any of the steps of any one of Group A embodiments; and a power supply circuit configured to supply power to the wireless device.

[0239] Embodiment 16: A base station for cross-time slot scheduling, the base station comprising: a processing circuit configured to perform any of the steps of any one of Group B embodiments; and a power supply circuit configured to supply power to a wireless device.

[0240] Embodiment 17: A user equipment (UE) for cross-time slot scheduling, the UE comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust the signal transmitted between the antenna and the processing circuit; the processing circuit is configured to perform any of the steps of any one of the embodiments in Group A; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to supply power to the UE.

[0241] Embodiment 18: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any of the steps of any one of the embodiments in Group B.

[0242] Embodiment 19: The communication system according to the aforementioned embodiment further includes: the base station.

[0243] Embodiment 20: The communication system according to the two aforementioned embodiments further includes: the UE, wherein the UE is configured to communicate with the base station.

[0244] Embodiment 21: A communication system according to the three aforementioned embodiments, wherein: a processing circuit of a host computer is configured to execute a host application to provide user data; and the UE includes a processing circuit configured to execute a client application associated with the host application.

[0245] Embodiment 22: A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station performs any of the steps of any one of the embodiments in Group B.

[0246] Embodiment 23: The method according to the aforementioned embodiment further includes: sending user data at the base station.

[0247] Embodiment 24: The method according to the above two embodiments, wherein the user data is provided at the host computer by executing a host application, and the method further comprises: at the UE, executing a client application associated with the host application.

[0248] Embodiment 25: A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform any one of the three preceding embodiments.

[0249] Embodiment 26: A communication system comprising a host computer, the host computer comprising: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and a processing circuit, and components of the UE are configured to perform any of the steps of any one of the embodiments of Group A.

[0250] Embodiment 27: In the communication system according to the foregoing embodiment, the cellular network further comprises a base station configured to communicate with the UE.

[0251] Embodiment 28: The communication system according to the two aforementioned embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the processing circuit of the UE is configured to execute a client application associated with the host application.

[0252] Embodiment 29: A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network including the base station, wherein the UE performs any of the steps of any one of the embodiments in Group A.

[0253] Embodiment 30: The method according to the aforementioned embodiment further includes: at the UE, receiving user data from the base station.

[0254] Embodiment 31: A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any of the steps of any one of the embodiments in Group A.

[0255] Embodiment 32: The communication system according to the aforementioned embodiment further includes: the UE.

[0256] Embodiment 33: The communication system according to the two aforementioned embodiments further includes: the base station, wherein the base station includes: a radio interface configured to communicate with the UE; and a communication interface configured to forward user data carried by the transmission from the UE to the base station to the host computer.

[0257] Embodiment 34: A communication system according to the three aforementioned embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0258] Embodiment 35: A communication system according to the aforementioned four embodiments, wherein: the processing circuit of the host computer is configured to execute a host application to provide request data; and the processing circuit of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.

[0259] Embodiment 36: A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data sent to the base station from the UE, wherein the UE performs any of the steps of any one of the embodiments in Group A.

[0260] Embodiment 37: The method according to the aforementioned embodiment further includes: at the UE, providing user data to the base station.

[0261] Embodiment 38: The method according to the above two embodiments further includes: executing a client application at the UE to provide user data to be sent; and executing a host application associated with the client application at the host computer.

[0262] Embodiment 39: The method according to the aforementioned three embodiments further includes: executing a client application at the UE; and receiving input data of the client application at the UE, wherein the input data is provided at the host computer by executing a host application associated with the client application, wherein the user data to be sent is provided by the client application in response to the input data.

[0263] Embodiment 40: A communication system comprising a host computer, the host computer comprising a communication interface, the communication interface being configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps of any one of the embodiments of Group B.

[0264] Embodiment 41: The communication system according to the above embodiment also includes: the base station.

[0265] Embodiment 42: The communication system according to the above two embodiments further includes: the UE, wherein the UE is configured to communicate with the base station.

[0266] Embodiment 43: A communication system according to the three aforementioned embodiments, wherein: the processing circuit of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0267] Embodiment 44: A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data originating from a transmission that the base station has received from the UE, wherein the UE performs any of the steps of any one of the embodiments in Group A.

[0268] Embodiment 45: The method according to the aforementioned embodiment further includes: receiving user data from the UE at the base station.

[0269] Embodiment 46: The method according to the above two embodiments further comprises: at the base station, initiating transmission of the received user data to a host computer.

[0270] Embodiment 47: A user device for communicating with a cellular telecommunication network, the user device comprising: a processing circuit configured to: define at least two search spaces comprising a first search space and a second search space, wherein the first search space has a first minimum K0 value and the second search space has a second minimum K0 value different from the first minimum K0 value; and switch PDCCH monitoring between the at least two search spaces.

[0271] Embodiment 48: A user device for communicating with a cellular telecommunication network, the user device comprising: a processing circuit configured to: define a first group of K0 values ​​and a second group of K0 values, wherein both the first group of K0 values ​​and the second group of K0 values ​​are used for a first search space; and switch between the first group and the second group based on an implicit or explicit dynamic indication.

[0272] abbreviation

[0273] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over subsequent listings.

[0274] 2G Second Generation

[0275] 3G Third Generation

[0276] 3GPP Third Generation Partnership Project

[0277] 4G Fourth Generation

[0278] 5G fifth generation

[0279] AC

[0280] ACK

[0281] AP Access Point

[0282] ASIC Application-Specific Integrated Circuit

[0283] ATM Asynchronous Transfer Mode

[0284] BCH Broadcast Channel

[0285] BS Base Station

[0286] BSC Base Station Controller

[0287] BTS Base Transceiver Station

[0288] BW Bandwidth

[0289] BWP Bandwidth Part

[0290] CD

[0291] CDMA Code Division Multiple Access

[0292] CDRX connected mode DRX

[0293] CORESET control resource set

[0294] ·COTS Commercial Off-the-Shelf

[0295] CPE Customer Premises Equipment

[0296] CPU Central Processing Unit

[0297] CRC Cyclic Redundancy Check

[0298] C-RNTI Cell Radio Network Temporary Identifier

[0299] CS-RNTI configured Scheduling Radio Network Temporary Identifier

[0300] D2D Device to Device

[0301] DAI Downlink Allocation Index

[0302] DAS Distributed Antenna System

[0303] DC

[0304] DCI Downlink Control Information

[0305] DIMM Dual In-line Memory Module

[0306] DL Downlink

[0307] DL-SCH Downlink Shared Channel

[0308] DRX Discontinuous Reception

[0309] DSP Digital Signal Processor

[0310] eMBB Enhanced Mobile Broadband

[0311] eMTC Enhanced Machine Type Communication

[0312] eNB Enhanced or evolved Node B

[0313] EPROM Erasable Programmable Read Only Memory

[0314] E-SMLC Evolved Service Mobile Location Center

[0315] FPGA Field Programmable Gate Array

[0316] GHz Gigahertz

[0317] gNB New Radio Base Station

[0318] GPS Global Positioning System

[0319] GSM Global System for Mobile Communications

[0320] HARQ Hybrid Automatic Repeat Request

[0321] HDDS Holographic Digital Data Storage

[0322] I / O input and output

[0323] IoT

[0324] IP Internet Protocol

[0325] LAN

[0326] LTE Long Term Evolution

[0327] M2M Machine to Machine

[0328] MAC Media Access Control

[0329] MANO management and orchestration

[0330] MCE Multi-cell / multicast coordination entity

[0331] MDT Minimized Drive Test

[0332] MIMO Multiple Input and Multiple Output

[0333] MME Mobility Management Entity

[0334] ms milliseconds

[0335] MSC Mobile Switching Center

[0336] MSR Multi-Standard Radio

[0337] MTC Machine Type Communication

[0338] NACK Negative Acknowledgement

[0339] NB-IoT Narrowband Internet of Things

[0340] NFV Network Function Virtualization

[0341] NIC Network Interface Controller

[0342] NR New Radio

[0343] O&M

[0344] OFDM Orthogonal Frequency Division Multiplexing

[0345] OSS Operation Support System

[0346] OTT Over the Top

[0347] PBCH Physical Broadcast Channel

[0348] PCH Paging Channel

[0349] PDA Personal Digital Assistant

[0350] PDCCH Physical Downlink Control Channel

[0351] PDSCH Physical Downlink Shared Channel

[0352] PHY

[0353] PRACH Physical Random Access Channel

[0354] PRB Physical Resource Block

[0355] P-RNTI Paging Radio Network Temporary Identifier

[0356] PROM Programmable Read Only Memory

[0357] PSM power saving mode

[0358] PSTN Public Switched Telephone Network

[0359] PUCCH Physical Uplink Control Channel

[0360] PUSCH Physical Uplink Shared Channel

[0361] RACH Random Access Channel

[0362] RAID Redundant Array of Independent Disks

[0363] RAM Random Access Memory

[0364] RAN Radio Access Network

[0365] RAR Random Access Response

[0366] RA-RNTI Random Access Radio Network Temporary Identifier

[0367] RAT Radio Access Technology

[0368] RB Resource Block

[0369] RF

[0370] RNC Radio Network Controller

[0371] RNTI Radio Network Temporary Identifier

[0372] ROM Read Only Memory

[0373] RRC Radio Resource Control

[0374] RRH Remote Radio Head

[0375] RRU Remote Radio Unit

[0376] RTT Round Trip Time

[0377] RUIM Removable User Identity Module

[0378] SCS subcarrier spacing

[0379] SDRAM Synchronous Dynamic Random Access Memory

[0380] SIM Subscriber Identity Module

[0381] SI-RNTI System Information Radio Network Temporary Identifier

[0382] SLIV Slot Length Indicator Value

[0383] ·SOC System on Chip

[0384] SON self-organizing network

[0385] SONET Synchronous Optical Network

[0386] SS synchronization signal

[0387] TCP Transmission Control Protocol

[0388] TPC Transmit Power Control

[0389] TS Technical Specification

[0390] UE User Equipment

[0391] UL Uplink

[0392] UMTS Universal Mobile Telecommunications System

[0393] URLLC ultra-reliable and low-latency communications

[0394] USB Universal Serial Bus

[0395] V2I Vehicle to Infrastructure

[0396] V2V Vehicle to Vehicle

[0397] V2X Vehicle to Everything

[0398] VMM Virtual Machine Monitor

[0399] VNE Virtual Network Element

[0400] VNF Virtual Network Function

[0401] ·VoIP Voice over Internet Protocol

[0402] VRB Virtual Resource Block

[0403] WAN Wide Area Network

[0404] ·WCDMA Wideband Code Division Multiple Access

[0405] WD Wireless Devices

[0406] WiMax Worldwide Interoperability for Microwave Access

[0407] WLAN Wireless Local Area Network

[0408] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless device, the method comprising: During a first time slot, monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmission by the wireless device using an assumption of a first scheduling delay, the first scheduling delay being equal to or exceeding a first value; determining (502; 904; 1104) that the wireless device is to switch from the hypothesis of the first scheduling delay to a hypothesis of a second scheduling delay, the second scheduling delay being equal to or exceeding a second value, the second value being less than the first value; and monitoring (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission by the wireless device using the assumption of the second scheduling delay during one or more later time slots occurring after the first time slot; Wherein, determining (502; 904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay includes: in response to an explicit indication or an implicit indication from a network node, determining (502; 904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay.

2. The method according to claim 1, wherein: Monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay comprises: monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay in a particular search space; and Using the assumption of the second scheduling delay to monitor (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission of the wireless device includes: in the specific search space, using the assumption of the second scheduling delay to monitor (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission of the wireless device.

3. The method according to claim 1, wherein: Monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay comprises: monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using the assumption of the first scheduling delay in a first search space; and Using the assumption of the second scheduling delay to monitor (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission of the wireless device includes: in a second search space different from the first search space, using the assumption of the second scheduling delay to monitor (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission of the wireless device.

4. The method according to claim 3, wherein: The first search space is associated with a first bandwidth, and the second search space is associated with a second bandwidth, wherein the first bandwidth is smaller than the second bandwidth.

5. The method according to claim 1, wherein: The explicit indication or implicit indication is an explicit indication included in downlink control information from the network node.

6. The method according to any one of claims 1 to 4, wherein: During the first time slot, monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using an assumption of the first scheduling delay comprises: during the first time slot, while the wireless device is operating in a first power mode associated with the first scheduling delay, monitoring (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device using an assumption of the first scheduling delay; and Determining (502; 904; 1104) that the wireless device is to switch from the hypothesis of the first scheduling delay to the hypothesis of the second scheduling delay includes transitioning (904; 1104) from the first power mode to a second power mode associated with the second scheduling delay.

7. The method according to claim 6, wherein: Transitioning (904; 1104) from the first power mode to a second power mode associated with the second scheduling delay includes: in response to an indication included in downlink control information from a network node, transitioning (904; 1104) from the first power mode to the second power mode associated with the second scheduling delay.

8. The method according to claim 6, wherein: Transitioning (904; 1104) from the first power mode to a second power mode associated with the second scheduling delay includes, after sending a hybrid automatic repeat request HARQ confirmation ACK for a transmission scheduled by downlink control information included in a downlink control channel detected in the first time slot, transitioning (904; 1104) from the first power mode to the second power mode associated with the second scheduling delay.

9. The method according to claim 6, wherein: Transitioning (904; 1104) from the first power mode to a second power mode associated with the second scheduling delay includes transitioning (904; 1104) from the first power mode to the second power mode associated with the second scheduling delay upon expiration of a timer.

10. The method according to claim 9, wherein: Expiry of the timer is dependent on the absence of reception of a downlink control channel.

11. The method according to claim 9, wherein: Expiration of the timer is dependent upon failure to receive a downlink control channel for a configured number of monitoring occasions.

12. The method according to claim 6, wherein: The first power mode is a power saving mode (PSM) and the second power mode is a non-PSM; or The first power mode is non-PSM and the second power mode is PSM.

13. The method according to claim 12, wherein: The PSM is a mode in which only cross-slot scheduling is used, and the non-PSM is a mode in which same-slot scheduling can be used.

14. The method according to claim 6, wherein: The first value is a value corresponding to a value greater than or equal to one time slot.

15. The method according to claim 14, wherein: The second value is a value corresponding to a value of zero time slots.

16. The method according to any one of claims 1 to 4, wherein: Determining (904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay includes: after sending a hybrid automatic repeat request HARQ confirmation ACK for a transmission scheduled by downlink control information included in a downlink control channel detected in the first time slot, determining (904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay.

17. The method according to any one of claims 1 to 4, wherein: Determining (904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay includes: after a timer expires, determining (904; 1104) that the wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay.

18. The method according to claim 17, wherein: Expiration of the timer is dependent upon failure to receive a downlink control channel for a configured number of monitoring occasions.

19. The method according to claim 1, wherein: The first value is a value corresponding to a value greater than or equal to one time slot.

20. The method according to claim 19, wherein: The first value is a value determined based on a wireless device indication, the wireless device indication depending on only a physical downlink shared channel parameter set, or depending on a physical downlink control channel parameter set and a physical downlink shared channel parameter set.

21. The method according to claim 19, wherein: The second value is a value corresponding to a value of zero time slots.

22. The method according to claim 19 or 21, further comprising: Operating in a low power mode when the downlink control channel is not monitored during the first time slot based on an assumption that a downlink schedule detected on the downlink control channel in the first time slot schedules downlink transmissions to the wireless device with the first scheduling delay exceeding the first value.

23. The method according to claim 19 or 21, wherein: Monitoring (500; 902; 1102) the downlink control channel during the first time slot comprises: monitoring (500; 902; 1102) the downlink control channel at a beginning portion of the first time slot, and the method further comprises: Based on the assumption of the first scheduling delay, operating in a low power mode during the first time slot begins at an end of the beginning portion of the first time slot in which the downlink control channel is monitored.

24. The method according to any one of claims 1 to 5, wherein: OK(502;904; 1104) The wireless device is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay including: determining (502) that a downlink control channel including downlink control information scheduled for transmission to the wireless device is detected during the first time slot.

25. The method according to claim 24, wherein: The one or more later time slots include a second time slot immediately following the first time slot.

26. The method according to claim 24, wherein: The one or more later time slots occur after a time slot in which the wireless device sends a hybrid automatic repeat request (HARQ) response for a transmission scheduled by the downlink control information included in the downlink control channel detected in the first time slot.

27. The method according to claim 24, wherein: The one or more later time slots occur after a time slot in which the wireless device sends a hybrid automatic repeat request HARQ acknowledgment ACK for a transmission scheduled by the downlink control information included in the downlink control channel detected in the first time slot.

28. The method of claim 24, wherein: The one or more later time slots occur after a time slot in which the wireless device detects another downlink control channel including downlink control information that schedules transmission for the wireless device according to the second scheduling delay.

29. The method according to any one of claims 26 to 28, further comprising: In one or more subsequent time slots after the first time slot and before the one or more later time slots, a downlink control channel including downlink control information scheduled for transmission by the wireless device is monitored (508; 510) using the assumption of the first scheduling delay.

30. The method of claim 24, wherein: The first time slot is during a discontinuous reception (DRX) on duration, and the one or more later time slots are all time slots that occur later than the first time slot in the DRX on duration.

31. The method of claim 24, wherein: The first time slot is during a discontinuous reception (DRX) on duration, and the one or more later time slots are a predefined number of time slots occurring later than the first time slot in the DRX on duration.

32. The method of claim 24, further comprising: Switching to monitoring (512) a downlink control channel including downlink control information scheduled for transmissions for the wireless device using the first scheduling delay assumption or using both the first scheduling delay assumption and the second scheduling delay assumption.

33. A wireless device (1510), comprising: Radio front end circuit (1512); as well as a processing circuit (1520) associated with the radio front end circuit (1512), the processing circuit (1520) being configured to cause the wireless device (1510): During a first time slot, monitoring (500; 902; 1102) includes a downlink control channel for scheduling downlink control information for transmission by the wireless device (1510), the first scheduling delay being equal to or exceeding a first value; determining (502; 904; 1104) that the wireless device (1510) is to switch from the assumption of the first scheduling delay to an assumption of a second scheduling delay, the second scheduling delay being equal to or exceeding a second value, the second value being less than the first value; and monitoring (506; 906; 1106) a downlink control channel including downlink control information scheduled for transmission by the wireless device (1510) using the assumption of the second scheduling delay during one or more later time slots occurring after the first time slot; In which, in order to enable the wireless device (1510) to determine that the wireless device (1510) is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay, the processing circuit (1520) is also configured to enable the wireless device (1510): in response to an explicit indication or an implicit indication from a network node, determine (502; 904; 1104) that the wireless device (1510) is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay.

34. The wireless device (1510) of claim 33, wherein: The explicit indication or implicit indication is an explicit indication included in downlink control information from the network node.

35. The wireless device (1510) of claim 33, wherein: The processing circuit (1520) is further configured to cause the wireless device (1510): during the first time slot, when the wireless device (1510) is operating in a first power mode associated with the first scheduling delay, to monitor (500; 902; 1102) a downlink control channel including downlink control information scheduled for transmissions of the wireless device (1510) using an assumption of the first scheduling delay; and In order to enable the wireless device (1510) to determine that the wireless device (1510) is to switch from the assumption of the first scheduling delay to the assumption of the second scheduling delay, the processing circuit (1520) is also configured to cause the wireless device (1510) to: transition (904; 1104) from the first power mode to a second power mode associated with the second scheduling delay.

36. The wireless device (1510) of claim 35, wherein: The processing circuit (1520) is further configured to cause the wireless device (1510): in response to an indication included in downlink control information from a network node, to transition (904; 1104) from the first power mode to the second power mode.

Images