A communication method and device

Abstract

A communication method and apparatus are used to clarify how a terminal device monitors PDCCH after receiving DCI during a retransmission period. The terminal device receives a first DCI from a network device, and after receiving the first DCI, receives a second DCI from the network device within a second time domain length, and determines that the terminal device does not monitor PDCCH within a third time domain length based on the second DCI; the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length; the second time domain length belongs to the first time domain length; the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length. In this way, when the terminal device receives DCI during the retransmission period, the time for skipping PDCCH indicated by the initial DCI can be kept valid.

Description

[0001] This application claims priority to a Chinese patent application filed with the China Patent Office on June 16, 2021, with application number 202110665649.5 and invention name “A method for indicating PDCCH adaptation”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0003] Before the network device and the terminal device transmit data, the network device will send data scheduling information to the terminal device, such as the physical downlink control channel (PDCCH). In order to avoid losing scheduling information, the terminal device needs to frequently monitor the PDCCH according to the configuration of the network device. Frequent monitoring of the PDCCH by the terminal device will result in higher power consumption of the terminal device. At present, research on power consumption saving of terminal devices is becoming more and more common, and detailed optimization solutions to reduce power consumption of terminal devices have become a research direction in the industry. Summary of the invention

[0004] The present application provides a communication method and apparatus for clarifying how a terminal device monitors a PDCCH after receiving a DCI during a retransmission period.

[0005] In a first aspect, the present application provides a communication method, which can be applied to a terminal device, a processor, a chip or a functional module in a terminal device, etc. The method may include: receiving a first downlink control information (DCI) from a network device, after receiving the first DCI, receiving a second DCI from the network device within a second time domain length, and determining that the terminal device does not monitor the PDCCH within a third time domain length according to the second DCI; wherein the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within the first time domain length; the second time domain length belongs to the first time domain length; the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0006] By using the above method, when DCI is received during the retransmission period, the end time of skipping PDCCH indicated by the initial transmission DCI can be kept valid.

[0007] In one possible design, the second DCI includes a first field, and a first value of the first field indicates that the terminal device does not switch the search space group to monitor PDCCH; the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length, which may be specifically: the first DCI indicates that the terminal device monitors PDCCH according to the first search space group, and the first search space group does not include the search space; then, according to the second DCI, it is determined not to monitor PDCCH within the third time domain length. The specific method may be: according to the first field in the second DCI being the first value, it is determined not to monitor PDCCH within the third time domain length.

[0008] Through the above method, when the network device sends the second DCI within the retransmission period (that is, within the second time domain length), the network device can set the first field in the second DCI to the first value to indicate not to switch the search space group to monitor PDCCH, so as to achieve the end time of not affecting the terminal device not monitoring PDCCH.

[0009] In one possible design, the second value of the first field indicates that the terminal device monitors PDCCH according to a second search space group, where the second search space group includes at least one search space.

[0010] In one possible design, the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length. Specifically, it may be: the first DCI indicates that the terminal device monitors PDCCH according to a third search space group, and the third search space group does not include a search space; the second DCI indicates that the terminal device monitors PDCCH according to the third search space group; and then, according to the second DCI, it is determined that PDCCH is not monitored within the third time domain length. The specific method may be: determine that a first timer is running when the second DCI is received, the first timer is not restarted, and determine that PDCCH is not monitored within the third time domain length, wherein the first timer is related to the third search space.

[0011] Through the above method, when the terminal device is already monitoring or using the empty search space group (i.e., the third search space group), and is instructed by the network device to monitor PDCCH according to the empty search space group during the retransmission period, the running time of the first timer will not be affected, and the end time of not monitoring PDCCH can be kept unchanged.

[0012] In one possible design, when the first DCI is received, the first timer is not running, and the first timer is started or restarted. In this way, the duration of not monitoring the PDCCH can be controlled by the first timer.

[0013] In one possible design, it is determined based on the second DCI that PDCCH is not monitored within the third time domain length. The specific method may be: when the second DCI indicates the monitoring method of PDCCH, it is determined that the monitoring method of PDCCH indicated by the second DCI is not effective; it is determined that PDCCH is not monitored within the third time domain length. In this way, the terminal device itself is instructed by the first DCI not to monitor PDCCH within the first time domain length. When the indication of the second DCI received during the retransmission period is not effective, the indication content of the first DCI is still valid, and the end time of the terminal device not monitoring PDCCH is still the end position of the first time domain length.

[0014] In one possible design, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation; based on the second DCI, it is determined not to monitor the PDCCH within the third time domain length. The specific method may be: based on the second field of the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

[0015] Through the above method, when the network device sends the second DCI within the retransmission period (that is, within the second time domain length), the network device can set the second field in the second DCI to the first value to indicate that the terminal device does not perform new operations, so as to achieve the end time of not affecting the terminal device's monitoring of PDCCH.

[0016] In one possible design, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0017] In one possible design, the second DCI indicates that PDCCH is monitored according to a fourth search space group, and the fourth search space group is the same as the currently monitored search space group; the fourth search space group includes at least one search space; according to the second DCI, it is determined that PDCCH is not monitored within the third time domain length, and the specific method may be: determining that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group; determining that PDCCH is not monitored within the third time domain length. In this way, the network device can indicate to the terminal device the search space group that the terminal device is currently monitoring or using, so that for the terminal device, no new indication is received, the monitored search space group remains unchanged, and the end time of not monitoring PDCCH remains unchanged.

[0018] In one possible design, the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the running time of a retransmission timer corresponding to a first hybrid automatic repeat request (HARQ) process; the first HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at a time when any HARQ process may retransmit, so as to avoid data retransmission failure of a certain HARQ process.

[0019] In one possible design, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the time during which the retransmission timer corresponding to the second HARQ process runs; the second HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at a time when any HARQ process may retransmit, thereby avoiding data retransmission failure of a certain HARQ process.

[0020] In one possible design, the second time domain length is the time for the retransmission timer corresponding to the third HARQ process to run; the third HARQ process is the HARQ process corresponding to the first DCI. This can shorten the monitoring time on the PDCCH and reduce the power consumption of the terminal device.

[0021] In one possible design, the first HARQ process is a downlink HARQ process.

[0022] In one possible design, the third HARQ process is a downlink HARQ process.

[0023] In one possible design, a third DCI is received from the network device within the second time domain length, and the third DCI is used to indicate successful transmission of uplink data.

[0024] In a second aspect, the present application provides a communication method, which can be applied to a network device, a processor, a chip or a functional module in a network device, etc. The method may include: sending a first downlink control information DCI to a terminal device, and after sending the first DCI, sending a second DCI to the terminal device within a second time domain length; the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within the first time domain length; the second time domain length belongs to the first time domain length; the second DCI is used by the terminal device to determine that the PDCCH is not monitored within a third time domain length, and the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0025] Through the above method, when the terminal device receives DCI during the retransmission period, the end time of skipping PDCCH indicated by the initial DCI transmission can remain valid.

[0026] In one possible design, the second DCI includes a first field, and a first value of the first field indicates not to switch the search space group to monitor PDCCH; the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length, which may be specifically: the first DCI indicates that the terminal device monitors PDCCH according to the first search space group, and the first search space group does not include a search space.

[0027] Through the above method, when the network device sends the second DCI within the retransmission period (that is, within the second time domain length), the network device can set the first field in the second DCI to the first value to indicate not to switch the search space group to monitor PDCCH, so as to achieve the end time of not affecting the terminal device not monitoring PDCCH.

[0028] In one possible design, the second value of the first field indicates that the terminal device monitors PDCCH according to a second search space group, where the second search space group includes at least one search space.

[0029] In one possible design, the first DCI instructs the terminal device not to monitor PDCCH within the first time domain length, which may be specifically: the first DCI instructs the terminal device to monitor PDCCH according to a third search space group, and the third search space group does not include a search space; the second DCI instructs the terminal device to monitor PDCCH according to the third search space group; wherein, when the second DCI is sent, the first timer is running, the first timer is not restarted, and the first timer is related to the third search space.

[0030] Through the above method, when the terminal device is already monitoring or using the empty search space group (i.e., the third search space group), and is instructed by the network device to monitor PDCCH according to the empty search space group during the retransmission period, the running time of the first timer will not be affected, and the end time of the terminal device not monitoring PDCCH can be kept unchanged.

[0031] In one possible design, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation. In this way, when the network device sends the second DCI within the retransmission period (i.e., within the second time domain length), the network device can set the second field in the second DCI to the first value to indicate that the terminal device does not perform a new operation, so as to achieve an end time that does not affect the terminal device's non-monitoring of the PDCCH.

[0032] In one possible design, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0033] In one possible design, the second DCI indicates that the PDCCH is monitored according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space. In this way, the network device can indicate to the terminal device the search space group that the terminal device is currently monitoring or using, so that for the terminal device, no new indication is received, the monitored search space group remains unchanged, and the end time of not monitoring the PDCCH remains unchanged.

[0034] In one possible design, the second time domain length includes a first sub-time domain length, the first sub-time domain length is the time for which a retransmission timer corresponding to a first hybrid automatic repeat request HARQ process runs; the first HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at a time when any HARQ process may retransmit, thereby avoiding data retransmission failure of a certain HARQ process.

[0035] In one possible design, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the time during which the retransmission timer corresponding to the second HARQ process runs; the second HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at a time when any HARQ process may retransmit, thereby avoiding data retransmission failure of a certain HARQ process.

[0036] In one possible design, the second time domain length is the time for the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process to run; the third HARQ process is the HARQ process corresponding to the first DCI. This can shorten the time for the terminal device to monitor the PDCCH and reduce the power consumption of the terminal device.

[0037] In one possible design, the first HARQ process is a downlink HARQ process.

[0038] In one possible design, the third HARQ process is a downlink HARQ process.

[0039] In one possible design, a third DCI is sent to the terminal device within the second time domain length, and the third DCI is used to indicate successful transmission of uplink data.

[0040] In a third aspect, the present application further provides a communication device, which may be a terminal device, and which has the function of implementing the method in the first aspect or each possible design example of the first aspect. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0041] In one possible design, the structure of the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the above-mentioned first aspect or various possible design examples of the first aspect. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0042] In one possible design, the structure of the communication device includes a transceiver and a processor, and optionally also includes a memory, the transceiver is used to send and receive data, and is used to communicate and interact with other devices in the communication system, and the processor is configured to support the communication device to perform the corresponding functions in the above-mentioned first aspect or each possible design example of the first aspect. The memory is coupled to the processor, and stores the necessary program instructions and data for the communication device.

[0043] In a fourth aspect, the present application further provides a communication device, which may be a network device, and which has the function of implementing the method in the second aspect or each possible design example of the second aspect. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0044] In one possible design, the structure of the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions in the above-mentioned second aspect or each possible design example of the second aspect. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0045] In one possible design, the structure of the communication device includes a transceiver and a processor, and optionally a memory, the transceiver is used to send and receive data, and to communicate and interact with other devices in the communication system, and the processor is configured to support the communication device to perform the corresponding functions in the above second aspect or each possible design example of the second aspect. The memory is coupled to the processor, and stores the necessary program instructions and data for the communication device.

[0046] In a fifth aspect, an embodiment of the present application provides a communication system, which may include the terminal device and network device mentioned above.

[0047] In a sixth aspect, a computer-readable storage medium provided by an embodiment of the present application stores program instructions, and when the program instructions are run on a computer, the computer executes the method described in the first aspect of the embodiment of the present application and any possible design thereof, or the second aspect and any possible design thereof. Exemplarily, the computer-readable storage medium can be any available medium that can be accessed by a computer. Taking this as an example but not limited to: a computer-readable medium may include a non-transient computer-readable medium, a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a CD-ROM or other optical disk storage, a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer.

[0048] In the seventh aspect, an embodiment of the present application provides a computer program product including computer program code or instructions, which, when running on a computer, enables the computer to implement the method described in the above-mentioned first aspect or any possible design of the first aspect, or the above-mentioned second aspect or any possible design of the second aspect.

[0049] In an eighth aspect, the present application also provides a chip, comprising a processor, wherein the processor is coupled to a memory, and is used to read and execute program instructions stored in the memory, so that the chip implements the method described in the above-mentioned first aspect or any possible design of the first aspect, or the above-mentioned second aspect or any possible design of the second aspect.

[0050] For each of the above-mentioned aspects from the third to the eighth aspect and the technical effects that may be achieved by each of the aspects, please refer to the above-mentioned description of the technical effects that can be achieved by the first aspect or the various possible schemes in the first aspect, or the second aspect or the various possible schemes in the second aspect, and no repetition will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 A schematic diagram of the architecture of a communication system provided for this application;

[0052] Figure 2 A schematic diagram of skipping PDCCH monitoring provided by the present application;

[0053] Figure 3 A schematic diagram of a search space group switching provided by the present application;

[0054] Figure 4 A schematic diagram of HARQ retransmission provided by this application;

[0055] Figure 5 A schematic diagram of monitoring PDCCH during a retransmission period provided by the present application;

[0056] Figure 6 A flow chart of a communication method provided for this application;

[0057] Figure 7a A schematic diagram of a second time domain length provided by the present application;

[0058] Figure 7b A schematic diagram of another second time domain length provided for this application;

[0059] Figure 8 A schematic diagram of another second time domain length provided for this application;

[0060] Fig. 9 A schematic diagram of monitoring PDCCH during a retransmission period provided by the present application;

[0061] Fig.10 A schematic diagram of monitoring a retransmitted DCI during a retransmission period provided by the present application;

[0062] Fig.11 A flow chart of another communication method provided by the present application;

[0063] Fig.12 A schematic diagram of a timer provided for this application;

[0064] Fig.13 A flow chart of another communication method provided by the present application;

[0065] Fig.14 A schematic diagram of the structure of a communication device provided by the present application;

[0066] Fig.15 A structural diagram of a communication device provided in this application. DETAILED DESCRIPTION

[0067] The present application will be described in further detail below in conjunction with the accompanying drawings.

[0068] The embodiments of the present application provide a communication method and apparatus for clarifying how a terminal device monitors a PDCCH after receiving a DCI during a retransmission period. The method and apparatus described in the present application are based on the same technical concept. Since the principles of solving problems by the method and apparatus are similar, the implementation of the apparatus and the method can refer to each other, and the repeated parts will not be repeated.

[0069] In the description of this application, the words "first", "second", etc. are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order. For example, the third may appear before the second in this application, and this application does not limit this.

[0070] In the description of the present application, "at least one" means one or more, and more means two or more.

[0071] In order to more clearly describe the technical solution of the embodiments of the present application, the communication method and device provided in the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0072] Figure 1 The architecture of the communication system involved in the embodiment of the present application is shown, and the architecture of the communication system includes a network device and a terminal device, wherein:

[0073] The network device is a device with a wireless transceiver function or a chip that can be set in the network device. The network device includes but is not limited to: a base station (generation node B, gNB), a radio network controller (radio network controller, RNC), a node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (for example, home evolved NodeB, or homeNode B, HNB), a baseband unit (baseband unit, BBU), an access point (access point, AP) in a wireless fidelity (wireless fidelity, Wi-Fi) system, a wireless relay node, a wireless backhaul node, a transmission point (transmission and reception point, TRP or transmission point, TP), etc., and can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.

[0074] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio unit (RU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB, for example, the CU implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and the DU implements the functions of the radio link control (RLC), media access control (MAC) and physical (PHY) layers. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling or PHCP layer signaling, can also be considered to be sent by the DU, or by the DU+RU. It can be understood that the network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, and the CU can also be divided into a network device in the core network CN, without limitation.

[0075] The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a smart wearable device (smart glasses, smart watch, smart headset, etc.), a wireless terminal in smart home, etc., and may also be a chip or chip module (or chip system) that can be set in the above devices, etc. The embodiment of the present application does not limit the application scenario. In the present application, a terminal device having a wireless transceiver function and a chip that can be provided in the aforementioned terminal device are collectively referred to as a terminal device.

[0076] It should be noted that Figure 1 The communication system shown may be, but is not limited to, a fourth generation (4G) system, a fifth generation (5G) system, such as a new generation of wireless access technology (NR). Optionally, the method of the embodiment of the present application is also applicable to various future communication systems, such as a sixth generation (6G) system or other communication networks.

[0077] In NR, the process of data transmission can be described as follows:

[0078] When a network device schedules a terminal device to receive downlink data, or when a network device schedules a terminal device to send uplink data, it will first send downlink control information (DCI). The DCI contains a data scheduling information, which indicates the transmission parameters of the physical downlink shared channel (PDSCH) (which contains downlink data) or the physical uplink shared channel (PUSCH) (which contains uplink data). These transmission parameters include the time-frequency domain resource location of PDSCH / PUSCH. Specifically, the above DCI is carried in the PDCCH. For downlink data, the network device will indicate the K0 value through the time domain resource allocation (TDRA) field in the DCI to determine the time slot interval between the PDCCH and the PDSCH; for uplink data, the network device will indicate the K2 value through the TDRA field in the DCI to determine the time slot interval between the PDCCH and the PUSCH.

[0079] The network device sends downlink data at the time-frequency domain resource location indicated in the DCI, and the terminal device receives it at the corresponding location; or, the terminal device sends uplink data at the time-frequency domain resource location indicated in the DCI, and the network device receives it at the corresponding location.

[0080] When receiving its own DCI, the terminal device needs to blindly detect (blind detect, BD) the PDCCH sent to it in the downlink control area, that is, the terminal device monitors many PDCCH candidate positions (PDCCH candidate) to find out whether there is one sent to it. A group of candidate positions that the terminal device needs to blindly detect constitutes a search space (searchspace set, SSS), which can also be called a search space set. Depending on the configuration of the network device, the terminal device may monitor one (group) or more (groups) of search spaces to find out whether there is a PDCCH sent to it. Among them, the location where the terminal device needs to monitor the PDCCH can also be called a PDCCH monitoring occasion.

[0081] If there is no service in the terminal device for a period of time, that is, no downlink data or uplink data needs to be transmitted, the terminal device cannot receive the PDCCH sent to itself even if it monitors the PDCCH. If the terminal device still monitors the PDCCH during these times, it will cause power consumption of the terminal device.

[0082] In order to reduce the power consumption of terminal devices, one possible solution is to introduce the concept of PDCCH skipping. Specifically, the network device can send an indication message to the terminal device, indicating that the terminal device can skip PDCCH monitoring for a period of time. The terminal device skipping PDCCH monitoring for a period of time can be equivalently described as the terminal device not monitoring PDCCH for a period of time. This period of time when PDCCH is not monitored can be called skipping duration. For example Figure 2 As shown in the schematic diagram of skipping PDCCH monitoring, the terminal device originally needs to monitor PDCCH in each time slot. When the terminal device is instructed by the network device not to monitor PDCCH for a period of time, the terminal device may not monitor PDCCH during the instructed period of time.

[0083] Another solution to reduce the power consumption of the terminal device may be: the network device may send an indication message to the terminal device, instructing the terminal device to switch between two pre-configured search spaces. For example, Figure 3 As shown, the terminal device is configured with 2 groups of search spaces, the period corresponding to search space group 1 is 1 time slot, and the period corresponding to search space group 2 is 4 time slots. The network device can send an indication message to the terminal device, indicating that the terminal device can switch from monitoring search space group 1 to monitoring search space group 2, thereby reducing the number of PDCCH monitoring times to save power consumption of the terminal device.

[0084] Both of the above solutions can achieve the purpose of "reducing PDCCH monitoring". However, in the first solution, the method of skipping PDCCH is more flexible and suitable for scheduling changes on a small time scale (i.e., changes with or without scheduling are more frequent); while in the second solution, the search space switching (hereinafter collectively referred to as search space set group switching (SSSG) switching) is suitable for situations with larger time scale changes. In order to obtain the benefits of the above two methods at the same time, it is possible to consider supporting both functions at the same time. Exemplarily, the following three methods can be used to support the above two functions:

[0085] Method 1: Support SSSG switching and use SSSG switching to implement the function of skipping PDCCH. For example, the network device can configure an empty SSSG (which can be called an empty SSSG or a dormant SSSG) for the terminal device. For example, the empty SSSG can be numbered as SSSG0 (which does not include any search space). The network device can instruct the terminal device to switch to using SSSG0. The terminal device will not monitor PDCCH when using SSSG0. At the same time, the network device configures or indicates a timer (timer) or time length, so that the terminal device automatically switches out of SSSG0 after using SSSG0 for a period of time, thereby achieving the effect of skipping PDCCH monitoring for a period of time.

[0086] Method 2: Explicitly support the functions of SSSG switching and skipping PDCCH. For example, the network device indicates to the terminal device whether to skip PDCCH or SSSG switching through a flag bit, and then uses other bits to indicate the specific content of skipping PDCCH or SSSG switching.

[0087] Method 3: Explicitly support the functions of SSSG switching and skipping PDCCH. For example, the network device performs joint encoding to indicate skipping PDCCH and SSSG switching. For example, M bits are used to indicate 2 M There are three states, each of which can be configured to skip a period of time and / or switch to a certain SSSG.

[0088] NR supports hybrid automatic repeat request (HARQ) retransmission. The specific HARQ process is as follows:

[0089] For downlink transmission, the terminal device sends HARQ feedback to the network device to indicate whether the PDSCH is received successfully. If the network device determines that the terminal device fails to decode the PDSCH, the network device can schedule the retransmission of the PDSCH. Since the network device determines the content carried in the HARQ feedback (i.e., the terminal device fails to receive the PDSCH), and it takes a certain amount of time for the network device to send the PDCCH to schedule the retransmission of the PDSCH, the network device will definitely not schedule the retransmission of the data packet during this period of time. Even if the terminal device monitors the retransmission scheduling of the data packet during this period of time, it will not receive the retransmission scheduling. Therefore, the current standard defines a HARQ round trip time (RTT) timer. When the terminal device sends a negative acknowledgement (NACK) to the network device, the HARQ RTT timer is started. During the time when the HARQ RTT timer is running, the terminal device does not expect to receive the retransmission of the corresponding data packet. The standard also defines a HARQ retransmission timer, which will start after the HARQ RTT timer times out. If the terminal device sends a NACK to the network device, the terminal device will monitor and expect to receive the retransmission of the corresponding data packet during the running time of the HARQ retransmission timer.

[0090] For uplink transmission, NR does not support HARQ feedback. When the network device fails to receive the PUSCH transmission sent by the terminal device, the network device can directly send the PDCCH that schedules the PUSCH retransmission. Similar to downlink transmission, the NR standard also defines the HARQ RTT timer and HARQ retransmission timer for uplink transmission. However, since there is no HARQ feedback in uplink transmission, the terminal device will start the HARQ RTT timer immediately after the PUSCH is sent. During the time when the HARQ RTT timer is running, the terminal device does not expect to receive the retransmission of the corresponding data packet. The HARQ retransmission timer is similar to the downlink transmission. After the HARQ RTT timer times out, the HARQ retransmission timer will start. During the time when the HARQ retransmission timer is running, the terminal device will monitor and expect to receive the retransmission of the corresponding data packet.

[0091] In addition, in order to support the parallel processing of multiple data packets, NR supports multiple HARQ processes (HARQ process), each of which can correspond to a data packet, and the data packets corresponding to multiple processes are processed in parallel. Whether the data packet corresponding to a HARQ process is transmitted successfully or not, it will not affect the transmission of the data packet corresponding to another HARQ process. In order to ensure that the HARQ processes do not affect each other, the HARQ RTT timer and HARQ retransmission timer mentioned above are for each HARQ process (per HARQ process). That is, the network device will configure the corresponding HARQ RTT timer and HARQ retransmission timer for each HARQ process. At present, in NR, there are a maximum of 16 HARQ processes for uplink transmission and a maximum of 16 HARQ processes for downlink transmission.

[0092] In practice, when reducing the power consumption of terminal equipment through the above three methods, HARQ retransmission should also be combined. Figure 4 As shown, if the network device indicates to skip PDCCH in the last data scheduling DCI, that is, to instruct the terminal device not to monitor PDCCH for a period of time, the terminal device will not monitor PDCCH for a period of time, that is, Figure 4 The terminal device does not monitor the PDCCH during the time when the PDCCH is not monitored. If the terminal device HARQ feedback is NACK, and the network device sends a retransmission DCI during the time when the terminal device does not monitor the PDCCH (such as Figure 4 As shown), the retransmission DCI of the data scheduled by the network device cannot be received by the terminal device.

[0093] In order to enable the terminal device to receive the retransmission DCI of the data scheduled by the network device under the above circumstances, even if the terminal device is instructed not to monitor the PDCCH for a period of time (this can be achieved by instructing to skip the PDCCH or using an empty SSSG), the terminal device can still monitor the PDCCH during a certain period of time within this period. For the sake of ease of description, the time period during which the PDCCH is still monitored can be called a retransmission period, that is, the retransmission period is within the period of time during which the PDCCH is instructed not to be monitored, and the terminal device can still monitor the PDCCH during the retransmission period. It should be noted that the retransmission period can also be replaced by other names, or the time period may not be named, and this application does not limit this. In the description of this application, only the description of the retransmission period is taken as an example. Figure 5As shown, in either uplink (UL) transmission or downlink (DL) transmission, when the network device indicates in the last DCI of the scheduled data initial transmission that the terminal device does not monitor the PDCCH for a period of time, when the terminal device fails to transmit data and needs to retransmit, the terminal device will continue to monitor the PDCCH during the retransmission period of the time when the network device indicates not to monitor the PDCCH, so that the terminal device can receive the DCI of the scheduled data retransmission. In one implementation, Figure 5 As shown, the retransmission period can be defined as the time during which the HARQ retransmission timer runs.

[0094] It should be noted that Figure 5 The retransmission timer setting time length shown is the preset retransmission timer time length, and the HARQ retransmission timer running time can be less than or equal to the retransmission timer setting time length. When the retransmission timer has not timed out, when the terminal device detects the retransmission DCI, that is, when it detects the PDCCH, the retransmission timer stops. At this time, the retransmission timer running time is the retransmission period, that is, the time when the network device still monitors the PDCCH within a period of time when it indicates not to monitor the PDCCH. Figure 5 As shown, the case where the running time of the retransmission timer is less than the set time length of the retransmission timer is taken as an example.

[0095] However, if the retransmission period is defined as the time when the HARQ retransmission timer runs, since the HARQ retransmission timer is for each HARQ process, the specific definition of the retransmission period is not clear without considering the HARQ process. Therefore, the present application proposes a communication method to clarify the retransmission period.

[0096] It should be noted that, in the embodiments of the present application, the terminal device, or the processor in the terminal device, or the chip or chip system, or a functional module, etc., can be used to monitor or not monitor the PDCCH; the network device, or the processor in the network device, or the chip or chip system, or a functional module, etc., can be used to instruct the terminal device how to monitor the PDCCH. In the following embodiments, the method for monitoring the PDCCH provided in the present application is described in detail only by taking the terminal device and the network device as examples, but it is not intended to limit the present application.

[0097] Based on the above description, a communication method provided in an embodiment of the present application is used to clarify the retransmission period, which is applicable to Figure 1 The communication system shown. Figure 6 As shown, the specific process of the method may include:

[0098] Step 601: The network device sends a first DCI to a terminal device, where the first DCI instructs the terminal device not to monitor the PDCCH within a first time domain length.

[0099] Exemplarily, the first DCI can implement the indication of the first DCI by instructing the terminal device to skip PDCCH, for example, the first DCI includes a flag bit indicating skipping PDCCH, or the first DCI corresponding field indicates a state indicating skipping PDCCH; or, the first DCI can also implement the indication of the first DCI by instructing the terminal device to implement the indication of the first DCI according to the empty SSSG.

[0100] Step 602: The terminal device monitors the PDCCH in the second time domain length. Correspondingly, the network device sends the PDCCH in the second time domain length. The second time domain length belongs to the first time domain length.

[0101] The second time domain length can be understood as the retransmission period in the above description, that is, the time period during which the indicated terminal device does not need to monitor the PDCCH (that is, within the first time domain length), and the additional time period during which the PDCCH needs to be monitored. The specific definition of the second time domain length can be divided into the following situations:

[0102] Case a1: the second time domain length may include multiple sub-time domain lengths, wherein each of the multiple sub-time domain lengths is related to one HARQ process among multiple HARQ processes of the terminal device.

[0103] Optionally, the multiple HARQ processes of the terminal device may be multiple HARQ processes supported by the terminal device, multiple HARQ processes used by the terminal device, multiple HARQ processes configured for the terminal device by the network device, HARQ processes that currently have incomplete data transmission, or HARQ processes that currently have a timer running. This application is not limited to this.

[0104] This situation a1 can be understood as the second time domain length being the union of multiple sub-time domain lengths, wherein the multiple sub-time domain lengths can exist continuously or discretely, and this application does not limit this.

[0105] For example, the second time domain length may include a first sub-time domain length, the first sub-time domain length is related to the first HARQ process, and the first HARQ process is one of multiple HARQ processes of the terminal device; further, the second time domain length may also include a second sub-time domain length, the second sub-time domain length is related to the second HARQ process; the second HARQ process is one of multiple HARQ processes of the terminal device.

[0106] Exemplarily, the first sub-time domain length is related to the first HARQ process, and specifically, the first sub-time domain length is the time during which the retransmission timer corresponding to the first HARQ process runs. The second sub-time domain length is related to the second HARQ process, and specifically, the second sub-time domain length is the time during which the retransmission timer corresponding to the second HARQ process runs.

[0107] For example, Figure 7a A schematic diagram of a second time domain length is shown. Figure 7a It can be seen that the terminal device has data from two HARQ processes that need to be retransmitted, for example, the two HARQ processes are the first HARQ process and the second HARQ process. The terminal device monitors PDCCH during the time when the retransmission timer corresponding to the first HARQ process runs, that is, within the first sub-time domain length, and during the time when the retransmission timer corresponding to the second HARQ process runs, that is, within the second sub-time domain length.

[0108] Optionally, the first HARQ process may be either an uplink HARQ process or a downlink HARQ process, and similarly, the second HARQ process may be either an uplink HARQ process or a downlink HARQ process. Figure 7a The first HARQ process and the second HARQ process are only taken as downlink HARQ processes for example, which is not intended to limit the present application.

[0109] In some other embodiments, the length of the first sub-time domain may not be equal to the running time of the retransmission timer corresponding to the first HARQ process. For example, the length of the first sub-time domain may be less than the running time of the retransmission timer corresponding to the first HARQ process, or the length of the first sub-time domain may be greater than the running time of the retransmission timer corresponding to the first HARQ process, as long as the terminal device still monitors the PDCCH within the first sub-time domain length. Similarly, the length of the second sub-time domain may not be equal to the running time of the retransmission timer corresponding to the second HARQ process. For example, the length of the second sub-time domain may be less than the running time of the retransmission timer corresponding to the second HARQ process, or the length of the second sub-time domain may be greater than the running time of the retransmission timer corresponding to the second HARQ process, as long as the terminal device still monitors the PDCCH within the second sub-time domain length. Figure 7b As shown, the length of the first sub-time domain is less than the running time of the retransmission timer corresponding to the first HARQ process, and the length of the second sub-time domain is greater than the running time of the retransmission timer corresponding to the second HARQ process. It should be noted that, Figure 7b This is only an example and is not intended to limit the present application.

[0110] Through the method of situation a1, the terminal device can monitor the PDCCH when a data packet corresponding to any HARQ process may be retransmitted, thereby avoiding data retransmission failure of a certain HARQ process.

[0111] Case a2: the second time domain length is related to the third HARQ process, and the third HARQ process is the HARQ process corresponding to the first DCI.

[0112] Exemplarily, the second time domain length is related to the third HARQ process, and specifically may be: the second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0113] Optionally, the third HARQ process may be either an uplink HARQ process or a downlink HARQ process.

[0114] For example, Figure 8 shows a schematic diagram of a second time domain length, Figure 8 In the description, the third HARQ process is taken as a downlink HARQ process as an example. Figure 8 It can be seen that when the HARQ feedback corresponding to the first DCI is a negative response NACK, the data of the HARQ process corresponding to the first DCI (that is, the third HARQ process) needs to be retransmitted. During the time when the retransmission timer corresponding to the third HARQ process runs, that is, within the second time domain length, the terminal device monitors the PDCCH.

[0115] Although the method of case a1 can monitor PDCCH at the time when the data packet corresponding to any HARQ process may be retransmitted, and can avoid the failure of data retransmission of a certain HARQ process, it may cause the duration of skipping PDCCH monitoring to be fragmented, which may cause the terminal device to be unable to enter deep sleep, resulting in a decrease in the energy saving effect of skipping PDCCH and a decrease in the power consumption optimization effect of the terminal device. Compared with case a1, the method of case a2 can avoid the above problems, shorten the time of monitoring PDCCH, and reduce the power consumption of the terminal device.

[0116] In other embodiments, Figure 7b Similarly, the second time domain length may not be equal to the running time of the retransmission timer corresponding to the third HARQ process. For example, the second time domain length may be less than the running time of the retransmission timer corresponding to the third HARQ process, or the second time domain length may be greater than the running time of the retransmission timer corresponding to the third HARQ process, as long as the terminal device still monitors the PDCCH within the second time domain length. For example, the second time domain length is less than the running time of the retransmission timer corresponding to the third HARQ process, which can be referred to Figure 7bThe first sub-time domain length is less than the running time of the retransmission timer corresponding to the first HARQ process, and the second time domain length is greater than the running time of the retransmission timer corresponding to the third HARQ process. Figure 7b The second sub-time domain length is greater than the running time of the retransmission timer corresponding to the second HARQ process, which is not illustrated here.

[0117] In one possible example, for uplink transmission, since there is no HARQ feedback, the retransmission timer will be started regardless of whether there is retransmission. If the uplink transmission does not require retransmission, the retransmission timer will continue to run until the configured duration expires. Fig. 9 As shown, the terminal device monitors the PDCCH during the retransmission timer of the uplink transmission. When the retransmission timer of the uplink transmission is configured for a longer duration (e.g., 8 or 16 time slots), the terminal device's skipping of PDCCH monitoring may not achieve the expected energy saving effect. Therefore, in order to avoid the above-mentioned problems in uplink transmission, the retransmission period in the uplink transmission, that is, the second time domain length, can be defined as follows:

[0118] Method b1: The second time domain length is the running time of the retransmission timer in downlink transmission.

[0119] Optionally, when there are retransmissions in both uplink transmission and downlink transmission, the retransmission of the uplink transmission can be scheduled within the second time domain length in method b1.

[0120] Optionally, when only uplink transmission has retransmission, the scheduling of uplink transmission can also be rescheduled after the first time domain length. That is, in this case, no retransmission timer of downlink transmission runs, and the retransmission of uplink transmission can only be performed after the skipping duration of PDCCH monitoring.

[0121] Further, in method b1, the second time domain length is the time for which the retransmission timer runs in the downlink transmission, which can be specifically the second time domain length in the above case a1, but it should be noted that at this time, each of the multiple sub-time domain lengths is related to a downlink HARQ process in the multiple downlink HARQ processes of the terminal device, that is, the first HARQ process and the second HARQ process involved in the method b1 are downlink HARQ processes. Alternatively, the second time domain length is the time for which the retransmission timer runs in the downlink transmission, which can be specifically the second time domain length in the above case a2, and it should be noted that at this time, in method b1, the third HARQ process is a downlink HARQ process.

[0122] Method b2, the second time domain length can still refer to the definition of the second time domain length in the above case a1 and case a2. In this method b2, the network device sends a third DCI to the terminal device within the second time domain length, and the third DCI is used to terminate the operation of the uplink retransmission timer in advance, or to avoid starting the uplink retransmission timer. That is, the third DCI can prevent the terminal device from performing meaningless PDCCH monitoring when the uplink data transmission is successful. The third DCI indicates the successful transmission of the uplink data, that is, the third DCI indicates the correct transmission of the PUSCH, so that the terminal device stops monitoring the PDCCH.

[0123] For example, the third DCI can be obtained by setting some fields in DCI format (format) 0_0 or DCI format (format) 0_1 or DCI format (format) 0_2 to preset values, and the third DCI is a non-scheduling DCI. Optionally, when the frequency domain resource allocation type is type 0 (i.e., resourceAllocation = resourceAllocationType0), the frequency domain resource allocation (FDRA) field in the DCI of the above format can be set to all 0s; when the frequency domain resource allocation type is type 1 (i.e., resourceAllocation = resourceAllocationType1), the FDRA field in the DCI of the above format can be set to all 1s; when the frequency domain resource allocation type is dynamic switching (i.e., resourceAllocation = dynamicSwitch), the FDRA field in the DCI of the above format can be set to all 0s or all 1s.

[0124] Optionally, in addition to setting the preset value of the FDRA field, it is also possible to further specify that a one-shot HARQ-ACK request field does not exist or the value of the field is set to 0. Of course, the values ​​of other fields may also be further specified, which are not listed here one by one.

[0125] Through the above method, the third DCI obtained is used to indicate that the DCI is not used for scheduling data, but is used to indicate the successful transmission of uplink data, that is, to indicate to stop monitoring PDCCH during the retransmission period (that is, within the second time domain length). By indicating the correct transmission of PUSCH through the third DCI, the terminal device can quickly stop monitoring PDCCH, avoiding the long PDCCH monitoring time caused by possible retransmission of uplink transmission, thereby reducing the power consumption of the terminal device.

[0126] In addition, a dedicated DCI format may also be used to indicate that the uplink retransmission timer is terminated, or the uplink retransmission timer is not started, or the uplink data transmission is successful.

[0127] Method b3: The network device configures the second time domain length to be the time during which the retransmission timer runs in downlink transmission, or the time during which the retransmission timer runs in downlink transmission and uplink transmission.

[0128] Exemplarily, the network device sends configuration information to the terminal device, and the configuration information indicates that the second time domain length is associated with a downlink HARQ process, or indicates that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process. Further, the terminal device determines, based on the configuration information of the network device, that the HARQ process currently associated with the second time domain length belongs to a downlink HARQ process, or, belongs to a downlink HARQ process or an uplink HARQ process.

[0129] For example, when the second time domain length is the second time domain length in the above situation a1, each of the multiple sub-time domain lengths is associated with one HARQ process in the multiple HARQ processes of the terminal device, wherein the terminal device determines whether the one HARQ process belongs only to the downlink HARQ process, or to the downlink HARQ process or the uplink HARQ process according to the configuration information of the network device; that is, whether the first HARQ process and the second HARQ process involved in the method b3 belong only to the downlink HARQ process, or can belong to both the downlink HARQ process and the uplink HARQ process is determined by the terminal device according to the configuration information of the network device. When the configuration information indicates that the second time domain length is only associated with the downlink HARQ process, if there is a downlink HARQ process that has not completed the transmission, the running time of the retransmission timer of the downlink HARQ process is a sub-time domain length. Even if there is an uplink HARQ process that has not completed the transmission, the running time of the retransmission timer of the uplink HARQ process will not be used as the basis for determining the sub-time domain length of the second time domain length. When the configuration information indicates that the second time domain length is associated with the uplink HARQ process and the downlink HARQ process, both the retransmission timer of the uplink HARQ process and the retransmission timer of the downlink HARQ process may run for a sub-time domain length.

[0130] For another example, when the second time domain length is the second time domain length in the above situation a2, in method b3, whether the third HARQ process belongs to a downlink HARQ process, a downlink HARQ process or an uplink HARQ process is determined by the terminal device according to the configuration information of the network device. When the configuration information indicates that the second time domain length is only associated with the downlink HARQ process, the third HARQ process can only be a downlink HARQ process, and the first DCI can only be a DCI for scheduling PDSCH. If the first DCI is a DCI for scheduling PUSCH and the third HARQ is an uplink HARQ process, there will be no second time domain length, that is, the terminal device will not monitor PDCCH within the first time domain length. When the configuration information indicates that the second time domain length can be associated with an uplink HARQ process and a downlink HARQ process, the third HARQ process can be either an uplink HARQ process or a downlink HARQ process, and accordingly, the first DCI can be either a DCI for scheduling PUSCH or a DCI for scheduling PDSCH. The terminal device will determine the second time domain length within the first time domain length according to the running time of the retransmission timer of the third HARQ process, and monitor the PDCCH within the second time domain length.

[0131] Optionally, in a delay-sensitive scenario, the network device can configure the second time domain length to be the time for the retransmission timer to run in the downlink transmission and the uplink transmission, so that the uplink retransmission can also be completed quickly. In a delay-insensitive scenario where energy saving is a concern, the network device can configure the second time domain length to be only the time for the retransmission timer to run in the downlink transmission, so that the PDCCH can be not monitored for a longer period of time in the case of uplink retransmission.

[0132] Through the above communication method, the time when the terminal device needs to monitor PDCCH during the time period instructed not to monitor PDCCH can be clarified, that is, the definition of the retransmission period is clarified so that the terminal device can accurately monitor the retransmission scheduled PDCCH.

[0133] Furthermore, in the above Figure 5 In the scenario shown in FIG. 10A for monitoring the PDCCH during the retransmission period, and in FIG. Figure 6 In the scenario where the PDCCH is monitored during the retransmission period specified in the communication method shown, the DCI for scheduling retransmission will also include a PDCCH monitoring indication. When the terminal device receives the PDCCH monitoring indication, if the indication of the previously received DCI (such as the initial transmission DCI) is changed, the following problems may occur:

[0134] For example, a network device uses 1 bit in DCI to indicate PDCCH monitoring, where '0' indicates not skipping PDCCH (i.e., continuously monitoring PDCCH), and '1' indicates skipping PDCCH monitoring for a fixed time domain length (called skipping duration) (i.e., not monitoring PDCCH within a fixed time domain length). Fig.10 In the schematic diagram shown in which retransmitted DCI is monitored during the retransmission period, if 1 bit in the retransmitted DCI is "0", indicating that PDCCH is not skipped, the terminal device will directly resume monitoring PDCCH and will not be able to save energy; if 1 bit in the retransmitted DCI is "1", indicating a fixed time domain length, so that the terminal device does not monitor PDCCH within a fixed time domain length, the terminal device will not monitor PDCCH within a fixed time domain length. If the time that the terminal device does not monitor PDCCH is longer than the time that the initial DCI indicates that PDCCH is not monitored, it may cause increased latency.

[0135] Based on this, the present application also proposes a communication method to clarify how to keep the time for skipping PDCCH indicated by the previous DCI valid when the terminal device receives DCI during the retransmission period.

[0136] It should be noted that the communication method can be implemented based on the retransmission period of the HARQ process (i.e., the time when the HARQ retransmission timer runs) that is not currently considered, or can be implemented based on Figure 5 The implementation may be based on the retransmission period (ie, the second time domain length) defined in the embodiment shown, or may be based on a retransmission period redefined later, which is not limited in the present application.

[0137] For example, the following is based on the communication method Figure 5 The second time domain length defined in the embodiment shown is implemented as an example, and it should be understood that this is not a limitation of the present application. It should be understood that when the communication method is implemented based on the current retransmission period or the newly defined retransmission period in the future, the second time domain length described below can be replaced by the current retransmission period or the newly defined retransmission period in the future.

[0138] Based on the above description, a communication method provided in an embodiment of the present application is used to clarify how to keep the time for skipping PDCCH indicated by the previous DCI valid when the terminal device receives DCI during the retransmission period. This method is applicable to Figure 1 The communication system shown. Fig.11 As shown, the specific process of the method may include:

[0139] Step 1101: The network device sends a first DCI to the terminal device. That is, the terminal device receives a first DCI from the network device. The first DCI instructs the terminal device not to monitor the PDCCH within a first time domain length.

[0140] Exemplarily, the first DCI can implement the indication of the first DCI by instructing the terminal device to skip PDCCH, for example, the first DCI includes a flag bit indicating skipping PDCCH, or the first DCI corresponding field indicates a state indicating skipping PDCCH; or, the first DCI can also implement the indication of the first DCI by instructing the terminal device to implement the indication of the first DCI according to the empty SSSG.

[0141] Step 1102: After sending the first DCI, the network device sends a second DCI to the terminal device within the second time domain length. That is, after receiving the first DCI, the terminal device receives the second DCI from the network device within the second time domain length. The second time domain length belongs to the first time domain length.

[0142] Optionally, the second DCI may be a DCI for the network device to schedule data retransmission of the terminal device.

[0143] Step 1103: The terminal device determines, based on the second DCI, that the terminal device does not monitor PDCCH within a third time domain length, the starting position of the third time domain length is the end position of the second time domain length or is after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0144] The end position of the third time domain length is the end position of the first time domain length, that is, the end time of the terminal device performing the "not monitoring PDCCH" operation is the same as the end position of the time (that is, the first time domain length) of skipping PDCCH indicated by the initial DCI (that is, the first DCI). In this way, the impact on the timeline (timeline) of skipping PDCCH indicated by the terminal device can be minimized.

[0145] Specifically, according to different specific forms of the first DCI and the indication of the second DCI, the terminal device may perform step 1103 in the following ways:

[0146] Method c1, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, which can be specifically implemented in the following manner: the first DCI instructs the terminal device to monitor the PDCCH according to the first search space group, and the first search space group does not include a search space (that is, the first search space group does not include any search space, and the first search space group is an empty search space group). That is, the first DCI can implement the indication of the first DCI by instructing the terminal device to monitor the PDCCH according to the empty SSSG.

[0147] In method c1, the second DCI may include a first field, the first value of which indicates that the terminal device does not switch the search space group to monitor PDCCH; the second value of the first field indicates that the terminal device monitors PDCCH according to the second search space group, and the second search space group includes at least one search space.

[0148] It should be noted that instructing the terminal device not to switch the search space group to monitor the PDCCH can also be described as instructing the terminal device not to switch the monitored search space group, etc.

[0149] Furthermore, when the first field of the second DCI has the first value, the terminal device determines, based on the second DCI, to continue monitoring PDCCH according to the first search space group within the third time domain length, that is, not monitoring PDCCH. Specifically, it can be: the terminal device determines, based on the first field in the second DCI having the first value, not to monitor PDCCH within the third time domain length.

[0150] That is to say, in method c1, when the network device sends the second DCI within the retransmission period (that is, within the second time domain length), the network device can set the first field in the second DCI to the first value to instruct the terminal device not to switch the search space group to monitor PDCCH, that is, to continue to monitor PDCCH according to the empty first search space group, so as not to affect the end time of the terminal device not monitoring PDCCH (that is, the original skipping timeline of the terminal device).

[0151] Method c2, the first DCI instructs the terminal device not to monitor PDCCH within the first time domain length, which can be specifically implemented in the following way: the first DCI instructs the terminal device to monitor PDCCH according to the third search space group, the third search space group does not include a search space, that is, the third search space group is an empty search space group (emptySSSG or dormant SSSG).

[0152] Optionally, when the terminal device receives the first DCI and the first timer is not running, the first timer is started or restarted, wherein the first timer is related to the third search space.

[0153] In the method c2, the second DCI instructs the terminal device to monitor the PDCCH according to the third search space group.

[0154] Furthermore, the terminal device determines not to monitor PDCCH within the third time domain length based on the second DCI. Specifically, it can be: the terminal device determines that the first timer is running when the second DCI is received, the first timer is not restarted, and determines not to monitor PDCCH within the third time domain length.

[0155] Optionally, the second time domain length may be associated with a second timer. That is, the second timer is a timer for controlling the terminal device to monitor the PDCCH during the retransmission period, and its duration may be set to the second time domain length. In one case, the second timer may be a HARQ retransmission timer. It should be noted that the first timer keeps running within the second time domain length, and the first timer is not affected by the second timer. For example, Fig.12 As shown in the schematic diagram, when the terminal device receives the first DCI, the first timer is started or restarted; when the terminal device receives the second DCI, the first timer continues to run without restarting, until the first timer times out and the first time domain length ends.

[0156] In this way, in method c2, when the terminal device is already monitoring or using an empty search space group (i.e., the third search space group), and is instructed by the network device to monitor PDCCH according to the empty search space group during the retransmission period, the running time of the first timer will not be affected, and the end time of not monitoring PDCCH can remain unchanged.

[0157] Method c3, the terminal device determines not to monitor PDCCH within the third time domain length based on the second DCI. Specifically, it can be: when the second DCI indicates the monitoring method of PDCCH, the terminal device determines that the monitoring method of PDCCH indicated by the second DCI is not effective, thereby determining not to monitor PDCCH within the third time domain length.

[0158] It should be noted that the terminal device determines that the monitoring method of the PDCCH indicated by the second DCI is not effective, which can also be described as: the terminal device ignores the monitoring method of the PDCCH indicated by the second DCI; or, it can also be described as: determining that the monitoring method of the PDCCH indicated by the second DCI is invalid; or, it can also be described as: the terminal device does not interpret, decode or translate the monitoring method of the PDCCH indicated by the second DCI.

[0159] In method c3, the terminal device itself is instructed by the first DCI not to monitor PDCCH within the first time domain length. When the indication of the second DCI received during the retransmission period is not effective, the first DCI indication content is still valid, and the end time when the terminal device does not monitor PDCCH is still the end position of the first time domain length.

[0160] It should be noted that in the method c3, the second DCI can be a retransmission DCI (DCI for the network device to schedule the retransmission of terminal device data) or a non-retransmission DCI. When the second DCI can be either a retransmission DCI or a non-retransmission DCI, the network device cannot change the end time of not monitoring PDCCH indicated by the first DCI during the retransmission period. When the second DCI can only be a retransmission DCI, in the method c3, the retransmission DCI will not affect the end time of not monitoring PDCCH indicated by the first DCI, and the non-retransmission DCI (for example, the initial transmission DCI) can also indicate a new end time of not monitoring PDCCH, that is, the network device is allowed to change the end time of not monitoring PDCCH of the terminal device through the initial transmission DCI in certain cases when necessary.

[0161] Method c4, the second DCI may include a second field, the first value of the second field indicates that the terminal device does not perform new operations (that is, indicates that the terminal device has no new behavior); the second value of the second field indicates that the terminal device does not monitor PDCCH within a preset time domain length.

[0162] Exemplarily, the first value may be a reserved value, also referred to as a reserved value. The reserved value means that the standard does not define the meaning corresponding to the value, or the network device does not configure the meaning corresponding to the value. After the terminal device determines that the second field of the received second DCI is the reserved value, it considers that no information indicating a change in the monitoring PDCCH mode has been received, so the terminal device does not perform related operations, that is, does not perform new operations.

[0163] When the second field of the second DCI is the first value, the terminal device determines not to monitor PDCCH within the third time domain length according to the second DCI. Specifically, it can be: the terminal device determines not to monitor PDCCH within the third time domain length according to the second field of the second DCI being the first value.

[0164] That is to say, in method c4, when the network device sends the second DCI within the retransmission period (that is, within the second time domain length), the network device can set the second field in the second DCI to the first value to indicate that the terminal device does not perform new operations, so as not to affect the end time of the terminal device not monitoring PDCCH (that is, the original skipping timeline of the terminal device).

[0165] In some embodiments, when a DCI received by a terminal device from a network device is not received within the second time domain length, the DCI may include the second field, and the first value of the second field may indicate that the terminal device does not perform a PDCCH skipping operation (i.e., instructs the terminal device to continue monitoring the PDCCH). In other words, the same field and the same value in the DCI of the same format received in different time periods may have different indication meanings, which is not limited in this application.

[0166] Method c5: The second DCI indicates that the PDCCH is monitored according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space.

[0167] The terminal device determines not to monitor PDCCH within the third time domain length according to the second DCI, which can be specifically as follows: the terminal device determines that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group; and determines not to monitor PDCCH within the third time domain length. That is, the network device indicates the search space group (that is, the fourth search space group) that the terminal device is currently monitoring through the second DCI, and the terminal device determines to continue to monitor PDCCH according to the current search space group (that is, the fourth search space group) according to the indication of the second DCI, so the end time of the terminal device not monitoring PDCCH will not change, that is, the end time of the terminal device not monitoring PDCCH remains unchanged, and therefore PDCCH is not monitored within the third time domain length.

[0168] In method c5, the network device may indicate the search space group currently being monitored or used by the terminal device, so that the terminal device does not receive new instructions, the monitored search space group remains unchanged, and the end time of not monitoring PDCCH remains unchanged.

[0169] This method c5 can be used as a constraint on the network device. For example, for the method 2 described above, the terminal device expects to only receive flag bits indicating search space group switching during the retransmission period (UE expects to only receive flag = SSSG switching during retransmission period); for another example, for the method 3 described above, the terminal device expects to only receive SSSG switching indication during the retransmission period (UE expects to only receive SSSG switching indication during retransmission period).

[0170] Method c6: The format of the second DCI is format 1_0 or format 0_0.

[0171] In method c6, the terminal device may only monitor DCI that does not include the PDCCH monitoring mode, that is, DCI of format 1_0 or format 0_0. Among them, DCI of format 1_0 or format 0_0 may also be called fallback DCI. The fallback DCI does not include information indicating the change of the PDCCH monitoring mode, and therefore does not affect the end time of the terminal device not monitoring the PDCCH.

[0172] According to the definition in the current standard, in the common search space (CSS), the terminal device monitors the fallback DCI and does not monitor the non-fallback DCI. In the terminal device specific search space (USS), the terminal device monitors the fallback DCI and one of the fallback DCI according to the configuration of the network device. Therefore, in the method c6, when only the fallback DCI is used to schedule retransmission during the retransmission period, the terminal device can only monitor the CSS and the USS configured to monitor the fallback DCI, which can reduce blind detection to a certain extent, thereby saving the power consumption of the terminal device.

[0173] By adopting the communication method provided in the embodiment of the present application, it is possible to avoid the influence of the retransmitted DCI on the end time of not monitoring the PDCCH indicated by the initially transmitted DCI.

[0174] In addition, the embodiment of the present application also proposes a communication method for proposing a monitoring method of a PDCCH of a terminal device indicated by a network device through a DCI, see Fig.13 As shown, the specific process of the method may include the following steps:

[0175] Step 1301: The network device sends a fourth DCI to the terminal device, where the fourth DCI is used to indicate a monitoring method for the PDCCH.

[0176] Step 1302: The terminal device monitors the PDCCH according to the PDCCH monitoring method indicated by the fourth DCI.

[0177] Exemplarily, the monitoring method of the PDCCH indicated by the fourth DCI may include the following method:

[0178] Mode d1, the fourth DCI includes a third field, the first value of the third field indicates that the terminal device switches from monitoring PDCCH according to the fifth search space group to monitoring PDCCH according to the sixth search space group; the second value of the third field indicates that the terminal device does not switch the search space group to monitor PDCCH.

[0179] Correspondingly, when the third field of the fourth DCI is the first value, the terminal device switches from monitoring PDCCH according to the fifth search space group to monitoring PDCCH according to the sixth search space group; when the third field of the fourth DCI is the second value, the terminal device continues to monitor PDCCH according to the current search space group.

[0180] It should be noted that the fifth search space group may include at least one search space, or may not include any search space (i.e., an empty search space). Similarly, the sixth search space group may include at least one search space, or may not include any search space (i.e., an empty search space). The fifth search space group and the sixth search space group may be the same or different, and this application does not limit this.

[0181] Mode d2: The fourth DCI instructs the terminal device to monitor the PDCCH according to the seventh search space group, and the seventh search space group does not include any search space.

[0182] Accordingly, when the terminal device receives the fourth DCI, the third timer is not running, and the third timer is started or restarted; the third timer is related to the seventh search space; when the terminal device receives the fourth DCI, the third timer is running, and the third timer is not restarted.

[0183] That is, in mode d2, the terminal device does not monitor the PDCCH during the operation of the third timer.

[0184] Mode d3, the fourth DCI includes a fourth field, and a value of one of the fourth field indicates that the terminal device does not monitor the PDCCH within a preset time domain length; a value of two of the fourth field indicates that the terminal device does not perform new operations (that is, indicates that the terminal device has no new behavior (no new behavior)), or indicates that the PDCCH skipping operation is not performed (that is, indicates that the terminal device continues to monitor the PDCCH).

[0185] Accordingly, when the fourth field of the fourth DCI is value one, the terminal device does not monitor PDCCH within the preset time domain length; when the fourth field of the fourth DCI is value two, the terminal device monitors PDCCH according to the current PDCCH monitoring method or the terminal device continues to monitor PDCCH.

[0186] It should be noted that the fourth DCI mentioned above may be an initial transmission DCI, or a DCI in a retransmission period, or a retransmission DCI, and this application does not limit this.

[0187] Optionally, when the fourth DCI is a DCI in a retransmission period, the value two of the fourth field of the fourth DCI indicates that the terminal device does not perform a new operation; when the fourth DCI is not a DCI in a retransmission period, the value two of the fourth DCI indicates that the terminal device does not perform a skip PDCCH operation.

[0188] It should be understood that when the fourth DCI is a DCI in the retransmission period, the fourth DCI may be Fig.11 In the embodiment shown, the second DCI corresponds to: Fig.11 The first field included in the second DCI shown can be the third field of the fourth DCI in the above-mentioned method d1, the first value of the first field corresponds to the second value of the third field, and the second value of the first field corresponds to the first value of the third field. For another example, the fourth DCI in method d2 corresponds to Fig.11 The second DCI in method c2 in the embodiment shown corresponds to. For another example, Fig.11 The second field in the second DCI shown may be the fourth field of the fourth DCI in the above-mentioned mode d3, the first value of the second field corresponds to the value 2 of the fourth field indicating that the terminal device does not perform a new operation, and the second value of the second field corresponds to the value 1 of the fourth field. It should be understood that the above is only an example and the present application does not limit this.

[0189] Based on the above embodiments, the present application also provides a communication device, referring to Fig.14 As shown, the communication device 1400 may include a transceiver unit 1401 and a processing unit 1402. The transceiver unit 1401 is used for the communication device 1400 to receive information (message or data) or send information (message or data), and the processing unit 1402 is used to control and manage the actions of the communication device 1400. The processing unit 1402 may also control the steps performed by the transceiver unit 1401.

[0190] Exemplarily, the communication device 1400 may specifically be the terminal device in the above-mentioned embodiments, the processor in the terminal device, or a chip, or a chip system, or a functional module, etc.; or, the communication device 1400 may specifically be the network device in the above-mentioned embodiments, the processor of the network device, or a chip, or a chip system, or a functional module, etc.

[0191] In one embodiment, the communication device 1400 is used to implement the above Fig.11 The functions of the terminal device in the above-described embodiment may specifically include:

[0192] The transceiver unit 1401 is used to receive a first DCI from a network device, wherein the first DCI indicates that the terminal device does not monitor the PDCCH within a first time domain length; and after receiving the first DCI, receive a second DCI from the network device within a second time domain length, wherein the second time domain length belongs to the first time domain length; the processing unit 1402 is used to determine, based on the second DCI, that the terminal device does not monitor the PDCCH within a third time domain length, wherein the starting position of the third time domain length is the ending position of the second time domain length or is located after the second time domain length, and the ending position of the third time domain length is the ending position of the first time domain length.

[0193] In an optional embodiment, the second DCI includes a first field, and a first value of the first field indicates that the terminal device does not switch the search space group to monitor PDCCH; the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length, including: the first DCI indicates that the terminal device monitors PDCCH according to the first search space group, and the first search space group does not include a search space; when the processing unit 1402 determines not to monitor PDCCH within the third time domain length according to the second DCI, it is specifically used to: determine not to monitor PDCCH within the third time domain length according to the first field in the second DCI being the first value.

[0194] Exemplarily, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, where the second search space group includes at least one search space.

[0195] In another optional implementation, the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length, including: the first DCI indicates that the terminal device monitors PDCCH according to a third search space group, and the third search space group does not include a search space; the second DCI indicates that the terminal device monitors PDCCH according to the third search space group; when the processing unit 1402 determines not to monitor PDCCH within the third time domain length according to the second DCI, it is specifically used to: determine that the first timer is running when the transceiver unit 1401 receives the second DCI, the first timer is not restarted, and determine that PDCCH is not monitored within the third time domain length, wherein the first timer is related to the third search space.

[0196] Exemplarily, the processing unit 1402 is further configured to start or restart the first timer when the first timer is not running when the transceiver unit 1401 receives the first DCI.

[0197] In another optional embodiment, when the processing unit 1402 determines not to monitor PDCCH within the third time domain length based on the second DCI, it is specifically used to: when the second DCI indicates the monitoring method of PDCCH, determine that the monitoring method of PDCCH indicated by the second DCI is not effective; determine not to monitor PDCCH within the third time domain length.

[0198] In yet another optional implementation, the format of the second DCI is format 1_0 or format 0_0.

[0199] In another optional embodiment, the second DCI includes a second field, and the first value of the second field indicates that the terminal device does not perform a new operation; when the processing unit 1402 determines not to monitor the PDCCH within the third time domain length according to the second DCI, it is specifically used to: determine not to monitor the PDCCH within the third time domain length according to the second field of the second DCI being the first value.

[0200] Exemplarily, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0201] In another optional embodiment, the second DCI indicates that PDCCH is monitored according to a fourth search space group, and the fourth search space group is the same as the currently monitored search space group; the fourth search space group includes at least one search space; when the processing unit 1402 determines not to monitor PDCCH within the third time domain length according to the second DCI, it is specifically used to: determine that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group; determine not to monitor PDCCH within the third time domain length.

[0202] In one example, the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the running time of a retransmission timer corresponding to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device.

[0203] Optionally, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0204] In another example, the second time domain length is the running time of the retransmission timer corresponding to the third HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

[0205] Optionally, the first HARQ process is a downlink HARQ process.

[0206] Optionally, the third HARQ process is a downlink HARQ process.

[0207] In an optional implementation, the transceiver unit 1401 is further used to: receive a third DCI from the network device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0208] In another embodiment, the communication device 1400 is used to implement the above Fig.11 The functions of the network device in the embodiments described above may specifically include:

[0209] The transceiver unit 1401 is used to send a first DCI to a terminal device, wherein the first DCI indicates that the terminal device does not monitor PDCCH within a first time domain length; and, after sending the first DCI, send a second DCI to the terminal device within a second time domain length, wherein the second time domain length belongs to the first time domain length; the second DCI is used by the terminal device to determine not to monitor PDCCH within a third time domain length, wherein the starting position of the third time domain length is the ending position of the second time domain length or is located after the second time domain length, and the ending position of the third time domain length is the ending position of the first time domain length; the processing unit 1402 is used to control the transceiver unit 1401 to perform the above-mentioned sending operation.

[0210] In an optional embodiment, the second DCI includes a first field, and a first value of the first field indicates not to switch the search space group to monitor PDCCH; the first DCI indicates that the terminal device does not monitor PDCCH within the first time domain length, including: the first DCI indicates that the terminal device monitors PDCCH according to the first search space group, and the first search space group does not include a search space.

[0211] Exemplarily, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, where the second search space group includes at least one search space.

[0212] In another optional embodiment, the first DCI instructs the terminal device not to monitor PDCCH within the first time domain length, including: the first DCI instructs the terminal device to monitor PDCCH according to a third search space group, and the third search space group does not include a search space; the second DCI instructs the terminal device to monitor PDCCH according to the third search space group; wherein, when the second DCI is sent, the first timer is running, the first timer is not restarted, and the first timer is related to the third search space.

[0213] In another optional implementation, the format of the second DCI is format 1_0 or format 0_0.

[0214] In another optional implementation, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation.

[0215] Exemplarily, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0216] In another optional implementation, the second DCI indicates monitoring of PDCCH according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space.

[0217] In one example, the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the running time of a retransmission timer corresponding to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device.

[0218] Optionally, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0219] In another example, the second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

[0220] Optionally, the first HARQ process is a downlink HARQ process.

[0221] Optionally, the third HARQ process is a downlink HARQ process.

[0222] In an optional implementation, the transceiver unit 1401 is further used to: send a third DCI to the terminal device within the second time domain length, and the third DCI is used to indicate successful transmission of uplink data.

[0223] In another embodiment, the communication device 1400 is used to implement the above Figure 6 The functions of the terminal device in the above-described embodiment may specifically include:

[0224] The transceiver unit 1401 is used to receive a first DCI from a network device, and the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within a first time domain length; the processing unit 1402 is used to monitor the PDCCH within a second time domain length; the second time domain length belongs to the first time domain length; the second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process, and the first HARQ process is one of multiple HARQ processes of the terminal device; or, the second time domain length is related to a third HARQ process, and the third HARQ process is the HARQ process corresponding to the first DCI.

[0225] Optionally, the second time domain length is related to the third HARQ process, including: the second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0226] Optionally, the first sub-time domain length is related to the first HARQ process, including: the first sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0227] Exemplarily, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0228] Optionally, the second sub-time domain length is related to the second HARQ process, including: the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0229] In one possible manner, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0230] In an optional implementation, the transceiver unit 1401 is further used to receive a third DCI from the network device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0231] In another embodiment, the communication device 1400 is used to implement the above Figure 6 The functions of the network device in the embodiments described above may specifically include:

[0232] The transceiver unit 1401 is used to send a first DCI to a terminal device, wherein the first DCI indicates that the terminal device does not monitor PDCCH within a first time domain length; and sends PDCCH within a second time domain length; the second time domain length belongs to the first time domain length; the second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process, which is one of multiple HARQ processes of the terminal device; or, the second time domain length is related to a third HARQ process, which is the HARQ process corresponding to the first DCI; the processing unit 1402 is used to control the transceiver unit 1401 to perform the above-mentioned sending operation.

[0233] Optionally, the second time domain length is related to the third HARQ process, including: the second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0234] Optionally, the second sub-time domain length is related to the first HARQ process, including: the second sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0235] Exemplarily, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0236] Optionally, the second sub-time domain length is related to the second HARQ process, including: the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0237] In one possible manner, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0238] In an optional implementation, the transceiver unit 1401 is further used to send a third DCI to the terminal device within the second time domain length, and the third DCI is used to indicate successful transmission of uplink data.

[0239] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. Each functional unit in the embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0240] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0241] Based on the above embodiments, the present application also provides a communication device, referring to Fig.15 As shown, the communication device 1500 may include a transceiver 1501 and a processor 1502. Optionally, the communication device 1500 may further include a memory 1503. The memory 1503 may be disposed inside the communication device 1500 or outside the communication device 1500. The processor 1502 may control the transceiver 1501 to receive and send information or data.

[0242] Specifically, the processor 1502 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 1502 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0243] The transceiver 1501, the processor 1502 and the memory 1503 are interconnected. Optionally, the transceiver 1501, the processor 1502 and the memory 1503 are interconnected via a bus 1504; the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0244] In an optional implementation, the memory 1503 is used to store programs, etc. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory 1503 may include a RAM, and may also include a non-volatile memory (non-volatile memory), such as one or more disk memories. The processor 1502 executes the application stored in the memory 1503 to implement the above functions, thereby realizing the functions of the communication device 1500.

[0245] Exemplarily, the communication device 1500 may be the terminal device in the above embodiment; or may be the network device in the above embodiment.

[0246] In one embodiment, the communication device 1500 implements Figure 6In the embodiment shown, the transceiver 1501 can implement the functions of the terminal device. Figure 6 The sending and receiving operations performed by the terminal device in the embodiment shown; the processor 1502 can implement Figure 6 In the embodiment shown, other operations other than the sending and receiving operations are performed by the terminal device. For specific related descriptions, please refer to the above Figure 6 The relevant description in the illustrated embodiment will not be described in detail here.

[0247] In another embodiment, the communication device 1500 implements Figure 6 In the embodiment shown, the transceiver 1501 can implement the functions of the network device. Figure 6 The transceiver operations performed by the network device in the embodiment shown; the processor 1502 can implement Figure 6 In the embodiment shown, other operations other than the sending and receiving operations are performed by the network device. For specific related descriptions, please refer to the above Figure 6 The relevant description in the illustrated embodiment will not be described in detail here.

[0248] In another embodiment, the communication device 1500 implements Fig.11 In the embodiment shown, the transceiver 1501 can implement the functions of the terminal device. Fig.11 The sending and receiving operations performed by the terminal device in the embodiment shown; the processor 1502 can implement Fig.11 In the embodiment shown, other operations other than the sending and receiving operations are performed by the terminal device. For specific related descriptions, please refer to the above Fig.11 The relevant description in the illustrated embodiment will not be described in detail here.

[0249] In another embodiment, the communication device 1500 implements Fig.11 In the embodiment shown, the transceiver 1501 can implement the functions of the network device. Fig.11 The transceiver operations performed by the network device in the embodiment shown; the processor 1502 can implement Fig.11 In the embodiment shown, other operations other than the sending and receiving operations are performed by the network device. For specific related descriptions, please refer to the above Fig.11 The relevant description in the illustrated embodiment will not be described in detail here.

[0250] In combination with the above, the present application provides the following embodiments, and the numbering of the following embodiments does not necessarily need to follow the numbering sequence of the previous embodiments:

[0251] Embodiment 1: A communication method, wherein the method comprises:

[0252] Receiving a first DCI from a network device, wherein the first DCI indicates that the terminal device does not monitor the PDCCH within a first time domain length;

[0253] After receiving the first DCI, receiving a second DCI from a network device within a second time domain length, where the second time domain length belongs to the first time domain length;

[0254] According to the second DCI, it is determined that the terminal device does not monitor PDCCH within a third time domain length, the starting position of the third time domain length is the end position of the second time domain length or is after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0255] Embodiment 2: According to the method of embodiment 1, the second DCI includes a first field, and a first value of the first field indicates that the terminal device does not switch the search space group to monitor the PDCCH;

[0256] The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes:

[0257] The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space;

[0258] Determining, according to the second DCI, not to monitor the PDCCH within a third time domain length includes:

[0259] According to the first field in the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

[0260] Embodiment 3: As described in the method of Embodiment 2, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, and the second search space group includes at least one search space.

[0261] Embodiment 4, as described in the method of embodiment 1, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

[0262] The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, and the third search space group does not include a search space;

[0263] The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group;

[0264] Determining, according to the second DCI, not to monitor the PDCCH within the third time domain length includes:

[0265] Determine that a first timer is running when the second DCI is received, the first timer is not restarted, and determine not to monitor PDCCH within the third time domain length, wherein the first timer is related to the third search space.

[0266] Embodiment 5: The method as described in Embodiment 4, further comprising:

[0267] When the first DCI is received, the first timer is not running, and the first timer is started or restarted.

[0268] Embodiment 6, as described in the method of embodiment 1, determining according to the second DCI not to monitor the PDCCH within the third time domain length includes:

[0269] When the second DCI indicates a monitoring mode of the PDCCH, determining that the monitoring mode of the PDCCH indicated by the second DCI is not effective;

[0270] It is determined not to monitor the PDCCH within the third time domain length.

[0271] Embodiment 7: As described in the method of Embodiment 1, the format of the second DCI is format 1_0 or format 0_0.

[0272] Embodiment 8: According to the method of embodiment 1, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation;

[0273] Determining, according to the second DCI, not to monitor the PDCCH within the third time domain length includes:

[0274] According to the second field of the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

[0275] Embodiment 9: As described in the method of Embodiment 8, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0276] Embodiment 10: According to the method of embodiment 1, the second DCI indicates monitoring the PDCCH according to a fourth search space group, and the fourth search space group is the same as the currently monitored search space group; the fourth search space group includes at least one search space;

[0277] Determining, according to the second DCI, not to monitor the PDCCH within a third time domain length includes:

[0278] Determining that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group;

[0279] It is determined not to monitor the PDCCH within the third time domain length.

[0280] Embodiment 11, as described in any one of embodiments 1-10, the second time domain length includes a first sub-time domain length, the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

[0281] Embodiment 12: As described in the method of Embodiment 11, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0282] Embodiment 13, as described in any one of embodiments 1-10, the second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

[0283] Embodiment 14: According to the method described in Embodiment 11, the first HARQ process is a downlink HARQ process.

[0284] Embodiment 15: According to the method described in Embodiment 13, the third HARQ process is a downlink HARQ process.

[0285] Embodiment 16: The method according to embodiment 11, further comprising:

[0286] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0287] It is determined according to the configuration information that the first HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0288] Embodiment 17: The method according to embodiment 13, further comprising:

[0289] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0290] It is determined according to the configuration information that the third HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0291] Embodiment 18: A method as described in any one of embodiments 11-13, wherein the method further includes: receiving a third DCI from the network device within the second time domain length, wherein the third DCI is used to indicate successful transmission of uplink data.

[0292] Embodiment 19, a communication method, wherein the method comprises:

[0293] Sending first downlink control information DCI to a terminal device, where the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length;

[0294] After sending the first DCI, a second DCI is sent to the terminal device within a second time domain length, and the second time domain length belongs to the first time domain length; the second DCI is used by the terminal device to determine not to monitor PDCCH within a third time domain length, and the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0295] Embodiment 20: As described in the method of embodiment 19, the second DCI includes a first field, and a first value of the first field indicates that the search space group monitoring PDCCH is not switched;

[0296] The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes:

[0297] The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space.

[0298] Embodiment 21: As described in the method of Embodiment 20, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, and the second search space group includes at least one search space.

[0299] Embodiment 22, the method according to embodiment 19, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

[0300] The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, where the third search space group does not include a search space;

[0301] The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group;

[0302] When the second DCI is sent, the first timer is running, the first timer is not restarted, and the first timer is related to the third search space.

[0303] Embodiment 23: As described in the method of Embodiment 19, the format of the second DCI is format 1_0 or format 0_0.

[0304] Embodiment 24: As described in the method of Embodiment 19, the second DCI includes a second field, and the first value of the second field indicates that the terminal device does not perform new operations.

[0305] Embodiment 25: As used in the method of Embodiment 24, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0306] Embodiment 26: As described in the method of Embodiment 19, the second DCI indicates monitoring PDCCH according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space.

[0307] Embodiment 27, as described in any one of embodiments 19-26, the second time domain length includes a first sub-time domain length, the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

[0308] Embodiment 28, as described in the method of Embodiment 27, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0309] Embodiment 29: A method as described in any one of embodiments 19-26, wherein the second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; and the third HARQ process is the HARQ process corresponding to the first DCI.

[0310] Embodiment 30: According to the method described in Embodiment 27, the first HARQ process is a downlink HARQ process.

[0311] Embodiment 31: According to the method described in Embodiment 29, the third HARQ process is a downlink HARQ process.

[0312] Embodiment 32: The method according to embodiment 27 or 29, further comprising:

[0313] Configuration information is sent to the terminal device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

[0314] Embodiment 33: The method as described in any one of embodiments 27-29, further comprising:

[0315] A third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0316] Embodiment 34: A communication method, comprising:

[0317] Receive first downlink control information DCI from a network device, where the first DCI instructs the terminal device not to monitor a physical downlink control channel PDCCH within a first time domain length;

[0318] Monitoring the PDCCH in a second time domain length; the second time domain length belongs to the first time domain length;

[0319] The second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device;

[0320] Alternatively, the second time domain length is related to a third HARQ process, and the third HARQ process is the HARQ process corresponding to the first DCI.

[0321] Embodiment 35: The method according to embodiment 34, wherein the second time domain length is related to the third HARQ process, including:

[0322] The second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0323] Embodiment 36: The method according to embodiment 34, wherein the first sub-time domain length is related to the first HARQ process, including:

[0324] The first sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0325] Embodiment 37: As described in the method of Embodiment 34 or 36, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0326] Embodiment 38: The method according to embodiment 37, wherein the second sub-time domain length is related to the second HARQ process, including:

[0327] The second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0328] Embodiment 39: According to the method described in any one of embodiments 34-38, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0329] Embodiment 40: The method as described in any one of embodiments 34 to 38, further comprising:

[0330] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0331] Determine, according to the configuration information, that the first HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process; and / or

[0332] It is determined according to the configuration information that the third HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0333] Embodiment 41: The method as described in any one of embodiments 34 to 38, further comprising:

[0334] A third DCI is received from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

[0335] Embodiment 42, a communication method, comprising:

[0336] Sending first downlink control information DCI to a terminal device, where the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length;

[0337] Sending a PDCCH in a second time domain length; the second time domain length belongs to the first time domain length;

[0338] The second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device;

[0339] Alternatively, the second time domain length is related to a third HARQ process, and the third HARQ process is the HARQ process corresponding to the first DCI.

[0340] Embodiment 43: The method according to embodiment 42, wherein the second time domain length is related to the third HARQ process, including:

[0341] The second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0342] Embodiment 44: The method according to embodiment 42, wherein the second sub-time domain length is related to the first HARQ process, including:

[0343] The second sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0344] Embodiment 45, as described in the method of Embodiment 42 or 44, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0345] Embodiment 46: The method according to embodiment 45, wherein the second sub-time domain length is related to the second HARQ process, including:

[0346] The second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0347] Embodiment 47: According to the method described in any one of embodiments 42-46, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0348] Embodiment 48: The method as described in any one of Embodiments 42-46, further comprising:

[0349] Configuration information is sent to the terminal device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

[0350] Embodiment 49: The method as described in any one of Embodiments 42-46, further comprising:

[0351] A third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0352] Embodiment 50: A communication device, comprising:

[0353] A transceiver unit, configured to receive a first DCI from a network device, wherein the first DCI indicates that the terminal device does not monitor the PDCCH within a first time domain length; and, after receiving the first DCI, receive a second DCI from the network device within a second time domain length, wherein the second time domain length belongs to the first time domain length;

[0354] A processing unit is used to determine, based on the second DCI, that the terminal device does not monitor the PDCCH within a third time domain length, the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

[0355] Embodiment 51, as described in embodiment 50, the second DCI includes a first field, and a first value of the first field indicates that the terminal device does not switch the search space group to monitor the PDCCH;

[0356] The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes:

[0357] The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space;

[0358] When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, the processing unit is specifically configured to:

[0359] According to the first field in the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

[0360] Embodiment 52: In the apparatus as described in Embodiment 51, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, and the second search space group includes at least one search space.

[0361] Embodiment 53, according to the apparatus of embodiment 50, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

[0362] The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, and the third search space group does not include a search space;

[0363] The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group;

[0364] When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, the processing unit is specifically configured to:

[0365] Determine that a first timer is running when the transceiver unit receives the second DCI, the first timer is not restarted, and determine not to monitor PDCCH within the third time domain length, wherein the first timer is related to the third search space.

[0366] Embodiment 54: In the device as described in Embodiment 53, the processing unit is further used for:

[0367] When the first timer is not running when the transceiver unit receives the first DCI, the first timer is started or restarted.

[0368] Embodiment 55: The apparatus according to embodiment 50, when the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, is specifically configured to:

[0369] When the second DCI indicates a monitoring mode of the PDCCH, determining that the monitoring mode of the PDCCH indicated by the second DCI is not effective;

[0370] It is determined not to monitor the PDCCH within the third time domain length.

[0371] Embodiment 56: In the device as described in Embodiment 50, the format of the second DCI is format 1_0 or format 0_0.

[0372] Embodiment 57: According to the apparatus of embodiment 50, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation;

[0373] When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, the processing unit is specifically configured to:

[0374] According to the second field of the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

[0375] Embodiment 58: In the apparatus as described in Embodiment 57, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0376] Embodiment 59: The apparatus according to embodiment 50, wherein the second DCI indicates monitoring of the PDCCH according to a fourth search space group, and the fourth search space group is the same as the currently monitored search space group; the fourth search space group includes at least one search space;

[0377] When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, the processing unit is specifically configured to:

[0378] Determining that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group;

[0379] It is determined not to monitor the PDCCH within the third time domain length.

[0380] Embodiment 60: In the apparatus as described in any one of embodiments 50-59, the second time domain length includes a first sub-time domain length, the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

[0381] Embodiment 61, as the apparatus of embodiment 60, the second time domain length also includes a second sub-time domain length, the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0382] Embodiment 62: In the device as described in any one of embodiments 50-59, the second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

[0383] Embodiment 63, in the device as described in Embodiment 60, the first HARQ process is a downlink HARQ process.

[0384] Example 64: In the device as described in Example 62, the third HARQ process is a downlink HARQ process.

[0385] Embodiment 65: In the device of embodiment 60, the transceiver unit is further used for:

[0386] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0387] The processing unit is also used for:

[0388] It is determined according to the configuration information that the first HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0389] Embodiment 66: In the device of embodiment 62, the transceiver unit is further used for:

[0390] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0391] The processing unit is also used for:

[0392] It is determined according to the configuration information that the third HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0393] Embodiment 67: In the apparatus as described in any one of embodiments 60-62, the transceiver unit is further used to: receive a third DCI from the network device within the second time domain length, wherein the third DCI is used to indicate successful transmission of uplink data.

[0394] Embodiment 68: A communication device, comprising:

[0395] A transceiver unit, configured to send first downlink control information DCI to a terminal device, wherein the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length; and, after sending the first DCI, send a second DCI to the terminal device within a second time domain length, wherein the second time domain length belongs to the first time domain length; the second DCI is used by the terminal device to determine that the PDCCH is not monitored within a third time domain length, wherein the starting position of the third time domain length is the ending position of the second time domain length or is located after the second time domain length, and the ending position of the third time domain length is the ending position of the first time domain length;

[0396] The processing unit is used to control the transceiver unit to send and receive information.

[0397] Embodiment 69: In the apparatus of embodiment 68, the second DCI includes a first field, and a first value of the first field indicates not to switch the search space group to monitor the PDCCH;

[0398] The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes:

[0399] The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space.

[0400] Embodiment 70: In the apparatus as described in Embodiment 69, the second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, and the second search space group includes at least one search space.

[0401] Embodiment 71, according to the apparatus of embodiment 68, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

[0402] The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, where the third search space group does not include a search space;

[0403] The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group;

[0404] When the second DCI is sent, the first timer is running, the first timer is not restarted, and the first timer is related to the third search space.

[0405] Embodiment 72: For the device as described in Embodiment 68, the format of the second DCI is format 1_0 or format 0_0.

[0406] Embodiment 73: In the apparatus as described in Embodiment 68, the second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation.

[0407] Embodiment 74: In the apparatus as described in Embodiment 73, the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

[0408] Embodiment 75: In the apparatus as described in Embodiment 68, the second DCI indicates monitoring of PDCCH according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space.

[0409] Embodiment 76: In the apparatus as described in any one of embodiments 68-75, the second time domain length includes a first sub-time domain length, the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

[0410] Embodiment 77: In the apparatus as described in Embodiment 76, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0411] Embodiment 78: In the device as described in any one of embodiments 68-75, the second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

[0412] Example 79: In the device as described in Example 76, the first HARQ process is a downlink HARQ process.

[0413] Embodiment 80: In the device as described in Embodiment 78, the third HARQ process is a downlink HARQ process.

[0414] Embodiment 81: In the device of Embodiment 76 or 78, the transceiver unit is further used for:

[0415] Configuration information is sent to the terminal device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

[0416] Embodiment 82: In the device as described in any one of Embodiments 76 to 78, the transceiver unit is further used for:

[0417] A third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0418] Embodiment 83: A communication device, comprising:

[0419] A transceiver unit, configured to receive first downlink control information DCI from a network device, wherein the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length;

[0420] A processing unit, configured to monitor the PDCCH in a second time domain length; the second time domain length belongs to the first time domain length;

[0421] The second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device;

[0422] Alternatively, the second time domain length is related to a third HARQ process, and the third HARQ process is the HARQ process corresponding to the first DCI.

[0423] Embodiment 84: The apparatus according to embodiment 83, wherein the second time domain length is related to the third HARQ process, including:

[0424] The second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0425] Embodiment 85, according to the apparatus of embodiment 83, wherein the first sub-time domain length is related to the first HARQ process, including:

[0426] The first sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0427] Embodiment 86: In the apparatus as described in Embodiment 83 or 85, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0428] Embodiment 87, according to the apparatus of embodiment 86, wherein the second sub-time domain length is related to the second HARQ process, including:

[0429] The second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0430] Embodiment 88: In the device as described in any one of embodiments 83-87, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0431] Embodiment 89: In the device as described in any one of Embodiments 83 to 87, the transceiver unit is further used for:

[0432] receiving configuration information from the network device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

[0433] The processing unit is also used for:

[0434] Determine, according to the configuration information, that the first HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process; and / or

[0435] It is determined according to the configuration information that the third HARQ process belongs to a downlink HARQ process, or belongs to a downlink HARQ process or an uplink HARQ process.

[0436] Embodiment 90: In the device as described in any one of Embodiments 83 to 87, the transceiver unit is further configured to:

[0437] A third DCI is received from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

[0438] Embodiment 91: A communication device, comprising:

[0439] A transceiver unit, configured to send first downlink control information DCI to a terminal device, wherein the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length; and sends the PDCCH within a second time domain length; the second time domain length belongs to the first time domain length;

[0440] The second time domain length includes a first sub-time domain length, and the first sub-time domain length is related to a first HARQ process; the first HARQ process is one of multiple HARQ processes of the terminal device;

[0441] Alternatively, the second time domain length is related to a third HARQ process, and the third HARQ process is a HARQ process corresponding to the first DCI;

[0442] The processing unit is used to control the transceiver unit to send and receive information.

[0443] Embodiment 92, the apparatus according to embodiment 91, wherein the second time domain length is related to the third HARQ process, including:

[0444] The second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

[0445] Embodiment 93, as described in the apparatus of embodiment 91, the second sub-time domain length is related to the first HARQ process, including:

[0446] The second sub-time domain length is the running time of the retransmission timer corresponding to the first HARQ process.

[0447] Embodiment 94: In the apparatus as described in Embodiment 91 or 93, the second time domain length also includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

[0448] Embodiment 95, according to the apparatus of embodiment 94, the second sub-time domain length is related to the second HARQ process, including:

[0449] The second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

[0450] Embodiment 96: In the device as described in any one of embodiments 91-95, the first HARQ process and / or the third HARQ process is a downlink HARQ process.

[0451] Embodiment 97: In the device as described in any one of Embodiments 91 to 95, the transceiver unit is further configured to:

[0452] Configuration information is sent to the terminal device, where the configuration information is used to indicate that the second time domain length is associated with a downlink HARQ process, or to indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

[0453] Embodiment 98: In the device as described in any one of Embodiments 91 to 95, the transceiver unit is further used for:

[0454] A third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

[0455] Embodiment 99: A communication device, comprising a memory, a processor, and a transceiver, wherein:

[0456] The memory is used to store computer instructions;

[0457] The transceiver is used to receive and send information;

[0458] The processor is coupled to the memory and is used to call the computer instructions in the memory so that the communication device executes the method described in any one of embodiments 1-18.

[0459] Embodiment 100, a communication device, comprising a memory, a processor and a transceiver, wherein:

[0460] The memory is used to store computer instructions;

[0461] The transceiver is used to receive and send information;

[0462] The processor is coupled to the memory and is used to call the computer instructions in the memory so that the communication device executes the method described in any one of embodiments 19-33.

[0463] Embodiment 101, a communication device, comprising a memory, a processor and a transceiver, wherein:

[0464] The memory is used to store computer instructions;

[0465] The transceiver is used to receive and send information;

[0466] The processor is coupled to the memory and is used to call computer instructions in the memory so that the communication device executes the method described in any one of embodiments 34-41.

[0467] Embodiment 102, a communication device, comprising a memory, a processor and a transceiver, wherein:

[0468] The memory is used to store computer instructions;

[0469] The transceiver is used to receive and send information;

[0470] The processor is coupled to the memory and is used to call computer instructions in the memory so that the communication device executes the method described in any one of embodiments 42-49.

[0471] Embodiment 103, a communication method, wherein the method comprises:

[0472] receiving a fourth DCI from the network device, where the fourth DCI is used to indicate a monitoring mode of a PDCCH;

[0473] The PDCCH is monitored according to the PDCCH monitoring method indicated by the fourth DCI.

[0474] Embodiment 104, as described in the method of Embodiment 103, the fourth DCI includes a third field, a first value of the third field indicates that the terminal device switches from monitoring PDCCH according to the fifth search space group to monitoring PDCCH according to the sixth search space group; the second value of the third field indicates that the terminal device does not switch the search space group to monitor PDCCH.

[0475] Embodiment 105: According to the method of embodiment 103, the fourth DCI indicates the terminal device to monitor the PDCCH according to a seventh search space group, and the seventh search space group does not include a search space;

[0476] When the fourth DCI is received, the third timer is not running, and the third timer is started or restarted; the third timer is related to the seventh search space; when the fourth DCI is received, the third timer is running, and the third timer is not restarted.

[0477] Embodiment 106, as described in Embodiment 103, the fourth DCI includes a fourth field, a value of one of the fourth field indicates that the terminal device does not monitor the PDCCH within a preset time domain length; a value of two of the fourth field indicates that the terminal device does not perform a new operation or indicates that the terminal device does not perform a skip PDCCH operation.

[0478] Embodiment 107, a communication method, wherein the method comprises:

[0479] Determining a fourth DCI;

[0480] The fourth DCI is sent to the terminal device, where the fourth DCI is used to indicate a monitoring method for the PDCCH.

[0481] Embodiment 108, as described in the method of Embodiment 107, the fourth DCI includes a third field, a first value of the third field indicates that the terminal device switches from monitoring PDCCH according to the fifth search space group to monitoring PDCCH according to the sixth search space group; the second value of the third field indicates that the terminal device does not switch the search space group to monitor PDCCH.

[0482] Embodiment 109: As used in the method of Embodiment 107, the fourth DCI instructs the terminal device to monitor the PDCCH according to a seventh search space group, and the seventh search space group does not include a search space.

[0483] Embodiment 110, as described in Embodiment 107, the fourth DCI includes a fourth field, a value of one of the fourth field indicates that the terminal device does not monitor the PDCCH within a preset time domain length; a value of two of the fourth field indicates that the terminal device does not perform a new operation or indicates that the terminal device does not perform a skip PDCCH operation.

[0484] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

[0485] Based on the above embodiments, an embodiment of the present application provides a communication system, which may include the terminal device and network device involved in the above embodiments.

[0486] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program. When the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.

[0487] An embodiment of the present application further provides a computer program product, which is used to store a computer program. When the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.

[0488] An embodiment of the present application also provides a chip, including a processor, wherein the processor is coupled to a memory and is used to call a program in the memory so that the chip implements the communication method provided by the above method embodiment.

[0489] An embodiment of the present application also provides a chip, which is coupled to a memory and is used to implement the communication method provided in the above method embodiment.

[0490] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0491] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0492] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0493] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0494] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: include: Receive first downlink control information DCI from a network device, where the first DCI instructs the terminal device not to monitor a physical downlink control channel PDCCH within a first time domain length; After receiving the first DCI, receiving a second DCI from a network device within a second time domain length, where the second time domain length belongs to the first time domain length; According to the second DCI, it is determined that the terminal device does not monitor PDCCH within a third time domain length, the starting position of the third time domain length is the end position of the second time domain length or is after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

2. The method according to claim 1, characterized in that The second DCI includes a first field, and a first value of the first field indicates that the terminal device does not switch the search space group to monitor the PDCCH; The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space; Determining, according to the second DCI, not to monitor the PDCCH within a third time domain length includes: According to the first field in the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

3. The method according to claim 2, characterized in that The second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, where the second search space group includes at least one search space.

4. The method according to claim 1, characterized in that The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, and the third search space group does not include a search space; The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group; Determining, according to the second DCI, not to monitor the PDCCH within the third time domain length includes: Determine that a first timer is running when the second DCI is received, the first timer is not restarted, and determine not to monitor PDCCH within the third time domain length, wherein the first timer is related to the third search space.

5. The method according to claim 4, characterized in that The method further comprises: When the first DCI is received, the first timer is not running, and the first timer is started or restarted.

6. The method according to claim 1, characterized in that Determining, according to the second DCI, not to monitor the PDCCH within the third time domain length includes: When the second DCI indicates a monitoring mode of the PDCCH, determining that the monitoring mode of the PDCCH indicated by the second DCI is not effective; It is determined not to monitor the PDCCH within the third time domain length.

7. The method according to claim 1, characterized in that The second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation; Determining, according to the second DCI, not to monitor the PDCCH within the third time domain length includes: According to the second field of the second DCI being the first value, it is determined not to monitor the PDCCH within the third time domain length.

8. The method according to claim 7, characterized in that The second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

9. The method according to claim 1, characterized in that The second DCI indicates monitoring the PDCCH according to a fourth search space group, and the fourth search space group is the same as the currently monitored search space group; the fourth search space group includes at least one search space; Determining, according to the second DCI, not to monitor the PDCCH within a third time domain length includes: Determining that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group; It is determined not to monitor the PDCCH within the third time domain length.

10. The method according to any one of claims 1 to 9, characterized in that: The second time domain length includes a first sub-time domain length, and the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

11. The method according to claim 10, characterized in that The second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

12. The method according to any one of claims 1 to 9, characterized in that: The second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

13. The method according to claim 10, characterized in that The first HARQ process is a downlink HARQ process.

14. The method according to claim 12, characterized in that The third HARQ process is a downlink HARQ process.

15. The method according to claim 10, characterized in that The method further comprises: A third DCI is received from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

16. A communication method, characterized in that: include: Sending first downlink control information DCI to a terminal device, where the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time domain length; After sending the first DCI, a second DCI is sent to the terminal device within a second time domain length, and the second time domain length belongs to the first time domain length; the second DCI is used by the terminal device to determine not to monitor PDCCH within a third time domain length, and the starting position of the third time domain length is the end position of the second time domain length or is located after the second time domain length, and the end position of the third time domain length is the end position of the first time domain length.

17. The method according to claim 16, characterized in that The second DCI includes a first field, and a first value of the first field indicates that the search space group monitoring PDCCH is not switched; The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: The first DCI instructs the terminal device to monitor the PDCCH according to a first search space group, and the first search space group does not include a search space.

18. The method according to claim 17, characterized in that The second value of the first field indicates that the terminal device monitors the PDCCH according to a second search space group, where the second search space group includes at least one search space.

19. The method according to claim 16, characterized in that The first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, where the third search space group does not include a search space; The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group; When the second DCI is sent, the first timer is running, the first timer is not restarted, and the first timer is related to the third search space.

20. The method of claim 16, wherein: The second DCI includes a second field, and a first value of the second field indicates that the terminal device does not perform a new operation.

21. The method of claim 20, wherein: The second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length.

22. The method of claim 16, wherein: The second DCI indicates that the PDCCH is monitored according to a fourth search space group, and the fourth search space group is the same as the search space group currently monitored by the terminal device; the fourth search space group includes at least one search space.

23. The method according to any one of claims 16 to 22, characterized in that: The second time domain length includes a first sub-time domain length, and the first sub-time domain length is the running time of the retransmission timer corresponding to the first hybrid automatic repeat request HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

24. The method of claim 23, wherein: The second time domain length also includes a second sub-time domain length, and the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process; the second HARQ process is one of the multiple HARQ processes of the terminal device.

25. The method according to any one of claims 16 to 22, characterized in that: The second time domain length is the running time of the retransmission timer corresponding to the third hybrid automatic repeat request HARQ process; the third HARQ process is the HARQ process corresponding to the first DCI.

26. The method of claim 23, wherein: The first HARQ process is a downlink HARQ process.

27. The method of claim 25, wherein: The third HARQ process is a downlink HARQ process.

28. The method of claim 23, wherein: The method further comprises: A third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate successful transmission of uplink data.

29. A communication device, characterized in that: Includes memory, processor and transceiver, where: The memory is used to store computer instructions; The transceiver is used to receive and send information; The processor is coupled to the memory and is configured to call computer instructions in the memory so that the communication device executes the method according to any one of claims 1 to 15.

30. A communication device, characterized in that: Includes memory, processor and transceiver, where: The memory is used to store computer instructions; The transceiver is used to receive and send information; The processor is coupled to the memory, and is used to call the computer instructions in the memory to enable the communication device to execute the method according to any one of claims 16-28.

31. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when called by the computer, are used to enable the computer to execute the method described in any one of claims 1 to 15, or to execute the method described in any one of claims 16 to 28.

32. A computer program product comprising instructions, characterized in that When the computer program product is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 15, or execute the method according to any one of claims 16 to 28.

33. A chip, characterized in that: The chip is coupled to the memory and is used to read and execute program instructions stored in the memory to implement the method as described in any one of claims 1-15, or to implement the method as described in any one of claims 16-28.

Images