WO2023165449A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023165449A1
WO2023165449A1 PCT/CN2023/078525 CN2023078525W WO2023165449A1 WO 2023165449 A1 WO2023165449 A1 WO 2023165449A1 CN 2023078525 W CN2023078525 W CN 2023078525W WO 2023165449 A1 WO2023165449 A1 WO 2023165449A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
terminal device
network device
drx
inactivity timer
Prior art date
Application number
PCT/CN2023/078525
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
Priority claimed from CN202210397041.3A external-priority patent/CN116761236A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023165449A1 publication Critical patent/WO2023165449A1/zh

Links

Classifications

    • 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

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method and device.
  • the network device Before data transmission between the network device and the terminal device, the network device will send data scheduling information, such as PDCCH, to the terminal device.
  • data scheduling information such as PDCCH
  • the terminal device In order to avoid losing the scheduling information, the terminal device needs to monitor the PDCCH frequently according to the configuration of the network device.
  • frequent monitoring of the PDCCH by the terminal equipment will result in high power consumption of the terminal equipment.
  • research on power saving of terminal equipment is becoming more and more common, and detailed optimization schemes for reducing power consumption of terminal equipment have become a research direction in the industry.
  • the present application provides a communication method and device for reducing power consumption of terminal equipment.
  • the present application provides a communication method, which may include: after a terminal device receives first downlink control information (downlink control information, DCI) from a network device, determine the first downlink control information (DCI) according to the first DCI Not monitoring the PDCCH within a period of time; wherein, the first DCI is used to schedule stuffing data packets, and the first DCI instructs the terminal device not to monitor the Physical Downlink Control Channel PDCCH within the first period of time.
  • DCI downlink control information
  • DCI downlink control information
  • the network device can instruct the terminal device not to monitor the PDCCH within the first duration by scheduling the DCI filling the data packet, thereby reducing the power consumption of the terminal device.
  • the first DCI is used to schedule a physical downlink shared channel (physical downlink shared channel, PDSCH).
  • the first DCI may instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first duration by scheduling the downlink filling data packet.
  • the first DCI is DCI format 1_1 or DCI format 1_2 scrambled by a cell-radio network temporary identity (C-RNTI); or, the first DCI is modulated DCI format 1_1 or DCI format 1_2 scrambled by a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI) coding method; or, the first DCI is a configuration scheduling wireless network DCI format 1_1 or DCI format 1_2 scrambled by a configured scheduling-radio network temporary identity (CS-RNTI).
  • C-RNTI cell-radio network temporary identity
  • MCS-C-RNTI modulation and coding scheme-cell-radio network temporary identifier
  • the terminal device receives a PDSCH from the network device, the PDSCH includes a media access control sub protocol data unit (media access control sub protocol data unit, MAC sub PDU), and the corresponding Logical channel identify (LCID).
  • media access control sub protocol data unit media access control sub protocol data unit, MAC sub PDU
  • LCID Logical channel identify
  • the first DCI is used to schedule a physical uplink shared channel (physical uplink shared channel, PUSCH).
  • the first DCI may instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first duration by scheduling the uplink filling data packet.
  • the first DCI is the DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the modulation and coding mode cell-specific radio network temporary identifier MCS - DCI format 0_1 or DCI format 0_2 with C-RNTI scrambling; or, the first DCI is DCI format 0_1 or DCI format 0_2 configured with CS-RNTI scrambling.
  • the first DCI can be flexibly implemented through the uplink DCI.
  • the terminal device sends a physical uplink shared channel PUSCH to the network device, the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier corresponding to the MAC sub PDU
  • the value of LCID is 63.
  • the terminal device sends a PUSCH to the network device, where the PUSCH includes the padding data packet; furthermore, the terminal device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, When the DRX-inactivity timer is running, the terminal device does not restart or stop the DRX-inactivity timer. In this way, the active time of the terminal device can be avoided, thereby saving the power consumption of the terminal device.
  • the terminal device when the terminal device is configured with an uplink skip function, the terminal device does not send the physical uplink shared channel PUSCH to the network device. In this way, the terminal device does not need to send any data packets to the network device, so as to save power consumption of the terminal device.
  • the terminal device when the terminal device does not send PUSCH to the network device, the terminal device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running , the terminal device does not restart or stop the DRX-inactivity timer. In this way, the active time of the terminal device can be avoided, thereby saving the power consumption of the terminal device.
  • the terminal device receives a PDSCH from the network device, where the PDSCH includes the padding data packet; furthermore, the terminal device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or , when the DRX-inactivity timer is running, the terminal device does not restart or stop the DRX-inactivity timer. In this way, the active time of the terminal device can be avoided, thereby saving the power consumption of the terminal device.
  • the value of the new data indicator (new data indicator, NDI) field in the first DCI is the same as the value of the NDI field in the second DCI, and the second DCI is the same as the first
  • the value of the hybrid automatic repeat request (hybrid automatic repeat request, HARQ) process number (HARQ process number, HPN) field of DCI is the same as that of the previous DCI.
  • the terminal device before the terminal device receives the first DCI from the network device, it receives the second DCI from the network device, and sends correct response ACK information to the network device. In this way, the subsequent terminal device can recognize the filling data packet, and then does not start, restart or stop the DRX-inactivity timer.
  • the value of the NDI field in the first DCI is different from the value of the NDI field in the third DCI
  • the third DCI is different from the HARQ process number HPN field of the first DCI The previous DCI with the same value.
  • the present application provides a communication method, which may include: a network device determines a first DCI, and sends the first DCI to the terminal device, where the first DCI is used to schedule padding packets , the first DCI instructs the terminal device not to monitor the physical downlink control channel PDCCH within the first duration.
  • the network device can instruct the terminal device not to monitor the PDCCH within the first duration by scheduling the DCI filling the data packet, thereby reducing the power consumption of the terminal device.
  • the network device determines that no traffic arrives at the terminal device within a preset time period; or, the network device determines There is no cached data corresponding to the terminal device. In this way, the network device can determine that no service arrives at the terminal device, and then send the first DCI to the terminal device.
  • the preset duration is a period of time before the network device sends the first DCI, or the preset duration is a period of time after the network device sends the first DCI, Or the preset duration is the moment when the network device sends the first DCI.
  • the first DCI is used for the PDSCH.
  • the first DCI may instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first duration by scheduling the downlink filling data packet.
  • the first DCI is the DCI format 1_1 or DCI format 1_2 scrambled by the cell wireless network temporary identifier C-RNTI; or, the first DCI is the modulation and coding mode cell-specific wireless network temporary identifier MCS - DCI format 1_1 or DCI format 1_2 of C-RNTI scrambling; or, the first DCI is DCI format 1_1 or DCI format 1_2 of configuring scheduling radio network temporary identifier CS-RNTI scrambling.
  • the first DCI can be flexibly implemented through the downlink DCI.
  • the network device sends the physical downlink shared channel PDSCH to the terminal device, the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier corresponding to the MAC sub PDU
  • the value of LCID is 63.
  • the first DCI is used to schedule the PUSCH.
  • the first DCI may instruct the terminal device not to monitor the physical downlink control channel PDCCH within the first duration by scheduling the uplink filling data packet.
  • the first DCI is the DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the modulation and coding mode cell-specific radio network temporary identifier MCS - DCI format 0_1 or DCI format 0_2 with C-RNTI scrambling; or, the first DCI is DCI format 0_1 or DCI format 0_2 configured with CS-RNTI scrambling.
  • the first DCI can be flexibly implemented through the uplink DCI.
  • the network device receives a physical uplink shared channel PUSCH from the terminal device, the PUSCH includes a media access control sub-protocol data unit MAC sub PDU, and a logical channel identifier corresponding to the MAC sub PDU
  • the value of LCID is 63.
  • the network device when the terminal device is configured with an uplink skip function, the network device does not receive the PUSCH from the terminal device. In this way, the terminal device does not need to send any data packets to the network device, so as to save power consumption of the terminal device.
  • the network device receives a physical uplink shared channel PUSCH from the terminal device, Wherein the PUSCH contains the filling data packet; furthermore, the network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop The DRX-inactivity timer. In this way, the active time of the terminal device can be avoided from being extended, thereby saving the power consumption of the terminal device.
  • the network device does not receive the physical uplink shared channel PUSCH sent by the terminal device at the position indicated by the first DCI; furthermore, the network device does not start the discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device does not restart or stop the DRX-inactivity timer. In this way, the active time of the terminal device can be avoided, thereby saving the power consumption of the terminal device.
  • the network device sends a physical downlink shared channel PDSCH to the terminal device, where the PDSCH includes the padding data packet; furthermore, the network device does not start the discontinuous reception inactivity timer DRX -inactivitytimer; or, when the DRX-inactivitytimer is running, the network device does not restart or stop the DRX-inactivitytimer. In this way, the active time of the terminal device can be avoided, thereby saving the power consumption of the terminal device.
  • the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI
  • the second DCI is a hybrid automatic retransmission with the first DCI Request the previous DCI with the same value of the HARQ process number HPN field.
  • the network device may not start, restart or stop the DRX-inactivity timer, so as to avoid prolonging the active time of the terminal device, thereby saving power consumption of the terminal device.
  • the method before the network device sends the first DCI to the terminal device, the method further includes: after the network device sends the second DCI to the terminal device, from The terminal device receives the correct response ACK information. In this way, the terminal device can subsequently recognize the filling data packet, and then does not start, restart or stop the DRX-inactivity timer.
  • the new data in the first DCI indicates that the value of the NDI field is different from the value of the NDI field in the third DCI
  • the third DCI is a hybrid automatic repeater with the first DCI.
  • the value of the HPN field of the requested HARQ process number is the same as that of the previous DCI.
  • the present application provides a communication method, which may include: after a terminal device receives a downlink filling data packet from a network device, determining a first operation of the terminal device according to the downlink filling data packet. In this way, the terminal device can trigger the first operation of the terminal device after receiving the downlink filling data packet, so as to save power consumption of the terminal device.
  • the terminal device receives the downlink filling data packet from the network device, and the method may be: the terminal device receives a physical downlink shared channel PDSCH from the network device, and the PDSCH contains media Access control sub-protocol data unit MAC sub PDU, the value of the logical channel identifier LCID corresponding to the MAC sub PDU is 63. In this way, the terminal device can receive accurate downlink filling data packets.
  • the first operation is that the terminal device does not monitor a Physical Downlink Control Channel (PDCCH) within a second duration.
  • PDCCH Physical Downlink Control Channel
  • the terminal device receives downlink control information DCI from the network device, the DCI is used to schedule the downlink filling data packet, and the DCI indicates that the terminal device receives the downlink filling data packet after packet
  • the PDCCH is not monitored within the second duration.
  • the network device can trigger the terminal device not to monitor the PDCCH by scheduling downlink filling data packets.
  • the DCI is DCI format 1_0.
  • the first operation is that the terminal device does not start a discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the first operation is that the terminal device The device does not reboot or stop the DRX-inactivitytimer. In this way, after the terminal device receives the downlink filling data packet, by not starting the DRX-inactivity timer, or not restarting or stopping the running DRX-inactivity timer, the activation time of the terminal device can be avoided, thereby reducing the work of the terminal device. consumption.
  • the present application provides a communication method, which may include: a network device sending a downlink filling data packet to a terminal device, and determining that the terminal device does not monitor a physical downlink control channel PDCCH within a second duration. In this way, the terminal device can be triggered not to monitor the PDCCH for a period of time by sending a downlink filling data packet to the terminal device, thereby saving power consumption of the terminal device.
  • the network device sends the downlink filling data packet to the terminal device
  • the method may be: the network device sends a physical downlink shared channel PDSCH to the terminal device, and the PDSCH includes a media interface Incoming control sub-protocol data unit MAC sub-PDU, the value of the logical channel identifier LCID corresponding to the MAC sub-PDU is 63. In this way, the network device can send accurate downlink filling data packets.
  • the network device sends downlink control information DCI to the terminal device, the DCI is used to schedule the downlink filling data packet, and the DCI indicates that the terminal device receives the downlink filling data packet
  • the PDCCH is not monitored within the second duration after the data packet. In this way, the network device can trigger the terminal device not to monitor the PDCCH by scheduling downlink filling data packets.
  • the DCI is DCI format 1_0.
  • the present application provides a communication method, which may include: the network device sends a downlink filling data packet to the terminal device, and the network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the When the DRX-inactivity timer is running, the network device does not restart or stop the DRX-inactivity timer.
  • the network device sends a downlink filling data packet to the terminal device, and the network device does not start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the When the DRX-inactivity timer is running, the network device does not restart or stop the DRX-inactivity timer.
  • the network device sends the downlink filling data packet to the terminal device
  • the method may be: the network device sends a physical downlink shared channel PDSCH to the terminal device, and the PDSCH includes a media interface Incoming control sub-protocol data unit MAC sub-PDU, the value of the logical channel identifier LCID corresponding to the MAC sub-PDU is 63. In this way, the network device can send accurate downlink filling data packets.
  • the present application also provides a communication device, which may be a terminal device, and the communication device has various possible design examples for realizing the above first aspect or the first aspect, or the above third aspect or Functions of methods in various possible design examples of the third aspect.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a transceiver unit and a processing unit, and these units can implement the above-mentioned first aspect or each possible design example of the first aspect, or the above-mentioned third aspect or the third aspect
  • these units can implement the above-mentioned first aspect or each possible design example of the first aspect, or the above-mentioned third aspect or the third aspect
  • the structure of the communication device includes a transceiver and a processor, and optionally also includes a memory, and the transceiver is used to send and receive information or data, and to communicate with other devices in the communication system interact,
  • the processor is configured to support the communication device to execute corresponding functions in the above first aspect or each possible design example of the first aspect, or the above third aspect or each possible design example of the third aspect.
  • the memory coupled to the processor, holds program instructions and data necessary for the communication device.
  • the present application also provides a communication device, which may be a network device, and the communication device has various possible design examples for realizing the above-mentioned second aspect or the second aspect, the above-mentioned fourth aspect or the first In each possible design example of the fourth aspect, the above fifth aspect or the function of the method in each possible design example of the fifth aspect.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the structure of the communication device includes a transceiver unit and a processing unit, and these units can implement the above-mentioned second aspect or each possible design example of the second aspect, the above-mentioned fourth aspect or the In each possible design example, for the fifth aspect or the corresponding functions in each possible design example of the fifth aspect, refer to the detailed description in the method example for details, and details are not repeated here.
  • the structure of the communication device includes a transceiver and a processor, and optionally also includes a memory, and the transceiver is used to send and receive information or data, and to communicate with other devices in the communication system Interaction, the processor is configured to support the communication device to execute the above-mentioned second aspect or each possible design example of the second aspect, the above-mentioned fourth aspect or each possible design example of the fourth aspect, the above-mentioned fifth aspect Corresponding functions in each possible design example of the aspect or the fifth aspect.
  • the memory coupled to the processor, holds program instructions and data necessary for the communication device.
  • the embodiment of the present application provides a communication system, which may include the terminal device and network device mentioned above.
  • the embodiments of the present application provide a computer-readable storage medium, the computer-readable storage medium stores program instructions, and when the program instructions are run on the computer, the computer executes the first aspect and its In any possible design, or the method described in the second aspect and any possible design thereof.
  • Exemplary, computer readable storage media may be any available media that can be accessed by a computer.
  • computer readable media may include non-transitory computer readable media, random-access memory (random-access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable Except for electrically programmable read-only memory (electrically EPROM, EEPROM), CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage device, or can be used to carry or store the desired program code in the form of instruction or data structure and can Any other media accessed by a computer.
  • random-access memory random-access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • the embodiment of the present application provides a computer program product, including computer program codes or instructions, when the computer program codes or instructions are run on a computer, the above first aspect or any possible design of the first aspect , or the method described in the above second aspect or any possible design of the second aspect is executed.
  • the present application also provides a chip, including a processor, the processor is coupled to a memory, and is used to read and execute program instructions stored in the memory, so that the chip realizes the above-mentioned first
  • the processor is coupled to a memory, and is used to read and execute program instructions stored in the memory, so that the chip realizes the above-mentioned first
  • the fourth aspect or any possible design of the fourth aspect, or the method described in the fifth aspect or any possible design of the fifth aspect are possible design of the fifth aspect.
  • FIG. 1 is a schematic structural diagram of a communication system provided by the present application.
  • FIG. 2 is a schematic diagram of skipping PDCCH monitoring provided by the present application.
  • FIG. 3 is a schematic diagram of a network device using scheduling DCI to indicate PDCCH skipping provided by the present application
  • FIG. 4 is a flowchart of a communication method provided by the present application.
  • FIG. 5 is a schematic diagram of a network device indicating PDCCH skipping by scheduling the first DCI of the filling data packet provided by the present application;
  • Fig. 6 is a schematic diagram that a MAC PDU provided by this application includes one or more MAC sub PDUs;
  • FIG. 7 is a schematic diagram of a CDRX cycle provided by the present application.
  • FIG. 8 is a schematic diagram of a network device instructing a terminal device configured with CDRX not to monitor the PDCCH for a period of time provided by the present application;
  • FIG. 9 is a flowchart of another communication method provided by the present application.
  • FIG. 10 is a flowchart of another communication method provided by the present application.
  • FIG. 11 is a schematic structural diagram of a communication device provided by the present application.
  • FIG. 12 is a structural diagram of a communication device provided by the present application.
  • Embodiments of the present application provide a communication method and device, so as to reduce power consumption of terminal equipment.
  • the method and the device described in this application are based on the same technical concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • At least one (species) refers to one (species) or multiple (species), and multiple (species) refers to two (species) or more than two (species).
  • Figure 1 shows the architecture of the communication system involved in the embodiment of the present application, the architecture of the communication system includes network equipment and terminal equipment, where:
  • the network device is a device with a wireless transceiver function or a chip that can be set on the network device, and the network device includes but is not limited to: a base station (generation node B, gNB), a radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless fidelity (wireless fidelity, Wi-Fi) system access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission and reception point, TRP or transmission point, TP), etc., can also be a network node that constitutes a gNB or a transmission point, such as A baseband unit (BBU), or a distributed unit (distributed unit, DU), etc.
  • RNC radio network controller
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include a radio unit (radio unit, RU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB, for example, CU implements radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer functions
  • DU implements wireless link Functions of the radio link control (radio link control, RLC), media access control (media access control, MAC) and physical (physical, PHY) layers.
  • the network device may be a CU node, or a DU node, or a device including a CU node and a DU node.
  • a CU may be divided into network devices in the access network RAN, or a CU may be divided into network devices in the core network CN, which is not limited.
  • the terminal equipment may also be called user equipment (user equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device , User Agent, or User Device.
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety ( Wireless terminals in transportation safety, wireless terminals in smart cities, smart wearable devices (smart glasses, smart watches, smart headphones, etc.), wireless terminals in smart homes, etc., can also be Chips or chip modules (or chip systems) that can be installed in the above devices.
  • the embodiments of the present application do not limit the application scenarios.
  • the communication system shown in Figure 1 may be, but not limited to, a fourth generation (4th Generation, 4G) system, a fifth generation (5th Generation, 5G) system, such as a new generation of wireless access technology (new radio access technology, NR).
  • 4G fourth generation
  • 5G fifth generation
  • NR new radio access technology
  • the method in the embodiment of the present application is also applicable to various communication systems in the future, such as a sixth generation (6th Generation, 6G) system or other communication networks.
  • 6G sixth generation
  • the network device When the network device schedules the terminal device to receive downlink data, or the network device schedules the terminal device to send uplink data, it will first send downlink control information (downlink control information, DCI), which contains a data scheduling information, the data scheduling information will instruct the physical Downlink shared channel (physical downlink shared channel, PDSCH) (which usually contains downlink data) or physical uplink shared channel (physical uplink shared channel, PUSCH) (which usually contains uplink data) transmission parameters, among these transmission parameters, Including the time-frequency domain resource positions of PDSCH/PUSCH.
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • the network device will indicate the K0 value through the time domain resource allocation (TDRA) field in the DCI, which is used to determine the time slot interval between the PDCCH and the PDSCH; for the uplink data, the network device will The K2 value is indicated by the TDRA field in the DCI, and is used to determine the time slot interval between the PDCCH and the PUSCH.
  • TDRA time domain resource allocation
  • the network device sends PDSCH at the time-frequency domain resource location indicated in the DCI, and the terminal device receives it at the corresponding location; or, the terminal device sends PUSCH at the time-frequency domain resource location indicated in the DCI, and the network device receives it at the corresponding location.
  • a terminal device When a terminal device receives its own DCI, it needs to blindly detect (blind detect, BD) the PDCCH sent to itself in the downlink control area, that is, the terminal device monitors (monitors) many PDCCH candidate positions (PDCCH candidates) to find out whether there are sent to myself.
  • blind detect BD
  • the terminal device monitors (monitors) many PDCCH candidate positions (PDCCH candidates) to find out whether there are sent to myself.
  • the terminal device will monitor the PDCCH frequently, but if there is no business happening on the terminal device for a period of time, that is, when there is no downlink data or uplink data to be transmitted, the network device will not send the PDCCH to schedule PDSCH or PUSCH. , even if the terminal device monitors the PDCCH, it cannot receive the PDCCH sent to itself. If the terminal equipment continues to monitor the PDCCH during these times, it will cause power consumption of the terminal equipment.
  • the network equipment can send an indication message to the terminal equipment, indicating that the terminal equipment can skip the PDCCH for a period of time monitor.
  • the PDCCH monitoring that the terminal device skips for a period of time can be equivalently described as the terminal device not monitoring the PDCCH for a period of time, and this period of time during which the PDCCH is not monitored can be called a skipping duration (skipping duration).
  • skipping duration the skipping duration
  • the terminal device originally needs to monitor the PDCCH for each time slot.
  • the terminal device can monitor the The PDCCH is not monitored for a period of time.
  • the network device can only trigger the PDCCH skipping of the terminal device by scheduling DCI. That is, the DCI that can indicate PDCCH skipping must be the DCI that schedules data transmission.
  • the scheduling DCI includes a PDCCH monitoring adaptation indication (PDCCH monitoring adaptation indication) field, which is 1-2 bits (bit), and can indicate PDCCH skipping. It should be noted that this field can indicate both PDCCH skipping and search space set group switching (search space set group switching, SSSG switching). This application only uses PDCCH skipping as an example for illustration.
  • the network device can configure 1 to 3 skipping durations for the terminal device, and indicate the length of the skipping duration used each time through 1 to 2 bits.
  • the scheduling DCI will contain 1 bit, and the value '0' means that PDCCH skipping is not performed (that is, PDCCH is monitored normally), and the value '1' means that it is in T1 During the time period, the PDCCH is not monitored.
  • the scheduling DCI will contain 2 bits, and the value '00' means that PDCCH skipping is not performed (that is, PDCCH is monitored normally); the value '01' means that in During the time length of T1, the PDCCH is not monitored; a value of '10' indicates that the PDCCH is not monitored during the time length of T2.
  • the scheduling DCI will contain 2 bits, and the value '00' means that PDCCH skipping is not performed (that is, PDCCH is monitored normally); the value is '01' Indicates that the PDCCH is not monitored during the duration of T1; the value '10' indicates that the PDCCH is not monitored during the duration of T2; the value of '11' indicates that the PDCCH is not monitored during the duration of T3. It should be noted that the relationship between the values of the above bits and their corresponding meanings is only an example, and there may be other indication methods.
  • the scheduling DCI will contain 1 bit, and the value is '1' indicates that PDCCH skipping is not performed (that is, PDCCH is monitored normally), and a value of '0' indicates that PDCCH is not monitored within the time length of T1.
  • This application is not limited to this.
  • the network device When the network device uses the scheduling DCI to indicate the PDCCH skipping, it usually indicates the PDCCH skipping in the last scheduling DCI of each service scheduling of the terminal device. For example, as shown in Figure 3, when the terminal equipment continues to transmit services, the DCI carried in the PDCCH of the scheduling data (that is, scheduling the PDSCH) always indicates "no skipping (no skipping) PDCCH" (that is, continuously monitoring the PDCCH), so as to quickly Complete data transfer. In the PDCCH of the last transmission of a service, the network device can indicate that a period of time (that is, the skipping duration) The PDCCH is not monitored, and the network device can determine whether it is the last transmission by checking whether there is still data to be transmitted by the terminal device in the cache.
  • the network device after the skipping time, if the service of the terminal device has not arrived, the network device generally does not schedule the data transmission of the terminal device, and cannot send scheduling DCI, and thus cannot indicate PDCCH skipping. At this time, the terminal equipment can only continuously monitor the PDCCH, which leads to waste of power consumption of the terminal equipment.
  • the present application proposes a communication method, which can instruct the terminal device not to monitor the PDCCH for a period of time when no service arrives at the terminal device, thereby reducing the power consumption of the terminal device.
  • the communication method provided by this application is described in detail by taking terminal equipment and network equipment as examples. It should be understood that the operations performed by the terminal equipment can also be performed by the processor in the terminal equipment, or the chip or a chip system, or a functional module, etc., and the operations performed by the network device may also be implemented by a processor in the network device, or a chip or a chip system, or a functional module, etc., which is not limited in this application.
  • the communication method provided by the embodiment of the present application is applicable to the communication system shown in FIG. 1 .
  • the specific process of the method may include:
  • Step 401 the network device determines a first DCI, the first DCI is used to schedule padding packets (padding packets), and the first DCI instructs the terminal device not to monitor the PDCCH within a first duration.
  • Step 402 The network device sends the first DCI to the terminal device.
  • Step 403 The terminal device determines not to monitor the PDCCH within the first duration according to the first DCI.
  • the terminal device when the first DCI of the filling data packet is scheduled to instruct the terminal device not to monitor the PDCCH within the first time period, the terminal device can skip the monitoring of the PDCCH even when no traffic arrives, thereby reducing The power consumption of the device.
  • the DCI carried in the PDCCH of the scheduling data that is, scheduling the PDSCH
  • the network device may indicate not to monitor the PDCCH within a period of time (ie skipping duration).
  • skipping duration if the service of the terminal device has not arrived, the network device can indicate PDCCH skipping by scheduling the first DCI of the filling data packet, thereby reducing the power consumption of the terminal device.
  • the two durations for which the terminal device does not monitor the PDCCH shown in FIG. 5 may be the same or different, which is not limited in this application.
  • the network device configures at least two skip durations for the terminal device, and the durations of not monitoring the PDCCH indicated by the network device twice are different.
  • the two durations may also be predefined, which is not limited in this application.
  • the network device may determine that no service arrives at the terminal device within the preset time period, or the network device determines that there is no The cached data corresponding to the terminal device.
  • the preset duration can be a period of time before the network device sends the first DCI, or the preset duration can be a period of time after the network device sends the first DCI, or the preset duration can also be the network device sends the first DCI moment.
  • the preset duration is a period of time after the terminal device sends the first DCI, the preset duration may be less than, equal to, or greater than the first duration, which is not limited in this application.
  • No service arrival of the terminal device may refer to no service data transmission, no data arrival, no downlink data arrival, no need to send RRC message or media access control control element (media access control control element, MAC CE) to the terminal device, etc.
  • media access control control element media access control control element, MAC CE
  • the network device can determine whether there is data from the terminal device on the core network side during this period of time, and when it is determined that there is no data from the terminal device on the core network side When receiving data, the network device determines that no traffic arrives at the terminal device within a preset time period.
  • the network device can predict through a prediction algorithm to determine that the terminal device has no Business arrives.
  • the prediction algorithm is not limited in this application.
  • the network device may determine that the buffer (buffer) corresponding to the terminal device is empty.
  • the first DCI may include the following two situations:
  • the first DCI may be used to schedule the PDSCH.
  • the first DCI may be used to schedule the PUSCH.
  • the first DCI may be a DCI format (format) 1_1 or DCI format 1_2 scrambled by a cell-radio network temporary identity (C-RNTI); or, the first DCI may be modulated DCI format 1_1 or DCI format 1_2 scrambled by modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI) scrambled by the coding method; or, the first DCI may be a temporary wireless network for configuration scheduling Identify (configured scheduling-radio network temporary identity, CS-RNTI) scrambled DCI format 1_1 or DCI format 1_2.
  • C-RNTI cell-radio network temporary identity
  • MCS-C-RNTI modulation and coding scheme-cell-radio network temporary identifier
  • the network device sends a PDSCH to the terminal device (correspondingly, the terminal device receives the PDSCH from the network device), and the PDSCH contains a media access control sub protocol data unit (MAC sub PDU),
  • MAC sub PDU media access control sub protocol data unit
  • the value of the logical channel identify (LCID) corresponding to the MAC sub-PDU is 63.
  • a PDSCH includes a media access control protocol data unit (media access control protocol data unit, MAC PDU).
  • MAC PDU media access control protocol data unit
  • one MAC PDU can contain one or more MAC sub PDUs, and the subheader (subheader) of each MAC sub PDU contains LCID, which is used to indicate the role of the corresponding MAC sub PDU.
  • different values of LCID may indicate different functions of the MAC sub PDU.
  • Table 1 below, they are the meanings corresponding to different values of LCID. It can be seen from Table 1 that when the value of LCID is 63, it can indicate that the corresponding MAC sub-PDU is a padding packet, and the padding packet indicates that it does not contain meaningful data.
  • the terminal equipment Since the terminal equipment receives the DCI, it needs to receive the PDSCH or send the PDSCH according to the DCI. Usually, the power consumption of the terminal equipment to send the PUSCH is greater than the power consumption of the received PDSCH. Therefore, from the perspective of terminal equipment energy saving, through the above situation a1 When the first DCI of scheduling PDSCH (scheduling padding) is used to instruct the terminal device not to monitor the PDCCH within the first duration, the power consumption of the terminal device can generally be lower than that of using the first DCI in case a2.
  • the first DCI may be DCI format 0_1 or DCI format 0_2 scrambled by C-RNTI; or, the first DCI may be DCI format 0_1 or DCI format 0_2 scrambled by MCS-C-RNTI; or, The first DCI may be CS-RNTI scrambled DCI format 0_1 or DCI format 0_2.
  • the terminal device when the terminal device is not configured with the uplink skip function, the terminal device sends a PUSCH to the network device (correspondingly, the network device receives the PUSCH from the terminal device), and the PUSCH contains the MAC sub PDU and the LCID corresponding to the MAC sub PDU
  • the value is 63.
  • a MAC A PDU may contain one or more MAC sub PDUs, and a subheader (subheader) of each MAC sub PDU includes an LCID, and the LCID is used to indicate the role of the corresponding MAC sub PDU. It can be seen from Table 1 that when the LCID value is 63, it can indicate that the corresponding MAC sub-PDU is a padding packet, and the padding packet indicates that it does not contain meaningful data.
  • the terminal device may send a PUSCH containing uplink data to the network device when the terminal device has traffic arriving temporarily. In this case, the end device does not send padding packets to the network device.
  • the terminal device does not send a scheduling request (scheduling request, SR) or a buffer status report (buffer status report, BSR) to the network device, when the network device schedules the terminal device to send PUSCH through the first DCI, it is impossible to know whether the terminal device is There is uplink data to be sent.
  • SR scheduling request
  • BSR buffer status report
  • the terminal device After receiving the first DCI, the terminal device will include the uplink data in the PUSCH when there is uplink data according to its actual situation, and include padding packets in the PUSCH when there is no uplink data. If the terminal device receives the first DCI, uplink data has just arrived, even if the terminal device has not sent the corresponding SR or BSR to request the scheduling of the network device, the terminal device can send the uplink data to the network through the PUSCH scheduled by the first DCI equipment.
  • the terminal device when the terminal device is configured with the uplink skip function, the terminal device may not send the PUSCH to the network device.
  • the terminal device When the terminal device is configured with the uplink skip function, when the terminal device receives the DCI for scheduling the PUSCH and there is no uplink data to be sent, the terminal device may not send the PUSCH. That is to say, in the above case a2, when the terminal device is configured with the uplink skip function, after the network device sends the first DCI, the terminal device neither needs to send PUSCH nor receive PDSCH, so the energy saving from the terminal device From a perspective, when the terminal device is configured with the uplink skip function, when the first DCI of scheduling PUSCH (scheduling padding) is used to instruct the terminal device not to monitor the PDCCH within the first duration through the above situation a2, the terminal device's The power consumption is lower than the power consumption when using the first DCI in case a1.
  • the terminal device when the terminal device is configured with the uplink skip function, if the terminal device temporarily has traffic arriving, that is, when it needs to send uplink data, the terminal device can send uplink data to the network device through the PUSCH scheduled by the network device. In this case, the terminal device no longer needs to request uplink resources from the network device through a scheduling request (scheduling request, SR), thereby reducing service delay.
  • SR scheduling request
  • the terminal device may be configured with connected discontinuous reception (connected discontinuous reception, CDRX).
  • the C-DRX cycle can be a long DRX cycle or a short DRX cycle.
  • the long DRX cycle is mandatory by default, and the short DRX cycle is optional. If a short DRX cycle is configured, the terminal device will When a short DRX cycle is used, the short cycle timer (ShortCycleTimer) is started, and when the ShortCycleTimer times out, it is converted to a long DRX cycle.
  • ShortCycleTimer short cycle timer
  • the CDRX cycle includes an "On Duration” part and an "DRX Opportunity (Opportunity for DRX)" part.
  • the terminal equipment monitors the PDCCH for a duration (OnDuration) within each CDRX cycle. If the new transmission data scheduling is not received in OnDuration (that is, the PDCCH indicating the initial transmission (new transmission) is not received), then enter Opportunity for DRX after OnDuration ends, and stop monitoring PDCCH until the next cycle of OnDuration starts again Monitor PDCCH.
  • the terminal device If a new transmission data schedule is received in OnDuration (that is, a PDCCH indicating initial transmission (new transmission) is received), the terminal device starts an inactivity timer (or an inactivity timer) (InactivityTimer or DRX-inactivitytimer), and in the InactivityTimer During operation, the terminal equipment still monitors the PDCCH. If a new data call is received during the running of the InactivityTimer degree, the InactivityTimer will be restarted. Whether it is in OnDuration or when InactivityTimer is running, it is called active time, and the terminal device needs to monitor the PDCCH during the active time. The restart of InactivityTimer can be understood as prolonging the active time of the terminal device. When the InactivityTimer expires, the terminal device stops monitoring the PDCCH.
  • the method of judging whether it is "newly transmitted data scheduling" is to see whether the new data indicator (new data indicator, NDI) (NDI is 1-bit, and the value is '0' or '1') field in DCI occurs Flip (toggle).
  • hybrid automatic repeat request process hybrid automatic repeat request process, HARQ process
  • HARQ process hybrid automatic repeat request process, HARQ process
  • the NDI in the DCI received by the terminal device is compared with the previous Once the NDI of the received DCI is flipped (for example, NDI is flipped from 0 to 1, or NDI is flipped from 1 to 0), it is considered that new data has been transmitted using the HARQ process; if the NDI in the DCI received by the terminal device If it is the same as the NDI of the DCI received last time, it is considered that the HARQ process is used for data retransmission.
  • the network device when the network device indicates that the terminal device configured with CDRX does not monitor the PDCCH for a period of time, as shown in FIG.
  • the PDCCH is not monitored in certain time periods, thereby increasing the sleep time of the terminal equipment based on the CDRX mechanism. In this case, the network device still cannot instruct the terminal device to skip the PDCCH when no service arrives at the terminal device.
  • scheduling the first DCI of the PDSCH may cause the restart of the InactivityTimer, resulting in prolonging the active time of the terminal device.
  • prolonging the active time may increase the time for the terminal device to monitor the PDCCH and increase the power consumption of the terminal device.
  • the terminal device when the terminal device is configured with CDRX, after the terminal device receives the PDSCH containing the filling data packet from the network device, the terminal device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running , the terminal device does not restart or stop the DRX-inactivity timer after receiving the PDSCH containing the padding data packet from the network device.
  • the network device when the terminal device is configured with CDRX, after the network device sends the PDSCH including filling data packets to the terminal device, the network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device sends the terminal device The DRX-inactivity timer is not restarted or stopped after sending the PDSCH including padding packets.
  • scheduling the first DCI of PUSCH may also cause the restart of InactivityTimer, resulting in prolonging the active time of the terminal device, and prolonging the active time may cause the terminal device to need to monitor the PDCCH
  • the duration increases, increasing the power consumption of the terminal equipment.
  • the terminal device when the terminal device is configured with CDRX and is not configured with the uplink skip function, after the terminal device sends a PUSCH containing padding data packets to the network device, the terminal device does not start the DRX-inactivity timer; or, when When the DRX-inactivity timer is running, the terminal device does not restart or stop the DRX-inactivity timer after sending the PUSCH containing the filling data packet to the network device.
  • the network device does not start the DRX-inactivity timer after receiving the PUSCH sent by the terminal device including the padding data packet; or, when the DRX-inactivity timer is running, the network device receives the terminal The device does not restart or stop the DRX-inactivity timer after sending the PUSCH including padding packets. After the network device completes the decoding of the PUSCH, it can determine whether the PUSCH contains padding packets, that is, it can determine whether to start, restart or stop the DRX-inactivity timer.
  • the terminal device when the terminal device is configured with CDRX and configured with the uplink skip function, when the terminal device does not send the PUSCH, that is, after the terminal device determines (because there is no data to be transmitted) not to send the PUSCH, the terminal device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the terminal device does not send the PUSCH, That is, the terminal device does not restart or stop the DRX-inactivity timer after determining (because there is no data to be transmitted) not to send the PUSCH.
  • the network device when the terminal device is configured with CDRX, the network device does not receive the PUSCH sent by the terminal device at the position indicated by the first DCI (that is, the time-frequency position at which the terminal device sends the PUSCH indicated when the first DCI schedules the PUSCH), and the network The device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device does not receive the PUSCH sent by the terminal device at the position indicated by the first DCI, and does not restart or stop the DRX-inactivity timer.
  • the active time of the terminal device can be avoided to be extended, thereby saving the power consumption of the terminal device.
  • the value of the NDI field in the first DCI may be different from the value of the NDI field in the third DCI, and the third DCI is different from the value of the NDI field in the first DCI.
  • the value of the HARQ HPN field of the DCI is the same as that of the previous DCI.
  • the first DCI may be understood as newly transmitted DCI.
  • the terminal equipment and the network equipment do not need to Start the DRX-inactivity timer, and then do not start, restart or stop the DRX-inactivity timer by the terminal device and network device, so as to avoid the extension of the active time of the terminal device, thereby saving the power consumption of the terminal device.
  • the value of the NDI field in the first DCI may be the same as the value of the NDI field in the second DCI, and the second DCI is the HARQ
  • the value of the HPN field is the same as the previous DCI.
  • the first DCI is a retransmission DCI.
  • the terminal device sends correct acknowledgment (acknowledgment character, ACK) information to the network device after receiving the second DCI from the network device.
  • ACK acknowledgment character
  • the terminal device Normally, after a terminal device receives a PDSCH incorrectly, it will feed back a NACK to allow the network device to schedule retransmission of the same data. After receiving the retransmission data, the terminal device will combine and decode the received retransmission data with the data that has been received before and stored in the buffer (buffer).
  • the terminal device will usually clear the history stored in the buffer. data pack. Therefore, the retransmitted DCI-scheduled data is usually not combined and decoded with the previously received data, but is decoded separately. After independently decoding the data packet scheduled by the first DCI, the terminal device can recognize that the currently scheduled data packet is a padding packet.
  • the terminal device and the network device do not start, restart or stop the DRX-inactivity timer to avoid prolonging the active time of the terminal device, thereby saving the power consumption of the terminal device.
  • the DCI of filling data packets can be scheduled to instruct the terminal device not to monitor the PDCCH within the first duration, thereby reducing the power consumption of the terminal device.
  • Another communication method provided in the embodiment of the present application is applicable to the communication system shown in FIG. 1 .
  • the specific process of the method may include:
  • Step 901 the network device sends a downlink filling data packet to the terminal device, and the terminal device receives the downlink filling data packet from the network device accordingly.
  • the network device can send a downlink filling data packet to the terminal device in the following manner: the network device sends a PDSCH to the terminal device, the PDSCH includes MAC sub-PDU, and the LCID value corresponding to the MAC sub-PDU for 63.
  • the LCID value corresponding to the MAC sub-PDU in the PDSCH being 63 to indicate the filling data packet
  • Step 902 the network device determines that the terminal device does not monitor the PDCCH within a second time period.
  • Step 903 The terminal device determines not to monitor the PDCCH within the second time period according to the downlink filling data packet.
  • step 902 and step 903 is not limited in this application.
  • the network device may send DCI to the terminal device, where the DCI is used to schedule the downlink filling data packet, and the DCI instructs the terminal device not to monitor the PDCCH within the second time period after receiving the downlink filling data packet. In this way, after receiving the downlink data packet, the terminal device can determine not to monitor the PDCCH within the second time period.
  • the second duration may be configured by the network device for the terminal device, may also be predefined, or may be indicated by the network device when sending the downlink filling data packet to the terminal device, for example, the network device sends the terminal device
  • the PDSCH includes both the downlink filling data packet and the second duration.
  • the DCI may be DCI format 1_0, or DCI format 1_1 or DCI format 1_2.
  • the terminal device After the terminal device receives the downlink filling data packet, it can realize not monitoring the PDCCH for a period of time, so that the power consumption of the terminal device can be saved.
  • Another communication method provided in the embodiment of the present application is applicable to the communication system shown in FIG. 1 .
  • the specific process of the method may include:
  • Step 1001 the network device sends a downlink filling data packet to the terminal device.
  • Step 1002 the network device does not start the DRX-inactivity timer; or, when the DRX-inactivity timer is running, the network device does not restart or stop the DRX-inactivity timer.
  • Step 1003 The terminal device determines that the terminal device does not start the DRX-inactivity timer according to the downlink filling data packet; or, when the DRX-inactivity timer is running, determines that the terminal device does not restart or stop the DRX-inactivity timer.
  • step 1002 and step 1003 is not limited in this application.
  • the terminal device After the terminal device receives the downlink filling data packet, by not starting the DRX-inactivity timer, or not restarting or stopping the running DRX-inactivity timer, it is possible to avoid prolonging the activation time of the terminal device, thereby reducing the number of terminal devices. power consumption.
  • the communication device 1100 may include a transceiver unit 1101 and a processing unit 1102 .
  • the transceiver unit 1101 is used for the communication device 1100 to receive information (message or data) or send information (message or data), and the processing unit 1102 is used to control and manage the actions of the communication device 1100 .
  • the processing unit 1102 may also control the steps performed by the transceiver unit 1101 .
  • the communication device 1100 may specifically be the network device in the foregoing embodiments, a processor in the network device, or a chip, or a chip system, or a functional module, etc.; or, the communication device 1100 may specifically be It is the terminal device in the above embodiments, the processor of the terminal device, or a chip, or a chip system, or a functional module, etc.
  • the processing unit 1102 is configured to determine the The PDCCH is not monitored within the first period of time.
  • the first DCI is used for scheduling a physical downlink shared channel PDSCH.
  • the first DCI is the DCI format 1_1 or DCI format 1_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the cell-specific radio network temporary identifier MCS-C- DCI format 1_1 or DCI format 1_2 of RNTI scrambling; or, the first DCI is DCI format 1_1 or DCI format 1_2 of configuring scheduling wireless network temporary identifier CS-RNTI scrambling.
  • the transceiver unit 1101 is further configured to receive a physical downlink shared channel PDSCH from the network device, the PDSCH includes a medium access control sub-protocol data unit MAC sub PDU, and the logical channel corresponding to the MAC sub PDU
  • the value of LCID is 63.
  • the first DCI is used for scheduling a physical uplink shared channel PUSCH.
  • the first DCI is the DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the cell-specific radio network temporary identifier MCS-C- DCI format 0_1 or DCI format 0_2 of RNTI scrambling; or, the first DCI is DCI format 0_1 or DCI format 0_2 of configuring scheduling wireless network temporary identifier CS-RNTI scrambling.
  • the transceiver unit 1101 is further configured to send a physical uplink shared channel PUSCH to the network device, the PUSCH includes a medium access control sub-protocol data unit MAC sub PDU, and the logical channel corresponding to the MAC sub PDU
  • the value of LCID is 63.
  • the transceiving unit 1101 is further configured to send a physical uplink shared channel PUSCH to the network device, where the PUSCH includes the padding data packet; the processing unit 1102 is further configured not to Continuously receive the inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, do not restart or stop the DRX-inactivity timer.
  • the transceiving unit 1101 is further configured not to send a physical uplink shared channel PUSCH to the network device.
  • the processing unit 1102 is further configured not to start the discontinuous reception inactivity timer DRX- inactivitytimer; or, when the DRX-inactivitytimer is running, do not restart or stop the DRX-inactivitytimer.
  • the transceiving unit 1101 is further configured to receive a physical downlink shared channel PDSCH from the network device, wherein the PDSCH includes the padding data packet; the processing unit 1102 is further configured not to enable discontinuous reception and An activity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, do not restart or stop the DRX-inactivitytimer.
  • the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI
  • the second DCI is a hybrid automatic repeat request HARQ process with the first DCI
  • the value of the HPN field is the same as that of the previous DCI.
  • the transceiving unit 1101 is further configured to receive the second DCI from the network device before receiving the first DCI from the network device, and send correct response ACK information to the network device.
  • the new data in the first DCI indicates that the value of the NDI field is different from the value of the NDI field in the third DCI
  • the third DCI is a hybrid automatic repeat request HARQ with the first DCI
  • the value of the HPN field of the process number is the same as that of the previous DCI.
  • the communication apparatus 1100 when used to implement the functions of the network device in the embodiment described in FIG. 4 , it may specifically include: the processing unit 1102 is used to determine the first downlink control information DCI, The first DCI is used to schedule stuffing data packets, and the first DCI instructs the terminal device not to monitor the physical downlink control channel PDCCH within a first duration; the transceiver unit 1101 is used to send the first DCI to the terminal device DCI.
  • the processing unit 1102 is further configured to: before the transceiver unit 1101 sends the first DCI to the terminal device, determine that no traffic arrives at the terminal device within a preset time period; or, determine that there is no The cached data corresponding to the terminal device.
  • the first DCI is used for scheduling a physical downlink shared channel PDSCH.
  • the first DCI is the DCI format 1_1 or DCI format 1_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the cell-specific radio network temporary identifier MCS-C- DCI format 1_1 or DCI format 1_2 of RNTI scrambling; or, the first DCI is DCI format 1_1 or DCI format 1_2 of configuring scheduling wireless network temporary identifier CS-RNTI scrambling.
  • the network device sends the physical downlink shared channel PDSCH to the terminal device, the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier LCID value corresponding to the MAC sub PDU for 63.
  • the PDSCH includes a media access control sub-protocol data unit MAC sub PDU, and the logical channel identifier LCID value corresponding to the MAC sub PDU for 63.
  • the first DCI is used for scheduling a physical uplink shared channel PUSCH.
  • the first DCI is the DCI format 0_1 or DCI format 0_2 scrambled by the cell radio network temporary identifier C-RNTI; or, the first DCI is the cell-specific radio network temporary identifier MCS-C- DCI format 0_1 or DCI format 0_2 of RNTI scrambling; or, the first DCI is DCI format 0_1 or DCI format 0_2 of configuring scheduling wireless network temporary identifier CS-RNTI scrambling.
  • the transceiver unit 1101 is further configured to receive a physical uplink shared channel PUSCH from the terminal device, the PUSCH includes a medium access control sub-protocol data unit MAC sub PDU, and the MAC sub PDU corresponds to The value of the logical channel identifier LCID is 63.
  • the transceiving unit 1101 is further configured not to receive the PUSCH from the terminal device.
  • the transceiving unit 1101 is further configured to receive a physical uplink shared channel PUSCH from the terminal device, wherein the PUSCH includes the padding data packet; the processing unit 1102 is further configured to not start discontinuous reception inactivity A timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, do not restart or stop the DRX-inactivitytimer.
  • the processing unit 1102 is further configured to not start discontinuous reception inactivity if the transceiver unit 1101 does not receive the physical uplink shared channel PUSCH sent by the terminal device at the position indicated by the first DCI A timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, do not restart or stop the DRX-inactivitytimer.
  • the transceiver unit 1101 is further configured to send a Physical Downlink Shared Channel (PDSCH) to the terminal device, where the PDSCH includes the padding data packet; the processing unit 1102 is also configured to not start discontinuous reception The inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the DRX-inactivitytimer is not restarted or stopped.
  • PDSCH Physical Downlink Shared Channel
  • the value of the new data indication NDI field in the first DCI is the same as the value of the NDI field in the second DCI
  • the second DCI is a hybrid automatic repeat request HARQ process with the first DCI
  • the value of the HPN field is the same as that of the previous DCI.
  • the transceiving unit 1101 is further configured to send the second DCI to the terminal device before sending the first DCI to the terminal device, and receive correct response ACK information from the terminal device.
  • the new data in the first DCI indicates that the value of the NDI field is different from the value of the NDI field in the third DCI
  • the third DCI is a hybrid automatic repeat request HARQ with the first DCI
  • the value of the HPN field of the process number is the same as that of the previous DCI.
  • the communication device 1100 when used to implement the functions of the terminal device in the embodiment shown in FIG. 9 or FIG. 10 , it may specifically include: the transceiver unit 1101 is used to receive downlink stuff from the network device A data packet; the processing unit 1102 is configured to determine a first operation of the terminal device according to the downlink filling data packet.
  • the transceiver unit 1101 when the transceiver unit 1101 receives the downlink filling data packet from the network device, it may be configured to: receive a physical downlink shared channel PDSCH from the network device, and the PDSCH includes a medium access control sub- A protocol data unit MAC sub PDU, the value of the logical channel identifier LCID corresponding to the MAC sub PDU is 63.
  • the first operation is not to monitor the Physical Downlink Control Channel PDCCH within the second duration.
  • the transceiving unit 1101 is further configured to receive downlink control information DCI from the network device, the DCI is used to schedule the downlink filling data packet, and the DCI indicates that the terminal device receives the downlink After the data packets are filled, the PDCCH is not monitored within the second duration.
  • the DCI is DCI format 1_0.
  • the first operation is not to start the discontinuous reception inactivity timer DRX-inactivitytimer; or, when the DRX-inactivitytimer is running, the first operation is not to restart or stop The DRX-inactivity timer.
  • the communication device 1100 when used to implement the functions of the network device in the embodiment described above in FIG. 9 , it may specifically include: the transceiver unit 1101 is used to send a downlink filling data packet to the terminal device; The processing unit 1102 is configured to determine that the terminal device does not monitor the physical downlink control channel PDCCH within the second time period.
  • the transceiver unit 1101 when it sends the downlink filling data packet to the terminal device, it may be configured to: send the physical downlink shared channel PDSCH to the terminal device, and the PDSCH includes a medium access control sub- A protocol data unit MAC sub-PDU, the value of the logical channel identifier LCID corresponding to the MAC sub-PDU is 63.
  • the transceiver unit 1101 is further configured to send downlink control information DCI to the terminal device, the DCI is used to schedule the downlink filling data packet, and the DCI indicates that the terminal equipment receives the downlink filling data packet.
  • the PDCCH is not monitored within the second duration after the data packet.
  • the DCI is DCI format 1_0.
  • the communication device 1100 when used to implement the functions of the network device in the embodiment described above in FIG. 10 , it may specifically include: the transceiver unit 1101 is used to send a downlink filling data packet to the terminal device; The processing unit 1102 is configured not to start the discontinuous reception inactivity timer DRX-inactivity timer; or, when the DRX-inactivity timer is running, not restart or stop the DRX-inactivity timer.
  • the transceiver unit 1101 when sending the downlink filling data packet to the terminal device, is configured to: send a physical downlink shared channel PDSCH to the terminal device, and the PDSCH includes a media access control sub-protocol data unit MAC sub-PDU, the value of the logical channel identifier LCID corresponding to the MAC sub-PDU is 63.
  • each functional unit in the embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • the communication device 1200 may include a transceiver 1201 and a processor 1202 .
  • the communication device 1200 may further include a memory 1203 .
  • the memory 1203 can be set inside the communication device 1200 , and can also be set outside the communication device 1200 .
  • the processor 1202 may control the transceiver 1201 to receive and send information, messages or data, and the like.
  • the processor 1202 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor 1202 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • the transceiver 1201, the processor 1202 and the memory 1203 are connected to each other.
  • the transceiver 1201, the processor 1202 and the memory 1203 are connected to each other through a bus 1204;
  • the bus 1204 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard Structure (Extended Industry Standard Architecture, EISA) bus, etc.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 12 , but it does not mean that there is only one bus or one type of bus.
  • the memory 1203 is used to store programs and the like.
  • the program may include program code including computer operation instructions.
  • the memory 1203 may include RAM, and may also include non-volatile memory (non-volatile memory), such as one or more disk memories.
  • the processor 1202 executes the application program stored in the memory 1203 to realize the above functions, thereby realizing the functions of the communication device 1200 .
  • the communication apparatus 1200 may be the network device in the foregoing embodiments; it may also be the terminal device in the foregoing embodiments.
  • the transceiver 1201 can implement the implementation shown in FIG. 4 , FIG. 9 or FIG. 10
  • the transceiving operation performed by the terminal device in the example; the processor 1202 can realize the operation performed by the terminal device in the embodiment shown in FIG. 4 , FIG. 9 or FIG. 10
  • Other operations other than sending and receiving operations.
  • the transceiver 1201 can implement the implementation shown in FIG. 4 , FIG. 9 or FIG. 10
  • the transceiving operation performed by the network device in the example; the processor 1202 may implement other operations except the transceiving operation performed by the network device in the embodiment shown in FIG. 4 , FIG. 9 or FIG. 10 .
  • the processor 1202 may implement other operations except the transceiving operation performed by the network device in the embodiment shown in FIG. 4 , FIG. 9 or FIG. 10 .
  • the embodiments of the present application provide a communication system, and the communication system may include the terminal device and the network device involved in the above embodiments.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the communication method provided by the above method embodiment.
  • the embodiment of the present application further provides a chip, including a processor, the processor is coupled to a memory, and is configured to call a program in the memory so that the chip implements the communication method provided by the above method embodiment.
  • the embodiment of the present application further provides a chip, the chip is coupled with a memory, and the chip is used to implement the communication method provided in the foregoing method embodiment.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，用以减少终端设备的功耗。网络设备确定第一DCI，并向终端设备发送第一DCI，然后终端设备根据所述第一DCI确定在第一时长内不监测PDCCH；其中，所述第一DCI用于调度填充数据包，所述第一DCI指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。这样，在终端设备无业务到达时，网络设备可以通过调度填充数据包的DCI来指示终端设备在第一时长内不监测PDCCH，从而减少终端设备的功耗。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年03月03日提交中国专利局、申请号为202210204563.7、申请名称为“一种指示跳过PDCCH和搜索空间切换的方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；本申请要求在2022年04月15日提交中国专利局、申请号为202210397041.3、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在网络设备和终端设备进行数据传输之前，网络设备会向终端设备发送数据调度信息，例如PDCCH，为了避免丢失调度信息，终端设备需要按照网络设备的配置频繁地监测PDCCH。而终端设备频繁监测PDCCH的行为会导致终端设备的功耗较高。目前，针对终端设备的功耗节省的研究越来越普遍，减少终端设备功耗的细节优化方案成为业界研究方向。
发明内容
本申请提供一种通信方法及装置，用以减少终端设备的功耗。
第一方面，本申请提供了一种通信方法，该方法可以包括：终端设备从网络设备接收第一下行控制信息(downlink control information，DCI)后，根据所述第一DCI确定在所述第一时长内不监测PDCCH；其中，所述第一DCI用于调度填充数据包，所述第一DCI指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。
通过上述方法，在终端设备无业务到达时，网络设备可以通过调度填充数据包的DCI来指示终端设备在第一时长内不监测PDCCH，从而减少终端设备的功耗。
在一个可能的设计中，所述第一DCI用于调度物理下行共享信道(physical downlink shared channel，PDSCH)。这样第一DCI可以通过调度下行填充数据包来指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。
在一个可能的设计中，所述第一DCI为小区无线网络临时标识(cell-radio network temporary identity，C-RNTI)加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识(modulation and coding scheme-cell-radio network temporary identifier，MCS-C-RNTI)加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为配置调度无线网络临时标识(configured scheduling-radio network temporary identity，CS-RNTI)加扰的DCI格式1_1或DCI格式1_2。这样第一DCI可以通过下行DCI灵活实现。
在一个可能的设计中，所述终端设备从所述网络设备接收PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元(media access control sub protocol data unit，MAC sub PDU)，所述对应的逻辑信道标(logical channel identify，LCID)。以实现网络设备调度下行填充数据包。
在一个可能的设计中，所述第一DCI用于调度物理上行共享信道(physical uplink shared channel，PUSCH)。这样第一DCI可以通过调度上行填充数据包来指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。
在一个可能的设计中，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。这样第一DCI可以通过上行DCI灵活实现。
在一个可能的设计中，所述终端设备向所述网络设备发送物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。以实现网络设备调度上行填充数据包。
在一个可能的设计中，所述终端设备向所述网络设备发送PUSCH，其中所述PUSCH包含所述填充数据包；进而所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，当所述终端设备被配置了上行跳过功能时，所述终端设备不向所述网络设备发送物理上行共享信道PUSCH。这样终端设备无需向网络设备发送任何数据包，以节省终端设备功耗。
在一个可能的设计中，当所述终端设备不向所述网络设备发送PUSCH时，进而所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，所述终端设备从所述网络设备接收PDSCH，其中所述PDSCH包括所述填充数据包；进而，所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，所述第一DCI中新数据指示(new data indicator，NDI)字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求(hybrid automatic repeat request，HARQ)进程数(HARQ process number，HPN)字段的取值相同的前一个DCI。这样第一DCI为重传DCI时，终端设备不启动、不重启或停止DRX-inactivitytimer可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，在所述终端设备从网络设备接收所述第一DCI之前，从所述网络设备接收所述第二DCI，向所述网络设备发送正确应答ACK信息。这样后续终端设备可以识别到填充数据包，进而不启动、不重启或停止DRX-inactivitytimer。
在一个可能的设计中，所述第一DCI中的NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的HARQ进程数HPN字段的取值相同的前一个DCI。这样第一DCI为新传DCI时，终端设备可以不启动、不重启或停止DRX-inactivitytimer可以避免终端设备的active time延长，从而节省终端设备的功耗。
第二方面，本申请提供了一种通信方法，该方法可以包括：网络设备确定第一DCI，并向所述终端设备发送所述第一DCI，其中所述第一DCI用于调度填充数据包，所述第一DCI指示终端设备在第一时长内不监测物理下行控制信道PDCCH。
通过上述方法，在终端设备无业务到达时，网络设备可以通过调度填充数据包的DCI来指示终端设备在第一时长内不监测PDCCH，从而减少终端设备的功耗。
在一个可能的设计中，在所述网络设备向所述终端设备发送所述第一DCI之前，所述网络设备确定所述终端设备在预设时长内无业务到达；或者，所述网络设备确定没有所述终端设备对应的缓存数据。这样所述网络设备可以确定所述终端设备没有业务到达，进而向终端设备发送第一DCI。
在一个可能的设计中，所述预设时长为所述网络设备发送所述第一DCI之前的一段时间，或所述预设时长为所述网络设备发送所述第一DCI之后的一段时间，或所述预设时长为所述网络设备发送所述第一DCI的时刻。
在一个可能的设计中，所述第一DCI用于PDSCH。这样第一DCI可以通过调度下行填充数据包来指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。
在一个可能的设计中，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式1_1或DCI格式1_2。这样第一DCI可以通过下行DCI灵活实现。
在一个可能的设计中，所述网络设备向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。以实现网络设备调度下行填充数据包。
在一个可能的设计中，所述第一DCI用于调度PUSCH。这样第一DCI可以通过调度上行填充数据包来指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH。
在一个可能的设计中，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。这样第一DCI可以通过上行DCI灵活实现。
在一个可能的设计中，所述网络设备从所述终端设备接收物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。以实现网络设备调度上行填充数据包。
在一个可能的设计中，当所述终端设备被配置了上行跳过功能时，所述网络设备不从所述终端设备接收PUSCH。这样终端设备无需向网络设备发送任何数据包，以节省终端设备功耗。
在一个可能的设计中，所述网络设备从所述终端设备接收物理上行共享信道PUSCH， 其中所述PUSCH包含所述填充数据包；进而，所述网络端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，所述网络设备在所述第一DCI指示的位置未接收到所述终端设备发送的物理上行共享信道PUSCH；进而，所述网络设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，所述网络设备向所述终端设备发送物理下行共享信道PDSCH，其中所述PDSCH包括所述填充数据包；进而，所述网络设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。这样可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，所述第一DCI中新数据指示NDI字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。这样第一DCI为重传DCI时，网络设备可以不启动、不重启或停止DRX-inactivitytimer可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一个可能的设计中，在所述网络设备向所述终端设备发送所述第一DCI之前，所述方法还包括：所述网络设备向所述终端设备接发送所述第二DCI后，从所述终端设备接收正确应答ACK信息。这样后续可以使终端设备可以识别到填充数据包，进而不启动、不重启或停止DRX-inactivitytimer。
在一个可能的设计中，所述第一DCI中的新数据指示NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。这样第一DCI为新传DCI时，终端设备可以不启动、不重启或停止DRX-inactivitytimer可以避免终端设备的active time延长，从而节省终端设备的功耗。
第三方面，本申请提供了一种通信方法，该方法可以包括：终端设备从网络设备接收下行填充数据包后，根据所述下行填充数据包确定所述终端设备的第一操作。这样终端设备接收到下行填充数据包后可以触发终端设备的第一操作，以节省终端设备的功耗。
在一个可能的设计中，所述终端设备从所述网络设备接收所述下行填充数据包，方法可以为：所述终端设备从所述网络设备接收物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。这样终端设备可以接收到准确的下行填充数据包。
在一个可能的设计中，所述第一操作为所述终端设备在第二时长内不监测物理下行控制信道PDCCH。这样在终端设备接收到下行填充数据包后，可以实现一段时长的不监测PDCCH，从而可以节省终端设备的功耗。
在一个可能的设计中，所述终端设备从所述网络设备接收下行控制信息DCI，所述DCI用于调度所述下行填充数据包，所述DCI指示所述终端设备在收到所述下行填充数据包后 在所述第二时长内不监测PDCCH。这样网络设备可以通过调度下行填充数据包触发终端设备不监测PDCCH。
在一个可能的设计中，所述DCI为DCI格式1_0。
在一个可能的设计中，所述第一操作为所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述第一操作为所述终端设备不重启或停止所述DRX-inactivitytimer。这样，在终端设备接收到下行填充数据包后，通过对DRX-inactivitytimer的不启动，或对运行的DRX-inactivitytimer不重启或停止，可以避免延长终端设备的激活时间，从而可以减少终端设备的功耗。
第四方面，本申请提供了一种通信方法，该方法可以包括：网络设备向终端设备发送下行填充数据包，并确定所述终端设备在第二时长内不监测物理下行控制信道PDCCH。这样可以通过向终端设备发送下行填充数据包，触发终端设备一段时长的不监测PDCCH，从而可以节省终端设备的功耗。
在一个可能的设计中，所网络设备向所述终端设备发送所述下行填充数据包，方法可以为：所述网络设备向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub-PDU，所述MAC sub-PDU对应的逻辑信道标识LCID取值为63。这样网络设备可以发送准确的下行填充数据包。
在一个可能的设计中，所述网络设备向所述终端设备发送下行控制信息DCI，所述DCI用于调度所述下行填充数据包，所述DCI指示所述终端设备在收到所述下行填充数据包后在所述第二时长内不监测PDCCH。这样网络设备可以通过调度下行填充数据包触发终端设备不监测PDCCH。
在一个可能的设计中，所述DCI为DCI格式1_0。
第五方面，本申请提供了一种通信方法，该方法可以包括：网络设备向终端设备发送下行填充数据包，并且网络设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。这样，可以通过向终端设备发送下行填充数据包，触发对DRX-inactivitytimer的不启动，或对运行的DRX-inactivitytimer不重启或停止，可以避免延长终端设备的激活时间，从而可以减少终端设备的功耗。
在一个可能的设计中，所网络设备向所述终端设备发送所述下行填充数据包，方法可以为：所述网络设备向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub-PDU，所述MAC sub-PDU对应的逻辑信道标识LCID取值为63。这样网络设备可以发送准确的下行填充数据包。
第六方面，本申请还提供了一种通信装置，所述通信装置可以是终端设备，该通信装置具有实现上述第一方面或第一方面的各个可能的设计示例中，或者上述第三方面或第三方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括收发单元和处理单元，这些单元可以执行上述第一方面或第一方面的各个可能的设计示例中，或者上述第三方面或第三方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发信息或数据，以及用于与通信系统中的其他设备进行通信交互， 所述处理器被配置为支持所述通信装置执行上述第一方面或第一方面的各个可能的设计示例中，或者上述第三方面或第三方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第七方面，本申请还提供了一种通信装置，所述通信装置可以是网络设备，该通信装置具有实现上述第二方面或第二方面的各个可能的设计示例中，上述第四方面或第四方面的各个可能的设计示例中，上述第五方面或第五方面的各个可能的设计示例中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，所述通信装置的结构中包括收发单元和处理单元，这些单元可以执行上述第二方面或第二方面的各个可能的设计示例中，上述第四方面或第四方面的各个可能的设计示例中，上述第五方面或第五方面的各个可能的设计示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一个可能的设计中，所述通信装置的结构中包括收发器和处理器，可选的还包括存储器，所述收发器用于收发信息或数据，以及用于与通信系统中的其他设备进行通信交互，所述处理器被配置为支持所述通信装置执行上述第二方面或第二方面的各个可能的设计示例中，上述第四方面或第四方面的各个可能的设计示例中，上述第五方面或第五方面的各个可能的设计示例中的相应的功能。所述存储器与所述处理器耦合，其保存所述通信装置必要的程序指令和数据。
第八方面，本申请实施例提供了一种通信系统，可以包括上述提及的终端设备和网络设备等。
第九方面，本申请实施例提供的一种计算机可读存储介质，该计算机可读存储介质存储有程序指令，当程序指令在计算机上运行时，使得计算机执行本申请实施例第一方面及其任一可能的设计中，或第二方面及其任一可能的设计中所述的方法。示例性的，计算机可读存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括非瞬态计算机可读介质、随机存取存储器(random-access memory，RAM)、只读存储器(read-only memory，ROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。
第十方面，本申请实施例提供一种计算机程序产品，包括计算机程序代码或指令的，当计算机程序代码或指令在计算机上运行时，使得上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中所述的方法被执行。
第十一方面，本申请还提供了一种芯片，包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以使所述芯片实现上述第一方面或第一方面任一种可能的设计中，或者上述第二方面或第二方面任一种可能的设计中，或者上述第三方面或第三方面任一种可能的设计中，或者上述第四方面或第四方面任一种可能的设计中，或者上述第五方面或第五方面任一种可能的设计中所述的方法。
上述第三方面至第八方面中的各个方面以及各个方面可能达到的技术效果请参照上述针对第一方面或第一方面中的各种可能方案，或者第二方面或第二方面中的各种可能方案，或者第三方面或第三方面中的各种可能方案，或者第四方面或第四方面中的各种可能 方案，或者第五方面或第五方面中的各种可能方案可以达到的技术效果说明，这里不再重复赘述。
附图说明
图1为本申请提供的一种通信系统的架构示意图；
图2为本申请提供的一种跳过PDCCH监测的示意图；
图3为本申请提供的一种网络设备使用scheduling DCI指示PDCCH skipping的示意图；
图4为本申请提供的一种通信方法的流程图；
图5为本申请提供的一种网络设备通过调度填充数据包的第一DCI指示PDCCH skipping的示意图；
图6为本申请提供的一个MAC PDU包含一个或多个MAC sub PDU的示意图；
图7为本申请提供的一种CDRX周期的示意图；
图8为本申请提供的一种网络设备指示被配置了CDRX的终端设备在一个时间段不监测PDCCH的示意图；
图9为本申请提供的另一种通信方法的流程图；
图10为本申请提供的另一种通信方法的流程图；
图11为本申请提供的一种通信装置的结构示意图；
图12为本申请提供的一种通信装置的结构图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种通信方法及装置，用以减少终端设备的功耗。其中，本申请所述方法和装置基于同一技术构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
在本申请中的描述中，“至少一个(种)”是指一个(种)或者多个(种)，多个(种)是指两个(种)或者两个(种)以上。
为了更加清晰地描述本申请实施例的技术方案，下面结合附图，对本申请实施例提供的通信方法及装置进行详细说明。
图1示出了本申请实施例涉及的通信系统的架构，所述通信系统的架构中包括网络设备和终端设备，其中：
所述网络设备为具有无线收发功能的设备或可设置于该网络设备的芯片，该网络设备包括但不限于：基站(generation node B，gNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，无线保真(wireless fidelity，Wi-Fi)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission and reception point，TRP或者transmission point，TP)等，还可以为构成gNB或传输点的网络节点，如 基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括射频单元(radio unit，RU)。CU实现gNB的部分功能，DU实现gNB的部分功能，比如，CU实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能，DU实现无线链路控制(radio link control，RLC)、媒体接入控制(media access control，MAC)和物理(physical，PHY)层的功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令或PHCP层信令，也可以认为是由DU发送的，或者，由DU+RU发送的。可以理解的是，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的设备。此外，CU可以划分为接入网RAN中的网络设备，也可以将CU划分为核心网CN中的网络设备，对此不作限定。
所述终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智能穿戴设备(智能眼镜、智能手表、智能耳机等)、智慧家庭(smart home)中的无线终端等等，也可以是能够设置于以上设备的芯片或芯片模组(或芯片系统)等。本申请的实施例对应用场景不做限定。本申请中将具有无线收发功能的终端设备及可设置于前述终端设备的芯片统称为终端设备。
需要说明的是，图1所示的通信系统可以但不限于为第四代(4th Generation，4G)系统、第五代(5th Generation，5G)系统，如新一代无线接入技术(new radio access technology，NR)，可选的，本申请实施例的方法还适用于未来的各种通信系统，例如第六代(6th Generation，6G)系统或者其他通信网络等。
在NR中，数据传输的过程可以如下所述：
网络设备调度终端设备接收下行数据，或网络设备调度终端设备发送上行数据的时候，首先会发送下行控制信息(downlink control information，DCI)，DCI中包含一个数据调度信息，该数据调度信息会指示物理下行共享信道(physical downlink shared channel，PDSCH)(其中通常会包含下行数据)或物理上行共享信道(physical uplink shared channel，PUSCH)(其中通常会包含上行数据)的传输参数，在这些传输参数中，包括PDSCH/PUSCH的时频域资源位置。具体地，物理下行控制信道(physical downlink control channel，PDCCH)中携带上述DCI。其中，对于下行数据，网络设备会通过DCI中的时域资源分配(time domain resource allocation，TDRA)字段指示K0值，用于确定PDCCH和PDSCH之间的时隙间隔；对于上行数据，网络设备会通过DCI中的TDRA字段指示K2值，用于确定PDCCH和PUSCH之间的时隙间隔。
网络设备在DCI中指示的时频域资源位置，发送PDSCH，终端设备在对应位置接收；或者，终端设备在DCI中指示的时频域资源位置，发送PUSCH，网络设备在对应位置接收。
终端设备在接收自己的DCI时，需要在下行控制区域中盲检(blind detect，BD)发送给自己的PDCCH，即终端设备监测(monitor)许多PDCCH候选位置(PDCCH candidate)，从中找出是否有发给自己的。
基于上述描述，终端设备会频繁地监测PDCCH，但是若在一段时间内，终端设备并没有业务发生，即没有下行数据或上行数据需要传输时，网络设备不会发送PDCCH调度PDSCH或PUSCH，此时，终端设备即使监测PDCCH也无法接收到发送给自己的PDCCH。若终端设备在这些时间仍持续监测PDCCH，会造成终端设备的功耗。
为了降低终端设备的功耗，一种可能的方案是，引入跳过PDCCH(PDCCH skipping)的概念，具体的，网络设备可以向终端设备发送一个指示信息，指示终端设备可以跳过一段时间的PDCCH监测。终端设备跳过一段时间的PDCCH监测可以等效描述为终端设备在一段时间内不监测PDCCH，这段不监测PDCCH的时间可以被称为跳过时长(skipping duration)。例如图2所示的跳过PDCCH监测的示意图，终端设备本来每个时隙都需要监测PDCCH，当终端设备被网络设备指示一段时间不需要监测PDCCH后，则终端设备可以在被指示的这段时间内不监测PDCCH。
然而，网络设备只能通过调度(scheduling)DCI来触发终端设备的PDCCH skipping。也即可以指示PDCCH skipping的DCI，必须是调度数据传输的DCI。例如，scheduling DCI中包含一个PDCCH监测自适应指示(PDCCH monitoring adaptation indication)字段，该字段为1～2比特(bit)，可以指示PDCCH skipping。需要说明的是，该字段既可以指示PDCCH skipping，又可以指示搜索空间组切换(search space set group switching，SSSG switching)，本申请中仅以PDCCH skipping为例说明。
其中，网络设备可以为终端设备配置1～3个跳过时长(skipping duration)，并通过1～2bit指示每次使用的skipping duration是多长。例如，当网络设备配置了1个skipping duration(长度为T1)时，scheduling DCI会包含1bit，取值‘0’表示不执行PDCCH skipping(即正常监测PDCCH)，取值‘1’表示在T1的时间长度内，不监测PDCCH。再例如，网络设备配置了2个skipping duration(长度为T1和T2)时，scheduling DCI会包含2bit，取值‘00’表示不执行PDCCH skipping(即正常监测PDCCH)；取值‘01’表示在T1的时间长度内，不监测PDCCH；取值‘10’表示在T2的时间长度内，不监测PDCCH。再例如，网络设备配置了3个skipping duration(长度为T1、T2和T3)时，scheduling DCI会包含2bit，取值‘00’表示不执行PDCCH skipping(即正常监测PDCCH)；取值‘01’表示在T1的时间长度内，不监测PDCCH；取值‘10’表示在T2的时间长度内，不监测PDCCH；取值‘11’表示在T3的时间长度内，不监测PDCCH。需要说明的是，上述比特的取值与对应含义的关系仅为示例，可以有其他指示方式，例如当网络设备配置了1个skipping duration(长度为T1)时，scheduling DCI会包含1bit，取值‘1’表示不执行PDCCH skipping(即正常监测PDCCH)，取值‘0’表示在T1的时间长度内，不监测PDCCH。本申请对此不作限定。
网络设备使用scheduling DCI指示PDCCH skipping时，通常是在每次终端设备业务调度的最后一个scheduling DCI中，指示PDCCH skipping。例如图3所示，当终端设备持续有业务传输时，调度数据(即调度PDSCH)的PDCCH中携带的DCI，始终指示“不跳过(no skipping)PDCCH”(即持续监测PDCCH)，以便快速完成数据传输。在一次业务的最后一次传输的PDCCH中，网络设备可以指示在一段时间(即跳过时长(skipping duration)) 内不监测PDCCH，其中网络设备可以通过检查缓存中是否还有该终端设备的待传数据来判断是否为最后一次传输。但是如图3中黑色部分所示，在跳过时长之后，若终端设备的业务尚未到达，网络设备一般不会调度终端设备的数据传输，也就无法发送scheduling DCI，进而无法指示PDCCH skipping，此时终端设备只能持续监测PDCCH，从而导致终端设备功耗浪费。
基于此，本申请提出了一种通信方法，可以实现在终端设备无业务到达时，也可以指示终端设备在一段时间内不监测PDCCH，从而减少终端设备的功耗。
需要说明的是，在以下的实施例中，以终端设备和网络设备为例对本申请提供的通信方法进行详细说明，应理解终端设备执行的操作也可以通过终端设备中的处理器，或者是芯片或芯片系统，或者是一个功能模块等实现，网络设备执行的操作也可以通过网络设备中的处理器，或者是芯片或芯片系统，或者是一个功能模块等实现，对本申请对此不作限定。
基于以上描述，本申请实施例提供的一种通信方法，适用于图1所示的通信系统。参阅图4所示，该方法的具体流程可以包括：
步骤401：网络设备确定第一DCI，第一DCI用于调度填充数据包(padding包)，第一DCI指示终端设备在第一时长内不监测PDCCH。
步骤402：网络设备向终端设备发送第一DCI。
步骤403：终端设备根据第一DCI确定在第一时长内不监测PDCCH。
本申请通信方法，通过调度填充数据包的第一DCI来指示终端设备在第一时长内不监测PDCCH时，可以使得终端设备在无业务到达时也能实现跳过PDCCH的监测，从而减少在终端设备的功耗。例如图5所示，当终端设备持续有业务传输时，调度数据(即调度PDSCH)的PDCCH中携带的DCI，始终指示“不跳过(no skipping)PDCCH”(即持续监测PDCCH)，以便快速完成数据传输。在一次业务的最后一次传输的PDCCH中，网络设备可以指示在一段时间(即跳过时长(skipping duration))内不监测PDCCH。进而，在跳过时长之后，若终端设备的业务尚未到达，网络设备可以通过调度填充数据包的第一DCI指示PDCCH skipping，从而减少终端设备的功耗。
需要说明的是，图5中示出的终端设备不监测PDCCH的两个时长可以相同，也可以不相同，本申请不作限定。当两个时间段不同时，一种可能的方式中，表明网络设备为终端设备配置了至少两个跳过时长，网络设备两次指示的不监测PDCCH的时长不同。或者，两个时长也可以是预定义的，本申请不作限定。
在一种可选的实施方式中，网络设备确定通过第一DCI指示终端设备在第一时长内不监测PDCCH之前，网络设备可以确定终端设备在预设时长内无业务到达，或者网络设备确定没有终端设备对应的缓存数据。
其中，预设时长可以为网络设备发送第一DCI之前的一段时间，或预设时长可以为网络设备发送第一DCI之后的一段时间，或所述预设时长也可以为网络设备发送第一DCI的时刻。当预设时长为终端设备发送第一DCI之后的一段时间时，预设时长可以小于第一时长，可以等于第一时长，也可以大于第一时长，本申请对此不作限定。
终端设备无业务到达可以指无业务数据传输、无数据到达、无下行数据到达、无需给终端设备发送RRC消息或媒体接入控制控制单元(media access control control element，MAC CE)等。
例如，当预设时长为网络设备发送第一DCI之前的一段时间时，网络设备可以在这段时间内判断是否有来自核心网侧的终端设备的数据，当确定没有来自核心网侧的终端设备的数据时，网络设备确定终端设备在预设时长内无业务到达。
又例如，当预设时长为网络设备发送第一DCI之后的一段时间，或者为网络设备发送第一DCI的时刻时，网络设备可以通过预测算法进行预测，来确定终端设备在预设时长内无业务到达。其中，预测算法本申请不作限定。
网络设备确定没有终端设备对应的缓存数据时，可以确定终端设备对应的缓存(buffer)为空。
示例性的，第一DCI可以包括以下两种情况：
情况a1、第一DCI可以用于调度PDSCH。
情况a2、第一DCI可以用于调度PUSCH。
在上述情况a1中，第一DCI可以为小区无线网络临时标识(cell-radio network temporary identity，C-RNTI)加扰的DCI格式(format)1_1或DCI格式1_2；或者，第一DCI可以为调制编码方式小区特定无线网络临时标识(modulation and coding scheme-cell-radio network temporary identifier，MCS-C-RNTI)加扰的DCI格式1_1或DCI格式1_2；或者，第一DCI可以为配置调度无线网络临时标识(configured scheduling-radio network temporary identity，CS-RNTI)加扰的DCI格式1_1或DCI格式1_2。
在上述情况a1中，网络设备向终端设备发送PDSCH(相应地终端设备从网络设备接收PDSCH)，PDSCH中包含媒体接入控制子协议数据单元(media access control sub protocol data unit，MAC sub PDU)，MAC sub-PDU对应的逻辑信道标识(logical channel identify，LCID)取值为63。
通常一个PDSCH中包含一个媒体接入控制协议数据单元(media access control protocol data unit，MAC PDU)。如图6所示，一个MAC PDU中可以包含一个或多个MAC sub PDU，每个MAC sub PDU的子头(subheader)包含LCID，LCID用于指示对应的MAC sub PDU的作用。例如，LCID的取值不同可以指示的MAC sub PDU的作用不同。如下表1所示，分别为LCID的不同取值对应的含义，从表1中可以看出当LCID取值为63时，可以表示对应的MAC sub-PDU是padding包，padding包表示不包含有意义的数据。
因此，在上述情况a1中，网络设备向终端设备发送的PDSCH中包含的MAC sub-PDU对应的LCID取值为63时，即表示网络设备向终端设备发送的是padding包。
表1

由于终端设备收到DCI后，要根据DCI接收PDSCH或者发送PDSCH，而通常情况下，终端设备发送PUSCH的功耗比接收PDSCH的功耗大，因此从终端设备节能的角度出发，通过上述情况a1使用调度PDSCH(调度padding)的第一DCI来指示终端设备在第一时长内不监测PDCCH时，通常可以使得终端设备的功耗相对使用情况a2中的第一DCI时的功耗更低。
在上述情况a2中，第一DCI可以为C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，第一DCI可以为MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，第一DCI可以为CS-RNTI加扰的DCI格式0_1或DCI格式0_2。
在上述情况a2中，当终端设备没有被配置上行跳过功能时，终端设备向网络设备发送PUSCH(相应地网络设备从终端设备接收PUSCH)，PUSCH中包含MAC sub PDU，MAC sub PDU对应的LCID取值为63。
与PDSCH同理，通常一个PUSCH中包含一个MAC PDU，仍如图6所示，一个MAC  PDU中可以包含一个或多个MAC sub PDU，每个MAC sub PDU的子头(subheader)包含LCID，LCID用于指示对应的MAC sub PDU的作用。从表1中可以看出当LCID取值为63时，可以表示对应的MAC sub-PDU是padding包，padding包表示不包含有意义的数据。
因此，在上述情况a2中，终端设备向网络设备发送的PUSCH中包含的MAC sub-PDU对应的LCID取值为63时，即表示终端设备向网络设备发送的是padding包。
一种可选的实施方式中，当终端设备没有被配置上行跳过功能时，当终端设备有业务临时到达，终端设备可以向网络设备发送包含上行数据的PUSCH。在这种情况下，终端设备不向网络设备发送padding包。在终端设备未向网络设备发送调度请求(scheduling request，SR)或缓存状态报告(buffer status report，BSR)的情况下，网络设备通过第一DCI调度终端设备发送PUSCH时，无法得知终端设备是否有上行数据待发送。终端设备收到第一DCI后，会根据自身实际情况，有上行数据时在PUSCH中包含上行数据，无上行数据时在PUSCH中包含padding包。若终端设备接收到第一DCI时，恰好有上行数据已经到达，即使终端设备尚未发送对应的SR或BSR请求网络设备的调度，终端设备也可以通过第一DCI调度的PUSCH将上行数据发给网络设备。
在上述情况a2中，当终端设备被配置了上行跳过功能时，终端设备可以不向网络设备发送PUSCH。
当终端设备被配置了上行跳过功能时，终端设备收到调度PUSCH的DCI且没有上行数据需要发送时，终端设备可以不发送PUSCH。也就是说，在上述情况a2中，当终端设备被配置了上行跳过功能时，网络设备发送第一DCI后，终端设备既不需要发送PUSCH，也不需要接收PDSCH，因此从终端设备节能的角度出发，终端设备被配置了上行跳过功能的情况下，通过上述情况a2使用调度PUSCH(调度padding)的第一DCI来指示终端设备在第一时长内不监测PDCCH时，可以使得终端设备的功耗相对使用情况a1中的第一DCI时的功耗更低。
可选的，当终端设备被配置了上行跳过功能时，如果终端设备临时有业务到达，也即需要发送上行数据时，终端设备可以通过网络设备调度的PUSCH向网络设备发送上行数据。这种情况下，终端设备无需再通过调度请求(scheduling request，SR)向网络设备请求上行资源，从而可以降低业务时延。
在一种可能的实施方式中，终端设备可以被配置了连接态非连续接收(connected discontinuous reception，CDRX)。C-DRX周期可以为长的DRX周期，还可以为短的DRX周期，其中长的DRX周期是默认必须配置、而短的DRX周期是可选配置，若配置了短的DRX周期，终端设备会在使用短的DRX周期的时候开启短周期定时器(ShortCycleTimer)，当ShortCycleTimer超时则转换为长的DRX周期。
例如，如图7所示，CDRX周期包括“持续时间(On Duration)”部分和“DRX机会(Opportunity for DRX)”部分。终端设备在每个CDRX周期内的持续时间(OnDuration)中监测PDCCH。若在OnDuration中未接收到新传数据调度(即未接收到指示初传(new transmission)的PDCCH)，则在OnDuration结束后进入在Opportunity for DRX，停止监测PDCCH，直到下一个周期的OnDuration再开始监测PDCCH。若在OnDuration中接收到了新传数据调度(即接收到指示初传(new transmission)的PDCCH)，则终端设备启动不活动定时器(或不激活定时器)(InactivityTimer或DRX-inactivitytimer)，在InactivityTimer运行过程中终端设备仍然监测PDCCH。若在InactivityTimer运行过程中又收到新传数据调 度，则会重启InactivityTimer。无论是OnDuration内还是InactivityTimer运行时，都被称为激活时间(active time)，终端设备在active time内要监测PDCCH。InactivityTimer的重启，可以理解为在延长终端设备的active time。当InactivityTimer超时，终端设备停止监测PDCCH。
其中，判断是否是“新传数据调度”的方法是看DCI中的新数据指示(new data indicator，NDI)(NDI为1-bit，取值为‘0’或‘1’)字段是否发生了翻转(toggle)。若对同一个混合自动重传请求进程(hybrid automatic repeat request process，HARQ process)(即HARQ进程数(HARQ process number，HPN)字段取值相同)，终端设备收到的DCI中的NDI相比前一次收到的DCI的NDI发生了翻转(例如NDI从0翻转为1，或者NDI从1翻转为0)，则认为使用该HARQ process传输了新的数据；若终端设备收到的DCI中的NDI与前一次收到的DCI的NDI相同，则认为使用该HARQ process进行了数据重传。
在一些实施例中，当网络设备指示被配置了CDRX的终端设备在一个时间段不监测PDCCH时，可以如图8所示，网络设备可以通过调度(scheduling)DCI指示终端设备在active time内的某些时间段不监测PDCCH，从而在CDRX机制的基础上的增加终端设备的休眠时间。这种情况下，仍会存在当终端设备无业务到达时网络设备无法指示终端设备跳过PDCCH。
而采用上述情况a1中的方法，通过调度PDSCH(包含填充数据包)的第一DCI可能会导致InactivityTimer的重启，导致延长终端设备的active time。而延长active time可能会导致终端设备需要监测PDCCH的时长增加，增加终端设备的功耗。
基于此，在上述情况a1中，当终端设备被配置了CDRX时，终端设备从网络设备接收包含填充数据包的PDSCH后，终端设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，终端设备从网络设备接收包含填充数据包的PDSCH后，不重启或停止DRX-inactivitytimer。
同理，当终端设备被配置了CDRX时，网络设备向终端设备发送包括填充数据包的PDSCH后，网络设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，网络设备向终端设备发送包括填充数据包的PDSCH后，不重启或停止DRX-inactivitytimer。
而采用上述情况a2中的方法，通过调度PUSCH(包含填充数据包)的第一DCI也可能会导致InactivityTimer的重启，导致延长终端设备的active time，延长active time可能会导致终端设备需要监测PDCCH的时长增加，增加终端设备的功耗。
因此，在上述情况a2中，当终端设备被配置了CDRX且未被配置上行跳过功能时，终端设备向网络设备发送包含填充数据包的PUSCH后，终端设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，终端设备向网络设备发送包含填充数据包的PUSCH后，不重启或停止DRX-inactivitytimer。
同理，当终端设备被配置了CDRX时，网络设备接收终端设备发送的包括填充数据包的PUSCH后，网络设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，网络设备接收终端设备发送的包括填充数据包的PUSCH后，不重启或停止DRX-inactivitytimer。网络设备在完成PUSCH的解码后，即可确定PUSCH中包含的是否是padding包，也即可以确定是否启动或重启或停止DRX-inactivitytimer。
或者，在上述情况a2中，当终端设备被配置了CDRX且被配置了上行跳过功能时， 终端设备不发送PUSCH时，也即终端设备确定(因为无数据需要传输)不发送PUSCH后，终端设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，终端设备不发送PUSCH时，也即终端设备确定(因为无数据需要传输)不发送PUSCH后，不重启或停止DRX-inactivitytimer。
同理，当终端设备被配置了CDRX时，网络设备在第一DCI指示的位置(即第一DCI调度PUSCH时指示的终端设备发送PUSCH的时频位置)未接收到终端设备发送的PUSCH，网络设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，网络设备在第一DCI指示的位置未接收到终端设备发送的PUSCH，不重启或停止DRX-inactivitytimer。
通过上述方法，可以避免终端设备的active time延长，从而节省终端设备的功耗。
在一种可选的实施方式中，在上述情况a1和a2的方法中，第一DCI中的NDI字段的取值与第三DCI中NDI字段的取值可以不同，第三DCI为与第一DCI的HARQ HPN字段的取值相同的前一个DCI。此种情况下，第一DCI可以理解为新传DCI。
当终端被配置了CDRX，第一DCI为新传DCI时，由于通过第一DCI调度的padding包(包含在PDSCH或PUSCH中)来指示终端设备跳过不监测PDCCH，所以终端设备和网络设备无需启动DRX-inactivitytimer，进而通过终端设备和网络设备不启动、不重启或停止DRX-inactivitytimer，实现避免终端设备的active time延长，从而节省终端设备的功耗。
在一种可选的实施方式中，在上述情况a1的方法中，第一DCI中NDI字段的取值可以与第二DCI中NDI字段的取值相同，第二DCI为与第一DCI的HARQ HPN字段的取值相同的前一个DCI。此种情况可以理解为第一DCI为重传DCI。
在第一DCI为重传DCI时，在终端设备从网络设备接收第一DCI之前，终端设备从网络设备接收第二DCI后，向网络设备发送正确应答(acknowledgement character，ACK)信息。
通常情况下，终端设备对一个PDSCH错误接收后，会反馈NACK，让网络设备调度相同数据的重传。当终端设备收到重传数据后，会把接收到的重传数据与之前已经接收过且存在缓存(buffer)中的数据合并解码。当第一DCI为重传DCI时，虽然网络设备发送了重传DCI，但是在相同HARQ进程的数据已经正确传输(终端设备反馈ACK信息)后，终端设备通常会清空在buffer中存储的历史的数据包。因此重传DCI调度的数据通常不会和之前接收过的数据被合并解码，而是被单独解码。终端设备在单独解码第一DCI调度的数据包后，可以识别当前调度的数据包为padding包。
另外，当终端被配置了CDRX，第一DCI为重传DCI时，终端设备和网络设备不启动、不重启或停止DRX-inactivitytimer可以避免终端设备的active time延长，从而节省终端设备的功耗。
采用本申请实施例提供的通信方法，在终端设备无业务到达时，可以通过调度填充数据包的DCI来指示终端设备在第一时长内不监测PDCCH，从而减少终端设备的功耗。
本申请实施例还提供的另一种通信方法，适用于图1所示的通信系统。参阅图9所示，该方法的具体流程可以包括：
步骤901：网络设备向终端设备发送下行填充数据包，相应地终端设备从网络设备接收下行填充数据包。
在一种可选的实施方式中，网络设备可以通过如下方式向终端设备发送下行填充数据包：网络设备向终端设备发送PDSCH，PDSCH中包含MAC sub-PDU，MAC sub-PDU对应的LCID取值为63。
具体的，关于PDSCH中MAC sub-PDU对应的LCID取值为63指示填充数据包的相关描述可以参见图4所示的实施例中结合图6和表1对PDSCH的说明，此处不再详细描述。
步骤902：网络设备确定终端设备在第二时长内不监测PDCCH。
步骤903：终端设备根据下行填充数据包确定在第二时长内不监测PDCCH。
需要说明的是，步骤902和步骤903的先后顺序本申请不作限定。
示例性的，网络设备可以向终端设备发送DCI，该DCI用于调度该下行填充数据包，DCI指示终端设备在收到下行填充数据包后在第二时长内不监测PDCCH。这样终端设备在接收到下行数据包后可以确定在第二时长内不监测PDCCH。
可选的，第二时长可以是网络设备为终端设备配置的，也可以预定义的，也可以是网络设备在向终端设备发送下行填充数据包时同时指示的，例如，网络设备向终端设备发送的PDSCH中既包含下行填充数据包也包含第二时长。
示例性的，该DCI可以为DCI格式1_0，也可以为DCI格式1_1或DCI格式1_2。
通过上述方法，在终端设备接收到下行填充数据包后，可以实现一段时长的不监测PDCCH，从而可以节省终端设备的功耗。
本申请实施例还提供的另一种通信方法，适用于图1所示的通信系统。参阅图10所示，该方法的具体流程可以包括：
步骤1001：网络设备向终端设备发送下行填充数据包。
具体的，网络设备向终端设备发送下行填充数据包的相关描述可以参见上述步骤901中的相关描述，此处不再赘述。
步骤1002：网络设备不启动DRX-inactivitytimer；或者，当DRX-inactivitytimer运行时，网络设备不重启或停止DRX-inactivitytimer。
步骤1003：终端设备根据下行填充数据包确定终端设备不启动DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，确定终端设备不重启或停止DRX-inactivitytimer。
需要说明的是，步骤1002和步骤1003的先后顺序本申请不作限定。
通过上述方法，在终端设备接收到下行填充数据包后，通过对DRX-inactivitytimer的不启动，或对运行的DRX-inactivitytimer不重启或停止，可以避免延长终端设备的激活时间，从而可以减少终端设备的功耗。
基于以上实施例，本申请实施例还提供了一种通信装置，参阅图11所示，通信装置1100可以包括收发单元1101和处理单元1102。其中，所述收发单元1101用于所述通信装置1100接收信息(消息或数据)或发送信息(消息或数据)，所述处理单元1102用于对所述通信装置1100的动作进行控制管理。所述处理单元1102还可以控制所述收发单元1101执行的步骤。
示例性地，该通信装置1100具体可以是上述实施例中的网络设备、所述网络设备中的处理器，或者芯片，或者芯片系统，或者是一个功能模块等；或者，该通信装置1100具体可以是上述实施例中的终端设备、所述终端设备的处理器，或者芯片，或者芯片系统，或者是一个功能模块等。
在一个实施例中，所述通信装置1100用于实现上述图4所述的实施例中终端设备的功能时，具体可以包括：所述收发单元1101用于从网络设备接收第一DCI，所述第一DCI用于调度填充数据包，所述第一DCI指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH；所述处理单元1102用于根据所述第一DCI确定在所述第一时长内不监测PDCCH。
一种可选的实施方式中，所述第一DCI用于调度物理下行共享信道PDSCH。
示例性的，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式1_1或DCI格式1_2。
可选的，所述收发单元1101还用于从所述网络设备接收物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
另一种可选的实施方式中，所述第一DCI用于调度物理上行共享信道PUSCH。
示例性的，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。
可选的，所述收发单元1101还用于向所述网络设备发送物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
在一种可能的方式中，所述收发单元1101还用于向所述网络设备发送物理上行共享信道PUSCH，其中所述PUSCH包含所述填充数据包；所述处理单元1102还用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
在一种示例中，当所述终端设备被配置了上行跳过功能时，所述收发单元1101还用于不向所述网络设备发送物理上行共享信道PUSCH。
另一种可能的方式中，当所述收发单元1101还用于不向所述网络设备发送物理上行共享信道PUSCH时，所述处理单元1102还用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
一种示例中，所述收发单元1101还用于从所述网络设备接收物理下行共享信道PDSCH，其中所述PDSCH包括所述填充数据包；所述处理单元1102还用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
可选的，所述第一DCI中新数据指示NDI字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
示例性的，所述收发单元1101还用于在从网络设备接收所述第一DCI之前，从网络设备接收所述第二DCI，向所述网络设备发送正确应答ACK信息。
可选的，所述第一DCI中的新数据指示NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
在另一个实施例中，所述通信装置1100用于实现上述图4所述的实施例中网络设备的功能时，具体可以包括：所述处理单元1102用于确定第一下行控制信息DCI，所述第一DCI用于调度填充数据包，所述第一DCI指示终端设备在第一时长内不监测物理下行控制信道PDCCH；所述收发单元1101用于向所述终端设备发送所述第一DCI。
可选的，所述处理单元1102还用于：在所述收发单元1101向所述终端设备发送所述第一DCI之前，确定所述终端设备在预设时长内无业务到达；或者，确定没有所述终端设备对应的缓存数据。
一种可选的实施方式中，所述第一DCI用于调度物理下行共享信道PDSCH。
示例性的，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式1_1或DCI格式1_2。
可选的，所述网络设备向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
一种可选的实施方式中，所述第一DCI用于调度物理上行共享信道PUSCH。
示例性的，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者，所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。
一种可能的设计中，所述收发单元1101还用于从所述终端设备接收物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
另一种可能的设计中，当所述终端设备被配置了上行跳过功能时，所述收发单元1101还用于不从所述终端设备接收PUSCH。
一种示例，所述收发单元1101还用于从所述终端设备接收物理上行共享信道PUSCH，其中所述PUSCH包含所述填充数据包；所述处理单元1102还用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
另一种示例，所述处理单元1102还用于在所述第一DCI指示的位置所述收发单元1101未接收到所述终端设备发送的物理上行共享信道PUSCH，则不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
又一种示例中，所述收发单元1101还用于向所述终端设备发送物理下行共享信道PDSCH，其中所述PDSCH包括所述填充数据包；所述处理单元1102还用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
可选的，所述第一DCI中新数据指示NDI字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
示例性的，所述收发单元1101还用于在向所述终端设备发送所述第一DCI之前，向所述终端设备发送所述第二DCI，从所述终端设备接收正确应答ACK信息。
可选的，所述第一DCI中的新数据指示NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
在另一个实施例中，所述通信装置1100用于实现上述图9或图10所述的实施例中终端设备的功能时，具体可以包括：所述收发单元1101用于从网络设备接收下行填充数据包；所述处理单元1102用于根据所述下行填充数据包确定所述终端设备的第一操作。
示例性的，所述收发单元1101在从所述网络设备接收所述下行填充数据包时，可以用于：从所述网络设备接收物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
一种可选的实施方式中，所述第一操作为在第二时长内不监测物理下行控制信道PDCCH。
可选的，所述收发单元1101还用于从所述网络设备接收下行控制信息DCI，所述DCI用于调度所述下行填充数据包，所述DCI指示所述终端设备在收到所述下行填充数据包后在所述第二时长内不监测PDCCH。
示例性的，所述DCI为DCI格式1_0。
另一种可选的实施方式中，所述第一操作为不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述第一操作为不重启或停止所述DRX-inactivitytimer。
在另一个实施例中，所述通信装置1100用于实现上述图9所述的实施例中网络设备的功能时，具体可以包括：所述收发单元1101用于向终端设备发送下行填充数据包；所述处理单元1102用于确定所述终端设备在第二时长内不监测物理下行控制信道PDCCH。
可选的，所述收发单元1101在向所述终端设备发送所述下行填充数据包时，可以用于：向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub-PDU，所述MAC sub-PDU对应的逻辑信道标识LCID取值为63。
示例性，所述收发单元1101还用于向所述终端设备发送下行控制信息DCI，所述DCI用于调度所述下行填充数据包，所述DCI指示所述终端设备在收到所述下行填充数据包后在所述第二时长内不监测PDCCH。
一种示例中，所述DCI为DCI格式1_0。
在另一个实施例中，所述通信装置1100用于实现上述图10所述的实施例中网络设备的功能时，具体可以包括：所述收发单元1101用于向终端设备发送下行填充数据包；所述处理单元1102用于不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，不重启或停止所述DRX-inactivitytimer。
可选的，收发单元1101在向所述终端设备发送所述下行填充数据包时，用于：向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub-PDU，所述MAC sub-PDU对应的逻辑信道标识LCID取值为63。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本申请实施例还提供了一种通信装置，参阅图12所示，通信装置1200可以包括收发器1201和处理器1202。可选的，所述通信装置1200中还可以包括存储器1203。其中，所述存储器1203可以设置于所述通信装置1200内部，还可以设置于所述通信装置1200外部。其中，所述处理器1202可以控制所述收发器1201接收和发送信息、消息或数据等。
具体地，所述处理器1202可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。所述处理器1202还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
其中，所述收发器1201、所述处理器1202和所述存储器1203之间相互连接。可选的，所述收发器1201、所述处理器1202和所述存储器1203通过总线1204相互连接；所述总线1204可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一种可选的实施方式中，所述存储器1203，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。所述存储器1203可能包括RAM，也可能还包括非易失性存储器(non-volatile memory)，例如一个或多个磁盘存储器。所述处理器1202执行所述存储器1203所存放的应用程序，实现上述功能，从而实现通信装置1200的功能。
示例性地，该通信装置1200可以是上述实施例中的网络设备；还可以是上述实施例中的终端设备。
在一个实施例中，所述通信装置1200在实现图4、图9或图10所示的实施例中终端设备的功能时，收发器1201可以实现图4、图9或图10所示的实施例中的由终端设备执行的收发操作；处理器1202可以实现图4、图9或图10所示的实施例中由终端设备执行 的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图4、图9或图10所示的实施例中的相关描述，此处不再详细介绍。
在一个实施例中，所述通信装置1200在实现图4、图9或图10所示的实施例中网络设备的功能时，收发器1201可以实现图4、图9或图10所示的实施例中的由网络设备执行的收发操作；处理器1202可以实现图4、图9或图10所示的实施例中由网络设备执行的除收发操作以外的其他操作。具体的相关具体描述可以参见上述图4、图9或图10所示的实施例中的相关描述，此处不再详细介绍。
基于以上实施例，本申请实施例提供了一种通信系统，该通信系统可以包括上述实施例涉及的终端设备和网络设备等。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的通信方法。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的通信方法。
本申请实施例还提供一种芯片，包括处理器，所述处理器与存储器耦合，用于调用所述存储器中的程序使得所述芯片实现上述方法实施例提供的通信方法。
本申请实施例还提供一种芯片，所述芯片与存储器耦合，所述芯片用于实现上述方法实施例提供的通信方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种通信方法，其特征在于，包括：
    终端设备从网络设备接收第一下行控制信息DCI，所述第一DCI用于调度填充数据包，所述第一DCI指示所述终端设备在第一时长内不监测物理下行控制信道PDCCH；
    所述终端设备根据所述第一DCI确定在所述第一时长内不监测PDCCH。
  2. 如权利要求1所述的方法，其特征在于，所述第一DCI用于调度物理下行共享信道PDSCH。
  3. 如权利要求2所述的方法，其特征在于，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者
    所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者
    所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式1_1或DCI格式1_2。
  4. 如权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述终端设备从所述网络设备接收物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
  5. 如权利要求1所述的方法，其特征在于，所述第一DCI用于调度物理上行共享信道PUSCH。
  6. 如权利要求5所述的方法，其特征在于，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者
    所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者
    所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。
  7. 如权利要求5或6所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
  8. 如权利要求5-7任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送物理上行共享信道PUSCH，其中所述PUSCH包含所述填充数据包；
    所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。
  9. 如权利要求5或6所述的方法，其特征在于，当所述终端设备被配置了上行跳过功能时，所述方法还包括：
    所述终端设备不向所述网络设备发送物理上行共享信道PUSCH。
  10. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述 DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。
  11. 如权利要求2-4任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备从所述网络设备接收物理下行共享信道PDSCH，其中所述PDSCH包括所述填充数据包；
    所述终端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述终端设备不重启或停止所述DRX-inactivitytimer。
  12. 如权利要求2-4、11任一项所述的方法，其特征在于，所述第一DCI中新数据指示NDI字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
  13. 如权利要求12所述的方法，其特征在于，在所述终端设备从网络设备接收所述第一DCI之前，所述方法还包括：
    所述终端设备从所述网络设备接收所述第二DCI，向所述网络设备发送正确应答ACK信息。
  14. 如权利要求2-11任一项所述的方法，其特征在于，所述第一DCI中的新数据指示NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
  15. 一种通信方法，其特征在于，包括：
    网络设备确定第一下行控制信息DCI，所述第一DCI用于调度填充数据包，所述第一DCI指示终端设备在第一时长内不监测物理下行控制信道PDCCH；
    所述网络设备向所述终端设备发送所述第一DCI。
  16. 如权利要求15所述的方法，其特征在于，在所述网络设备向所述终端设备发送所述第一DCI之前，所述方法还包括：
    所述网络设备确定所述终端设备在预设时长内无业务到达；或者
    所述网络设备确定没有所述终端设备对应的缓存数据。
  17. 如权利要求15或16所述的方法，其特征在于，所述第一DCI用于调度物理下行共享信道PDSCH。
  18. 如权利要求17所述的方法，其特征在于，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者
    所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式1_1或DCI格式1_2；或者
    所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式1_1或DCI格式1_2。
  19. 如权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送物理下行共享信道PDSCH，所述PDSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
  20. 如权利要求15或16所述的方法，其特征在于，所述第一DCI用于调度物理上行共享信道PUSCH。
  21. 如权利要求20所述的方法，其特征在于，所述第一DCI为小区无线网络临时标识C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者
    所述第一DCI为调制编码方式小区特定无线网络临时标识MCS-C-RNTI加扰的DCI格式0_1或DCI格式0_2；或者
    所述第一DCI为配置调度无线网络临时标识CS-RNTI加扰的DCI格式0_1或DCI格式0_2。
  22. 如权利要求20或21所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收物理上行共享信道PUSCH，所述PUSCH中包含媒体接入控制子协议数据单元MAC sub PDU，所述MAC sub PDU对应的逻辑信道标识LCID取值为63。
  23. 如权利要求20或21所述的方法，其特征在于，当所述终端设备被配置了上行跳过功能时，所述方法还包括：
    所述网络设备不从所述终端设备接收PUSCH。
  24. 如权利要求20-22任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收物理上行共享信道PUSCH，其中所述PUSCH包含所述填充数据包；
    所述网络端设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。
  25. 如权利要求20-21、23任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备在所述第一DCI指示的位置未接收到所述终端设备发送的物理上行共享信道PUSCH；
    所述网络设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。
  26. 如权利要求17-19任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送物理下行共享信道PDSCH，其中所述PDSCH包括所述填充数据包；
    所述网络设备不启动非连续接收不活动定时器DRX-inactivitytimer；或者，当所述DRX-inactivitytimer运行时，所述网络设备不重启或停止所述DRX-inactivitytimer。
  27. 如权利要求17-19、26任一项所述的方法，其特征在于，所述第一DCI中新数据指示NDI字段的取值与第二DCI中NDI字段的取值相同，所述第二DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
  28. 如权利要求27所述的方法，其特征在于，在所述网络设备向所述终端设备发送所述第一DCI之前，所述方法还包括：
    所述网络设备向所述终端设备发送所述第二DCI，从所述终端设备接收正确应答ACK信息。
  29. 如权利要求17-26任一项所述的方法，其特征在于，所述第一DCI中的新数据指示NDI字段的取值与第三DCI中NDI字段的取值不同，所述第三DCI为与所述第一DCI的混合自动重传请求HARQ进程数HPN字段的取值相同的前一个DCI。
  30. 一种通信装置，其特征在于，包括存储器，处理器和收发器，其中：
    所述存储器用于存储计算机指令；
    所述收发器用于接收和发送信息；
    所述处理器与所述存储器耦合，用于调用所述存储器中的计算机指令，以通过所述收 发器执行如权利要求1-14任一项所述的方法。
  31. 一种通信装置，其特征在于，包括存储器，处理器和收发器，其中：
    所述存储器用于存储计算机指令；
    所述收发器，用于接收和发送信息；
    所述处理器，与所述存储器耦合，用于调用所述存储器中的计算机指令，以通过所述收发器执行如权利要求15-29任一项所述的方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时以执行如权利要求1-14中任一项所述的方法，或者执行如权利要求15-29中任一项所述的方法。
  33. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得如权利要求1-14中任一项所述的方法，或如权利要求15-29中任一项所述的方法被执行。
  34. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-14中任一项所述的方法，或者实现如述权利要求15-29中任一项所述的方法。
PCT/CN2023/078525 2022-03-03 2023-02-27 一种通信方法及装置 WO2023165449A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210204563.7 2022-03-03
CN202210204563 2022-03-03
CN202210397041.3 2022-04-15
CN202210397041.3A CN116761236A (zh) 2022-03-03 2022-04-15 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2023165449A1 true WO2023165449A1 (zh) 2023-09-07

Family

ID=87882957

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/078525 WO2023165449A1 (zh) 2022-03-03 2023-02-27 一种通信方法及装置

Country Status (1)

Country Link
WO (1) WO2023165449A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110868749A (zh) * 2018-08-28 2020-03-06 华为技术有限公司 通信方法、装置及存储介质
WO2020155677A1 (en) * 2019-01-30 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Methods, transmitter device and receiver device for communication of mac pdu
CN111901835A (zh) * 2020-01-21 2020-11-06 中兴通讯股份有限公司 一种信息处理方法、装置、设备和存储介质
CN112436925A (zh) * 2020-08-03 2021-03-02 上海移远通信技术股份有限公司 一种副链路无线通信的方法和装置
CN113163473A (zh) * 2020-01-22 2021-07-23 华为技术有限公司 一种跳过pdcch监测的指示方法及装置
CN113473632A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 物理下行共享信道的调度方法、网络设备及终端设备
WO2021224283A1 (en) * 2020-05-04 2021-11-11 Fraunhofer Gesellschaft zur Förderung der angewandten Forschung e.V. Methods and apparatuses for enhancing the reliability and performance of the physical downlink control channel in a wireless communications network

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110868749A (zh) * 2018-08-28 2020-03-06 华为技术有限公司 通信方法、装置及存储介质
WO2020155677A1 (en) * 2019-01-30 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Methods, transmitter device and receiver device for communication of mac pdu
CN111901835A (zh) * 2020-01-21 2020-11-06 中兴通讯股份有限公司 一种信息处理方法、装置、设备和存储介质
CN113163473A (zh) * 2020-01-22 2021-07-23 华为技术有限公司 一种跳过pdcch监测的指示方法及装置
CN113473632A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 物理下行共享信道的调度方法、网络设备及终端设备
WO2021224283A1 (en) * 2020-05-04 2021-11-11 Fraunhofer Gesellschaft zur Förderung der angewandten Forschung e.V. Methods and apparatuses for enhancing the reliability and performance of the physical downlink control channel in a wireless communications network
CN112436925A (zh) * 2020-08-03 2021-03-02 上海移远通信技术股份有限公司 一种副链路无线通信的方法和装置

Similar Documents

Publication Publication Date Title
WO2019192342A1 (zh) 非连续接收的通信方法、装置、通信设备和通信系统
US10594447B2 (en) Data transmission method, terminal, and ran device
US9591663B2 (en) Scheduling request method, apparatus and system
JP6034885B2 (ja) データブロック伝送の処理時間依存制御
US9295040B2 (en) Packet scheduling in communications
EP2169871B1 (en) Method and apparatus of handling a timer for triggering buffer status report
KR101164117B1 (ko) 무선 통신 시스템상에서 물리 하향 채널의 모니터링 동작을 효율적으로 제어하는 방법
WO2021027963A1 (zh) 一种定时器控制方法、装置及系统
WO2021244501A1 (zh) 通信方法及装置
WO2021170136A1 (zh) 一种通信方法及装置
WO2021147426A1 (zh) 一种跳过pdcch监测的指示方法及装置
WO2019062838A1 (zh) 数据传输方法及装置
WO2017020302A1 (zh) 一种建立数据无线承载的方法及装置
WO2021032022A1 (zh) 一种调度方法及装置
EP3570607B1 (en) Reducing the transmission delay and improving the reliability of uplink data
WO2022021412A1 (zh) Cg配置方法、装置、设备及介质
JP2023536002A (ja) データ送信のための方法および装置
WO2023165449A1 (zh) 一种通信方法及装置
WO2021134151A1 (zh) 通信方法及装置
WO2021062790A1 (zh) 一种数据传输方法及装置
CN116761236A (zh) 一种通信方法及装置
CN113260026B (zh) 一种非连续接收处理方法、终端、装置以及介质
WO2023207568A1 (zh) 一种通信方法及装置
US20240214127A1 (en) Method for data transmission, terminal device, and computer storage medium
WO2024140267A1 (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: 23762848

Country of ref document: EP

Kind code of ref document: A1