CN117354900A

CN117354900A - Discontinuous reception configuration method and device

Info

Publication number: CN117354900A
Application number: CN202210890313.3A
Authority: CN
Inventors: 薛祎凡; 张彦清; 秦熠; 曹佑龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-06-27
Filing date: 2022-07-27
Publication date: 2024-01-05
Also published as: WO2024001790A1

Abstract

The application provides a discontinuous reception configuration method and device, relates to the technical field of communication, and solves the problems that the duration of monitoring a Physical Downlink Control Channel (PDCCH) by a terminal device is longer, and the energy-saving efficiency is lower. The method comprises the following steps: the terminal equipment receives a first PDCCH in a first Discontinuous Reception (DRX) period; if the first condition is met, the terminal equipment stops monitoring the physical downlink control channel PDCCH at a first moment; the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH times out or a time after the inactivity timer InactivityTimer times out.

Description

Discontinuous reception configuration method and device

The present application claims priority from the chinese patent application filed on 27 months 2022, with application number 202210743794.5, application name "method for stopping monitoring PDCCH, terminal device, network device", the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for configuring discontinuous reception.

Background

In a wireless communication system, in order to save power consumption of a terminal device on the premise of ensuring that data can be effectively transmitted, a discontinuous reception (discontinuous reception, DRX) mechanism is introduced to control the behavior of the terminal device to monitor a physical downlink control channel (Physical Downlink Control Channel, PDCCH). The network device issues a DRX configuration for the terminal device, where the DRX configuration may include configuration information of a DRX cycle and duration onDuration, and is used to determine that the terminal device may continuously monitor a PDCCH to obtain scheduling information in an onDuration period of the DRX cycle. If the terminal equipment does not receive any scheduling information in the onDuration period, the terminal equipment enters a sleep state, and stops monitoring the PDCCH to save power consumption.

For extended reality (XR) services, such as Virtual Reality (VR), augmented reality (augmented reality, AR), cloud Game (CG), etc., the service features that the arrival of data packets is periodic and has a short interval time, for example, a certain XR service is to transmit 60 frames of images per second, and the arrival time interval of two adjacent data packets is 16.67 milliseconds (ms) on average, without considering the transmission delay. However, considering that in downlink transmission, due to different routing paths of the data packets from the server to the base station, jitter (jitter) may occur in the actual arrival time of the data packets, for example, 0-8 ms jitter delay, and different durations of jitter delay may occur in different data packets, for example, the arrival time interval of the data packets may be 16.67 ms-24.67 ms.

Currently, in order to solve the packet delay arrival problem caused by jitter, so that the data arrival time is within the onDuration period of the DRX cycle as much as possible, the length of onDuration may be configured to be long so that the length of onDuration is sufficient to cover the possible period of packet arrival. However, the increase of the onDuration length of the DRX cycle may cause an increase of power consumption of the terminal, and if the jitter delay is short and the actual arrival time of the data packet is early, invalid PDCCH monitoring is performed in the onDuration period after the terminal completes data transmission, so that the energy saving efficiency of the terminal is low.

Disclosure of Invention

The application provides a discontinuous reception configuration method and device, which solve the problems of longer duration setting and lower energy-saving efficiency of a terminal monitoring a Physical Downlink Control Channel (PDCCH) in the prior art.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, a method for configuring discontinuous reception is provided, the method comprising: the terminal equipment receives a first PDCCH in a first DRX period; if the first condition is met, the terminal equipment stops monitoring the physical downlink control channel PDCCH at a first moment; the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH is overtime or a time after overtime.

According to the embodiment, the rule that the terminal equipment stops monitoring the PDCCH is defined, so that the terminal equipment and the network equipment can synchronously stop monitoring the PDCCH according to the rule, and the time for invalid monitoring of the PDCCH in the DRX period is shortened to save power consumption.

In one embodiment, the first condition comprises: at a second moment, a first timer is not running or has timed out, wherein the second moment is the moment when the terminal equipment receives the first PDCCH in the first DRX period, and the starting moment of the first timer is the starting moment or the ending moment of duration onDuration of the second DRX period, or the moment when the terminal equipment receives the PDCCH for the first time in the second DRX period; wherein the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

In the above possible implementation manner, by configuring the first timer, it is determined whether the first timer is overtime, which is used as a determination condition for determining whether the received first PDCCH belongs to the XR data frame of the current DRX cycle or the previous DRX cycle by the terminal device, so as to further determine whether the inactivity timer overtime triggered by the first PDCCH can stop monitoring the PDCCH in advance, and shorten the time for invalidating monitoring the PDCCH to save the power consumption of the terminal device.

In one embodiment, the first condition comprises: the inactivity timer InactivityTimer is not running in a first period, wherein an end time of the first period is a start time of an onDuration of a first DRX period.

According to the possible implementation manner, the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer is the current DRX period or the XR data frame arrived in the previous DRX based on whether the InactivityTimer is running in the first period, so that whether the monitoring of the PDCCH can be terminated in advance is determined, the purpose of saving the power consumption of the terminal device is achieved, the problem that the monitoring of the PDCCH is stopped too early to cause data transmission failure is avoided, and the data transmission efficiency is not influenced. In addition, when the PDCCH is lost at the terminal equipment side, the terminal equipment side can also make the same judgment with the network equipment side, so that the problem of data transmission failure is avoided.

In one embodiment, the duration of the first period is the duration of the inactivity timer.

In one embodiment, the first condition comprises: at the starting moment of the onDuration of the first DRX cycle, the inactive timer is not running, and the terminal device does not lose downlink control information DCI in a second DRX cycle, where the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

According to the possible implementation manner, the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer is the current DRX period or the XR data frame of the previous DRX by determining whether packet loss occurs in the previous DRX period based on the first condition, so that whether the monitoring of the PDCCH can be terminated in advance is judged, the purpose of saving power consumption of the terminal device is achieved, the problem that the monitoring of the PDCCH is stopped too early to cause data transmission failure is avoided, and the data transmission efficiency is not influenced. In addition, when the DCI is lost at the terminal equipment side, the terminal equipment side can also make the same judgment with the network equipment side, so that the problem of data transmission failure is avoided.

In one embodiment, the first condition comprises: the terminal device receives first indication information from the network device in the first DRX cycle, where the first indication information is used to instruct the terminal device to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the terminal device to stop running an onDuration timer (also referred to as onDuration timer) when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

According to the possible implementation manner, the terminal equipment can determine whether to terminate monitoring of the PDCCH in advance when the current InactivityTimer is overtime based on the indication information from the network equipment, so that the purpose of saving power consumption of the terminal equipment is achieved, the problem of data transmission failure caused by stopping monitoring the PDCCH in advance is avoided, and the data transmission efficiency is not affected.

In one embodiment, if the first indication information is carried in a second PDCCH, the first data is data scheduled by the second PDCCH; or if the first indication information is carried in the first PDSCH, the first data is data carried by the first PDSCH.

In one embodiment, the duration of the first timer is preconfigured, or the duration of the first timer is configured by the network device.

In one embodiment, the duration of the first timer is related to the PDB of the application server transmitting the data packet to the terminal device, or the PDB of the application server transmitting the data packet to the terminal device is related to the difference between the PDBs of the application server transmitting the data packet to the access network device. Or the duration of the first timer is related to PDB of the access network device for transmitting the data packet to the terminal device.

In one embodiment, the terminal device starts a second timer at a start time or an end time of onDuration of the first DRX cycle, or at a time when PDCCH is first received in the first DRX cycle; receiving a third PDCCH in a third DRX period; if the second timer is not running or has timed out at the third moment, the terminal equipment stops monitoring the physical downlink control channel PDCCH at the fourth moment; the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time of receiving the third PDCCH, the fourth time is a time of an inactivity timer triggered by the third PDCCH or a time after the inactivity timer is overtime, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In an embodiment, if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle, the terminal device starts the first timer after the first timer times out and the time when the PDCCH is first received in an onDuration of the first DRX cycle.

In one embodiment, the first condition further comprises: the terminal device is not running at the beginning moment of onDuration of the first DRX cycle, and the inactive timer is not running.

In one embodiment, the terminal device loses DCI in the second DRX cycle, which is determined according to at least one of the following information: the HARQ process number HPN, the new data indication NDI and the redundancy version RV received in the second DRX period; alternatively, the data allocation indicates a DAI.

In one embodiment, stopping monitoring the physical downlink control channel PDCCH includes: and stopping the running of the onDuration timer of the first DRX cycle.

In a second aspect, a method for configuring discontinuous reception is provided, the method comprising: the network equipment sends a first PDCCH to the terminal equipment in a first DRX period; if the first condition is met, stopping monitoring the physical downlink control channel PDCCH at a first moment; the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH is overtime or a time after overtime.

In one embodiment, the first condition comprises: the inactivity timer InactivityTimer is not running in a first period, wherein an end time of the first period is a start time of an onDuration of the first DRX cycle.

In one embodiment, the first condition comprises: and the network equipment sends first indication information to the terminal equipment in the first DRX period, wherein the first indication information is used for indicating that the PDCCH is stopped to be monitored when the InactivityTimer is overtime or after the InactivityTimer is overtime, or indicating that the operation of the onDuration timer is stopped when the InactivityTimer is overtime or after the InactivityTimer is overtime, or the first data indicated by the first indication information and the scheduled data in the previous DRX period belong to the same frame of data.

In one embodiment, a second timer is started at a start time or an end time of onDuration of the first DRX cycle, or at a time when a PDCCH is first received in the first DRX cycle of the terminal device; transmitting a third PDCCH to the terminal equipment in a third DRX period; if the second timer is not running or has timed out at the third moment, stopping monitoring the physical downlink control channel PDCCH at the fourth moment; the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time when the terminal device receives the third PDCCH, the fourth time is a time when an inactive timer triggered by the third PDCCH times out or a time after the inactive timer times out, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In an embodiment, if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle, after the first timer times out, and the time when the PDCCH is first received in the onDuration of the first DRX cycle starts the first timer.

In one embodiment, the terminal device loses DCI in the second DRX cycle, which is determined according to at least one of the following information: the HARQ process number HPN, the new data indication NDI and the redundancy version RV in the second DRX period; alternatively, the data allocation indicates a DAI.

In a third aspect, a communication apparatus is provided, the communication apparatus including a transceiver module and a processing module, the transceiver module configured to receive a first PDCCH during a first DRX cycle; if the first condition is met, the processing module is used for stopping monitoring the physical downlink control channel PDCCH at the first moment; the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH is overtime or a time after overtime.

In one embodiment, the first condition comprises: at a second time, a first timer is not running or has timed out, wherein the second time is a time when the communication device receives the first PDCCH in the first DRX cycle, and a starting time of the first timer is a starting time or an ending time of duration onDuration of the second DRX cycle, or a time when the PDCCH is received for the first time in the second DRX cycle; wherein the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

In one embodiment, the first condition comprises: at the starting moment of the onDuration of the first DRX cycle, the inactive timer is not running, and the communication device does not lose downlink control information DCI in a second DRX cycle, where the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

In one embodiment, the first condition comprises: the communication device receives first indication information from the network equipment in the first DRX cycle, where the first indication information is used to instruct the communication device to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the communication device to stop running an onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

In one embodiment, the processing module is further configured to start a second timer at a start time or an end time of onDuration of the first DRX cycle, or at a time when the PDCCH is first received in the first DRX cycle; the transceiver module is further configured to receive a third PDCCH in a third DRX cycle; if the second timer is not running or has timed out at the third time, the processing module is further configured to stop monitoring the physical downlink control channel PDCCH at the fourth time; the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time of receiving the third PDCCH, the fourth time is a time of an inactivity timer triggered by the third PDCCH or a time after the inactivity timer is overtime, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In an embodiment, if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle, the processing module is further configured to start the first timer after the first timer times out and the time when the PDCCH is first received in an onDuration of the first DRX cycle.

In one embodiment, the first condition further comprises: the communication device is not running at the beginning of the onDuration of the first DRX cycle, the inactive timer.

In one embodiment, the processing module is further configured to determine that DCI is lost in the second DRX cycle based on at least one of: the HARQ process number HPN, the new data indication NDI and the redundancy version RV received in the second DRX period; alternatively, the data allocation indicates a DAI.

In a fourth aspect, a communication apparatus is provided, where the communication apparatus includes a transceiver module and a processing module, where the transceiver module is configured to send a first PDCCH to a terminal device in a first DRX cycle; if the first condition is met, the processing module is used for stopping monitoring the physical downlink control channel PDCCH at the first moment; the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH is overtime or a time after overtime.

In one embodiment, the first condition comprises: the communication device sends first indication information to the terminal device in the first DRX cycle, where the first indication information is used to indicate that monitoring of the PDCCH is stopped when or after the inactivity timer times out, or indicate that the operation of the onDuration timer is stopped when or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

In one embodiment, the duration of the first timer is preconfigured or the duration of the first timer is configured by the communication device.

In an embodiment, the processing module is further configured to start a second timer at a start time or an end time of onDuration of the first DRX cycle, or at a time when the PDCCH is first received in the first DRX cycle of the terminal device; the transceiver module is further configured to send a third PDCCH to the terminal device in a third DRX cycle; if the second timer is not running or has timed out at the third time, the processing module is further configured to stop monitoring the physical downlink control channel PDCCH at the fourth time; the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time when the terminal device receives the third PDCCH, the fourth time is a time when an inactive timer triggered by the third PDCCH times out or a time after the inactive timer times out, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In one embodiment, the processing module is further configured to determine that the terminal device loses DCI in the second DRX cycle according to at least one of the following information: the HARQ process number HPN, the new data indication NDI and the redundancy version RV in the second DRX period; alternatively, the data allocation indicates a DAI.

In a fifth aspect, there is provided a terminal device, including: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories for storing computer program code comprising computer instructions which, when executed by the one or more processors, cause the terminal device to perform the method of any of the first aspects described above.

In a sixth aspect, there is provided a network device comprising: one or more processors and one or more memories; the one or more memories are coupled with the one or more processors, the one or more memories for storing computer program code comprising computer instructions that, when executed by the one or more processors, cause the network device to perform the method of any of the second aspects described above.

In a seventh aspect, there is provided a computer readable storage medium having stored therein computer executable instructions for causing the computer to perform the method of any of the above first aspects when invoked by the computer.

In an eighth aspect, there is provided a computer readable storage medium having stored therein computer executable instructions for causing the computer to perform the method of any of the second aspects above when invoked by the computer.

In a ninth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any one of the first aspects above.

In a tenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any of the second aspects above.

In an eleventh aspect, there is provided a chip coupled to a memory for reading and executing program instructions stored in the memory to implement the method according to any of the first aspects above.

In a twelfth aspect, there is provided a chip coupled to a memory for reading and executing program instructions stored in the memory to implement the method of any of the second aspects above.

A thirteenth aspect provides a communication system comprising a communication device as claimed in any one of the third aspects and a communication device as claimed in any one of the fourth aspects.

It should be appreciated that any of the above-described communication apparatuses, computer-readable storage media, computer program products, chips or communication systems may be used to perform the corresponding methods provided above, and thus, the advantages achieved by the above-described communication apparatuses, computer-readable storage media, computer-readable chips or communication systems may refer to the advantages of the corresponding methods provided above, and are not described herein.

Drawings

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of a communication device according to an embodiment of the present application;

fig. 3 is a schematic diagram of a discontinuous reception DRX configuration according to an embodiment of the present application;

fig. 4 is a schematic diagram of a DRX configuration and data transmission according to an embodiment of the present application;

fig. 5 is a flow chart of a discontinuous reception configuration method provided in an embodiment of the present application;

fig. 6 and fig. 7 are schematic diagrams of data transmission under consideration of transmission jitter according to an embodiment of the present application;

fig. 8 is a schematic diagram of a PDB for downlink data transmission according to an embodiment of the present application;

FIGS. 9-13 are schematic diagrams of several configurations of discontinuous reception provided by embodiments of the present application;

fig. 14 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

In this application, the terms "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

First, the implementation environment and application scenario of the embodiment of the present application will be briefly described.

The present application is applicable to existing New Radio (NR) systems and to any other wireless communication system having similar structure and functionality. As shown in fig. 1, the communication system includes at least a terminal device 101 and a network device 102.

The terminal device 101 according to the embodiment of the present application may be a User Equipment (UE), where the UE includes a handheld device, an in-vehicle device, a wearable device, or a computing device with a wireless communication function. The UE may be a mobile phone (mobile phone), a tablet computer, or a computer with a wireless transceiver function, for example. The terminal device may also be a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city, a wireless terminal in smart home, etc.

In the embodiment of the present application, the device for implementing the function of the terminal may be the terminal; or may be a device, such as a chip system, capable of supporting the terminal to perform the function, which may be installed in the terminal. In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiments of the present application, the device for implementing the function of the terminal device is a UE, which is described in the technical solution provided in the embodiments of the present application.

The network device 102 according to the embodiment of the present application may include a Base Station (BS), which may be a device deployed in a radio access network and capable of performing wireless communication with a terminal.

Among them, the base station may have various forms such as macro base station, micro base station, relay station, access point, etc. Illustratively, the base station referred to in the embodiments of the present application may be a base station in 5G or a base station in LTE, where the base station in 5G may also be referred to as a transmission reception point (transmission reception point, TRP) or gNB.

In the embodiment of the present application, the means for implementing the function of the network device may be the network device; or may be a device, such as a system-on-a-chip, capable of supporting the network device to perform this function, which may be installed in the network device.

In the technical solution provided in the embodiments of the present application, the device for implementing the function of the network device is a network device, and the network device is a base station as an example, which describes the technical solution provided in the embodiments of the present application.

The technical scheme provided by the embodiment of the application can be applied to wireless communication between the network equipment and the terminal equipment. In this embodiment of the present application, the term "wireless communication" may also be simply referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission".

It should be noted that fig. 1 is only an exemplary frame diagram, and the number of network element nodes included in fig. 1 is not limited. In addition to the functional nodes shown in fig. 1, other nodes may be included, such as: core network devices, gateway devices, application servers, etc., are not limited. The access network devices communicate with the core network devices via a wired or wireless network, such as via a Next Generation (NG) interface.

In specific implementation, each network element shown in fig. 1 includes: the terminal device, the network device may adopt the constituent structure shown in fig. 2 or include the components shown in fig. 2. Fig. 2 is a schematic structural diagram of a communication device 200 provided in the embodiment of the present application, where the communication device 200 has the function of the terminal device in the embodiment of the present application, the communication device 200 may be a terminal device or a chip or a system on a chip in the terminal device. When the communication apparatus 200 has the function of the network device described in the embodiment of the present application, the communication apparatus 200 may be a network device or a chip or a system on a chip in the network device.

As shown in fig. 2, the communication device 200 may include a processor 201, a communication line 202, and a communication interface 203. Further, the communication device 200 may also include a memory 204. The processor 201, the memory 204, and the communication interface 203 may be connected through a communication line 202.

The processor 201 may be a central processing unit (Central Processing Unit, CPU), a general purpose processor network processor (Network Processor, NP), a digital signal processor (Digital Signal Processing, DSP), a microprocessor, a microcontroller, a programmable logic device, or any combination thereof. The processor 201 may also be other means for processing, such as a circuit, device, or software module.

Communication line 202 is used to communicate information between the various components included in communication device 200.

Communication interface 203 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a radio access network (Radio Access Network, RAN), a wireless local area network (Wireless Local Area Networks, WLAN), etc. The communication interface 203 may be an interface circuit, pin, radio frequency module, transceiver, or any device capable of enabling communication.

Memory 204 for storing instructions. Wherein the instructions may be computer programs.

The Memory 204 may be a Read-only Memory (ROM) or other type of static storage device capable of storing static information and/or instructions, a random access Memory (Random Access Memory, RAM) or other type of dynamic storage device capable of storing information and/or instructions, an electrically erasable programmable Read-only Memory (Electrically Erasable Programmable Read-only Memory, EEPROM), a compact disc Read-only Memory (Compact Cisc Read-only Memory, CD-ROM) or other optical disc storage, magnetic disc storage medium or other magnetic storage device, and optical disc storage includes compact discs, laser discs, optical discs, digital versatile discs, or blu-ray discs, etc.

It should be noted that, the memory 204 may exist separately from the processor 201 or may be integrated with the processor 201. Memory 204 may be used to store instructions or program code or some data, etc. The memory 204 may be located inside the communication device 200 or outside the communication device 200, and is not limited. Processor 201 is configured to execute instructions stored in memory 204 to implement methods provided in the embodiments described below.

In one example, processor 201 may include one or more CPUs, such as CPU0 and CPU1 in fig. 2.

As an alternative implementation, the communication device 200 includes multiple processors, e.g., in addition to the processor 201 in fig. 2, a processor 207 may be included.

As an alternative implementation, the communication apparatus 200 further comprises an output device 205 and an input device 206. By way of example, input device 206 is a keyboard, mouse, microphone, or joystick, and output device 205 is a display, speaker, or the like.

It should be noted that the communication apparatus 200 may be a wearable device, a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device having a similar structure in fig. 2. Further, the constituent structure shown in fig. 2 does not constitute a limitation of the communication apparatus, and the communication apparatus may include more or less components than those shown in fig. 2, or may combine some components, or may be arranged in different components, in addition to those shown in fig. 2.

In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

In connection with the above fig. 1, when in the connection state, the terminal device may enter duration onDuration to monitor the PDCCH continuously or enter sleep time according to the DRX configuration information configured by the network device, and stop monitoring the PDCCH to achieve the purpose of saving power. Wherein the DRX includes a DRX long cycle and a start offset (DRX-longcycle offset), which is used to configure the length of the long DRX cycle and an offset value of the start position of one DRX cycle (whether long or short). Wherein the length of the long DRX cycle is in milliseconds ms, and the configuration granularity of the start offset is 1ms. The DRX configuration information may further include configuration information of a duration timer onduration for determining a period during which the terminal device continuously listens to the PDCCH from a start position of the DRX cycle, that is, a number of consecutive subframes in which the terminal device needs to listen to the PDCCH from a start subframe indicated by DRX-StartOffset. The DRX configuration information may also include configuration information of an inactivity timer. In addition, the DRX parameter further comprises a DRX time slot offset value (DRX-SlotOffset), and the DRX time slot offset value is used for configuring a delay value before starting the DRX-onduration timer, wherein the configuration granularity is 1/32ms, and the value range is 0-31, namely 0 ms-31/32 ms. When the network device enables a DRX short cycle for the terminal device, the DRX parameters may also include a short cycle (shortDRX), which is used to configure the length of the short DRX cycle.

As shown in fig. 3, the general procedure of DRX is as follows: after entering one DRX cycle, the terminal device starts to monitor the PDCCH continuously for a duration (on duration) period. If the PDCCH is not monitored within the duration period, the terminal device directly enters a sleep state after the duration period is ended. If the PDCCH is monitored during the duration period and is used to schedule newly transmitted data (i.e., the PDCCH is used to transmit scheduling information for initial transmission scheduling), the terminal device receives data according to the received scheduling information (i.e., receives PDSCH) and starts a DRX inactivity timer, which is started (or restarted) once every time the terminal device monitors scheduling information for initial transmission scheduling, and the terminal device continuously monitors the PDCCH during the DRX inactivity timer until the DRX inactivity timer times out (expire), and the terminal device enters a sleep state. The DRX configuration information may further include parameters such as DRX hybrid automatic repeat request round trip time Timer (DRX-hybrid auto repeat request round trip Timer, DRX-HARQ-RTT-Timer), DRX retransmission Timer (DRX-retransmission Timer), etc. The terminal device needs to monitor PDCCH during the start of DRX duration timer, DRX inactivity timer, downlink (DL) DRX retransmission timer and Uplink (UL) DRX retransmission timer, which are also collectively referred to as Active Time. The remaining time is collectively referred to as being outside of the activation time (outside Active Time). And the terminal equipment does not need to monitor the PDCCH outside the activation time, and can enter a sleep state at the moment so as to save power consumption.

In a packet scenario where a network device transmits XR or XR-like traffic to a terminal device, as shown in fig. 4, taking an example that the arrival time interval of packets corresponding to two adjacent frames of images (i.e., two XR data frames) is 16.67ms on average, the ideal arrival time interval of XR data frames at the terminal device side may be 16.67ms. It should be understood that a data frame is defined from an application layer perspective, and that a data frame may be replaced by a video frame. One set of protocol data units (protocol data unit set, PDU set) includes traffic data in one frame (frame) of data. The PDU set is defined from the MAC layer point of view. A data frame may also be replaced by a PDU set. In the following embodiments, the service data is taken as an XR data frame as an example, but the following method is also applicable to other service scenarios, and is not limited.

In this case, the network device may configure the terminal device with a DRX cycle length that is relatively close to the XR data frame arrival time interval, for example, may be 16ms, or, by other embodiments, match or approximately match the DRX cycle length with the terminal device side XR data frame arrival time. In the following embodiments of the present application, it is assumed that the DRX cycle length matches the cycle length of the XR data frame.

In addition, considering that in downlink transmission, due to different routing paths of XR data frames from the server to the base station, jitter (jitter) may occur in the actual arrival time of the XR data frames, for example, the duration of jitter may be 0-8 ms. As shown in fig. 4, the actual arrival time of an XR data frame may be delayed by 0-8 ms, i.e., the time interval for the XR data frame to arrive fluctuates between 16.67ms and 24.67 ms. As can be seen in fig. 4, in the presence of jitter, the location where the XR data frame actually arrives may fall outside the onDuration. In this case, since the terminal device does not receive the schedule in the onDuration, the PDCCH is not monitored after the onDuration is finished, and the base station can only delay the XR data frame until the next DRX cycle for scheduling. This situation increases the transmission delay of the data. It is understood that the duration range of jitter is 0-8 ms, and can be equivalently described as that the jitter range is-4 ms, and the reference points are different in the two description modes, but the physical meanings are the same.

In one solution, the problem of XR data frame delay arrival due to jitter can be solved by configuring the onDuration period in the DRX cycle to be longer, i.e. to make the data arrival time as much as possible within the onDuration period. For example, the length of onduratiton is configured to cover the range of delays possible by jitter such that the length of onDuration is sufficient to cover all possible time periods for XR data frame arrival. However, too long duration configuration of DRX may result in too long activation time of the terminal device, and the terminal device may start the inactive timer to extend the activation time when hearing the primary PDCCH, and at the same time, the transmission time of each XR data frame may be shorter, so that the terminal device may perform ineffective PDCCH monitoring (i.e. monitor PDCCH but not receive data scheduling) during most of the activation time, which is difficult to achieve the energy saving effect.

Based on the above-mentioned problems, the implementation manner provided in the embodiment of the present application will be described below with reference to the communication system shown in fig. 1. Wherein each of the devices in the embodiments described below may have the components shown in fig. 2. In this application, the terms and the like related to the embodiments may refer to each other, and the embodiments may be combined with each other without limitation. In the embodiment of the present application, the name of the message or the name of the parameter in the message, etc. interacted between the devices are only an example, and other names may also be adopted in the specific implementation, and are not limited.

The embodiment of the application provides a discontinuous reception configuration method, which enables terminal equipment to shorten the time for monitoring PDCCH in an invalid way and save power consumption for the terminal equipment by configuring some rules for stopping monitoring PDCCH by the terminal equipment. As shown in fig. 5, the method may include:

s501: the network device sends a first PDCCH to the terminal device.

The same network device may be used for data scheduling for multiple terminal devices, and the sizes of XR data frames and the XR data frame scheduling periods of the multiple terminal devices may be different, so that DRX configurations configured by the network device for the terminal devices are also different. Thus, the network device side maintains its corresponding DRX configuration based on different terminal devices, and maintains and updates various DRX related timer operations corresponding to the terminal devices, etc. For example, the network device side determines, according to the DRX configuration of the first terminal, a start time of each DRX cycle corresponding to the first terminal, a start time of duration onDuration of the DRX cycle, and start an inactivity timer, for example, so as to maintain the same DRX configuration as the first terminal side, to synchronize data scheduling, and so on, thereby improving communication efficiency.

It should be noted that, in the embodiments of the present application, only the synchronization DRX configuration of the network device and one terminal device and the interaction between the two are described as examples, and the application scenario is not limited.

Specifically, the network device may send a first PDCCH to the terminal device in a first DRX cycle, where the first PDCCH is scheduling data of the terminal device in the first DRX cycle.

S502: the terminal device receives a first PDCCH in a first DRX period.

Correspondingly, the terminal device receives a first PDCCH from the network device in a first DRX period.

S503: if the first condition is met, stopping monitoring the PDCCH when the inactivity timer InactivityTimer is overtime or after the inactivity timer InactivityTimer is overtime.

Specifically, it may be determined that monitoring of the PDCCH is stopped at a first time, where the first time may be a time when an inactivity timer, including an inactivity timer, triggered by the first PDCCH times out, or a time when the inactivity timer times out.

That is, the embodiment of the application may define a rule for the terminal device to stop monitoring the PDCCH, so that the terminal device may stop monitoring the PDCCH according to the rule, and shorten the time for monitoring the PDCCH in an invalid manner to save power consumption.

Correspondingly, the network device may also determine that the terminal device stops monitoring the PDCCH according to the same judgment rule as the terminal device. Therefore, the network equipment can align with the terminal equipment to monitor the PDCCH time period, so that packet loss or invalid PDCCH monitoring is avoided, and the communication efficiency and the energy-saving efficiency are improved.

Specifically, the rule for stopping monitoring the PDCCH may specifically be: and the terminal equipment determines to stop monitoring the PDCCH after the InactivityTimer triggered by the first PDCCH is overtime, or stops monitoring the PDCCH when the InactivityTimer is overtime.

The terminal device may stop monitoring the PDCCH at a time before the end of the onDuration in the DRX cycle, that is, the terminal device may determine to stop monitoring the PDCCH before the end of the onDuration according to a predefined rule, and enter the sleep state in advance.

For example, as shown in fig. 6, the terminal device may receive the first PDCCH within the onDuration of the DRX cycle, and start the inactivity timer at the time of receiving the first PDCCH. And stopping monitoring the PDCCH after the terminal equipment determines that the InactivityTimer is overtime, namely, the terminal equipment does not monitor the PDCCH any more in the subsequent period of the original onDuration, and enters a dormant state in advance, so that the duration of continuously monitoring the PDCCH is shortened.

In one possible implementation, when the XR data frame of the terminal device is larger, one XR data frame may be further divided into a plurality of protocol data units (Protocol Data Unit, PDU) to be issued respectively, where the XR data frame in the same DRX cycle is divided into a first PDU, a second PDU, a third PDU, and so on to be issued respectively, and each PDU corresponds to a PDCCH of the scheduling data. For example, the terminal device receives a first PDCCH, a second PDCCH, a third PDCCH, and the like in one DRX cycle. Wherein, each PDCCH comprises downlink control information (Downlink control information, DCI) for scheduling one PDU. In addition, each PDCCH for scheduling the newly transmitted data can trigger the start or restart of an inactivity timer InactivityTimer, so that the time for monitoring the PDCCH is prolonged. When XR data frames of the terminal device are large or the number of users in a cell is large, the data transmission duration is long, and the operation time of the inactive time may be continued to the next DRX cycle, for example, as shown in fig. 7, the operation time of the inactive time of the second DRX cycle overlaps with the onDuration of the next adjacent DRX cycle (first DRX cycle).

If the terminal device stops monitoring the PDCCH after the inactivity timer times out, as shown in fig. 7, the terminal device stops monitoring the PDCCH in advance in the onDuration period of the first DRX cycle, so that the terminal device cannot monitor the XR data frame scheduling information PDCCH corresponding to the first DRX cycle. In fig. 7, the PDCCH corresponding to the first DRX indicates the PDCCH corresponding to the XR data frame reached in the first DRX cycle, and the PDCCH corresponding to the second DRX indicates the PDCCH corresponding to the XR data frame reached in the second DRX cycle. In fig. 7, XR data frames arriving at the second DRX cycle are divided into 5 transmissions, so there are 5 PDCCHs corresponding to the second DRX in fig. 7. That is, the terminal device cannot know whether the XR data frame received in one DRX cycle is an XR data frame corresponding to the current cycle or a part of an XR data frame corresponding to the previous cycle, and stops monitoring the PDCCH for energy saving, which results in data reception failure or increases transmission delay.

In order to solve the above problem, in the technical solution provided in the embodiments of the present application, by combining the higher latency requirement of the XR service and the XR data frame dropping (packet drop) function of the network device, the rule that the terminal device stops monitoring the PDCCH is optimized, so that the network device and the terminal device side can determine whether the current startup timer overtime PDCCH is the XR data frame of the current DRX cycle or the XR data frame of the previous DRX based on a certain judgment condition, thereby determining whether to terminate the monitoring of the PDCCH in advance, so as to achieve the purpose of saving the power consumption of the terminal device without affecting the data transmission efficiency.

The XR service has a high requirement for time delay. For example, in a real-time video scene, if the XR data frame transmission delay exceeds a preset standard, problems such as blocking of a real-time video picture, unsmooth display and the like may be caused, and user experience is affected. And the latency requirement may be embodied as a packet latency budget (packet delay budget, PDB). As shown in fig. 8, the downlink data packet is transmitted from the application server to the terminal device, and needs to pass through several processes of internet transmission (the application server sends the data packet to the core network device), core network transmission (the core network device sends the data packet to the access network device), and access network transmission (the access network device sends the data packet to the terminal device), so that the PDB may be divided into an end-to-end PDB and an air-interface PDB.

The end-to-end PDB of the downlink data packet refers to the maximum allowable duration between the time when the data packet is sent from the application server and the time when the data packet is received by the terminal device in order to meet the service requirement. For example, the end-to-end PDB of a service is 100ms, and if the downlink data packet can complete transmission from the application server to the terminal device within 100ms, the transmission requirement of the service can be considered to be satisfied; if the time required for the downlink data packet to complete transmission from the application server to the terminal device exceeds 100ms, the transmission requirement of the service may not be considered to be satisfied.

In addition, the air interface PDB of the downlink data packet refers to the maximum allowable duration for completing transmission of the data packet from the access network device to the terminal device. For example, if the air interface PDB of a certain service is 10ms, and a downlink packet can complete transmission from the base station to the terminal device within 10ms, the transmission requirement of the service can be considered to be satisfied.

Therefore, according to the PDB corresponding to the specific service, if the transmission duration of a certain XR data frame exceeds the corresponding PDB requirement, it can be considered that even if the transmission of the XR data frame is completed, the XR data frame has little meaning for the receiving end. Thus, the network device may enable a Packet Drop (PDB) function, i.e. the network device may not schedule a packet to be transmitted for a packet exceeding the PDB according to the PDB requirements of the XR service.

For example, if the transmission duration of an XR data frame exceeds the corresponding PDB, i.e. the image display time of the XR data frame has elapsed when the XR data frame is sent to the terminal device, the network device may discard the XR data frame and no longer send the XR data frame to the terminal device.

Based on the above technology, in one embodiment, the first condition in the step S503 may specifically include: at a second time, the first timer is not running or has timed out, wherein the second time may be a time when the terminal device receives the first PDCCH in the first DRX cycle.

That is, by configuring the first timer, it will be determined whether the first timer is timed out, as a determination condition for the terminal device to determine whether the received first PDCCH belongs to the XR data frame of the current DRX cycle or the previous DRX cycle.

In one embodiment, as shown in fig. 9, the starting time of the first timer may be the starting time of the duration onDuration of the second DRX cycle, that is, the starting time of the onDuration of the second DRX cycle, and the first timer is started at the same time, where the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.

As shown in fig. 9, in case 1, if the terminal device receives the first PDCCH at the second time in the first DRX cycle and the first timer is running at the second time, it is considered that the first PDCCH may be the scheduling information of the XR data frame arriving in the previous DRX cycle of the first DRX cycle, that is, the scheduling information of the XR data frame arriving in the second DRX cycle, and the inactive timer triggered by the first PDCCH is not triggered to stop monitoring the PDCCH when it is timed out.

Otherwise, in case 2, if the first timer is not running or has timed out at the second moment of receiving the first PDCCH, the first PDCCH is considered to be the scheduling information of the first DRX cycle, and if the inactivity timer triggered by the first PDCCH is timed out, the monitoring of the PDCCH may be stopped, and the monitoring of the PDCCH may be terminated in advance, so as to save power consumption.

In an embodiment, the stopping monitoring the PDCCH may specifically include: the operation of the onDuration timer of the DRX cycle is stopped. As in the example of fig. 9, the operation of the onDuration timer of the first DRX cycle is stopped.

In the above embodiment, the duration of the first timer may be preconfigured, or may also be configured by the network device.

The duration of the first timer may be related to the end-to-end PDB, i.e. to the PDB where the application server transmits XR data frames to the terminal device. In addition, if the average duration of the application server transmitting the XR data frame to the access network device is regarded as a constant value, the duration of the first timer may be the difference between: based on the end-to-end PDB, the average transmission time length of the application server-access network device. For example, as shown in fig. 8, if the end-to-end PDB is T1 and the average transmission duration between the server and the access network device is T2, the duration of the first timer may be set to be the difference obtained by T1-T2.

In the above embodiment, even if a PDCCH (or DCI) packet loss or reception failure occurs in the second DRX cycle, the first DRX cycle XR data frame is not lost due to the PDCCH monitoring being stopped.

As shown in fig. 9, in case 3, if the terminal device does not receive PDCCH-1 shown in the figure, the operation states of the terminal device and the network device side with respect to the inactive timer are inconsistent. At this time, the network device considers that the InactivityTimer does not have timeout, and the terminal device considers that the InactivityTimer has timeout once. However, according to the above embodiment of the present application, when the terminal device receives the first PDCCH and determines that the first timer is in an operation state, when the inactive timer triggered by the first PDCCH times out, both the terminal device and the network device determine that the PDCCH is not triggered to stop being monitored, that is, the PDCCH is still monitored after the inactive timer times out and before the onduration timer does not time out. Otherwise, if the terminal device receives the first PDCCH and determines that the first timer is not running, it is determined that when the InactivityTimer triggered by the first PDCCH is over time, both the terminal device and the network device determine that the monitoring of the PDCCH can be triggered at the moment. Therefore, the technical scheme has stronger robustness.

In another embodiment, the starting time of the first timer may also be the ending time of the second DRX cycle onDuration. That is, the first timer may be started at the end of the onDuration.

At this time, if the terminal device receives the first PDCCH at the second time in the first DRX cycle and the first timer is in the running process at the second time, it is considered that the first PDCCH may be the scheduling information of the XR data frame reached in the previous DRX cycle of the first DRX cycle, that is, the scheduling information of the second DRX cycle, and when the inactive timer triggered by the first PDCCH is timed out, the monitoring PDCCH is not triggered. If the first timer is not running or has timed out at the second moment of receiving the first PDCCH, the first PDCCH is considered to be the scheduling information of the XR data frame arrived in the first DRX cycle, and if the first PDCCH triggers the inactive timer to timeout, the monitoring of the PDCCH may be stopped, and the monitoring of the PDCCH may be terminated in advance.

In such an embodiment, the duration of the first timer may be related to the end-to-end PDB, i.e. to the PDB where the application server transmits XR data frames to the terminal device. Specifically, if the sum of the average transmission duration between the application server and the access network device and the onDuration duration in the DRX cycle is regarded as a constant value, the duration of the first timer may also be related to the difference between the transmission PDB between the application server and the terminal device and the constant value. For example, as shown in fig. 8, the end-to-end PDB is T1, the average transmission duration of the server to the access network device is T2, and the duration of the onDuration of the DRX cycle is T3, and then the duration of the first timer may be set to be the difference obtained by T1-T2-T3.

Further, it should be noted that, in the above embodiment, since the onDuration start time or end time of one DRX cycle starts the first timer, the first timer corresponding to the DRX cycle may coincide with the next adjacent DRX cycle, for example, the first timer of the second DRX cycle may coincide with the onDuration of the first DRX cycle, and the start time or end time of the onDuration of the first DRX cycle needs to restart the first timer (or named as a different timer). Thus, at the same time, more than one first timer may be running that satisfies the foregoing functions.

In one embodiment, the method further comprises the following steps.

Step 1: the second timer is started at a start or end of the onDuration of the first DRX cycle.

Step 2: the terminal device receives a third PDCCH at a third time of a third DRX cycle.

Step 3: and if the second timer is not running or has timed out at the third moment, stopping monitoring the physical downlink control channel PDCCH at the fourth moment. The fourth time is the time of the timeout or the time after the timeout of the InactivityTimer triggered by the third PDCCH.

The third DRX cycle is a next DRX cycle adjacent to the first DRX cycle, the second timer and the first timer are the same function timer, and the duration of the second timer and the first timer are the same.

For example, as shown in fig. 10, taking the starting time of the first timer as the starting time of the DRX cycle onDuration as an example, when the first timer is started at the starting position of the second DRX cycle, and the first timer does not end to run, another timer, that is, the second timer needs to be started at the starting position of the first DRX cycle, where the first timer and the second timer run simultaneously. The terminal device or the network device may determine that the second timer is not running at the third time of receiving the third PDCCH, and therefore, at the fourth time of the inactivity timer timeout, may stop monitoring the PDCCH to save power consumption of the terminal device side.

In another embodiment, the starting time of the first timer included in the first condition may also be a time when the terminal device receives the PDCCH for the first time in the DRX cycle. That is, a first timer is started at the time when the PDCCH is first received within a certain DRX cycle.

At this time, the duration of the first timer may be related to the PDB of the transmission of the XR data frame by the access network device to the terminal device. For example, as shown in connection with fig. 8, the air interface PDB between the access network device and the terminal device is T4, and the duration of the first timer may be set to T4.

In connection with a specific embodiment, as shown in fig. 11, the terminal device starts the first timer at the moment when the PDCCH is first received in the second DRX cycle. If the terminal device receives the PDCCH-1 in the first DRX cycle, the time of receiving the PDCCH-1 is within the running time of the first timer, and the inactive duration time triggered by the PDCCH-1 will not trigger the onDuration early termination of the first DRX cycle, i.e. the onDuration timer is still monitoring the PDCCH after the inactive duration time is overtime and before the onDuration time is overtime.

For example, as shown in fig. 11, if the terminal device starts the first timer at the moment when the terminal device first receives the PDCCH in the first DRX cycle, if the terminal device receives the PDCCH-2 in the third DRX cycle and the moment when the terminal device receives the PDCCH-2 is located after the timer times out, the inactive timer triggered by the PDCCH-2 triggers the onDuration early termination of the third DRX cycle, i.e. the PDCCH monitoring is ended in advance to save the power consumption of the terminal device.

Further, if the starting time of the first timer is the time when the PDCCH is first received in the DRX cycle, as shown in fig. 11, the terminal device starts the first timer corresponding to the second DRX cycle when the PDCCH is first received in the second DRX cycle, and starts (or restarts) the first timer when the first timer times out and the PDCCH is first received in the onDuration of the first DRX cycle.

Similarly, after the first timer corresponding to the first DRX cycle expires, and at the time when the PDCCH is first received in the onDuration of the third DRX cycle, the first timer may be started (or restarted). Wherein the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle.

According to the embodiments, the first timer is defined, so that the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer timeout is the XR data frame of the current DRX period or the XR data frame of the previous DRX based on whether the first timer is running or overtime as a judging condition, and whether the monitoring of the PDCCH can be terminated in advance is determined, the purpose of saving the power consumption of the terminal device is achieved, the problem that the monitoring of the PDCCH is stopped too early to cause data transmission failure is avoided, and the data transmission efficiency is not influenced. In addition, when DCI is lost at the terminal equipment side, the terminal equipment side can also make the same judgment with the network equipment side, so that the robustness of the whole scheme is improved.

In another embodiment, the first condition in the step S503 may specifically include: the inactivity timer InactivityTimer is not running during the first period. Wherein the end time of the first period is the start time of the onDuration of the first DRX cycle. Wherein the duration of the first period of time may be predefined or configured for the network device.

That is, the terminal device or the network device may determine that, in a first period of time that is pushed backward for a certain period of time from the starting time of the onDuration of the first DRX cycle, if the inactive type timer is not running, it indicates that the scheduling information carried by the first PDCCH is the scheduling information of the XR data frame that arrives in the first DRX cycle, but not the scheduling information of the XR data frame that arrives in the previous DRX cycle, so that when the inactive type timer triggered by the first PDCCH is timed out or after the time is timed out (i.e. the XR data frame that arrives in the first DRX cycle completes transmission), monitoring the PDCCH may be stopped; otherwise, if the InactivityTimer is running in the first period, the scheduling information carried by the first PDCCH may be the scheduling information of the XR data frame arrived in the second DRX period, but not the scheduling information of the XR data frame arrived in the first DRX period, and the monitoring of the PDCCH is not stopped in advance, but is continuously monitored to receive the scheduling information of the XR data frame arrived in the subsequent first DRX period.

The above solution considers that there may be an XR data frame with a later completed transmission in the XR data frame arriving in the previous DRX cycle, and therefore, if it is determined that the XR data frame arriving in the previous DRX cycle is still being transmitted at a time close to the next DRX cycle, that is, a preset duration before the starting time of the next DRX cycle onDuration (that is, the duration of the first period described above) is still possible to be transmitted, it is determined that monitoring of the PDCCH is not stopped in advance in the next DRX cycle.

The duration of the first period may be predefined, for example, a specific value of the duration of the first period may be predefined or the duration of the first period may be predefined to be equal to a value of some configuration parameter (for example, the length of the inactive timer); alternatively, the duration of the first period may be configured by the network device, for example, may be carried when the network device issues DRX configuration information to the terminal device. The specific configuration mode is not limited in the present application.

In one embodiment, the duration of the first period may be the duration of the InactivityTimer.

That is, in the duration of the InactivityTimer before the initial time of the onDuration of the first DRX cycle, if the InactivityTimer is not running, monitoring the PDCCH may be stopped when or after the InactivityTimer triggered by the first PDCCH is timed out; if the InactivityTimer is running, the monitoring of the PDCCH is not stopped in advance, namely the PDCCH is still monitored after the InactivityTimer triggered by the first PDCCH is overtime and before the OnDuationTimer is overtime.

Further, in an embodiment, the first condition may specifically include: at the beginning of the onDuration of the first DRX cycle, the InactivityTimer is not running.

That is, the terminal device or the network device may determine: if the InactivityTimer is not running at the initial time of the onDuration of the first DRX period, the monitoring of the PDCCH may be stopped when the InactivityTimer times out or after the InactivityTimer times out (triggered by the first PDCCH received in the first DRX period). Otherwise, if the inactive timer is running at the initial moment of the onDuration of the first DRX cycle, the PDCCH may not be monitored after the inactive timer times out or after the inactive timer times out (triggered by the first PDCCH received in the first DRX cycle), i.e. the PDCCH is still monitored after the inactive timer times out and before the onDuration timer does not time out.

However, if the PDCCH is stopped to be monitored only according to the first condition, and the data loss occurs at the terminal device side, misalignment between the terminal device and the network device side may occur.

For example, if the network device normally transmits PDCCH-1 and the terminal device side does not receive PDCCH-1, the running states of the terminal device and the network device side are misaligned, as shown in fig. 12. When the terminal device receives the PDCCH-2 in the first DRX period, the InactivityTimer triggered by the PDCCH-2 is overlapped with the onDuration of the first DRX period.

As shown in fig. 12 in mode 1, if the network device determines not to stop monitoring the PDCCH by determining that the onDuration start time incactivity timer of the first DRX cycle is running; and the terminal device determines to stop monitoring the PDCCH by judging that the onDuration starting time InactivityTimer of the first DRX period is not running, thereby causing the terminal device and the network device to be misaligned and possibly causing the transmission failure of the XR data frame arrived in the first DRX period.

To solve the above problem, the two first conditions may be combined, that is, the terminal device or the network device may determine the starting time of the onDuration of the first DRX cycle, where the inactive timer is not running; in addition, in the InactivityTimer before the onDuration starting time of the first DRX period, if the InactivityTimer is not running, monitoring the PDCCH can be stopped when the InactivityTimer triggered by the first PDCCH is overtime or after the InactivityTimer is overtime. Otherwise, the PDCCH is still monitored after OnDurationTimer is not overtime after the overtime without stopping the monitoring PDCCH, inactivityTimer.

As shown in fig. 13 in mode 2, the time of the inactivity timer timeout is T1, the onDuration start time of the first DRX cycle is T2, and if T2-T1 is equal to or less than the inactivity timer duration, it is determined that the monitoring of the PDCCH is not stopped or the onDuration timer is not stopped in advance at the time of or after the inactivity timer timeout in the first DRX cycle.

Conversely, if the inactivity timer of the first DRX cycle is sufficiently long, even if the terminal device loses the PDCCH, the inactivity timer triggered by the lost PDCCH will not coincide with the onDuration of the first DRX cycle. Therefore, it can be determined the initial time of onDuration of the first DRX cycle if the inactive timer is running; or at any time within the duration of the InactivityTimer before the onDuration starting time of the first DRX period, if the InactivityTimer is in an operation state, the terminal device does not stop monitoring the PDCCH in the first DRX period in advance.

Therefore, through the embodiment, the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer is the XR data frame reached in the current DRX period or the XR data frame reached in the previous DRX based on the first condition, so that whether the monitoring of the PDCCH can be terminated in advance is determined, the purpose of saving the power consumption of the terminal device is achieved, the problem of data transmission failure caused by the fact that the monitoring of the PDCCH is stopped too early is avoided, and the data transmission efficiency is not influenced. In addition, when the PDCCH is lost at the terminal equipment side, the terminal equipment side can also make the same judgment with the network equipment side, so that the problem of data transmission failure is avoided.

In another embodiment, the method can also be used as a judging condition for determining whether the terminal device loses the packet in the previous DRX cycle or not and stopping monitoring the PDCCH in the current DRX cycle after the inactivity timer is overtime.

Thus, the first condition in step S503 may specifically include: at the start of the onDuration of the first DRX cycle, the InactivityTimer is not running and the terminal device does not lose the downlink control information DCI in the second DRX cycle. Wherein the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

That is, if it is determined that the terminal device does not lose DCI in the second DRX cycle and the inactive timer is not running at the starting time of the onDuration of the first DRX cycle, the monitoring of the PDCCH may be stopped when the inactive timer times out or after the timeout (triggered by the first PDCCH received in the first DRX cycle). Conversely, if it is determined that the terminal device loses DCI in the second DRX cycle and the inactive timer is not running at the starting time of the onDuration of the first DRX cycle, the monitoring of the PDCCH may not be stopped in advance when the inactive timer times out or after the timeout (triggered by the first PDCCH received in the first DRX cycle), i.e. the PDCCH may still be monitored before the onDuration timer does not time out after the timeout of the inactive timer.

In one embodiment, the terminal device may determine whether DCI is lost in a DRX cycle based on a hybrid automatic repeat request (hybrid automatic repeat request, HARQ) process number (HARQ process number, HPN), a new data indication (new data indicator, NDI), and a redundancy version (redundancy version, RV) received in the DRX cycle. Alternatively, the terminal device may also determine whether DCI is lost within a certain DRX cycle according to the data allocation indication (data assignment indication, DAI).

Wherein the HPN is used to indicate the process number of the HARQ process. NDI is used to indicate whether data is initially transmitted or retransmitted, and specifically, whether current data is newly transmitted or retransmitted can be determined by whether the NDI parameter is inverted (toggle). The NDI inversion means that the value of NDI changes from 0 last time to 1 this time or from 1 last time to 0 this time. For example, if the NDI parameter in the DCI allocated by the base station to a certain uplink HARQ process is inverted compared with the previous one, it indicates that the terminal device can perform new uplink transmission this time; if the NDI parameter is the same as the last time, the terminal device can execute uplink adaptive retransmission this time.

The design of RV is used for realizing incremental redundancy (Incremental redundancy, IR) HARQ transmission, namely, the redundant bits generated by an encoder are divided into a plurality of groups, each RV defines a transmission starting point, and different RVs are respectively used for the first transmission and each HARQ retransmission so as to realize gradual accumulation of the redundant bits and complete incremental redundancy HARQ operation. Normally, data primary transmission would use rv=0 and retransmission would use RV >0.

For example, determining whether to lose DCI according to HPN, NDI and RV fields carried in DCI specifically includes: if the NDI corresponding to the same HPN is inverted and RV >0, determining that there is a missing DCI in the DRX cycle.

In addition, in the scenario where the dynamic codebook is adopted for HARQ feedback, when the terminal device feeds back HARQ-Acknowledgement (ACK) information, HARQ-ACK information corresponding to a plurality of physical downlink shared channels (physical downlink shared channel, PDSCH) may be carried in the same information (e.g., DCI) for feedback, that is, the number of HARQ-ACK information and the sequence of a plurality of HARQ-ACKs may be designed through the HARQ-ACK codebook.

Illustratively, in the case where the terminal device determines that the dynamic HARQ-ACK codebook is employed, the downlink control information (downlink control information, DCI) received by the terminal device includes a data allocation indication (data assignment indication, DAI) field. The DAI field indicates the number of data packets (i.e., PDSCH) scheduled. This field can be understood as a counter, and the count result of the DAI indicates the number of bits of the HARQ-ACK codebook before the terminal device feeds back the HARQ-ACK codebook. For example, the HARQ-ACK information of 3 slots is to be fed back in the same slot, the DAI field in the DCI of each slot indicates 1/2/3 of the time slot, and when the terminal device feeds back the HARQ-ACK codebook, if the value indicated by the DAI field in the last DCI is equal to 3, the terminal device can determine that the number of bits of the feedback HARQ-ACK codebook is 3. In another design, the DAI field may be further divided into a count DAI (counter DAI) and a total DAI (total DAI), where the counter DAI is consistent with the functionality of the DAI described above, i.e., is used to indicate which packet (or PDSCH) before a feedback is currently scheduled. the total DAI is used to indicate how many data packets (or PDSCH) are scheduled before one feedback, and the value of total DAI contained in DCI of each scheduling data is generally the same before one feedback. At this time, the size of the HARQ-ACK codebook may be determined according to the value indicated by the total DAI. If the value indicated by the DAI field (specifically, counter DAI) in the first DCI received by the terminal device is greater than 0, determining that the DCI is lost.

According to the embodiment, the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer is the XR data frame of the current DRX period or the XR data frame of the previous DRX by determining whether packet loss occurs in the previous DRX period based on the first condition, so that whether the monitoring of the PDCCH can be terminated in advance is judged, the purpose of saving power consumption of the terminal device is achieved, the problem that the monitoring of the PDCCH is stopped too soon to cause data transmission failure is avoided, and the data transmission efficiency is not influenced. In addition, when the DCI is lost at the terminal equipment side, the terminal equipment side can also make the same judgment with the network equipment side, so that the problem of data transmission failure is avoided.

In another embodiment, since the network device knows which XR data frame arrives in which DRX cycle the XR data frame belongs to when sending the XR data frame to the terminal device, an indication may be sent to the terminal device by the network device, where the indication is used to indicate whether the monitoring of the PDCCH or the running of the onDuration timer may be stopped after the inactivity timer times out, or whether the currently scheduled or transmitted XR data frame is that the data scheduled in the previous DRX cycle belongs to the same frame data.

The first condition in step S503 may specifically include: the network device sends first indication information to the terminal device in a first DRX cycle, where the first indication information may be used to instruct the terminal device to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the terminal device to stop running an onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

Correspondingly, the terminal device receives the first indication information from the network device in the first DRX period.

In one embodiment, the first indication information may be indicated by a specific bit. For example, the bit value is 1, which is used to indicate the first indication information, that is, to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or to stop the operation of the onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame data. Otherwise, if the bit value is 0, the method is used for indicating the second indication information, that is, not stopping monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or indicating the terminal device not to stop the operation of the onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle do not belong to the same frame data.

In one embodiment, the first indication information or the second indication information may be carried in the PDCCH, or in DCI of the PDCCH. For example, if the first indication information is carried in the second PDCCH, the first data is data scheduled by the second PDCCH. That is, the network device may indicate to the terminal device that the data scheduled by the PDCCH and the data scheduled in the previous DRX cycle belong to the same frame of data by carrying the first indication information in the PDCCH.

In another embodiment, the first indication information or the second indication information may be carried in PDSCH, or in higher layer control signaling of PDSCH, for example, control Element (CE) of media access control (Medium Access Control, MAC) or radio resource control (Radio Resource Control, RRC) signaling, etc.

For example, if the first indication information is carried in the first PDSCH, the first data is data carried by the first PDSCH. That is, the network device may indicate to the terminal device that the data transmitted by the PDSCH and the data scheduled in the previous DRX cycle belong to the same frame of data by carrying the first indication information in the PDSCH.

According to the embodiment, the terminal equipment can determine whether to terminate monitoring of the PDCCH in advance when the current InactivityTimer is overtime based on the indication information from the network equipment, so that the purpose of saving power consumption of the terminal equipment is achieved, the problem of data transmission failure caused by stopping monitoring of the PDCCH in advance is avoided, and the data transmission efficiency is not influenced.

It will be appreciated that the same steps or messages having the same function in the embodiments of the present application may be referred to in the reference between the different embodiments.

Based on the above embodiments, the present application further provides a communication device, which may be a terminal device. The communication device has the function of implementing the terminal device in each of the possible embodiments described above. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

The embodiment of the present application further provides a communication device, as shown in fig. 14, where the communication device 1400 includes a transceiver module 1401 and a processing module 1402.

Wherein the transceiver module 1401 may be configured to receive a first PDCCH during a first DRX cycle.

The processing module 1402 may be configured to stop monitoring the physical downlink control channel PDCCH at a first time if the first condition is met. The first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH times out or a time after the inactivity timer InactivityTimer times out.

In one embodiment, the first condition comprises: at a second time, the first timer is not running or has timed out, where the second time is a time when the communication device 1400 receives the first PDCCH in the first DRX cycle, and a start time of the first timer is a start time or an end time of a duration onDuration of the second DRX cycle, or a time when the PDCCH is first received in the second DRX cycle; wherein the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle.

In one embodiment, the first condition comprises: at the beginning of the onDuration of the first DRX cycle, the incapacity timer is not running, and the communication device 1400 does not lose downlink control information DCI in a second DRX cycle, where the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.

In one embodiment, the first condition comprises: the communication apparatus 1400 receives first indication information from the network device in the first DRX cycle, where the first indication information is used to instruct the communication apparatus 1400 to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the communication apparatus 1400 to stop running the onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

In an embodiment, the processing module 1402 may be further configured to start the second timer at a start time or an end time of onDuration of the first DRX cycle, or at a time when the PDCCH is first received in the first DRX cycle.

The transceiver module 1401 is further configured to receive a third PDCCH in a third DRX cycle.

The processing module 1402 may be further configured to stop monitoring the physical downlink control channel PDCCH at a fourth time if the second timer is not running or has timed out at the third time. The third DRX cycle is a next DRX cycle adjacent to the first DRX cycle, the third time is a time of receiving the third PDCCH, the fourth time is a time of an inactivity timer triggered by the third PDCCH or a time after the inactivity timer times out, the second timer is a different timer from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In an embodiment, the processing module 1402 may be further configured to start the first timer after the first timer expires and when the PDCCH is first received in the onDuration of the first DRX cycle if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle.

In one embodiment, the first condition further comprises: the communication device 1400 is not running at the beginning of the onDuration of the first DRX cycle, the inactive timer.

In one embodiment, the processing module 1402 may be further configured to determine that DCI is lost in the second DRX cycle based on at least one of: the HARQ process number HPN, the new data indication NDI and the redundancy version RV received in the second DRX period; alternatively, the data allocation indicates a DAI.

Specifically, the communication apparatus 1400 may implement the functions of the terminal device in the foregoing possible embodiments, and specific reference may be made to the detailed descriptions in the foregoing method examples, which are not repeated herein.

In addition, the application also provides a communication device, which can be a network device. The communication apparatus has a function of implementing the network device in each of the possible embodiments described above. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, as shown in fig. 14, the communication device 1400 includes a transceiver module 1401 and a processing module 1402.

Wherein, the transceiver module 1401 is configured to send a first PDCCH to a terminal device in a first DRX cycle.

The processing module 1402 is configured to stop monitoring the physical downlink control channel PDCCH at a first time if the first condition is satisfied. The first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH times out or a time after the inactivity timer InactivityTimer times out.

In one embodiment, the first condition comprises: the communication apparatus 1400 sends, in the first DRX cycle, first indication information to the terminal device, where the first indication information is used to indicate that monitoring of the PDCCH is stopped when or after the inactivity timer times out, or indicate that the onDuration timer is stopped when or after the inactivity timer times out, or that the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

In one embodiment, the duration of the first timer is preconfigured or the duration of the first timer is configured by the communication device 1400.

In an embodiment, the processing module 1402 is further configured to start the second timer at a start time or an end time of onDuration of the first DRX cycle, or at a time when the PDCCH is first received in the first DRX cycle of the terminal device.

The transceiver module 1401 is further configured to send a third PDCCH to the terminal device in a third DRX cycle.

The processing module 1402 is further configured to stop monitoring the physical downlink control channel PDCCH at a fourth time if the second timer is not running or has timed out at the third time. The third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time when the terminal device receives the third PDCCH, the fourth time is a time when an inactive timer triggered by the third PDCCH times out or a time after the inactive timer times out, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

In an embodiment, the processing module 1402 is further configured to determine that the terminal device lost DCI in the second DRX cycle according to at least one of: the HARQ process number HPN, the new data indication NDI and the redundancy version RV in the second DRX period; alternatively, the data allocation indicates a DAI.

Specifically, the communication apparatus 1400 may implement the functions of the network device in the foregoing possible embodiments, and specific reference may be made to the detailed descriptions in the foregoing method examples, which are not repeated herein.

It will be appreciated that when the apparatus is an electronic device, as shown in fig. 2, the transmission module may be a transceiver, may include an antenna, a radio frequency circuit, etc., and the processing module may be a processor, such as a baseband chip, etc. When the apparatus is a component having the function of the first communication device and/or the second communication device in the above embodiments, the transmission module may be a radio frequency unit, and the processing module may be a processor. When the device is a chip system, the transmission module may be an input interface and/or an output interface of the chip system, and the processing module may be a processor of the chip system, for example: a central processing unit (central processing unit, CPU).

It should be noted that, the specific execution process and embodiment of the foregoing apparatus may refer to the steps and related descriptions executed by the terminal device or the network device in the foregoing method embodiment, and the solved technical problems and the technical effects brought by the solved technical problems may also refer to the descriptions in the foregoing embodiment, which are not repeated herein.

In this embodiment, the apparatus is presented in the form of dividing the individual functional modules in an integrated manner. A "module" herein may refer to a particular circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the functionality described above. In a simple embodiment, the person skilled in the art will appreciate that the transmission means of the side link may take the form shown in fig. 2 in the foregoing.

Illustratively, the functions/implementations of the processing module 1402 in FIG. 14 may be implemented by the processor 201 in FIG. 2 invoking computer program instructions stored in the memory 204. For example, the functionality/implementation of the transceiver module 1401 in fig. 14 may be through the communication interface 203 in fig. 2.

In some embodiments, the processor 201 in fig. 2 may implement the above-described possible implementation methods of the present application by invoking computer-executable instructions stored in the memory 204, so that the apparatus 200 may perform the operations of the terminal device or the network device in the above-described method embodiments.

The communication device in the above-described respective device embodiments may correspond exactly to the terminal equipment or the network equipment in the method embodiments, and the respective steps are performed by respective modules or units, for example, when the device is implemented in a chip, the transceiver unit may be an interface circuit of the chip for receiving signals from other chips or devices. The above transceiver module for transmitting or receiving is an interface circuit of the apparatus for transmitting signals to other apparatuses, and for example, when the apparatus is implemented in a chip form, the transceiver module may be an interface circuit for transmitting signals to other chips or apparatuses.

In an exemplary embodiment, a computer readable storage medium or a computer program product comprising instructions executable by the processor 201 of the communication device 200 to perform the method of the above-described embodiment is also provided. Therefore, reference may be made to the above method embodiments for the technical effects, which are not described herein.

The present application also provides a computer program product comprising instructions which, when executed, cause the computer to perform operations corresponding to the terminal device or network device, respectively, of the above method.

The embodiment of the application also provides a system chip, which comprises: a processing unit, which may be, for example, a processor, and a communication unit, which may be, for example, an input/output interface, pins or circuitry, etc. The processing unit may execute the computer instructions to cause the communication device to which the chip is applied to execute the operations of the terminal device and the network device in the method provided in the embodiments of the present application.

Alternatively, any one of the communication devices provided in the embodiments of the present application may include the system chip.

Optionally, the computer instructions are stored in a storage unit.

The embodiment of the application also provides a communication system, which may include: any of the above embodiments may be a terminal device and a network device.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.

Finally, it should be noted that: the foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of configuring discontinuous reception, the method comprising:

the terminal equipment receives a first PDCCH in a first DRX period;

if the first condition is met, the terminal equipment stops monitoring the physical downlink control channel PDCCH at a first moment;

the first time is a time when an inactivity timer InactivityTimer triggered by the first PDCCH overturns or a time after overtime;

The first condition includes:

at a second moment, a first timer is not running or has timed out, wherein the second moment is the moment when the terminal equipment receives the first PDCCH in the first DRX period, and the starting moment of the first timer is the starting moment or the ending moment of duration onDuration of the second DRX period, or the moment when the terminal equipment receives the PDCCH for the first time in the second DRX period; wherein the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle; or,

the InactivityTimer is not running in a first period, wherein the ending time of the first period is the starting time of the onDuration of a first DRX period; or,

at the initial moment of the onDuration of the first DRX cycle, the inactive timer is not running, and the terminal device does not lose downlink control information DCI in a second DRX cycle, where the second DRX cycle is a previous DRX cycle adjacent to the first DRX cycle; or,

the terminal device receives first indication information from the network device in the first DRX cycle, where the first indication information is used to instruct the terminal device to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the terminal device to stop running an onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

2. The method of claim 1, wherein the duration of the first period is a duration of the inactivity timer.

3. The method of claim 1, wherein the first data is data scheduled by a second PDCCH if the first indication information is carried in the second PDCCH; or,

and if the first indication information is carried in the first physical downlink shared channel PDSCH, the first data is the data carried by the first PDSCH.

4. The method of claim 1, wherein a duration of the first timer is preconfigured or wherein a duration of the first timer is configured by a network device.

5. The method according to claim 1 or 4, wherein,

the terminal equipment starts a second timer at the starting time or the ending time of the onDuration of the first DRX period or at the time of receiving the PDCCH for the first time in the first DRX period;

receiving a third PDCCH in a third DRX period;

if the second timer is not running or has timed out at the third moment, the terminal equipment stops monitoring the physical downlink control channel PDCCH at the fourth moment;

The third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time of receiving the third PDCCH, the fourth time is a time of an inactivity timer triggered by the third PDCCH or a time after the inactivity timer is overtime, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

6. The method according to claim 1, 4 or 5, wherein if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle, the terminal device starts the first timer after the first timer times out and the time when the PDCCH is first received in an onDuration of the first DRX cycle.

7. The method of claim 1 or 2, wherein the first condition further comprises: the terminal device is not running at the beginning moment of onDuration of the first DRX cycle, and the inactive timer is not running.

8. The method of claim 1, wherein the terminal device loses DCI within the second DRX cycle, determined from at least one of:

The HARQ process number HPN, the new data indication NDI and the redundancy version RV received in the second DRX period;

alternatively, the data allocation indicates a DAI.

9. The method according to any of claims 1-8, wherein the ceasing to monitor the physical downlink control channel, PDCCH, comprises: and stopping the running of the onDuration timer of the first DRX cycle.

10. A method of configuring discontinuous reception, the method comprising:

the network equipment sends a first PDCCH to the terminal equipment in a first DRX period;

if the first condition is met, stopping monitoring the physical downlink control channel PDCCH at a first moment;

the first condition includes:

the network device sends first indication information to the terminal device in the first DRX cycle, where the first indication information is used to instruct the terminal device to stop monitoring the PDCCH when the inactivity timer times out or after the inactivity timer times out, or instruct the terminal device to stop running an onDuration timer when the inactivity timer times out or after the inactivity timer times out, or the first data indicated by the first indication information and the data scheduled in the previous DRX cycle belong to the same frame of data.

11. The method of claim 10, wherein the duration of the first period is a duration of the inactivity timer.

12. The method of claim 10, wherein the first data is data scheduled by a second PDCCH if the first indication information is carried in the second PDCCH; or,

And if the first indication information is loaded in the first PDSCH, the first data is the data carried by the first PDSCH.

13. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

starting a second timer at a start time or an end time of an onDuration of the first DRX cycle, or at a time when a PDCCH is first received in the first DRX cycle of the terminal device;

transmitting a third PDCCH to the terminal equipment in a third DRX period;

if the second timer is not running or has timed out at the third moment, stopping monitoring the physical downlink control channel PDCCH at the fourth moment;

the third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is a time when the terminal device receives the third PDCCH, the fourth time is a time when an inactive timer triggered by the third PDCCH times out or a time after the inactive timer times out, the second timer is a timer different from the first timer, and a duration of the second timer is the same as a duration of the first timer.

14. The method according to claim 10 or 13, wherein if the starting time of the first timer is the time when the PDCCH is first received in the second DRX cycle, starting the first timer after the first timer expires and the time when the PDCCH is first received in an onDuration of the first DRX cycle.

15. The method of claim 10 or 11, wherein the first condition further comprises: the terminal device is not running at the beginning moment of onDuration of the first DRX cycle, and the inactive timer is not running.

16. The method of claim 10, wherein the terminal device loses DCI during the second DRX cycle, determined from at least one of:

the HARQ process number HPN, the new data indication NDI and the redundancy version RV in the second DRX period;

alternatively, the data allocation indicates a DAI.

17. A terminal device comprising a processor and a memory coupled to the processor; the memory stores computer program code comprising computer instructions which, when executed by the processor, cause the terminal device to perform the method of any of claims 1-9.

18. A network device comprising a processor and a memory coupled to the processor; the memory is coupled to the processor, the memory storing computer program code comprising computer instructions that, when executed by the processor, cause the network device to perform the method of any of claims 10-16.

19. A computer readable storage medium storing computer executable instructions which, when invoked by the computer, cause the computer to perform the method of any one of claims 1-9 or the method of any one of claims 10-16.

20. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-9 or to perform the method of any one of claims 10-16.

21. A chip, characterized in that the chip is coupled to a memory for reading and executing program instructions stored in the memory for implementing the method according to any of claims 1-9 or for implementing the method according to any of claims 10-16.

22. A communication system comprising a terminal device according to claim 17 and a network device according to claim 18.