PDCCH skipping process after NACK transmission

Abstract

Exemplary embodiments of the present disclosure relate to terminal devices, network devices, methods, apparatus, and computer-readable storage media for solutions to PDCCH skipping processing after NACK transmission in multi-cell operation. In some embodiments, a terminal device may receive a DCI indicating to skip PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmissions on a scheduled cell. If a NACK for a PDSCH transmission on a scheduled cell is transmitted, the terminal device may further resume PDCCH monitoring on at least one serving cell or terminate PDCCH skipping, the at least one serving cell including a scheduling cell that schedules PDSCH transmissions. In such a configuration, communication between the terminal device and the network device may be maintained on at least the scheduling cell, and power consumption may be reduced.

Description

Technical Field

[0001] Exemplary embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to terminal devices, network devices, methods, apparatuses, and computer-readable storage media for physical downlink control channel (PDCCH) skipping handling after negative acknowledgment (NACK) transmission in multi-cell operation.

Background Art

[0002] The PDCCH skipping function was introduced in the 3rd Generation Partnership Project (3GPP) Release 17 (Rel-17). A terminal device such as a user equipment (UE) can skip PDCCH monitoring based on downlink control information (DCI) related to a type-3 common search space (type-3 CSS) for monitoring the PDCCH and a UE-specific search space (USS) for monitoring the PDCCH during a duration. However, when a UE is composed of multiple serving cells, how to implement PDCCH skipping needs further consideration.

Summary of the Invention

[0003] Generally, exemplary embodiments of the present disclosure provide a solution for PDCCH skipping handling after NACK transmission in multi-cell operation.

[0004] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory for storing instructions, which, when executed by at least one processor, cause the terminal device to at least receive downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and, based on the determination that a negative response (NACK) for a PDSCH transmission on the scheduled cell has been sent, restart PDCCH monitoring or terminate PDCCH skipping on at least one serving cell, the at least one serving cell includes a scheduling cell that schedules a PDSCH transmission.

[0005] In a second embodiment, a network device is provided. The network device comprises at least one processor and at least one memory for storing instructions, which, when executed by at least one processor, cause the network device to at least transmit downlink control information (DCI) to a terminal device indicating to skip physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmissions on a scheduled cell, and, based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been received, cause the terminal device to determine at least one serving cell on which PDCCH monitoring will be resumed or PDCCH skipping will be terminated, the at least one serving cell including a scheduling cell that schedules PDSCH transmissions.

[0006] In a third embodiment, a method is provided that is carried out by a terminal device. The method includes the terminal device receiving downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and resuming PDCCH monitoring or terminating PDCCH skipping on at least one serving cell based on the determination that a negative response (NACK) for a PDSCH transmission on the scheduled cell has been sent, the at least one serving cell including a scheduling cell that schedules a PDSCH transmission.

[0007] In a fourth embodiment, a method is provided that is implemented by a network device. The method includes the network device sending downlink control information (DCI) to a terminal device that indicates to skip physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and the terminal device determining, based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been received, at least one serving cell on which PDCCH monitoring is resumed or PDCCH skipping is terminated, the at least one serving cell including a scheduling cell that schedules a PDSCH transmission.

[0008] In a fifth embodiment, an apparatus is provided. The apparatus includes, in a terminal device, means for receiving downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and means for restarting PDCCH monitoring or terminating PDCCH skipping on at least one serving cell based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been transmitted, wherein at least one serving cell includes a scheduling cell that schedules a PDSCH transmission.

[0009] In a sixth embodiment, an apparatus is provided. The apparatus is a network device comprising means for transmitting downlink control information (DCI) to a terminal device that indicates to skip physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and means for the terminal device to determine, based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been received, at least one serving cell on which PDCCH monitoring is resumed or PDCCH skipping is terminated, wherein the at least one serving cell includes a scheduling cell that schedules a PDSCH transmission.

[0010] In a seventh embodiment, a terminal device is provided. The terminal device comprises a receiving circuit configured to receive downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and an implementing circuit configured to restart PDCCH monitoring or terminate PDCCH skipping on at least one serving cell based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been transmitted, the at least one serving cell including a scheduling cell that schedules a PDSCH transmission.

[0011] In an eighth embodiment, a network device is provided. The network device comprises a transmit circuit configured to transmit downlink control information (DCI) to a terminal device that indicates to skip physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules a physical downlink shared channel (PDSCH) transmission on a scheduled cell, and a determination circuit configured to determine, by the terminal device, at least one serving cell on which PDCCH monitoring is resumed or PDCCH skipping is terminated, based on the determination that a negative response (NACK) for a PDSCH transmission on a scheduled cell has been received, the at least one serving cell including a scheduling cell that schedules a PDSCH transmission.

[0012] In the ninth embodiment, a non-temporary computer-readable medium is provided which includes program instructions for causing an apparatus to carry out at least the method of the third or fourth embodiment.

[0013] In a tenth embodiment, a computer program is provided that, when executed by the apparatus, includes instructions causing the apparatus to perform at least the method of the third or fourth embodiment.

[0014] It should be understood that the Summary section is not intended to identify any material or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will be more readily apparent through the following description.

[0015] Several exemplary embodiments will be described below with reference to the attached drawings. [Brief explanation of the drawing]

[0016] [Figure 1] This figure illustrates an example of a network environment in which several exemplary embodiments of this disclosure may be implemented. [Figure 2A] This is a schematic diagram of a carrier aggregation with self-scheduling, in which some exemplary embodiments of the present disclosure may be implemented. [Figure 2B] This is a schematic diagram of carrier aggregation with cross-carrier scheduling, in which several exemplary embodiments of the present disclosure may be implemented. [Figure 2C] This is a schematic diagram of cell grouping into a DRX group, in which several exemplary embodiments of the present disclosure may be implemented. [Figure 3] This figure shows an example of a process flow according to some exemplary embodiments of the present disclosure. [Figure 4] This is a flowchart of a method implemented in a terminal device according to some example embodiments of the present disclosure. [Figure 5] This is a flowchart of a method implemented in a network device according to some exemplary embodiments of the present disclosure. [Figure 6] This is a simplified block diagram of a device suitable for carrying out some exemplary embodiments of the present disclosure. [Figure 7] This is a block diagram of an example of a computer-readable medium according to some exemplary embodiments of the present disclosure. [Modes for carrying out the invention]

[0017] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.

[0018] The principles of the present disclosure will be described with reference to several exemplary embodiments hereinafter. These embodiments are described for illustrative purposes only and are not intended to imply any limitation with respect to the scope of the present disclosure, and it should be understood that they assist those skilled in the art in understanding and implementing the present disclosure. The disclosure described herein can be implemented in various forms other than those described hereinafter.

[0019] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0020] References to "one embodiment", "an embodiment", "exemplary embodiment", and the like in the present disclosure indicate that the embodiment described may include a particular feature, structure, or characteristic, but not all embodiments necessarily include that particular feature, structure, or characteristic. Moreover, such expressions do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with one embodiment, it is proposed that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0021] The terms "first", "second", and the like may be used herein to describe various elements, but it should be understood that these elements are not to be limited by these terms. These terms are only used to distinguish one element from another. Without departing from the scope of the exemplary embodiments, for example, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0022] The terms used herein are for the purpose of describing particular embodiments only and are not intended to be limitations of the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprise", "comprising", "have", "having", "include", and / or "including", when used herein, specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, "at least one of <list of two or more elements>", and "<list of two or more elements> of at least one", and similar phrases mean at least any one of the elements in the list of two or more elements, or at least any two or more of the elements in the list, or at least all of the elements, when the list of two or more elements is joined by "and" or "or".

[0023] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) only hardware circuit implementations (such as only analog and / or digital circuit implementations), and (b) combinations of hardware circuits and software, where applicable, for example: (i) combinations of analog and / or digital hardware circuits with software / firmware, (ii) Any part of a hardware processor with software (including digital signal processors, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions), (c) Hardware circuits and / or processors, such as a microprocessor or a part of a microprocessor, that require software (e.g., firmware) for operation, but the software may not be present when not required for operation.

[0024] Such definition of circuit applies to all use of the term in this application, including in any claims. Further as an example, as used in this application, the term circuit also encompasses simply a hardware circuit or processor (or more processors), or a portion of a hardware circuit or processor, and the implementation of its (or their) accompanying software and / or firmware. The term circuit also encompasses, for example, and, as applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or networking device.

[0025] As used herein, the term “communication network” refers to a network conforming to any preferred communication standard, such as Long-Term Evolution (LTE), LTE-Advanced (LTE-A), New Radio (NR), Broadband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communications within a communication network may be carried out in accordance with any preferred generation communication protocol, including, but not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure may be applied to a variety of communication systems. Given the rapid development in communications, there will naturally be future types of communication technologies and systems to which this disclosure may be embodied. It should not be considered that the scope of this disclosure is limited to the aforementioned systems only.

[0026] As used herein, the term “network device” refers to a node in a communication network through which terminal devices access the network and receive services from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or access point (AP), e.g., Node B (NodeB or NB), evolved Node B (eNodeB or eNB), New Radio (NR) NB (also known as gNB), remote radio equipment (RRU), radio header (RH), remote radio head (RRH), IAB (Integrated Access and Backhaul) node, relay equipment, low-power node, e.g., femto, pico, etc.

[0027] The term "terminal device" refers to any end device that may have the capability to communicate wirelessly. For illustrative purposes only, terminal devices may also be called communication devices, user equipment (UE), subscriber stations (SS), portable subscriber stations, mobile stations (MS), or access terminals (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image-capturing terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop embedded devices (LMEs), USB dongles, smart devices, wireless subscriber equipment (CPEs), Internet of Things (IoT) devices, machine-type communications (MTC) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics, devices operating on commercial and / or industrial wireless networks, and similar devices. In the following explanation, the terms “terminal device,” “communication device,” “terminal,” “user equipment,” and “UE” may be used synonymously.

[0028] As described above, terminal devices such as UEs may skip PDCCH monitoring based on downlink control information (DCI) regarding a type-3 common search space (type-3 CSS) and a UE-specific search space (USS) for monitoring PDCCH over a time period determined, for example, by a skipping indication in a 2-bit indication field, with each indication associated with a duration configured in Radio Resource Control (RRC). The PDCCH skipping behavior described in TS38.213 is cell-specific and applies, for example, to the active downlink (DL) bandwidth portion (BWP).

[0029] A New Radio(NR)UE can consist of multiple serving cells (which may include both DL and UL, or only DL). In other words, it can be configured as a carrier aggregation. For each serving cell, its PUCCH can be configured on a PCell / SpCell, or on a PUCCH SCell if one is configured.

[0030] When a NACK is sent within the UL, it is beneficial to terminate PDCCH skipping (or, equivalently, resume PDCCH monitoring). By introducing this feature, the network can configure longer skipping durations without negatively impacting DL traffic KPIs, and (due to the longer skipping duration) enable better power savings at the UE. However, when multiple serving cells are configured, how to implement this feature needs further consideration, taking into account not only UE power savings but also maintaining and enabling network scheduling flexibility.

[0031] Exemplary embodiments of this disclosure provide solutions for PDCCH skipping after NACK transmission in multi-cell operation. In some embodiments, a terminal device may receive a DCI indicating to skip PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmission on a scheduled cell. If a NACK for PDSCH transmission on a scheduled cell has been transmitted (by the terminal device), the terminal device may further resume PDCCH monitoring on at least one serving cell or terminate PDCCH skipping, the at least one serving cell including a scheduling cell that schedules PDSCH transmission. In such a case, communication between the terminal device and the network device may be maintained on at least the scheduling cell, and power consumption may be reduced as well. The principles of this disclosure and some exemplary embodiments are described below in detail with reference to the accompanying drawings.

[0032] Figure 1 illustrates an example of a network environment 100 in which several exemplary embodiments of the present disclosure may be implemented. Environment 100, which may be part of a communication network, includes terminal devices 110 and network devices 120. Network environment 100 may be referred to as a network system, communication environment, communication network, communication system, or similar, and the present disclosure is not limited to these embodiments.

[0033] Environment 100 may include any suitable number of devices and cells. Within Environment 100, network device 120 may provide services to terminal device 110, and network device 120 and terminal device 110 may communicate with each other with data and control information. In some embodiments, network device 120 and terminal device 110 may communicate using direct links / channels.

[0034] Within system 100, the link from network device 120 to terminal device 110 is referred to as a downlink (DL), while the link from terminal device 110 to network device 120 is referred to as an uplink (UL). In the downlink, network device 120 is a transmit (TX) device (or transmitter), and terminal device 110 is a receive (RX) device (or receiver). In the uplink, terminal device 110 is a transmit TX device (or transmitter), and network device 120 is an RX device (or receiver). It should be understood that network device 120 may provide one or more serving cells. In some embodiments, network device 120 may provide multiple cells.

[0035] Communication within the network environment 100 may be conducted in accordance with any suitable communication protocol, including, but not limited to, cellular communication protocols of first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (1G), and sixth generation (6G) and similar, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and similar, and / or any other protocols currently known or to be developed in the future. Furthermore, communication may utilize any suitable wireless communication technology, including, but is not limited to, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0036] It should be understood that the number of devices (i.e., terminal devices 110 and network devices 120), and their connectivity relationships and types shown in Figure 1, are for illustrative purposes only and do not imply any limitations. For example, environment 100 may include any suitable number of devices adapted to carry out embodiments of this disclosure. For example, Figure 1 depicts terminal device 110 as a mobile phone, but terminal device 110 could be any type of user equipment.

[0037] In some exemplary embodiments, the network device 120 may provide multiple serving cells for the terminal device 110. For example, there may be primary cells (PCells) and secondary cells (SCells). More cells, such as SpCells, may exist, but it should be understood that this disclosure is not limited to these embodiments.

[0038] Figure 2A illustrates a schematic diagram 210 of a carrier aggregation (CA) with self-scheduling, in which several exemplary embodiments of the present disclosure may be implemented. Schematic diagram 210 illustrates a basic carrier aggregation configuration in which each cell schedules itself. As shown in Figure 2A, PCells and SCells exist in a multi-cell deployment, and each cell performs self-scheduling.

[0039] As shown in 211, a PCell DCI on a PDCCH(C) is detected in the PDCCH monitoring status of the search space on the PCell, and the DCI schedules a PCell PDSCH. The PDSCH may be in the same slot where the PDCCH transmitting the DCI is detected, or it may be in a later slot.

[0040] As shown in 212, the PCell PDSCH's hybrid automatic iterative request-response (HARQ-ACK) feedback (ACK or NACK) is mapped to the PCell uplink.

[0041] As shown in 213, a SCell DCI on a PDCCH(C) is detected in the PDCCH monitoring status of the search space on the SCell, and the DCI schedules a SCell PDSCH. The PDSCH may be in the same slot where the PDCCH transmitting the DCI is detected, or it may be in a later slot.

[0042] As shown in 214, the HARQ-ACK feedback (ACK or NACK) of the SCell PDSCH is mapped to the PCell uplink.

[0043] Each PCell and SCell performs self-scheduling that corresponds to a different cell than the skipping indication (included in the DCI) in the NACK. For example, the Scell ​​DCI may indicate skipping and schedule a PDSCH, while the PCell only schedules a PDSCH (without skipping). HARQ feedback is held by the (joint) PUCCH. The NACK may correspond to a PDSCH held within the PCell, but skipping cancellation is applied within the Scell.

[0044] Figure 2B illustrates a schematic diagram 220 of a carrier aggregation with cross-carrier scheduling, in which several exemplary embodiments of the present disclosure may be implemented. As shown in Figure 2B, PCells and SCells are present in a multi-cell deployment. Schematic diagram 220 illustrates a cross-carrier scheduling carrier aggregation configuration in which SCells are scheduled by PCells.

[0045] As shown in 221, a PCell DCI on a PDCCH(C) is detected in the PDCCH monitoring status of the search space on the PCell, and the DCI schedules a PCell PDSCH. The PDSCH may be in the same slot where the PDCCH transmitting the DCI is detected, or it may be in a later slot.

[0046] As shown in 222, the HARQ-ACK feedback (ACK or NACK) of the PCell PDSCH is mapped to the PCell uplink.

[0047] As shown in 223, the PCell DCI on PDCCH(C) is detected by the PDCCH monitoring status of the search space on PCell, and the DCI schedules the SCell PDSCH.

[0048] As shown in 224, the HARQ-ACK feedback (ACK or NACK) of the SCell PDSCH is mapped to the PCell uplink.

[0049] The rules for mapping HARQ-ACK feedback for PDSCH in carrier aggregation settings are shown in Table 1 below. When a PUCCH SCell is configured, for cells in the same group that have a PUCCH SCell, the PUCCH SCell behaves as a PCell in Table 1 below.

[0050] [Table 1]

[0051] Note that the CA configuration may be for DL ​​only, in which case only the PCell has any uplink, and the HARQ-ACK feedback is always on the PCell uplink. The basic principle is that the response of all downlinks is mapped to one uplink.

[0052] Figure 2C illustrates a schematic diagram of cell grouping into DRX groups, in which several exemplary embodiments of the present disclosure may be implemented. As shown in Figure 2C, there are a first DRX group and a second DRX group. The first DRX group includes PCell, SCell 1, and SCell 2, while the second DRX group includes SCell 3 and SCell 4.

[0053] The total number of cells in Figure 2C is 5, but this is for illustrative purposes only and does not imply any limitations; understand that there may be more or fewer cells, for example. Each DRX group contains two or more cells, but in some other cases, there may be only one cell within a DRX group. In some examples, within a carrier aggregation configuration, cells may be grouped into DRX groups. All cells in a CA configuration may be mapped to the same DRX group, or each DRX group may consist of a single cell, or there may be an intermediate form.

[0054] Only DL is shown for each cell shown in Figure 2C, but please understand that this is for illustrative purposes only and does not imply any limitations. For example, PCell has both UL and DL. For example, one of S cells 1-4 may also have both UL and DL.

[0055] Figure 3 illustrates an example of process flow 300 according to some exemplary embodiments of the present disclosure. For the purposes of discussion, process flow 300 will be described with reference to Figure 1. Process flow 300 involves terminal device 110 and network device 120. Although process flow 300 is depicted within the network environment 100 of Figure 1, it should be understood that this process flow may be similarly applicable to other communication scenarios.

[0056] Network device 120 sends DCI 312 to terminal device 110, DCI 312 may indicate that PDCCH monitoring should be skipped for a duration on the scheduling cell, which schedules PDSCH transmission on the scheduled cell. On the other side of the communication, terminal device 110 receives DCI 312. The duration may be configured within the DCI or pre-configured, for example, by RRC signaling.

[0057] Terminal device 110 sends a NACK 322 to network device 120, and the NACK may be associated with a PDSCH transmission on the scheduled cell. On the other side of the communication, network device 120 receives the NACK 322.

[0058] In addition, terminal device 110 restarts PDCCH monitoring or terminates PDCCH skipping on at least one serving cell, for example, on at least one scheduling cell, in 330. Similarly, network device 120 determines, by terminal device 110, at least one serving cell on which PDCCH monitoring is restarted or PDCCH skipping is terminated in 340.

[0059] In some exemplary embodiments, the NACK may be transmitted over the physical uplink control channel (PUCCH) or physical uplink sharing channel (PUSCH) of the feedback cell. For example, the feedback cell may be a special cell or a PUCCH secondary cell (SCell).

[0060] In some exemplary embodiments, the scheduling cell and the scheduled cell are the same serving cell. In some examples, when self-scheduling is used, the scheduling cell and the scheduled cell may be the same.

[0061] In some other exemplary embodiments, the scheduling cell and the cell being scheduled may differ, for example, when cross-carrier scheduling is used.

[0062] In some exemplary embodiments, the terminal device 110 may resume PDCCH monitoring or terminate PDCCH skipping on at least one serving cell after transmitting a NACK, for example, after the last time unit (such as the last code) of the PUCCH or PUSCH providing the NACK, or after a known time duration after that last time unit. For example, the terminal device 110 may resume PDCCH monitoring or terminate PDCCH skipping on at least one serving cell at the beginning of a first slot after the last code of the PUCCH or PUSCH providing the NACK.

[0063] In some exemplary embodiments, at least one serving cell includes a scheduling cell that schedules PDSCH transmissions. As such, it is proposed that the termination of PDSCH skipping for the scheduling serving cell for PDSCH transmissions after at least a NACK is sent for the PDSCH transmission. As a result, the terminal device can discover the PDSCH resources for retransmission following the NACK.

[0064] In some examples, at least one serving cell may consist only of a scheduling cell, i.e., a scheduling serving cell. For example, if terminal device 120 detects a DCI format that provides a PDCCH monitoring conformance field that indicates skipping PDCCH monitoring for a duration on a scheduling cell that has scheduled a PDSCH to which a NACK is sent, and then terminal device 120 sends a PUCCH or PUSCH that provides a NACK for the PDSCH transmission of the scheduled cell, then terminal device 120 will resume PDCCH monitoring (or terminate PDCCH skipping) only on the scheduling cell that has scheduled a PDSCH to which a NACK is sent.

[0065] Therefore, from the perspective of UE power consumption, terminal device 120 only needs to wake up for scheduling cells that can schedule the retransmission of NACKed PDSCH.

[0066] In some other exemplary embodiments, at least one serving cell may include multiple cells within the Discontinuous Reception (DRX) group to which the scheduling cell belongs.

[0067] In some examples, if terminal device 120 detects a DCI format that provides a PDCCH monitoring conformance field that indicates skipping PDCCH monitoring for a duration on a scheduling cell that scheduled a PDSCH to which a NACK is sent, and then terminal device 120 sends a PUCCH or PUSCH that provides a NACK for the scheduled cell's PDSCH transmission, then terminal device 120 will resume PDCCH monitoring (or terminate PDCCH skipping) on ​​the cell in the DRX group corresponding to the NACK sent by the scheduling cell that scheduled the PDSCH.

[0068] For example, referring to Figure 2C, if the scheduling cell is a PCell in the first DRX group, then at least one serving cell includes a PCell, SCell 1, and SCell 2. In other words, terminal device 110 can resume PDCCH monitoring (or terminate PDCCH skipping) on ​​PCell, SCell 1, and SCell 2.

[0069] As such, it enables network feasibility by allowing the selection of a PDSCH from another cell to be retransmitted as a new transmission.

[0070] In some other exemplary embodiments, at least one serving cell may include all serving cells of the Media Access Control (MAC) entity to which the scheduling cell belongs.

[0071] In some examples, if terminal device 120 detects a DCI format that provides a PDCCH monitoring conformance field indicating to skip PDCCH monitoring for a duration on a scheduling cell that has scheduled a PDSCH to which a NACK is sent, and then terminal device 120 sends a PUCCH or PUSCH providing a NACK for the scheduled cell's PDSCH transmission, terminal device 120 will resume PDCCH monitoring (or terminate PDCCH skipping) on ​​all serving cells of the MAC entity. As such, it enables network implementation that chooses to retransmit a PDSCH from another cell as a new transmission.

[0072] In some other exemplary embodiments, at least one serving cell may include multiple cells, each of which can function as a scheduling cell.

[0073] In some examples, if terminal device 120 detects a DCI format that provides a PDCCH monitoring conformance field that indicates skipping PDCCH monitoring for a duration on a scheduling cell that has scheduled a PDSCH to which a NACK is sent, and then terminal device 120 sends a PUCCH or PUSCH that provides a NACK for the scheduled cell's PDSCH transmission, then terminal device 120 will resume PDCCH monitoring (or terminate PDCCH skipping) on ​​all cells that could function as scheduling cells for the cell to which the PDSCH is scheduled.

[0074] For example, referring to Figure 2A, if the PDCCH transmission is on a PCell, i.e., a scheduled cell, and the scheduling cell can be a PCell or an SCell, then at least one serving cell includes both a PCell and an SCell. In other words, terminal device 110 can resume PDCCH monitoring (or terminate PDCCH skipping) on ​​both the PCell and the SCell.

[0075] For example, in a single carrier aggregation (CA) configuration, a serving cell PDSCH can be self-scheduled or cross-carrier scheduled. For instance, in a single carrier aggregation (CA) configuration, one DCI can schedule PDSCHs across multiple cells, while each cell also monitors a self-scheduling DCI.

[0076] Referring to Figure 3, if a NACK is sent and PDCCH monitoring is resumed by terminal device 110 on at least one serving cell, or if PDCCH skipping is terminated, network device 120 may retransmit the PDSCH again. Thus, transmission delay may be reduced and transmission efficiency may be improved.

[0077] An embodiment with reference to Figure 3 provides a solution for PDCCH skipping after NACK transmission in multi-cell operation. In some embodiments, a terminal device may receive a DCI indicating to skip PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmission on the scheduled cell. If a NACK for PDSCH transmission on the scheduled cell has been transmitted, the terminal device may further resume PDCCH monitoring or terminate PDCCH skipping on at least one serving cell, the at least one serving cell including a scheduling cell that schedules PDSCH transmission. In such a case, retransmission may be performed consecutively on at least one serving cell. Thus, transmission efficiency can be guaranteed.

[0078] Figure 4 illustrates a flowchart of Method 400 as implemented in a terminal device according to some exemplary embodiments of the present disclosure. For the purposes of discussion, Method 400 will be described from the perspective of terminal device 110 with reference to Figure 1.

[0079] In block 410, terminal device 110 receives a DCI from a network device indicating to skip PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmission on the scheduled cell. In block 420, if a NACK for PDSCH transmission on the scheduled cell has been sent, terminal device 110 resumes PDCCH monitoring on at least one serving cell or terminates PDCCH skipping, where at least one serving cell includes a scheduling cell that schedules PDSCH transmission.

[0080] In some exemplary embodiments, at least one serving cell includes multiple cells within the DRX group to which the scheduling cell belongs (such as all cells within the DRX group).

[0081] In some exemplary embodiments, at least one serving cell includes all serving cells of the MAC entity to which the scheduling cell belongs.

[0082] In some exemplary embodiments, at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

[0083] In some exemplary embodiments, the NACK is transmitted on the PUCCH or PUSCH of the feedback cell. In some exemplary embodiments, the feedback cell is a special cell or PUCCH SCell.

[0084] In some exemplary embodiments, the scheduling cell and the scheduled cell are the same serving cell. In some exemplary embodiments, the scheduling cell and the scheduled cell are different.

[0085] Figure 5 illustrates a flowchart of Method 500 as implemented in a network device according to some exemplary embodiments of the present disclosure. For the purposes of discussion, Method 500 will be described from the perspective of network device 120 with reference to Figure 1.

[0086] In block 510, the network device 120 sends a DCI to the terminal device indicating to skip PDCCH monitoring for a duration on the scheduling cell that schedules PDSCH transmission on the scheduled cell. In block 520, if a NACK for PDSCH transmission on the scheduled cell is received, the network device 120 determines, by the terminal device, at least one serving cell on which PDCCH monitoring will be resumed or PDCCH skipping will be terminated, the at least one serving cell which includes the scheduling cell that schedules PDSCH transmission.

[0087] In some exemplary embodiments, at least one serving cell includes multiple cells within the DRX group to which the scheduling cell belongs (such as all cells within the DRX group).

[0088] In some exemplary embodiments, at least one serving cell includes all serving cells of the MAC entity to which the scheduling cell belongs.

[0089] In some exemplary embodiments, at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

[0090] In some exemplary embodiments, the NACK is transmitted on the PUCCH or PUSCH of the feedback cell. In some exemplary embodiments, the feedback cell is a special cell or PUCCH SCell.

[0091] In some exemplary embodiments, the scheduling cell and the scheduled cell are the same serving cell. In some exemplary embodiments, the scheduling cell and the scheduled cell are different.

[0092] In some exemplary embodiments, an apparatus capable of carrying out Method 400 (e.g., a terminal device 110) may include means for carrying out each step of Method 400. The means can be carried out in any preferred form. For example, the means can be carried out in a circuit or a software module.

[0093] In some exemplary embodiments, the device includes means for receiving a DCI from a network device indicating to skip PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmissions on a scheduled cell, and means for resuming PDCCH monitoring or terminating PDCCH skipping on at least one serving cell based on the determination that a negative response (NACK) for PDSCH transmissions on a scheduled cell has been sent, wherein at least one serving cell includes a scheduling cell that schedules PDSCH transmissions.

[0094] In some exemplary embodiments, at least one serving cell includes multiple cells within the DRX group to which the scheduling cell belongs (such as all cells within the DRX group).

[0095] In some exemplary embodiments, at least one serving cell includes all serving cells of the MAC entity to which the scheduling cell belongs.

[0096] In some exemplary embodiments, at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

[0097] In some exemplary embodiments, the NACK is transmitted on the PUCCH or PUSCH of the feedback cell. In some exemplary embodiments, the feedback cell is a special cell or PUCCH SCell.

[0098] In some exemplary embodiments, the scheduling cell and the scheduled cell are the same serving cell. In some exemplary embodiments, the scheduling cell and the scheduled cell are different.

[0099] In some exemplary embodiments, an apparatus capable of carrying out Method 500 (for example, a network device 120) may include means for carrying out each step of Method 500. The means can be carried out in any preferred form. For example, the means can be carried out in a circuit or a software module.

[0100] In some exemplary embodiments, the apparatus includes means for sending a DCI to a terminal device that indicates skipping PDCCH monitoring for a duration on a scheduling cell that schedules PDSCH transmission on a scheduled cell, and means for the terminal device to determine, based on the determination that a NACK for PDSCH transmission on a scheduled cell has been received, at least one serving cell on which PDCCH monitoring will be resumed or PDCCH skipping will be terminated, the at least one serving cell including a scheduling cell that schedules PDSCH transmission.

[0101] In some exemplary embodiments, at least one serving cell includes multiple cells within the DRX group to which the scheduling cell belongs (such as all cells within the DRX group).

[0102] In some exemplary embodiments, at least one serving cell includes all serving cells of the MAC entity to which the scheduling cell belongs.

[0103] In some exemplary embodiments, at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

[0104] In some exemplary embodiments, the NACK is transmitted on the PUCCH or PUSCH of the feedback cell. In some exemplary embodiments, the feedback cell is a special cell or PUCCH SCell.

[0105] In some exemplary embodiments, the scheduling cell and the scheduled cell are the same serving cell. In some exemplary embodiments, the scheduling cell and the scheduled cell are different.

[0106] Figure 6 illustrates a simplified block diagram of a device 600 suitable for carrying out some exemplary embodiments of the present disclosure. The device 600 may be provided for carrying out a communication device, for example, a terminal device 110 or a network device 120 as shown in Figure 1. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processors 610, and one or more communication modules 640 coupled to the processors 610.

[0107] The communication module 640 is for bidirectional communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communication with other network elements.

[0108] The processor 610 can be any type suitable for a local technology network and may include, in non-limiting examples, one or more of the following: a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multicore processor architecture. The device 600 may have multiple processors, such as application-specific integrated circuit chips that are temporally slaved to a clock that synchronizes the main processor.

[0109] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact discs (CDs), digital video discs (DVDs), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random-access memory (RAM) 622, and other volatile memories that do not persist during the power-down period.

[0110] The computer program 630 includes computer-executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 624. The processor 610 can perform any preferred operations and processes by loading the program 630 into the RAM 622.

[0111] Embodiments of the present disclosure may be implemented using program 630 so that device 600 can perform any process of the present disclosure, as discussed with reference to Figures 3 to 5. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0112] In some exemplary embodiments, the program 630 may be tangibly contained in a computer-readable medium that may be contained within device 600 (such as in memory 620), or in another storage device accessible by device 600. Device 600 may read the program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disk, CD, DVD, and similar.

[0113] Figure 7 illustrates a block diagram of an example of a computer-readable medium 700 according to some exemplary embodiments of the present disclosure. The computer-readable medium 700 stores a program 630. Although the computer-readable medium 700 is depicted in the form of a CD or DVD in Figure 7, it should be noted that the computer-readable medium 700 may be any other form suitable for holding or storing the program 630.

[0114] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Various embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or any other graphical descriptions, but it should be understood that any blocks, apparatus, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controller or other computing device, or any combination thereof, as non-limiting examples.

[0115] This disclosure also provides at least one computer program product that is tangibly stored in a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as those contained in a program module, which are executed on a device on a target real or virtual processor to perform a method as described above with reference to any of Figures 4-5. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, or the like that perform a particular task or implement a particular abstract data type. The functions of program modules can be combined or divided among program modules as desired in various embodiments. The machine-executable instructions for a program module can be executed on a local device or a distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0116] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and as a result, when executed by the processor or controller, the program code will perform functions / operations specified in flowcharts and / or block diagrams. The program code may run entirely on a machine, partially on a machine, as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0118] A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any preferred combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any preferred combination thereof. The term “non-transient,” as used herein, refers to the limitations of the medium itself (i.e., tangible and not signaling), as opposed to limitations on data storage persistence (e.g., RAM vs. ROM).

[0119] Furthermore, while the operations are described in a specific order, this should not be understood as requiring that such operations be performed in a specific order or sequentially as shown, or that all illustrated operations be performed, in order to achieve a desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, while some specific embodiment details are included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any preferred partial combination in multiple embodiments.

[0120] While this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as set forth in the attached claims is not necessarily limited to the specific features and actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. Terminal device, At least one processor, At least one memory to store instructions and The instructions, when executed by the at least one processor, are transmitted to the terminal device, Receiving Downlink Control Information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmission on a scheduled cell, and Based on the determination that a negative response (NACK) for the PDSCH transmission has been sent on the scheduled cell, restart the PDCCH monitoring on at least one serving cell or terminate the PDCCH skipping. A terminal device in which at least one serving cell includes the scheduling cell that schedules the PDSCH transmission.

2. The terminal device according to claim 1, wherein the at least one serving cell includes a plurality of cells within the intermittent receive (DRX) group to which the scheduling cell belongs.

3. The terminal device according to claim 1, wherein the at least one serving cell includes all serving cells of the media access control (MAC) entity to which the scheduling cell belongs.

4. The terminal device according to claim 1, wherein the at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

5. The terminal device according to any one of claims 1 to 4, wherein the NACK is transmitted over the physical uplink control channel (PUCCH) or physical uplink sharing channel (PUSCH) of the feedback cell.

6. The terminal device according to claim 5, wherein the feedback cell is a special cell or a PUCCH secondary cell (SCell).

7. The terminal device according to any one of claims 1 to 6, wherein the scheduling cell and the scheduled cell are the same serving cell.

8. A network device, At least one processor, At least one memory to store instructions and The instructions, when executed by the at least one processor, provide at least the network device with Sending Downlink Control Information (DCI) to a terminal device that indicates to skip monitoring the Physical Downlink Control Channel (PDCCH) for a duration on a scheduling cell that schedules Physical Downlink Shared Channel (PDSCH) transmission on the scheduled cell, and Based on the determination that a negative response (NACK) for the PDSCH transmission has been received on the scheduled cell, the terminal device determines at least one serving cell on which the PDCCH monitoring will be resumed or PDCCH skipping will be terminated. A network device comprising the at least one serving cell, which includes the scheduling cell that schedules the PDSCH transmission.

9. The network device according to claim 8, wherein the at least one serving cell includes a plurality of cells within the intermittent receive (DRX) group to which the scheduling cell belongs.

10. The network device according to claim 8, wherein the at least one serving cell includes all serving cells of the media access control (MAC) entity to which the scheduling cell belongs.

11. The network device according to claim 8, wherein the at least one serving cell includes a plurality of cells, each of which can function as a scheduling cell.

12. The network device according to any one of claims 8 to 11, wherein the NACK is transmitted over the physical uplink control channel (PUCCH) or physical uplink sharing channel (PUSCH) of the feedback cell.

13. The network device according to claim 12, wherein the feedback cell is a special cell or a PUCCH secondary cell (SCell).

14. The network device according to any one of claims 8 to 13, wherein the scheduling cell and the scheduled cell are the same serving cell.

15. In a terminal device, receiving downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmission on a scheduled cell, and Based on the determination that a negative response (NACK) for the PDSCH transmission has been sent on the scheduled cell, restart the PDCCH monitoring on at least one serving cell, or terminate the PDCCH skipping. A method comprising, wherein the at least one serving cell includes the scheduling cell that schedules the PDSCH transmission.

16. In a network device, send downlink control information (DCI) to a terminal device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmission on the scheduled cell, and Based on the determination that a negative response (NACK) for the PDSCH transmission has been received on the scheduled cell, the terminal device determines at least one serving cell on which the PDCCH monitoring will be resumed or PDCCH skipping will be terminated. A method comprising, wherein the at least one serving cell includes the scheduling cell that schedules the PDSCH transmission.

17. It is a device, A terminal device provides means for receiving downlink control information (DCI) from a network device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmission on a scheduled cell, and Based on the determination that a negative response (NACK) for the PDSCH transmission has been transmitted on the scheduled cell, means for restarting the PDCCH monitoring or terminating PDCCH skipping on at least one serving cell An apparatus comprising, wherein the at least one serving cell includes the scheduling cell that schedules the PDSCH transmission.

18. It is a device, A network device provides means for transmitting downlink control information (DCI) to a terminal device that indicates skipping physical downlink control channel (PDCCH) monitoring for a duration on a scheduling cell that schedules physical downlink shared channel (PDSCH) transmission on a scheduled cell, and Means for determining, by the terminal device, at least one serving cell in which PDCCH monitoring is resumed or PDCCH skipping is terminated, based on the determination that a negative response (NACK) for the PDSCH transmission has been received on the scheduled cell. An apparatus comprising, wherein the at least one serving cell includes the scheduling cell that schedules the PDSCH transmission.

19. A computer-readable medium containing program instructions for causing a device to carry out at least the method according to claim 15 or 16.

Images