WO2022262531A1 - Communication method and apparatus - Google Patents

Abstract

A communication method and apparatus, which are used for determining how a terminal device monitors a PDCCH after DCI is received during a retransmission time period. The method comprises: a terminal device receiving first DCI from a network device, receiving second DCI from the network device in a second time domain length after receiving the first DCI, and determining, according to the second DCI, that the terminal device does not monitor a PDCCH in a third time domain length, wherein the first DCI indicates that the terminal device does not monitor a PDCCH in a first time domain length; the second time domain length belongs to the first time domain length; and 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. In this way, when a terminal device receives DCI during a retransmission time period, it is possible to keep the time for skipping a PDCCH, which is indicated by initially transmitted DCI, still valid.

Description

A communication method and device

Cross References to Related Applications

This application claims the priority of the Chinese patent application submitted to the China Patent Office on June 16, 2021, with the application number 202110665649.5 and the application name "A Method for Indicating PDCCH Adaptation", the entire content of which is incorporated by reference in this application ; This application claims the priority of the Chinese patent application submitted to the China Patent Office on July 29, 2021, the application number is 202110864935.4, and the application name is "a communication method and device", the entire content of which is incorporated in this application by reference .

technical field

The present application relates to the technical field of communication, and in particular to a communication method and device.

Background technique

Before data transmission between the network device and the terminal device, 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 the scheduling information, the terminal device needs to follow the configuration of the network device The PDCCH is monitored frequently. However, frequent monitoring of the PDCCH by the terminal equipment will result in high power consumption of the terminal equipment. At present, research on power saving of terminal equipment is becoming more and more common, and detailed optimization schemes for reducing power consumption of terminal equipment have become a research direction in the industry.

Contents of the invention

The present application provides a communication method and device for clarifying how a terminal device monitors a PDCCH after receiving DCI within a retransmission period.

In a first aspect, the present application provides a communication method, which can be applied to a terminal device, a processor in the terminal device, a chip or a functional module, and the like. The method may include: receiving first downlink control information (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 according to the second DCI, it is determined that the terminal device does not monitor the PDCCH within the third time domain length; 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 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 after the second time domain length, and the The end position of the third time domain length is the end position of the first time domain length.

Through the above method, when the DCI is received during the retransmission period, the end time of skipping the PDCCH indicated by the initial transmission DCI can still be kept valid.

In a possible design, the second DCI includes a first field, and the 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 indicates that the terminal device Not monitoring the PDCCH within the first time domain length may specifically be: 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; furthermore, According to the second DCI, it is determined not to monitor the PDCCH within the third time domain length. The specific method may be: according to the first value of the first field in the second DCI, determine that in the third time domain The PDCCH is not monitored within the field length.

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 no switching The search space group monitors the PDCCH, so as not to affect the terminal equipment not to monitor the end time of the PDCCH.

In a possible design, 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.

In a possible design, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, specifically: the first DCI instructs the terminal device to monitor the PDCCH according to the third search space group , 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; furthermore, according to the second DCI, it is determined that in the third time domain Not monitoring the PDCCH within the length, the specific method may be: determine that the first timer is running when the second DCI is received, the first timer is not restarted, and determine that the PDCCH is not monitored within the third time domain length, Wherein, the first timer is related to the third search space.

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

In a possible design, the first timer is not running when the first DCI is received, 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.

In a possible design, it is determined according to the second DCI not to monitor the PDCCH within the third time domain length. The specific method may be: when the second DCI indicates a PDCCH monitoring mode, determine the second The PDCCH monitoring manner indicated by the DCI does not take effect; it is determined not to monitor the PDCCH within the third time domain length. In this way, the terminal device itself is instructed by the first DCI not to monitor the PDCCH within the first time domain length, and when the indication of the second DCI received in the retransmission period does not take effect, the content indicated by the first DCI is still valid, and the terminal device does not monitor the PDCCH. The end time of the PDCCH is still the end position of the first time domain length.

In a possible design, 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; it is determined according to the second DCI that in the third time domain The specific method of not monitoring the PDCCH within the length may be: according to the first value of the second field of the second DCI, determine not to monitor the PDCCH within the third time domain length.

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 A new operation is performed to realize that the terminal equipment does not monitor the end time of the PDCCH.

In a 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.

In a possible design, the second DCI indicates to monitor 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 group space; according to the second DCI, it is determined not to monitor the PDCCH within the third time domain length, and the specific method may be: determine that the fourth search space group indicated by the second DCI is the same as the currently monitored search space group; determine The PDCCH is not monitored during the third time domain length. In this way, the network device can indicate the search space group that the terminal device is currently monitoring or using for the terminal device. In this way, for the terminal device, no new indication is received, the monitored search space group remains unchanged, and the end time of PDCCH is not monitored. Change.

In a possible design, the second time domain length includes a first sub-time domain length, and the first sub-time domain length is a retransmission request (hybrid automatic repeat request, HARQ) process corresponding to the first hybrid automatic repeat request (HARQ) process. transmit the running time of the timer; 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 any time when any HARQ process may be retransmitted, and can avoid data retransmission failure of a certain HARQ process.

In a possible design, the second time domain length further 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 The HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at any time when any HARQ process may be retransmitted, and can avoid data retransmission failure of a certain HARQ process.

In a possible design, 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. In this way, the time for monitoring the PDCCH can be shortened, and the power consumption of the terminal equipment can be reduced.

In a possible design, the first HARQ process is a downlink HARQ process.

In a possible design, the third HARQ process is a downlink HARQ process.

In a possible design, a third DCI from the network device is received within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

In a second aspect, the present application provides a communication method, which can be applied to a network device, a processor in the network device, a chip or a functional module, and the like. The method may include: sending 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 the 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 second DCI is used by the terminal device to determine The PDCCH is not monitored within the length, the starting position of the third time domain length is the end position of the second time domain length or 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.

Through the above method, when the terminal device receives the DCI in the retransmission period, it can keep the end time of skipping the PDCCH indicated by the initial transmission DCI still valid.

In a possible design, the second DCI includes a first field, and the first value of the first field indicates not to switch the search space group to monitor the PDCCH; the first DCI indicates that the terminal device Not monitoring the PDCCH within a time domain length may specifically be: 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.

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 no switching The search space group monitors the PDCCH, so as not to affect the terminal equipment not to monitor the end time of the PDCCH.

In a possible design, 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.

In a possible design, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, specifically: the first DCI instructs the terminal device to group Monitoring PDCCH, 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; wherein, when the second DCI is sent, the first timer is running running, the first timer is not restarted, and the first timer is related to the third search space.

Through the above method, when the terminal device is already monitoring or using the empty search space group (that is, the third search space group), the network device is instructed by the network device to monitor the PDCCH according to the empty search space group during the retransmission period, and the first timer The running time of the PDCCH will not be affected, so that the terminal equipment does not monitor the end time of the PDCCH unchanged.

In a 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 (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 instruct the terminal device not to perform new operations , so as not to affect the terminal equipment not to monitor the end time of the PDCCH.

In a 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.

In a possible design, the second DCI indicates to monitor the 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 Include at least one search space. In this way, the network device can indicate the search space group that the terminal device is currently monitoring or using for the terminal device. In this way, for the terminal device, no new indication is received, the monitored search space group remains unchanged, and the end time of PDCCH is not monitored. Change.

In a 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 the retransmission timer corresponding to the 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 any time when any HARQ process may be retransmitted, and can avoid data retransmission failure of a certain HARQ process.

In a possible design, the second time domain length further 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 The HARQ process is one of multiple HARQ processes of the terminal device. In this way, the terminal device can monitor the PDCCH at any time when any HARQ process may be retransmitted, and can avoid data retransmission failure of a certain HARQ process.

In a possible design, 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 . In this way, the time for the terminal equipment to monitor the PDCCH can be shortened, and the power consumption of the terminal equipment can be reduced.

In a possible design, the first HARQ process is a downlink HARQ process.

In a possible design, the third HARQ process is a downlink HARQ process.

In a possible design, a third DCI is sent to the terminal device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

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

In a possible design, the structure of the communication device includes a transceiver unit and a processing unit, and these units can perform the corresponding functions in the above-mentioned first aspect or in each possible design example of the first aspect, for details, refer to Detailed description will not be repeated here.

In a possible design, the structure of the communication device includes a transceiver and a processor, and optionally also includes a memory, and the transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system, The processor is configured to support the communication device to execute corresponding functions in the first aspect or each possible design example of the first aspect. The memory, coupled to the processor, holds program instructions and data necessary for the communication device.

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

In a possible design, the structure of the communication device includes a transceiver unit and a processing unit, and these units can perform the corresponding functions in the above-mentioned second aspect or in each possible design example of the second aspect. For details, refer to Detailed description will not be repeated here.

In a possible design, the structure of the communication device includes a transceiver and a processor, and optionally also includes a memory, and the transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system, The processor is configured to support the communication device to execute corresponding functions in the second aspect or each possible design example of the second aspect. The memory, coupled to the processor, holds program instructions and data necessary for the communication device.

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

In the sixth aspect, the embodiments of the present application provide a computer-readable storage medium, the computer-readable storage medium stores program instructions, and when the program instructions are run on the computer, the computer executes the first aspect and its In any possible design, or the method described in the second aspect and any possible design thereof. Exemplary, computer readable storage media may be any available media that can be accessed by a computer. Taking this as an example without limitation: computer readable media may include non-transitory computer readable media, random-access memory (random-access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable In addition to programmable read-only memory (electrically EPROM, EEPROM), CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or can be used to carry or store the desired program code in the form of instructions or data structures and can Any other media accessed by a computer.

In the seventh aspect, the embodiments of the present application provide a computer program product including computer program codes or instructions, which, when run on a computer, enable the computer to implement the above-mentioned first aspect or any possible design of the first aspect, or The method described in the above second aspect or any possible design of the second aspect.

In an eighth aspect, the present application also provides a chip, including a processor, the processor is coupled to a memory, and is used to read and execute program instructions stored in the memory, so that the chip realizes the above first aspect Or any possible design of the first aspect, or the method described in the above second aspect or any possible design of the second aspect.

For the various aspects in the above-mentioned third to eighth aspects and the possible technical effects of each aspect, please refer to the above-mentioned aspects for the first aspect or various possible solutions in the first aspect, or the second aspect or various possible solutions in the second aspect. The description of the technical effect that may be achieved by the scheme will not be repeated here.

Description of drawings

FIG. 1 is a schematic structural diagram of a communication system provided by the present application;

FIG. 2 is a schematic diagram of skipping PDCCH monitoring provided by the present application;

FIG. 3 is a schematic diagram of a search space group switching provided by the present application;

FIG. 4 is a schematic diagram of a HARQ retransmission provided by the present application;

FIG. 5 is a schematic diagram of monitoring a PDCCH during a retransmission period provided by the present application;

FIG. 6 is a flowchart of a communication method provided by the present application;

FIG. 7a is a schematic diagram of a second time domain length provided by the present application;

FIG. 7b is a schematic diagram of another second time domain length provided by the present application;

FIG. 8 is a schematic diagram of another second time domain length provided by the present application;

FIG. 9 is a schematic diagram of monitoring a PDCCH during a retransmission period provided by the present application;

FIG. 10 is a schematic diagram of monitoring retransmission DCI during the retransmission period provided by the present application;

FIG. 11 is a flowchart of another communication method provided by the present application;

FIG. 12 is a schematic diagram of a timer provided by the present application;

FIG. 13 is a flowchart of another communication method provided by the present application;

FIG. 14 is a schematic structural diagram of a communication device provided by the present application;

FIG. 15 is a structural diagram of a communication device provided by the present application.

detailed description

The application will be described in further detail below in conjunction with the accompanying drawings.

The embodiments of the present application provide a communication method and device for specifying how a terminal device monitors a PDCCH after receiving DCI within a retransmission period. Wherein, the method and the device described in this application are based on the same technical concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.

In the description of the present application, terms such as "first" and "second" 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 order. For example, in this application, the third may appear first and then the second, which is not limited in this application.

In the description in this application, "at least one (species)" refers to one (species) or multiple (species), and multiple (species) refers to two (species) or more than two (species).

In order to describe the technical solutions of the embodiments of the present application more clearly, the communication method and device provided in the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

Figure 1 shows the architecture of the communication system involved in the embodiment of the present application, the architecture of the communication system includes network equipment and terminal equipment, where:

The network device is a device with a wireless transceiver function or a chip that can be set on the network device, and the network device includes but is not limited to: a base station (generation node B, gNB), a radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP) in wireless fidelity (wireless fidelity, Wi-Fi) system Or a transmission point, TP), etc., 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).

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio unit (radio unit, RU). CU implements some functions of gNB, DU implements some functions of gNB, for example, CU implements radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer functions, DU implements wireless link Functions of the radio link control (radio link control, RLC), media access control (media access control, MAC) and physical (physical, PHY) layers. Because 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, therefore, under this architecture, high-level signaling, such as RRC layer signaling or PHCP layer signaling, can also be It is considered to be sent by DU, or sent by DU+RU. It can be understood that the network device may be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, a CU may be divided into network devices in the access network RAN, or a CU may be divided into network devices in the core network CN, which is not limited.

The terminal equipment may also be called user equipment (user equipment, UE), access terminal, subscriber unit, subscriber 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 (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety ( Wireless terminals in transportation safety, wireless terminals in smart cities, smart wearable devices (smart glasses, smart watches, smart headphones, etc.), wireless terminals in smart homes, etc., can also be Chips or chip modules (or chip systems) that can be installed in the above devices. The embodiments of the present application do not limit the application scenarios. In this application, a terminal device with a wireless transceiver function and a chip that can be installed in the aforementioned terminal device are collectively referred to as a terminal device.

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

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

When the network device schedules the terminal device to receive downlink data, or the network device schedules the terminal device to send uplink data, it will first send downlink control information (downlink control information, DCI), which contains a data scheduling information, the data scheduling information will instruct the physical Transmission parameters of a physical downlink shared channel (PDSCH) (which contains downlink data) or a physical uplink shared channel (PUSCH) (which contains uplink data), including PDSCH/PUSCH The time-frequency domain resource location of . Specifically, the above DCI is carried in the PDCCH. Among them, for the downlink data, the network device will indicate the K0 value through the time domain resource allocation (TDRA) field in the DCI, which is used to determine the time slot interval between the PDCCH and the PDSCH; for the uplink data, the network device will The K2 value is indicated by the TDRA field in the DCI, and is used to determine the time slot interval between the PDCCH and the PUSCH.

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.

When a terminal device receives its own DCI, it needs to blindly detect (blind detect, BD) the PDCCH sent to itself in the downlink control area, that is, the terminal device monitors (monitors) many PDCCH candidate positions (PDCCH candidates) to find out whether there are sent to myself. A group of candidate positions that the terminal device needs to blindly detect constitutes a search space (search space set, SSS), and the search space may also be referred to as a search space set. According to the configuration of the network device, the terminal device may monitor one (group) or multiple (groups) of search spaces to find out whether there is a PDCCH sent to itself. Wherein, the terminal equipment needs to monitor the position of the PDCCH, which may also be called a PDCCH monitoring occasion (PDCCH monitoring occasion).

If the terminal device has no business within a period of time, that is, when there is no downlink data or uplink data to be transmitted, the terminal device cannot receive the PDCCH sent to itself even if it monitors the PDCCH. If the terminal equipment still monitors the PDCCH during these times, it will cause power consumption of the terminal equipment.

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

Another solution for reducing 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 groups of pre-configured search spaces. For example, as shown in FIG. 3 , 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 may send an indication message to the terminal device, instructing the terminal device to switch from monitoring search space group 1 to monitoring search space group 2, thereby reducing the number of PDCCH monitoring and saving power consumption of the terminal device.

Both of the above two solutions can achieve the purpose of "reducing PDCCH monitoring". However, in the first scheme, the way of skipping PDCCH is more flexible and changeable, and is suitable for small time-scale scheduling changes (that is, there are frequent changes in scheduling and non-scheduling); in the second scheme, search space switching (later The method collectively known as search space set group switching ((search space set group, SSSG) switching) is applicable to the case of larger time scale changes. In order to obtain the benefits of the above two methods at the same time, it may be considered to support both functions at the same time. Exemplarily, the above two functions can be supported by the following three methods:

Method 1: SSSG switching is supported, and at the same time, the function of skipping the PDCCH is realized by using the SSSG switching. For example, the network device may configure an empty SSSG (which may be called an empty (empty) SSSG or a dormant (dormant) SSSG) for the terminal device. For example, the empty SSSG may be numbered as SSSG0 (which does not include any search space). The network device may instruct the terminal device to switch to use SSSG0, and the terminal device will not monitor the PDCCH when using SSSG0. At the same time, the network device configures or indicates a timer (timer) or a length of time, so that the terminal device automatically cuts out of the SSSG0 after using the SSSG0 for a period of time, so as to achieve the effect of skipping PDCCH monitoring for a period of time.

The second method is to explicitly support the functions of SSSG switching and PDCCH skipping. For example, the network device instructs the terminal device to skip PDCCH or SSSG switching through a flag bit, and then use other bits to indicate the specific content of skipping PDCCH or SSSG switching.

Method 3: explicitly support the functions of SSSG switching and PDCCH skipping. For example, the network device performs a joint encoding (joint encoding) instruction for skipping the PDCCH and SSSG handover. For example, M bits are used to indicate 2 ^M states, and each state can be configured to skip a period of time, and/or switch to a certain SSSG.

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

For downlink transmission, the terminal device will send 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 may schedule retransmission of the PDSCH. Since the network device determines the content carried in the HARQ feedback (that is, the terminal device fails to receive the PDSCH), and the network device sends the PDCCH to schedule the retransmission of the PDSCH, it takes a certain amount of time, so the network device will not schedule the data packet during this period of time. Even if the terminal device monitors the retransmission schedule of the data packet during this period, it will not receive the retransmission schedule. Therefore, the current standard defines a HARQ round trip time (round trip time, RTT) timer (timer). After the terminal device sends a negative acknowledgment (NACK) to the network device, the HARQ RTT timer will be started. During the running time of the HARQ RTT timer, the terminal equipment does not expect to receive the retransmission of the corresponding data packet. The standard also defines a HARQ retransmission timer (retransmission timer). After the HARQ RTT timer expires, the HARQ retransmission timer will start. If the terminal device sends a NACK to the network device, within the running time of the HARQ retransmission timer, the terminal device will monitor and expect to receive the retransmission of the corresponding data packet.

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 may directly send a PDCCH for scheduling retransmission of the PUSCH. Similar to downlink transmission, the NR standard also defines HARQ RTT timer and HARQ retransmission timer for uplink transmission. However, since there is no HARQ feedback for uplink transmission, the terminal device will start the HARQ RTT timer immediately after the PUSCH is sent. During the running time of the HARQ RTT timer, the terminal device does not expect to receive the retransmission of the corresponding data packet. The HARQ retransmission timer is similar to downlink transmission. After the HARQ RTT timer expires, the HARQ retransmission timer will start. During the running time of the HARQ retransmission timer, the terminal device will monitor and expect to receive the corresponding data packet. Retransmission.

In addition, in order to support parallel processing of multiple data packets, NR supports multiple HARQ processes (HARQ process), where each process can correspond to a data packet, and data packets corresponding to multiple processes are processed in parallel. Regardless of whether the data packet corresponding to one HARQ process is successfully transmitted, it will not affect the transmission of the data packet corresponding to another HARQ process. In order to ensure that each HARQ process does not affect each other, the aforementioned HARQ RTT timer and HARQ retransmission timer 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. Currently, in NR, there are at most 16 HARQ processes for uplink transmission, and at most 16 HARQ processes for downlink transmission.

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

In order to enable the terminal device to receive the retransmission DCI of the data scheduled by the network device under the above circumstances, the terminal device can be instructed not to monitor the PDCCH for a period of time (it can be realized by instructing to skip the PDCCH or use an empty SSSG), here A certain time period within the time period still monitors the PDCCH. For ease of description, the time period during which the PDCCH is still monitored can be referred to as a retransmission period (retransmission period), that is, the retransmission period is within a period of time when the PDCCH is not monitored, and the terminal device can still monitor the PDCCH during the retransmission period. It should be noted that the retransmission time period may also be replaced with another name, or the time period is not named, which is not limited in this application. In the description of this application, only the description of the retransmission period is taken as an example. As shown in Figure 5, regardless of uplink (UL) transmission or downlink (downlink, DL) transmission, the network device instructs the terminal device not to monitor for a period of time in the DCI of the last scheduled data initial transmission. In the case of PDCCH, 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 when the network device indicates that it does not monitor the PDCCH, so that the terminal device can receive the schedule data retransmission DCI. In one implementation manner, as shown in FIG. 5 , the retransmission period may be defined as the running time of the HARQ retransmission timer.

It should be noted that the retransmission timer setting time length shown in FIG. 5 is the time length when the preset retransmission timer expires, and the running time of the HARQ retransmission timer may be less than or equal to the retransmission timer setting time. length of time. When the retransmission timer does not expire, the terminal device detects the retransmission of DCI, that is, the retransmission timer stops when the PDCCH is detected. At this time, the retransmission timer runs for the retransmission period, which is the The device indicates the time during which the PDCCH is still monitored within a period of time when the PDCCH is not monitored. As shown in FIG. 5 , it is described by taking the running time of the retransmission timer shorter than the set time length of the retransmission timer as an example.

However, if the retransmission period is defined as the running time of the HARQ retransmission timer, 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, so this application proposes A communication method to specify the retransmission period.

It should be noted that in the embodiment of the present application, it may be a terminal device, a processor in a terminal device, a chip or a chip system, or a functional module that can monitor or not monitor the PDCCH in the embodiment of the present application; How the device monitors the PDCCH may be a network device, or a processor in the network device, or a chip or a chip system, or a functional module. In the following embodiments, the PDCCH monitoring method provided by the present application is described in detail by taking terminal equipment and network equipment as examples, but this application is not limited thereto.

Based on the above description, the embodiment of the present application provides a communication method for specifying a retransmission time period, which is applicable to the communication system shown in FIG. 1 . Referring to Figure 6, the specific process of the method may include:

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

Exemplarily, the first DCI can realize the indication of the first DCI by instructing the terminal device to skip the PDCCH, for example, the first DCI contains a flag bit indicating to skip the PDCCH, or the corresponding field of the first DCI indicates a state (state ) means skipping the PDCCH; or, the first DCI may also indicate the first DCI by instructing the terminal device to implement the first DCI according to the empty SSSG.

Step 602: The terminal device monitors the PDCCH within the second time domain length. Correspondingly, the network device sends the PDCCH within the second time domain length. Wherein, the second time domain length belongs to the first time domain length.

Wherein, the second time domain length can be understood as the retransmission period in the above introduction, that is, during the time when the indicated terminal device does not need to monitor the PDCCH (that is, within the first time domain length), it is additionally necessary to monitor the PDCCH period. The specific definition of the length of the second time domain can be divided into the following situations:

In case a1, the second time domain length may include multiple sub-time domain lengths, where each sub-time domain length in the multiple sub-time domain lengths is related to one HARQ process among the multiple HARQ processes of the terminal device.

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 by the network device for the terminal device, and currently unfinished data transmission The HARQ process or the HARQ process currently running with a timer is not limited in this application.

In this case a1, it can be understood that the second time domain length is a union of multiple sub-time domain lengths, where the multiple sub-time domain lengths may exist continuously or discretely, which is not limited in the present application.

For example, the second time domain length may include 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; further, the The second time domain length may further include a second sub-time domain length, and 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.

Exemplarily, the length of the first sub-time domain is related to the first HARQ process, specifically, the length of the first sub-time domain is the running time of the retransmission timer corresponding to the first HARQ process. The second sub-time domain length is related to the second HARQ process, which may be: the second sub-time domain length is the running time of the retransmission timer corresponding to the second HARQ process.

For example, Fig. 7a shows a schematic diagram of a second time domain length. It can be seen from Fig. 7a that there are data of two HARQ processes in the terminal device that need to be retransmitted, for example, the two HARQ processes are the first HARQ process and the second HARQ process. Within the running time of the retransmission timer corresponding to the first HARQ process, that is, within the first sub-time domain length, and within the running time of the retransmission timer corresponding to the second HARQ process, that is, the second sub-time domain length , the terminal equipment monitors the PDCCH.

Optionally, the first HARQ process can be both an uplink HARQ process and a downlink HARQ process, and similarly, the second HARQ process can be both an uplink HARQ process and a downlink HARQ process. It should be noted that, in FIG. 7a , only the first HARQ process and the second HARQ process are taken as an example for illustration, which is not intended as a limitation to the present application.

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 Within the length of the first sub-time domain, the terminal device still monitors the PDCCH. 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 Within the length of the second sub-time domain, the terminal device still monitors the PDCCH. As shown in FIG. 7b, the length of the first sub-time domain is shorter than the running time of the retransmission timer corresponding to the first HARQ process, and the length of the second sub-time domain is longer than the running time of the retransmission timer corresponding to the second HARQ process. It should be noted that Fig. 7b is only an example, and is not intended to limit the present application.

Through the method of case a1, the terminal device can monitor the PDCCH at the time when the data packet corresponding to any HARQ process may be retransmitted, which can avoid the data retransmission failure of a certain HARQ process.

In 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.

Exemplarily, the second time domain length is related to the third HARQ process, specifically, the second time domain length is the running time of the retransmission timer corresponding to the third HARQ process.

Optionally, the third HARQ process can be either an uplink HARQ process or a downlink HARQ process.

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

Although the method of the above case a1 can monitor the PDCCH at the time when the data packet corresponding to any HARQ process may be retransmitted, it can avoid the data retransmission failure of a certain HARQ process, but it may cause the duration of PDCCH monitoring to be skipped (skipping duration ) is relatively fragmented, which in turn may cause the terminal equipment to fail to enter deep sleep, resulting in a decline in the energy saving effect of skipping the PDCCH, and a decline in the power consumption optimization effect of the terminal equipment. Compared with the above-mentioned case a1, the above-mentioned problem can be avoided through the method of the above-mentioned case a2, and at the same time, the time for monitoring the PDCCH is shortened, and the power consumption of the terminal equipment is reduced.

In some other embodiments, similar to the foregoing FIG. 7 b , the length of the second time domain 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 In the second time domain length, the terminal equipment still monitors the PDCCH. Exemplarily, the illustration that the length of the second time domain is less than the running time of the retransmission timer corresponding to the third HARQ process can refer to the fact that the length of the first sub-time domain in Figure 7b is less than the running time of the retransmission timer corresponding to the first HARQ process For the illustration of the time, and the illustration of the length of the second time domain being greater than the running time of the retransmission timer corresponding to the third HARQ process, you can refer to the second sub-time domain length in Figure 7b being greater than the running time of the retransmission timer corresponding to the second HARQ process The indication of the time of , no longer drawing illustration here.

In a possible example, for uplink transmission, since there is no HARQ feedback, a retransmission timer (retransmission timer) will be started regardless of whether there is retransmission. If the uplink transmission does not need to be retransmitted, the retransmission timer will continue to run until the configured duration expires. For example, as shown in FIG. 9 , the terminal device monitors the PDCCH all the time within the retransmission timer of uplink transmission. When the configuration time of the retransmission timer for uplink transmission is relatively long (for example, 8 or 16 time slots (slots)), the skipping of PDCCH monitoring by the terminal equipment may fail to achieve the expected energy saving effect. Therefore, in order to avoid the above problems in uplink transmission, the retransmission period in uplink transmission, that is, the length of the second time domain, can be defined as follows:

In method b1, the length of the second time domain is the running time of the retransmission timer in the downlink transmission.

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

Optionally, when there is retransmission only in the uplink transmission, the scheduling of the uplink transmission may also be rescheduled after the first time domain length. That is, in this case, there is no retransmission timer for downlink transmission running, and the retransmission of uplink transmission can only be performed after skipping the PDCCH monitoring duration (skipping duration).

Further, in method b1, the second time domain length is the running time of the retransmission timer 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, multiple sub-time domains The length of each sub-time domain in the length is related to one downlink HARQ process among the multiple downlink HARQ processes of the terminal device, that is, the first HARQ process and the second HARQ process mentioned above are downlink HARQ processes in method b1. Alternatively, the second time domain length is the running time of the retransmission timer in the downlink transmission, which may be specifically the second time domain length in the above case a2. It should be noted that in method b1 at this time, the third HARQ process is the downlink HARQ process. process.

For method b2 and the second time domain length, reference may still be made to the definition of the second time domain length in the above-mentioned case a1 and case a2. In the method b2, the network device sends the 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 that the transmission of the uplink data is successful, that is, the third DCI indicates that the PUSCH is correctly transmitted, so that the terminal device stops monitoring the PDCCH.

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-scheduled (non-scheduled) -scheduling DCI). Optionally, when the frequency domain resource allocation type is type 0 (that is, resourceAllocation=resourceAllocationType0), the frequency domain resource allocation (frequency domain resource allocation, FDRA) field in the DCI of the above format can be set to all 0; when the frequency domain When the resource allocation type is type 1 (that is, 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 (that is, resourceAllocation=dynamicSwitch), the above format can be set to The FDRA field in the DCI is set to all 0s or all 1s.

Optionally, in addition to setting the preset value of the above-mentioned FDRA field, it can be further stipulated that a short HARQ response request (one-shot HARQ-ACK request) field does not exist or the value of this field is set to 0. Of course, the values of other fields can also be further specified, which will not be listed here.

Through the above method, the obtained third DCI is used to indicate that the DCI is not used for scheduling data, but is used to indicate that the transmission of uplink data is successful, that is, to indicate that the monitoring is stopped within the retransmission period (that is, within the second time domain length) PDCCH. The third DCI indicates that the PUSCH is correctly transmitted, so that the terminal equipment can quickly stop monitoring the PDCCH, avoiding the excessively long PDCCH monitoring time caused by the possible retransmission of the uplink transmission, thereby reducing the power consumption of the terminal equipment.

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.

In method b3, the network device configures the second time domain length as the running time of the retransmission timer in downlink transmission, or as the running time of the retransmission timer in downlink transmission and uplink transmission.

Exemplarily, the network device sends configuration information to the terminal device, where 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 according to 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.

For example, when the second time domain length is the second time domain length in the above case a1, each sub-time domain length in the multiple sub-time domain lengths is related to one of the multiple HARQ processes of the terminal device, wherein the terminal According to the configuration information of the network device, the device determines whether the HARQ process only belongs to the downlink HARQ process, or belongs to the downlink HARQ process or the uplink HARQ process; that is, the first HARQ process and the second HARQ process involved in the method b3 only belong to the downlink HARQ process. Whether the process belongs to the downlink HARQ process or 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 yet completed 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 yet completed transmission, the running time of the retransmission timer of the uplink HARQ process will not be used as a 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, whether it is the retransmission timer of the uplink HARQ process or the retransmission timer of the downlink HARQ process, its running time can be one Sub-time domain length.

For another example, when the second time domain length is the second time domain length in the above case a2, in method b3 at this time, whether the third HARQ process belongs to the downlink HARQ process, or whether it belongs to the downlink HARQ process or the uplink HARQ process depends on the terminal device The configuration information of the network device is determined. 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 the downlink HARQ process, and the first DCI can only be the DCI for scheduling the PDSCH. If the first DCI is the DCI for scheduling the PUSCH, and the third HARQ is the uplink HARQ process, then there will be no second time domain length, that is, the terminal device will not monitor the PDCCH within the first time domain length. When the configuration information indicates that the second time domain length can be associated with the uplink HARQ process and the downlink HARQ process, the third HARQ process can be both the uplink HARQ process and the downlink HARQ process, and correspondingly, the first DCI can be a PUSCH scheduling The DCI may also be the DCI for scheduling the 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.

Optionally, in a delay-sensitive scenario, the network device can configure the second time domain length as the running time of the retransmission timer in downlink transmission and uplink transmission, so that uplink retransmission can also be completed quickly. In the scenario where the delay is not sensitive and energy saving is concerned, the network device can configure the length of the second time domain to be only the running time of the retransmission timer in the downlink transmission, so that in the case of uplink retransmission, it can be used for a longer period of time. Monitor PDCCH.

Through the above communication method, it is possible to clarify the time when the terminal equipment needs to monitor the PDCCH within the period of time when it is instructed not to monitor the PDCCH, that is, the definition of the retransmission period is clarified, so that the terminal equipment can accurately monitor the retransmission-scheduled PDCCH.

Further, in the scenario of monitoring the PDCCH during the retransmission period shown in FIG. 5 above, and in the scenario of monitoring the PDCCH during the definite retransmission period in the communication method shown in FIG. 6 , the DCI for scheduling retransmission will also include PDCCH monitoring indication, when the terminal equipment receives the PDCCH monitoring indication, if it changes the indication of the previously received DCI (such as the initial transmission DCI), the following problems may exist:

The network device uses 1 bit in the DCI for PDCCH monitoring indication, where '0' means not skipping PDCCH (that is, continuously monitoring PDCCH), and '1' means skipping a fixed time domain length (called skipping duration) The PDCCH monitoring (that is, not monitoring the PDCCH within a fixed time domain length) is described as an example. As shown in Figure 10, in the schematic diagram of detecting the retransmission DCI during the retransmission period, if 1 bit in the retransmission DCI is "0", it indicates that the PDCCH is not skipped, and the terminal device will directly resume monitoring the PDCCH, which cannot save energy; If 1 bit in the retransmission DCI is "1", it indicates a fixed time domain length, so that the terminal device does not monitor the PDCCH within a fixed time domain length, and the terminal device does not monitor the PDCCH within a fixed time domain length. For the PDCCH, if the terminal device does not monitor the PDCCH for a longer period of time than the period indicated by the initial DCI transmission, it may cause an increase in delay.

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

It should be noted that the communication method can be realized based on the retransmission period (that is, the running time of the HARQ retransmission timer) that does not consider the HARQ process at present, or can be based on the retransmission period defined in the embodiment shown in FIG. 5 (that is, second time domain length), or may also be implemented based on a later redefined retransmission period, which is not limited in this application.

Exemplarily, the following only uses the implementation of the communication method based on the second time domain length defined in the embodiment shown in FIG. 5 as an example for illustration. 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 a later newly defined retransmission period, the second time domain length in the following description is replaced by the current retransmission period or a later newly defined retransmission period That's it.

Based on the above description, the embodiment of the present application provides a communication method to clarify how to keep the PDCCH skipping time indicated by the previous DCI still valid when the terminal device receives the DCI during the retransmission period. This method is applicable to the communication system shown in FIG. 1 . Referring to Figure 11, the specific process of the method may include:

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

Exemplarily, the first DCI can realize the indication of the first DCI by instructing the terminal device to skip the PDCCH, for example, the first DCI contains a flag bit indicating to skip the PDCCH, or the corresponding field of the first DCI indicates a state (state ) means skipping the PDCCH; or, the first DCI may also indicate the first DCI by instructing the terminal device to implement the first DCI according to the empty SSSG.

Step 1102: After sending the first DCI, the network device sends the 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.

Optionally, the second DCI may be a DCI for scheduling terminal device data retransmission for the network device.

Step 1103: The terminal device determines according to the second DCI that the terminal device does not monitor the PDCCH within the 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.

Wherein, the end position of the third time domain length is the end position of the first time domain length, that is, the end time for the terminal device to perform the operation of "not monitoring the PDCCH", and the skipping indicated by the initial transmission DCI (that is, the first DCI) The end positions of the time (that is, the length of the first time domain) of the PDCCH are the same. In this way, the impact on the timeline (timeline) in which the terminal equipment is instructed to skip the PDCCH can be minimized.

Specifically, according to the specific form of the first DCI and the indication of the second DCI, the execution of step 1103 by the terminal device may include the following methods:

Method c1. The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length. Specifically, it can be 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 the search space group. 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 may indicate the first DCI by instructing the terminal device according to an empty SSSG.

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

It should be noted that instructing the terminal device not to switch the search space group to monitor the PDCCH may also be described as instructing the terminal device not to switch the search space group to monitor.

Furthermore, when the first field of the second DCI is the first value, the terminal device determines according to the second DCI to continue to monitor the PDCCH according to the first search space group within the third time domain length, that is, not to monitor the PDCCH. It is: the terminal device determines not to monitor the PDCCH within the third time domain length according to the first value of the first field in the second DCI.

That is to say, in the 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 the PDCCH, that is, to continue to monitor the PDCCH according to the empty first search space group, so as not to affect the end time of the terminal device not monitoring the PDCCH (that is, the terminal device's original skip Deadline (skipping timeline)).

Method c2. The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length. Specifically, it can be implemented in the following manner: the first DCI instructs the terminal device to monitor the PDCCH according to the third search space group, and the third search space group does not include search space, that is, the third search space group is an empty search space group (emptySSSG or dormant SSSG).

Optionally, when the first timer is not running when the terminal device receives the first DCI, start or restart the first timer, where the first timer is related to the third search space.

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

Furthermore, the terminal device determines not to monitor the PDCCH within the third time domain length according to the second DCI. Specifically, the terminal device determines that the first timer is running when the second DCI is received, and the first timer is not restarted. The PDCCH is not monitored within the length of the three time domains.

Optionally, the second time domain length may be associated with the second timer. That is, the second timer is a timer for controlling the terminal device to monitor the PDCCH within the retransmission period, and its duration can be set as the length of the second time domain. 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, in the schematic diagram shown in FIG. 12 , 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 being restarted. Until the first timer expires, the first time domain length ends.

In this way, in the method c2, when the terminal device is already monitoring or using the empty search space group (that is, the third search space group), it is instructed by the network device to monitor the PDCCH according to the empty search space group during the retransmission period. The running time of a timer will not be affected, and the end time of not monitoring the PDCCH can be kept unchanged.

Method c3, the terminal device determines not to monitor the PDCCH within the third time domain length according to the second DCI, which may specifically be: when the second DCI indicates the PDCCH monitoring mode, the terminal device determines the PDCCH indicated by the second DCI The monitoring mode does not take effect, so it is determined that the PDCCH is not monitored within the third time domain length.

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

In this method c3, the terminal device itself is instructed by the first DCI not to monitor the PDCCH within the first time domain length, and when the received indication of the second DCI does not take effect within the retransmission period, the content indicated by the first DCI is still valid, The end time of the terminal device not monitoring the PDCCH is still the end position of the first time domain length.

It should be noted that, in the method c3, the second DCI may be a retransmission DCI (DCI for the network device to schedule terminal device data retransmission), or may be a non-retransmission DCI. When the second DCI can be retransmission DCI or non-retransmission DCI, the network device cannot change the end time of not monitoring the PDCCH indicated by the first DCI within the retransmission period. When the second DCI can only be a retransmission DCI, in method c3, the retransmission DCI will not affect the end time of not monitoring the PDCCH indicated by the first DCI, and the non-retransmission DCI (for example, the initial transmission DCI) can also indicate a new Not to monitor the end time of the PDCCH, that is, to allow the network device to change the end time of the terminal device not to monitor the PDCCH through the initial transmission DCI in some necessary situations.

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 (no new behavior)); the second value of the second field A value instructs the terminal device not to monitor the PDCCH for the preset time domain length.

Exemplarily, the first value may be a reserved value (reserved), which may also be called a reserved value. This reserved value means that the standard does not define the meaning corresponding to this value, or the network device is not configured with the meaning corresponding to this 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 the change of the monitoring PDCCH mode has been received, so the terminal device does not perform related operations, that is, does not perform new operations.

When the second field of the second DCI is the first value, the terminal device determines not to monitor the PDCCH within the third time domain length according to the second DCI, which may specifically be: the terminal device is the first value according to the second field of the second DCI One value, it is determined not to monitor the PDCCH within the third time domain length.

That is to say, in the 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 instruct the terminal device not to perform new operations, so as not to affect the end time of the terminal device not monitoring the PDCCH (that is, the original skipping timeline (skipping timeline) of the terminal device).

In some embodiments, when a DCI received by the terminal device from the 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 The operation of skipping the PDCCH is not performed (that is, the terminal device is instructed to continue monitoring the PDCCH). That is to say, the same value of the same field in the DCI of the same format received at different time periods may have different indication meanings, which is not limited in this application.

Method c5, the second DCI indicates to monitor the PDCCH according to the 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.

The terminal device determines not to monitor the PDCCH within the third time domain length according to the second DCI. Specifically, 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; PDCCH is not monitored within the 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 according to the current search space group (that is, the fourth search space group) according to the indication of the second DCI. Four search space groups) monitor the PDCCH, so the end time of the terminal device not monitoring the PDCCH will not be changed, that is, the end time of the terminal device not monitoring the PDCCH will not change, so the PDCCH will not be monitored within the third time domain length.

In this method c5, the network device can indicate the search space group that the terminal device is currently monitoring or using, so that the terminal device does not receive a new indication, the monitored search space group remains unchanged, and the end time of the PDCCH is not monitored constant.

The method c5 can be used as a constraint on network devices. For example, for the second method in the foregoing introduction, it may indicate that the terminal device expects to only receive flag bits during the retransmission period to indicate search space group switching (UE expects to only receive flag=SSSG switching during retransmission period); In the third method, the UE expects to only receive SSSG switching indication during retransmission period (UE expects to only receive SSSG switching indication during retransmission period).

In method c6, the format of the second DCI is format 1_0 or format 0_0.

In the method c6, the terminal device may only monitor the DCI not including the PDCCH monitoring mode, that is, the DCI of format 1_0 or format 0_0. Wherein, the DCI of the format 1_0 or the format 0_0 may also be called a fallback (fallback) DCI. The fallback DCI does not include information indicating the change of the PDCCH monitoring mode, so it does not affect the end time of the terminal equipment not monitoring the PDCCH.

According to the definition in the current standard, in the common search space (common search space, CSS), the terminal device monitors the fallback (fallback) DCI, and does not monitor the non-fallback (non-fallback) DCI. In the terminal device specific search space (UE specific search space, USS), the terminal device monitors one of fallback (fallback) DCI and fallback (fallback) DCI according to the configuration of the network device. Therefore, in this method c6, when only fallback (fallback) DCI is used to schedule retransmission within the retransmission period, the terminal device can only monitor the CSS and the USS configured to monitor the fallback (fallback) DCI, so that to a certain extent Blind detection can be reduced, thereby saving power consumption of terminal equipment.

By adopting the communication method provided by the embodiment of the present application, the influence of the retransmitted DCI on the end time of not monitoring the PDCCH indicated by the initially transmitted DCI can be avoided.

In addition, the embodiment of the present application also proposes a communication method, which is used to propose a monitoring method in which the network device instructs the terminal device PDCCH through DCI. Referring to FIG. 13 , the specific process of the method may include the following steps:

Step 1301: The network device sends a fourth DCI to the terminal device, where the fourth DCI is used to indicate a PDCCH monitoring manner.

Step 1302: The terminal device monitors the PDCCH according to the PDCCH monitoring manner indicated by the fourth DCI.

Exemplarily, the monitoring manner of the PDCCH indicated by the fourth DCI may include the following manners:

Mode d1, the fourth DCI includes a third field, the first value of the third field indicates that the terminal device switches from monitoring the PDCCH according to the fifth search space group to monitoring the PDCCH according to the sixth search space group; the first value of the third field The two values indicate that the terminal equipment does not switch the search space group to monitor the PDCCH.

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

It should be noted that the fifth search space group may include at least one search space, or may not include any search space (that is, an empty search space). Similarly, the sixth search space group may include at least one search space, or may not include any search space (that is, an empty search space). The fifth search space group and the sixth search space group may or may not be the same, which is not limited in this application.

Manner 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.

Correspondingly, when the terminal device receives the fourth DCI, the third timer is not running, start or restart the third timer; the third timer is related to the seventh search space; when the terminal device receives the fourth The third timer is running during DCI, and the third timer is not restarted.

That is, in the manner d2, the terminal device does not monitor the PDCCH during the running of the third timer.

Mode d3, the fourth DCI includes a fourth field, the value of the fourth field indicates that the terminal equipment does not monitor the PDCCH within the preset time domain length; the value of the fourth field indicates that the terminal equipment does not perform new operations (also That is, instruct the terminal device to have no new behavior (no new behavior)), or indicate not to perform the PDCCH skipping (PDCCH skipping) operation (that is, instruct the terminal device to continue monitoring the PDCCH).

Correspondingly, when the fourth field of the fourth DCI has a value of 1, the terminal device does not monitor the PDCCH within the preset time domain length; when the fourth field of the fourth DCI has a value of 2, the terminal device monitors the PDCCH according to the current PDCCH monitor the PDCCH in the same way or the terminal equipment continues to monitor the PDCCH.

It should be noted that the above-mentioned fourth DCI may be the initial transmission DCI, may also be the DCI in the retransmission period, or may also be the retransmission DCI, which is not limited in this application.

Optionally, when the fourth DCI is the DCI in the retransmission period, the value 2 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 the DCI in the retransmission period, the second The value two of the four DCIs indicates that the terminal equipment does not perform the PDCCH skipping operation.

It should be understood that when the fourth DCI is the DCI in the retransmission period, the fourth DCI may correspond to the second DCI in the embodiment shown in FIG. 11 . For example, the first field included in the second DCI shown in FIG. 11 may be the third field of the fourth DCI in the above manner d1, and the first value of the first field corresponds to the second value of the third field. The second value of a field corresponds to the first value of the third field. For another example, the fourth DCI in manner d2 corresponds to the second DCI in method c2 in the embodiment shown in FIG. 11 . For another example, the second field in the second DCI shown in FIG. 11 may be the fourth field of the fourth DCI in the above manner d3, and the value of the first value of the second field and the value of the fourth field indicate that the terminal device does not perform new DCI. Operation correspondence, the second value of the second field corresponds to the value of the fourth field. It should be understood that the above is only an example, and the present application does not limit it.

Based on the above embodiments, this embodiment of the present application also provides a communication device. Referring to FIG. 14 , a communication device 1400 may include a transceiver unit 1401 and a processing unit 1402 . Wherein, 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 .

Exemplarily, the communication device 1400 may specifically be the terminal device in the above embodiments, a 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 It is the network device in the above embodiments, the processor of the network device, or a chip, or a chip system, or a functional module.

In an embodiment, when the communication device 1400 is used to implement the functions of the terminal device in the embodiment described in FIG. 11 , it may specifically include:

The transceiver unit 1401 is configured to receive a first DCI from a network device, the first DCI instructs the terminal device not to monitor the PDCCH within a first time domain length; and after receiving the first DCI, at a second time receiving a second DCI from the network device within a domain length, where the second time domain length belongs to the first time domain length; the processing unit 1402 is configured to determine, according to the second DCI, that the terminal device is The PDCCH is not monitored within the domain length, the starting position of the third time domain length is the end position of the second time domain length or after the second time domain length, and the end of the third time domain length The position is the end position of the first time domain length.

In an optional implementation manner, the second DCI includes a first field, and the 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 indicates that the The terminal device does not monitor the PDCCH within the first time domain length, including: 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; When the processing unit 1402 determines according to the second DCI that the PDCCH is not to be monitored within the third time domain length, it is specifically configured to: according to the first value of the first field in the second DCI, determine in The PDCCH is not monitored within the third time domain length.

Exemplarily, 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.

In another optional implementation manner, the first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: the first DCI instructing the terminal device to group Monitor the PDCCH, 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; the processing unit 1402 determines in accordance with the second DCI When the PDCCH is not monitored within the third time domain length, 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 the The PDCCH is not monitored within the third time domain length, wherein the first timer is related to the third search space.

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.

In yet another optional implementation manner, 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 configured to: when the second DCI indicates a PDCCH When the PDCCH monitoring mode indicated by the second DCI is determined to be ineffective, it is determined that the PDCCH is not monitored within the third time domain length.

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

In yet another optional implementation manner, 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 second DCI determines that the PDCCH is not monitored within the third time domain length, it is specifically used to: determine that within the third time domain length according to the second field of the second DCI being the first value PDCCH is not monitored.

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

In yet another optional implementation manner, the second DCI indicates to monitor 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 including at least one search space; 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 configured to: determine the fourth search space group indicated by the second DCI It is the same as the currently monitored search space group; it is determined not to monitor the PDCCH within the third time domain length.

In an 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 the retransmission timer corresponding to the first HARQ process; the first HARQ process is One of multiple HARQ processes of the terminal device.

Optionally, the second time domain length further 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 multiple HARQ processes of the terminal device.

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.

Optionally, the first HARQ process is a downlink HARQ process.

Optionally, the third HARQ process is a downlink HARQ process.

In an optional implementation manner, the transceiving unit 1401 is further configured to: receive a third DCI from the network device within the second time domain length, the third DCI is used to indicate the uplink data The transfer was successful.

In another embodiment, when the communication device 1400 is used to implement the functions of the network device in the embodiment described above in FIG. 11 , it may specifically include:

The transceiving unit 1401 is configured to send a first DCI to the terminal device, the first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length; and, after sending the first DCI, in the second Sending a second DCI to the terminal device within a time domain length, where 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 within the third time domain length PDCCH, the starting position of the third time domain length is the end position of the second time domain length or after the second time domain length, and the end position of the third time domain length is the end position of the second time domain length An end position of a time domain length; the processing unit 1402 is configured to control the transceiver unit 1401 to perform the above sending operation.

In an optional implementation manner, the second DCI includes a first field, and the first value of the first field indicates not to switch the search space group to monitor the PDCCH; the first DCI indicates that the terminal device is in the The not monitoring 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.

Exemplarily, 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.

In another optional implementation manner, the first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length includes: the first DCI instructing the terminal device to search The space group monitors the PDCCH, 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; wherein, the first timing when sending the second DCI The timer is running, the first timer is not restarted, and the first timer is related to the third search space.

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

In another optional implementation manner, 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.

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

In another optional implementation manner, the second DCI indicates to monitor the 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 first A group of four search spaces includes at least one search space.

In an 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 the retransmission timer corresponding to the first HARQ process; the first HARQ process It is one of multiple HARQ processes of the terminal device.

Optionally, the second time domain length further 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 multiple HARQ processes of the terminal device.

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 .

Optionally, the first HARQ process is a downlink HARQ process.

Optionally, the third HARQ process is a downlink HARQ process.

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

In another embodiment, when the communication device 1400 is used to implement the functions of the terminal device in the embodiment described above in FIG. 6 , it may specifically include:

The transceiving unit 1401 is configured to receive a first DCI from a network device, the first DCI instructing the terminal device not to monitor the physical downlink control channel PDCCH within the first time domain length; the processing unit 1402 is configured to Monitor the PDCCH within the domain length; the second time domain length belongs to the first time domain length; the second time domain length includes the first sub-time domain length, and the first sub-time domain length is related to the first HARQ process related, the first HARQ process is one of the 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 one corresponding to the first DCI HARQ process.

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

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

Exemplarily, the second time domain length further 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 a plurality of HARQ processes of the terminal device one of the processes.

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

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

In an optional implementation manner, the transceiver unit 1401 is further configured to receive a third DCI from the network device within the second time domain length, and the third DCI is used to indicate the transmission of uplink data success.

In another embodiment, when the communication device 1400 is used to implement the functions of the network device in the embodiment described above in FIG. 6 , it may specifically include:

The transceiver unit 1401 is configured to send the first DCI to the terminal device, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length; and transmit the PDCCH within the second time domain length; the second time domain length Two time domain lengths belong 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 the 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; the processing unit 1402 uses It controls the transceiving unit 1401 to perform the above sending operation.

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

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

Exemplarily, the second time domain length further 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 a plurality of HARQ processes of the terminal device one of the processes.

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

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

In an optional implementation manner, the transceiving unit 1401 is further configured to send a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

It should be noted that the division of units in the embodiment of the present application is schematic, and is only a logical function division, and there may be another division manner in actual implementation. Each functional unit in the embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function 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 part of the contribution 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 several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Based on the above embodiments, this embodiment of the present application also provides a communication device. Referring to FIG. 15 , a communication device 1500 may include a transceiver 1501 and a processor 1502 . Optionally, the communication device 1500 may further include a memory 1503 . Wherein, the memory 1503 may be set inside the communication device 1500 , and may also be set outside the communication device 1500 . Wherein, the processor 1502 may control the transceiver 1501 to receive and send information or data and the like.

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

Wherein, the transceiver 1501, the processor 1502 and the memory 1503 are connected to each other. Optionally, the transceiver 1501, the processor 1502 and the memory 1503 are connected to each other through a bus 1504; the bus 1504 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 15 , but it does not mean that there is only one bus or one type of bus.

In an optional implementation manner, the memory 1503 is used to store programs and the like. Specifically, the program may include program code including computer operation instructions. The memory 1503 may include RAM, and may also include non-volatile memory (non-volatile memory), such as one or more disk memories. The processor 1502 executes the application program stored in the memory 1503 to realize the above functions, thereby realizing the functions of the communication device 1500 .

Exemplarily, the communication apparatus 1500 may be the terminal device in the foregoing embodiments; it may also be the network device in the foregoing embodiments.

In one embodiment, when the communication device 1500 realizes the functions of the terminal device in the embodiment shown in FIG. 6, the transceiver 1501 can realize the transceiving operation performed by the terminal device in the embodiment shown in FIG. 6; processing The device 1502 can implement other operations performed by the terminal device in the embodiment shown in FIG. 6 except the transceiving operation. For specific related specific descriptions, reference may be made to related descriptions in the above-mentioned embodiment shown in FIG. 6 , which will not be described in detail here.

In another embodiment, when the communication device 1500 implements the functions of the network equipment in the embodiment shown in FIG. 6 , the transceiver 1501 can implement the transceiving operations performed by the network equipment in the embodiment shown in FIG. 6 ; The processor 1502 may implement other operations performed by the network device in the embodiment shown in FIG. 6 except the transceiving operation. For specific related specific descriptions, reference may be made to related descriptions in the above-mentioned embodiment shown in FIG. 6 , which will not be described in detail here.

In another embodiment, when the communication apparatus 1500 realizes the functions of the terminal device in the embodiment shown in FIG. 11 , the transceiver 1501 can realize the transceiving operation performed by the terminal device in the embodiment shown in FIG. 11 ; The processor 1502 may implement other operations performed by the terminal device in the embodiment shown in FIG. 11 except the transceiving operation. For specific related specific descriptions, reference may be made to related descriptions in the above embodiment shown in FIG. 11 , which will not be described in detail here.

In another embodiment, when the communication device 1500 implements the functions of the network equipment in the embodiment shown in FIG. 11 , the transceiver 1501 can implement the transceiving operations performed by the network equipment in the embodiment shown in FIG. 11 ; The processor 1502 may implement other operations performed by the network device in the embodiment shown in FIG. 11 except the transceiving operation. For specific related specific descriptions, reference may be made to related descriptions in the above embodiment shown in FIG. 11 , which will not be described in detail here.

In combination with the above, this 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:

Embodiment 1. A communication method, wherein the method includes:

receiving a first DCI from the network device, the first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length;

After receiving the first DCI, receive a second DCI from the network device within a second time domain length, the second time domain length belonging to the first time domain length;

According to the second DCI, it is determined that the terminal device does not monitor the PDCCH within the third time domain length, and the start position of the third time domain length is the end position of the second time domain length or is located in the second time domain length. After the time domain length, and the end position of the third time domain length is the end position of the first time domain length.

Embodiment 2, the method as described in Embodiment 1, the second DCI includes a first field, and the 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 instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

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 not to monitor the PDCCH within the third time domain length according to the second DCI includes:

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

Embodiment 3: In the method described in 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.

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

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 not to monitor the PDCCH within the third time domain length according to the second DCI includes:

It is determined that the first timer is running when the second DCI is received, the first timer is not restarted, and it is determined that the PDCCH is not monitored within the third time domain length, wherein the first timer and the The third search space is related.

Embodiment 5, the method as described in embodiment 4, described method also comprises:

The first timer is not running when the first DCI is received, and the first timer is started or restarted.

Embodiment 6. According to the method described in Embodiment 1, determining not to monitor PDCCH within the third time domain length according to the second DCI includes:

When the second DCI indicates a PDCCH monitoring mode, determine that the PDCCH monitoring mode indicated by the second DCI does not take effect;

Determine not to monitor the PDCCH within the third time domain length.

Embodiment 7, the method as described in embodiment 1, the format of the second DCI is format 1_0 or format 0_0.

Embodiment 8, the method according to Embodiment 1, 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;

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

According to the second field of the second DCI being the first value, determine not to monitor the PDCCH within the third time domain length.

Embodiment 9, the method according to embodiment 8, the second value of the second field indicates that the terminal device does not monitor the PDCCH within the preset time domain length.

Embodiment 10, the method as described in Embodiment 1, the second DCI indicates to monitor the PDCCH according to the 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 the group of spaces includes at least one search space;

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

determining 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 the PDCCH within the third time domain length.

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

Embodiment 12, the method as described in Embodiment 11, the second time domain length further 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 Time; the second HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 13, the method according to 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 The HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 14. The method according to Embodiment 11, wherein the first HARQ process is a downlink HARQ process.

Embodiment 15. The method according to Embodiment 13, wherein the third HARQ process is a downlink HARQ process.

Embodiment 16, the method as described in embodiment 11, described method also comprises:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

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.

Embodiment 17, the method as described in embodiment 13, described method also comprises:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

Determine 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.

Embodiment 18: The method according to any one of embodiments 11-13, the method further includes: receiving a third DCI from the network device within the second time domain length, the third DCI It is used to indicate that the transmission of uplink data is successful.

Embodiment 19, a communication method, wherein the method includes:

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

After sending the first DCI, send a second DCI to the terminal device within a second time domain length, where the second time domain length belongs to the first time domain length; the second DCI is used for the The terminal device determines not to monitor the PDCCH within the 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 The end position of the third time domain length is the end position of the first time domain length.

Embodiment 20, the method according to Embodiment 19, the second DCI includes a first field, and the first value of the first field indicates not to switch the search space group to monitor the PDCCH;

The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

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.

Embodiment 21, the method according to 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.

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:

The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, the third search space group not including a search space;

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

Wherein, the first timer is running when the second DCI is sent, the first timer is not restarted, and the first timer is related to the third search space.

Embodiment 23, the method according to embodiment 19, the format of the second DCI is format 1_0 or format 0_0.

Embodiment 24: The method according to 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 a new operation.

Embodiment 25, the method according to 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.

Embodiment 26, the method according to Embodiment 19, the second DCI indicates to monitor the PDCCH according to the 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 set of search spaces includes at least one search space.

Embodiment 27, the method according to any one of embodiments 19-26, the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the first hybrid automatic repeat request The running time of the retransmission timer corresponding to the HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

Embodiment 28, the method as described in Embodiment 27, the second time domain length further 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 Time; the second HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 29, the method according to any one of embodiments 19-26, 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 The HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 30: The method according to Embodiment 27, wherein the first HARQ process is a downlink HARQ process.

Embodiment 31. The method according to Embodiment 29, wherein the third HARQ process is a downlink HARQ process.

Embodiment 32. The method of embodiment 27 or 29, further comprising:

Send configuration information 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

Embodiment 33. The method of any one of claims 27-29, further comprising:

Sending a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that the uplink data transmission is successful.

Embodiment 34. A communication method, including:

Receive first downlink control information DCI from the network device, the first DCI instructing the terminal device not to monitor the physical downlink control channel PDCCH within the first time domain length;

monitoring 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; the first HARQ process is one of multiple HARQ processes of the terminal device;

Alternatively, the second time domain length is related to a third HARQ process, where the third HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 35, the method according to Embodiment 34, 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.

Embodiment 36, the method according to Embodiment 34, the length of the first sub-time domain is related to the first HARQ process, including:

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

Embodiment 37. The method according to claim 34 or 36, wherein the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second The HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 38, the method as described in embodiment 37, the second sub-time domain length is related to the second HARQ process, including:

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

Embodiment 39: The method according to any one of embodiments 34-38, wherein the first HARQ process and/or the third HARQ process is a downlink HARQ process.

Embodiment 40. The method according to any one of embodiments 34-38, further comprising:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

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

Determine 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.

Embodiment 41. The method according to any one of embodiments 34-38, further comprising:

Receive a third DCI from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

Embodiment 42. A communication method, including:

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

Sending 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; the first HARQ process is one of multiple HARQ processes of the terminal device;

Alternatively, the second time domain length is related to a third HARQ process, where the third HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 43. The method according to Embodiment 42, 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.

Embodiment 44, the method according to Embodiment 42, the second sub-time domain length is related to the first HARQ process, including:

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

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

Embodiment 46, the method as described in Embodiment 45, the second sub-time domain length is related to the second HARQ process, including:

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

Embodiment 47. The method according to any one of embodiments 42-46, wherein the first HARQ process and/or the third HARQ process is a downlink HARQ process.

Embodiment 48. The method according to any one of embodiments 42-46, further comprising:

Send configuration information 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

Embodiment 49. The method according to any one of embodiments 42-46, further comprising:

Sending a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that the uplink data transmission is successful.

Embodiment 50, a communication device, including:

A transceiver unit, configured to receive a first DCI from a network device, the first DCI instructing the terminal device not to monitor the PDCCH within the first time domain length; and, after receiving the first DCI, in the second time domain receiving a second DCI from a network device within a length, where the second time domain length belongs to the first time domain length;

a processing unit, configured to determine, according to the second DCI, that the terminal device does not monitor the PDCCH within a third time domain length, where the starting position of the third time domain length is the end position of the second time domain length or It 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.

Embodiment 51, the apparatus according to Embodiment 50, the second DCI includes a first field, and the first value of the first field indicates that the terminal device does not switch search space groups to monitor PDCCH;

The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

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;

When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, it is specifically used to:

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

Embodiment 52: In the apparatus according to 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.

Embodiment 53. In the apparatus according to Embodiment 50, the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

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;

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

It is determined that the first timer is running when the transceiver unit receives the second DCI, the first timer is not restarted, and it is determined that the PDCCH is not monitored within the third time domain length, wherein the first timing is associated with the third search space.

Embodiment 54. The device according to Embodiment 53, the processing unit is further used for:

The first timer is not running when the transceiver unit receives the first DCI, and starts or restarts the first timer.

Embodiment 55: The device 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, it is specifically configured to:

When the second DCI indicates a PDCCH monitoring mode, determine that the PDCCH monitoring mode indicated by the second DCI does not take effect;

Determine not to monitor the PDCCH within the third time domain length.

Embodiment 56, the device according to Embodiment 50, the format of the second DCI is format 1_0 or format 0_0.

Embodiment 57, the apparatus according to Embodiment 50, 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 determines not to monitor the PDCCH within the third time domain length according to the second DCI, it is specifically configured to:

According to the second field of the second DCI being the first value, determine not to monitor the PDCCH within the third time domain length.

Embodiment 58: In the apparatus according to 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.

Embodiment 59: The device according to Embodiment 50, the second DCI indicates to monitor the PDCCH according to the 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 the group of spaces includes at least one search space;

When the processing unit determines not to monitor the PDCCH within the third time domain length according to the second DCI, it is specifically used to:

determining 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 the PDCCH within the third time domain length.

Embodiment 60: The device according to any one of Embodiments 50-59, wherein the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the first hybrid automatic repeat request The running time of the retransmission timer corresponding to the HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

Embodiment 61: In the device according to Embodiment 60, the second time domain length further 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 Time; the second HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 62: The device according to any one of Embodiments 50-59, wherein 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 The HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 63. The device according to Embodiment 60, wherein the first HARQ process is a downlink HARQ process.

Embodiment 64. The device according to Embodiment 62, wherein the third HARQ process is a downlink HARQ process.

Embodiment 65. The device according to Embodiment 60, the transceiver unit is also used for:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

The processing unit is also used for:

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.

Embodiment 66. The device according to Embodiment 62, the transceiver unit is also used for:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

The processing unit is also used for:

Determine 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.

Embodiment 67: The device according to any one of Embodiments 60-62, wherein the transceiver unit is further configured to: receive a third DCI from the network device within the second time domain length, the first The triple DCI is used to indicate that the transmission of uplink data is successful.

Embodiment 68, a communication device, including:

A transceiver unit, configured to send first downlink control information DCI to a terminal device, the first DCI instructing the terminal device not to monitor a physical downlink control channel PDCCH within a first time domain length; and, when sending the first After the DCI, send a second DCI to the terminal device within a second 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 the The PDCCH is not monitored within the time domain length, the starting position of the third time domain length is the end position of the second time domain length or after the second time domain length, and the third time domain length The end position is the end position of the first time domain length;

A processing unit, configured to control the transceiver unit to send and receive information.

Embodiment 69, the device according to Embodiment 68, the second DCI includes a first field, and the first value of the first field indicates not to switch the search space group to monitor the PDCCH;

The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

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.

Embodiment 70: In the apparatus according to 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.

Embodiment 71. The apparatus according to Embodiment 68, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including:

The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, the third search space group not including a search space;

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

Wherein, the first timer is running when the second DCI is sent, the first timer is not restarted, and the first timer is related to the third search space.

Embodiment 72, the device according to Embodiment 68, the format of the second DCI is format 1_0 or format 0_0.

Embodiment 73: The apparatus according to Embodiment 68, 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.

Embodiment 74, the apparatus according to 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.

Embodiment 75: The apparatus according to Embodiment 68, the second DCI indicates to monitor the PDCCH according to the 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 set of search spaces includes at least one search space.

Embodiment 76: The device according to any one of Embodiments 68-75, wherein the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the first hybrid automatic repeat request The running time of the retransmission timer corresponding to the HARQ process; the first HARQ process is one of the multiple HARQ processes of the terminal device.

Embodiment 77: In the device according to Embodiment 76, the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is run by the retransmission timer corresponding to the second HARQ process Time; the second HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 78: The device according to any one of Embodiments 68-75, wherein 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 The HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 79: In the device according to Embodiment 76, the first HARQ process is a downlink HARQ process.

Embodiment 80: The device according to Embodiment 78, wherein the third HARQ process is a downlink HARQ process.

Embodiment 81. The device according to Embodiment 76 or 78, the transceiver unit is further used for:

Send configuration information 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

Embodiment 82. The device according to any one of claims 76-78, the transceiver unit is further used for:

Sending a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that the uplink data transmission is successful.

Embodiment 83, a communication device, including:

A transceiver unit, configured to receive first downlink control information DCI from the network device, the first DCI instructing the terminal device not to monitor the physical downlink control channel PDCCH within the first time domain length;

a processing unit, configured 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; the first HARQ process is one of multiple HARQ processes of the terminal device;

Alternatively, the second time domain length is related to a third HARQ process, where the third HARQ process is the HARQ process corresponding to the first DCI.

Embodiment 84. The device according to Embodiment 83, 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.

Embodiment 85. The device according to Embodiment 83, the first sub-time domain length is related to the first HARQ process, including:

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

Embodiment 86. The apparatus according to claim 83 or 85, the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second The HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 87. The device according to Embodiment 86, the second sub-time domain length is related to the second HARQ process, including:

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

Embodiment 88: The device according to any one of Embodiments 83-87, wherein the first HARQ process and/or the third HARQ process is a downlink HARQ process.

Embodiment 89. The device according to any one of embodiments 83-87, the transceiver unit is further used for:

Receive 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process;

The processing unit is also used for:

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

Determine 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.

Embodiment 90, the device according to any one of embodiments 83-87, the transceiver unit is further used for:

Receive a third DCI from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful.

Embodiment 91. A communication device, including:

A transceiver unit, configured to send first downlink control information DCI to the terminal device, the first DCI instructing the terminal device not to monitor the physical downlink control channel PDCCH within the first time domain length; and, during the second time domain length sending a PDCCH within; 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; 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, where the third HARQ process is the HARQ process corresponding to the first DCI;

A processing unit, configured to control the transceiver unit to send and receive information and the like.

Embodiment 92. The device according to Embodiment 91, 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.

Embodiment 93. The device according to Embodiment 91, the second sub-time domain length is related to the first HARQ process, including:

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

Embodiment 94: In the device according to Embodiment 91 or 93, the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is related to a second HARQ process; the second The HARQ process is one of multiple HARQ processes of the terminal device.

Embodiment 95, the device according to Embodiment 94, the second sub-time domain length is related to the second HARQ process, including:

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

Embodiment 96: In the device according to any one of Embodiments 91-95, the first HARQ process and/or the third HARQ process is a downlink HARQ process.

Embodiment 97. The device according to any one of embodiments 91-95, the transceiver unit is further used for:

Send configuration information 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 indicate that the second time domain length is associated with an uplink HARQ process and a downlink HARQ process.

Embodiment 98: The device according to any one of embodiments 91-95, the transceiver unit is further configured to:

Sending a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that the uplink data transmission is successful.

Embodiment 99. A communications device, comprising a memory, a processor, and a transceiver, wherein:

said memory for storing computer instructions;

The transceiver is used to receive and send information;

The processor, coupled to the memory, is configured to invoke computer instructions in the memory to enable the communication device to execute the method described in any one of embodiments 1-18.

Embodiment 100. A communication device, comprising a memory, a processor, and a transceiver, wherein:

said memory for storing computer instructions;

The transceiver is used to receive and send information;

The processor, coupled with the memory, is configured to call computer instructions in the memory to make the communication device execute the method according to any one of embodiments 19-33.

Embodiment 101. A communication device, comprising a memory, a processor, and a transceiver, wherein:

said memory for storing computer instructions;

The transceiver is used to receive and send information;

The processor, coupled to the memory, is configured to invoke computer instructions in the memory to enable the communication device to execute the method described in any one of embodiments 34-41.

Embodiment 102. A communication device, comprising a memory, a processor, and a transceiver, wherein:

said memory for storing computer instructions;

The transceiver is used to receive and send information;

The processor, coupled with the memory, is configured to invoke computer instructions in the memory to enable the communication device to execute the method described in any one of embodiments 42-49.

Embodiment 103, a communication method, wherein the method includes:

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

Monitor the PDCCH according to the PDCCH monitoring manner indicated by the fourth DCI.

Embodiment 104, the method according to Embodiment 103, the fourth DCI includes a third field, and 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 according to the first The six search space groups monitor the PDCCH; the second value of the third field indicates that the terminal device does not switch the search space group to monitor the PDCCH.

Embodiment 105, the method according to Embodiment 103, 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 a search space;

When the third timer is not running when the fourth DCI is received, start or restart the third timer; the third timer is related to the seventh search space; when the fourth DCI is received, the The third timer is running, and the third timer is not restarted.

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

Embodiment 107. A communication method, wherein the method includes:

determining a fourth DCI;

Sending the fourth DCI to the terminal device, where the fourth DCI is used to indicate a PDCCH monitoring manner.

Embodiment 108, the method according to Embodiment 107, the fourth DCI includes a third field, and 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 according to the first The six search space groups monitor the PDCCH; the second value of the third field indicates that the terminal device does not switch the search space group to monitor the PDCCH.

Embodiment 109: the method according to 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.

Embodiment 110, the method according to embodiment 107, the fourth DCI includes a fourth field, and the value of the fourth field is one indicating that the terminal device does not monitor the PDCCH within a preset time domain length; the fourth The value two of the field indicates that the terminal equipment does not perform a new operation or indicates that the terminal equipment does not perform a PDCCH skip operation.

The above is only a specific implementation of this application, but the protection scope of this application is not limited thereto, and changes or replacements within the technical scope disclosed in this application should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Based on the above embodiments, the embodiments of the present application provide a communication system, and the communication system may include the terminal device and the network device involved in the above embodiments.

The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.

The embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.

The embodiment of the present application further provides a chip, including a processor, the processor is coupled to a memory, and is configured to call a program in the memory so that the chip implements the communication method provided by the above method embodiment.

The embodiment of the present application also provides a chip, the chip is coupled with the memory, and the chip is used to implement the communication method provided in the above method embodiment.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Apparently, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (33)

A communication method, characterized in that, comprising: Receive first downlink control information DCI from the network device, the first DCI instructing the terminal device not to monitor the physical downlink control channel PDCCH within the first time domain length; After receiving the first DCI, receive a second DCI from the network device within a second time domain length, 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 the PDCCH within the third time domain length, and the start position of the third time domain length is the end position of the second time domain length or is located in the second time domain length. After the time domain length, and the end position of the third time domain length is the end position of the first time domain length. The method according to claim 1, wherein the second DCI includes a first field, and the first value of the first field indicates that the terminal device does not switch search space groups to monitor PDCCH; The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including: 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 not to monitor the PDCCH within the third time domain length according to the second DCI includes: According to the first value of the first field in the second DCI, it is determined not to monitor the PDCCH within the third time domain length. The method according to claim 2, wherein 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. The method according to claim 1, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, comprising: 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 not to monitor the PDCCH within the third time domain length according to the second DCI includes: It is determined that the first timer is running when the second DCI is received, the first timer is not restarted, and it is determined that the PDCCH is not monitored within the third time domain length, wherein the first timer and the The third search space is related. The method of claim 4, further comprising: The first timer is not running when the first DCI is received, and the first timer is started or restarted. The method according to claim 1, wherein determining not to monitor the PDCCH within the third time domain length according to the second DCI comprises: When the second DCI indicates a PDCCH monitoring mode, determine that the PDCCH monitoring mode indicated by the second DCI does not take effect; Determine not to monitor the PDCCH within the third time domain length. The method according to claim 1, wherein 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; Determining not to monitor the PDCCH within the third time domain length according to the second DCI includes: According to the second field of the second DCI being the first value, determine not to monitor the PDCCH within the third time domain length. The method according to claim 7, wherein the second value of the second field indicates that the terminal device does not monitor the PDCCH within a preset time domain length. The method according to claim 1, wherein the second DCI indicates to monitor 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 group of spaces includes at least one search space; Determining not to monitor the PDCCH within the third time domain length according to the second DCI includes: determining 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 the PDCCH within the third time domain length. The method according to any one of claims 1-9, wherein the second time domain length includes a first sub-time domain length, and the first sub-time domain length is the first Hybrid Automatic Repeat Request (HARQ) The running time of the retransmission timer corresponding to the process; the first HARQ process is one of the multiple HARQ processes of the terminal device. The method according to claim 10, wherein the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is the number of times the retransmission timer corresponding to the second HARQ process runs Time; the second HARQ process is one of multiple HARQ processes of the terminal device. The method according to any one of claims 1-9, wherein 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 The process is the HARQ process corresponding to the first DCI. The method according to claim 10, wherein the first HARQ process is a downlink HARQ process. The method according to claim 12, wherein the third HARQ process is a downlink HARQ process. The method according to any one of claims 10-12, wherein the method further comprises: Receive a third DCI from the network device within the second time domain length, where the third DCI is used to indicate that uplink data transmission is successful. A communication method, characterized in that, comprising: Sending first downlink control information DCI to the terminal device, where the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within the first time domain length; After sending the first DCI, send a second DCI to the terminal device within a second time domain length, where the second time domain length belongs to the first time domain length; the second DCI is used for the The terminal device determines not to monitor the PDCCH within the 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 The end position of the third time domain length is the end position of the first time domain length. The method according to claim 16, wherein the second DCI includes a first field, and the first value of the first field indicates not to switch the search space group to monitor the PDCCH; The first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, including: 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. The method according to claim 17, wherein 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. The method according to claim 16, wherein the first DCI instructs the terminal device not to monitor the PDCCH within the first time domain length, comprising: The first DCI instructs the terminal device to monitor the PDCCH according to a third search space group, the third search space group not including a search space; The second DCI instructs the terminal device to monitor the PDCCH according to the third search space group; Wherein, the first timer is running when the second DCI is sent, the first timer is not restarted, and the first timer is related to the third search space. The method according to claim 16, wherein 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. The method according to 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. The method according to 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 set of search spaces includes at least one search space. The method according to any one of claims 16-22, wherein the second time domain length includes a first sub-time domain length, and the first sub-time domain length is a first Hybrid Automatic Repeat Request (HARQ) The running time of the retransmission timer corresponding to the process; the first HARQ process is one of the multiple HARQ processes of the terminal device. The method according to claim 23, wherein the second time domain length further includes a second sub-time domain length, and the second sub-time domain length is the number of times the retransmission timer corresponding to the second HARQ process runs Time; the second HARQ process is one of multiple HARQ processes of the terminal device. The method according to any one of claims 16-22, wherein 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 The process is the HARQ process corresponding to the first DCI. The method according to claim 23, wherein the first HARQ process is a downlink HARQ process. The method according to claim 25, wherein the third HARQ process is a downlink HARQ process. The method according to any one of claims 23-25, further comprising: Sending a third DCI to the terminal device within the second time domain length, where the third DCI is used to indicate that the uplink data transmission is successful. A communication device, characterized in that it includes a memory, a processor and a transceiver, wherein: the memory is used to store computer instructions; The transceiver is used to receive and transmit information; The processor is coupled with a memory, and is used for invoking computer instructions in the memory to make the communication device execute the method according to any one of claims 1-15. A communication device, characterized in that it includes a memory, a processor and a transceiver, wherein: the memory is used to store computer instructions; The transceiver is used to receive and send information; The processor, coupled with the memory, is used to call computer instructions in the memory to make the communication device execute the method according to any one of claims 16-28. A computer-readable storage medium, characterized in that, computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to make the computer execute the above claims when called by the computer The method described in any one of 1-15, or perform the method described in any one of the above-mentioned claims 16-28. A computer program product comprising instructions, characterized in that, when the computer program product is run on a computer, the computer is made to perform the method according to any one of claims 1-15, or to perform the method according to any one of claims 1-15 The method described in any one of 16-28. A chip, characterized in that the chip is coupled with a memory for reading and executing program instructions stored in the memory, so as to implement the method according to any one of claims 1-15, or to implement the The method of any one of claims 16-28.

Images