WO2024001790A1 - 一种非连续接收的配置方法及装置 - Google Patents

一种非连续接收的配置方法及装置 Download PDF

Info

Publication number
WO2024001790A1
WO2024001790A1 PCT/CN2023/100245 CN2023100245W WO2024001790A1 WO 2024001790 A1 WO2024001790 A1 WO 2024001790A1 CN 2023100245 W CN2023100245 W CN 2023100245W WO 2024001790 A1 WO2024001790 A1 WO 2024001790A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx cycle
pdcch
timer
time
data
Prior art date
Application number
PCT/CN2023/100245
Other languages
English (en)
French (fr)
Inventor
薛祎凡
张彦清
秦熠
曹佑龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024001790A1 publication Critical patent/WO2024001790A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present application relates to the field of communication technology, and in particular, to a configuration method and device for discontinuous reception.
  • a discontinuous reception (DRX) mechanism is introduced to control the terminal equipment to monitor the physical downlink control channel (Physical Downlink Control). Channel, PDCCH) behavior.
  • the network device delivers DRX configuration to the terminal device, where the DRX configuration may include configuration information of the DRX cycle and duration onDuration, which is used to determine that the terminal device can continue to monitor the PDCCH to obtain scheduling information during the onDuration period of the DRX cycle. If the terminal device does not receive any scheduling information within the onDuration period, the terminal device enters the sleep state and stops monitoring the PDCCH to save power consumption.
  • the business characteristic is that data packets arrive It is periodic and has a short interval. For example, if an XR service transmits 60 frames of images per second, the average arrival time interval of two adjacent data packets is 16.67 milliseconds (ms) without considering the transmission delay.
  • XR extended reality
  • VR virtual reality
  • AR augmented reality
  • CG cloud gaming
  • jitter may occur in the actual arrival time of the data packet, such as a jitter delay of 0 ⁇ 8ms, and different data packets may have jitter Jitter delays of different lengths, for example, the time interval between data packet arrivals may be 16.67ms to 24.67ms.
  • the length of onDuraiton can be configured longer so that the length of onDuration is enough to cover the arrival time of the data packet. Possible time period.
  • the increase in the onDuration length of the DRX cycle will lead to an increase in the power consumption of the terminal. If the jitter delay is short and the actual arrival time of the data packet is earlier, invalid PDCCH monitoring will be performed during the onDuration period after the terminal completes the data transmission. As a result, the terminal The energy saving efficiency is low.
  • the present application provides a configuration method and device for discontinuous reception, which solves the problem in the prior art that the duration of terminal monitoring of the physical downlink control channel PDCCH is set to be long and the energy saving efficiency is low.
  • a first aspect provides a configuration method for discontinuous reception.
  • the method includes: a terminal device first The DRX cycle receives the first PDCCH; if the first condition is met, the terminal equipment stops monitoring the physical downlink control channel PDCCH at the first moment; wherein the first moment is the inactivity timer InactivityTimer triggered by the first PDCCH The time of timeout or the time after timeout.
  • the terminal equipment and the network equipment can stop monitoring the PDCCH synchronously according to the rule, thereby shortening the time for ineffectively monitoring the PDCCH in the DRX cycle to save power consumption.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the terminal device receives all the data in the first DRX cycle.
  • the time of the first PDCCH, the starting time of the first timer is the starting time or the end time of the duration onDuration of the second DRX cycle, or the time when the PDCCH is first received in the second DRX cycle ;
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first timer by configuring the first timer, it will be judged whether the first timer has timed out, as a judgment condition for the terminal device to determine whether the first PDCCH received belongs to the XR data frame of the current DRX cycle or the previous DRX cycle, thereby further Determine whether the InactivityTimer triggered by the first PDCCH can stop monitoring the PDCCH in advance when it times out, and shorten the time for ineffectively monitoring the PDCCH to save power consumption of the terminal equipment.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end moment of the first period is the start of onDuration of the first DRX cycle. time.
  • both the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer timeout is the current DRX cycle or the XR data frame arriving in the previous DRX based on whether the InactivityTimer is running during the first period, thereby determining whether it can Terminate the monitoring of PDCCH early to achieve the purpose of saving the power consumption of terminal equipment, avoid the problem of data transmission failure caused by stopping monitoring PDCCH prematurely, and do not affect the data transmission efficiency.
  • the terminal equipment side can also make the same judgment as the network equipment side to avoid the problem of data transmission failure.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the terminal device does not lose downlink control information DCI in the second DRX cycle. , wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • both the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer timeout is the XR data of the current DRX cycle or the previous DRX by determining whether packet loss occurs in the previous DRX cycle based on the first condition. frame, and then determine whether the monitoring of the PDCCH can be terminated early to achieve the purpose of saving power consumption of the terminal equipment, avoiding the problem of data transmission failure caused by prematurely stopping monitoring the PDCCH, and not affecting the data transmission efficiency.
  • the terminal device side can also make the same judgment as the network device side to avoid the problem of data transmission failure.
  • the first condition includes: the terminal device receives first indication information from the network device within the first DRX cycle, and the first indication information is used to instruct the terminal device to Stop monitoring the PDCCH when the InactivityTimer times out or after the timeout, or instruct the terminal device to stop the operation of the onDuration timer (also called onDurationTimer) when the InactivityTimer times out or after the timeout, or, the first indication information indicates One data belongs to the same frame data as the data that has been scheduled in the previous DRX cycle.
  • the onDuration timer also called onDurationTimer
  • the terminal device can determine whether the monitoring of the PDCCH can be terminated early when the current InactivityTimer times out based on the instruction information from the network device, so as to save the power consumption of the terminal device and avoid prematurely stopping monitoring the PDCCH resulting in data loss.
  • the problem of transmission failure does not affect the data transmission efficiency.
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by a network device.
  • the duration of the first timer is related to the PDB in which the application server transmits the data packet to the terminal device, or the PDB in which the application server transmits the data packet to the terminal device is related to the PDB in which the application server transmits the data packet to the terminal device.
  • the difference in PDB of the data packet transmitted by the access network device is related.
  • the duration of the first timer is related to the PDB in which the access network device transmits the data packet to the terminal device.
  • the terminal equipment starts the second timer at the starting time or the end time of onDuration of the first DRX cycle, or at the time when the PDCCH is first received in the first DRX cycle; in The third DRX cycle receives the third PDCCH; 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; wherein, the third timer is not running or has expired.
  • the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle, the third time is the time when the third PDCCH is received, and the fourth time is when the InactivityTimer triggered by the third PDCCH times out. time or a time after timeout, the second timer is a timer different from the first timer, and the duration of the second timer is the same as the duration of the first timer.
  • the starting time of the first timer is the time when the PDCCH is received for the first time in the second DRX cycle, then the terminal equipment after the first timer times out, and the The first timer is started when the PDCCH is first received within the onDuration of the first DRX cycle.
  • the first condition further includes: the InactivityTimer is not running at the starting moment of onDuration of the first DRX cycle of the terminal device.
  • the loss of DCI by the terminal device in the second DRX cycle is determined based on at least one of the following information: the HARQ process number HPN, new data indication NDI and redundancy version received in the second DRX cycle. RV; alternatively, data allocation indication DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • a discontinuous reception configuration method includes: the network device sends the first PDCCH to the terminal device in the first DRX cycle; if the first condition is met, stopping monitoring the physical downlink control channel at the first moment PDCCH; wherein the first time is the time when the inactivity timer InactivityTimer triggered by the first PDCCH times out or the time after timeout.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the terminal device receives all the data in the first DRX cycle.
  • the time of the first PDCCH, the starting time of the first timer is the starting time or the end time of the duration onDuration of the second DRX cycle, or the time when the PDCCH is first received in the second DRX cycle ;
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end time of the first period is the starting time of onDuration of the first DRX cycle.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the terminal device does not lose downlink control information DCI in the second DRX cycle. , wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the network device sends first indication information to the terminal device within the first DRX cycle, and the first indication information is used to indicate when or after the InactivityTimer times out. Stop monitoring the PDCCH, or instruct the onDuration timer to stop running when or after the InactivityTimer times out, or the first data indicated by the first indication information belongs to the same frame of data as the data that has been scheduled in the previous DRX cycle.
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by the network device.
  • the second timing is started at the start time or end time of onDuration of the first DRX cycle, or at the time when the terminal device first receives the PDCCH in the first DRX cycle.
  • the device sends a third PDCCH to the terminal equipment in the third DRX cycle; if at the third moment, the second timer is not running or has timed out, stop monitoring the physical downlink control channel PDCCH at the fourth moment; wherein , the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle, the third time is the time when the terminal equipment receives the third PDCCH, and the fourth time is the The time when the InactivityTimer triggered by the third PDCCH times out or the time after timeout, the second timer is a timer different from the first timer, and the duration of the second timer is the same as that of the first timer. The duration is the same.
  • the starting time of the first timer is the time when the PDCCH is received for the first time in the second DRX cycle, then after the first timer times out, and the first DRX The first timer is started when the PDCCH is first received within the onDuration of the cycle.
  • the first condition further includes: the InactivityTimer is not running at the starting moment of onDuration of the first DRX cycle of the terminal device.
  • the loss of DCI by the terminal device in the second DRX cycle is determined based on at least one of the following information: HARQ process number HPN, new data indication NDI and redundancy in the second DRX cycle. Rest version RV; alternatively, data allocation indication DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • a communication device in a third aspect, includes a transceiver module and a processing module.
  • the transceiver module is configured to receive the first PDCCH in the first DRX cycle; if the first condition is met, the processing module is configured to receive the first PDCCH in the first DRX cycle. Stop monitoring the physical downlink control channel PDCCH at any time; wherein the first time is the time when the inactivity timer InactivityTimer triggered by the first PDCCH times out or the time after timeout.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the communication device receives all the data in the first DRX cycle.
  • the time of the first PDCCH, the starting time of the first timer is the starting time or the end time of the duration onDuration of the second DRX cycle, or the time when the PDCCH is first received in the second DRX cycle ;
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end time of the first period is the starting time of onDuration of the first DRX cycle.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the communication device does not lose downlink control information DCI in the second DRX cycle. , wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the communication device receives first indication information from the network device within the first DRX cycle, and the first indication information is used to instruct the communication device to wait until the InactivityTimer expires. Stop monitoring the PDCCH every time or after a timeout, or instruct the communication device to stop the operation of the onDuration timer when the InactivityTimer times out or after a timeout, or the first data indicated by the first indication information is different from the one that has been used in the previous DRX cycle.
  • the scheduled data belongs to the same frame of data.
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by a network device.
  • the processing module is further configured to start the second DRX cycle at the starting time or end time of onDuration of the first DRX cycle, or at the time when the PDCCH is first received in the first DRX cycle. timer; the transceiver module is also used to receive the third PDCCH in the third DRX cycle; if at the third moment, the second timer is not running or has timed out, the processing module is also used to Stop monitoring the physical downlink control channel PDCCH at the fourth moment; wherein the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle, and the third moment is the moment when the third PDCCH is received, The fourth time is the time when the InactivityTimer triggered by the third PDCCH times out or the time after timeout, the second timer is a timer different from the first timer, and the duration of the second timer The same length as the first timer.
  • the processing module is also configured to wait until the first timer times out. Then, the first timer is started when the PDCCH is first received within onDuration of the first DRX cycle.
  • the first condition further includes: the InactivityTimer is not running at the start time of onDuration of the first DRX cycle of the communication device.
  • the processing module is further configured to determine that the DCI is lost in the second DRX cycle based on at least one of the following information: HARQ process number HPN, new data indication NDI received in the second DRX cycle and redundancy version RV; alternatively, data allocation indication DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • a communication device in a fourth aspect, includes a transceiver module and a processing module.
  • the transceiver module is configured to send the first PDCCH to the terminal equipment in the first DRX cycle; if the first condition is met, the processing module uses Stop monitoring the physical downlink control channel PDCCH at the first moment; wherein the first moment is the moment when the inactivity timer InactivityTimer triggered by the first PDCCH times out or the moment after timeout.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the terminal device receives all the data in the first DRX cycle.
  • the time of the first PDCCH, the starting time of the first timer is the starting time or the end time of the duration onDuration of the second DRX cycle, or the time when the PDCCH is first received in the second DRX cycle ;
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end time of the first period is the starting time of onDuration of the first DRX cycle.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the terminal device does not lose downlink control information DCI in the second DRX cycle. , wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the communication device sends first indication information to the terminal device within the first DRX cycle, and the first indication information is used to indicate when or after the InactivityTimer times out. Stop monitoring the PDCCH, or instruct the onDuration timer to stop running when or after the InactivityTimer times out, or the first data indicated by the first indication information belongs to the same frame of data as the data that has been scheduled in the previous DRX cycle.
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by the communication device.
  • the processing module is also configured to start the onDuration of the first DRX cycle.
  • the transceiver module is also configured to send a message to the terminal device in the third DRX cycle.
  • the terminal equipment sends the third PDCCH; if the second timer is not running or has timed out at the third moment, the processing module is also configured to stop monitoring the physical downlink control channel PDCCH at the fourth moment; wherein, The third DRX cycle is a subsequent DRX cycle adjacent to the first DRX cycle, the third time is the time when the terminal equipment receives the third PDCCH, and the fourth time is the third time.
  • the moment when the InactivityTimer triggered by PDCCH times out or the moment after timeout, the second timer is a timer different from the first timer, and the duration of the second timer is the same as the duration of the first timer. .
  • the starting time of the first timer is the time when the PDCCH is received for the first time in the second DRX cycle, then after the first timer times out, and the first DRX The first timer is started when the PDCCH is first received within the onDuration of the cycle.
  • the first condition further includes: the InactivityTimer is not running at the starting moment of onDuration of the first DRX cycle of the terminal device.
  • the processing module is further configured to determine that the terminal device has lost DCI in the second DRX cycle based on at least one of the following information: HARQ process number HPN in the second DRX cycle, new Data indicates NDI and redundancy version RV; alternatively, data allocation indicates DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • 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, and the one or more memories Used to store computer program code, the computer program code including computer instructions, when the one or more processors execute the computer instructions, causing the terminal device to perform the method described in any one of the above first aspects. method.
  • a sixth aspect provides a network device, including: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories Used to store computer program code, the computer program code including computer instructions, when the one or more processors execute the computer instructions, causing the network device to perform the method described in any one of the above second aspects. method.
  • a computer-readable storage medium is provided.
  • Computer-executable instructions are stored in the computer-readable storage medium.
  • the computer-executable instructions are used to cause the computer to execute the above-mentioned first step. The method of any one of the aspects.
  • a computer-readable storage medium is provided.
  • Computer-executable instructions are stored in the computer-readable storage medium. When called by the computer, the computer-executable instructions are used to cause the computer to execute the above-mentioned first step. The method described in any one of the two aspects.
  • a ninth aspect provides a computer program product containing instructions, which when the computer program product is run on a computer, causes the computer to perform the method described in any one of the above first aspects.
  • a tenth aspect provides a computer program product containing instructions, which when the computer program product is run on a computer, causes the computer to perform the method described in any one of the above second aspects.
  • a chip is provided, the chip is coupled with a memory, and is used for reading and executing the storage program instructions stored in the device to implement the method described in any one of the above first aspects.
  • a twelfth aspect provides a chip, which is coupled to a memory and used to read and execute program instructions stored in the memory to implement the method described in any one of the above second aspects.
  • a thirteenth aspect provides a communication system, which includes the communication device according to any one of the above third aspects and the communication device according to any one of the above fourth aspects.
  • any communication device, computer-readable storage medium, computer program product, chip or communication system provided above can be used to execute the corresponding method provided above. Therefore, the benefits it can achieve are For the effect, please refer to the beneficial effect in the corresponding method provided above, which will not be described again here.
  • Figure 1 is an architecture diagram of a communication system provided by an embodiment of the present application.
  • Figure 2 is an architecture diagram of a communication device provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of a discontinuous reception DRX configuration provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of discontinuous reception DRX configuration and data transmission provided by an embodiment of the present application
  • Figure 5 is a schematic flowchart of a discontinuous reception configuration method provided by an embodiment of the present application.
  • Figures 6 and 7 are schematic diagrams of data transmission considering transmission jitter provided by the embodiment of the present application.
  • Figure 8 is a schematic diagram of a PDB for downlink data transmission provided by an embodiment of the present application.
  • Figures 9 to 13 are schematic configuration diagrams of several discontinuous receptions provided by embodiments of the present application.
  • Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • first and second are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as “first” and “second” may explicitly or implicitly include one or more of these features. In the description of this embodiment, unless otherwise specified, “plurality” means two or more.
  • the communication system includes at least a terminal device 101 and a network device 102 .
  • the terminal device 101 involved in the embodiment of this application may be a user equipment (UE), where the UE includes a handheld device, a vehicle-mounted device, a wearable device or a computing device with wireless communication functions.
  • the UE may be a mobile phone, a tablet computer, or a computer with wireless transceiver functions.
  • the terminal device can also be a virtual reality (VR) terminal device, augmented reality (augmented reality, AR) terminal equipment, wireless terminals in industrial control, wireless terminals in driverless driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, smart Wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • the device used to implement the function of the terminal may be a terminal; it may also be a device that can support the terminal to implement the function, such as a chip system, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the network device 102 involved in the embodiment of this application may include a base station (BS), which may be a device deployed in a wireless access network and capable of wireless communication with terminals.
  • BS base station
  • base stations may come in many forms, such as macro base stations, micro base stations, relay stations, and access points.
  • the base station involved in the embodiments of this application may be a base station in 5G or a base station in LTE, where the base station in 5G may also be called a transmission reception point (transmission reception point, TRP) or gNB.
  • TRP transmission reception point
  • the device used to implement the function of the network device may be a network device; it may also be a device that can support the network device to implement the function, such as a chip system, and the device may be installed in the network device.
  • the device for realizing the functions of the network device is a network device, and the network device is a base station as an example to describe the technical solution provided by the embodiment of the present application.
  • wireless communication can also be referred to as “communication”
  • communication can also be described as “data transmission”, “information transmission” or “transmission”.
  • Figure 1 is only an exemplary framework diagram, and the number of network element nodes included in Figure 1 is not limited. In addition to the functional nodes shown in Figure 1, other nodes may also be included, such as core network equipment, gateway equipment, application servers, etc., without limitation. Access network equipment communicates with core network equipment through a wired network or wireless network, such as through a Next Generation (NG) interface.
  • NG Next Generation
  • each network element shown in Figure 1 may adopt the composition structure shown in Figure 2 or include the components shown in Figure 2.
  • Figure 2 is a schematic structural diagram of a communication device 200 provided by an embodiment of the present application.
  • the communication device 200 can be a terminal device or a chip in the terminal device. Or a system on a chip.
  • the communication device 200 may be a network device or a chip or a system-on-chip in the network device.
  • 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 can be a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a network processor (Network Processor, NP), a digital signal processor (Digital Signal Processing, DSP), a microprocessor, or a microcontroller. , programmable logic devices, or any combination thereof.
  • the processor 201 may also be other devices with processing functions, such as circuits, devices or software modules.
  • the communication line 202 is used to transmit information between various components included in the communication device 200 .
  • Communication interface 203 is used to communicate with other devices or other communication networks.
  • the other communication network may be Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.
  • the communication interface 203 may be an interface circuit, a pin, a radio frequency module, a transceiver, or any device capable of realizing communication.
  • Memory 204 is used to store instructions. Wherein, the instructions may be computer programs.
  • the memory 204 can be a read-only memory (Read-only Memory, ROM) or other types of static storage devices that can store static information and/or instructions, or it can be a random access memory (Random Access Memory, RAM) or other types of static storage devices that can store static information and/or instructions.
  • ROM read-only memory
  • RAM Random Access Memory
  • Other types of dynamic storage devices that store information and/or instructions can also be Electrically Erasable Programmable read-only Memory (EEPROM), Compact Cisc read-only Memory (CD- ROM) or other optical disk storage, optical disc storage, magnetic disk storage media or other magnetic storage devices.
  • Optical disc storage includes compressed optical discs, laser discs, optical discs, digital versatile discs, or Blu-ray discs, etc.
  • the memory 204 may exist independently of the processor 201 or may be integrated with the processor 201 .
  • the memory 204 can be used to store instructions or program codes or some data.
  • the memory 204 may be located within the communication device 200 or may be located outside the communication device 200, without limitation.
  • the processor 201 is configured to execute instructions stored in the memory 204 to implement the methods provided in the following embodiments of this application.
  • the processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 2 .
  • the communication device 200 includes multiple processors.
  • the processor 201 in FIG. 2 it may also include a processor 207.
  • the communication device 200 also includes an output device 205 and an input device 206.
  • the input device 206 is a device such as a keyboard, a mouse, a microphone, or a joystick
  • the output device 205 is a device such as a display screen, a speaker, or the like.
  • the communication device 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 with a similar structure as shown in FIG. 2 .
  • the composition structure shown in Figure 2 does not constitute a limitation of the communication device.
  • the communication device may include more or less components than shown in the figure, or combine certain components. , or a different component arrangement.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • DRX includes DRX long cycle and start offset (drx-LongCycleStartOffset). This parameter is used to configure the length of the long DRX cycle and the offset of the starting position of a DRX cycle (whether it is a long DRX cycle or a short DRX cycle). value.
  • the length of the long DRX cycle is in milliseconds (ms), and the configuration granularity of the starting offset is 1ms.
  • the DRX configuration information may also include the configuration information of the duration timer onDurationTimer, which is used to determine the period during which the terminal device continues to monitor the PDCCH from the starting position of the DRX cycle, that is, from the starting subframe indicated by drx-StartOffset. The number of consecutive subframes of PDCCH.
  • the DRX configuration information may also include configuration information of the inactivity timer InactivityTimer.
  • the DRX parameters also include the DRX slot offset value (drx-SlotOffset), which is used to configure Set the delay value before starting drx-onDurationTimer.
  • the configuration granularity is 1/32ms, and the value range is 0 ⁇ 31, that is, 0ms ⁇ 31/32ms.
  • the DRX parameters can also include short DRX, which is used to configure the length of the short DRX cycle.
  • the general process of DRX is as follows: After entering a DRX cycle, during the duration (on duration) period, the terminal equipment begins to continuously monitor the PDCCH. If the PDCCH is not detected within the duration period, the terminal device directly enters the sleep state after the duration period ends. If the PDCCH is monitored within the duration period and the PDCCH is used to schedule newly transmitted data (i.e., the PDCCH is used to transmit the scheduling information of the initial transmission schedule), then the terminal device receives the data according to the received scheduling information (i.e. Receive PDSCH) and start the DRX inactivation timer. Whenever the terminal equipment detects the scheduling information of the initial transmission schedule, the DRX inactivation timer is started (or restarted) once.
  • the received scheduling information i.e. Receive PDSCH
  • the terminal equipment is in the DRX inactivation timer period. , continue to monitor the PDCCH until the DRX inactivation timer times out (expire), and the terminal device enters the sleep state.
  • DRX configuration information can also include parameters such as DRX hybrid auto repeat request round trip timer (drx-hybrid auto repeat request round trip timer, drx-HARQ-RTT-Timer), DRX retransmission timer (drx-RetransmissionTimer).
  • the terminal equipment needs to be started during the DRX duration timer, DRX inactivation timer, downlink (DL) DRX retransmission timer and uplink (uplink, UL) DRX retransmission timer.
  • Monitor PDCCH these times are also collectively called activation time (Active Time).
  • the remaining time is collectively referred to as outside Active Time.
  • Outside the activation time the terminal device does not need to monitor the PDCCH. At this time, the terminal device can enter the sleep state to save power consumption.
  • the average arrival time interval of data packets corresponding to two adjacent frames of images is 16.67ms.
  • the ideal arrival time interval of XR data frames on the terminal device side can be 16.67ms.
  • the data frame is defined from the perspective of the application layer, and a data frame can also be replaced by a video frame.
  • a protocol data unit set (PDU set) includes business data in a frame (frame) data frame.
  • PDU set is defined from the MAC layer perspective.
  • a data frame can also be replaced by a PDU set.
  • the service data is an XR data frame as an example, but the following method is also applicable to other business scenarios without limitation.
  • the network device can configure the DRX cycle length for the terminal device that is closer to the arrival time interval of the Time matching or approximate matching.
  • the DRX cycle length matches the cycle length of the XR data frame.
  • the actual arrival time of the XR data frame may appear jitter.
  • the jitter duration may be 0 to 8 ms.
  • the actual arrival time of the XR data frame may be delayed by 0 to 8ms, which makes the arrival time interval of the XR data frame fluctuate between 16.67ms and 24.67ms.
  • the actual arrival position of the XR data frame may fall outside onDuration.
  • the terminal device since the terminal device does not receive scheduling within onDuration, it will no longer monitor the PDCCH after onDuration ends, and the base station can only delay the XR data frame for scheduling in the next DRX cycle. This situation will increase the data transmission delay.
  • the duration range of jitter is 0 ⁇ 8ms, which can be equivalently described as the range of jitter is - 4ms ⁇ 4ms, the reference points are different in the two description methods, but the physical meaning is the same.
  • the onDuration period in the DRX cycle can be configured to be longer to solve the problem of delayed arrival of XR data frames due to jitter, that is, the data arrival time should be within the onDuration period as much as possible. For example, configure the length of onDuraiton to cover the possible delay range of jitter, so that the length of onDuration is enough to cover all possible time periods for the arrival of the XR data frame.
  • the DRX duration configuration is too long, the activation time of the terminal device will be too long.
  • the terminal device monitors the initial transmission of PDCCH, it will also start the InactivityTimer to extend the activation time. At the same time, the transmission time of each XR data frame may be shorter. , In this way, the terminal equipment will perform ineffective PDCCH monitoring during most of the activation time (that is, it monitors the PDCCH but does not receive data scheduling), making it difficult to achieve energy saving effects.
  • Embodiments of the present application provide a discontinuous reception configuration method. By configuring some rules for the terminal equipment to stop monitoring the PDCCH, the terminal equipment can shorten the time for ineffectively monitoring the PDCCH and save power consumption for the terminal equipment. As shown in Figure 5, the method may include:
  • S501 The network device sends the first PDCCH to the terminal device.
  • the same network device may be used to schedule data for multiple terminal devices, and the sizes of XR data frames and XR data frame scheduling periods of multiple terminal devices may be different. Therefore, the DRX configuration configured by the network device for the terminal devices is also different. Therefore, the network device side will maintain its corresponding DRX configuration based on different terminal devices, and maintain and update various DRX-related timer operations corresponding to the terminal device. For example, based on the DRX configuration of the first terminal, the network device side determines the starting time of each DRX cycle corresponding to the first terminal, the starting time of the duration onDuration of the DRX cycle, and starts the inactivity timer InactivityTimer, etc., thereby communicating with the first terminal. The first terminal side maintains the same DRX configuration to synchronize data scheduling, etc., to improve communication efficiency.
  • the network device may send the first PDCCH to the terminal device in the first DRX cycle, where the first PDCCH is the scheduling data of the terminal device in the first DRX cycle.
  • the terminal equipment receives the first PDCCH in the first DRX cycle.
  • the terminal device receives the first PDCCH from the network device in the first DRX cycle.
  • the embodiment of the present application can define the rules for the terminal equipment to stop monitoring the PDCCH, so that the terminal equipment can stop monitoring the PDCCH according to the rules, shorten the time of invalid PDCCH monitoring, and save power. Consumption.
  • the network device may also determine that the terminal device stops monitoring the PDCCH based on the same judgment rules as the terminal device. Therefore, the network equipment can align the monitoring period of PDCCH with the terminal equipment, avoid packet loss or invalid PDCCH monitoring, and improve communication efficiency and energy saving efficiency.
  • the rule for stopping monitoring the PDCCH may be: the terminal device determines to stop monitoring the PDCCH after the InactivityTimer triggered by the first PDCCH times out, or stops monitoring the PDCCH when the InactivityTimer times out.
  • the terminal equipment can stop monitoring the PDCCH at the moment before the end of onDuration in the DRX cycle. That is, the terminal equipment can determine to stop monitoring the PDCCH before the end of onDuration according to the predefined rules and enter the sleep state in advance.
  • the terminal device may receive the first PDCCH within the onDuration of the DRX cycle, and start the InactivityTimer at the moment when the first PDCCH is received.
  • the terminal device determines that the InactivityTimer has timed out, it stops monitoring the PDCCH. That is, the terminal device no longer monitors the PDCCH in the subsequent period of the original onDuration and enters the sleep state in advance, shortening the duration of continuous monitoring of the PDCCH.
  • one XR data frame of the terminal device can also be divided into multiple protocol data units (Protocol Data Unit, PDU) for delivery respectively, in the same DRX cycle
  • PDU Protocol Data Unit
  • the XR data frame in the PDU is divided into the first PDU, the second PDU and the third PDU and are delivered respectively, and each PDU corresponds to a PDCCH for scheduling data.
  • the terminal equipment receives the first PDCCH, the second PDCCH, the third PDCCH, etc. within one DRX cycle.
  • each PDCCH includes downlink control information (Downlink control information, DCI) for scheduling a PDU.
  • DCI downlink control information
  • each PDCCH that schedules new data transmission will trigger the start or restart of the inactivity timer InactivityTimer, extending the time for monitoring the PDCCH.
  • the data transmission lasts for a long time, and the running time of the InactivityTimer may continue until the next DRX cycle, for example, as shown in Figure 7, the second DRX cycle
  • the running time of InactivityTimer overlaps with the onDuration of the next adjacent DRX cycle (the first DRX cycle).
  • the terminal equipment stops monitoring the PDCCH after the InactivityTimer times out, as shown in Figure 7, the terminal equipment stops monitoring the PDCCH early during the onDuration period of the first DRX cycle, resulting in the terminal equipment being unable to monitor the XR corresponding to the first DRX cycle.
  • Data frame scheduling information PDCCH PDCCH.
  • the PDCCH corresponding to the first DRX represents the PDCCH corresponding to the XR data frame arriving in the first DRX cycle
  • the PDCCH corresponding to the second DRX represents the PDCCH corresponding to the XR data frame arriving in the second DRX cycle.
  • the XR data frame arriving in the second DRX cycle is divided into 5 transmissions, so there are 5 PDCCHs corresponding to the second DRX in Figure 7.
  • the terminal equipment cannot know whether the XR data frame received in a DRX cycle is the XR data frame corresponding to the current cycle or part of the XR data frame corresponding to the previous cycle, it stops monitoring the PDCCH out of the need to save energy. Cause data reception failure or increase transmission delay.
  • the technical solution proposed by the embodiment of the present application optimizes the rules for terminal equipment to stop monitoring PDCCH by combining the higher delay requirements of XR services and the XR data frame dropping (packet dropping) function of network equipment, thereby This enables the network equipment and terminal equipment side to determine whether the PDCCH whose current InactivityTimer times out is the XR data frame of the current DRX cycle or the previous DRX based on certain judgment conditions, thereby determining whether the monitoring of the PDCCH can be terminated in advance to achieve savings.
  • Terminal equipment The purpose is to reduce power consumption without affecting data transmission efficiency.
  • XR services have higher latency requirements.
  • the XR data frame transmission delay exceeds the preset standard, it may cause problems such as freezes in the real-time video screen and unsmooth display, affecting the user experience.
  • the delay requirements can be specifically reflected in the packet delay budget (PDB).
  • PDB packet delay budget
  • downlink data packets are transmitted from the application server to the terminal device through Internet transmission (the application server sends data packets to the core network device) and core network transmission (the core network device sends data packets to the access network device). ), access network transmission (the access network device sends data packets to the terminal device), the PDB can be divided into end-to-end PDB and air interface PDB.
  • the end-to-end PDB of the downlink data packet refers to, in order to meet the business requirements, the maximum allowed length of time between the time when the application server sends the data packet and the time when the terminal device receives the data packet. For example, if the end-to-end PDB of a certain service is 100ms, if the downlink data packet can be transmitted from the application server to the terminal device within 100ms, it can be considered to meet the transmission requirements of the service; if the downlink data packet can be transmitted from the application server to the terminal If the transmission time of the device exceeds 100ms, it can be considered that the transmission requirements of the service are not met.
  • the air interface PDB of the downlink data packet refers to the maximum allowed time for the data packet to complete transmission from the access network device to the terminal device. For example, if the air interface PDB of a certain service is 10ms, if the downlink data packet can be transmitted from the base station to the terminal device within 10ms, it can be considered that the transmission requirements of the service are met.
  • the network device can enable the packet dropping function, that is, the network device can no longer schedule and transmit data packets that exceed the PDB according to the PDB requirements of the XR service.
  • the transmission time of an XR data frame exceeds the corresponding PDB, it means that when the XR data frame is sent to the terminal device, the image display time of the XR data frame has passed, then there is no need to transmit the XR data frame.
  • the network device can discard such XR data frames and no longer send them to the terminal device.
  • the first condition in the above step S503 may specifically include: at the second moment, the first timer is not running or has timed out, wherein the second moment may be when the terminal device is in The time when the first PDCCH is received in the first DRX cycle.
  • the terminal device by configuring the first timer, it will be judged whether the first timer times out, which is used as a judgment condition for the terminal device to determine whether the first PDCCH received belongs to the XR data frame of the current DRX cycle or the previous DRX cycle.
  • the starting time of the first timer may be the starting time of onDuration, the duration of the second DRX cycle, that is, it is started at the same time as the starting time of onDuration of the second DRX cycle.
  • the first PDCCH is considered to be the scheduling information of the first DRX cycle, and the first PDCCH triggers When the InactivityTimer times out, you can stop monitoring the PDCCH and terminate the monitoring of the PDCCH early to save power consumption.
  • the stopping of monitoring the PDCCH may specifically include: stopping the operation of the onDuration timer of the DRX cycle. As shown in the example in Figure 9, the onDuration timer of the first DRX cycle is stopped from running.
  • 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, that is, related to the PDB in which the application server transmits the XR data frame to the terminal device.
  • the duration of the first timer can also be the difference between the following two items: based on the end-to-end PDB, application server —The average transmission time of access network equipment. For example, as shown in Figure 8, the end-to-end PDB is T1, and the average transmission duration between the server and the access network device is T2. Then the duration of the first timer can be set to the difference between T1 and T2.
  • the starting time of the first timer may also be the ending time of the second DRX cycle onDuration.
  • the first timer can be started at the end of onDuration.
  • the terminal equipment receives the first PDCCH at the second moment in the first DRX cycle, and the first timer is running at the second moment, it is considered that the first PDCCH may be the previous one in the first DRX cycle.
  • the scheduling information of the XR data frame arriving within the DRX cycle is the scheduling information of the second DRX cycle.
  • the first PDCCH is the scheduling information of the XR data frame arriving within the first DRX cycle, and the InactivityTimer triggered by the first PDCCH When timeout occurs, you can stop monitoring PDCCH and terminate monitoring PDCCH early.
  • the duration of the first timer may be related to the end-to-end PDB, that is, related to the PDB in which the application server transmits the XR data frame 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 fixed value, then the first The duration of the timer may also be related to the difference between the PDB transmitted by the application server and the terminal device and the aforementioned fixed value.
  • the end-to-end PDB is T1
  • the average transmission duration from the server to the access network device is T2
  • the onDuration duration of the DRX cycle is T3
  • the duration of the first timer can be set to T1-T2- The difference obtained by T3.
  • the first timer is started at the onDuration start time or end time of a DRX cycle
  • the first timer corresponding to the DRX cycle may be different from the adjacent next DRX cycle.
  • the first timer of the second DRX cycle may coincide with the onDuration of the first DRX cycle, and the start or end time of onDuration of the first DRX cycle needs to start another first timer (or name it differently). timer). Therefore, at the same time, more than one first timer that meets the aforementioned functions may be running.
  • the method further includes the following steps.
  • Step 1 Start the second timer at the start time or end time of onDuration of the first DRX cycle.
  • Step 2 The terminal equipment receives the third PDCCH at the third time of the third DRX cycle.
  • Step 3 If the second timer is not running or has timed out at the third moment, stop monitoring the physical downlink control channel PDCCH at the fourth moment.
  • the fourth time is the time when the InactivityTimer triggered by the third PDCCH times out or the time after timeout.
  • the third DRX cycle is a DRX cycle adjacent to the first DRX cycle, the second timer and the first timer are timers with the same function, and the second timer and the first timer have the same duration.
  • the first timer is started at the starting position of the second DRX cycle, and the first timer has not finished running.
  • another timer that is, the second timer
  • the terminal device or network device may determine that the second timer is not running at the third moment when the third PDCCH is received. Therefore, at the fourth moment when the InactivityTimer times out, the monitoring of the PDCCH may be stopped to save power consumption on the terminal device side.
  • the starting time of the first timer included in the above first condition may also be the time when the terminal equipment first receives the PDCCH in the DRX cycle. That is, the first timer is started when the PDCCH is received for the first time in a certain DRX cycle.
  • the duration of the first timer may be related to the PDB in which the access network device transmits the XR data frame to the terminal device.
  • the air interface PDB between the access network device and the terminal device is T4, and the duration of the first timer can be set to T4.
  • the terminal device receives the
  • the first timer is started. If the terminal equipment receives PDCCH-1 in the first DRX cycle, and the time of receiving PDCCH-1 is within the running time of the first timer, the InactivityTime timeout triggered by the PDCCH-1 will not trigger the onDuration advance of the first DRX cycle. Terminate, that is, the PDCCH is still monitored after the InactivityTimer times out but before the OnDurationTimer times out.
  • the terminal equipment starts the first timer when it first receives PDCCH in the first DRX cycle
  • the terminal equipment receives PDCCH-2 in the third DRX cycle
  • receives PDCCH- 2 is after the timer times out
  • the InactivityTimer triggered by PDCCH-2 will trigger the third DRX
  • the onDuration of the cycle is terminated early, that is, PDCCH monitoring ends early to save the power consumption of the terminal equipment.
  • the terminal equipment starts the second DRX cycle at the time when the PDCCH is first received in the second DRX cycle.
  • the first timer is started (or restarted).
  • the first timer can be started (or restarted).
  • the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle.
  • both the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer timeout is the XR of the current DRX cycle based on whether the first timer is running or has timed out as a judgment condition.
  • the data frame is still the XR data frame of the previous DRX, thereby determining whether the monitoring of PDCCH can be terminated early to achieve the purpose of saving power consumption of the terminal equipment, avoiding the problem of data transmission failure caused by stopping monitoring PDCCH prematurely, and not affecting the data transmission efficiency.
  • the terminal equipment side can also make the same judgment as the network equipment side, improving the robustness of the overall solution.
  • the first condition in step S503 may specifically include: the inactivity timer InactivityTimer is not running within the first period.
  • the end time of the first period is the start time of onDuration of the first DRX cycle.
  • the duration of the first period may be predefined or configured for the network device.
  • the terminal equipment or network equipment can determine that within the first period of a certain length of time from the starting time of onDuration of the first DRX cycle, if the InactivityTimer is not running, it means that the scheduling information carried by the first PDCCH is large.
  • the probability is the scheduling information of the XR data frame arriving in the first DRX cycle, not the scheduling information of the XR data frame arriving in the previous DRX cycle, so the InactivityTimer triggered by the first PDCCH times out or after it times out (that is, the first DRX cycle
  • the XR data frame arriving within the first period has completed transmission
  • the PDCCH will not stop monitoring in advance, but will continue to monitor the PDCCH to receive the scheduling information of the subsequent XR data frames arriving in the first DRX cycle.
  • the above solution is to take into account that the XR data frames arriving in the previous DRX cycle may contain XR data frames whose transmission is completed later. Therefore, if it is judged that the XR data frames arriving in the previous DRX cycle are near the next DRX cycle, It is still transmitting at the moment, that is, it is still possible to transmit within the preset time period before the onDuration start time of the next DRX cycle (that is, the length of the aforementioned first period), then it is determined not to stop monitoring the PDCCH in the next DRX cycle in advance.
  • 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 the value of some configuration parameters (such as the length of InactivityTimer); Alternatively, the duration of the first period may be configured by the network device. For example, it may be carried when the network device delivers the DRX configuration information to the terminal device. This application does not limit the specific configuration method.
  • the duration of the first period may be the duration of InactivityTimer.
  • the PDCCH can be stopped monitoring when or after the InactivityTimer triggered by the first PDCCH times out; if the InactivityTimer is running, Then the PDCCH monitoring is not stopped in advance, that is, after the InactivityTimer triggered by the first PDCCH times out, the PDCCH is still monitored before the OnDurationTimer times out.
  • the first condition may specifically include: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running.
  • the terminal device or the network device can determine that: if the InactivityTimer is not running at the starting time of onDuration of the first DRX cycle, it can be triggered when or after the InactivityTimer times out (the first PDCCH received in the first DRX cycle ), stop monitoring PDCCH. On the contrary, if the InactivityTimer is running at the starting moment of onDuration of the first DRX cycle, you can not stop monitoring the PDCCH when or after the InactivityTimer times out (triggered by the first PDCCH received in the first DRX cycle), that is, the InactivityTimer times out. The PDCCH is still monitored before OnDurationTimer times out.
  • the InactivityTimer running status of the terminal device and the network device side will be misaligned, as shown in Figure 12.
  • the terminal equipment receives PDCCH-2 in the first DRX cycle, and the InactivityTimer triggered by PDCCH-2 overlaps with the onDuration of the first DRX cycle.
  • the network device determines not to stop monitoring the PDCCH by judging that the InactivityTimer at the onDuration starting time of the first DRX cycle is running; and the terminal device determines that the onDuration starting time InactivityTimer of the first DRX cycle is not running. While running, it is determined to stop monitoring the PDCCH, resulting in misalignment between the terminal equipment and the network equipment, which may cause the transmission of the XR data frame arriving in the first DRX cycle to fail.
  • the two aforementioned first conditions can be combined. That is to say, the terminal device or network device can determine the starting time of onDuration of the first DRX cycle and the InactivityTimer is not running; and, the first DRX cycle If the InactivityTimer is not running during the InactivityTimer before the onDuration start time, then the PDCCH can be stopped monitoring when or after the InactivityTimer triggered by the first PDCCH times out. Otherwise, the monitoring of PDCCH is not stopped, and PDCCH is still monitored after InactivityTimer times out and before OnDurationTimer times out.
  • the time when InactivityTimer times out is T1
  • the starting time of onDuration in the first DRX cycle is T2. If T2-T1 ⁇ InactivityTimer duration, determine the time when InactivityTimer times out in the first DRX cycle or After timeout, do not stop monitoring PDCCH, or do not stop the onDuration timer in advance.
  • the InactivityTimer of the first DRX cycle stops early enough, even if the terminal equipment loses the PDCCH, the InactivityTimer triggered by the lost PDCCH will not coincide with the onDuration of the first DRX cycle. Therefore, the starting time of the onDuration of the first DRX cycle can be determined. If the InactivityTimer is running; or at any time within the duration of the InactivityTimer before the starting time of the onDuration of the first DRX cycle, the InactivityTimer is in the running state, then the terminal device is in the running state. Monitoring of PDCCH will not be stopped in advance during a DRX cycle.
  • both the network device and the terminal device can determine whether the PDCCH corresponding to the current InactivityTimer timeout is an XR data frame arriving in the current DRX cycle or an XR data frame arriving in the previous DRX based on the first condition, thereby determining Whether it is possible to terminate the monitoring of PDCCH early to achieve the purpose of saving the power consumption of the terminal equipment and avoid the problem of data transmission failure caused by stopping monitoring PDCCH prematurely without affecting the data transmission efficiency.
  • the terminal equipment side can also make the same judgment as the network equipment side to avoid the problem of data transmission failure.
  • the first condition in the above step S503 may specifically include: at the starting moment of 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.
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the InactivityTimer can be reset when or after the InactivityTimer times out (within the first DRX cycle). triggered by the first PDCCH received), stop monitoring the PDCCH.
  • the terminal device can receive a hybrid automatic repeat request (HARQ) process number (HARQ process number, HPN) and a new data indicator (new data indicator, NDI) according to a certain DRX cycle. and redundancy version (RV) to determine whether DCI is lost within this DRX cycle.
  • HARQ process number HARQ process number, HPN
  • NDI new data indicator
  • RV redundancy version
  • the terminal device can also determine whether the DCI is lost within a certain DRX cycle based on the data assignment indication (DAI).
  • DAI data assignment indication
  • HPN is used to indicate the process number of the HARQ process.
  • NDI is used to indicate whether data is initially transmitted or retransmitted. Specifically, whether the current data is newly transmitted or retransmitted can be determined by whether the NDI parameter is toggled.
  • NDI reversal 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 parameters in the DCI allocated by the base station for an uplink HARQ process are reversed compared to the last time, it means that the terminal device can perform new uplink transmission this time; if the NDI parameters are the same as last time, then the terminal device Uplink adaptive retransmission can be performed this time.
  • RV is designed to implement incremental redundancy (IR) HARQ transmission, which divides the redundant bits generated by the encoder into several groups.
  • IR incremental redundancy
  • Each RV defines a transmission starting point, which is used separately for the first transmission and each HARQ retransmission.
  • determining whether the DCI is lost based on the HPN, NDI and RV fields carried in the DCI specifically includes: if the NDI corresponding to the same HPN is inverted and RV>0, it is determined that the DCI is lost within the DRX cycle.
  • HARQ feedback uses a dynamic codebook
  • the terminal device when the terminal device feeds back HARQ-acknowledgement (ACK) information, it can use multiple physical downlink shared channels (PDSCH) corresponding HARQ-ACK
  • PDSCH physical downlink shared channels
  • the information is carried in the same information (such as DCI) for feedback, that is, the number of HARQ-ACK information and the order of multiple HARQ-ACKs can be designed through the HARQ-ACK codebook.
  • the downlink control information (DCI) received by the terminal device includes a data assignment indication (data assignment indication, DAI) field.
  • the DAI field indicates the number of scheduled data packets (ie, PDSCH). This field can be understood as a counter.
  • the DAI count result indicates the number of bits in the HARQ-ACK codebook. For example, the HARQ-ACK information of three time slots needs to be fed back in the same time slot.
  • the DAI field in the DCI of each time slot indicates 1/2/3 respectively.
  • the terminal device can determine that the number of bits in the feedback HARQ-ACK codebook is 3.
  • the DAI field can be further divided into count DAI (counter DAI) and total DAI (total DAI).
  • the function of counter DAI is consistent with the DAI introduced earlier, that is, it is used to indicate that the current schedule is before a feedback
  • total DAI is used to indicate how many data packets (or PDSCHs) are scheduled before a feedback. Usually before a feedback, the value of total DAI contained in the DCI of each scheduling data is the same.
  • the size of the HARQ-ACK codebook can be determined based on the value indicated by 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, it is determined that the DCI is lost.
  • both 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 cycle or the previous DRX by determining whether packet loss occurs in the previous DRX cycle based on the first condition. XR data frame, and then determine whether the monitoring of PDCCH can be terminated early to achieve the purpose of saving power consumption of the terminal equipment, avoiding the problem of data transmission failure caused by stopping monitoring PDCCH prematurely, and does not affect the data transmission efficiency.
  • the terminal device side can also make the same judgment as the network device side to avoid the problem of data transmission failure.
  • the network device since the network device knows the XR data frame arriving in which DRX cycle the XR data frame belongs to when sending the XR data frame to the terminal device, the network device can send an instruction to the terminal device through the network device, using It is used to indicate whether it is possible to stop monitoring PDCCH or stop running the onDuration timer after the InactivityTimer times out, or to indicate whether the currently scheduled or transmitted XR data frame is the same frame of data that has been scheduled in the previous DRX cycle.
  • the first condition in step S503 may specifically include: the network device sends first indication information to the terminal device within the first DRX cycle, where the first indication information may be used to instruct the terminal device in
  • the data belongs to the same frame of data.
  • the terminal device receives the first indication information from the network device in the first DRX cycle.
  • the first indication information may be indicated through a specific bit.
  • the value of this bit is 1, which is used to indicate the first indication information, that is, to stop monitoring the PDCCH when the InactivityTimer times out or after the timeout, or to instruct the terminal device to stop the operation of the onDuration timer when the InactivityTimer times out or after the timeout, or,
  • the first data indicated by the first indication information and the data that has been scheduled in the previous DRX cycle belong to the same frame data.
  • the bit value is 0, it is used to indicate the second indication information, that is, not to stop monitoring the PDCCH when the InactivityTimer times out or after the timeout, or to instruct the terminal device not to stop the running of the onDuration timer when the InactivityTimer times out or after the timeout. , or the first data indicated by the first indication information does not belong to the same frame data as the data that has been scheduled in the previous DRX cycle.
  • the first indication information or the second indication information may be carried in the PDCCH, or in the DCI of the PDCCH.
  • the first indication information is carried in the second PDCCH
  • the first data is data scheduled by the second PDCCH. That is to say, the network device may carry the first indication information in the PDCCH to indicate to the terminal device that the data scheduled by the PDCCH and the data that has been scheduled in the previous DRX cycle belong to the same frame of data.
  • the first indication information or the second indication information may be carried in the PDSCH, or in the high-level control signaling of the PDSCH, such as the control unit (control unit) of the Medium Access Control (Medium Access Control, MAC). element, CE) or Radio Resource Control (Radio Resource Control, RRC) signaling, etc.
  • control unit control unit of the Medium Access Control (Medium Access Control, MAC). element, CE) or Radio Resource Control (Radio Resource Control, RRC) signaling, etc.
  • CE Medium Access Control
  • RRC Radio Resource Control
  • the first data is the data carried by the first PDSCH. That is to say, the network device may carry the first indication information in the PDSCH to indicate to the terminal device that the data transmitted by the PDSCH and the data that has been scheduled in the previous DRX cycle belong to the same frame of data.
  • the terminal device can determine whether the monitoring of the PDCCH can be terminated early when the current InactivityTimer times out based on the instruction information from the network device, so as to achieve the purpose of saving the power consumption of the terminal device and avoid prematurely stopping monitoring the PDCCH causing data transmission failure.
  • the problem does not affect the data transmission efficiency.
  • this application also provides a communication device, which may be a terminal device.
  • the communication device has the function of realizing the terminal equipment in each of the above possible implementations.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication device 1400 includes a transceiver module 1401 and a processing module 1402.
  • the transceiver module 1401 may be used to receive the first PDCCH in the first DRX cycle.
  • the processing module 1402 may be configured to, if the first condition is met, stop monitoring the physical downlink control channel PDCCH at the first moment.
  • the first time is the time when the inactivity timer InactivityTimer triggered by the first PDCCH times out or the time after timeout.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the communication device 1400 receives the signal within the first DRX cycle.
  • the moment of the first PDCCH, the starting moment of the first timer is the starting moment or the end moment of the duration onDuration of the second DRX cycle, or the first time the PDCCH is received in the second DRX cycle. hour moment; wherein, the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end time of the first period is the starting time of onDuration of the first DRX cycle.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the communication device 1400 does not lose downlink control information in the second DRX cycle.
  • DCI wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the communication device 1400 receives first indication information from a network device within the first DRX cycle, and the first indication information is used to instruct the communication device 1400 to Stop monitoring the PDCCH when the InactivityTimer times out or after the timeout, or instruct the communication device 1400 to stop the operation of the onDuration timer when the InactivityTimer times out or after the timeout, or the first data indicated by the first indication information is different from the previous DRX cycle.
  • the data that has been scheduled within belongs to the same frame of data.
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by a network device.
  • the processing module 1402 may also be configured to start at the starting time or end time of onDuration of the first DRX cycle, or at the time when the PDCCH is first received in the first DRX cycle. Second timer.
  • the transceiver module 1401 is also used to receive the third PDCCH in the third DRX cycle.
  • the processing module 1402 may also be configured to stop monitoring the physical downlink control channel PDCCH at the fourth moment if the second timer is not running or has timed out at the third moment.
  • the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle
  • the third time is the time when the third PDCCH is received
  • the fourth time is the time when the InactivityTimer triggered by the third PDCCH times out or times out.
  • the second timer is a timer different from the first timer, and the duration of the second timer is the same as the duration of the first timer.
  • the processing module 1402 may also be configured to: 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 first timer is started when the PDCCH is first received within the onDuration of the first DRX cycle.
  • the first condition further includes: the InactivityTimer is not running at the starting moment of onDuration of the first DRX cycle of the communication device 1400 .
  • the processing module 1402 may also be configured to determine that the DCI is lost in the second DRX cycle based on at least one of the following information: HARQ process number HPN, new data received in the second DRX cycle Indicates NDI and redundancy version RV; alternatively, data allocation indicates DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • the communication device 1400 can implement the functions of the terminal device in each of the above possible implementations.
  • the functions of the terminal device in each of the above possible implementations.
  • this application also provides a communication device, which may be a network device.
  • the communication device has the function of realizing the network equipment in each of the above possible implementations.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication device 1400 includes a transceiver module 1401 and a processing module 1402.
  • the transceiver module 1401 is used to send the first PDCCH to the terminal device in the first DRX cycle.
  • the processing module 1402 is configured to, if the first condition is met, stop monitoring the physical downlink control channel PDCCH at the first moment.
  • the first time is the time when the inactivity timer InactivityTimer triggered by the first PDCCH times out or the time after timeout.
  • the first condition includes: at the second moment, the first timer is not running or has timed out, wherein the second moment is when the terminal device receives all the data in the first DRX cycle.
  • the time of the first PDCCH, the starting time of the first timer is the starting time or the end time of the duration onDuration of the second DRX cycle, or the time when the PDCCH is first received in the second DRX cycle ;
  • the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the inactivity timer InactivityTimer is not running during the first period, wherein the end time of the first period is the starting time of onDuration of the first DRX cycle.
  • the duration of the first period is the duration of the InactivityTimer.
  • the first condition includes: at the starting moment of onDuration of the first DRX cycle, the InactivityTimer is not running, and the terminal device does not lose downlink control information DCI in the second DRX cycle. , wherein the second DRX cycle is the previous DRX cycle adjacent to the first DRX cycle.
  • the first condition includes: the communication device 1400 sends first indication information to the terminal device within the first DRX cycle, and the first indication information is used to indicate when the InactivityTimer times out or times out. stop monitoring the PDCCH, or instruct the onDuration timer to stop running when or after the InactivityTimer times out, or the first data indicated by the first indication information belongs to the same frame of data as the data that has been scheduled in the previous DRX cycle. .
  • the first data is data scheduled by the second PDCCH; or, if the first indication information is carried in the first In the PDSCH, the first data is the data carried by the first PDSCH.
  • the duration of the first timer is preconfigured, or the duration of the first timer is configured by the communication device 1400 .
  • the processing module 1402 is further configured to receive the PDCCH for the first time in the first DRX cycle of the terminal device at the start time or end time of onDuration of the first DRX cycle. moment, start the second timer.
  • the transceiver module 1401 is also configured to send the third PDCCH to the terminal device in the third DRX cycle.
  • the processing module 1402 is also configured to, if the second timer is not running or has timed out at the third moment, stop monitoring the physical downlink control channel PDCCH at the fourth moment.
  • the third DRX cycle is the next DRX cycle adjacent to the first DRX cycle
  • the third time is the time when the terminal equipment receives the third PDCCH
  • the fourth time is the time when the terminal equipment receives the third PDCCH.
  • the time when the InactivityTimer triggered by the third PDCCH times out or the time after timeout, the second timer is a timer different from the first timer
  • the duration of the second timer is the same as that of the first timer. of the same duration.
  • the starting time of the first timer is the time when the PDCCH is received for the first time in the second DRX cycle, then after the first timer times out, and the first DRX The first timer is started when the PDCCH is first received within the onDuration of the cycle.
  • the first condition further includes: the InactivityTimer is not running at the starting moment of onDuration of the first DRX cycle of the terminal device.
  • the processing module 1402 is further configured to determine that the terminal device has lost DCI in the second DRX cycle based on at least one of the following information: HARQ process number HPN in the second DRX cycle, new Data indicates NDI and redundancy version RV; alternatively, data allocation indicates DAI.
  • stopping monitoring of the physical downlink control channel PDCCH includes: stopping the operation of the onDuration timer of the first DRX cycle.
  • the communication device 1400 can implement the functions of the network device in each of the above possible implementations.
  • the functions of the network device in each of the above possible implementations.
  • the above transmission module may be a transceiver, which may include an antenna and a radio frequency circuit, etc.
  • the processing module may be a processor, such as a baseband chip, etc.
  • the transmission module may be a radio frequency unit
  • the processing module may be a processor.
  • the transmission module may be an input interface and/or an output interface of the chip system
  • the processing module may be a processor of the chip system, such as a central processing unit (CPU).
  • CPU central processing unit
  • the device is presented in the form of dividing various functional modules in an integrated manner.
  • Module here may refer to specific circuits, processors and memories that execute one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above functions.
  • the transmission device of the side link can take the form as shown in Figure 2 mentioned above.
  • the function/implementation process of the processing module 1402 in Figure 14 can be implemented by the processor 201 in Figure 2 calling the computer program instructions stored in the memory 204.
  • the function/implementation process of the transceiver module 1401 in Figure 14 can be through the communication interface 203 in Figure 2 .
  • the processor 201 in Figure 2 can call the computer execution instructions stored in the memory 204, so that the device 200 can perform the operations of the terminal device or network device in each of the above method embodiments, and implement the above-mentioned aspects of the present application.
  • the processor 201 in Figure 2 can call the computer execution instructions stored in the memory 204, so that the device 200 can perform the operations of the terminal device or network device in each of the above method embodiments, and implement the above-mentioned aspects of the present application.
  • Various possible implementation methods can call the computer execution instructions stored in the memory 204, so that the device 200 can perform the operations of the terminal device or network device in each of the above method embodiments, and implement the above-mentioned aspects of the present application.
  • the communication device in each of the above device embodiments may completely correspond to the terminal device or network device in the method embodiment, and the corresponding steps may be executed by corresponding modules or units.
  • the transceiver unit may be an interface circuit used by the chip to receive signals from other chips or devices.
  • the above transceiver module for sending or receiving is an interface circuit of the device and is used to send signals to other devices.
  • the transceiver module can be used to send signals to other chips or devices. Interface circuit that sends signals.
  • a computer-readable storage medium or a computer program product including instructions is also provided, and the instructions can be executed by the processor 201 of the communication device 200 to complete the method of the above embodiment. Therefore, the technical effects that can be obtained can be referred to the above method embodiments, and will not be described again here.
  • the computer program product includes instructions. When the instructions are executed, the computer can respectively perform operations of the terminal device or network device corresponding to the above method.
  • An embodiment of the present application also provides a system chip.
  • the system chip includes: a processing unit and a communication unit.
  • the processing unit may be, for example, a processor.
  • the communication unit may be, for example, an input/output interface, a pin, or a circuit.
  • the processing unit can execute computer instructions to cause the communication device to which the chip is applied to perform the operations of the terminal device and the network device in the method provided by the embodiments of the present application.
  • any communication device provided in the above embodiments of the present application may include the system chip.
  • the computer instructions are stored in a storage unit.
  • An embodiment of the present application also provides a communication system, which may include: any terminal device and network device in the above embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.

Abstract

本申请提供一种非连续接收的配置方法及装置，涉及通信技术领域，解决了终端设备监听物理下行控制信道PDCCH的持续时间设置较长，节能效率较低的问题。该方法包括：终端设备在第一非连续接收DRX周期接收第一PDCCH；若满足第一条件，则终端设备在第一时刻停止监测物理下行控制信道PDCCH；其中，第一时刻为第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。

Description

一种非连续接收的配置方法及装置
本申请要求于2022年06月27日提交国家知识产权局、申请号为202210743794.5、申请名称为“一种停止监测PDCCH的方法、终端设备、网络设备”的中国专利申请的优先权，以及于2022年07月27日提交国家知识产权局、申请号为202210890313.3、申请名称为“一种非连续接收的配置方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种非连续接收的配置方法及装置。
背景技术
在无线通信系统中，在保证数据能够有效传输的前提下为了节省终端设备的功耗，引入了一种非连续接收(discontinuous reception，DRX)机制来控制终端设备监听物理下行控制信道(Physical Downlink Control Channel，PDCCH)的行为。网络设备为终端设备下发DRX配置，其中，DRX配置可以包括DRX周期和持续时间onDuration的配置信息，用于确定终端设备在该DRX周期的onDuration时段内可以持续监听PDCCH获取调度信息。如果终端设备在onDuration时段内没有接收到任何调度信息，则终端设备进入睡眠状态，停止监听PDCCH以节省功耗。
其中，针对扩展现实(extended reality，XR)类业务，例如虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、云游戏(cloud gaming，CG)等，其业务特点是数据包到达具有周期性且间隔时间较短，例如，某XR业务为每秒传输60帧图像，则不考虑传输时延的情况下，相邻两个数据包的到达时间间隔平均为16.67毫秒(ms)。但是，考虑到下行传输中，由于数据包从服务器到达基站的路由路径不同，数据包实际到达的时间可能出现抖动(jitter)现象，如0～8ms的抖动时延，且不同数据包可能会出现不同时长的抖动时延，例如数据包到达的时间间隔可能为16.67ms～24.67ms。
目前，为了解决由抖动引起的数据包延迟到达问题，尽可能使得数据到达时间处于DRX周期的onDuration时段之内，可以将onDuraiton的长度配置得较长，以使得onDuration的长度足以覆盖数据包到达的可能时间段。但是，DRX周期的onDuration长度增长会导致终端的功耗增加，若抖动时延较短，数据包实际到达时刻较早，则终端完成数据传输后的onDuration时段内会进行无效的PDCCH监测，从而终端的节能效率较低。
发明内容
本申请提供一种非连续接收的配置方法及装置，解决了现有技术中终端监听物理下行控制信道PDCCH的持续时间设置较长，节能效率较低的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种非连续接收的配置方法，该方法包括：终端设备在第一 DRX周期接收第一PDCCH；若满足第一条件，则所述终端设备在第一时刻停止监测物理下行控制信道PDCCH；其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
上述实施方案，通过定义终端设备停止监测PDCCH的规则，使得终端设备以及网络设备可以同步根据该规则停止监测PDCCH，缩短DRX周期内无效监测PDCCH的时间以节省功耗。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
上述可能的实施方式，通过配置第一定时器，将判断第一定时器是否超时，作为终端设备确定接收的第一PDCCH属于当前DRX周期还是前一个DRX周期的XR数据帧的判断条件，从而进一步判断该第一PDCCH触发的InactivityTimer超时是否可以提前停止监测PDCCH，缩短无效监测PDCCH的时间以节省终端设备的功耗。
在一种实施方式中，所述第一条件包括：在第一时段内所述不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
上述可能的实施方式，网络设备和终端设备都可以基于第一时段内InactivityTimer是否在运行，确定当前InactivityTimer超时所对应的PDCCH是当前DRX周期还是前一个DRX内到达的XR数据帧，从而确定是否能够提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。另外，当终端设备侧出现PDCCH丢失的情况下，终端设备侧也能与网络设备侧做出相同的判断，避免数据传输失败的问题。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
上述可能的实施方式，网络设备和终端设备都可以基于第一条件，通过确定前一个DRX周期内是否发生丢包，从而确定当前InactivityTimer超时所对应的PDCCH是当前DRX周期还是前一个DRX的XR数据帧，进而判断是否能够提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。另外，当终端设备侧出现DCI丢失的情况下，终端设备侧也能与网络设备侧做出相同的判断，避免数据传输失败的问题。
在一种实施方式中，第一条件包括：所述终端设备在所述第一DRX周期内接收来自网络设备的第一指示信息，所述第一指示信息用于指示所述终端设备在所述 InactivityTimer超时时或超时后停止监测PDCCH，或者，指示所述终端设备在所述InactivityTimer超时时或超时后停止onDuration定时器(也称为onDurationTimer)的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
上述可能的实施方式，终端设备可以基于来自网络设备的指示信息，确定是否可以在当前InactivityTimer超时时提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由网络设备配置的。
在一种实施方式中，第一定时器的时长与应用服务器向所述终端设备传输数据包的PDB相关，或者，所述应用服务器向所述终端设备传输数据包的PDB与所述应用服务器向接入网设备传输数据包的PDB的差值相关。或者，所述第一定时器的时长与接入网设备向所述终端设备传输数据包的PDB相关。
在一种实施方式中，终端设备在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；在第三DRX周期接收第三PDCCH；若在第三时刻，所述第二定时器未在运行或者已超时，则所述终端设备在第四时刻停止监测物理下行控制信道PDCCH；其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则所述终端设备在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，终端设备在所述第二DRX周期内丢失DCI，根据以下至少一种信息确定：所述第二DRX周期内接收的HARQ进程号HPN、新数据指示NDI和冗余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
第二方面，提供一种非连续接收的配置方法，该方法包括：网络设备在第一DRX周期向终端设备发送第一PDCCH；若满足第一条件，则在第一时刻停止监测物理下行控制信道PDCCH；其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：在第一时段内不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：所述网络设备在所述第一DRX周期内向所述终端设备发送第一指示信息，所述第一指示信息用于指示在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由所述网络设备配置的。
在一种实施方式中，在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述终端设备的所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；在第三DRX周期向所述终端设备发送第三PDCCH；若在第三时刻，所述第二定时器未在运行或者已超时，则在第四时刻停止监测物理下行控制信道PDCCH；其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为所述终端设备接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，终端设备在所述第二DRX周期内丢失DCI，根据以下至少一种信息确定：所述第二DRX周期内的HARQ进程号HPN、新数据指示NDI和冗 余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
第三方面，提供一种通信装置，该通信装置包括收发模块和处理模块，收发模块，用于在第一DRX周期接收第一PDCCH；若满足第一条件，则处理模块，用于在第一时刻停止监测物理下行控制信道PDCCH；其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述通信装置在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：在第一时段内不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述通信装置在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：所述通信装置在所述第一DRX周期内接收来自网络设备的第一指示信息，所述第一指示信息用于指示所述通信装置在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示所述通信装置在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由网络设备配置的。
在一种实施方式中，处理模块，还用于在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；所述收发模块，还用于在第三DRX周期接收第三PDCCH；若在第三时刻，所述第二定时器未在运行或者已超时，则所述处理模块，还用于在第四时刻停止监测物理下行控制信道PDCCH；其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则所述处理模块，还用于在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述通信装置在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，处理模块还用于，根据以下至少一种信息，确定在所述第二DRX周期内丢失DCI：所述第二DRX周期内接收的HARQ进程号HPN、新数据指示NDI和冗余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
第四方面，提供一种通信装置，通信装置包括收发模块和处理模块，收发模块，用于在第一DRX周期向终端设备发送第一PDCCH；若满足第一条件，则所述处理模块，用于在第一时刻停止监测物理下行控制信道PDCCH；其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：在第一时段内不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：所述通信装置在所述第一DRX周期内向所述终端设备发送第一指示信息，所述第一指示信息用于指示在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由所述通信装置配置的。
在一种实施方式中，处理模块，还用于在所述第一DRX周期的onDuration的起 始时刻或者结束时刻，或者，在所述终端设备的所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；所述收发模块，还用于在第三DRX周期向所述终端设备发送第三PDCCH；若在第三时刻，所述第二定时器未在运行或者已超时，则所述处理模块，还用于在第四时刻停止监测物理下行控制信道PDCCH；其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为所述终端设备接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，处理模块，还用于根据以下至少一种信息，确定所述终端设备在所述第二DRX周期内丢失DCI：所述第二DRX周期内的HARQ进程号HPN、新数据指示NDI和冗余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
第五方面，提供一种终端设备，包括：一个或多个处理器和一个或多个存储器；所述一个或多个存储器与所述一个或多个处理器耦合，所述一个或多个存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述一个或多个处理器执行所述计算机指令时，使得所述终端设备执行如上述第一方面中任一项所述的方法。
第六方面，提供一种网络设备，包括：一个或多个处理器和一个或多个存储器；所述一个或多个存储器与所述一个或多个处理器耦合，所述一个或多个存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述一个或多个处理器执行所述计算机指令时，使得所述网络设备执行如上述第二方面中任一项所述的方法。
第七方面，提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述第一方面中任一项所述的方法。
第八方面，提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述第二方面中任一项所述的方法。
第九方面，提供一种包含指令的计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机如上述第一方面中任一项所述的方法。
第十方面，提供一种包含指令的计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机如上述第二方面中任一项所述的方法。
第十一方面，提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储 器中存储的程序指令，以实现如上述第一方面中任一项所述的方法。
第十二方面，提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如上述第二方面中任一项所述的方法。
第十三方面，提供一种通信系统，所述通信系统包括如上述第三方面中任一项所述的通信装置和如上述第四方面中任一项所述的通信装置。
可以理解地，上述提供的任一种通信装置、计算机可读存储介质、计算机程序产品、芯片或者通信系统，均可以用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种通信系统的架构图；
图2为本申请实施例提供的一种通信装置的架构图；
图3为本申请实施例提供的一种非连续接收DRX配置示意图；
图4为本申请实施例提供的一种非连续接收DRX配置与数据传输的示意图；
图5为本申请实施例提供的一种非连续接收的配置方法的流程示意图；
图6和图7为本申请实施例提供的考虑传输抖动下的数据传输示意图；
图8为本申请实施例提供的一种下行数据传输的PDB示意图；
图9-图13为本申请实施例提供的几种非连续接收的配置示意图；
图14为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先，对本申请实施例的实施环境和应用场景进行简单介绍。
本申请可应用到现有的新无线(new radio，NR)系统中，也可用在其它任何有类似结构和功能的无线通信系统中。如图1所示，该通信系统至少包括终端设备101和网络设备102。
本申请实施例涉及到的终端设备101可以是用户设备(user equipment，UE)，其中，UE包括具有无线通信功能的手持式设备、车载设备、可穿戴设备或计算设备。示例性地，UE可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是虚拟现实(virtual reality，VR)终端设备、增强现实 (augmented reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
本申请实施例中，用于实现终端的功能的装置可以是终端；也可以是能够支持终端实现该功能的装置，例如芯片系统，该装置可以被安装在终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端设备功能的装置是UE为例，描述本申请实施例提供的技术方案。
本申请实施例涉及到的网络设备102可以包括基站(base station，BS)，可以是一种部署在无线接入网中能够和终端进行无线通信的设备。
其中，基站可能有多种形式，比如宏基站、微基站、中继站和接入点等。示例性地，本申请实施例涉及到的基站可以是5G中的基站或LTE中的基站，其中，5G中的基站还可以称为发送接收点(transmission reception point，TRP)或gNB。
本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。
在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备，以网络设备是基站为例，描述本申请实施例提供的技术方案。
本申请实施例提供的技术方案可以应用于网络设备和终端设备之间的无线通信。其中，在本申请实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描述为“数据传输”、“信息传输”或“传输”。
需要说明的是，图1仅为示例性框架图，图1中包括的网元节点的数量不受限制。除图1所示功能节点外，还可以包括其他节点，如：核心网设备、网关设备、应用服务器等等，不予限制。接入网设备通过有线网络或无线网络与核心网设备相互通信，如通过下一代(Next Generation，NG)接口相互通信。
在具体实现时，图1所示各网元，如：终端设备、网络设备可采用图2所示的组成结构或者包括图2所示的部件。图2为本申请实施例提供的一种通信装置200的结构示意图，当该通信装置200具有本申请实施例所述终端设备的功能时，该通信装置200可以为终端设备或者终端设备中的芯片或者片上系统。当通信装置200具有本申请实施例所述的网络设备的功能时，通信装置200可以为网络设备或者网络设备中的芯片或者片上系统。
如图2所示，该通信装置200可以包括处理器201，通信线路202以及通信接口203。进一步的，该通信装置200还可以包括存储器204。其中，处理器201，存储器204以及通信接口203之间可以通过通信线路202连接。
其中，处理器201可以是中央处理器(Central Processing Unit，CPU)、通用处理器网络处理器(Network Processor，NP)、数字信号处理器(Digital Signal Processing，DSP)、微处理器、微控制器、可编程逻辑器件或它们的任意组合。处理器201还可以是其它具有处理功能的装置，如电路、器件或软件模块等。
通信线路202，用于在信装置200所包括的各部件之间传送信息。
通信接口203，用于与其他设备或其它通信网络进行通信。该其它通信网络可以为以太网，无线接入网(Radio Access Network，RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。通信接口203可以是接口电路、管脚、射频模块、收发器或者任何能够实现通信的装置。
存储器204，用于存储指令。其中，指令可以是计算机程序。
其中，存储器204可以是只读存储器(Read-only Memory，ROM)或可存储静态信息和/或指令的其他类型的静态存储设备，也可以是随机存取存储器(Random Access Memory，RAM)或者可存储信息和/或指令的其他类型的动态存储设备，还可以是电可擦可编程只读存储器(Electrically Erasable Programmable read-only Memory，EEPROM)、只读光盘(Compact Cisc read-only Memory，CD-ROM)或其他光盘存储、光碟存储、磁盘存储介质或其他磁存储设备，光碟存储包括压缩光碟、激光碟、光碟、数字通用光碟、或蓝光光碟等。
需要说明的是，存储器204可以独立于处理器201存在，也可以和处理器201集成在一起。存储器204可以用于存储指令或者程序代码或者一些数据等。存储器204可以位于通信装置200内，也可以位于通信装置200外，不予限制。处理器201，用于执行存储器204中存储的指令，以实现本申请下述实施例提供的方法。
在一种示例中，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
作为一种可选的实现方式，通信装置200包括多个处理器，例如，除图2中的处理器201之外，还可以包括处理器207。
作为一种可选的实现方式，通信装置200还包括输出设备205和输入设备206。示例性地，输入设备206是键盘、鼠标、麦克风或操作杆等设备，输出设备205是显示屏、扬声器等设备。
需要说明的是，通信装置200可以是可穿戴设备、台式机、便携式电脑、网络服务器、移动手机、平板电脑、无线终端、嵌入式设备、芯片系统或有图2中类似结构的设备。此外，图2中示出的组成结构并不构成对该通信装置的限定，除图2所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
结合上述图1中，终端设备在连接态时可以根据网络设备配置的DRX配置信息，进入持续时间onDuration以持续监听PDCCH，或者进入休眠时间，停止监听PDCCH以达到省电的目的。其中，DRX包括DRX长周期和起始偏移(drx-LongCycleStartOffset)，该参数用于配置长DRX周期的长度以及一个DRX周期(无论是长DRX周期还是短DRX周期)的起始位置的偏移值。其中，长DRX周期的长度以毫秒ms为单位，起始偏移的配置粒度为1ms。DRX配置信息还可以包括持续时间定时器onDurationTimer的配置信息，用于确定终端设备从DRX周期的起始位置开始持续监听PDCCH的时段，也就是从drx-StartOffset指示的起始子帧算起需要监听PDCCH的连续子帧数。DRX配置信息还可以包括不活动定时器InactivityTimer的配置信息。此外，DRX参数还包括DRX时隙偏移值(drx-SlotOffset)，该参数用于配 置启动drx-onDurationTimer之前的延迟值，其配置粒度为1/32ms，取值范围为0～31，即0ms～31/32ms。当网络设备为终端设备使能DRX短周期时，DRX参数还可以包括短周期(shortDRX)，该参数用于配置短DRX周期的长度。
如图3所示，DRX的大致过程如下：进入一个DRX周期后，在持续时间(on duration)的时间段内，终端设备开始持续监测PDCCH。如果在持续时间的时间段内未监测到PDCCH，终端设备在持续时间的时间段结束后直接进入休眠状态。如果在持续时间的时间段内监测到PDCCH，且该PDCCH用于调度新传的数据(即PDCCH用于传输初传调度的调度信息)，那么，终端设备按照接收到的调度信息接收数据(即接收PDSCH)，并且启动DRX非激活定时器，每当终端设备监测到初传调度的调度信息，该DRX非激活定时器就被启动(或重启)一次，终端设备在DRX非激活定时器定时期间，持续监测PDCCH，直至DRX非激活定时器超时(expire)，终端设备进入休眠状态。DRX配置信息还可以包括DRX混合自动重传请求往返时间定时器(drx-hybrid auto repeat request round trip timer，drx-HARQ-RTT-Timer)、DRX重传定时器(drx-RetransmissionTimer)等参数。其中，终端设备在DRX持续时间定时器、DRX非激活定时器、下行链路(downlink，DL)的DRX重传定时器和上行链路(uplink，UL)的DRX重传定时器启动期间均需要监测PDCCH，这些时间也统称为激活时间(Active Time)。其余时间被统称为在激活时间之外(outside Active Time)。在激活时间外，终端设备无需监测PDCCH，此时终端设备可以进入睡眠状态，以节省功耗。
在网络设备向终端设备传输XR或类似XR业务的数据包场景中，如图4所示，以相邻两帧图像对应的数据包(即两个XR数据帧)的到达时间间隔平均为16.67ms为例，终端设备侧XR数据帧的理想到达时间间隔可以为16.67ms。应理解，数据帧是从应用层角度所定义的，一个数据帧也可以替换为一个视频帧。一个协议数据单元集合(protocol data unit set，PDU set)包括一帧(frame)数据帧中的业务数据。PDU set是从MAC层角度所定义的。一个数据帧也可以替换为一个PDU set。在下面的实施例中，均以业务数据为XR数据帧为例，但是下面的方法也适用于其他业务场景，不予限制。
在这种情况下，网络设备可以为该终端设备配置比较接近XR数据帧到达时间间隔的DRX周期长度，例如可以为16ms，或者，通过其他实施方式使得DRX周期长度与终端设备侧XR数据帧到达时间匹配或者近似匹配。在本申请的下述实施例中，假设DRX周期长度与XR数据帧的周期长度是匹配的。
另外，考虑到下行传输中，由于XR数据帧从服务器到达基站的路由路径不同，XR数据帧实际到达的时间可能出现抖动(jitter)现象，例如，抖动的时长可能为0～8ms。如图4所示，XR数据帧的实际到达时间可能会延迟0～8ms，即使得XR数据帧到达的时间间隔为16.67ms～24.67ms之间波动。如图4可以看到，在有抖动的情况下，XR数据帧实际到达的位置可能会落在onDuration之外。这种情况下，由于终端设备在onDuration内未收到调度，在onDuration结束后便不再监测PDCCH，基站只能将XR数据帧延迟到下一个DRX周期内进行调度。这种情况就会增大数据的传输时延。可以理解的是，抖动的时长范围为0～8ms，可以等价描述为抖动的范围为- 4ms～4ms，两种描述方式下参考点不同，但物理含义相同。
一种解决方式中，可以通过将DRX周期中的onDuration时段配置得较长，以解决由于抖动引起的XR数据帧延迟到达的问题，即，尽可能使得数据到达时间处于onDuration时段之内。例如，将onDuraiton的长度配置为可以覆盖到jitter可能的延迟范围，使得onDuration的长度足以覆盖XR数据帧到达的所有可能时间段。但是，DRX的持续时间配置过长会导致终端设备的激活时间过长，终端设备监听到初传PDCCH还会启动InactivityTimer以延长激活时间，与此同时，每个XR数据帧的传输时间可能较短，如此，终端设备会在激活时间的大部分时段内进行无效的PDCCH监测(即监测了PDCCH但是没有收到数据调度)，难以达到节能的效果。
基于上述问题，下面结合图1所示通信系统，对本申请实施例提供的实施方式进行描述。其中，下述实施例中的各设备可以具有图2所示部件。其中，本申请各实施例之间涉及的动作，术语等均可以相互参考，各实施例之间还可以相互结合，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
本申请实施例提供一种非连续接收的配置方法，通过配置终端设备停止监测PDCCH的一些规则，使得终端设备可以缩短无效监测PDCCH的时间，为终端设备节省功耗。如图5所示，该方法可以包括：
S501：网络设备向终端设备发送第一PDCCH。
其中，同一网络设备可能用于对多个终端设备进行数据调度，而多个终端设备XR数据帧的大小、XR数据帧调度周期可能不同，因此，网络设备为终端设备配置的DRX配置也不同。从而，网络设备侧会基于不同的终端设备维护其对应的DRX配置，以及维护和更新该终端设备对应的各种DRX相关的定时器运行等。例如，网络设备侧根据第一终端的DRX配置，确定第一终端对应的每个DRX周期的起始时间，DRX周期的持续时间onDuration的起始时间，以及启动不活动定时器InactivityTimer等，从而与第一终端侧保持相同的DRX配置，以同步数据调度等，提高通信效率。
需要说明的是，本申请的实施例中仅以网络设备与一个终端设备同步DRX配置、以及两者之间的交互为例进行说明，并不构成对应用场景的限定。
具体的，网络设备可以在第一DRX周期内向终端设备发送第一PDCCH，第一PDCCH是该终端设备在第一DRX周期的调度数据。
S502：终端设备在第一DRX周期接收第一PDCCH。
相对应的，终端设备在第一DRX周期接收来自网络设备的第一PDCCH。
S503：若满足第一条件，则在不活动定时器InactivityTimer超时时或超时后停止监测PDCCH。
具体的，可以确定在第一时刻停止监测PDCCH，第一时刻可以为第一PDCCH触发的不活动定时器InactivityTimer超时的时刻，或者InactivityTimer超时后的时刻。
也就是说，本申请实施例可以通过定义终端设备停止监测PDCCH的规则，使得终端设备可以根据该规则停止监测PDCCH，缩短无效监测PDCCH的时间以节省功 耗。
相对应的，网络设备也可以根据与终端设备相同的判断规则，确定该终端设备停止监测PDCCH。从而网络设备可以与终端设备对齐监测PDCCH的时段，避免丢包或者无效PDCCH监测，提高通信效率与节能效率。
具体的，该停止监测PDCCH的规则具体可以为：终端设备确定在第一PDCCH触发的InactivityTimer超时后停止监测PDCCH，或者在InactivityTimer超时时停止监测PDCCH。
其中，终端设备可以在DRX周期内onDuration结束前的时刻停止监测PDCCH，即终端设备可以根据预先定义的规则确定在onDuration结束前停止监测PDCCH，提前进入休眠状态。
示例性的，如图6所示，终端设备可以在DRX周期的onDuration内接收第一PDCCH，接收第一PDCCH的时刻启动InactivityTimer。当终端设备确定InactivityTimer超时后停止监测PDCCH，即终端设备在原有onDuration的后续时段不再监测PDCCH，提前进入休眠状态，缩短了持续监测PDCCH的时长。
在一种可能的实施方式中，当终端设备的XR数据帧较大时，一个XR数据帧还可以被分为多个协议数据单元(Protocol Data Unit，PDU)分别进行下发，同一个DRX周期内的XR数据帧分为第一PDU、第二PDU以及第三PDU等分别下发，而每个PDU都对应一个调度数据的PDCCH。例如，终端设备在一个DRX周期内接收第一PDCCH、第二PDCCH以及第三PDCCH等。其中，每个PDCCH中包括调度一个PDU的下行控制信息(Downlink control information，DCI)。另外，每个调度新传数据的PDCCH都会触发启动或重启不活动定时器InactivityTimer，延长监测PDCCH的时间。当终端设备的XR数据帧较大或小区内用户数很多时，数据传输持续的时间较长，InactivityTimer的运行时间可能持续到下一个DRX周期，例如，图7中所示的，第二DRX周期的InactivityTimer的运行时间与相邻的下一个DRX周期(第一DRX周期)的onDuration有重叠。
若终端设备在InactivityTimer超时后停止监测PDCCH，如图7所示，则该终端设备在第一DRX周期的onDuration时段内提前停止监测PDCCH，从而导致该终端设备无法监测到第一DRX周期对应的XR数据帧调度信息PDCCH。在图7中，第一DRX对应的PDCCH表示在第一DRX周期到达的XR数据帧对应的PDCCH，第二DRX对应的PDCCH表示在第二DRX周期到达的XR数据帧对应的PDCCH。在图7中，在第二DRX周期到达的XR数据帧被分为5次传输，因此图7中有5个第二DRX对应的PDCCH。也就是说，终端设备由于无法得知在一个DRX周期中接收的XR数据帧是当前周期对应的XR数据帧还是前一个周期对应的XR数据帧的一部分，出于节能的需求停止监测PDCCH，而导致数据接收失败或增加传输时延。
为解决上述问题，本申请实施例提出的技术方案中，通过结合XR业务的较高时延需求，以及网络设备的XR数据帧丢弃(packet dropping)功能，优化终端设备停止监测PDCCH的规则，从而使得网络设备和终端设备侧可以基于一定的判断条件，确定当前InactivityTimer超时的PDCCH是当前DRX周期的XR数据帧还是前一个DRX的XR数据帧，从而确定是否能够提前终止PDCCH的监测，以达到节省终端设 备功耗的目的，同时不影响数据传输效率。
其中，XR业务对时延要求较高。例如，在实时视频场景中，若XR数据帧传输时延超过预设标准，则可能造成实时视频画面卡顿、显示不流畅等问题，影响用户体验。而时延要求具体可以体现为数据包时延预算(packet delay budget，PDB)。其中，如图8所示，下行数据包从应用服务器传输到终端设备，需要经过互联网传输(应用服务器向核心网设备发送数据包)、核心网传输(核心网设备向接入网设备发送数据包)、接入网传输(接入网设备向终端设备发送数据包)这几个过程，从而PDB可以分为端到端PDB，以及空口PDB。
其中，下行数据包的端到端PDB是指，为满足业务需求，从应用服务器发出数据包的时刻，到终端设备接收到该数据包的时刻之间的最大允许时长。例如，某业务的端到端PDB为100ms，若下行数据包可以在100ms内完成从应用服务器到终端设备的传输，则可以认为满足该业务的传输要求；若下行数据包完成从应用服务器到终端设备的传输需要的时长超过100ms，则可以认为不满足该业务的传输要求。
另外，下行数据包的空口PDB是指，数据包从接入网设备到终端设备完成传输的最大允许时长。例如，某业务的空口PDB为10ms，若下行数据包可以在10ms内完成从基站到终端设备的传输，则可以认为满足该业务的传输要求。
从而，根据特定业务对应的PDB可知，若某XR数据帧传输时长超过对应的PDB需求，可以认为即使完成该XR数据帧传输，该XR数据帧对于接收端的使用意义也不大。因此，网络设备可以使能数据包丢弃(packet dropping)功能，即网络设备可以根据XR业务的PDB需求，对超过PDB的数据包，网络设备不再调度传输该数据包。
例如，某XR数据帧的传输时长超过对应的PDB，即表示当该XR数据帧发送至终端设备时，已经过了该XR数据帧的图像显示时刻，那么该XR数据帧没有传输的必要了，网络设备可以将这类XR数据帧丢弃，不再向终端设备发送。
基于上述技术，在一种实施方式中，上述步骤S503中的第一条件，具体可以包括：在第二时刻，第一定时器未在运行或者已超时，其中，第二时刻可以为终端设备在第一DRX周期内接收第一PDCCH的时刻。
也就是说，通过配置第一定时器，将判断第一定时器是否超时，作为终端设备确定接收的第一PDCCH属于当前DRX周期还是前一个DRX周期的XR数据帧的判断条件。
在一种实施方式中，如图9所示，第一定时器的起始时刻可以为第二DRX周期的持续时长onDuration的起始时刻，即在第二DRX周期的onDuration的起始时刻同时启动第一定时器，其中，第二DRX周期为与第一DRX周期相邻的前一个DRX周期。
如图9所示，在情况1中，若终端设备在第一DRX周期内的第二时刻接收第一PDCCH，并且第一定时器在第二时刻处于运行过程中，则认为该第一PDCCH可能是第一DRX周期的前一个DRX周期内到达的XR数据帧的调度信息，即是第二DRX周期内到达的XR数据帧的调度信息，则该第一PDCCH触发的InactivityTimer超时时，不触发停止监测PDCCH。
反之，在情况2中，若接收第一PDCCH的第二时刻，第一定时器未在运行或者已超时，则认为该第一PDCCH是第一DRX周期的调度信息，则该第一PDCCH触发的InactivityTimer超时时，可以停止监测PDCCH，提前终止监测PDCCH，以节省功耗。
在一种实施方式中，所述停止监测PDCCH，具体可以包括：停止DRX周期的onDuration定时器的运行。如图9中的示例，即停止第一DRX周期的onDuration定时器的运行。
在上述的实施方式中，第一定时器的时长可以是预配置的，或者，还可以是由网络设备配置的。
其中，第一定时器的时长可以与端到端PDB相关，即与应用服务器向终端设备传输XR数据帧的PDB相关。另外，若将应用服务器向接入网设备传输XR数据帧的平均时长看成是一个定值，则第一定时器的时长还可以是如下两项的差值：基于端到端PDB、应用服务器—接入网设备平均传输时长。例如，如图8所示，端到端PDB为T1，服务器与接入网设备之间的平均传输时长为T2，则第一定时器的时长可以设置为T1-T2得到的差值。
另外，在上述的实施方式中，即使第二DRX周期内出现了PDCCH(或DCI)丢包或接收失败，也不会由于停止PDCCH监测而导致的第一DRX周期XR数据帧丢失。
如图9所示，在情况3中，若终端设备未接收到图中所示的PDCCH-1，则终端设备和网络设备侧关于InactivityTimer的运行状态是不一致的。此时网络设备认为InactivityTimer未出现超时，而终端设备会认为IactivityTimer超时过一次。但是，根据本申请的上述实施方式，在终端设备接收第一PDCCH的时刻，若判断第一定时器处于运行状态，则在该第一PDCCH触发的InactivityTimer超时时，终端设备和网络设备都确定不会触发停止监测PDCCH，即InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。反之，若终端设备接收第一PDCCH的时刻，判断第一定时器未在运行，则确定在该第一PDCCH触发的InactivityTimer超时时，终端设备和网络设备都会判断此时可以触发停止监测PDCCH。因此，该技术方案的鲁棒性更强。
在另一种实施方式中，第一定时器的起始时刻还可以为第二DRX周期onDuration的结束时刻。也就是说，可以在onDuration的结束时刻启动第一定时器。
此时，若终端设备在第一DRX周期内的第二时刻接收第一PDCCH，并且第一定时器在第二时刻处于运行过程中，则认为该第一PDCCH可能是第一DRX周期的前一个DRX周期内到达的XR数据帧的调度信息，即是第二DRX周期的调度信息，则该第一PDCCH触发的InactivityTimer超时时，不触发停止监测PDCCH。若接收第一PDCCH的第二时刻，第一定时器未在运行或者已超时，则认为该第一PDCCH是第一DRX周期内到达的XR数据帧的调度信息，则该第一PDCCH触发的InactivityTimer超时时，可以停止监测PDCCH，提前终止监测PDCCH。
在这种实施方式下，第一定时器的时长可以与端到端PDB相关，即与应用服务器向终端设备传输XR数据帧的PDB相关。具体的，若将应用服务器与接入网设备之间的传输平均时长与DRX周期中onDuration时长之和看成是一个定值，则第一定 时器的时长还可以是与应用服务器与终端设备的传输PDB与前述定值的差值相关。例如，结合图8所示，端到端PDB为T1，服务器向接入网设备的平均传输时长为T2，DRX周期的onDuration时长为T3，则第一定时器的时长可以设置为T1-T2-T3得到的差值。
进一步的，需要说明的是，由于上述实施方式中，一个DRX周期的onDuration起始时刻或结束时刻启动第一定时器，则该DRX周期对应的第一定时器可能与相邻的下一个DRX周期有重合，例如第二DRX周期的第一定时器可能与第一DRX周期的onDuration重合，而第一DRX周期的onDuration的起始时刻或结束时刻需要再启动一个第一定时器(或命名为不同的定时器)。因此，同一时刻，可能会运行不止一个满足前述功能的第一定时器。
在一种实施方式中，该方法还包括如下步骤。
步骤1：在第一DRX周期的onDuration的起始时刻或者结束时刻，启动第二定时器。
步骤2：终端设备在第三DRX周期的第三时刻接收第三PDCCH。
步骤3：若在第三时刻，第二定时器未在运行或者已超时，则在第四时刻停止监测物理下行控制信道PDCCH。其中，第四时刻为第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻。
其中，第三DRX周期为与第一DRX周期相邻的后一个DRX周期，第二定时器与第一定时器是功能相同的定时器，第二定时器与第一定时器的时长相同。
例如，如图10所示，以第一定时器的起始时刻为DRX周期onDuration的起始时刻为例，在第二DRX周期的起始位置启动第一定时器，第一定时器未结束运行时，在第一DRX周期的起始位置需要启动另一个定时器，即第二定时器，其中，第一定时器和第二定时器同时运行。终端设备或网络设备可以确定在接收第三PDCCH的第三时刻，第二定时器未在运行，因此，在InactivityTimer超时的第四时刻，可以停止监测PDCCH，以节省终端设备侧的功耗。
在另一种实施方式中，上述第一条件中包括的第一定时器的起始时刻，还可以为终端设备在DRX周期内首次收到PDCCH的时刻。也就是，在某DRX周期内第一次收到PDCCH的时刻，启动第一定时器。
此时，第一定时器的时长可以与接入网设备向终端设备传输XR数据帧的PDB相关。例如，结合图8所示，接入网设备与终端设备之间的空口PDB为T4，第一定时器的时长可以设置为T4。
结合具体的实施例，如图11所示，终端设备在第二DRX周期内首次收到
PDCCH的时刻，启动第一定时器。若终端设备在第一DRX周期内收到PDCCH-1，接收PDCCH-1的时刻位于第一定时器的运行时间内，则该PDCCH-1触发的InactivityTime超时不会触发第一DRX周期的onDuration提前终止，即InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。
示例性的，如图11所示，若终端设备在第一DRX周期内首次收到PDCCH的时刻启动第一定时器，若终端设备在第三DRX周期内收到PDCCH-2，而接收PDCCH-2的时刻位于定时器超时之后，则PDCCH-2触发的InactivityTimer会触发第三DRX 周期的onDuration提前终止，即提前结束PDCCH监测以节省终端设备的功耗。
进一步的，若第一定时器的起始时刻为DRX周期内首次收到PDCCH的时刻，则如图11所示，终端设备在第二DRX周期内首次收到PDCCH的时刻，启动第二DRX周期对应的第一定时器，第一定时器超时后，且第一DRX周期的onDuration内首次收到PDCCH的时刻，启动(或重启)第一定时器。
以此类推，在第一DRX周期对应的第一定时器超时后，且第三DRX周期的onDuration内首次收到PDCCH的时刻，可以启动(或重启)第一定时器。其中，第三DRX周期为与第一DRX周期相邻的后一个DRX周期。
上述的几种实施方式，通过定义第一定时器，从而网络设备和终端设备都可以基于第一定时器是否在运行或超时作为判断条件，确定当前InactivityTimer超时所对应的PDCCH是当前DRX周期的XR数据帧还是前一个DRX的XR数据帧，从而确定是否能够提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。另外，当终端设备侧出现DCI丢失的情况下，终端设备侧也能与网络设备侧做出相同的判断，提高整体方案的鲁棒性。
在另一种实施方式中，上述步骤S503中的第一条件，具体可以包括：在第一时段内不活动定时器InactivityTimer未在运行。其中，第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。其中，第一时段的时长可以为预定义的或者为所述网络设备配置的。
也就是说，终端设备或网络设备可以判断，从第一DRX周期的onDuration的起始时刻倒推一定时长的第一时段内，若InactivityTimer未在运行，则表示该第一PDCCH承载的调度信息大概率是第一DRX周期内到达的XR数据帧的调度信息，而不是前一个DRX周期内到达的XR数据帧的调度信息，所以第一PDCCH触发的InactivityTimer超时时或超时后(即第一DRX周期内到达的XR数据帧完成了传输)，可以停止监测PDCCH；否则，若第一时段内，InactivityTimer正在运行，则该第一PDCCH承载的调度信息可能是第二DRX周期内到达的XR数据帧的调度信息，而不是第一DRX周期内到达的XR数据帧的调度信息，则不提前停止监测PDCCH，而是持续监测PDCCH，以接收后续的第一DRX周期内到达的XR数据帧的调度信息。
上述解决方式是考虑到，前一个DRX周期内到达的XR数据帧中可能存在传输完成较晚的XR数据帧，因此，若判断前一个DRX周期内到达的XR数据帧在临近下一个DRX周期的时刻还在传输，即在下一个DRX周期onDuration起始时刻前的预设时长(即前述的第一时段的时长)内仍有可能在传输，则确定在下一个DRX周期中不提前停止监测PDCCH。
其中，第一时段的时长可以为预先定义的，例如，可以预先定义第一时段的时长的具体值或者预先定义第一时段的时长与某些配置参数的取值(例如InactivityTimer的长度)相等；或者，第一时段的时长可以为网络设备配置的，例如，可以在网络设备向终端设备下发DRX配置信息的时候携带。本申请对具体的配置方式不做限定。
在一种实施方式中，第一时段的时长可以为InactivityTimer的时长。
也就是说，在第一DRX周期的onDuration的起始时刻之前的InactivityTimer时长内，若InactivityTimer未在运行，则第一PDCCH触发的InactivityTimer超时时或超时后，可以停止监测PDCCH；若InactivityTimer在运行，则不提前停止监测PDCCH，即第一PDCCH触发的InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。
进一步的，在一种实施方式中，第一条件具体可以包括：在第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行。
也就是说，终端设备或网络设备可以判断：若第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行，则可以在InactivityTimer超时时或超时后(第一DRX周期内接收的第一PDCCH触发的)，停止监测PDCCH。反之，若第一DRX周期的onDuration的起始时刻，InactivityTimer正在运行，则可以在InactivityTimer超时时或超时后(第一DRX周期内接收的第一PDCCH触发的)，不停止监测PDCCH，即InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。
但是，仅依据上述的第一条件判断停止监测PDCCH，在终端设备侧出现数据丢失的情况下，可能会导致终端设备和网络设备侧不对齐的情况。
示例性的，网络设备正常发送PDCCH-1，而终端设备侧未收到该PDCCH-1，则终端设备与网络设备侧的InactivityTimer运行状态会出现不对齐，如图12中所示。当终端设备在第一DRX周期接收到PDCCH-2，且PDCCH-2触发的InactivityTimer与第一DRX周期的onDuration有重叠。
如图12所示的方式1，若网络设备通过判断第一DRX周期的onDuration起始时刻InactivityTimer在运行，而确定不停止监测PDCCH；而终端设备通过判断第一DRX周期的onDuration起始时刻InactivityTimer未在运行，而确定停止监测PDCCH，从而导致终端设备和网络设备没有对齐，可能导致第一DRX周期内到达的XR数据帧传输失败。
为解决上述问题，可以将前述的两种第一条件进行结合，也就是说，终端设备或网络设备可以判断第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行；并且，第一DRX周期的onDuration起始时刻之前的InactivityTimer内，InactivityTimer未在运行，则第一PDCCH触发的InactivityTimer超时时或超时后，可以停止监测PDCCH。否则，不停止监测PDCCH，InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。
如图13所示的方式2，InactivityTimer超时的时刻为T1，第一DRX周期的onDuration起始时刻为T2，若T2-T1≤InactivityTimer时长，则确定在第一DRX周期内的InactivityTimer超时的时刻或超时后，不停止监测PDCCH，或者不提前停止onDuration定时器。
反之，若第一DRX周期的InactivityTimer停止时间足够早，即使终端设备发生PDCCH丢失的情况，该丢失的PDCCH触发的InactivityTimer也不会与第一DRX周期的onDuration重合。因此，可以判断第一DRX周期的onDuration的起始时刻，若InactivityTimer正在运行；或者第一DRX周期的onDuration起始时刻前的InactivityTimer时长内的任意时刻，InactivityTimer处于运行状态，则终端设备在第 一DRX周期中均不提前停止监测PDCCH。
可见，通过上述实施方式，网络设备和终端设备都可以基于第一条件，确定当前InactivityTimer超时所对应的PDCCH是当前DRX周期内到达的XR数据帧还是前一个DRX内到达的XR数据帧，从而确定是否能够提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。另外，当终端设备侧出现PDCCH丢失的情况下，终端设备侧也能与网络设备侧做出相同的判断，避免数据传输失败的问题。
在另一种实施方式中，还可以通过判断终端设备在前一个DRX周期内是否丢包，以此来作为确定InactivityTimer超时后是否可以在当前DRX周期内停止监测PDCCH的判断条件。
从而，上述步骤S503中的第一条件，具体可以包括：在第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行，并且终端设备在第二DRX周期内未丢失下行控制信息DCI。其中，第二DRX周期为与第一DRX周期相邻的前一个DRX周期。
也就是说，若判断终端设备在第二DRX周期内未丢失DCI，且第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行，则可以在InactivityTimer超时时或超时后(第一DRX周期内接收的第一PDCCH触发的)，停止监测PDCCH。反知，若判断终端设备在第二DRX周期内丢失DCI，且第一DRX周期的onDuration的起始时刻，InactivityTimer未在运行，则在InactivityTimer超时时或超时后(第一DRX周期内接收的第一PDCCH触发的)，不可以提前停止监测PDCCH，即InactivityTimer超时后OnDurationTimer未超时前仍监测PDCCH。
在一种实施方式中，终端设备可以根据某DRX周期内接收的混合自动重传请求(hybrid automatic repeat request，HARQ)进程号(HARQ process number，HPN)、新数据指示(new data indicator，NDI)和冗余版本(redundancy version，RV)确定在该DRX周期内是否丢失DCI。或者，终端设备还可以根据数据分配指示(data assignment indication，DAI)确定在某个DRX周期内是否丢失DCI。
其中，HPN用于指示HARQ进程的进程号。NDI用于指示数据是初传还是重传，具体的，可以通过NDI参数是否发生反转(toggled)来判断当前的数据是新传还是重传。其中，NDI反转是指NDI的值从上次的0变成本次为1，或者从上次的1变成本次为0。例如，基站为某个上行HARQ进程分配的DCI中NDI参数，与上次相比发生了反转，则表示终端设备本次可以进行上行新传；如果NDI参数与上次的相同，那么终端设备本次可以执行上行自适应重传。
RV的设计用于实现增量冗余(Incremental redundancy，IR)HARQ传输，即将编码器生成的冗余比特分成若干组，每个RV定义一个传输开始点，首次传输和各次HARQ重传分别使用不同的RV，以实现冗余比特的逐步积累，完成增量冗余HARQ操作。正常情况下，数据初传会使用RV＝0，重传会使用RV>0。
示例性的，根据DCI中携带的HPN、NDI和RV字段确定是否丢失DCI，具体包括：若同一HPN对应的NDI反转，且RV>0，则确定该DRX周期内存在丢失DCI的情况。
另外，在HARQ反馈采用动态码本的场景中，终端设备在反馈HARQ-确认(acknowledge，ACK)信息的时候，可以将多个物理下行共享信道(physical downlink shared channel，PDSCH)对应的HARQ-ACK信息承载于同一信息(如DCI)中进行反馈，即可以通过HARQ-ACK码本设计HARQ-ACK信息的数量，以及多个HARQ-ACK的顺序。
示例性的，终端设备在确定采用动态HARQ-ACK码本的情况下，终端设备接收的下行控制信息(downlink control information，DCI)包括数据分配指示(data assignment indication，DAI)字段。DAI字段指示被调度的数据包(即PDSCH)数量。该字段可以被理解为一个计数器，终端设备在反馈HARQ-ACK码本之前，DAI的计数结果指示了HARQ-ACK码本的比特数。例如3个时隙的HARQ-ACK信息要在同一个时隙反馈，每个时隙的DCI中DAI字段分别指示1/2/3，终端设备在反馈HARQ-ACK码本时，若最后一个DCI中DAI字段指示的取值等于3，则终端设备即可确定反馈HARQ-ACK码本的比特数为3。在另一种设计中，DAI字段可以进一步被分为计数DAI(counter DAI)和总数DAI(total DAI)，counter DAI与前面介绍的DAI的功能一致，即用来指示当前调度的是一次反馈之前的第几个数据包(或第几个PDSCH)。total DAI用于指示在一次反馈之前被调度的数据包(或第几个PDSCH)有多少个，通常在一次反馈之前，各个调度数据的DCI中包含的total DAI的取值相同。此时，可以根据total DAI指示的值确定HARQ-ACK码本的大小。若终端设备接收到的第一个DCI中的DAI字段(具体为counter DAI)指示的值大于0，则确定丢失DCI。
上述实施方式，网络设备和终端设备都可以基于第一条件，通过确定前一个DRX周期内是否发生丢包，从而确定当前InactivityTimer超时所对应的PDCCH是当前DRX周期的XR数据帧还是前一个DRX的XR数据帧，进而判断是否能够提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。另外，当终端设备侧出现DCI丢失的情况下，终端设备侧也能与网络设备侧做出相同的判断，避免数据传输失败的问题。
在另一种实施方式中，由于网络设备向终端设备发送XR数据帧的时候，知晓该XR数据帧属于哪个DRX周期内到达的XR数据帧，因此，可以通过网络设备向终端设备发送指示，用于指示是否可以在InactivityTimer超时后停止监测PDCCH或者停止运行onDuration定时器，或者，指示当前调度或传输的XR数据帧是否是前一个DRX周期内已被调度的数据属于同一帧数据。
上述步骤S503中的第一条件，具体可以包括：网络设备在第一DRX周期内向终端设备发送第一指示信息，其中，第一指示信息可以用于指示终端设备在
InactivityTimer超时时或超时后停止监测PDCCH，或者，指示终端设备在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，该第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
相对应的，终端设备在第一DRX周期内接收来自网络设备的第一指示信息。
在一种实施方式中，第一指示信息可以通过一个特定的比特位来实现指示。例 如，该比特位值为1，用于指示第一指示信息，即在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示终端设备在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，该第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。反之，若该比特位值为0，用于指示第二指示信息，即在InactivityTimer超时时或超时后不停止监测PDCCH，或者，指示终端设备在InactivityTimer超时时或超时后不停止onDuration定时器的运行，或者，该第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据不属于同一帧数据。
在一种实施方式中，第一指示信息或第二指示信息可以承载于PDCCH中，或者PDCCH的DCI中。示例性的，若第一指示信息承载于第二PDCCH内，则第一数据为第二PDCCH调度的数据。也就是说，网络设备可以通过在PDCCH中携带第一指示信息，用于向终端设备指示该PDCCH调度的数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在另一种实施方式中，第一指示信息或第二指示信息可以承载于PDSCH中，或者，PDSCH的高层控制信令中，例如媒体接入控制(Medium Access Control，MAC)的控制单元(control element，CE)或无线资源控制(Radio Resource Control，RRC)信令等。
示例性的，若第一指示信息承载于第一PDSCH内，则第一数据为第一PDSCH携带的数据。也就是说，网络设备可以通过在PDSCH中携带第一指示信息，用于向终端设备指示该PDSCH传输的数据与前一个DRX周期内已被调度的数据属于同一帧数据。
上述实施方式，终端设备可以基于来自网络设备的指示信息，确定是否可以在当前InactivityTimer超时时提前终止PDCCH的监测，以达到节省终端设备功耗的目的，避免了过早停止监测PDCCH导致数据传输失败的问题，不影响数据传输效率。
可以理解的，本申请实施例中同一个步骤或者具有相同功能的步骤或者消息在不同实施例之间可以互相参考借鉴。
基于上述的各实施方式，本申请还提供一种通信装置，该通信装置可以是终端设备。该通信装置具有实现上述各个可能的实施方式中的终端设备的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例还提供一种通信装置，如图14所示，该通信装置1400包括收发模块1401和处理模块1402。
其中，收发模块1401可以用于在第一DRX周期接收第一PDCCH。
处理模块1402可以用于，若满足第一条件，则在第一时刻停止监测物理下行控制信道PDCCH。其中，第一时刻为第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述通信装置1400在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时 刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：在第一时段内不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述通信装置1400在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：所述通信装置1400在所述第一DRX周期内接收来自网络设备的第一指示信息，所述第一指示信息用于指示所述通信装置1400在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示所述通信装置1400在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由网络设备配置的。
在一种实施方式中，处理模块1402还可以用于，在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器。
收发模块1401还用于在第三DRX周期接收第三PDCCH。
处理模块1402还可以用于，若在第三时刻，第二定时器未在运行或者已超时，则在第四时刻停止监测物理下行控制信道PDCCH。其中，第三DRX周期为与第一DRX周期相邻的后一个DRX周期，第三时刻为接收所述第三PDCCH的时刻，第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，处理模块1402还可以用于，若第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述通信装置1400在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，处理模块1402还可以用于，根据以下至少一种信息，确定在所述第二DRX周期内丢失DCI：所述第二DRX周期内接收的HARQ进程号HPN、新数据指示NDI和冗余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
具体的，该通信装置1400可以实现上述各个可能的实施方式中的终端设备的功能，具体可以参见前述各个方法示例中的详细描述，此处不做赘述。
另外，本申请还提供一种通信装置，该通信装置可以是网络设备。该通信装置具有实现上述各个可能的实施方式中的网络设备的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，如图14所示，该通信装置1400包括收发模块1401和处理模块1402。
其中，收发模块1401用于在第一DRX周期向终端设备发送第一PDCCH。
处理模块1402用于，若满足第一条件，则在第一时刻停止监测物理下行控制信道PDCCH。其中，第一时刻为第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻。
在一种实施方式中，第一条件包括：在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：在第一时段内不活动定时器InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻。
在一种实施方式中，第一时段的时长为所述InactivityTimer的时长。
在一种实施方式中，第一条件包括：在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期。
在一种实施方式中，第一条件包括：所述通信装置1400在所述第一DRX周期内向所述终端设备发送第一指示信息，所述第一指示信息用于指示在InactivityTimer超时时或超时后停止监测PDCCH，或者，指示在InactivityTimer超时时或超时后停止onDuration定时器的运行，或者，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
在一种实施方式中，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
在一种实施方式中，第一定时器的时长为预配置的，或者，所述第一定时器的时长是由所述通信装置1400配置的。
在一种实施方式中，处理模块1402还用于，在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述终端设备的所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器。
收发模块1401还用于在第三DRX周期向所述终端设备发送第三PDCCH。
处理模块1402还用于，若在第三时刻，第二定时器未在运行或者已超时，则在第四时刻停止监测物理下行控制信道PDCCH。其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为所述终端设备接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
在一种实施方式中，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
在一种实施方式中，第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
在一种实施方式中，处理模块1402还用于根据以下至少一种信息，确定所述终端设备在所述第二DRX周期内丢失DCI：所述第二DRX周期内的HARQ进程号HPN、新数据指示NDI和冗余版本RV；或者，数据分配指示DAI。
在一种实施方式中，停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
具体的，该通信装置1400可以实现上述各个可能的实施方式中的网络设备的功能，具体可以参见前述各个方法示例中的详细描述，此处不做赘述。
可以理解的，结合图2所示，当上述装置是电子设备时，上述的传输模块可以是收发器，可以包括天线和射频电路等，处理模块可以是处理器，例如基带芯片等。当该装置是具有上述实施例中的第一通信设备和/或第二通信设备功能的部件时，传输模块可以是射频单元，处理模块可以是处理器。当装置是芯片系统时，传输模块可以是芯片系统的输入接口和/或输出接口，处理模块可以是芯片系统的处理器，例如：中央处理单元(central processing unit，CPU)。
需要说明的是，上述装置中具体的执行过程和实施例可以参照上述方法实施例中终端设备或者网络设备执行的步骤和相关的描述，所解决的技术问题和带来的技术效果也可以参照前述实施例所述的内容，此处不再一一赘述。
在本实施例中，该装置以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路、和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该侧行链路的传输装置可以采用如前述中的图2所示的形式。
示例性的，图14中的处理模块1402的功能/实现过程可以通过图2中的处理器201调用存储器204中存储的计算机程序指令来实现。例如，图14中收发模块1401的功能/实现过程可以通过图2中的通信接口203。
在一些实施方式中，图2中的处理器201可以通过调用存储器204中存储的计算机执行指令，使得装置200可以执行上述各个方法实施例中的终端设备或者网络设备的操作，实现本申请的上述各个可能的实施方法。
上述各个装置实施例中的通信装置可以与方法实施例中的终端设备或者网络设备完全对应，由相应的模块或者单元执行相应的步骤，例如，当该装置以芯片的方式实 现时，该收发单元可以是该芯片用于从其他芯片或者装置接收信号的接口电路。以上用于发送或接收的收发模块是一种该装置的接口电路，用于向其他装置发送信号，例如，当该装置以芯片的方式实现时，该收发模块可以是用于向其他芯片或者装置发送信号的接口电路。
在示例性实施例中，还提供了一种包括指令的计算机可读存储介质，或者计算机程序产品，上述指令可由通信装置200的处理器201执行以完成上述实施例的方法。因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
本申请还提供了一种计算机程序产品，该计算机程序产品包括指令，当该指令被执行时，以使得该计算机分别可以执行对应于上述方法的终端设备或者网络设备的操作。
本申请实施例还提供了一种系统芯片，该系统芯片包括：处理单元和通信单元，该处理单元，例如可以是处理器，该通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行计算机指令，以使该芯片所应用的通信装置执行上述本申请实施例提供的方法中的终端设备和网络设备的操作。
可选地，上述本申请实施例中提供的任意一种通信装置可以包括该系统芯片。
可选地，该计算机指令被存储在存储单元中。
本申请实施例还提供了一种通信系统，该通信系统可以包括：上述的实施方式中的任一种终端设备和网络设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。
最后应说明的是：以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种非连续接收的配置方法，其特征在于，所述方法包括：
    终端设备在第一DRX周期接收第一PDCCH；
    若满足第一条件，则所述终端设备在第一时刻停止监测物理下行控制信道PDCCH；
    其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻；
    所述第一条件包括：
    在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期；或者，
    在第一时段内所述InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻；或者，
    在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期；或者，
    所述终端设备在所述第一DRX周期内接收来自网络设备的第一指示信息，所述第一指示信息用于指示所述终端设备在所述InactivityTimer超时时或超时后停止监测PDCCH，或，指示所述终端设备在所述InactivityTimer超时时或超时后停止onDuration定时器的运行，或，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一时段的时长为所述InactivityTimer的时长。
  3. 根据权利要求1所述的方法，其特征在于，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，
    若所述第一指示信息承载于第一物理下行共享信道PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
  4. 根据权利要求1所述的方法，其特征在于，所述第一定时器的时长为预配置的，或者，所述第一定时器的时长是由网络设备配置的。
  5. 根据权利要求1或4所述的方法，其特征在于，
    所述终端设备在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；
    在第三DRX周期接收第三PDCCH；
    若在第三时刻，所述第二定时器未在运行或者已超时，则所述终端设备在第四时刻停止监测物理下行控制信道PDCCH；
    其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所 述第三时刻为接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
  6. 根据权利要求1、4或5所述的方法，其特征在于，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则所述终端设备在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
  7. 根据权利要求1或2所述的方法，其特征在于，所述第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
  8. 根据权利要求1所述的方法，其特征在于，所述终端设备在所述第二DRX周期内丢失DCI，根据以下至少一种信息确定：
    所述第二DRX周期内接收的HARQ进程号HPN、新数据指示NDI和冗余版本RV；
    或者，数据分配指示DAI。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述停止监测物理下行控制信道PDCCH，包括：停止所述第一DRX周期的onDuration定时器的运行。
  10. 一种非连续接收的配置方法，其特征在于，所述方法包括：
    网络设备在第一DRX周期向终端设备发送第一PDCCH；
    若满足第一条件，则在第一时刻停止监测物理下行控制信道PDCCH；
    其中，所述第一时刻为所述第一PDCCH触发的不活动定时器InactivityTimer超时的时刻或者超时后的时刻；
    所述第一条件包括：
    在第二时刻，第一定时器未在运行或者已超时，其中，所述第二时刻为所述终端设备在所述第一DRX周期内接收所述第一PDCCH的时刻，所述第一定时器的起始时刻为第二DRX周期的持续时长onDuration的起始时刻或者结束时刻，或者，在所述第二DRX周期内首次收到PDCCH的时刻；其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期；或者，
    在第一时段内所述InactivityTimer未在运行，其中，所述第一时段的结束时刻为第一DRX周期的onDuration的起始时刻；或者，
    在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行，并且所述终端设备在第二DRX周期内未丢失下行控制信息DCI，其中，所述第二DRX周期为与所述第一DRX周期相邻的前一个DRX周期；或者，
    所述网络设备在所述第一DRX周期内向所述终端设备发送第一指示信息，所述第一指示信息用于指示所述终端设备在所述InactivityTimer超时时或超时后停止监测PDCCH，或，指示所述终端设备在所述InactivityTimer超时时或超时后停止onDuration定时器的运行，或，所述第一指示信息指示的第一数据与前一个DRX周期内已被调度的数据属于同一帧数据。
  11. 根据权利要求10所述的方法，其特征在于，所述第一时段的时长为所述 InactivityTimer的时长。
  12. 根据权利要求10所述的方法，其特征在于，若所述第一指示信息承载于第二PDCCH内，则所述第一数据为所述第二PDCCH调度的数据；或者，
    若所述第一指示信息承载于第一PDSCH内，则所述第一数据为所述第一PDSCH携带的数据。
  13. 根据权利要求10所述的方法，其特征在于，
    在所述第一DRX周期的onDuration的起始时刻或者结束时刻，或者，在所述终端设备的所述第一DRX周期内首次收到PDCCH的时刻，启动第二定时器；
    在第三DRX周期向所述终端设备发送第三PDCCH；
    若在第三时刻，所述第二定时器未在运行或者已超时，则在第四时刻停止监测物理下行控制信道PDCCH；
    其中，所述第三DRX周期为与所述第一DRX周期相邻的后一个DRX周期，所述第三时刻为所述终端设备接收所述第三PDCCH的时刻，所述第四时刻为所述第三PDCCH触发的InactivityTimer超时的时刻或者超时后的时刻，所述第二定时器为与所述第一定时器不同的定时器，所述第二定时器的时长与所述第一定时器的时长相同。
  14. 根据权利要求10或13所述的方法，其特征在于，若所述第一定时器的起始时刻为所述第二DRX周期内首次收到PDCCH的时刻，则在所述第一定时器超时后，且所述第一DRX周期的onDuration内首次收到PDCCH的时刻启动所述第一定时器。
  15. 根据权利要求10或11所述的方法，其特征在于，所述第一条件还包括：所述终端设备在所述第一DRX周期的onDuration的起始时刻，所述InactivityTimer未在运行。
  16. 根据权利要求10所述的方法，其特征在于，所述终端设备在所述第二DRX周期内丢失DCI，根据以下至少一种信息确定：
    所述第二DRX周期内的HARQ进程号HPN、新数据指示NDI和冗余版本RV；
    或者，数据分配指示DAI。
  17. 一种终端设备，其特征在于，所述终端设备包括处理器和与所述处理器耦合的存储器；所述存储器存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述处理器执行所述计算机指令时，使得所述终端设备执行如权利要求1-9中任一项所述的方法。
  18. 一种网络设备，其特征在于，所述网络设备包括处理器和与所述处理器耦合的存储器；所述存储器与所述处理器耦合，所述存储器存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述处理器执行所述计算机指令时，使得所述网络设备执行如权利要求10-16中任一项所述的方法。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时，使得所述计算机执行如权利要求1-9中任一项所述的方法，或者执行如权利要求10-16中任一项所述的方法。
  20. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1-9中任一项所述的方法，或者执行如权利要求10-16中任一项所述的方法。
  21. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-9中任一项所述的方法，或者实现如权利要求10-16中任一项所述的方法。
  22. 一种通信系统，其特征在于，所述通信系统包括如权利要求17所述的终端设备和如权利要求18所述的网络设备。
PCT/CN2023/100245 2022-06-27 2023-06-14 一种非连续接收的配置方法及装置 WO2024001790A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210743794.5 2022-06-27
CN202210743794 2022-06-27
CN202210890313.3 2022-07-27
CN202210890313.3A CN117354900A (zh) 2022-06-27 2022-07-27 一种非连续接收的配置方法及装置

Publications (1)

Publication Number Publication Date
WO2024001790A1 true WO2024001790A1 (zh) 2024-01-04

Family

ID=89360120

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/100245 WO2024001790A1 (zh) 2022-06-27 2023-06-14 一种非连续接收的配置方法及装置

Country Status (2)

Country Link
CN (1) CN117354900A (zh)
WO (1) WO2024001790A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111418223A (zh) * 2017-12-27 2020-07-14 Oppo广东移动通信有限公司 管理定时器的方法和终端设备
CN113475142A (zh) * 2019-07-16 2021-10-01 Oppo广东移动通信有限公司 Drx定时器控制方法、装置、终端及存储介质
US20210329560A1 (en) * 2019-01-11 2021-10-21 Huawei Technologies Co., Ltd. Communication method and apparatus
EP4009713A1 (en) * 2019-08-02 2022-06-08 Huawei Technologies Co., Ltd. Communication method and apparatus
CN115226187A (zh) * 2021-04-20 2022-10-21 华为技术有限公司 一种非连续接收的配置方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111418223A (zh) * 2017-12-27 2020-07-14 Oppo广东移动通信有限公司 管理定时器的方法和终端设备
US20210329560A1 (en) * 2019-01-11 2021-10-21 Huawei Technologies Co., Ltd. Communication method and apparatus
CN113475142A (zh) * 2019-07-16 2021-10-01 Oppo广东移动通信有限公司 Drx定时器控制方法、装置、终端及存储介质
EP4009713A1 (en) * 2019-08-02 2022-06-08 Huawei Technologies Co., Ltd. Communication method and apparatus
CN115226187A (zh) * 2021-04-20 2022-10-21 华为技术有限公司 一种非连续接收的配置方法及装置

Also Published As

Publication number Publication date
CN117354900A (zh) 2024-01-05

Similar Documents

Publication Publication Date Title
WO2022083769A1 (zh) 一种数据传输方法、装置及终端
WO2021031934A1 (zh) 边链路非连续发送、接收方法与装置及终端设备
WO2019192342A1 (zh) 非连续接收的通信方法、装置、通信设备和通信系统
US11451345B2 (en) Data transmission method, terminal, and RAN device
EP2169871B1 (en) Method and apparatus of handling a timer for triggering buffer status report
US10342063B2 (en) Activation of DRX parameters
JP4954189B2 (ja) 無線通信システムにおいて不連続受信機能を改善する方法及び装置
CN109756996B (zh) Drx配置下的上行传输方法及装置、设备、存储介质
WO2020168458A1 (zh) Drx定时器的运行方法、装置、设备及存储介质
WO2013020417A1 (zh) 一种非连续接收方法及系统
WO2021026918A1 (zh) 下行控制信息的监听方法及装置
WO2020063782A1 (zh) 一种通信方法及装置
WO2012167629A1 (zh) Drx模式下终端保持上行同步的处理方法及装置
US20240049347A1 (en) Discontinuous reception configuration method and apparatus
WO2024001790A1 (zh) 一种非连续接收的配置方法及装置
US8233909B2 (en) Reception cycle control method, radio base station, and mobile station
WO2021204077A1 (zh) 设置drx的活动态的方法、装置、用户设备及存储介质
CN113365326B (zh) 资源调度方法、装置、设备及存储介质
WO2023246588A1 (zh) 一种通信方法及装置
WO2022267844A1 (zh) 一种通信方法及装置
WO2023165449A1 (zh) 一种通信方法及装置
WO2024032077A1 (zh) 上行传输方法和通信装置
WO2022205479A1 (zh) 定时器状态更改方法、装置、终端及存储介质
WO2022082806A1 (zh) 无线通信的方法和装置
WO2023207568A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23829972

Country of ref document: EP

Kind code of ref document: A1