CN116761236A - A communication method and device - Google Patents

Abstract

A communication method and device are used to reduce the power consumption of terminal equipment. The network device determines the first DCI and sends the first DCI to the terminal device, and then the terminal device determines not to monitor the PDCCH within the first duration according to the first DCI; wherein the first DCI is used to schedule filling data packets, so The first DCI instructs the terminal equipment not to monitor the physical downlink control channel PDCCH within a first period of time. In this way, when no traffic arrives at the terminal device, the network device can instruct the terminal device not to monitor the PDCCH within the first duration by scheduling the DCI of the filled data packet, thereby reducing the power consumption of the terminal device.

Description

A communication method and device

This application claims the priority of a Chinese patent application filed with the China Patent Office on March 3, 2022, with application number 202210204563.7 and invention name “A method for indicating skipping of PDCCH and search space switching”, the entire contents of which are incorporated by reference in this application.

Technical Field

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

Background Art

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

Summary of the invention

The present application provides a communication method and apparatus for reducing the power consumption of a terminal device.

In a first aspect, the present application provides a communication method, which may include: after a terminal device receives first downlink control information (DCI) from a network device, it determines not to monitor PDCCH within a first time period based on the first DCI; wherein the first DCI is used to schedule fill data packets, and the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within the first time period.

Through the above method, when no business arrives at the terminal device, the network device can instruct the terminal device not to monitor the PDCCH within the first time period by scheduling the DCI of the filling data packet, thereby reducing the power consumption of the terminal device.

In one possible design, the first DCI is used to schedule a physical downlink shared channel (PDSCH). Thus, the first DCI can instruct the terminal device not to monitor the physical downlink control channel PDCCH within a first time period by scheduling a downlink padding data packet.

In one possible design, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a cell-radio network temporary identity (C-RNTI); or, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI); or, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a configured scheduling-radio network temporary identity (CS-RNTI). In this way, the first DCI can be flexibly implemented through downlink DCI.

In one possible design, the terminal device receives a PDSCH from the network device, wherein the PDSCH includes a media access control sub protocol data unit (MACsub PDU) and a corresponding logical channel identify (LCID), so as to enable the network device to schedule a downlink filling data packet.

In one possible design, the first DCI is used to schedule a physical uplink shared channel (PUSCH). Thus, the first DCI can instruct the terminal device not to monitor the physical downlink control channel PDCCH within a first time period by scheduling an uplink padding data packet.

In one possible design, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a cell radio network temporary identifier C-RNTI; or, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a modulation and coding mode cell-specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a configuration scheduling radio network temporary identifier CS-RNTI. In this way, the first DCI can be flexibly implemented through uplink DCI.

In a possible design, the terminal device sends a physical uplink shared channel PUSCH to the network device, wherein the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63, so as to enable the network device to schedule uplink filling data packets.

In one possible design, the terminal device sends a PUSCH to the network device, wherein the PUSCH includes the padding data packet; and the terminal device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not restart or stop the DRX-inactivitytimer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, when the terminal device is configured with an uplink skip function, the terminal device does not send a physical uplink shared channel PUSCH to the network device, so that the terminal device does not need to send any data packets to the network device, thereby saving power consumption of the terminal device.

In one possible design, when the terminal device does not send a PUSCH to the network device, the terminal device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not restart or stop the DRX-inactivitytimer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, the terminal device receives a PDSCH from the network device, wherein the PDSCH includes the padding data packet; further, the terminal device does not start a discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, the terminal device does not restart or stop the DRX-inactivity timer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, the value of the new data indicator (NDI) field in the first DCI is the same as the value of the NDI field in the second DCI, and the second DCI is the previous DCI with the same value of the hybrid automatic repeat request (HARQ) process number (HPN) field as the first DCI. In this way, when the first DCI is a retransmission DCI, the terminal device does not start, restart or stop the DRX-inactivity timer to avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, before the terminal device receives the first DCI from the network device, it receives the second DCI from the network device and sends a correct response ACK message to the network device. In this way, the subsequent terminal device can identify the padding data packet and thus does not start, restart or stop the DRX-inactivity timer.

In one possible design, the value of the NDI field in the first DCI is different from the value of the NDI field in the third DCI, and the third DCI is the previous DCI with the same value of the HARQ process number HPN field as the first DCI. In this way, when the first DCI is a new transmission DCI, the terminal device may not start, restart or stop the DRX-inactivity timer to avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In a second aspect, the present application provides a communication method, which may include: a network device determines a first DCI and sends the first DCI to the terminal device, wherein the first DCI is used to schedule a fill data packet, and the first DCI indicates that the terminal device does not monitor a physical downlink control channel PDCCH within a first time period.

Through the above method, when no business arrives at the terminal device, the network device can instruct the terminal device not to monitor the PDCCH within the first time period by scheduling the DCI of the filling data packet, thereby reducing the power consumption of the terminal device.

In one possible design, before the network device sends the first DCI to the terminal device, the network device determines that no service has arrived at the terminal device within a preset time period; or the network device determines that there is no cache data corresponding to the terminal device. In this way, the network device can determine that no service has arrived at the terminal device, and then send the first DCI to the terminal device.

In one possible design, the preset duration is a period of time before the network device sends the first DCI, or the preset duration is a period of time after the network device sends the first DCI, or the preset duration is the moment when the network device sends the first DCI.

In one possible design, the first DCI is used for PDSCH. In this way, the first DCI can instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first time period by scheduling a downlink padding data packet.

In one possible design, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a cell radio network temporary identifier C-RNTI; or, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a modulation and coding scheme cell-specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is a DCI format 1_1 or DCI format 1_2 scrambled by a configuration scheduling radio network temporary identifier CS-RNTI. In this way, the first DCI can be flexibly implemented through downlink DCI.

In a possible design, the network device sends a physical downlink shared channel PDSCH to the terminal device, wherein the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63, so as to enable the network device to schedule downlink filling data packets.

In one possible design, the first DCI is used to schedule PUSCH. In this way, the first DCI can instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first time period by scheduling an uplink padding data packet.

In one possible design, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a cell radio network temporary identifier C-RNTI; or, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a modulation and coding mode cell-specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is a DCI format 0_1 or DCI format 0_2 scrambled by a configuration scheduling radio network temporary identifier CS-RNTI. In this way, the first DCI can be flexibly implemented through uplink DCI.

In one possible design, the network device receives a physical uplink shared channel PUSCH from the terminal device, wherein the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. This enables the network device to schedule uplink filling data packets.

In one possible design, when the terminal device is configured with an uplink skip function, the network device does not receive a PUSCH from the terminal device, so that the terminal device does not need to send any data packets to the network device, thereby saving power consumption of the terminal device.

In a possible design, the network device receives a physical uplink shared channel PUSCH from the terminal device, wherein the PUSCH includes the padding data packet; further, the network device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, the network device does not receive the physical uplink shared channel PUSCH sent by the terminal device at the position indicated by the first DCI; further, the network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, the network device sends a physical downlink shared channel PDSCH to the terminal device, wherein the PDSCH includes the padding data packet; further, the network device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. This can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI, and the second DCI is the previous DCI with the same value as the hybrid automatic repeat request HARQ process number HPN field of the first DCI. In this way, when the first DCI is a retransmission DCI, the network device may not start, restart or stop the DRX-inactivity timer to avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In one possible design, before the network device sends the first DCI to the terminal device, the method further includes: after the network device sends the second DCI to the terminal device, receiving correct response ACK information from the terminal device. This allows the terminal device to subsequently identify the padding data packet and thus not start, restart or stop the DRX-inactivity timer.

In one possible design, the value of the new data indication NDI field in the first DCI is different from the value of the NDI field in the third DCI, and the third DCI is the previous DCI with the same value of the hybrid automatic repeat request HARQ process number HPN field as the first DCI. In this way, when the first DCI is a new transmission DCI, the terminal device may not start, restart or stop the DRX-inactivity timer, which can avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

In a third aspect, the present application provides a communication method, which may include: after a terminal device receives a downlink filling data packet from a network device, determining a first operation of the terminal device according to the downlink filling data packet. In this way, after the terminal device receives the downlink filling data packet, the first operation of the terminal device can be triggered to save power consumption of the terminal device.

In one possible design, the terminal device receives the downlink filling data packet from the network device, and the method may be: the terminal device receives a physical downlink shared channel PDSCH from the network device, the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. In this way, the terminal device can receive an accurate downlink filling data packet.

In one possible design, the first operation is that the terminal device does not monitor the physical downlink control channel PDCCH within the second time period. In this way, after the terminal device receives the downlink filling data packet, it can achieve a period of time without monitoring the PDCCH, thereby saving power consumption of the terminal device.

In one possible design, the terminal device receives downlink control information DCI from the network device, the DCI is used to schedule the downlink filling data packet, and the DCI instructs the terminal device not to monitor the PDCCH within the second time period after receiving the downlink filling data packet. In this way, the network device can trigger the terminal device not to monitor the PDCCH by scheduling the downlink filling data packet.

In one possible design, the DCI is DCI format 1_0.

In one possible design, the first operation is that the terminal device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the first operation is that the terminal device does not restart or stop the DRX-inactivitytimer. In this way, after the terminal device receives a downlink padding data packet, by not starting the DRX-inactivitytimer, or not restarting or stopping the running DRX-inactivitytimer, it is possible to avoid extending the activation time of the terminal device, thereby reducing the power consumption of the terminal device.

In a fourth aspect, the present application provides a communication method, which may include: a network device sends a downlink filling data packet to a terminal device, and determines that the terminal device does not monitor a physical downlink control channel PDCCH within a second time period. In this way, by sending a downlink filling data packet to the terminal device, the terminal device is triggered to not monitor the PDCCH for a period of time, thereby saving power consumption of the terminal device.

In a possible design, the network device sends the downlink filling data packet to the terminal device, and the method may be: the network device sends a physical downlink shared channel PDSCH to the terminal device, the PDSCH includes a media access control sub-protocol data unit MAC sub-PDU, and the logical channel identifier LCID corresponding to the MAC sub-PDU has a value of 63. In this way, the network device can send an accurate downlink filling data packet.

In one possible design, the network device sends downlink control information DCI to the terminal device, the DCI is used to schedule the downlink filling data packet, and the DCI instructs the terminal device not to monitor the PDCCH within the second time period after receiving the downlink filling data packet. In this way, the network device can trigger the terminal device not to monitor the PDCCH by scheduling the downlink filling data packet.

In one possible design, the DCI is DCI format 1_0.

In a fifth aspect, the present application provides a communication method, which may include: a network device sends a downlink filling data packet to a terminal device, and the network device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. In this way, by sending a downlink filling data packet to the terminal device, the DRX-inactivitytimer can be triggered to not start, or the running DRX-inactivitytimer can not be restarted or stopped, which can avoid extending the activation time of the terminal device, thereby reducing the power consumption of the terminal device.

In a possible design, the network device sends the downlink filling data packet to the terminal device, and the method may be: the network device sends a physical downlink shared channel PDSCH to the terminal device, the PDSCH includes a media access control sub-protocol data unit MAC sub-PDU, and the logical channel identifier LCID corresponding to the MAC sub-PDU has a value of 63. In this way, the network device can send an accurate downlink filling data packet.

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

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

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

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

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

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

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

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

In the tenth aspect, an embodiment of the present application provides a computer program product, including computer program codes or instructions. When the computer program codes or instructions are run on a computer, the method described in the above-mentioned first aspect or any possible design of the first aspect, or the above-mentioned second aspect or any possible design of the second aspect is executed.

In the eleventh aspect, the present application also provides a chip, including a processor, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the chip implements the method described in the above-mentioned first aspect or any possible design of the first aspect, or the above-mentioned second aspect or any possible design of the second aspect, or the above-mentioned third aspect or any possible design of the third aspect, or the above-mentioned fourth aspect or any possible design of the fourth aspect, or the above-mentioned fifth aspect or any possible design of the fifth aspect.

For each aspect from the third to the eighth aspect and the technical effects that may be achieved by each aspect, please refer to the technical effects that can be achieved by the first aspect or the various possible schemes in the first aspect, or the second aspect or the various possible schemes in the second aspect, or the third aspect or the various possible schemes in the third aspect, or the fourth aspect or the various possible schemes in the fourth aspect, or the fifth aspect or the various possible schemes in the fifth aspect, and no repetition will be given here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the architecture of a communication system provided by the present application;

FIG2 is a schematic diagram of skipping PDCCH monitoring provided by the present application;

FIG3 is a schematic diagram of a network device using scheduling DCI to indicate PDCCH skipping provided by the present application;

FIG4 is a flow chart of a communication method provided by the present application;

FIG5 is a schematic diagram of a network device providing a method of indicating PDCCH skipping by scheduling a first DCI filling data packet provided by the present application;

FIG6 is a schematic diagram of a MAC PDU provided by the present application including one or more MAC sub PDUs;

FIG7 is a schematic diagram of a CDRX cycle provided by the present application;

FIG8 is a schematic diagram of a network device provided by the present application instructing a terminal device configured with CDRX not to monitor PDCCH in a period of time;

FIG9 is a flow chart of another communication method provided by the present application;

FIG10 is a flow chart of another communication method provided by the present application;

FIG11 is a schematic diagram of the structure of a communication device provided by the present application;

FIG12 is a structural diagram of a communication device provided in the present application.

DETAILED DESCRIPTION

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

The embodiment of the present application provides a communication method and device for reducing the power consumption of terminal equipment. The method and device described in the present application are based on the same technical concept. Since the method and device solve the problem in a similar way, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

In the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance or order.

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

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

FIG1 shows the architecture of a communication system involved in an embodiment of the present application, wherein the architecture of the communication system includes a network device and a terminal device, wherein:

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

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

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

It should be noted that the communication system shown in Figure 1 may be but is 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 of the embodiment of the present application is also applicable to various future communication systems, 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 a network device schedules a terminal device to receive downlink data, or when a network device schedules a terminal device to send uplink data, it will first send downlink control information (DCI). The DCI contains a data scheduling information, which indicates the transmission parameters of the physical downlink shared channel (PDSCH) (which usually contains downlink data) or the physical uplink shared channel (PUSCH) (which usually contains uplink data). These transmission parameters include the time-frequency domain resource location of PDSCH/PUSCH. Specifically, the physical downlink control channel (PDCCH) carries the above DCI. For downlink data, the network device indicates the K0 value through the time domain resource allocation (TDRA) field in the DCI to determine the time slot interval between PDCCH and PDSCH; for uplink data, the network device indicates the K2 value through the TDRA field in the DCI to determine the time slot interval between PDCCH and PUSCH.

The network device sends PDSCH at the time-frequency domain resource position indicated in the DCI, and the terminal device receives it at the corresponding position; or, the terminal device sends PUSCH at the time-frequency domain resource position indicated in the DCI, and the network device receives it at the corresponding position.

When receiving its own DCI, the terminal device needs to blindly detect (blind detect, BD) the PDCCH sent to itself in the downlink control region, that is, the terminal device monitors (monitor) many PDCCH candidate positions (PDCCH candidates) to find out whether there is one sent to itself.

Based on the above description, the terminal device will frequently monitor the PDCCH. However, if there is no business happening in the terminal device for a period of time, that is, there is no downlink data or uplink data to be transmitted, the network device will not send PDCCH to schedule PDSCH or PUSCH. At this time, the terminal device cannot receive the PDCCH sent to itself even if it monitors PDCCH. If the terminal device continues to monitor PDCCH during these times, it will cause power consumption of the terminal device.

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

However, the network device can only trigger the PDCCH skipping of the terminal device through scheduling DCI. That is, the DCI that can indicate PDCCH skipping must be the DCI that schedules data transmission. For example, the scheduling DCI contains a PDCCH monitoring adaptation indication field, which is 1 to 2 bits and can indicate PDCCH skipping. It should be noted that this field can indicate both PDCCH skipping and search space set groupswitching (SSSG switching). In this application, only PDCCH skipping is used as an example.

Among them, the network device can configure 1 to 3 skipping durations for the terminal device, and use 1 to 2 bits to indicate how long the skipping duration used each time is. For example, when the network device is configured with 1 skipping duration (length is T1), the scheduling DCI will contain 1 bit, and the value of '0' indicates that PDCCH skipping is not performed (that is, PDCCH is monitored normally), and the value of '1' indicates that PDCCH is not monitored within the time length of T1. For another example, when the network device is configured with 2 skipping durations (lengths are T1 and T2), the scheduling DCI will contain 2 bits, and the value of '00' indicates that PDCCH skipping is not performed (that is, PDCCH is monitored normally); the value of '01' indicates that PDCCH is not monitored within the time length of T1; the value of '10' indicates that PDCCH is not monitored within the time length of T2. For another example, when the network device is configured with 3 skipping durations (lengths of T1, T2, and T3), the scheduling DCI will contain 2 bits, with a value of ‘00’ indicating that PDCCH skipping is not performed (i.e., PDCCH is monitored normally); a value of ‘01’ indicating that PDCCH is not monitored within the time length of T1; a value of ‘10’ indicating that PDCCH is not monitored within the time length of T2; a value of ‘11’ indicating that PDCCH is not monitored within the time length of T3. It should be noted that the relationship between the above-mentioned bit values and the corresponding meanings is only an example, and there may be other indication methods. For example, when the network device is configured with 1 skipping duration (length of T1), the scheduling DCI will contain 1 bit, with a value of ‘1’ indicating that PDCCH skipping is not performed (i.e., PDCCH is monitored normally), and a value of ‘0’ indicating that PDCCH is not monitored within the time length of T1. This application does not limit this.

When the network device uses the scheduling DCI to indicate PDCCH skipping, it usually indicates PDCCH skipping in the last scheduling DCI of each terminal device service scheduling. For example, as shown in Figure 3, when the terminal device continues to have service transmission, the DCI carried in the PDCCH of the scheduling data (i.e., scheduling PDSCH) always indicates "no skipping PDCCH" (i.e., continuous monitoring of PDCCH) to quickly complete data transmission. In the PDCCH of the last transmission of a service, the network device can indicate that the PDCCH will not be monitored for a period of time (i.e., the skipping duration), wherein the network device can determine whether it is the last transmission by checking whether there is still data to be transmitted by the terminal device in the cache. However, as shown in the black part of Figure 3, after the skipping duration, if the terminal device's service has not arrived, the network device generally will not schedule the terminal device's data transmission, and will not be able to send the scheduling DCI, and thus will not be able to indicate PDCCH skipping. At this time, the terminal device can only continue to monitor the PDCCH, resulting in a waste of power consumption of the terminal device.

Based on this, the present application proposes a communication method, which can be implemented when no business arrives at the terminal device, and can also instruct the terminal device not to monitor the PDCCH for a period of time, thereby reducing the power consumption of the terminal device.

It should be noted that in the following embodiments, the communication method provided in the present application is described in detail using terminal devices and network devices as examples. It should be understood that the operations performed by the terminal device can also be implemented through a processor in the terminal device, or a chip or chip system, or a functional module, etc., and the operations performed by the network device can also be implemented through a processor in the network device, or a chip or chip system, or a functional module, etc., and the present application does not limit this.

Based on the above description, a communication method provided in an embodiment of the present application is applicable to the communication system shown in Figure 1. Referring to Figure 4, the specific process of the method may include:

Step 401: The network device determines a first DCI, where the first DCI is used to schedule a padding data packet (padding packet), and the first DCI instructs the terminal device not to monitor the PDCCH within a first time period.

Step 402: The network device sends a first DCI to the terminal device.

Step 403: The terminal device determines not to monitor the PDCCH within a first time period according to the first DCI.

The communication method of the present application, by scheduling the first DCI of the filling data packet to instruct the terminal device not to monitor the PDCCH within the first time period, can enable the terminal device to skip the monitoring of the PDCCH even when no service arrives, thereby reducing the power consumption of the terminal device. For example, as shown in Figure 5, when the terminal device continues to have service transmission, the DCI carried in the PDCCH of the scheduling data (i.e., scheduling PDSCH) always indicates "no skipping PDCCH" (i.e., continuous monitoring of PDCCH) to quickly complete data transmission. In the PDCCH of the last transmission of a service, the network device can indicate that the PDCCH will not be monitored for a period of time (i.e., the skipping duration). Furthermore, after the skipping duration, if the service of the terminal device has not arrived, the network device can indicate PDCCH skipping by scheduling the first DCI of the filling data packet, thereby reducing the power consumption of the terminal device.

It should be noted that the two durations of not monitoring PDCCH shown in FIG5 may be the same or different, which is not limited in this application. When the two time periods are different, in one possible manner, it indicates that the network device has configured at least two skip durations for the terminal device, and the durations of not monitoring PDCCH indicated by the network device twice are different. Alternatively, the two durations may also be predefined, which is not limited in this application.

In an optional implementation, before the network device determines through the first DCI to instruct the terminal device not to monitor the PDCCH within a first time period, the network device may determine that no service arrives at the terminal device within a preset time period, or the network device determines that there is no cached data corresponding to the terminal device.

The preset duration may be a period of time before the network device sends the first DCI, or the preset duration may be a period of time after the network device sends the first DCI, or the preset duration may be the moment when the network device sends the first DCI. When the preset duration is a period of time after the terminal device sends the first DCI, the preset duration may be less than the first duration, may be equal to the first duration, or may be greater than the first duration, and this application does not limit this.

No service arrival at the terminal device may refer to no service data transmission, no data arrival, no downlink data arrival, no need to send an RRC message or a media access control element (MAC CE) to the terminal device, etc.

For example, when the preset duration is a period of time before the network device sends the first DCI, the network device can determine whether there is data from the terminal device on the core network side during this period of time. When it is determined that there is no data from the terminal device on the core network side, the network device determines that no service has arrived at the terminal device within the preset time period.

For another example, when the preset duration is a period of time after the network device sends the first DCI, or is the moment when the network device sends the first DCI, the network device can predict through a prediction algorithm to determine that no service arrives at the terminal device within the preset duration. The prediction algorithm is not limited in this application.

When the network device determines that there is no cache data corresponding to the terminal device, it can be determined that the cache (buffer) corresponding to the terminal device is empty.

Exemplarily, the first DCI may include the following two cases:

Case a1: the first DCI may be used to schedule the PDSCH.

Case a2: the first DCI can be used to schedule PUSCH.

In the above situation a1, the first DCI can be DCI format 1_1 or DCI format 1_2 scrambled by cell-radio network temporary identity (C-RNTI); or, the first DCI can be DCI format 1_1 or DCI format 1_2 scrambled by modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI); or, the first DCI can be DCI format 1_1 or DCI format 1_2 scrambled by configured scheduling-radio network temporary identity (CS-RNTI).

In the above situation a1, the network device sends PDSCH to the terminal device (correspondingly, the terminal device receives PDSCH from the network device), and the PDSCH contains a media access control subprotocol data unit (MAC sub PDU), and the logical channel identifier (LCID) corresponding to the MAC sub-PDU is 63.

Usually, a PDSCH contains a media access control protocol data unit (MAC PDU). As shown in Figure 6, a MAC PDU may contain one or more MAC subPDUs. The subheader of each MAC sub PDU contains an LCID, which is used to indicate the function of the corresponding MAC sub PDU. For example, different LCID values may indicate different functions of the MAC sub PDU. As shown in Table 1 below, the meanings corresponding to different LCID values are shown. It can be seen from Table 1 that when the LCID value is 63, it can be indicated that the corresponding MAC sub-PDU is a padding packet, and a padding packet means that it does not contain meaningful data.

Therefore, in the above situation a1, when the LCID value corresponding to the MAC sub-PDU contained in the PDSCH sent by the network device to the terminal device is 63, it means that the network device sends a padding packet to the terminal device.

Table 1

After receiving the DCI, the terminal device needs to receive or send PDSCH according to the DCI. Normally, the power consumption of the terminal device for sending PUSCH is greater than that for receiving PDSCH. Therefore, from the perspective of energy saving of the terminal device, by using the first DCI of scheduling PDSCH (scheduling padding) in the above situation a1 to instruct the terminal device not to monitor PDCCH within the first time period, the power consumption of the terminal device can usually be lower than that when using the first DCI in situation a2.

In the above situation a2, the first DCI can be DCI format 0_1 or DCI format 0_2 scrambled by C-RNTI; or, the first DCI can be DCI format 0_1 or DCI format 0_2 scrambled by MCS-C-RNTI; or, the first DCI can be DCI format 0_1 or DCI format 0_2 scrambled by CS-RNTI.

In the above situation a2, when the terminal device is not configured with the uplink skip function, the terminal device sends PUSCH to the network device (correspondingly, the network device receives PUSCH from the terminal device), and the PUSCH contains MAC sub PDU, and the LCID value corresponding to the MAC subPDU is 63.

Similar to PDSCH, a PUSCH usually contains a MAC PDU, as shown in Figure 6. A MAC PDU can contain one or more MAC sub PDUs. The subheader of each MAC sub PDU contains an LCID, which is used to indicate the function of the corresponding MAC sub PDU. From Table 1, it can be seen that when the LCID value is 63, it can be said that the corresponding MAC sub-PDU is a padding packet, which means that it does not contain meaningful data.

Therefore, in the above situation a2, when the LCID value corresponding to the MAC sub-PDU contained in the PUSCH sent by the terminal device to the network device is 63, it means that the terminal device sends a padding packet to the network device.

In an optional implementation, when the terminal device is not configured with an uplink skip function, when a service temporarily arrives at the terminal device, the terminal device can send a PUSCH containing uplink data to the network device. In this case, the terminal device does not send a padding packet to the network device. When the terminal device does not send a scheduling request (scheduling request, SR) or a buffer status report (buffer status report, BSR) to the network device, when the network device schedules the terminal device to send a PUSCH through the first DCI, it is impossible to know whether the terminal device has uplink data to be sent. After receiving the first DCI, the terminal device will include uplink data in the PUSCH when there is uplink data, and include a padding packet in the PUSCH when there is no uplink data, according to its actual situation. If uplink data happens to have arrived when the terminal device receives the first DCI, even if the terminal device has not sent the corresponding SR or BSR to request the network device to schedule, the terminal device can send the uplink data to the network device through the PUSCH scheduled by the first DCI.

In the above situation a2, when the terminal device is configured with the uplink skip function, the terminal device may not send PUSCH to the network device.

When the terminal device is configured with the uplink skip function, when the terminal device receives the DCI that schedules PUSCH and there is no uplink data to be sent, the terminal device may not send PUSCH. That is to say, in the above situation a2, when the terminal device is configured with the uplink skip function, after the network device sends the first DCI, the terminal device does not need to send PUSCH or receive PDSCH. Therefore, from the perspective of energy saving of the terminal device, when the terminal device is configured with the uplink skip function, the first DCI that schedules PUSCH (scheduling padding) is used in the above situation a2 to indicate that the terminal device does not monitor PDCCH within the first time period, the power consumption of the terminal device can be lower than that when the first DCI in situation a1 is used.

Optionally, when the terminal device is configured with the uplink skip function, if the terminal device has a temporary service arrival, that is, when uplink data needs to be sent, the terminal device can send uplink data to the network device through the PUSCH scheduled by the network device. In this case, the terminal device no longer needs to request uplink resources from the network device through a scheduling request (SR), thereby reducing service latency.

In a possible implementation, the terminal device may be configured with connected discontinuous reception (CDRX). The C-DRX cycle may be a long DRX cycle or a short DRX cycle, wherein the long DRX cycle is a default mandatory configuration and the short DRX cycle is an optional configuration. If the short DRX cycle is configured, the terminal device will start a short cycle timer (ShortCycleTimer) when using the short DRX cycle, and will convert to a long DRX cycle when the ShortCycleTimer times out.

For example, as shown in FIG7 , the CDRX cycle includes an “On Duration” portion and an “Opportunity for DRX” portion. The terminal device monitors the PDCCH during the OnDuration of each CDRX cycle. If no new data scheduling is received during the OnDuration (i.e., no PDCCH indicating a new transmission is received), the terminal device enters the Opportunity for DRX after the OnDuration ends, stops monitoring the PDCCH, and starts monitoring the PDCCH again until the OnDuration of the next cycle. If a new data scheduling is received during the OnDuration (i.e., a PDCCH indicating a new transmission is received), the terminal device starts an inactivity timer (or inactivation timer) (InactivityTimer or DRX-inactivitytimer), and the terminal device still monitors the PDCCH during the running of the InactivityTimer. If a new data scheduling is received again during the running of the InactivityTimer, the InactivityTimer will be restarted. Whether it is within OnDuration or when InactivityTimer is running, it is called active time. The terminal device needs to monitor PDCCH during active time. Restarting InactivityTimer can be understood as extending the active time of the terminal device. When InactivityTimer times out, the terminal device stops monitoring PDCCH.

Among them, the method for judging whether it is "new data scheduling" is to see whether the new data indicator (NDI) (NDI is 1-bit, with a value of '0' or '1') field in the DCI is flipped (toggle). If for the same hybrid automatic repeat request process (HARQ process) (i.e., the HARQ process number (HPN) field has the same value), the NDI in the DCI received by the terminal device is flipped compared to the NDI of the DCI received last time (for example, NDI flips from 0 to 1, or NDI flips from 1 to 0), it is considered that new data is transmitted using the HARQ process; if the NDI in the DCI received by the terminal device is the same as the NDI of the DCI received last time, it is considered that data is retransmitted using the HARQ process.

In some embodiments, when the network device instructs the terminal device configured with CDRX not to monitor the PDCCH in a time period, as shown in FIG8 , the network device can instruct the terminal device not to monitor the PDCCH in certain time periods within the active time by scheduling DCI, thereby increasing the sleep time of the terminal device based on the CDRX mechanism. In this case, there is still a situation where the network device cannot instruct the terminal device to skip the PDCCH when no business arrives at the terminal device.

However, using the method in the above situation a1, the first DCI of scheduling PDSCH (including padding data packets) may cause the restart of InactivityTimer, resulting in an extension of the active time of the terminal device. Extending the active time may increase the time the terminal device needs to monitor PDCCH, increasing the power consumption of the terminal device.

Based on this, in the above situation a1, when the terminal device is configured with CDRX, the terminal device does not start the DRX-inactivity timer after receiving the PDSCH containing the filling data packet from the network device; or, when the DRX-inactivity timer is running, the terminal device does not restart or stop the DRX-inactivity timer after receiving the PDSCH containing the filling data packet from the network device.

Similarly, when the terminal device is configured with CDRX, after the network device sends a PDSCH including a padding data packet to the terminal device, the network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, after the network device sends a PDSCH including a padding data packet to the terminal device, it does not restart or stop the DRX-inactivity timer.

However, using the method in the above situation a2, scheduling the first DCI of PUSCH (including padding data packet) may also cause the InactivityTimer to be restarted, resulting in extending the active time of the terminal device. Extending the active time may increase the time the terminal device needs to monitor PDCCH, thereby increasing the power consumption of the terminal device.

Therefore, in the above situation a2, when the terminal device is configured with CDRX and is not configured with the uplink skip function, after the terminal device sends a PUSCH containing a filling data packet to the network device, the terminal device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, after the terminal device sends a PUSCH containing a filling data packet to the network device, it does not restart or stop the DRX-inactivity timer.

Similarly, when the terminal device is configured with CDRX, after the network device receives a PUSCH including a padding data packet sent by the terminal device, the network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, after the network device receives a PUSCH including a padding data packet sent by the terminal device, the network device does not restart or stop the DRX-inactivity timer. After completing the decoding of the PUSCH, the network device can determine whether the PUSCH contains a padding packet, and can also determine whether to start, restart or stop the DRX-inactivity timer.

Alternatively, in the above situation a2, when the terminal device is configured with CDRX and the uplink skip function, when the terminal device does not send PUSCH, that is, after the terminal device determines (because there is no data to be transmitted) not to send PUSCH, the terminal device does not start the DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not send PUSCH, that is, after the terminal device determines (because there is no data to be transmitted) not to send PUSCH, it does not restart or stop the DRX-inactivitytimer.

Similarly, when the terminal device is configured with CDRX, the network device does not receive the PUSCH sent by the terminal device at the position indicated by the first DCI (i.e., the time and frequency position of the terminal device sending PUSCH indicated when the first DCI schedules PUSCH), and the network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device does not receive the PUSCH sent by the terminal device at the position indicated by the first DCI, and does not restart or stop the DRX-inactivity timer.

Through the above method, the active time of the terminal device can be prevented from being extended, thereby saving the power consumption of the terminal device.

In an optional implementation, in the methods of the above cases a1 and a2, the value of the NDI field in the first DCI may be different from the value of the NDI field in the third DCI, and the third DCI is the previous DCI with the same value as the HARQ HPN field of the first DCI. In this case, the first DCI can be understood as a new transmission DCI.

When the terminal is configured with CDRX and the first DCI is a new DCI, the terminal device and the network device do not need to start the DRX-inactivity timer because the padding packet scheduled by the first DCI (contained in PDSCH or PUSCH) instructs the terminal device to skip monitoring PDCCH. Therefore, the terminal device and the network device do not start, restart or stop the DRX-inactivity timer, thereby avoiding extending the active time of the terminal device and saving power consumption of the terminal device.

In an optional implementation, in the method of the above situation a1, the value of the NDI field in the first DCI may be the same as the value of the NDI field in the second DCI, and the second DCI is the previous DCI with the same value as the HARQ HPN field of the first DCI. This situation can be understood as the first DCI being a retransmission DCI.

When the first DCI is a retransmitted DCI, before the terminal device receives the first DCI from the network device, the terminal device sends correct response (acknowledgement character, ACK) information to the network device after receiving the second DCI from the network device.

Normally, after a terminal device erroneously receives a PDSCH, it will feedback NACK, allowing the network device to schedule the retransmission of the same data. When the terminal device receives the retransmitted data, it will combine and decode the received retransmitted data with the data that has been received previously and is in the buffer. When the first DCI is a retransmission DCI, although the network device sends the retransmission DCI, after the data in the same HARQ process has been correctly transmitted (the terminal device feedbacks ACK information), the terminal device usually clears the historical data packets stored in the buffer. Therefore, the data scheduled by the retransmission DCI is usually not combined and decoded with the previously received data, but is decoded separately. After the terminal device decodes the data packet scheduled by the first DCI separately, it can identify that the currently scheduled data packet is a padding packet.

In addition, when the terminal is configured with CDRX and the first DCI is a retransmission DCI, the terminal device and the network device do not start, restart or stop the DRX-inactivity timer to avoid extending the active time of the terminal device, thereby saving power consumption of the terminal device.

By adopting the communication method provided in the embodiment of the present application, when no service arrives at the terminal device, the DCI of the scheduled filling data packet can be used to instruct the terminal device not to monitor the PDCCH within the first time period, thereby reducing the power consumption of the terminal device.

Another communication method provided in the embodiment of the present application is applicable to the communication system shown in Figure 1. Referring to Figure 9, the specific process of the method may include:

Step 901: The network device sends a downlink filling data packet to the terminal device, and correspondingly, the terminal device receives a downlink filling data packet from the network device.

In an optional implementation, the network device may send a downlink filling data packet to the terminal device in the following manner: the network device sends a PDSCH to the terminal device, the PDSCH includes a MAC sub-PDU, and the LCID value corresponding to the MAC sub-PDU is 63.

Specifically, for the description about the LCID value corresponding to the MAC sub-PDU in the PDSCH being 63 to indicate the padding data packet, please refer to the description of the PDSCH in the embodiment shown in FIG. 4 in combination with FIG. 6 and Table 1, which will not be described in detail here.

Step 902: The network device determines that the terminal device does not monitor the PDCCH within a second time period.

Step 903: The terminal device determines not to monitor the PDCCH within the second time period according to the downlink filling data packet.

It should be noted that the order of step 902 and step 903 is not limited in this application.

Exemplarily, the network device may send a DCI to the terminal device, the DCI being used to schedule the downlink filling data packet, and the DCI instructing the terminal device not to monitor the PDCCH within the second time period after receiving the downlink filling data packet. In this way, the terminal device may determine not to monitor the PDCCH within the second time period after receiving the downlink data packet.

Optionally, the second duration may be configured by the network device for the terminal device, may be predefined, or may be indicated simultaneously by the network device when sending a downlink filling data packet to the terminal device. For example, the PDSCH sent by the network device to the terminal device includes both the downlink filling data packet and the second duration.

Exemplarily, the DCI may be DCI format 1_0, or may be DCI format 1_1 or DCI format 1_2.

Through the above method, after the terminal device receives the downlink filling data packet, it can achieve not monitoring the PDCCH for a period of time, thereby saving the power consumption of the terminal device.

Another communication method provided in the embodiment of the present application is applicable to the communication system shown in Figure 1. Referring to Figure 10, the specific process of the method may include:

Step 1001: The network device sends a downlink filling data packet to the terminal device.

Specifically, the relevant description of the network device sending the downlink filling data packet to the terminal device can be found in the relevant description in the above step 901, which will not be repeated here.

Step 1002: The network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device does not restart or stop the DRX-inactivity timer.

Step 1003: The terminal device determines, based on the downlink filling data packet, that the terminal device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, determines that the terminal device does not restart or stop the DRX-inactivity timer.

It should be noted that the order of step 1002 and step 1003 is not limited in this application.

Through the above method, after the terminal device receives a downlink filling data packet, by not starting the DRX-inactivitytimer, or not restarting or stopping the running DRX-inactivitytimer, it is possible to avoid extending the activation time of the terminal device, thereby reducing the power consumption of the terminal device.

Based on the above embodiments, the embodiments of the present application further provide a communication device, as shown in FIG11 , the communication device 1100 may include a transceiver unit 1101 and a processing unit 1102. The transceiver unit 1101 is used for the communication device 1100 to receive information (message or data) or send information (message or data), and the processing unit 1102 is used to control and manage the actions of the communication device 1100. The processing unit 1102 may also control the steps performed by the transceiver unit 1101.

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

In one embodiment, when the communication device 1100 is used to implement the function of the terminal device in the embodiment described in Figure 4 above, it may specifically include: the transceiver unit 1101 is used to receive a first DCI from a network device, the first DCI is used to schedule a fill data packet, and the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within a first time length; the processing unit 1102 is used to determine not to monitor the PDCCH within the first time length according to the first DCI.

In an optional implementation, the first DCI is used to schedule a physical downlink shared channel PDSCH.

Exemplarily, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the modulation and coding mode cell specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the configuration scheduling radio network temporary identifier CS-RNTI.

Optionally, the transceiver unit 1101 is further used to receive a physical downlink shared channel PDSCH from the network device, where the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63.

In another optional implementation, the first DCI is used to schedule a physical uplink shared channel PUSCH.

Exemplarily, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the modulation and coding mode cell specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the configuration scheduling radio network temporary identifier CS-RNTI.

Optionally, the transceiver unit 1101 is further used to send a physical uplink shared channel PUSCH to the network device, where the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63.

In one possible embodiment, the transceiver unit 1101 is also used to send a physical uplink shared channel PUSCH to the network device, wherein the PUSCH includes the padding data packet; the processing unit 1102 is also used to not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, not restarting or stopping the DRX-inactivitytimer.

In one example, when the terminal device is configured with an uplink skip function, the transceiver unit 1101 is further used to not send a physical uplink shared channel PUSCH to the network device.

In another possible manner, when the transceiver unit 1101 is also used to not send a physical uplink shared channel PUSCH to the network device, the processing unit 1102 is also used to not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the DRX-inactivitytimer is not restarted or stopped.

In one example, the transceiver unit 1101 is also used to receive a physical downlink shared channel PDSCH from the network device, wherein the PDSCH includes the padding data packet; the processing unit 1102 is also used to not start a discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, not restarting or stopping the DRX-inactivity timer.

Optionally, the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI, and the second DCI is the previous DCI having the same value as the hybrid automatic repeat request HARQ process number HPN field of the first DCI.

Exemplarily, the transceiver unit 1101 is further configured to receive the second DCI from the network device before receiving the first DCI from the network device, and send correct response ACK information to the network device.

Optionally, the value of the new data indication NDI field in the first DCI is different from the value of the NDI field in the third DCI, and the third DCI is the previous DCI having the same value as the hybrid automatic repeat request HARQ process number HPN field of the first DCI.

In another embodiment, when the communication device 1100 is used to implement the function of the network device in the embodiment described in Figure 4 above, it may specifically include: the processing unit 1102 is used to determine the first downlink control information DCI, the first DCI is used to schedule fill data packets, and the first DCI indicates that the terminal device does not monitor the physical downlink control channel PDCCH within a first time period; the transceiver unit 1101 is used to send the first DCI to the terminal device.

Optionally, the processing unit 1102 is further used to: before the transceiver unit 1101 sends the first DCI to the terminal device, determine that no service arrives at the terminal device within a preset time period; or determine that there is no cache data corresponding to the terminal device.

In an optional implementation, the first DCI is used to schedule a physical downlink shared channel PDSCH.

Exemplarily, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the modulation and coding mode cell specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the configuration scheduling radio network temporary identifier CS-RNTI.

Optionally, the network device sends a physical downlink shared channel PDSCH to the terminal device, where the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63.

In an optional implementation, the first DCI is used to schedule a physical uplink shared channel PUSCH.

Exemplarily, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the modulation and coding mode cell specific radio network temporary identifier MCS-C-RNTI; or, the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the configuration scheduling radio network temporary identifier CS-RNTI.

In one possible design, the transceiver unit 1101 is also used to receive a physical uplink shared channel PUSCH from the terminal device, where the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier LCID corresponding to the MAC subPDU has a value of 63.

In another possible design, when the terminal device is configured with an uplink skip function, the transceiver unit 1101 is also used to not receive PUSCH from the terminal device.

In one example, the transceiver unit 1101 is also used to receive a physical uplink shared channel PUSCH from the terminal device, wherein the PUSCH includes the padding data packet; the processing unit 1102 is also used to not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, not restarting or stopping the DRX-inactivitytimer.

In another example, the processing unit 1102 is also used to not start the discontinuous reception inactivity timer DRX-inactivitytimer if the transceiver unit 1101 does not receive the physical uplink shared channel PUSCH sent by the terminal device at the position indicated by the first DCI; or, when the DRX-inactivitytimer is running, not restart or stop the DRX-inactivitytimer.

In another example, the transceiver unit 1101 is also used to send a physical downlink shared channel PDSCH to the terminal device, wherein the PDSCH includes the padding data packet; the processing unit 1102 is also used to not start a discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, not restarting or stopping the DRX-inactivity timer.

Optionally, the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI, and the second DCI is the previous DCI having the same value as the hybrid automatic repeat request HARQ process number HPN field of the first DCI.

Exemplarily, the transceiver unit 1101 is further used to send the second DCI to the terminal device before sending the first DCI to the terminal device, and receive correct response ACK information from the terminal device.

Optionally, the value of the new data indication NDI field in the first DCI is different from the value of the NDI field in the third DCI, and the third DCI is the previous DCI having the same value as the hybrid automatic repeat request HARQ process number HPN field of the first DCI.

In another embodiment, when the communication device 1100 is used to implement the function of the terminal device in the embodiment described in Figure 9 or Figure 10 above, it may specifically include: the transceiver unit 1101 is used to receive a downlink filling data packet from a network device; the processing unit 1102 is used to determine the first operation of the terminal device according to the downlink filling data packet.

Exemplarily, when receiving the downlink filling data packet from the network device, the transceiver unit 1101 can be used to: receive a physical downlink shared channel PDSCH from the network device, the PDSCH containing a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63.

In an optional implementation, the first operation is not to monitor a physical downlink control channel PDCCH within a second time period.

Optionally, the transceiver unit 1101 is further used to receive downlink control information DCI from the network device, the DCI is used to schedule the downlink filling data packet, and the DCI instructs the terminal device not to monitor PDCCH within the second time length after receiving the downlink filling data packet.

Exemplarily, the DCI is DCI format 1_0.

In another optional implementation, the first operation is not starting a discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, the first operation is not restarting or stopping the DRX-inactivity timer.

In another embodiment, when the communication device 1100 is used to implement the function of the network device in the embodiment described in Figure 9 above, it may specifically include: the transceiver unit 1101 is used to send a downlink filling data packet to the terminal device; the processing unit 1102 is used to determine that the terminal device does not monitor the physical downlink control channel PDCCH within the second time period.

Optionally, when sending the downlink filling data packet to the terminal device, the transceiver unit 1101 can be used to: send a physical downlink shared channel PDSCH to the terminal device, the PDSCH including a media access control sub-protocol data unit MAC sub-PDU, and the logical channel identifier LCID corresponding to the MAC sub-PDU has a value of 63.

Exemplarily, the transceiver unit 1101 is further used to send downlink control information DCI to the terminal device, the DCI is used to schedule the downlink filling data packet, and the DCI instructs the terminal device not to monitor the PDCCH within the second time length after receiving the downlink filling data packet.

In one example, the DCI is DCI format 1_0.

In another embodiment, when the communication device 1100 is used to implement the function of the network device in the embodiment described in Figure 10 above, it may specifically include: the transceiver unit 1101 is used to send a downlink filling data packet to the terminal device; the processing unit 1102 is used to not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, not restarting or stopping the DRX-inactivitytimer.

Optionally, when sending the downlink filling data packet to the terminal device, the transceiver unit 1101 is used to: send a physical downlink shared channel PDSCH to the terminal device, the PDSCH including a media access control sub-protocol data unit MAC sub-PDU, and the logical channel identifier LCID corresponding to the MAC sub-PDU has a value of 63.

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

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

Based on the above embodiments, the embodiments of the present application further provide a communication device, as shown in FIG12, the communication device 1200 may include a transceiver 1201 and a processor 1202. Optionally, the communication device 1200 may further include a memory 1203. The memory 1203 may be disposed inside the communication device 1200 or outside the communication device 1200. The processor 1202 may control the transceiver 1201 to receive and send information, messages or data, etc.

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

The transceiver 1201, the processor 1202 and the memory 1203 are interconnected. Optionally, the transceiver 1201, the processor 1202 and the memory 1203 are interconnected via a bus 1204; the bus 1204 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus and the like. For ease of representation, FIG12 is represented by only one thick line, but it does not mean that there is only one bus or one type of bus.

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

Exemplarily, the communication device 1200 may be the network device in the above embodiment; or may be the terminal device in the above embodiment.

In one embodiment, when the communication device 1200 implements the functions of the terminal device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10, the transceiver 1201 can implement the transceiver operation performed by the terminal device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10; the processor 1202 can implement other operations except the transceiver operation performed by the terminal device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10. For specific related descriptions, please refer to the related descriptions in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10, which will not be described in detail here.

In one embodiment, when the communication device 1200 implements the function of the network device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10, the transceiver 1201 can implement the transceiver operation performed by the network device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10; the processor 1202 can implement other operations except the transceiver operation performed by the network device in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10. For specific related descriptions, please refer to the related descriptions in the embodiment shown in FIG. 4, FIG. 9 or FIG. 10, which will not be described in detail here.

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

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

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

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

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

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

The present application is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

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

Claims (34)

1. A communication method, characterized in that it includes: The terminal device receives first downlink control information DCI from the network device, the first DCI is used to schedule filling data packets, and the first DCI instructs the terminal device not to monitor the physical downlink control channel PDCCH within a first duration; The terminal equipment determines not to monitor the PDCCH within the first duration according to the first DCI. 2. The method of claim 1, wherein the first DCI is used to schedule a physical downlink shared channel (PDSCH). 3. The method of claim 2, wherein the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the cell wireless network temporary identifier C-RNTI; or The first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the modulation and coding method cell-specific wireless network temporary identity MCS-C-RNTI; or The first DCI is a DCI format 1_1 or a DCI format 1_2 scrambled by the configured scheduling wireless network temporary identifier CS-RNTI. 4. The method according to claim 2 or 3, characterized in that the method further comprises: The terminal device receives the physical downlink shared channel PDSCH from the network device. The PDSCH contains a media access control sub-protocol data unit MAC sub PDU. The logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. 5. The method of claim 1, wherein the first DCI is used to schedule a physical uplink shared channel (PUSCH). 6. The method of claim 5, wherein the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the cell wireless network temporary identifier C-RNTI; or The first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the modulation and coding method cell-specific wireless network temporary identity MCS-C-RNTI; or The first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the configuration scheduling wireless network temporary identity CS-RNTI. 7. The method according to claim 5 or 6, characterized in that the method further comprises: The terminal device sends a physical uplink shared channel PUSCH to the network device. The PUSCH contains a media access control sub-protocol data unit MAC sub PDU. The logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. 8. The method according to any one of claims 5-7, characterized in that the method further includes: The terminal device sends a physical uplink shared channel PUSCH to the network device, where the PUSCH contains the padding data packet; The terminal device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not restart or stop the DRX-inactivitytimer. 9. The method according to claim 5 or 6, characterized in that when the terminal device is configured with an uplink skip function, the method further includes: The terminal device does not send the physical uplink shared channel PUSCH to the network device. 10. The method of claim 9, further comprising: The terminal device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not restart or stop the DRX-inactivitytimer. 11. The method according to any one of claims 2-4, characterized in that the method further includes: The terminal device receives a physical downlink shared channel PDSCH from the network device, wherein the PDSCH includes the padding data packet; The terminal device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the terminal device does not restart or stop the DRX-inactivitytimer. 12. The method according to any one of claims 2-4 and 11, wherein the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI. The second DCI is the previous DCI that has the same value as the HARQ process number HPN field of the first DCI. 13. The method of claim 12, wherein before the terminal device receives the first DCI from a network device, the method further includes: The terminal device receives the second DCI from the network device and sends correct response ACK information to the network device. 14. The method of any one of claims 2-11, wherein the new data in the first DCI indicates that the value of the NDI field is different from the value of the NDI field in the third DCI, and the value of the NDI field in the first DCI is different. The third DCI is the previous DCI with the same value as the HARQ process number HPN field of the first DCI. 15. A communication method, characterized by comprising: The network device determines the first downlink control information DCI, the first DCI is used to schedule the filling data packet, and the first DCI instructs the terminal device not to monitor the physical downlink control channel PDCCH within the first duration; The network device sends the first DCI to the terminal device. 16. The method of claim 15, wherein before the network device sends the first DCI to the terminal device, the method further includes: The network device determines that no traffic arrives at the terminal device within a preset time period; or The network device determines that there is no cache data corresponding to the terminal device. 17. The method according to claim 15 or 16, characterized in that the first DCI is used to schedule the physical downlink shared channel PDSCH. 18. The method of claim 17, wherein the first DCI is a DCI format 1_1 or a DCI format 1_2 scrambled by the cell radio network temporary identifier C-RNTI; or The first DCI is DCI format 1_1 or DCI format 1_2 scrambled by the modulation and coding method cell-specific wireless network temporary identity MCS-C-RNTI; or The first DCI is a DCI format 1_1 or a DCI format 1_2 scrambled by the configured scheduling wireless network temporary identifier CS-RNTI. 19. The method of claim 17 or 18, further comprising: The network device sends a physical downlink shared channel PDSCH to the terminal device. The PDSCH contains a media access control sub-protocol data unit MAC sub PDU. The logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. 20. The method according to claim 15 or 16, characterized in that the first DCI is used to schedule the physical uplink shared channel PUSCH. 21. The method of claim 20, wherein the first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the cell wireless network temporary identifier C-RNTI; or The first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the modulation and coding method cell-specific wireless network temporary identity MCS-C-RNTI; or The first DCI is DCI format 0_1 or DCI format 0_2 scrambled by the configuration scheduling wireless network temporary identity CS-RNTI. 22. The method of claim 20 or 21, further comprising: The network device receives the physical uplink shared channel PUSCH from the terminal device. The PUSCH contains a media access control sub-protocol data unit MAC sub PDU. The logical channel identifier LCID corresponding to the MAC sub PDU has a value of 63. 23. The method of claim 20 or 21, wherein when the terminal device is configured with an uplink skip function, the method further includes: The network device does not receive PUSCH from the terminal device. 24. The method according to any one of claims 20-22, wherein the method further comprises: The network device receives a physical uplink shared channel PUSCH from the terminal device, where the PUSCH contains the padding data packet; The network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. 25. The method according to any one of claims 20-21 and 23, characterized in that the method further includes: The network device does not receive the physical uplink shared channel PUSCH sent by the terminal device at the location indicated by the first DCI; The network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. 26. The method according to any one of claims 17-19, characterized in that the method further comprises: The network device sends a physical downlink shared channel PDSCH to the terminal device, where the PDSCH includes the padding data packet; The network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. 27. The method according to any one of claims 17-19 and 26, wherein the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI. The second DCI is the previous DCI that has the same value as the HARQ process number HPN field of the first DCI. 28. The method of claim 27, wherein before the network device sends the first DCI to the terminal device, the method further includes: The network device sends the second DCI to the terminal device, and receives correct response ACK information from the terminal device. 29. The method of any one of claims 17-26, wherein the new data in the first DCI indicates that the value of the NDI field is different from the value of the NDI field in the third DCI, and the value of the NDI field in the first DCI is different. The third DCI is the previous DCI with the same value as the HARQ process number HPN field of the first DCI. 30. A communication device, characterized by comprising 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 is coupled to the memory and configured to invoke computer instructions in the memory to perform the method according to any one of claims 1-14 through the transceiver. 31. A communication device, characterized by comprising 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 is coupled to the memory and configured to invoke computer instructions in the memory to perform the method according to any one of claims 15-29 through the transceiver. 32. A computer-readable storage medium, characterized in that computer-executable instructions are stored in the computer-readable storage medium, and when called by the computer, the computer-executable instructions execute claims 1-14 The method according to any one of claims 15-29, or the method according to any one of claims 15-29. 33. A computer program product, characterized in that it contains instructions that, when run on a computer, cause the method of any one of claims 1-14, or the method of any one of claims 15-29. The method described in one item is executed. 34. A chip, characterized in that the chip is coupled to a memory for reading and executing program instructions stored in the memory to implement the method according to any one of claims 1-14, or Implement the method as claimed in any one of claims 15-29.