Communication method and communication apparatus

By receiving N downlink control messages from network devices and using a cross-timeslot scheduling mechanism, the terminal device communicates in a low-power mode during periods of no data transmission and in a high-power mode during periods of data transmission. This solves the problems of increased heat and reduced battery life in the high-power mode, effectively reducing power consumption and ensuring reliable data reception.

WO2026233257A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/094485
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Terminal devices may experience increased heat, reduced battery life, and decreased performance when operating in high-power modes. How can we effectively reduce power consumption while reliably receiving data?

Method used

By receiving N downlink control messages from network devices, the terminal device communicates in a low-power mode during periods of no data transmission and in a high-power mode during periods of data transmission. Combined with cross-timeslot scheduling and timer mechanisms, it dynamically adjusts the number of receiving antennas and the operating bandwidth to avoid data loss.

Benefits of technology

This significantly reduces the power consumption of terminal devices while ensuring reliable data reception, thus improving the energy-saving effect of terminal devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026094485_12112026_PF_FP_ABST
    Figure CN2026094485_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method and a communication apparatus. The communication method comprises: receiving N pieces of downlink control information (DCI) from a network device, the N pieces of DCI being the first N pieces of DCI received following receipt of first DCI, a time interval between a reception time of any one of the N pieces of DCI and a reception time of the first DCI being greater than or equal to a first duration, and N being a positive integer; and a candidate value of a time interval between each piece of DCI among the N pieces of DCI and a PDSCH scheduled by each piece of DCI is greater than a first value. The technical solution provided in the present application enables a terminal device to effectively reduce power consumption while reliably receiving transmitted data.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510600066.2, filed on May 9, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0003] The power consumption of a terminal device refers to the rate at which the device consumes electrical energy during operation, and is related to the modules that are activated. When a terminal device consistently communicates in a high-power mode, such as using multiple receiving antennas or large bandwidth, it may experience problems such as increased heat, reduced battery life, and decreased performance, thus degrading the user experience. Therefore, reducing the power consumption of terminal devices has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a communication method and a communication device that enables terminal devices to reliably receive and transmit data while effectively reducing power consumption.

[0005] Firstly, a communication method is provided, which can be executed by a communication device. This communication device can be a terminal device, or a component for the terminal device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of the terminal device, etc. The following example uses a terminal device for illustration.

[0006] The communication method includes receiving N downlink control information (DCI) from a network device. The N DCI are the first N DCIs received after receiving the first DCI. The time interval between the reception time of any one of the N DCI and the reception time of the first DCI is greater than or equal to a first duration, where N is a positive integer. The candidate value of the time interval between each of the N DCI and the physical downlink shared channel (PDSCH) scheduled for each DCI is greater than a first value.

[0007] Based on the above technical solution, the terminal device can communicate in a lower power consumption mode (e.g., 2 receiving antennas, 20MHz bandwidth) to reduce power consumption during periods without data transmission; and in a higher power consumption mode (e.g., 4 receiving antennas, 100MHz bandwidth) during data transmission periods to ensure reliable data reception. Furthermore, the terminal device can know in advance that the scheduling method of the first N DCIs during the data transmission period is cross-timeslot scheduling (i.e., DCIs and PDSCHs will definitely not be in the same time slot). Thus, when receiving downlink signals, the terminal device can only buffer the first few symbols of the downlink signals in each of the N time slots containing the N DCIs (e.g., downlink signals within the duration range of the control-resource set (CORESET) corresponding to the first N DCIs), without buffering the subsequent symbols of the downlink signals in each of the N time slots, thereby further improving the energy-saving effect of the terminal device. In addition, the terminal device can also adjust the number of receiving antennas and / or the operating bandwidth before the PDSCH scheduled by the N DCIs arrives to avoid PDSCH data loss.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after receiving the DCI used for scheduling PDSCH and when the timer is not running, starting the timer, the timer's runtime being a first duration.

[0009] Based on the above technical solution, the terminal device can start the timer when preset conditions are met. This allows the terminal device to perform subsequent operations based on the timer's running state; for example, it can operate in a lower power mode when the timer is not running, and in a higher power mode when the timer is running. Simultaneously, the network device can also maintain the timer based on the same conditions, thus ensuring alignment between the terminal device and the network device.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: restarting the timer after receiving the DCI used for scheduling PDSCH and while the timer is running.

[0011] Based on the above technical solution, the terminal device can restart the timer when preset conditions are met. This allows the terminal device to perform subsequent operations based on the timer's running state; for example, it can operate in a lower power mode when the timer is not running, and in a higher power mode when the timer is running. Simultaneously, the network device can also maintain the timer based on the same conditions, thus ensuring alignment between the terminal device and the network device.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, receiving N DCIs from the network device includes: receiving the first DCI among the N DCIs from the network device when the timer is not running.

[0013] Based on the above technical solution, the terminal device can determine whether a new data transmission phase has been entered by combining the running status of the timer, or in other words, whether the received DCI is the first N DCI in a data transmission period, thereby determining whether it can work in a low-power mode when receiving the first N DCI.

[0014] In conjunction with the first aspect, in certain implementations of the first aspect, the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled by each DCI is greater than a first value, including: receiving multiple time domain resource allocation (TDRA) configuration information from network devices, the multiple TDRA configuration information including first TDRA configuration information, and all time intervals corresponding to the first TDRA configuration information being greater than the first value; wherein, the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information.

[0015] Based on the above technical solution, by setting the value of the first value, the terminal device can know in advance that the scheduling mode of the N DCIs is cross-time slot scheduling. The terminal device can receive and decode the physical downlink control channel used to carry each of the N DCIs in a low power consumption working mode, and the power consumption of the terminal device can be further reduced.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, after receiving N DCIs from the network device, the method further includes: receiving a second DCI from the network device, wherein the candidate value of the time interval between the second DCI and the PDSCH scheduled by the second DCI is determined based on the second TDRA configuration information among multiple TDRA configuration information.

[0017] Based on the above technical solution, after receiving the first N DCIs, the terminal device can process other DCIs in a simultaneous time-slot scheduling manner, thereby reducing the latency of the data transmission process of the terminal device.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving first TDRA configuration information from the network device; determining a minimum time interval; and determining a candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI based on the first TDRA configuration information and the minimum time interval.

[0019] Based on the above technical solution, the terminal device can configure the time domain resources corresponding to N DCIs and other DCIs more effectively through the same TDRA configuration information. This reduces the memory usage and resource consumption of the terminal device, and further improves its energy-saving effect.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is the time interval that is greater than or equal to the minimum time interval among all time intervals corresponding to the first TDRA configuration information.

[0021] Based on the above technical solution, by setting the minimum value of the time interval, the terminal device can know in advance that the scheduling mode of N DCIs is cross-time slot scheduling. The terminal device can receive and decode the physical downlink control channel used to carry each of the N DCIs in a low power consumption working mode, and the power consumption of the terminal device can be further reduced.

[0022] Secondly, a communication method is provided, which can be executed by a communication device. This communication device can be a network device, or a component for a network device (such as a chip or circuit, which can be a modem chip, also known as a baseband chip, or a SoC or SIP chip containing a modem core, etc.), or a logic module or software capable of implementing some or all of the functions of a network device, etc. The following example uses a network device for illustration.

[0023] The communication method includes sending N DCIs to the terminal device, wherein the N DCIs are the first N DCIs received after receiving the first DCI, and the time interval between the reception time of any one of the N DCIs and the reception time of the first DCI is greater than or equal to a first duration, and N is a positive integer; wherein, the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled for each DCI is greater than a first value.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, when the timer is not running, the timer starts at the moment after the terminal device receives the DCI used to schedule the PDSCH, and the timer runs for a first duration.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, when the timer is running, the timer restarts at the moment after the terminal device receives the DCI used to schedule the PDSCH.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, sending N DCIs to the terminal device includes: sending the first DCI among the N DCIs to the terminal device when the timer is not running.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, obtaining a candidate value for the time interval between each DCI and the PDSCH scheduled by each DCI among the N DCIs is greater than a first value, including: sending multiple TDRA configuration information to the terminal device, the multiple TDRA configuration information including first TDRA configuration information, and all time intervals in the first TDRA configuration information being greater than the first value; wherein, the time interval between each DCI and the PDSCH scheduled by each DCI among the N DCIs is determined based on the first TDRA configuration information.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, after sending N downlink control information (DCI) messages to the terminal device, the method further includes: sending a second DCI message to the terminal device, wherein the candidate value of the time interval between the second DCI message and the PDSCH message scheduled by the second DCI message is determined based on the second TDRA configuration information among multiple TDRA configuration information messages.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending first TDRA configuration information to the terminal device; the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information and the minimum value of the time interval.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is the time interval that is greater than or equal to the minimum time interval among all time intervals corresponding to the first TDRA configuration information.

[0031] Thirdly, a communication device is provided, comprising at least one processor for executing a computer program or instructions, causing the device to perform a method as described in any of the possible implementations of the first or second aspect above. Optionally, the device further comprises a memory for storing the computer program or instructions; correspondingly, at least one processor is configured to execute the computer program or instructions in the memory. Optionally, the device further comprises a communication interface coupled to the processor, which can be used to input information to the processor or output information from the processor. Optionally, the processor reads the computer program or instructions from the memory via the communication interface.

[0032] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0033] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment).

[0034] Fourthly, a communication apparatus is provided for performing the method in any possible implementation of the first or second aspect described above. Specifically, the apparatus may include units and / or modules for performing the method in any possible implementation of the first or second aspect, such as processing units and / or communication units.

[0035] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0036] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0037] Fifthly, a processor is provided for executing the methods provided in any possible implementation of either the first or second aspect described above.

[0038] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0039] In a sixth aspect, a computer program product is provided that, when the computer program product is run on a communication device, causes the communication device to perform the method as described in any of the possible implementations of the first or second aspect above.

[0040] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a communication device, cause the communication device to perform the method as described in any possible implementation of the first or second aspect above.

[0041] Eighthly, a chip or chip system is provided, including at least one processor for calling and running a computer program from a memory, such that a communication device equipped with the chip system performs the method as described in any of the possible implementations of the first or second aspect above.

[0042] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the methods provided in any of the possible implementations of the first or second aspect described above. Attached Figure Description

[0043] Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application.

[0044] Figure 2 is a schematic diagram of a data receiving method provided in an embodiment of this application.

[0045] Figure 3 is a schematic diagram of a communication method provided in an embodiment of this application.

[0046] Figure 4 is a schematic diagram of another data receiving method provided in an embodiment of this application.

[0047] Figure 5 is a schematic diagram of a communication device provided in an embodiment of this application.

[0048] Figure 6 is a schematic diagram of another communication device provided in an embodiment of this application.

[0049] Figure 7 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0050] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0051] Before introducing the scheme of this application, the following points should be noted.

[0052] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing a certain instruction information as being used to instruct A, it can be understood that the instruction information carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of a certain instruction information can determine A based on the instruction information, it can be described as the instruction information being used to instruct A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" or "used to instruct" can be replaced with "includes". In this case, a statement similar to "sending / receiving instruction information, the instruction information being used to instruct A" can be replaced with "sending / receiving A".

[0053] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0054] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

[0055] (3) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0056] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0057] (5) In this application, “first”, “second”, and “#1”, “#2”, “#A” are merely for the convenience of description and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application.

[0058] (6) In this application, "predefined" can mean a standard protocol predefined, or it can mean a pre-agreed or pre-negotiated agreement between devices. Here, "protocol" can refer to a standard protocol in the field of communications, for example, it may include fourth-generation (4G) protocols. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols applied in future communication networks.

[0059] (7) In this application, the configuration can be signaling configuration, such as radio resource control (RRC) messages, control information (such as DCI), or medium access control (MAC) signaling (e.g., MAC control element (MAC CE / MAC-CE)). As an example, signaling configuration can be configured by signaling to the terminal device. For example, the network device configures resources (or the network device configures resources for the terminal device). This can be understood as the network device indicating the location of the resource to the terminal device through signaling.

[0060] (8) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0061] First, let me introduce the communication system to which this application applies.

[0062] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, frequency division duplex (FDD) systems, and time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication networks. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication.

[0063] As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. Satellite base stations can also communicate with each other. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment.

[0064] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0065] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses a device as an example for description.

[0066] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely used in various scenarios, such as: cellular communication, D2D, V2X, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The device may be a wireless communication unit (RSU), or a device built into the aforementioned device (e.g., a communication module, modem, or chip in the aforementioned device), or other processing devices connected to the wireless modem.

[0067] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X or D2D.

[0068] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0069] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, multiple standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0070] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0071] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes.

[0072] In some deployments, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0073] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN or ORAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0074] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0075] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0076] Referring to Figure 1, as an example, Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application. As shown in Figure 1, the wireless communication system includes a wireless access network 100. The wireless access network 100 may be a next-generation (e.g., future or higher version) wireless access network or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 120) may be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) in the wireless access network 100. Network elements in the wireless communication system are connected through interfaces (e.g., NG, Xn) or air interfaces.

[0077] When network devices and terminal devices communicate, the network device can manage one or more cells, and a cell can include at least one terminal device. A cell can be understood as an area within the wireless signal coverage range of the network device.

[0078] Figure 1 is just a schematic diagram. The wireless communication system may also include other devices, such as core network devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figure 1.

[0079] To facilitate a better understanding of the technical solutions of this application, some terms or concepts involved in the technical solutions of this application are introduced. The terms or concepts introduced below are merely illustrative examples for ease of understanding and do not limit the scope of protection of the embodiments of this application.

[0080] 1. Discontinuous Reception (DRX): Generally, packet-based data streams are bursty, with data transmission occurring for a period of time, followed by a period without data transmission. Therefore, NR can configure DRX processing procedures for terminal devices. When there is no data transmission, power consumption can be reduced by having the terminal device stop detecting the physical downlink control channel (PDCCH) and stop receiving corresponding data transmissions.

[0081] In DRX, network devices can configure a DRX cycle for terminal devices in an RRC-connected state. The DRX cycle includes a "duration" time period during which the terminal device can detect the PDCCH. If the terminal device detects the PDCCH during the "duration" time, it can start an inactive timer (drx-InactivityTimer) within the DRX mechanism. If the terminal device continues to detect the PDCCH during the drx-InactivityTimer's running time, it can restart (or reset) the drx-InactivityTimer and restart the timing. Furthermore, if the drx-InactivityTimer is running, the terminal device will continue to detect the PDCCH even after the "duration" time has ended, until the drx-InactivityTimer times out.

[0082] 2. Same-slot scheduling: Network devices transmit PDSCH and PDCCH to terminal devices. Since the DCI carried by the PDCCH includes relevant information needed to receive the PDSCH, such as the location and size of PDSCH time-frequency resources or multi-antenna configuration information, the terminal device needs to demodulate the PDCCH first to correctly receive the PDSCH. The PDCCH is transmitted in the CORESET.

[0083] For simultaneous slot scheduling, the scheduled PDSCH and the PDCCH that schedule it are located in the same slot. For example, in slot n, both the scheduled PDSCH and the PDCCH that schedule it are located in that slot.

[0084] 3. Cross-slot scheduling: For cross-slot scheduling, the PDSCH being scheduled is located in a different time slot than the PDCCH that is scheduling it. For example, if the subcarrier spacing of the PDCCH and PDSCH is the same, the PDCCH is in time slot n, while the PDSCH is in time slot n+1 or time slot n+2. This is cross-slot scheduling of the PDSCH.

[0085] 4. K0: This is the time slot offset (or time delay, time slot interval, etc.) between the PDCCH and the PDSCH scheduled by the PDCCH. It can also be described as the time slot offset between the DCI carried by the PDCCH and the PDSCH scheduled by the DCI. For example, when the subcarrier spacing of the PDSCH and PDCCH is the same, if the terminal device receives the DCI in time slot n, then the PDSCH scheduled by that DCI is in time slot n+K0. Therefore, when K0=0, the PDCCH and PDSCH are in the same time slot, or in other words, they are scheduled within the same time slot; when K0>0, the PDCCH and PDSCH are not in the same time slot, or in other words, they are scheduled across time slots.

[0086] 5. TDRA Configuration Information: This defines the time-domain resource allocation of the PDSCH or Physical Uplink Shared Channel (PUSCH). TDRA configuration information can be, for example, a TDRA table, configured by the network device to the terminal device via RRC signaling. Each entry in the TDRA table includes parameters such as K0, used to define different time-domain resource allocation schemes.

[0087] 6. Time Domain Resource Assignment (TDRA) Field: This field in the DCI indicates the time domain resource allocation of the PDSCH or PUSCH. The terminal device can determine the time domain resource allocation of the PDSCH or PUSCH scheduled by the DCI based on the TDRA field and TDRA configuration information. For example, after receiving the DCI, the terminal device decodes it to obtain the TDRA field value. Based on this TDRA field value, the terminal device can find the corresponding entry in the TDRA configuration information, thereby determining the time domain resource location of the PDSCH or PUSCH.

[0088] 7. Bandwidth Part (BWP): A portion of the system bandwidth. System bandwidth can refer to the bandwidth of a single carrier wave. System bandwidth can be very large, such as 100MHz or 200MHz. Some terminal devices cannot support such a large system bandwidth. Therefore, network devices can configure a portion of the system bandwidth for terminal devices (i.e., configure the BWP for the terminal device), such as 20MHz. The terminal device can then communicate with the network device on 20MHz.

[0089] The above content, in conjunction with Figure 1, illustrates the scenarios in which the communication method provided in the embodiments of this application can be applied, and also introduces the technical terms or basic concepts that may be involved in the embodiments of this application. The solution provided in the embodiments of this application will now be described in conjunction with the accompanying drawings.

[0090] The power consumption of a terminal device is related to the operating modules that are enabled. For example, when a terminal device operates with more receiving antennas (hereinafter referred to as Rx) or a larger bandwidth, the power consumption is correspondingly higher; when a terminal device operates with fewer Rx or a smaller bandwidth, the power consumption is correspondingly lower. However, when a terminal device communicates in a high-power operating mode for a long time, the terminal device may experience problems such as increased heat, reduced battery life, and decreased performance, thus reducing the user experience.

[0091] Understandably, to reduce the power consumption of terminal devices, they can communicate in a lower-power mode when there is no data transmission, and in a higher-power mode when there is data transmission. Taking downlink data transmission as an example, when there is no data transmission, the terminal device can receive signals with two receiving antennas (2Rx) and a 20MHz bandwidth to reduce power consumption; when there is data transmission, the terminal device can receive signals with four receiving antennas (4Rx) and a 100MHz bandwidth to ensure reliable data reception.

[0092] Figure 2 is a schematic diagram of some data receiving methods of terminal devices provided in the embodiments of this application.

[0093] One possible implementation, as shown in Figure 2(a), involves network devices scheduling data transmission using a simultaneous slot scheduling method. Terminal devices communicate with fewer receiving antennas and a smaller bandwidth (e.g., 2Rx, CORESET bandwidth of 20MHz) when there is no data transmission, and with more receiving antennas and a larger bandwidth (e.g., 4Rx, 100MHz) when there is data transmission. However, because data arrival is often uncertain and sudden, terminal devices cannot predict when data will arrive. Therefore, when data arrives, the first or even the first few PDSCHs may not be received correctly. For example, if the bandwidth of the first or even the first few PDSCHs exceeds the CORESET bandwidth, the terminal device will be unable to buffer the data properly, resulting in the loss of some data carried in the PDSCH.

[0094] Another possible implementation, as shown in Figure 2(b), involves network devices scheduling data transmission using a simultaneous slot scheduling method, and terminal devices communicating with multiple receiving antennas and a larger bandwidth (e.g., 4Rx, 100MHz) to avoid PDSCH data loss. This implementation ensures the reliability of downlink data reception, but it is obvious that the power consumption of the terminal devices is difficult to reduce.

[0095] Another possible implementation is that the terminal device can switch the number of receiving antennas and / or operating bandwidth according to the instructions or configuration of the network device. For example, in the 3GPP standard NR Release 15 (R15), NR introduced the BWP mechanism. The network device can configure different bandwidth BWPs for the terminal device and switch the operating bandwidth by instructing the terminal device to switch BWPs. For instance, when the terminal device is not transmitting data, the network device instructs the terminal device to switch to a narrower BWP (such as a 20MHz bandwidth BWP) to reduce power consumption; when the terminal device is transmitting data, the network device instructs the terminal device to switch to a wider BWP (such as a 100MHz bandwidth BWP) to ensure reliable data reception.

[0096] Furthermore, in Release 16 (R16), NR introduced a maximum MIMO layer per BWP mechanism. Network devices can configure different maximum MIMO layers for terminal devices by instructing them to switch BWPs. The number of MIMO layers for a terminal device is related to the number of receive antennas; each MIMO layer's data stream requires a corresponding receive antenna for reception and demodulation. This means that network devices can indirectly control the number of Rx antennas currently used by a terminal device by configuring different maximum MIMO layers. For example, when the terminal device is not transmitting data, the network device can instruct it to switch to a BWP with a lower maximum MIMO layer count, allowing the terminal device to use fewer receive antennas (e.g., 2 Rx) to receive signals and reduce power consumption. Conversely, when the terminal device is transmitting data, the network device can instruct it to switch to a BWP with a higher maximum MIMO layer count, allowing the terminal device to use more receive antennas (e.g., 4 Rx) to ensure reliable data reception.

[0097] However, in current NR protocols, different RRC parameters are typically configured for each BWP. This means that each time a terminal device performs a BWP handover, it needs to reread the relevant configuration from memory, resulting in relatively large latency (e.g., several milliseconds) during BWP handover. Therefore, to minimize these latency issues and ensure a good user experience, network devices typically employ conservative BWP scheduling algorithms. For example, network devices usually only instruct the terminal device to switch to a BWP with narrower bandwidth and / or a lower maximum MIMO layer count when the terminal device's data transmission volume is very small. This instructs the terminal device to use a lower-power operating mode, which often makes it difficult to reduce the terminal device's power consumption in practical applications. Furthermore, the DCI-based BWP handover process for terminal devices may encounter false alarms. For instance, in situations with strong channel interference or weak signals, the terminal device may misdecode the BWP indication field in the DCI, leading to an incorrect BWP handover. Therefore, due to the impact of false alarms, network devices are less motivated to configure lower-power BWPs for terminal devices, which also makes it difficult to reduce the terminal device's power consumption.

[0098] In summary, the aforementioned method of reducing power consumption by instructing the terminal device to switch BWPs typically fails to achieve satisfactory energy-saving effects in practical applications. Furthermore, the implementation shown in Figure 2(a) may result in the loss of some PDSCH data. Therefore, effectively reducing the power consumption of the terminal device without affecting reliable data transmission has become an urgent problem to be solved.

[0099] To address the aforementioned issues, this application provides a communication method that enables terminal devices to communicate in a low-power operating mode when no data transmission occurs while operating on the same BWP, thereby effectively improving the energy efficiency of the terminal devices. Furthermore, this method can prevent the terminal devices from losing data when the next round of data transmission arrives.

[0100] It should be understood that, in order to support a large amount of data transmission, the bandwidth of the BWP configured on the terminal device is usually greater than that of the CORESET. In this way, the terminal device can receive PDSCH with a bandwidth greater than that of the CORESET on the BWP.

[0101] Figure 3 is a schematic flowchart of the communication method 300 provided in an embodiment of this application.

[0102] S301, the terminal device receives N DCIs from the network device, and correspondingly, the network device sends N DCIs to the terminal device.

[0103] The N DCIs are carried on N PDCCHs, with each DCI used for scheduling PDSCHs. Specifically, the N DCIs are the first N DCIs received by the terminal device after receiving the first DCI.

[0104] Here, N DCIs can be understood as the first N DCIs received by the terminal device after a period of no data transmission following the previous data transmission period. Alternatively, N DCIs can be described as the first N DCIs received by the terminal device within a single data transmission period. In this case, the first DCI can be understood as the last DCI received by the terminal device in the previous data transmission period.

[0105] Furthermore, the time interval between the reception time of any one of the aforementioned N DCIs and the reception time of the first DCI is greater than or equal to the first duration, where N is a positive integer. Alternatively, it can be said that the period of no data transmission experienced by the terminal device is greater than or equal to the first duration. In this case, the N DCIs can also be understood as the first N DCIs received by the terminal device after the previous data transmission period and the first duration.

[0106] The reception time of DCI (including the first DCI) refers to the moment when the terminal device receives the DCI, such as the last symbol of the PDCCH where the DCI is located; the time interval can be the interval of time units, and the time unit can be a time slot or a symbol; the value of N can be 1, 2, 3, etc. The value of N can be determined based on the actual communication scenario, combined with the terminal device's capabilities (the ability to adjust the number of Rx currently used and the working bandwidth, etc.) and latency requirements, etc. This application does not limit this.

[0107] Furthermore, the terminal device can use a timer to determine whether it has entered a period without data transmission. In other words, the terminal device can use a timer to determine whether the received DCI is "N DCIs". For example, the timer's runtime can be a first duration. After the terminal device receives the DCI used for scheduling PDSCH, or more specifically, after the terminal device receives the DCI used for scheduling new transmission PDSCH (e.g., the first symbol after receiving this DCI), the timer is started or restarted. After the timer expires, it stops running, indicating that the terminal device has entered a period without data transmission (or the previous data transmission period has ended). When the terminal device receives another DCI, it is considered that the terminal device has entered a new data transmission period. In this data transmission period, the first N DCIs received by the terminal device are the "N DCIs" in S301. Here, new transmission PDSCH refers to the PDSCH initially sent by the network device to the terminal device, a concept relative to retransmitted PDSCH.

[0108] One possible implementation is that the network device can align with the terminal device using a timer. For example, the terminal device maintains a first timer, and the network device maintains a second timer. The second timer's runtime, start or restart time, and other related timer information are the same as the first timer.

[0109] Based on the above implementation, network devices can align the data transmission status of terminal devices through timers, resulting in higher system synchronization. This allows network devices to perform other operations based on the data transmission status of terminal devices, such as sending instruction or configuration information to terminal devices, leading to more precise resource allocation.

[0110] It should be understood that regardless of whether the timer is running or not, after the terminal device receives the DCI used to schedule the new PDSCH transmission, it performs an operation on the timer to restart the timer (or in other words, start the timer from the initial value). Therefore, this operation can be uniformly described as "starting or restarting the timer" or "restarting the timer".

[0111] Furthermore, the operations performed on the timer can be refined based on the timer's state. For example, after receiving the DCI for scheduling the PDSCH (or more specifically, after receiving the DCI for scheduling the newly transmitted PDSCH), the terminal device performs the following operations:

[0112] Start the timer if it is not running.

[0113] Restart the timer while it is running.

[0114] Understandably, the timer will stop counting after its runtime expires; in other words, the timer will enter a non-running state after it times out. Therefore, when the terminal device receives the first DCI out of N DCIs, the timer will be in a non-running state. Alternatively, the terminal device receives the first DCI out of N DCIs from the network device while the timer is not running, and correspondingly, the network device sends the first DCI out of N DCIs to the terminal device while the timer is not running.

[0115] It is also understandable that timer-related information, such as the timer's runtime (the value of the first duration), start conditions, or restart conditions, can be configured by the network device for the terminal device, or it can be predefined by the protocol; this application does not limit this. Furthermore, the timer can reuse the drx-InactivityTimer mentioned above to simplify system design and reduce resource consumption (such as the terminal device's memory usage and central processing unit (CPU) overhead). A description of drx-InactivityTimer can be found in the conceptual introduction section above, and will not be repeated here.

[0116] Furthermore, the terminal device can switch to a lower power consumption operating mode after each data transmission period ends to improve energy efficiency.

[0117] One possible implementation is that the terminal device can automatically switch to a lower power consumption mode after the timer expires. For example, during a data transmission period (or while the timer is running), the terminal device receives downlink data in a higher power consumption mode (e.g., 4Rx, 100MHz bandwidth). After the terminal device receives the last DCI in this data transmission period, the timer restarts, begins counting until it times out and stops. Then, when the terminal device enters a period without data transmission (or, after the timer stops counting, or while the timer is not running), the terminal device can automatically switch to a lower power consumption mode (e.g., 2Rx, CORESET bandwidth such as 20MHz) to receive signals.

[0118] Based on the above implementation, the terminal device can learn about the data transmission status according to the timer's state and adjust its own operating bandwidth and / or the number of Rx currently used. Therefore, the terminal device can communicate in a lower power consumption mode during periods without data transmission, improving its energy efficiency. Furthermore, this method does not rely on network device instructions, reducing signaling overhead and resource consumption.

[0119] Another possible implementation is that the terminal device can switch to a lower power consumption operating mode based on an instruction from the network device. For example, after the terminal device enters a period without data transmission, the network device can send an instruction message to the terminal device (e.g., the network device sends the instruction message to the terminal device in the form of DCI, MAC CE, or RRC signaling) to instruct the terminal device to switch to a lower power consumption operating mode (e.g., a bandwidth of 20MHz for 2Rx or CORESET) to receive signals.

[0120] Based on the above implementation method, the terminal device can adjust its own working bandwidth and / or the number of Rx currently in use according to the explicit instructions of the network device, which can also improve the energy saving effect of the terminal device. Moreover, this method is simple and easy to implement.

[0121] Furthermore, the candidate value for the time interval between each of the N DCIs and the PDSCH scheduled for that DCI is greater than the first value. The time interval between each DCI and its scheduled PDSCH can be, for example, K0 as mentioned above, meaning the time interval is the slot offset between the DCI and the PDSCH. The first value can be 0, 1, etc. For example, when the first value is 0, K0 > 0 for the N DCIs; in other words, the scheduling method for these N DCIs is cross-slot scheduling.

[0122] However, during the downlink data reception process, the terminal device typically cannot know whether data will arrive in the current time slot during the period of receiving and decoding the PDCCH (i.e., before decoding the DCI). Therefore, even if K0>0, the terminal device will still buffer most or even all of the downlink signals in the current time slot to prepare for receiving data in the current time slot as much as possible, which will also lead to a higher power consumption of the terminal device.

[0123] To avoid the aforementioned problems, in the communication method provided in this application embodiment, the candidate value of the time interval can be at least one possible value of K0 known to the terminal device. This candidate value can be predefined by the protocol or configured on the terminal device by the network device. Based on this, the terminal device can obtain advance knowledge of the data scheduling situation in this time slot.

[0124] For example, when the first value is 0, all candidate values ​​of K0 corresponding to each of the N DCIs are greater than 0. In other words, the terminal device can know in advance that K0 of the N DCIs will necessarily be greater than 0, regardless of its specific value. For example, Figure 4 shows a data scheduling example when N is 1 and K0 is 1. In the case shown in Figure 4, the terminal device can only cache the downlink signals of the first few symbols of each of the N time slots containing the N DCIs (such as the downlink signals within the CORESET duration range corresponding to the first N DCIs) and not cache the downlink signals of the subsequent symbols of each of the N time slots, so as to further improve the energy saving effect.

[0125] Furthermore, since the N DCIs employ a cross-timeslot scheduling method, the terminal device has ample time to adjust its operating bandwidth and the number of Rx currently in use. For example, when the timer is not running, the terminal device can receive signals in a low-power operating mode (e.g., 2Rx, CORESET bandwidth such as 20MHz); then, the terminal device receives N DCIs, and the terminal device knows that the scheduling method of these N DCIs is cross-timeslot scheduling; then, the terminal device can adjust to a higher-power operating mode (e.g., 4Rx, 100MHz) to receive signals, thereby avoiding the loss of PDSCH data scheduled by these N DCIs.

[0126] Therefore, in order to ensure that the candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is greater than the first value, the embodiments of this application mainly involve the following schemes: Scheme A and Scheme B.

[0127] In Scheme A, the network device can configure multiple TDRA configuration information for the terminal device. Therefore, within a data transmission period, the candidate time interval values ​​corresponding to the first N DCIs and other DCIs can be determined based on different TDRA configuration information. Scheme A includes S302 and S303:

[0128] S302, the terminal device receives multiple TDRA configuration information from the network device, and correspondingly, the network device sends multiple TDRA configuration information to the terminal device.

[0129] Specifically, the multiple TDRA configuration information includes first TDRA configuration information and second TDRA configuration information. All time intervals corresponding to the first TDRA configuration information are greater than a first value; the time interval values ​​in the second TDRA configuration information are not limited in this application.

[0130] The first TDRA configuration information could be, for example, a first TDRA table; the time interval could be, for example, K0. As one possible implementation, when the first value is 0, all K0 values ​​included in the first TDRA table are greater than 0. This means that any DCI that determines K0 based on the first TDRA table uses cross-timeslot scheduling.

[0131] The second TDRA configuration information could be, for example, a second TDRA table. As another possible implementation, all K0 values ​​in the second TDRA table are greater than or equal to 0. This means that the DCI for determining K0 based on the second TDRA table can be scheduled simultaneously or across time slots.

[0132] It should be understood that TDRA configuration information can also be any other form that enables the terminal device to obtain relevant time-domain resource information of PDSCH. For example, in current communication systems, TDRA configuration information can be a TDRA table; in future communication systems, TDRA configuration information may also be in other formats, which this application does not limit.

[0133] S303, the terminal device determines a candidate time interval value for each of the N DCIs based on the first TDRA configuration information. Specifically, the candidate time interval value is the candidate time interval between each of the N DCIs and the PDSCH scheduled for that DCI. In other words, the candidate time interval between each of the N DCIs and the PDSCH scheduled for that DCI is determined based on the first TDRA configuration information.

[0134] Based on the above scheme, the terminal device can know in advance that the scheduling method used for the first N DCIs in a data transmission period (e.g., the period when the terminal device receives data again after the timer has stopped or when the timer is not running) is cross-time slot scheduling. Then, the terminal device can receive and decode the PDCCH used to carry each of the N DCIs in a low-power operating mode. For example, after receiving each of the N DCIs, the terminal device can look up the first TDRA configuration information based on the TDRA field in the DCI and determine the specific time domain resource allocation result (the value of K0) for that DCI. In this way, the power consumption of the terminal device can be further reduced. Furthermore, the terminal device can adjust the currently used Rx quantity and / or operating bandwidth before the PDSCH arrives to avoid downlink data loss.

[0135] Furthermore, during a data transmission period, after receiving N DCIs from the network device, the terminal device can also receive other DCIs. Therefore, Scheme A also includes S304 and S305:

[0136] S304, the terminal device receives the second DCI from the network device, and accordingly, the network device sends the second DCI to the terminal device.

[0137] S305, the terminal device determines a candidate time interval value corresponding to the second DCI based on the second TDRA configuration information. Specifically, this candidate time interval value is a candidate time interval between the second DCI and the PDSCH scheduled by the second DCI. In other words, the candidate time interval between the second DCI and the PDSCH scheduled by the second DCI is determined based on the second TDRA configuration information.

[0138] With the above implementation, the terminal device can receive other PDSCHs in the data transmission period in the same time slot scheduling manner after receiving the first N DCI-scheduled PDSCHs, which helps to reduce the communication latency of the terminal device.

[0139] In the above scheme A, the terminal device determines the time interval between N DCIs and other DCIs based on different TDRA configuration information. In this way, by setting different TDRA configuration information (for example, making all time intervals corresponding to the TDRA configuration information greater than the first value), the terminal device can know in advance that the N DCIs will adopt cross-time slot scheduling, while other DCIs are not restricted.

[0140] In Scheme B, the candidate time interval value corresponding to a DCI within a data transmission period can be determined using the same TDRA configuration information. However, the effective range of this TDRA configuration information can differ when receiving the first N DCIs and other DCIs. For example, the candidate time interval value corresponding to the first N DCIs can be determined based on a subset of entries in the TDRA configuration information. Scheme B includes S306 to S308:

[0141] S306, the terminal device receives the first TDRA configuration information from the network device, and accordingly, the network device sends the first TDRA configuration information to the terminal device.

[0142] S307, the terminal device determines the minimum time interval. This minimum time interval can be configured or indicated to the terminal device by the network device. Therefore, S307 can also be understood as the terminal device receiving the minimum time interval from the network device, and correspondingly, the network device sending the minimum time interval to the terminal device.

[0143] The minimum time interval can be understood as the smallest valid (or usable) time interval among all time intervals corresponding to the first TDRA configuration information. For example, the valid range of the first TDRA table differs depending on the value of the minimum time interval (K0min). For instance, when K0min is 1, entries in the first TDRA table where K0 is greater than or equal to K0min can be indexed by the terminal device. In other words, the current valid range of the first TDRA table is the entries where K0 is greater than or equal to K0min.

[0144] S308, the terminal device determines a candidate time interval value for each of the N DCIs based on the first TDRA configuration information and the minimum time interval value. Specifically, the candidate time interval value is the candidate time interval between each of the N DCIs and the PDSCH scheduled for that DCI. In other words, the candidate time interval between each of the N DCIs and the PDSCH scheduled for that DCI is determined based on the first TDRA configuration information and the minimum time interval value.

[0145] Based on the above scheme, and using the minimum time interval at the current moment (i.e., when receiving the current DCI), the terminal device can determine the specific K0 value within the current valid range of the first TDRA configuration information. Therefore, the terminal device can use the same TDRA configuration information to more effectively configure the time-domain resources corresponding to N DCIs and other DCIs, reducing memory usage and resource overhead, and further improving energy efficiency.

[0146] One possible implementation is that the candidate time interval between each of the N DCIs and the PDSCH scheduled by that DCI is the time interval greater than or equal to the minimum time interval among all time intervals corresponding to the first TDRA configuration information.

[0147] When the terminal device receives N DCIs, the effective range of the first TDRA configuration information will be the entries whose time interval is greater than or equal to the minimum value of the time interval, and if the minimum value of the time interval is greater than the first value, the time interval corresponding to these effective entries will be greater than the first value.

[0148] For example, when receiving each of the N DCIs, the minimum time interval K0min can be set to 1. Then, the terminal device will be able to know in advance that the candidate values ​​of K0 for the N DCIs are greater than or equal to 1. In other words, the terminal device can know in advance that the scheduling method for the N DCIs is cross-time slot scheduling. Therefore, for similar reasons to Scheme A above, the terminal device can further reduce power consumption and avoid losing downlink data.

[0149] Another possible implementation is that, when the terminal device receives other DCIs, the effective range of the first TDRA configuration information can be all of its entries, or in other words, the candidate values ​​for the time intervals corresponding to other DCIs can be determined based on all the entries of the first TDRA configuration information.

[0150] For example, when receiving other DCIs, the minimum time interval can be automatically set to 0 by the terminal device, or the minimum time interval can be automatically invalidated. Then, the scheduling method for other DCIs can be simultaneous slot scheduling, which can reduce the communication latency of the terminal device.

[0151] The foregoing section, in conjunction with Figure 3, has described in detail the method provided by the embodiments of this application. The apparatus provided by the embodiments of this application will now be described in detail with reference to Figures 5 to 7. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the above method embodiments, and for the sake of brevity, will not be repeated here.

[0152] Figure 5 is a schematic diagram of a communication device 500 provided in an embodiment of this application. The device 500 includes a transceiver unit 510 and a processing unit 520. The transceiver unit 510 can be used to implement corresponding communication functions. The transceiver unit 510 can also be referred to as a communication interface or communication unit. The processing unit 520 can be used to perform processing, such as determining the time interval between each of the N DCIs and the PDSCH scheduled by that DCI.

[0153] Optionally, the device 500 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 520 can read the instructions and / or data in the storage unit so that the device 500 can implement the aforementioned method embodiments.

[0154] In a first possible design, the device 500 can be the terminal device in the foregoing embodiments, and the device 500 can implement the steps or processes corresponding to those executed by the terminal device in the above method embodiments. Specifically, the transceiver unit 510 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the terminal device in the above method embodiments, and the processing unit 520 can be used to perform processing-related operations of the terminal device in the above method embodiments, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0155] One possible implementation is that the transceiver unit 510 is used to receive N downlink control information (DCI) from the network device, where the N DCI are the first N DCIs received after receiving the first DCI, and the time interval between the reception time of any one of the N DCIs and the reception time of the first DCI is greater than or equal to a first duration, where N is a positive integer; and the processing unit 520 is used to determine the time interval between each of the N DCIs and the PDSCH scheduled for each DCI, where the candidate value of the time interval is greater than a first value.

[0156] Optionally, the processing unit 520 is further configured to start a timer after receiving the DCI for scheduling PDSCH and when the timer is not running, wherein the timer's running duration is a first duration.

[0157] Optionally, the processing unit 520 is also configured to restart the timer after receiving the DCI for scheduling PDSCH and while the timer is running.

[0158] Optionally, the transceiver unit 510 is also configured to receive multiple TDRA configuration information, which are used by the terminal device to determine the time interval between the received DCI and the PDSCH scheduled by the DCI.

[0159] Optionally, the transceiver unit 510 is further configured to receive first TDRA configuration information and minimum time interval, wherein the first TDRA configuration information and minimum time interval are used to determine the time interval between the received DCI and the PDSCH scheduled by the DCI.

[0160] In a second possible design, the device 500 can be a network device as described in the foregoing embodiments. This device 500 can implement the steps or processes performed by the network device corresponding to those described in the method embodiments above. Specifically, the transceiver unit 510 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the network device described in the method embodiments above, and the processing unit 520 can be used to perform processing-related operations of the network device described in the method embodiments above, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0161] One possible implementation is that the transceiver unit 510 is used to send N DCIs to the terminal device. The N DCIs are the first N DCIs received after receiving the first DCI. The time interval between the reception time of any one of the N DCIs and the reception time of the first DCI is greater than or equal to a first duration, and N is a positive integer. Among them, the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled for each DCI is greater than the first value.

[0162] Optionally, the transceiver unit 510 is further configured to send multiple TDRA configuration information to the terminal device, wherein the multiple TDRA configuration information is used by the terminal device to determine the time interval between the received DCI and the PDSCH scheduled by the DCI.

[0163] Optionally, the transceiver unit 510 is further configured to send first TDRA configuration information and minimum time interval to the terminal device. The first TDRA configuration information and minimum time interval are used to determine the time interval between the received DCI and the PDSCH scheduled by the DCI.

[0164] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0165] It should also be understood that the device 500 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 500 can specifically be the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to device 500 in the above method embodiments; to avoid repetition, these will not be described again here.

[0166] The apparatus 500 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as a terminal device or a network device) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by a processor, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0167] In addition, the transceiver unit 510 can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit 520 can be a processing circuit.

[0168] It should be noted that the device 500 in Figure 5 can be the communication device (such as a terminal device or a network device) in the aforementioned embodiments, or it can be a chip or a chip system, such as a SoC. The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0169] Figure 6 is a schematic diagram of another communication device 600 provided in an embodiment of this application. The device 600 includes a processor 610, which is coupled to a memory 620. The memory 620 is used to store computer programs or instructions and / or data. The processor 610 is used to execute the computer programs or instructions stored in the memory 620, or to read the data stored in the memory 620, in order to execute the methods in the above method embodiments.

[0170] Optionally, there may be one or more processors 610.

[0171] Optionally, the memory 620 may be one or more.

[0172] Alternatively, the memory 620 can be integrated with the processor 610, or it can be set separately.

[0173] Optionally, as shown in FIG6, the device 600 further includes a transceiver 630 for receiving and / or transmitting signals. For example, the processor 610 is used to control the transceiver 630 to receive and / or transmit signals.

[0174] As an example, processor 610 may have the functions of processing unit 520 shown in FIG5, memory 620 may have the functions of storage unit, and transceiver 630 may have the functions of transceiver unit 510 shown in FIG5.

[0175] As one approach, the device 600 is used to implement the operations performed by a communication device (such as a terminal device or a network device) in the various method embodiments described above.

[0176] For example, processor 610 is used to execute computer programs or instructions stored in memory 620 to implement the relevant operations of the communication device in the various method embodiments described above.

[0177] It should be understood that the processor mentioned in the embodiments of this application can be a CPU, or other general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0178] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0179] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0180] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0181] Referring to Figure 7, as an example, Figure 7 is a schematic diagram of a chip system 700 provided in an embodiment of this application. The chip system 700 (or may also be referred to as a processing system) includes logic circuitry 710 and an input / output interface 720.

[0182] The logic circuit 710 can be a processing circuit in the chip system 700. The logic circuit 710 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 700 to implement the methods and functions of the embodiments of this application. The input / output interface 720 can be an input / output circuit in the chip system 700, outputting processed information or inputting data or signaling information to be processed into the chip system 700 for processing.

[0183] As one approach, the chip system 700 is used to implement the operations performed by the communication device (such as a terminal device or a network device) in the various method embodiments described above.

[0184] For example, logic circuit 710 is used to implement processing-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments; input / output interface 720 is used to implement sending and / or receiving-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments.

[0185] This application also provides a computer-readable storage medium storing a computer program or instructions for implementing the methods executed by a communication device (such as a terminal device or a network device) in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, they cause the communication device (such as a terminal device or a network device) to execute the above-described methods (such as method 300).

[0186] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods described above as performed by a communication device (such as a terminal device or a network device). For example, when the computer program or instructions are run on the communication device, the communication device (such as a terminal device or a network device) performs the methods described above (such as method 300).

[0187] This application also provides a communication system that includes the terminal device and / or network device described in the above embodiments. For example, the system includes the terminal device and network device shown in the embodiment of FIG3.

[0188] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0189] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0190] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0191] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0192] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0193] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive N downlink control information (DCI) messages from the network device. The N DCI messages are the first N DCI messages received after the first DCI message is received. The time interval between the reception time of any one of the N DCI messages and the reception time of the first DCI message is greater than or equal to a first duration. N is a positive integer. Among them, the candidate value of the time interval between each of the N DCIs and the Physical Downlink Shared Channel (PDSCH) scheduled by each DCI is greater than the first value.

2. The method according to claim 1, characterized in that, The method further includes: After receiving the DCI for scheduling PDSCH and if the timer is not running, the timer is started, and the timer's runtime is the first duration.

3. The method according to claim 2, characterized in that, The method further includes: After receiving the DCI for scheduling PDSCH and while the timer is running, the timer is restarted.

4. The method according to claim 2 or 3, characterized in that, The receipt of N DCIs from the network device includes: If the timer is not running, the first of the N DCIs is received from the network device.

5. The method according to any one of claims 1 to 4, characterized in that, Candidate values ​​for the time interval between each of the N DCIs and the PDSCH scheduled for each DCI are greater than a first value, including: Receive multiple Time Domain Resource Allocation (TDRA) configuration information from the network device, wherein the multiple TDRA configuration information includes first TDRA configuration information, and all time intervals corresponding to the first TDRA configuration information are greater than the first value; The candidate value of the time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information.

6. The method according to claim 5, characterized in that, After receiving N DCIs from the network device, the method further includes: The second DCI is received from the network device, and the candidate value of the time interval between the second DCI and the PDSCH scheduled by the second DCI is determined based on the second TDRA configuration information in the plurality of TDRA configuration information.

7. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive first TDRA configuration information from the network device; Determine the minimum time interval; The candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information and the minimum time interval.

8. The method of claim 7, wherein, The candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is a time interval that is greater than or equal to the minimum time interval among all time intervals corresponding to the first TDRA configuration information.

9. A communication method characterized by comprising: include: N downlink control information (DCI) messages are sent to the terminal device. The N DCI messages are the first N DCI messages received after the first DCI message is received. The time interval between the reception time of any one of the N DCI messages and the reception time of the first DCI message is greater than or equal to a first duration. N is a positive integer. Among them, the candidate value of the time interval between each of the N DCIs and the PDSCH scheduled by each DCI is greater than the first value.

10. The method according to claim 9, characterized in that, When the timer is not running, the timer starts at the moment after the terminal device receives the DCI for scheduling PDSCH, and the timer runs for the first duration.

11. The method according to claim 10, characterized in that, When the timer is running, the timer restarts at the moment after the terminal device receives the DCI for scheduling PDSCH.

12. The method according to claim 10 or 11, characterized in that, Sending N DCIs to the terminal device includes: If the timer is not running, send the first of the N DCIs to the terminal device.

13. The method according to any one of claims 9 to 12, characterized in that, Among the N DCIs, the candidate values ​​for the time interval between each DCI and the PDSCH scheduled by each DCI that are greater than the first value include: Send multiple Time Domain Resource Allocation (TDRA) configuration information to the terminal device. The multiple TDRA configuration information includes first TDRA configuration information, and all time intervals in the first TDRA configuration information are greater than the first value. The time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information.

14. The method according to claim 13, characterized in that, After sending N downlink control information (DCI) messages to the terminal device, the method further includes: A second DCI is sent to the terminal device. The candidate value of the time interval between the second DCI and the PDSCH scheduled by the second DCI is determined based on the second TDRA configuration information among the plurality of TDRA configuration information.

15. The method according to any one of claims 9 to 12, characterized in that, The method further includes: Send the first TDRA configuration information to the terminal device; The candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is determined based on the first TDRA configuration information and the minimum time interval.

16. The method according to claim 15, characterized in that, The candidate time interval between each of the N DCIs and the PDSCH scheduled by each DCI is a time interval that is greater than or equal to the minimum time interval among all time intervals corresponding to the first TDRA configuration information.

17. A communication device, characterized in that, It includes at least one processor for executing computer programs or instructions to cause the apparatus to perform the method as described in any one of claims 1 to 16.

18. A computer program product, characterized in that, When the computer program product is run on a communication device, it causes the communication device to perform the method as described in any one of claims 1 to 16.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 16.