Communication method and device

Abstract

A communication method and a device, applied to the technical field of communications. In the method, a dynamic activation period associated with a sending time of uplink data or an arrival time of uplink data is introduced; and a terminal device determines a first time point associated with the sending time of the uplink data or the arrival time of the uplink data and used for indicating the starting point of the dynamic activation period, and detects, starting from the first time point, a PDCCH used for scheduling data transmission. The method enables the terminal device to promptly detect the PDCCH starting from the starting point of the dynamic activation period associated with the sending time of the uplink data or the arrival time of the uplink data, thereby reducing downlink service latency.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202411517028.2, filed on October 28, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] Artificial intelligence generated content (AIGC) intelligent dialogue is an emerging question-and-answer service based on large language models. In AIGC intelligent dialogue services, the downlink data sent from the network to the terminal includes the downlink initial packet and downlink non-initial packets. The downlink initial packet is constrained by end-to-end latency requirements and the inference time of large models, and is typically tens of milliseconds (ms).

[0004] When the network needs to send its first downlink packet to the terminal, the terminal may be in a discontinuous reception (DRX) sleep period. In this case, the network needs to wait until the terminal is in the DRX active period before it can send the first downlink packet. If the DRX period is long, such as hundreds of milliseconds, the network may have to wait for hundreds of milliseconds to send the first downlink packet to the terminal, which cannot meet the latency requirements for the first downlink packet. Summary of the Invention

[0005] This application provides a communication method and apparatus that enables a terminal device to detect the PDCCH used for scheduling data transmission in a timely manner, thereby reducing the latency of downlink services.

[0006] In a first aspect, embodiments of this application provide a communication method executed by a terminal device. The terminal device may be a terminal, a component of a terminal (e.g., a processor, chip, or chip system), or a logic module capable of implementing all or part of the terminal's functions. Specifically, the terminal device determines a first time point, which is associated with the transmission time or arrival time of uplink data. Starting from the first time point, the terminal device detects the Physical Downlink Control Channel (PDCCH), which is used to schedule data transmission.

[0007] As can be seen, using the above method, the terminal device detects the PDCCH used for scheduling data transmission starting from a time point associated with the transmission or arrival time of uplink data. The terminal device can detect the PDCCH in a timely manner, reducing downlink service latency.

[0008] In one optional implementation, the terminal device may further determine a second time point, which is later than the first time point. In this method, the terminal device detects the PDCCH starting from the first time point, including: detecting the PDCCH between the first time point and the second time point.

[0009] As can be seen, in this embodiment, the terminal device detects the PDCCH from a first time point associated with the transmission or arrival time of the uplink data to a second time point, so that the terminal device can detect the PDCCH in a timely manner and save power consumption.

[0010] In one optional implementation, the terminal device determines a first time point by: receiving first indication information from a network device, the first indication information indicating a first time point; and determining the first time point based on the first indication information.

[0011] As can be seen, in this embodiment, the terminal device determines the first time point based on the instructions of the network device, which can reduce the complexity of the terminal device's processing.

[0012] In one possible approach, the first indication information includes a first time point to directly indicate the first time point. In another possible approach, the first indication information includes the transmission time of the uplink data and the duration between the first time point and the transmission time of the uplink data to indirectly indicate the first time point. Therefore, the first indication information can flexibly indicate the first time point through either direct or indirect indication.

[0013] In one optional implementation, the first indication information is further used to indicate a second time point. In this method, the terminal device determines the second time point by: determining the second time point based on the first indication information.

[0014] As can be seen, in this embodiment, the terminal device can also determine a second time point based on the instructions of the network device, which can reduce the complexity of the terminal device's processing.

[0015] In one possible approach, the first indication information also includes a second time point to directly indicate the second time point. In another possible approach, the first indication information also includes the duration between the second time point and the first time point to indirectly indicate the second time point. Therefore, the first indication information can flexibly indicate the second time point through either direct or indirect indication.

[0016] In another optional implementation, the terminal device determines the first time point by: determining the earliest time point at which downlink data associated with uplink data, estimated based on the transmission time of uplink data, arrives at the network device.

[0017] As can be seen, in this embodiment, the terminal device can estimate the earliest time when the downlink data associated with the uplink data arrives at the network device from the server, based on the uplink data transmission time. The earliest time estimated by the terminal device may be the time when the network device begins sending the PDCCH used to schedule downlink data. Therefore, the terminal device determines the estimated earliest time as the starting point for PDCCH detection, thereby enabling timely PDCCH detection and reducing downlink service latency.

[0018] In one optional implementation, the terminal device determines the second time point by: determining the latest time point at which downlink data associated with uplink data, estimated based on the uplink data transmission time, arrives at the network device.

[0019] As can be seen, in this embodiment, the terminal device can estimate the latest time that the downlink data associated with the uplink data will arrive at the network device from the server based on the uplink data transmission time. The latest time estimated by the terminal device may be the end point of the PDCCH sent by the network device for scheduling downlink data. Therefore, the terminal device determines the estimated latest time point as the end point of detecting the PDCCH to reduce the power consumption of the terminal device.

[0020] In one optional implementation, the terminal device may also send second indication information to the network device, for example, if it has determined a first time point itself, it may send the second indication information to the network device. The second indication information may be used to indicate the first time point, or it may be used to indicate both the first and a second time point.

[0021] As can be seen, in this embodiment, the terminal device can indicate the start point of PDCCH detection determined by the terminal device itself to the network device, or indicate the start and end points of PDCCH detection determined by the terminal device itself to the network device, so that the network device can send PDCCH to the terminal device based on the time point indicated by the second indication information. This method can align the time period for the network device to send PDCCH with the time period for the terminal device to detect PDCCH, which is beneficial for the terminal device to detect PDCCH in a timely manner.

[0022] In one optional implementation, the terminal device may send capability information to the network device. For example, the terminal device may send capability information to the network device after determining the start point for detecting the PDCCH based on an instruction from the network device. The capability information indicates that the terminal device has the capability to support a dynamic activation period. Furthermore, a dynamic activation period may also be referred to as a temporary activation period, an additional activation period, or an extra activation period.

[0023] As can be seen, in this embodiment, the terminal device can indicate to the network through capability information that it has the capability to support dynamic activation periods. This allows the network device to configure the terminal device to determine the start point of the dynamic activation period, such as configuring a first time point for the terminal device. This, in turn, allows the terminal device to detect the PDCCH based on the start point of the dynamic activation period, for example, starting detection from the configured first time point, without waiting until during a discontinuous reception activation period. This enables the terminal device to detect the PDCCH in a timely manner, reducing downlink service latency.

[0024] In another alternative implementation, the terminal device may receive first configuration information from the network device. For example, if the terminal device determines the starting point for detecting the PDCCH itself, it may receive the first configuration information from the network device. The first configuration information is used to indicate whether the terminal device is allowed to initiate a dynamic activation period.

[0025] As can be seen, in this embodiment, the terminal device can learn from the configured information that it can initiate a dynamic activation period, and thus can independently determine the time point used to indicate the dynamic activation period, and detect the PDCCH based on that time point. For example, after receiving the first configuration information, the terminal device can independently determine the starting point for dynamically detecting the PDCCH, and thus start detecting the PDCCH from that starting point, without waiting to detect the PDCCH during a discontinuous reception activation period, enabling the terminal device to detect the PDCCH in a timely manner and reducing downlink service latency.

[0026] In one optional implementation, the terminal device detects the PDCCH starting from a first time point, including: periodically detecting the PDCCH based on a first period, starting from the first time point. The first period can be configured by the network device for the terminal device, or it can be determined by the terminal device itself.

[0027] As can be seen, in this embodiment, the introduction of a first cycle allows the terminal device to periodically detect the PDCCH starting from a first time point. Compared with the terminal device continuously detecting the PDCCH starting from a first time point, this can reduce the power consumption of the terminal device.

[0028] In one optional implementation, the terminal device may also periodically detect the PDCCH based on the second cycle, starting from a third time point. The third time point is the time point at which the PDCCH is detected.

[0029] As can be seen, in this embodiment, a second period is introduced, so that the terminal device periodically detects the PDCCH based on the second period starting from the time point when the PDCCH is detected, thereby enabling the terminal device to detect subsequent periodic PDCCHs.

[0030] Secondly, embodiments of this application also provide a communication method, which can be executed by a network device. The network device can be a network equipment (such as a base station), a component of a network equipment (such as a processor, chip, or chip system), or a logic module capable of implementing all or part of the network functions. Specifically, the network device determines a first time point, which is associated with the transmission time or arrival time of uplink data. Based on the first time point, the network device sends a Physical Downlink Control Channel (PDCCH) to the terminal device. This PDCCH is used to schedule data transmission.

[0031] As can be seen, by using the above method, the network device can send a PDCCH for scheduling data transmission to the terminal device based on a first time point associated with the transmission time or arrival time of the uplink data, so that the network device can send the PDCCH in a timely manner and reduce the latency of downlink services.

[0032] In one possible approach, the network device sends the PDCCH to the terminal device based on a first time point. This could be done either after the first time point or at a time point later than the first time point. This method allows the network device to send the PDCCH in a timely manner, reducing downlink service latency.

[0033] In one optional implementation, the network device may further determine a second time point, which is later than the first time point. In this method, the network device sends a PDCCH to the terminal device based on the first time point, including sending the PDCCH to the terminal device between the first time point and the second time point.

[0034] As can be seen, in this embodiment, the network device sends PDCCH to the terminal device between the determined first time point and the second time point, so that the network device sends PDCCH to the terminal device in a timely manner.

[0035] In one optional implementation, the network device determines a first time point by: receiving second indication information from a terminal device, the second indication information indicating the first time point; and determining the first time point based on the second indication information.

[0036] As can be seen, in this embodiment, the network device can determine the first time point according to the instructions of the terminal device, which can reduce the complexity of the network device processing.

[0037] In one possible approach, the second indication information includes a first time point to directly indicate the first time point. In another possible approach, the second indication information includes the uplink data transmission time and the duration between the first time point and the uplink data transmission time to indirectly indicate the first time point. Therefore, the second indication information can flexibly indicate the first time point through either direct or indirect indication.

[0038] In one optional implementation, the second indication information is further used to indicate a second time point. In this method, the network device determines the second time point by: determining the second time point based on the second indication information.

[0039] As can be seen, in this embodiment, the network device can also determine a second time point based on the instructions of the terminal device, which can reduce the complexity of the network device processing.

[0040] In one possible approach, the second indication information also includes a second time point to directly indicate the second time point. In another possible approach, the second indication information also includes the duration between the second time point and the first time point to indirectly indicate the second time point. Therefore, the second indication information can flexibly indicate the second time point through either direct or indirect indication.

[0041] In another alternative implementation, the network device determines the first time point by: determining the earliest time point at which downlink data associated with uplink data arrives at the network device based on the estimated arrival time of uplink data as the first time point.

[0042] As can be seen, in this embodiment, the network device can estimate the earliest time that the downlink data associated with the uplink data will arrive at the network device from the server, based on the arrival time of the uplink data. Therefore, the network device can send a PDCCH for scheduling data transmission to the terminal device based on the estimated earliest time. Thus, by determining the estimated earliest time as the first time, the network device can send the PDCCH to the terminal device in a timely manner, reducing downlink service latency.

[0043] In one alternative implementation, the network device determines the second time point by: determining the latest time point at which downlink data associated with the uplink data arrives at the network device based on the estimated arrival time of the uplink data as the second time point.

[0044] As can be seen, in this embodiment, the network device can estimate the latest possible arrival time of the downlink data associated with the uplink data from the server to the network device based on the arrival time of the uplink data. Therefore, the network device may send the PDCCH for scheduling data transmission to the terminal device at the latest estimated latest time. Thus, by determining the estimated latest time as the second time point, the network device can send the PDCCH to the terminal device in a timely manner, reducing downlink service latency.

[0045] In one optional implementation, the network device may send first indication information to the terminal device, for example, by sending the first indication information to the terminal device after determining a first time point itself. The first indication information is used to indicate the first time point.

[0046] As can be seen, in this embodiment, the network device informs the terminal device of the first time point it determines, so that the terminal device can detect the PDCCH based on the first time point. This helps the terminal device to detect the PDCCH in a timely manner and reduces the latency of downlink services.

[0047] In one possible approach, the first indication information includes a first time point to directly indicate the first time point. In another possible approach, the first indication information includes the uplink data transmission time and the duration between the uplink data transmission time and the first time point to indirectly indicate the first time point. Therefore, the first indication information can indicate the first time point through either direct or indirect indication.

[0048] In one alternative implementation, the first indication information is further used to indicate a second time point. For example, if the network device has determined the second time point itself, the first indication information is also used to indicate the second time point.

[0049] As can be seen, in this embodiment, the network device can also inform the terminal device of its own determined second time point, so that the terminal device can also detect the PDCCH based on the second time point. This is beneficial for the terminal device to detect the PDCCH in a timely manner and reduce power consumption.

[0050] In one possible approach, the first indication information also includes a second time point to directly indicate the second time point. In another possible approach, the first indication information also includes the duration between the second time point and the first time point to indirectly indicate the second time point. Therefore, the first indication information can indicate the second time point through either direct or indirect indication.

[0051] In one optional implementation, the network device may send first configuration information to the terminal device. For example, the network device may send the first configuration information to the terminal device based on an instruction from the terminal device to determine a first time point. The first configuration information is used to indicate that the terminal device is allowed to activate a dynamic activation period. Furthermore, the dynamic activation period may also be referred to as a temporary activation period, an additional activation period, or an extra activation period.

[0052] As can be seen, in this embodiment, the network device instructs the terminal device to enable the function of activating the dynamic activation period through the first configuration information. This allows the terminal device to determine the time point for indicating the dynamic activation period, such as determining the first time point for indicating the dynamic activation period. This, in turn, allows the terminal device to detect the PDCCH during the dynamic activation period, enabling timely detection of the PDCCH and reducing the latency of downlink services.

[0053] In one alternative implementation, the network device may receive capability information from the terminal device. For example, the network device may receive capability information from the terminal device after determining a first point in time. The capability information indicates that the terminal device has the capability to support a dynamic activation period.

[0054] As can be seen, in this embodiment, the network device learns from the capability information of the terminal device that the terminal device has the capability to support a dynamic activation period. Therefore, the network device can independently determine the time point used to indicate that the terminal device is in a dynamic activation period, such as determining a first time point to indicate the dynamic activation period. Based on the dynamic activation period indicated by the first time point, the network device can send a PDCCH to the terminal device, enabling timely scheduling of downlink data and reducing downlink service latency.

[0055] In one optional implementation, the network device may receive second configuration information. The second configuration information includes a first data packet delay budget (PDB) and a second PDB. The first PDB is used to schedule a first data packet, and the second PDB is used to schedule a second data packet. The first data packet is the first N data packets in the downlink data associated with the uplink data, and the second data packet is the data packet in the downlink data excluding the first N data packets, where N is a positive integer. In this mode, the network device sends a PDCCH to the terminal device based on a first time point, including: sending a PDCCH for scheduling the first data packet to the terminal device based on the first PDB, and sending a PDCCH for scheduling the second data packet to the terminal device based on the second PDB.

[0056] As can be seen, in this embodiment, the network device is configured with PDBs for scheduling different data packets. Therefore, the network device can schedule different data packets based on different PDBs, ensuring the latency requirements of different data packets are met.

[0057] Thirdly, embodiments of this application also provide a communication method, which can be executed by a network device. The network device can be a network equipment (such as a base station), a component of a network equipment (such as a processor, chip, or chip system), or a logic module capable of implementing all or part of the network functions. Specifically, the network device determines a third data packet delay budget (PDB) for scheduling downlink data associated with the uplink data based on uplink data transmission information. Based on the third PDB, the network device sends downlink data to the terminal device.

[0058] As can be seen, in this method, the PDB used by the network device to send downlink data to the terminal device is determined based on the transmission information of the uplink data associated with the downlink data. Compared with the network device directly using a preset downlink PDB to send downlink data to the terminal device, this method can ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the service-allowed delay requirements even when the uplink data transmission delay exceeds the preset uplink PDB.

[0059] In one optional implementation, the uplink data transmission information includes at least one of the following: uplink data timing information, uplink continuous data transmission volume, and uplink continuous data transmission duration. Here, uplink continuous data refers to a set of continuous data within the uplink data generated by the terminal device.

[0060] In one optional implementation, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the transmission information of the uplink data, including: receiving third indication information from a terminal device, the third indication information indicating the time information of the uplink data; and determining a third PDB for scheduling downlink data associated with the uplink data based on the time information of the uplink data.

[0061] As can be seen, in this embodiment, the network device can determine the third PDB based on the uplink data time information indicated by the terminal device, so that the determined third PDB can ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the latency requirements allowed by the service.

[0062] In one optional implementation, the uplink data time information includes a first duration, where the uplink data transmission duration is greater than the duration of a preset uplink PDB. In this method, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data time information, including: determining the difference between the preset downlink PDB and the first duration as the third PDB for scheduling the downlink data associated with the uplink data. The preset downlink PDB may be pre-configured by the network device, or it may be pre-configured for the network device by other devices (such as core network equipment).

[0063] As can be seen, in this embodiment, the uplink data time information indicated by the terminal device to the network device includes uplink data transmission duration greater than the uplink preset PDB duration (first duration). Therefore, in order to ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the service-allowed delay requirements, the third PDB used for scheduling downlink data needs to be subtracted from the downlink preset PDB by the first duration; that is, the value of the third PDB is equal to the difference between the downlink preset PDB and the first duration.

[0064] In one optional implementation, the uplink data timing information includes the waiting time of the uplink data in the terminal device's buffer. In this method, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data timing information, including: if the waiting time is greater than a preset uplink PDB, determining the difference between the preset downlink PDB and a second duration as the third PDB for scheduling the downlink data associated with the uplink data. The second duration is equal to the difference between the waiting time and the preset uplink PDB.

[0065] As can be seen, in this embodiment, the uplink data timing information indicated by the terminal device to the network device includes the waiting time of the uplink data in the terminal device's buffer. Therefore, if the waiting time exceeds the preset PDB, to ensure that the sum of the uplink and downlink data transmission delays is within the service-allowed latency requirements, downlink data cannot be directly sent based on the downlink preset PDB; the downlink preset PDB needs to be adjusted. Specifically, the third PDB used to schedule downlink data associated with uplink data is equal to the downlink preset PDB minus the difference between the waiting time and the uplink preset PDB; that is, the third PDB is equal to the difference between the downlink preset PDB and the second waiting time.

[0066] In one optional implementation, the uplink data timing information includes the time it takes for the uplink data to arrive at the terminal device's buffer. In this method, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data timing information, including: determining the waiting time for the uplink data in the buffer based on the time it arrives at the terminal device's buffer and the time it arrives at the network device; if the waiting time is longer than a preset uplink PDB, the difference between the preset downlink PDB and the second duration is determined as the third PDB for scheduling the downlink data associated with the uplink data. The second duration is equal to the difference between the waiting time and the preset uplink PDB.

[0067] As can be seen, in this embodiment, the uplink data time information indicated by the terminal device to the network device includes the time it takes for the uplink data to arrive in the terminal device's buffer. Therefore, if the waiting time of the uplink data in the terminal device's buffer, determined by the network device based on the time it takes for the uplink data to arrive in the terminal device's buffer, is greater than the uplink preset PDB, then to ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the allowable latency requirements of the service, the downlink data cannot be directly sent based on the downlink preset PDB, and the downlink preset PDB needs to be adjusted. Specifically, the third PDB used to schedule the downlink data associated with the uplink data is equal to the downlink preset PDB minus the difference between the waiting time and the uplink preset PDB; that is, the third PDB is equal to the difference between the downlink preset PDB and the second duration.

[0068] In one optional implementation, the uplink data transmission information includes the transmission volume of continuous uplink data. In this method, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data transmission information, including: if the transmission volume of continuous uplink data is greater than a first threshold, determining a first value as the third PDB for scheduling the downlink data associated with the uplink data. The first value is less than a preset downlink PDB.

[0069] As can be seen, in this embodiment, when the transmission volume of uplink continuous data is greater than the first threshold, the network device determines a first value less than the preset downlink PDB as the PDB for scheduling the downlink data associated with the uplink data, which can ensure that the sum of the transmission delay of uplink data and the transmission delay of downlink data is within the latency requirements allowed by the service.

[0070] In one optional implementation, the uplink data transmission information includes the transmission duration of continuous uplink data. In this method, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data transmission information, including: if the transmission duration of continuous uplink data is greater than a second threshold, determining a second value as the third PDB for scheduling the downlink data associated with the uplink data. The second value is less than a preset downlink PDB.

[0071] As can be seen, in this embodiment, when the transmission duration of uplink continuous data exceeds the second threshold, the network device determines a second value less than the preset downlink PDB as the PDB for scheduling the downlink data associated with the uplink data, which can ensure that the sum of the transmission delay of uplink data and the transmission delay of downlink data is within the latency requirements allowed by the service.

[0072] In one possible scenario, the first value is equal to the second value, or the first value is not equal to the second value.

[0073] In one optional implementation, the network device may receive second configuration information, which includes a first PDB. The first PDB is used to schedule a first data packet, where the first data packet is the first N data packets in the downlink data, and N is a positive integer. In this mode, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data transmission information, including: determining the third PDB for scheduling the first data packet associated with the uplink data based on the uplink data transmission information and the first PDB.

[0074] As can be seen, in this embodiment, the network device is configured with a first PDB for scheduling the first N data packets (first data packets) in the downlink data. Therefore, based on the uplink data transmission information and the configured first PDB, the network device determines a third PDB for scheduling the first data packets in the downlink data, thereby ensuring that the sum of the uplink data transmission delay and the downlink data transmission delay is within the service-permitted delay requirements.

[0075] In one optional implementation, the second configuration information further includes a second PDB, which is used to schedule a second data packet. The second data packet is a data packet in the downlink data excluding the first N data packets. In this method, the network device can also send the second data packet to the terminal device based on the second PDB.

[0076] As can be seen, in this embodiment, the network device is also configured with a second PDB for scheduling data packets (second data packets) that are not included in the first N data packets in the downlink data. Therefore, the network device can send the second data packets to the terminal device based on the second PDB to ensure the latency requirements of the second data packets are met.

[0077] Fourthly, embodiments of this application provide a communication method executed by a terminal device. The terminal device may be a terminal, a component of a terminal (e.g., a processor, chip, or chip system), or a logic module capable of implementing all or part of the terminal's functions. Specifically, the terminal device sends third indication information to a network device. This third indication information indicates the timing information of uplink data and is used by the network device to determine a third data packet delay budget (PDB) for scheduling downlink data associated with the uplink data.

[0078] As can be seen, through this method, the terminal device indicates the uplink data time information to the network device, so that the network device can determine the PDB of the downlink data associated with the uplink data based on the uplink data time information. This is beneficial to ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the service-allowed delay requirement when the uplink data transmission delay exceeds the uplink preset PDB.

[0079] In one optional implementation, the uplink data timing information includes at least one of the following: a first duration, a waiting time for uplink data in the terminal device's buffer, and the time for uplink data to arrive at the terminal device's buffer. The first duration is when the uplink data transmission duration is greater than the duration of the preset uplink PDB.

[0080] Fifthly, embodiments of this application also provide a communication device. This communication device has some or all of the functions of the terminal device described in the first or fourth aspect above, or some or all of the functions of the network device described in the second or third aspect above. For example, the communication device may have some or all of the functions of the terminal device described in the first aspect of this application, or it may have the functions of any one of the embodiments of this application implemented individually. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0081] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above method. The communication unit is used to support communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device.

[0082] In one embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a terminal device, and the communication unit being used to send and receive signals / signaling.

[0083] The processing unit is configured to determine a first time point, which is associated with the transmission time or arrival time of uplink data; the processing unit is also configured to detect the Physical Downlink Control Channel (PDCCH) starting from the first time point, the PDCCH being used to schedule data transmission.

[0084] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0085] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a network device, and the communication unit being used to send and receive signals / signaling.

[0086] The processing unit is configured to determine a first time point, which is associated with the transmission time or arrival time of uplink data; the processing unit is also configured to send a Physical Downlink Control Channel (PDCCH) to the terminal device based on the first time point, the PDCCH being used to schedule data transmission.

[0087] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0088] In another embodiment, the communication device includes a processing unit and a communication unit, and the device is applied to a network device;

[0089] The processing unit is used to determine the third data packet delay budget (PDB) for scheduling downlink data associated with the uplink data based on the transmission information of the uplink data; the communication unit is used to send downlink data to the terminal device based on the third PDB.

[0090] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0091] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a terminal device, and the processing unit being used to process signals / signaling;

[0092] The communication unit is used to send third indication information to the network device. The third indication information is used to indicate the time information of the uplink data and to help the network device determine the third data packet delay budget (PDB) for scheduling the downlink data associated with the uplink data.

[0093] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0094] As an example, the processing unit can be a processor, and the communication unit can be a transceiver unit, transceiver, or communication interface. It is understood that when the communication device is a communication apparatus (e.g., a terminal or network device), the communication unit can be a transceiver within the communication apparatus (e.g., a transceiver includes a transmitter and a receiver), implemented, for example, through an antenna, feeder, and codec within the communication apparatus. Alternatively, if the communication device is a chip located within a device, the processing unit can be the chip's processing circuitry, logic circuitry, etc., and the communication unit can be the chip's input / output interface, such as input / output circuitry, pins, etc.

[0095] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0096] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a system-on-a-chip (SoC). Whether the various devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above-mentioned devices.

[0097] Sixthly, embodiments of this application also provide a processor for executing the various methods described above. During the execution of these methods, the processes related to sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. When outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0098] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0099] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0100] Seventhly, embodiments of this application also provide a communication system, which includes a terminal device and a network device. In another possible design, the system may further include other devices / functional network elements that interact with at least one of the terminal device and the network device.

[0101] Eighthly, embodiments of this application provide a computer-readable storage medium for storing instructions that, when executed on a communication device, implement the method described in any one of the first to fourth aspects.

[0102] Ninthly, embodiments of this application also provide a computer program product including instructions that, when executed on a communication device, implement the method described in any one of the first to fourth aspects.

[0103] In a tenth aspect, this application provides a chip including a processor (or logic circuit). Optionally, the chip may further include a communication interface (or interface) for implementing at least one of the following: the method in any of the possible embodiments of the first to fourth aspects. In one possible implementation, if the chip is the smallest processing unit in the whole machine, the chip may be a processor, or may include a processor and a memory, or may include a processor, a memory, and a transceiver for implementing at least one of the following: the method in any of the possible embodiments of the first to fourth aspects.

[0104] Eleventhly, this application provides a chip system. The chip system includes a processor and an interface. Optionally, it may also include memory for implementing at least one of the following: the methods in any of the possible embodiments of the first to fourth aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0105] The beneficial effects of aspects five through eleven above can be found in the descriptions of the beneficial effects in aspects one through four, and will not be repeated here. Attached Figure Description

[0106] Figure 1 is a schematic diagram of a system architecture;

[0107] Figure 2 is a schematic diagram of the processing flow of AIGC intelligent dialogue;

[0108] Figure 3 is a schematic diagram of a DRX cycle;

[0109] Figure 4 is a schematic diagram of another DRX cycle;

[0110] Figure 5 is a schematic diagram of another DRX cycle;

[0111] Figure 6 is a schematic diagram of another DRX cycle;

[0112] Figure 7 is a schematic diagram of another type of DRX cycle;

[0113] Figure 8 is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0114] Figure 9 is a schematic diagram of a transmission provided in an embodiment of this application;

[0115] Figure 10 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0116] Figure 11 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0117] Figure 12 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0118] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0119] Figure 14 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0120] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0121] The embodiments of this application can be applied to fourth-generation (4G) communication systems such as long-term evolution (LTE) systems and fifth-generation (5G) communication systems such as new radio (NR) systems. As communication technologies continue to develop, the technical solutions of the embodiments of this application can also be used in subsequent evolved communication systems, such as sixth-generation (6G) mobile communication technology systems and seventh-generation (7G) mobile communication technology systems.

[0122] Please refer to Figure 1, which is a schematic diagram of a system architecture provided in an embodiment of this application. This system architecture includes network functional entities such as terminal devices, a radio access network (RAN), a user plane function (UPF), a data network (DN), and an access and mobility management function (AMF). As shown in Figure 1, the terminal device can access the wireless network to obtain services from an external network (e.g., DN) or communicate with other devices, such as other terminal devices, through the wireless network. The devices / functional network elements involved in the system architecture shown in Figure 1 will be described in detail below.

[0123] Terminal devices can include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem that have wireless communication capabilities. Terminal devices can also be referred to as terminals. Terminal equipment can also refer to user equipment (UE), access terminal, subscriber unit, user agent, cellular phone, smartphone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handset, laptop computer, point of sale (POS) machine, customer-premises equipment (CPE), machine-type communication (MTC) terminal, communication equipment carried on high-altitude aircraft, wearable device, drone, robot, device-to-device (D2D) terminal, vehicle-to-everything (V2X) terminal, virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, and smart grid. This application does not limit the scope of wireless terminals, such as those in grids, transportation safety, smart cities, smart homes, or future communication networks.

[0124] The RAN (Radio Access Provider) is a network composed of multiple 5G-RAN nodes, implementing radio physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management. The 5G-RAN connects to the UPF (User Plane Provider Function) via the user plane interface N3 for transmitting data from terminal devices; it also establishes a control plane signaling connection with the AMF (Ambient Function Provider) via the control plane interface N2 for implementing functions such as radio access bearer control. RAN nodes can be base stations in 5G networks or base stations, broadband network gateways (BNGs), aggregation switches, or non-3rd generation partnership project (3GPP) access devices in future communication systems. Optionally, the RAN node in this application embodiment may include various forms of base stations, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, equipment that implements base station functions in communication systems evolved after 5G, transmitting and receiving points (TRP), transmitting points (TP), integrated access and backhaul nodes (IAB nodes), mobile switching centers, and equipment that undertakes base station functions in D2D and machine-to-machine (M2M) communications, etc. This application embodiment does not specifically limit these.

[0125] The following network functional entities can be understood as core network devices:

[0126] The AMF is primarily responsible for UE authentication, UE mobility management, network slice selection, and session management function (SMF) selection. The AMF serves as the anchor point for N1 and N2 signaling connections and provides routing for N1 / N2 SM messages to the SMF. The AMF maintains and manages UE status information, such as user location updates, user registration networks, and user handover.

[0127] SMF is primarily responsible for all control plane functions of UE session management, such as session establishment, modification, and release. Its specific functions include UPF selection, Internet Protocol (IP) address allocation, session quality of service (QoS) management, and obtaining policies and charging control (PCC) policies from the policy control function (PCF).

[0128] UPF serves as the anchor point for protocol data unit (PDU) session connections, and is responsible for filtering data packets from user equipment, data transmission / forwarding, rate control, and generating billing information.

[0129] Unified data management (UDM) mainly manages user data, such as subscription information. This includes obtaining subscription information from the unified data repository (UDR) and providing it to other network elements (such as AMF); generating 3rd generation partnership project (3GPP) authentication credentials for UEs; and registering and maintaining the network elements currently serving the UE (for example, AMF ID1 represents the UE's current serving AMF).

[0130] UDR is primarily used to store user data, including subscription data invoked by UDM, policy information invoked by PCF, structured data for capability openness, and application data invoked by network element function (NEF).

[0131] NEF stands for Network Capability Open Element, which is used to connect other internal network elements of the core network with external application servers of the core network to provide network capability information to external application servers, or to provide information from external application servers to core network elements.

[0132] Application functions (AFs) interact with core network elements to provide services. For example, they interact with PCFs to control service policies, interact with NEFs to obtain network capability information or provide application information to the network, and provide data network access point information to PCFs to generate routing information for corresponding data services.

[0133] PCF provides configuration policy information to UE and provides network control plane elements (such as AMF and SMF elements) with policy information for managing UE, such as QoS policies and slice selection policies.

[0134] DN refers to the operator network that provides data transmission services to users, such as IP multi-media service (IMS) and the Internet.

[0135] It is understood that when the solutions of this application are applied to 6G or future communication systems, the names of the corresponding network function entities may change, and this application does not limit this.

[0136] The embodiments disclosed in this application will be presented to illustrate various aspects, embodiments, or features of this application in relation to systems including multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0137] To facilitate understanding of the solutions in the embodiments of this application, the terms that may be involved in the embodiments of this application are explained below.

[0138] 1. AIGC Intelligent Dialogue.

[0139] Referring to Figure 2, which is a schematic diagram of the processing flow of an AIGC intelligent dialogue, the processing flow includes, but is not limited to: the terminal inputs a question (i.e., the user asks a question), which can be any combination of text, voice, and image, such as a prompt word + image; the input question is converted into text by voice in the network, for example, by automatic speech recognition (ASR); the network converts the text into tokens and inputs them into a large model; the large model performs reasoning based on the input tokens and generates an answer, which is presented in the form of tokens, with the interval between each token possibly ranging from tens of milliseconds; the network packages the voice corresponding to N tokens and sends it to the terminal, where each token may correspond to a character, a word, or a punctuation mark, and N is a positive integer.

[0140] In a downlink data stream, the first data packet sent by the network to the terminal is called the downlink first packet. Subsequent data packets in the same data stream are called downlink non-first packets. When downlink data carries AI inference results, the downlink data can also be called the downlink inference results. The downlink first packet is constrained by end-to-end latency requirements and the inference time of large models, typically tens of milliseconds. For example, the packet delay budget (PDB) of the downlink first packet is 20 to 40 milliseconds. Furthermore, the latency requirements of downlink non-first packets are limited by the voice playback rate. For example, subsequent non-first packets can arrive at the terminal before the voice playback corresponding to the downlink first packet is completed. The latency of downlink non-first packets is typically several hundred milliseconds, for example, the PDB of downlink non-first packets is 200 milliseconds.

[0141] It is evident that in the AIGC intelligent dialogue scenario, the latency requirements for the downlink first packet are different from those for the downlink non-first packets, and the latency requirements for the downlink first packet are lower than those for the downlink non-first packets.

[0142] 2. Discontinuous reception (DRX).

[0143] DRX is a mechanism for saving terminal power. Figure 3 is a schematic diagram of a DRX cycle. In Figure 3, the time period marked "on duration" is the period during which the terminal continuously detects the physical downlink control channel (PDCCH). During this period, the terminal is in a wake-up state, which is the "active period". In Figure 3, the time period marked "opportunity for DRX" is the DRX sleep time, that is, the period during which the terminal enters sleep mode and does not detect the PDCCH in order to save power, which is the "dormant period".

[0144] The terminal's activation period includes not only the time period corresponding to the on duration timer, but also the DRX inactivity time and the retransmission time. For example, Figure 4 illustrates another DRX cycle. As shown in Figure 4, the terminal is active not only during the on duration timer, but also during the DRX inactivity timer and the DRX retransmission timer.

[0145] Specifically, during the on-duration period of the DRX activation period, when the terminal performs uplink or downlink initial multiple transmission scheduling, the base station will start or restart a drx-inactivity timer. Consequently, the terminal will remain in the activation period / active state until the drx-inactivity timer times out. For example, Figure 5 illustrates another DRX cycle. As shown in Figure 5, when the terminal performs uplink or downlink initial multiple transmission scheduling, the base station starts or restarts a drx-inactivity timer. Therefore, even if the configured on-duration timer has ended, but the drx-inactivity timer is running, the terminal still needs to continue monitoring the PDCCH until the drx-inactivity timer times out.

[0146] Furthermore, if decoding of a transport block (TB) in a downlink Hybrid Automatic Repeat Request (HARQ) process fails, the terminal can assume that a retransmission will not occur until at least the HARQ round-trip time (HARQ RTT). Therefore, while the HARQ RTT timer is running, the terminal does not need to check the PDCCH. When the HARQ RTT timer expires and the data received by the HARQ process has not been successfully decoded, the terminal starts a drx-retransmission timer for that HARQ process. The drx-retransmission timer represents the maximum time the terminal can wait for a retransmission. While this drx-retransmission timer is running, the terminal checks the PDCCH used for HARQ retransmissions.

[0147] For example, Figure 6 illustrates another DRX cycle. As shown in Figure 6, when the terminal receives downlink control information (DCI) for the initial data transmission, it starts a drx-inactivity timer. When the terminal sends a non-acknowledgement (NACK) indicating unsuccessful data decoding, it starts a HARQ RTT timer. The terminal does not check the PDCCH during the HARQ RTT timer. After the HARQ RTT timer expires, the terminal starts a drx-retransmission timer and checks the PDCCH during the drx-retransmission timer. When the terminal sends another NACK indicating unsuccessful data decoding, it restarts a HARQ RTT timer.

[0148] Please refer to Figure 7, which illustrates another type of DRX cycle. As shown in Figure 7, the network is configured with a DRX cycle for the terminal, and the network has downlink data that needs to be sent to the terminal at time t1. However, the terminal is in the DRX sleep period at time t1. Therefore, the network needs to wait until the terminal enters the DRX active period (after time t2), that is, the network needs to wait an additional time between time t1 and time t2 before sending the downlink data to the terminal. If the DRX cycle is long, for example, 160ms, and the time when the network has downlink data to send to the terminal coincides with the time when the terminal enters the sleep period from the active period, then the maximum additional waiting time for the network is 160ms before sending the downlink data to the terminal. However, in some services, the PDB requirement for downlink data is high, and the network's long waiting time cannot meet the PDB constraint of the downlink data. For example, in AIGC intelligent dialogue services, the PDB requirement for the first downlink packet is tens of milliseconds, and the DRX period is hundreds of milliseconds. There is a moment when the network needs to send the first downlink packet to the terminal, which happens to be the moment when the terminal enters the DRX sleep period from the DRX activation period. In this case, the network needs to wait hundreds of milliseconds before it can send the first downlink packet to the terminal. This long waiting time makes the downlink service latency large and fails to meet the PDB constraint of the first downlink packet.

[0149] In this embodiment, within the DRX cycle configured by the network for the terminal, a dynamic activation period associated with the uplink data transmission time or arrival time is introduced above the first activation period controlled by the on-duration timer, drx-inactivity timer, and drx-retransmission timer. Therefore, when the time when downlink data needs to be sent to the terminal is outside the first activation period, the network does not need to wait until the terminal is in the first activation period to send the downlink data. Instead, it can directly schedule the downlink data to the terminal within the dynamic activation period associated with the uplink data transmission time or arrival time, enabling timely scheduling of the downlink data. Correspondingly, the terminal does not need to wait until the first activation period to detect the PDCCH used for scheduling data transmission. It can start detecting the PDCCH used for scheduling data transmission from the beginning of the dynamic activation period associated with the uplink data transmission time or arrival time, enabling timely detection of the PDCCH used for scheduling downlink data and reducing downlink service latency.

[0150] For example, the network and the terminal each determine a first time point that indicates the start of the dynamic activation period and is associated with the uplink data transmission time or the uplink data arrival time. The network sends a PDCCH (Power-Oriented Data Communication) to the terminal for scheduling data transmission based on this first time point. The terminal then starts detecting the PDCCH for scheduling data transmission from this first time point. Therefore, the network can promptly schedule downlink data to the terminal based on the first time point indicating the start of the dynamic activation period; the terminal can also promptly detect the PDCCH for scheduling downlink data from this first time point, reducing downlink service latency.

[0151] The embodiments of this application are described in detail below with reference to the accompanying drawings. The embodiments of this application illustrate the corresponding methods using a terminal device and a network device as examples of the execution subjects. For example, the terminal device is the terminal equipment in the system shown in Figure 1, and the network device is a node in the wireless access network in the system shown in Figure 1. However, this application does not limit the execution subject of the method. For example, the terminal device in the method can also be a processor, module, chip, chip system, or software module that supports the implementation of the corresponding method.

[0152] This application provides a communication method 100, and Figure 8 is an interactive schematic diagram of the communication method 100. The communication method 100 is described from the perspective of the interaction between a terminal device and a network device. The communication method 100 includes, but is not limited to, the following steps:

[0153] S801. The network device determines a first time point, which is associated with the transmission time of uplink data or the arrival time of uplink data.

[0154] The uplink data transmission time refers to the time when the terminal device sends uplink data to the network device, and the uplink data arrival time refers to the time when the uplink data arrives at the network device. The first time point is related to the uplink data transmission time or the uplink data arrival time. This can be understood as: the first time point is correlated with the uplink data transmission time or the uplink data arrival time, or it can be understood as: the first time point is determined based on the uplink data transmission time or the uplink data arrival time.

[0155] For example, in implementation 1.1 below, the first time point indicated by the terminal device to the network device can be the earliest time point at which the downlink data associated with the uplink data, estimated based on the uplink data transmission time, arrives at the network device. This indicates that the first time point is determined by the terminal device based on the uplink data transmission time, or in other words, the first time point is correlated with the uplink data transmission time. In this method, the first time point indicated by the terminal device to the network device is the earliest time point at which the downlink data associated with the uplink data, estimated based on the uplink data transmission time, arrives at the network device. Therefore, the network device can schedule the downlink data associated with the uplink data to the terminal device as early as the first time point, and the terminal device can start detecting the PDCCH used for scheduling data transmission as early as the first time point. This is beneficial for the network device to schedule downlink data in a timely manner based on the first time point, and for the terminal device to detect the PDCCH in a timely manner based on the first time point, thereby reducing the latency of downlink services.

[0156] For example, in implementation 1.2 below, the network device can determine the earliest time point at which downlink data associated with uplink data arrives at the network device, based on the estimated arrival time of uplink data, as the first time point. This indicates that the first time point is determined by the network device based on the arrival time of the uplink data, or in other words, the first time point is correlated with the arrival time of the uplink data. In this method, since the first time point is the earliest time point at which downlink data associated with uplink data arrives at the network device, as estimated by the network device based on the arrival time of the uplink data, the network device can schedule downlink data associated with uplink data to the terminal device as early as the first time point. The terminal device can also start detecting the PDCCH used for scheduling data transmission as early as the first time point. This is beneficial for the network device to schedule downlink data in a timely manner based on the first time point, and for the terminal device to detect the PDCCH in a timely manner based on the first time point, thereby reducing the latency of downlink services.

[0157] It is evident that associating the first time point with the uplink data transmission time or the uplink data arrival time allows the first time point to be regarded as: the earliest time point for network devices to schedule downlink data associated with uplink data, or for terminal devices to detect the PDCCH used to schedule downlink data associated with uplink data. This facilitates network devices to schedule downlink data associated with uplink data in a timely manner based on the first time point, and terminal devices to detect the PDCCH used to schedule downlink data associated with uplink data in a timely manner based on the first time point, thereby reducing downlink service latency.

[0158] Furthermore, the network device can determine the first time point in various ways, and this application embodiment does not limit this method. In one possible approach, the network device can determine the first time point through an instruction from the terminal device. In another possible approach, the network device can determine the first time point itself, for example, by determining the first time point based on the arrival time of uplink data. The following details two implementation methods: the network device determining the first time point based on an instruction from the terminal, and the network device determining the first time point itself.

[0159] Implementation method 1.1: The network device determines the first time point based on the instruction of the terminal device.

[0160] In one optional implementation, the network device determines the first time point by: receiving second indication information from a terminal device, the second indication information indicating the first time point; and determining the first time point based on the second indication information. Correspondingly, the terminal device sends the second indication information to the network device. The first time point indicated by the second indication information is determined by the terminal device itself, and its determination method can be found in Embodiment 2.2 below.

[0161] In one possible approach, the second indication information can also be understood as: used to determine the dynamic activation period of the terminal device. In this approach, the network device can determine the dynamic activation period of the terminal device based on the second indication information, such as determining the start point (first time point) for indicating the dynamic activation period of the terminal device. This allows the network device to send a PDCCH for scheduling data transmission to the terminal device based on the start point of the dynamic activation period of the terminal device.

[0162] Furthermore, the dynamic activation period can also be referred to as a temporary activation period, an additional activation period, or an extra activation period, etc., and this application embodiment does not limit this. The dynamic activation period can be understood as an additional activation period defined above the first activation period controlled by the on-duration timer, drx-inactivity timer, and drx-retransmission timer within the DRX cycle configured by the network device for the terminal device. However, the dynamic activation period of the terminal device can be located within the first activation period, outside the first activation period, or partly within the first activation period and partly outside the first activation period; this application embodiment does not limit this. Regarding the first activation period controlled by the on-duration timer, drx-inactivity timer, and drx-retransmission timer within the DRX cycle configured by the network device for the terminal device, please refer to the activation periods shown in Figures 4 to 6 above, and will not be repeated here.

[0163] Optionally, the first time point can be associated with the uplink data transmission time or the uplink data arrival time. This first time point can be seen as indicating the start of the dynamic activation period, which can then be considered a dynamic activation period associated with the uplink data transmission time or the uplink data arrival time. Associating the dynamic activation period with the uplink data transmission time or the uplink data arrival time allows the network device to promptly schedule downlink data associated with the uplink data to the terminal device during the dynamic activation period. The terminal device can also promptly detect the PDCCH during the dynamic activation period, reducing downlink service latency.

[0164] In another possible approach, the second indication information can also be understood as: the time point used to determine the data of the downlink service corresponding to the uplink data. For example, for the AIGC intelligent dialogue service, the second indication information is used to determine the time point for scheduling the first downlink packet in the AIGC intelligent dialogue service. Thus, the network device can determine the time point for scheduling the first downlink packet in the AIGC intelligent dialogue service based on the second indication information. For example, if the first time point determined by the network device based on the second indication information is the time point for scheduling the first downlink packet in the AIGC intelligent dialogue service, it is beneficial for the network device to send the PDCCH for scheduling the first downlink packet in the AIGC intelligent dialogue service to the terminal device based on the determined time point for scheduling the first downlink packet in the AIGC intelligent dialogue service.

[0165] Furthermore, the mechanism described in this paper is based on the AIGC intelligent dialogue service, but it is not limited to the AIGC intelligent dialogue service. All services with uplink and downlink correlation logic can be processed using the method provided in the embodiments of this application.

[0166] In another possible approach, the second indication information can also be understood as: time information used to indicate the arrival time of downlink services from the server to the network device. For example, the first time point indicated is the starting point of the downlink services arriving at the network device from the server, which is beneficial for the network device to send a PDCCH for scheduling downlink data transmission to the terminal device based on the time information indicated by the second indication information.

[0167] In one possible approach, the second indication information includes a first time point to directly indicate that first time point. In this approach, the network device determines the first time point based on the second indication information, which can be understood as obtaining the first time point by interpreting the second indication information.

[0168] In another possible approach, the second indication information includes the uplink data transmission time and the duration between the first time point and the uplink data transmission time, to indirectly indicate the first time point. The uplink data transmission time can be the transmission time of the last uplink data packet or the time when the network device successfully receives the last data packet. For example, if the terminal device sends a data packet at time Ta but fails to transmit it, and then retransmits the data packet at time Tb, and the network device successfully receives the data packet at time Tb, then the uplink data transmission time at this time is time Tb. Furthermore, the duration between the first time point and the uplink data transmission time can be represented by the term "duration".

[0169] When the second indication information includes the uplink data transmission time and the duration between the first time point and the uplink data transmission time, the network device determines the first time point based on the second indication information. This can be understood as follows: interpreting the second indication information to obtain the uplink data transmission time and the duration between the first time point and the uplink data transmission time; determining the first time point based on the uplink data transmission time and the duration between the first time point and the uplink data transmission time. The first time point is the time point at which the uplink data transmission time is delayed by the duration between the first time point and the uplink data transmission time. For example, if the uplink data transmission time is t1 and the duration between the first time point and the uplink data transmission time is m, then the first time point t2 is t1 + m.

[0170] It is evident that the second indication information can flexibly indicate the first time point through direct or indirect indication. Regardless of the method by which the second indication information is indicated, the network device can determine the first time point based on the second indication information from the terminal device, thereby reducing the processing complexity of the network device.

[0171] In one possible approach, the second indication information is carried in the media access control-control element (MAC CE). The MAC CE can be sent by the terminal device along with the last packet of uplink data to the network device, or it can be sent via other layer signaling, such as Layer 2 or Layer 3 signaling (e.g., radio resource control (RRC) signaling).

[0172] Furthermore, in the method where the network device determines the first time point based on the instruction from the terminal device, how the first time point indicated by the terminal device to the network device is determined is unknown to the network device. Therefore, the first time point indicated by the terminal device to the network device is associated with the uplink data transmission time or the uplink data arrival time, which is invisible to the network device. Alternatively, in the method where the network device determines the first time point through second instruction information, the first time point is associated with the uplink data transmission time or the uplink data arrival time, which is an optional implementation.

[0173] In one optional implementation, the network device may further send first configuration information to the terminal device, the first configuration information being used to indicate that the terminal device is allowed to activate the dynamic activation period function. Accordingly, the terminal device receives the first configuration information from the network device.

[0174] In this method, the network device instructs the terminal device to activate the dynamic activation period function through first configuration information. This allows the terminal device to activate the dynamic activation period function. For example, the terminal device can determine the time point for indicating the dynamic activation period, such as a first time point. This facilitates the terminal device in instructing the network device to indicate the determined first time point, which in turn allows the network device to send a PDCCH for scheduling data transmission to the terminal device during the dynamic activation period. This ensures that the terminal device can detect the PDCCH in a timely manner, such as after uplink data transmission. Furthermore, this method also helps the terminal device detect the PDCCH for scheduling data transmission during the dynamic activation period, enabling the terminal device to receive downlink data promptly upon arrival, reducing downlink service latency.

[0175] Implementation method 1.2: The network device determines the first time point on its own.

[0176] In one possible approach, when the network device determines that a dynamic activation period needs to be configured for the terminal device, it automatically determines the first time point. Optionally, the network device can determine whether a dynamic activation period needs to be configured for the terminal device based on the service type corresponding to the uplink data. For example, if the service type corresponding to the uplink data is a service with high latency requirements, it is determined that a dynamic activation period needs to be configured for the terminal device. In this approach, the network device needs to have the ability to identify the service type based on the uplink data. For example, if the network device has the ability to identify the service type as AIGC intelligent dialogue service based on the uplink data, then when the network device identifies that the service corresponding to its uplink data is AIGC intelligent dialogue service, since the latency requirements of the first downlink packet in AIGC intelligent dialogue service are high, it is determined that a dynamic activation period needs to be configured for the terminal device for AIGC intelligent dialogue service. Therefore, the network device can automatically determine the starting point (first time point) used to indicate the dynamic activation period.

[0177] Furthermore, the network device can determine the first time point in various ways, and this application embodiment does not limit this method. In one optional implementation, the network device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the arrival time of the uplink data, as the first time point. Therefore, the first time point is associated with the arrival time of the uplink data.

[0178] Specifically, the network device determines the arrival time of the associated downlink data based on the arrival time of the uplink data. For example, for the AGIC intelligent dialogue service, the network device estimates the earliest time when the associated downlink data arrives from the server, based on the arrival time of the uplink data and the processing time of the uplink data by the large model in the server. The processing time of the large model for the uplink data can be understood as the time between the input of the uplink data to the input of the downlink data. Furthermore, the processing time of the large model for the uplink data, or the time from the arrival of the uplink data to the arrival of the corresponding downlink data, can be a time pre-indicated by other devices, such as servers, core network devices, or terminal devices, or it can be a time determined by the network device through feature learning of the uplink service. Alternatively, the network device can receive the service characteristics of the service corresponding to the uplink data from other devices to determine the time from the arrival of the uplink data to the arrival of the associated downlink data. Business characteristics can include business type, business latency requirements, etc.

[0179] In this method, the network device can estimate the earliest arrival time of the associated downlink data from the server based on the arrival time of the uplink data. Therefore, the network device can send a PDCCH (Programmable Controller Communication) to the terminal device for scheduling data transmission based on the estimated earliest time. Thus, by determining the estimated earliest time as the first time point, the network device can promptly schedule downlink data transmission to the terminal device, which helps the terminal device to detect the PDCCH in a timely manner and receive the downlink data promptly upon arrival, reducing downlink service latency.

[0180] In an optional implementation, the terminal device further sends capability information to the network device, the capability information indicating that the terminal device has the capability to support a dynamic activation period. Correspondingly, the network device may also receive capability information from the terminal device. The dynamic activation period is as described above and will not be repeated here.

[0181] In this method, the terminal device can send capability information to the network device indicating that it has the ability to support dynamic activation periods, so that the network device knows that the terminal device has the ability to support dynamic activation periods. Therefore, the network device can independently determine the time point used to indicate that the terminal device is in a dynamic activation period, such as determining the first time point to indicate the dynamic activation period. Then, based on the dynamic activation period, the network device can send a PDCCH to the terminal device for scheduling data transmission, enabling timely scheduling of downlink data and reducing downlink service latency.

[0182] In one optional implementation, the network device may further determine a second time point, which is later than the first time point and is associated with the transmission time or arrival time of the uplink data. The association of the second time point with the transmission time or arrival time of the uplink data is similar to the association of the first time point with the transmission time or arrival time of the uplink data, and will not be elaborated further.

[0183] The network device can determine the second time point in various ways, and the embodiments of this application are not limited thereto. In one optional embodiment, in the case of embodiment 1.1 above, the second indication information is further used to indicate the second time point, so that the network device can determine the second time point based on the second indication information.

[0184] In one possible approach, the second indication information further includes a second time point to directly indicate that time point. In this approach, the network device can directly obtain the second time point by interpreting the second indication information.

[0185] In another possible approach, the second indication information also includes the duration between the second time point and the first time point to indirectly indicate the second time point. In this approach, the network device can obtain the duration between the second time point and the first time point by interpreting the second indication information, and then determine the second time point based on the determined first time point and the duration between the second time point and the first time point. Here, the second time point is the time point corresponding to the duration between the first and second time points after the first time point.

[0186] It is evident that the second indication information can also flexibly indicate the second time point through direct or indirect means, and regardless of the indication method used by the second indication information, the network device can determine the second time point based on the second indication information.

[0187] Therefore, if the network device determines a first time point based on the second indication information from the terminal device, and the second indication information also indicates a second time point, the network device can also determine a second time point based on the second indication information. In this method, the second time point is associated with the transmission time or arrival time of the uplink data, and is also invisible to the network device.

[0188] Furthermore, if the second indication information also indicates a second time point, it can be understood that: the indication information received by the network device from the terminal device indicates the time information of the downlink service arriving at the network device. The network device can determine the time range of the downlink data corresponding to the downlink service arriving at the network device based on the time information indicated by the terminal device, such as determining the earliest time point (first time point) and the latest time point (second time point) of the downlink data arriving at the network device. This allows the network device to send a PDCCH for scheduling data transmission to the terminal device based on the determined earliest and latest time points, ensuring that the downlink data is scheduled in a timely manner.

[0189] In another alternative implementation, the network device may also determine the second time point itself. For example, if the second indication information in Implementation 1.1 does not indicate a second time point, or if it is in Implementation 1.2, the network device may also determine the second time point itself.

[0190] The network device can determine the second time point in various ways, and this application embodiment does not limit this method. In one possible approach, the network device determines the second time point as the latest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the arrival time of the uplink data. Specifically, the network device estimates the latest time point at which the downlink data associated with the uplink data arrives at the network device from the server, based on the arrival time of the uplink data and the processing time of the uplink data by the large model in the server. Therefore, the second time point is associated with the arrival time of the uplink data. The processing time of the uplink data by the large model can be a duration pre-indicated to the network device by other devices, such as servers or core network devices, or it can be a duration determined by the network device through feature learning of the uplink service.

[0191] In this method, the network device can send a PDCCH for scheduling data transmission to the terminal device at the latest estimated latest time point. Therefore, the network device determines the estimated latest time point as a second time point so that it can send the PDCCH for scheduling data transmission to the terminal device between the first time point and the second time point, thereby reducing the power consumption of the network device.

[0192] Furthermore, if the network device also determines the second time point, it can be understood that the network device can determine the time range of downlink data arriving from the server based on the arrival time of uplink data. For example, it can determine the starting point of downlink data arriving from the server (the first time point) and the latest time point of downlink data arriving from the server (the second time point) to ensure that the terminal device is in the activation period when the downlink data arrives, such as in the dynamic activation period, so that the downlink data can be scheduled in a timely manner and the latency of downlink services can be reduced.

[0193] In an optional implementation, the network device may further send a first indication message to the terminal device, the first indication message being used to indicate a first time point. For example, if the network device determines the first time point itself, i.e., in the case of implementation 2 above, it may send the first indication message to the terminal device to indicate the determined first time point to the terminal device. This facilitates the terminal device in detecting the PDCCH based on the first time point, thereby enabling the terminal device to detect the PDCCH in a timely manner and reducing the latency of downlink services.

[0194] The first indication information can indicate the first time point in various ways, and this application embodiment does not limit this. In one possible way, the first indication information includes the first time point to directly indicate the first time point. In another possible way, the first indication information includes the arrival time of the uplink data and the duration between the arrival time of the uplink data and the first time point to indirectly indicate the first time point. It can be seen that the first indication information can flexibly indicate the first time point through direct or indirect indication.

[0195] In one possible approach, when the network device determines the second time point, the first indication information is also used to indicate the second time point, so as to indicate the second time point determined by the network device to the terminal device, so that the terminal device can also detect the PDCCH based on the second time point, which can reduce power consumption.

[0196] The first indication information can indicate the second time point in various ways, and this application embodiment does not limit this. In one possible way, the first indication information includes the second time point to directly indicate the second time point. In another possible way, the first indication information includes the duration between the second time point and the first time point to indirectly indicate the second time point. It can be seen that the first indication information can also flexibly indicate the first time point through direct or indirect indication.

[0197] In one possible approach, the first indication information can also be understood as: used to configure the dynamic activation period of the terminal device, thereby enabling the terminal device to determine the dynamic activation period based on the first indication information. For example, the first time point indicated by the first indication information can be used as the starting point of the dynamic activation period, which in turn enables the terminal device to detect the PDCCH used for scheduling data transmission during the dynamic activation period, so that the terminal device can detect the PDCCH in a timely manner and reduce the latency of downlink services.

[0198] In another possible approach, the first indication information can also be understood as: the time point at which the terminal device determines the detection time of the PDCCH used to schedule the downlink data associated with the uplink data. For example, for the AIGC intelligent dialogue service, the first indication information is used by the terminal device to determine the time point at which the PDCCH used to schedule the first downlink packet in the AIGC intelligent dialogue service is detected. This facilitates the terminal device in determining the time point at which the PDCCH used to schedule the first downlink packet in the AIGC intelligent dialogue service is detected based on the first indication information. For example, the first time point indicated by the first indication information can be used as the time point at which the PDCCH used to schedule the first downlink packet in the AIGC intelligent dialogue service is detected. This, in turn, facilitates the terminal device in detecting the PDCCH from the time point at which the PDCCH used to schedule the first downlink packet in the AIGC intelligent dialogue service is detected, so as to detect the PDCCH used to schedule the first downlink packet in the AIGC intelligent dialogue service in a timely manner, thereby reducing the latency of the first downlink packet in the AIGC intelligent dialogue service.

[0199] In one possible approach, the first indication information is carried in RRC signaling or Layer 2 (L2) control signaling. Alternatively, the network device can indicate a first time point, or a first time point and a second time point, to the terminal device via RRC signaling or L2 control signaling.

[0200] S802. The network device sends a PDCCH to the terminal device according to the first time point. The PDCCH is used to schedule data transmission.

[0201] In one optional implementation, the PDCCH sent by the network device to the terminal device is used to schedule the data transmission of downlink data associated with uplink data. Optionally, the PDCCH sent by the network device to the terminal device may also be used to schedule the data transmission of other data besides the downlink data associated with uplink data.

[0202] The first time point can be understood as the starting point of the dynamic activation period of the terminal device. The network device sends PDCCH to the terminal device according to the first time point, which can be: sending PDCCH to the terminal device at a time point later than the first time point, or sending PDCCH to the terminal device after the first time point, so that the terminal device can detect PDCCH during the dynamic activation period.

[0203] In one optional implementation, the network device sends a PDCCH to the terminal device based on a first time point, provided that a second time point has also been determined. This includes sending the PDCCH to the terminal device between the first and second time points.

[0204] In this method, the network device also determines a second time point, meaning the terminal device may be in a dynamic activation period between the first and second time points. Therefore, to ensure the terminal device detects the PDCCH in a timely manner, the network device sends the PDCCH to the terminal device between the first and second time points.

[0205] In an optional implementation, the network device may further receive second configuration information for service information. For example, the network device may receive second configuration information for service information from a server or core network device. The second configuration information includes a first PDB and a second PDB. The first PDB is used to schedule a first data packet, and the second PDB is used to schedule a second data packet. The first data packet is the first N data packets in the downlink data associated with the uplink data, and the second data packet is the data packet in the downlink data excluding the first N data packets, where N is a positive integer. Furthermore, the service information may be quality of service flow (QoS flow) information or service bearer information.

[0206] Therefore, when the network device is configured with the second configuration information, it sends a PDCCH to the terminal device according to the first time point, including: sending a PDCCH for scheduling the first data packet to the terminal device based on the first PDB according to the first time point, and sending a PDCCH for scheduling the second data packet to the terminal device based on the second PDB.

[0207] As can be seen, servers or core network equipment can configure PDBs for network devices to schedule different data packets. Thus, network devices schedule different data packets based on the constraints of different PDBs to meet the latency requirements of different data packets.

[0208] For example, the first data packet is the first downlink packet in the AIGC intelligent dialogue service, and the second data packet is a non-first downlink packet in the AIGC intelligent dialogue service. Then, the network device can send a PDCCH for scheduling the first downlink packet to the terminal device based on the configured first PDB, and send a PDCCH for scheduling the non-first downlink packet to the terminal device based on the configured second PDB, according to the first time point.

[0209] As can be seen, the network device can schedule the downlink first packet based on the constraints of the first PDB and schedule downlink non-first packets based on the constraints of the second PDB, thereby satisfying the latency requirements of the downlink first packet and downlink non-first packets respectively. In other words, the network device can ensure the timely transmission of the downlink first packet without increasing the transmission requirements of the downlink non-first packets. Furthermore, compared to configuring a PDB for AIGC intelligent dialogue services, such as configuring a PDB for AIGC intelligent dialogue services based on the latency requirements of the downlink first packet, this method reduces resource waste caused by the high latency requirements of the downlink first packet; and compared to configuring a PDB for AIGC intelligent dialogue services based on the latency requirements of downlink non-first packets, it reduces the probability of failing to meet the latency requirements of the downlink first packet.

[0210] Furthermore, the implementation method of scheduling different data packets based on different PDB constraints when the network device is configured with the second configuration information can be implemented independently of the communication method 100. In other words, the implementation method of scheduling different data packets based on different PDB constraints when the network device is configured with the second configuration information can be implemented independently of the communication method 100.

[0211] S803. The terminal device determines a first time point, which is associated with the uplink data transmission time or the uplink data arrival time.

[0212] The implementation method for the terminal device to determine the first time point is similar to that for the network device. For example, the terminal device can determine the first time point based on an instruction from the network device, or the terminal device can determine the first time point itself. The following details two implementation methods for the terminal device to determine the first time point:

[0213] Implementation method 2.1: The terminal device determines the first time point based on the instruction of the network device.

[0214] Based on the above implementation method 1.2, in the mode of automatically determining the first time point, the network device also sends first indication information to the terminal device to indicate the first time point. Therefore, the network device determines the first time point by: determining the first time point based on the first indication information.

[0215] In one optional implementation, when the first indication information includes a first time point, the terminal device determines the first time point based on the first indication information, which may be: obtaining the first time point based on the interpretation of the first indication information.

[0216] In another optional implementation, when the first indication information includes the duration between the second time point and the first time point, the terminal device determines the first time point based on the first indication information, including: obtaining the duration between the second time point and the first time point based on the interpretation of the first indication information; and determining the second time point based on the first time point and the duration between the second time point and the first time point. The second time point is the time point after the first time point, following the duration between the second time point and the first time point.

[0217] As can be seen, in this method, the terminal device determines the first time point based on the instruction from the network device, which reduces the complexity of the terminal device determining the first time point. Furthermore, in this method, how the first time point indicated by the network device to the terminal device is determined is unknown to the terminal device; therefore, the association between the first time point and the uplink data transmission time or arrival time is invisible to the terminal device. Alternatively, in the method where the terminal device determines the first time point through the instruction from the network device, associating the first time point with the uplink data transmission time or arrival time is an optional implementation.

[0218] Implementation method 2.2: The terminal device determines the first time point on its own.

[0219] In one possible approach, the terminal device determines the first time point when it determines that a dynamic activation period needs to be configured. Optionally, the terminal device can determine whether a dynamic activation period needs to be configured based on the service type corresponding to the uplink data. For example, if the service type corresponding to the uplink data is a service with high latency requirements, it is determined that a dynamic activation period needs to be configured. For instance, if the service type corresponding to the uplink data is AIGC intelligent dialogue service, since the latency requirements of the first downlink packet in AIGC intelligent dialogue service are high, it is determined that a dynamic activation period needs to be configured for AIGC intelligent dialogue service, and thus the terminal device can determine the starting point (first time point) used to indicate the dynamic activation period.

[0220] Furthermore, the terminal device can determine the first time point in various ways, and this application embodiment does not limit this method. In one optional method, the terminal device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the uplink data transmission time, as the first time point. Therefore, the first time point is associated with the uplink data transmission time.

[0221] Specifically, the terminal device estimates the earliest time when the downlink data associated with the uplink data arrives at the network device from the server, based on the uplink data transmission time and the processing time of the uplink data by the large model in the server. The processing time of the uplink data by the large model can be estimated by the terminal device based on previous statistics of the corresponding latency of uplink and downlink services.

[0222] In this method, the terminal device estimates the earliest time when the downlink data associated with the uplink data arrives at the network device from the server, based on the uplink data transmission time. The earliest time estimated by the terminal device may be the time when the network device begins sending the PDCCH used for scheduling downlink data. Therefore, the terminal device determines the estimated earliest time as the first time point, so that it can detect the PDCCH from this estimated earliest time point. This ensures that the terminal device can detect the PDCCH used for scheduling downlink data in a timely manner and receive the downlink data promptly upon its arrival, reducing downlink service latency.

[0223] In one alternative implementation, the terminal device may further determine a second time point, which is later than the first time point, and the second time point is associated with the uplink data transmission time or the uplink data arrival time.

[0224] The terminal device can determine the second time point in various ways, and this application embodiment does not limit this method. In an optional embodiment, in the above embodiment 1.2, where the first indication information is also used to indicate the second time point, the terminal device can determine the second time point based on the first indication information, which can reduce the processing complexity of the terminal device.

[0225] In one possible approach, the first indication information includes a second time point, which the terminal device can obtain by interpreting the first indication information. In another possible approach, the first indication information includes time information associated with the second time point, which the terminal device can obtain based on the first indication information, thereby determining the second time point. For example, if the first indication information includes a first time point and the duration between the second and first time points, the terminal device can interpret the first indication information to obtain the first time point and the duration between the second and first time points, and then determine the second time point as the time point between the first and second time points, postponing the first time point by the duration between the second and first time points.

[0226] Therefore, if the terminal device determines the first time point based on the first indication information from the network device, and the first indication information also indicates a second time point, then the terminal device can also determine the second time point based on the first indication information. In this method, the second time point and the uplink data transmission time point or uplink data arrival time point are also invisible to the terminal device.

[0227] In another alternative implementation, the terminal device may also determine the second time point itself. For example, in embodiment 2.1 above, if the first indication information does not indicate the second time point, or in embodiment 2.2 above, the network device may also determine the second time point itself.

[0228] The terminal device can determine the second time point in various ways, and this application embodiment does not limit this method. In one possible approach, the terminal device determines the second time point as the latest time point at which the downlink data associated with the uplink data, estimated based on the uplink data transmission time, arrives at the network device. Specifically, the terminal device estimates the latest time point from the server to the network device for the downlink data associated with the uplink data, based on the uplink data transmission time and the processing time of the large model on the server for the uplink data. Therefore, the second time point is associated with the uplink data transmission time. The processing time of the large model for the uplink data can be the processing time of the large model for the uplink data estimated by the terminal device.

[0229] In this method, the terminal device estimates the latest time that the downlink data associated with the uplink data will arrive at the network device from the server, based on the uplink data transmission time. The latest time estimated by the terminal device may be the time when the network device finishes sending the PDCCH used to schedule the downlink data. Therefore, the estimated latest time is determined as the second time point so that the PDCCH can be detected before the estimated latest time point, thereby reducing the power consumption of the terminal device.

[0230] S804. The terminal device starts detecting the PDCCH from the first time point.

[0231] In one optional implementation, the terminal device detects the PDCCH starting from the first time point, provided that a second time point has also been determined, including: detecting the PDCCH between the first time point and the second time point.

[0232] In this method, the terminal device also determines a second time point. The time period between the first time point and the second time point can be regarded as the dynamic activation period of the terminal device. The terminal device detects the PDCCH between the first time point and the second time point in order to detect the PDCCH used for scheduling data transmission in a timely manner, reduce the latency of downlink services, and also reduce the power consumption of the terminal device.

[0233] The terminal device can detect the PDCCH between the first and second time points in various ways, and this application embodiment does not limit this method. In one possible approach, the terminal device starts a timer at the first time point, and the duration of this timer is equal to the duration between the second and first time points. Thus, during the timer's duration, the terminal device is in an active state / active period and detects the PDCCH. This timer can also be called a dynamic activation timer, a temporary activation timer, or an additional activation timer, etc.

[0234] Furthermore, whether the terminal device is active before the first time point and / or after the second time point, and whether it detects the PDCCH, can be determined based on the configured DRX. Alternatively, whether the terminal device detects the PDCCH before the timer starts and / or after the timer expires can be determined based on the configured DRX. For example, the terminal device determines whether to detect the PDCCH based on the timers associated with the configured DRX. The timers associated with the DRX include, but are not limited to, at least one of the following: on duration timer, drx-inactivity, and drx-retransmission timer. Specifically, before the timer starts and / or after the timer expires, if the timers associated with the configured DRX of the terminal device are in the timing period, the terminal device detects the PDCCH; if none of the timers associated with the configured DRX of the terminal device are in the timing period, the terminal device does not detect the PDCCH to save power.

[0235] For example, if the configured drx-inactivity timer is in progress after the timer expires, the terminal device will continue to detect the PDCCH. As another example, if the configured on duration timer, drx-inactivity timer, and drx-retransmission timer all expire after the timer expires, the terminal device will stop detecting the PDCCH.

[0236] In another optional implementation, if the terminal device does not determine a second time point, it can start detecting the PDCCH from a first time point. This can be achieved by starting PDCCH detection from the first time point and stopping PDCCH detection upon detection, thereby reducing the power consumption of the terminal device. Alternatively, the terminal device can start a timer at the first time point and stop the timer upon PDCCH detection. However, whether the terminal device continues to detect the PDCCH after detection or after stopping the timer can be determined based on the configured DRX, and the implementation method can refer to the above description, which will not be repeated here.

[0237] In one optional implementation, the terminal device detects the PDCCH starting from a first time point, including: periodically detecting the PDCCH based on a first period, starting from the first time point. This method enables the terminal device to periodically detect the PDCCH during the dynamic activation period, reducing the power consumption of the terminal device.

[0238] In one possible approach, the duration of PDCCH detection in the first cycle and / or each first cycle can be pre-configured by the network device for the terminal device, for example, by the network device through RRC signaling or L2 control signaling.

[0239] In another possible approach, the duration of PDCCH detection in the first cycle and / or each first cycle can be determined by the terminal device itself. In this approach, the terminal device can also indicate the self-determined duration of PDCCH detection in the first cycle and / or each first cycle to the network device, so that the network device can determine the dynamic activation period of the terminal device based on the duration of PDCCH detection in the first cycle and / or each first cycle, and then schedule downlink data for the terminal device in a timely manner during the dynamic activation period.

[0240] For example, the first cycle is 20ms. The terminal device can dynamically control the activation period based on 20ms between the first and second time points. For instance, every 20ms after the first time point, the activation period can be controlled in a pattern of 1ms (activation) - 19ms (sleep) - 1ms (activation) - 19ms (sleep). This saves the power consumption of the terminal device in detecting the PDCCH between the first and second time points and does not cause a long downlink service delay.

[0241] For example, Figure 9 is a transmission schematic diagram. In Figure 9, the first time point and the second time point determined by the network device and the terminal device can be regarded as the start and end points of the dynamic activation period of the terminal device, respectively. Therefore, the network device can send a PDCCH for scheduling data transmission to the terminal device between the first time point and the second time point, and the terminal device can detect the PDCCH for scheduling data transmission between the first time point and the second time point. In Figure 9, the terminal device can periodically detect the PDCCH based on a first cycle between the first time point and the second time point to reduce power consumption between the first time point and the second time point. Furthermore, the dynamic activation period indicated by the first and second time points in Figure 9 is located in the inactive period of the DRX cycle, so the network device and the terminal device can transmit the PDCCH during the dynamic activation period within the inactive period of the DRX cycle, enabling the network device to schedule downlink data transmission in a timely manner and the terminal device to detect the PDCCH in a timely manner, reducing downlink service latency.

[0242] Furthermore, the relationship between the first and second time points in Figure 9 and the DRX period configured by the network device for the terminal device is an exemplary relationship. In addition, the first and second time points can both be within the first activation period controlled by the on duration timer, drx-inactivity timer, and drx-retransmission timer within the DRX period; or, the first time point can be within the first activation period and the second time point can be outside the first activation period; or, the first time point can be outside the first activation period and the second time point can be within the first activation period. Wherein, when both the first and second time points are within the first activation period, the dynamic activation period of the terminal device is within the first activation period; when the first time point is within the first activation period and the second time point is outside the first activation period, or when the first time point is outside the first activation period and the second time point is within the first activation period, a portion of the dynamic activation period of the terminal device is within the first activation period and another portion is outside the first activation period.

[0243] In one optional implementation, the terminal device may also periodically detect the PDCCH based on the second cycle, starting from a third time point. The third time point is the time when the terminal device first detects the PDCCH starting from the first time point. The third cycle may be pre-configured by the network device for the terminal device, or it may be determined by the terminal device itself.

[0244] This method enables the terminal device to determine the periodic dynamic activation period based on the second cycle, and then detect the PDCCH during the periodic dynamic activation period so that the terminal device can detect the PDCCH of the periodically scheduled downlink data in a timely manner, thereby reducing the latency of downlink services.

[0245] Furthermore, this application embodiment does not limit the execution order of S801 and S803. For example, S801 can be executed before S803, or S801 can be executed after S803. This application embodiment does not limit the execution order of S802 and S803. For example, S802 can be executed before S803, or S802 can be executed after S803.

[0246] As can be seen, in this embodiment, both the network device and the terminal device can determine the transmission time or arrival time of the uplink data, which is associated with and used to indicate the start point (first time point) of the dynamic activation period for the terminal device. Therefore, the network device sends a PDCCH for scheduling data transmission to the terminal device based on the start point of the dynamic activation period, and the terminal device starts detecting the PDCCH from the start point of the dynamic activation period. This ensures that the network device sends the PDCCH for scheduling data transmission to the terminal device in a timely manner, and the terminal device detects the PDCCH for scheduling data transmission in a timely manner, reducing downlink service latency.

[0247] In addition, this method introduces a dynamic activation period for the terminal device. Compared with the network device only being able to send the PDCCH for scheduling data transmission to the terminal device during the DRX activation period, and the terminal device only being able to detect the PDCCH for scheduling data transmission during the DRX activation period, this method can reduce the waiting time for the network device to send the PDCCH and reduce the latency of downlink services.

[0248] This application embodiment also takes the above-described communication method 100, in which the network device independently determines a first time point and instructs it to the terminal device, thereby allowing the terminal device to determine the first time point based on the instruction from the network device, as an example to propose an exemplary communication method 200. A schematic diagram of the interaction of this communication method 200 can be seen in Figure 10. As shown in Figure 10, its interaction process includes, but is not limited to:

[0249] S1001. The network device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device, based on the estimated arrival time of the uplink data, as the first time point.

[0250] In one implementation method, the network device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device based on the estimated arrival time of the uplink data as the first time point. This can be found in the implementation method 1.2 above, which describes the implementation method of the network device. It will not be repeated here.

[0251] In this method, the network device estimates the earliest arrival time of the associated downlink data from the server based on the arrival time of the uplink data. Therefore, the network device can send a PDCCH (Programmable Controller Communication) to the terminal device to schedule data transmission based on the estimated earliest time. Thus, the network device determines the estimated earliest time as the first time point, enabling it to promptly schedule downlink data transmission to the terminal device and reduce downlink service latency.

[0252] In an optional implementation, the network device may also receive capability information from the terminal device, which indicates that the terminal device has the capability to support dynamic activation periods. The implementation of this method can be found in the above implementation method 1.2, and will not be repeated here.

[0253] In one alternative implementation, the network device may further determine a second time point for indicating the end of the dynamic activation period. For example, the network device may determine the latest time point at which the downlink data associated with the uplink data arrives at the network device, based on the estimated arrival time of the uplink data, as the second time point. Specific implementation details can be found in Implementation 1.2 above and will not be repeated here.

[0254] S1002. The network device sends first indication information to the terminal device, the first indication information indicating a first time point. Correspondingly, the terminal device receives the first indication information from the network device.

[0255] The implementation method of the first instruction information can be found in the above implementation method 1.2, and will not be repeated here.

[0256] In one optional implementation, when the network device has determined a second time point, the first indication information can also be used to indicate the second time point. The implementation method where the first indication information indicates the second time point, and other implementation methods of the first indication information, can be found in implementation method 1.2 above, and will not be repeated here.

[0257] S1003. The terminal device determines the first time point based on the first instruction information.

[0258] The implementation method for determining the first time point based on the first indication information of the terminal device can be found in the above implementation method 2.1, and will not be repeated here.

[0259] S1004. The network device sends a PDCCH for scheduling data transmission to the terminal device according to the first time point.

[0260] S1005. The terminal device starts detecting the PDCCH from the first time point.

[0261] The implementation methods of S1004 and S1005 can be found in the implementation methods of S802 and S804 described above, and will not be repeated here.

[0262] As can be seen, in this method, the network device automatically determines the earliest arrival time of the downlink data associated with the uplink data, estimated based on the arrival time of the uplink data, as the first time point, and indicates this first time point to the terminal device. Thus, the terminal device determines the first time point based on the network device's indication. Furthermore, based on the first time point, the network device sends a PDCCH (Programmable Data Center Communication) for scheduling data transmission to the terminal device. The terminal device starts detecting the PDCCH from the first time point, ensuring that the network device sends the PDCCH for scheduling data transmission in a timely manner. This timely detection of the PDCCH by the terminal device reduces downlink service latency.

[0263] This application embodiment also takes the above-described communication method 100, in which the terminal device determines a first time point and instructs it to the network device, thereby allowing the network device to determine the first time point based on the terminal device's instruction, as an example to propose another exemplary communication method 300. The interaction diagram of this communication method 300 can be seen in Figure 11. As shown in Figure 11, its interaction process includes, but is not limited to:

[0264] S1101. The terminal device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device, based on the estimated uplink data transmission time, as the first time point.

[0265] In one implementation method, the terminal device determines the earliest time point at which the downlink data associated with the uplink data arrives at the network device based on the uplink data transmission time as the first time point. This can be found in the implementation method 2.2 above, which describes the implementation method of the terminal device. It will not be repeated here.

[0266] In this method, the terminal device estimates the earliest time when the downlink data associated with the uplink data arrives at the network device from the server, based on the uplink data transmission time. The earliest time estimated by the terminal device may be the time when the network device begins sending the PDCCH used for scheduling downlink data. Therefore, the terminal device determines the estimated earliest time as the first time point so that it can detect the PDCCH from this estimated earliest time point, thereby timely detecting the PDCCH used for scheduling downlink data and reducing downlink service latency.

[0267] In an optional implementation, the terminal device may also receive first configuration information from the network device. The first configuration information is used to indicate that the terminal device is allowed to start the function of dynamic activation period. The implementation of this function can be found in the above implementation 1.1, and will not be repeated here.

[0268] In an optional implementation, the terminal device may also determine a second time point to indicate the end of the dynamic activation period. For example, the terminal device may determine the latest time point at which the downlink data associated with the uplink data, estimated based on the uplink data transmission time, arrives at the network device as the second time point. Specific implementation details can be found in Implementation 2.2 above and will not be repeated here.

[0269] S1102. The terminal device sends second indication information to the network device, the second indication information being used to indicate a first time point. Correspondingly, the network device receives the second indication information from the terminal device.

[0270] The implementation method of the second instruction information can be found in the above implementation method 1.1, and will not be repeated here.

[0271] It is evident that when the terminal device determines the first time point on its own, it can indicate the determined first time point to the network device, so that the network device can determine the first time point based on the second indication information.

[0272] In one optional implementation, when the terminal device has determined the second time point, the second indication information can also be used to indicate the second time point. The implementation methods for using the second indication information to indicate the second time point, as well as other implementation methods for the second indication information, can be found in Embodiment 1.1 above, and will not be repeated here.

[0273] S1103. The network device determines the first time point based on the second instruction information.

[0274] The implementation method for determining the first time point based on the second indication information can be found in the above implementation method 1.1, and will not be repeated here.

[0275] S1104. The network device sends a PDCCH for scheduling data transmission to the terminal device according to the first time point.

[0276] S1105. The terminal device starts detecting the PDCCH from the first time point.

[0277] The implementation methods of S1104 and S1105 can be found in the implementation methods of S802 and S804 described above, and will not be repeated here.

[0278] As can be seen, in this method, the terminal device determines the earliest arrival time of the downlink data associated with the uplink data (based on the estimated uplink data transmission time) as the first time point and indicates this first time point to the network device. Therefore, the network device determines the first time point based on the terminal device's indication. Subsequently, the network device sends a PDCCH (Plan-Do-Check-Chat) for scheduling data transmission to the terminal device based on the first time point. The terminal device starts detecting the PDCCH from the first time point, ensuring that the network device promptly sends the PDCCH for scheduling data transmission. This timely detection of the PDCCH by the terminal device reduces downlink service latency.

[0279] This application also provides a communication method 400, and Figure 12 is a schematic flowchart of the communication method 400. The communication method 400 is described from the perspective of a network device. The communication method includes, but is not limited to, the following steps:

[0280] S1201. The network device determines a third PDB for scheduling downlink data associated with uplink data based on the transmission information of uplink data.

[0281] In one optional implementation, the uplink data transmission information includes at least one of the following: uplink data time information, uplink continuous data transmission amount, and uplink continuous data transmission duration.

[0282] The uplink data timing information can be indicated by the terminal device to the network device through indication information, and the uplink data timing information includes, but is not limited to, at least one of the following: a first duration, the waiting time of the uplink data in the terminal device's buffer, and the time of the uplink data arriving in the terminal device's buffer. The first duration is when the uplink data transmission duration is greater than the duration of the uplink preset PDB, and the uplink preset PDB can be a PDB configured by the core network equipment or network device for uplink services.

[0283] Furthermore, uplink continuous data refers to a set of continuous data within the uplink data generated by the terminal device. For example, in the AGIC intelligent dialogue service, the data packet corresponding to the uplink prompt can be considered a set of uplink continuous data. Uplink continuous data may not be transmitted continuously. For instance, if the communication link is time division duplex (TDD), the uplink time slots themselves may not be continuous. For example, in a 4:1 ratio, there is only one uplink time slot after every four downlink time slots, causing continuous uplink data to wait for uplink time slots during transmission, resulting in a discontinuity in physical time.

[0284] The association of upstream data with downstream data can be understood as follows: when both upstream and downstream data belong to the same business, the upstream data is associated with the downstream data; or it can be understood as follows: when downstream data is data that responds to upstream data, the upstream data is associated with that downstream data.

[0285] In one optional implementation, the network device determines a third PDB for scheduling downlink data associated with uplink data based on uplink data transmission information, including: determining, based on the uplink data transmission information, whether it is necessary to adjust the PDB for scheduling downlink data associated with uplink data based on a preset downlink PDB; if it is determined that it is necessary to adjust the PDB for scheduling downlink data based on the preset downlink PDB, determining a third PDB for scheduling downlink data based on the uplink data transmission information and the preset downlink PDB; if it is determined that it is not necessary to adjust the preset downlink PDB for scheduling, determining the preset downlink PDB as the third PDB.

[0286] In this method, the network device can dynamically adjust the PDB (Programmable Deposit Count) of downlink data associated with uplink data based on uplink data transmission information. For example, when the uplink data transmission delay does not exceed the preset uplink PDB, the network device uses the preset downlink PDB as the PDB for scheduling downlink data associated with uplink data; when the uplink data transmission delay exceeds the preset uplink PDB, the network device adjusts the PDB for scheduling downlink data associated with uplink data based on the preset downlink PDB. Thus, even when the uplink data transmission delay exceeds the preset uplink PDB, the sum of the uplink and downlink data transmission delays can be ensured to be within the service-allowed delay requirements, reducing the demand on uplink service transmission rates.

[0287] In one optional implementation, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the transmission information of the uplink data, including: receiving third indication information from a terminal device, the third indication information indicating the time information of the uplink data; and determining a third PDB for scheduling downlink data associated with the uplink data based on the time information of the uplink data.

[0288] In this method, the terminal device indicates the time information of the uplink data to the network device, so that the network device can determine the third PDB of the downlink data associated with the uplink data based on the time information of the uplink data indicated by the terminal device, so that the determined third PDB can meet the latency requirements of the service.

[0289] In one optional implementation, when the time information of the uplink data indicated by the third indication information includes a first duration, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the time information of the uplink data, including: determining the difference between the downlink preset PDB and the first duration as the third PDB for scheduling downlink data associated with the uplink data.

[0290] In this method, if the uplink data time information indicated by the third indication information includes a first duration, it means that the uplink data transmission duration exceeds the duration of the uplink preset PDB. Therefore, to ensure the total latency requirement of the service, the network device determines that it cannot directly use the downlink preset PDB as the PDB for scheduling downlink data. That is, it needs to adjust the downlink preset PDB to obtain a third PDB for scheduling downlink data. Specifically, the network device determines the difference between the downlink preset PDB and the first duration as the third PDB for scheduling the downlink data associated with the uplink data, ensuring that the sum of the uplink data transmission latency and the downlink data transmission latency is within the latency requirement allowed by the service.

[0291] For example, if both the uplink and downlink preset PDBs are 30ms, and the uplink data transmission duration is 50ms, then the terminal device indicates a first duration of 50-30=20ms to the network device via third indication information. Based on this first duration, the network device determines the third PDB for scheduling the downlink data associated with the uplink data as the difference between the downlink preset PDB and the first duration, i.e., the third PDB is 30-20=10ms. Therefore, the network device sends downlink data to the terminal device based on a 10ms latency budget, ensuring that the sum of the uplink and downlink transmission latency is within the allowed latency requirement (60ms). Conversely, if the network device directly determines the downlink preset PDB as the third PDB for scheduling the downlink data associated with the uplink data, the sum of the uplink data transmission latency (50ms) and the downlink data transmission latency (30ms) will exceed the allowed latency requirement (60ms).

[0292] In another optional implementation, where the uplink data time information indicated by the third indication information includes the waiting time of the uplink data in the terminal device's buffer, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data time information. This includes: if the waiting time is greater than the uplink preset PDB, determining the difference between the downlink preset PDB and the second duration as the third PDB for scheduling the downlink data associated with the uplink data. The second duration is equal to the difference between the waiting time and the uplink preset PDB.

[0293] In this method, when the uplink data time information indicated by the third indication information includes the waiting time of the uplink data in the terminal device's buffer, if the waiting time is greater than the uplink preset PDB, it indicates that the uplink data transmission time exceeds the requirement of the uplink preset PDB. Therefore, to ensure the total latency requirement of the service, the network device determines that the downlink preset PDB needs to be adjusted to obtain a third PDB for scheduling downlink data. Specifically, the network device subtracts the difference between the waiting time and the uplink preset PDB from the downlink preset PDB to obtain the third PDB, i.e., third PDB = downlink preset PDB - (waiting time - uplink preset PDB). This method can ensure that the sum of the uplink data transmission latency and the downlink data transmission latency is within the latency requirements allowed by the service.

[0294] For example, if both the uplink preset PDB and the downlink preset PDB are 30ms, and the waiting time for uplink data in the terminal device's buffer is 40ms, then the terminal device indicates to the network device via third indication information that the waiting time for uplink data in the buffer is 40ms. If the waiting time for uplink data in the terminal device's buffer is longer than the uplink preset PDB, then the network device determines the third PDB for scheduling the downlink data associated with the uplink data to be 30 - (40 - 30) = 20ms based on this waiting time. Furthermore, the network device sends downlink data to the terminal device based on a 20ms latency budget, ensuring that the sum of the uplink and downlink transmission latency is within the total allowed latency requirement of the service (60ms).

[0295] In another optional implementation, when the uplink data time information indicated by the third indication information includes the time when the uplink data arrives at the terminal device's buffer, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data time information. This includes: determining the waiting time of the uplink data in the buffer based on the time when the uplink data arrives at the terminal device's buffer and the arrival time of the uplink data at the network device; and if the waiting time is greater than the uplink preset PDB, determining the difference between the downlink preset PDB and the second duration as the third PDB for scheduling downlink data associated with the uplink data. The second duration is equal to the difference between the waiting time and the uplink preset PDB.

[0296] In this method, when the uplink data time information indicated by the third indication information includes the time when the uplink data arrives at the terminal device's buffer, the network device determines, based on the uplink data arrival time at the terminal device's buffer and the uplink data arrival time at the network device, that if the waiting time of the uplink data in the terminal device's buffer is greater than the uplink preset PDB, it indicates that the uplink data transmission delay exceeds the uplink preset PDB. Therefore, to ensure the total latency requirement of the service, the network device determines that the downlink preset PDB needs to be adjusted to obtain a third PDB for scheduling downlink data. Specifically, the network device determines that the third PDB equals the downlink preset PDB minus the second duration, and the second duration equals the waiting time minus the uplink preset PDB. This method ensures that the sum of the uplink latency requirement and the downlink latency requirement of the service remains within the allowable latency requirement of the service.

[0297] For example, if both the uplink preset PDB and the downlink preset PDB are 30ms, and the uplink data arrives at the terminal device's buffer at 10ms and at the network device at 50ms, then the uplink data arrival time indicated by the terminal device to the network device via the third indication information is that the uplink data arrives at the terminal device's buffer at 10ms. Therefore, the network device can determine that the uplink data wait time in the terminal device's buffer is 40ms, which is longer than the uplink preset PDB of 30ms, and thus further determines that the downlink preset PDB needs to be adjusted. Consequently, the network device determines that the third PDB used for scheduling downlink data = 30 - (40 - 30) = 20ms.

[0298] Optionally, if the network device waits for uplink data in the terminal device's buffer for a period of less than the uplink preset PDB, it may use the downlink preset PDB as the PDB for scheduling downlink data associated with the uplink data, that is, determine the downlink preset PDB as the third PDB.

[0299] In this method, when the waiting time of uplink data in the terminal device's buffer is less than the uplink preset PDB, it indicates that the transmission latency of the uplink data has not exceeded the requirement of the uplink preset PDB. Therefore, when the network device sends downlink data based on the downlink preset PDB, it can ensure that the sum of the uplink latency requirement and the downlink latency requirement of the service is within the allowable latency requirement of the service. Thus, determining that the third PDB used for scheduling downlink data is equal to the downlink preset PDB reduces the complexity of the network device re-determining the PDB used for scheduling downlink data.

[0300] In another optional implementation, when the uplink data transmission information includes the transmission volume of continuous uplink data, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data transmission information. This includes: if the transmission volume of continuous uplink data is greater than a first threshold, determining a first value as the third PDB for scheduling downlink data associated with the uplink data. The first value is less than a preset downlink PDB. The first value can be a fixed value predetermined by the network device or a fixed value pre-configured for the network device by other devices (such as core network devices). Furthermore, the first threshold can be predetermined by the network device or pre-configured for the network device by other devices.

[0301] In this method, when the transmission volume of continuous uplink data exceeds a first threshold, it indicates a large amount of uplink data, potentially causing uplink transmission latency to exceed the preset uplink PDB. Therefore, the network device determines that it needs to adjust the PDB of downlink data used for scheduling uplink data associations based on the preset downlink PDB to ensure that the sum of the uplink and downlink latency requirements is within the allowable latency requirements of the service. Specifically, the network device can set the PDB of downlink data used for scheduling uplink data associations to a value smaller than the preset downlink PDB, such as a first value. For example, in the AIGC intelligent dialogue service, both the preset uplink and downlink PDBs are 30ms. When the user input includes an image, the uplink data volume is large. Therefore, when the transmission volume of continuous uplink data exceeds the first threshold, the network device can set a first value (e.g., 10ms) smaller than 30ms as the PDB for scheduling the first downlink packet, thus ensuring that the sum of the uplink transmission latency and the first downlink packet transmission latency is within the allowable latency requirements of the AIGC intelligent dialogue service.

[0302] Optionally, if the amount of uplink continuous data transmission is less than or equal to a first threshold, the network device may determine the downlink preset PDB as the third PDB for scheduling the downlink data associated with the uplink data.

[0303] In this method, when the transmission volume of continuous uplink data is less than or equal to the first threshold, it indicates that the amount of uplink data may be small, and therefore the transmission delay of the uplink data may not exceed the uplink preset PDB. Therefore, the network device determines that it does not need to adjust the downlink preset PDB; that is, it can directly determine the downlink preset PDB as the third PDB used to schedule the downlink data associated with the uplink data, thus ensuring that the sum of the uplink and downlink delays of the service is within the allowable delay requirements of the service.

[0304] In another optional implementation, when the uplink data transmission information includes the transmission duration of continuous uplink data, the network device determines a third PDB for scheduling downlink data associated with the uplink data based on the uplink data transmission information, including: when the continuous duration of the continuous uplink data is greater than a second threshold, determining a second value as the third PDB for scheduling downlink data associated with the uplink data.

[0305] The second value is less than the downlink preset PDB. This second value can be a fixed value predetermined by the network device that is less than the downlink preset PDB, or it can be a fixed value pre-configured for the network device by other devices. Furthermore, the second threshold can be predetermined by the network device or pre-configured for the network device by other devices.

[0306] Optionally, the second value may be equal to or different from the first value mentioned above; this application does not limit this.

[0307] In this method, when the transmission duration of continuous uplink data exceeds a second threshold, it indicates that the uplink data transmission delay may exceed the uplink preset PDB. The network device then determines that it needs to adjust the PDB of the downlink data associated with the uplink data, based on the downlink preset PDB, to ensure that the sum of the uplink and downlink transmission delays is within the allowable delay requirements of the service. Specifically, the network device determines the PDB of the downlink data associated with the uplink data to be a value smaller than the downlink preset PDB, such as the second value.

[0308] Optionally, if the transmission duration of uplink continuous data is less than or equal to the second threshold, the network device may determine the downlink preset PDB as the third PDB for scheduling the downlink data associated with the uplink data.

[0309] In this method, when the transmission duration of continuous uplink data is less than or equal to the second threshold, it indicates that the transmission delay of the uplink data may not exceed the uplink preset PDB. Therefore, the network device determines that there is no need to adjust the downlink preset PDB; that is, it directly determines the downlink preset PDB as the PDB used to schedule the downlink data associated with the uplink data. This ensures that the sum of the uplink transmission delay and the downlink transmission delay of the service is within the allowable delay requirements of the service.

[0310] In summary, when a network device determines, based on uplink data transmission information, that the uplink data transmission delay exceeds or may exceed the uplink preset PDB, it determines that the downlink preset PDB needs to be adjusted to determine the PDB of the downlink data associated with the uplink data, thereby ensuring that the sum of the uplink and downlink data transmission delays is within the service-permitted delay requirements. Conversely, when a network device determines, based on uplink data transmission information, that the uplink data transmission delay does not exceed or may not exceed the uplink preset PDB, it determines that the downlink preset PDB does not need to be adjusted and can directly use the downlink preset PDB as the PDB for scheduling the downlink data associated with the uplink data, thus ensuring reliable downlink data transmission.

[0311] S1202. The network device sends downlink data to the terminal device based on the third PDB. Correspondingly, the terminal device receives the downlink data.

[0312] In this method, the network device sends downlink data to the terminal device based on the third PDB. This can be understood as the network device sending downlink data to the terminal device under the constraint of the third PDB to ensure the latency of downlink services.

[0313] In one optional implementation, the network device further receives second configuration information, which includes a first PDB. The first PDB is used to schedule the first data packet, which is the first N data packets in the downlink data, where N is a positive integer. Additionally, the second configuration information may be configured for the network device by a server or core network equipment; that is, the network device can receive second configuration information from a server or core network equipment.

[0314] Therefore, the network device can be configured to use a first PDB for scheduling the first N data packets in the downlink data. In this case, the network device determines a third PDB for scheduling the downlink data associated with the uplink data based on the uplink data transmission information, including: determining a third PDB for scheduling the first data packets associated with the uplink data based on the uplink data transmission information and the first PDB.

[0315] Specifically, when the network device is configured with a first PDB for scheduling the first N data packets (first data packets) in the downlink data, if it determines, based on the uplink data transmission information, that the uplink data transmission duration exceeds or may exceed the uplink preset PDB, then it determines that the first PDB needs to be adjusted to obtain a PDB for scheduling the first data packets. Alternatively, when the network device is configured with a first PDB for scheduling the first N data packets (first data packets) in the downlink data, it can treat the first PDB as the aforementioned downlink preset PDB, and thus, when it determines that the downlink preset PDB needs to be adjusted, it adjusts the first PDB to obtain a PDB for scheduling the first data packets.

[0316] For example, if the uplink data transmission information includes the transmission duration of continuous uplink data, and the transmission duration of continuous uplink data is greater than the second threshold, the network device determines that the first PDB needs to be adjusted to determine the PDB of the first data packet in the downlink data associated with the uplink data. For example, the network device determines the second value as the PDB of the first data packet in the downlink data.

[0317] Optionally, when the network device determines, based on the uplink data transmission information, that the uplink data transmission duration has not exceeded or may not exceed the uplink preset PDB, it does not adjust the first PDB, but directly uses the first PDB as the PDB for scheduling the first data packet in the downlink data, and then uses the first PDB to send the first data packet to the terminal device.

[0318] In one optional implementation, the second configuration information further includes a second PDB. The second PDB is used to schedule a second data packet, which is a data packet in the downlink data excluding the first N data packets.

[0319] In this method, the network device is also configured with a second PDB for scheduling the second data packet in the downlink data packets. In this mode, the network device can also send the second data packet to the terminal device based on the second PDB to ensure the transmission delay of the second data packet.

[0320] As can be seen, network devices can be configured to schedule different data packets in downlink data using PDBs, so that the network device can send different data packets in downlink data to the terminal device based on different PDBs to ensure the latency requirements of different data packets.

[0321] For example, the network device learns from the second configuration information that a first PDB is configured for scheduling the first downlink packet in the AIGC intelligent dialogue service, and a second PDB is configured for scheduling non-first downlink packets in the AIGC intelligent dialogue service. Then, when the network device determines, based on the uplink data transmission information, that the uplink data transmission duration exceeds or may exceed the preset uplink PDB, it adjusts the first PDB to obtain a third PDB for scheduling the first downlink packet, and sends the first downlink packet to the terminal device based on the third PDB. This ensures that the transmission delay of both the uplink data and the first downlink packet is within the total latency requirement of the AIGC intelligent dialogue service. When the network device determines, based on the uplink data transmission information, that the uplink data transmission delay does not exceed or may not exceed the preset uplink PDB, it does not need to adjust the first PDB; it directly designates the first PDB as the PDB for scheduling the first downlink packet and sends the first downlink packet to the terminal device based on the first PDB. Furthermore, since the transmission delay of non-first downlink packets is not affected by the uplink data transmission duration, the network device can directly send non-first downlink packets to the terminal device based on the second PDB.

[0322] As can be seen, in this embodiment, the PDB used by the network device to send downlink data to the terminal device is determined based on the transmission information of the uplink data associated with the downlink data. Compared with the network device directly using a preset downlink PDB, this method can ensure that the sum of the uplink data transmission delay and the downlink data transmission delay is within the service-allowed delay requirement even when the uplink data transmission delay exceeds the preset uplink PDB.

[0323] The following section further describes the corresponding device implementation scheme in relation to the technical solution described above.

[0324] To achieve the functions of the methods provided in the embodiments of this application, the terminal-side device and the network-side device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0325] Figure 13 is a schematic diagram of a communication device provided in this application. The device may include modules corresponding to the methods / operations / steps / actions described in any of the embodiments of communication methods 100 to 400. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0326] The communication device 1300 includes a communication unit 1301 and a processing unit 1302, used to implement the methods executed by the various devices in the foregoing embodiments. The communication unit 1301 is also called a transceiver unit, which includes a sending unit and a receiving unit. The sending unit is used to send signals, and the receiving unit is used to receive signals.

[0327] In one possible implementation, the device is, for example, a terminal device. Specifically, the processing unit 1302 is configured to determine a first time point, which is associated with the transmission time or arrival time of uplink data. The processing unit 1302 is also configured to detect the Physical Downlink Control Channel (PDCCH) starting from the first time point, the PDCCH being used to schedule data transmission.

[0328] The specific execution flow of the communication unit 1301 and the processing unit 1302 in this embodiment can be referred to the steps described by the terminal device in the previous method embodiment, as well as related descriptions, which will not be repeated here. In the communication method implemented by this device, the terminal device can detect the PDCCH used for scheduling data transmission from a first time point associated with the uplink data transmission time or the uplink data arrival time, so that the terminal device can detect the PDCCH in a timely manner and reduce the latency of downlink services.

[0329] In one possible implementation, the device is, for example, a network device. Specifically, processing unit 1302 is configured to determine a first time point, which is associated with the transmission time or arrival time of uplink data. Processing unit 1302 is further configured to send a Physical Downlink Control Channel (PDCCH) to a terminal device based on the first time point, the PDCCH being used to schedule data transmission.

[0330] The specific execution flow of the communication unit 1301 and the processing unit 1302 in this embodiment can be referred to the steps described by the network device in the previous method embodiment, as well as related descriptions, which will not be repeated here. In the communication method implemented by this device, the network device can send a PDCCH for scheduling data transmission to the terminal device according to a first time point associated with the transmission time or arrival time of the uplink data, so that the network device sends the PDCCH in a timely manner and reduces the latency of downlink services.

[0331] In one possible implementation, when the communication device is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, integrated circuit, or logic circuit integrated on the chip.

[0332] This application also provides a communication device 1400, as shown in Figure 14, which is a schematic diagram of another communication device. The communication device 1400 can be used to perform the steps executed by the terminal device or network device in the above method embodiments, and can be referred to the relevant descriptions in the above method embodiments.

[0333] The communication device 1400 includes a processor 1401. Optionally, the communication device 1400 may also include a memory 1402 and a transceiver 1403.

[0334] In one possible implementation, the processor 1401, memory 1402, and transceiver 1403 are connected via a bus, and the memory stores computer instructions. Optionally, the processor 1401 and memory 1402 can also be integrated together.

[0335] Optionally, the processing unit 1302 in the foregoing embodiments may specifically be the processor 1401 in this embodiment, therefore the specific implementation of the processor 1401 will not be described in detail. The communication unit 1301 in the foregoing embodiments may specifically be the transceiver 1403 in this embodiment, therefore the specific implementation of the transceiver 1403 will not be described in detail.

[0336] In this application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0337] In this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited to this. The memory in this application can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0338] This application provides another communication device, which includes a processor and an interface. Optionally, it also includes a memory, with the processor coupled to the memory, the processor being used to read and execute computer instructions stored in the memory to implement the communication methods as shown in the embodiments of communication methods 100 to 400.

[0339] This application also provides a communication system, which includes a terminal device and a network device. The terminal device is used to perform all or part of the steps performed by the terminal device in the preceding embodiments. The network device is used to perform all or part of the steps performed by the network device in the preceding embodiments. In another possible design, the system may further include other devices / functional network elements that interact with at least one of the terminal device and the network device.

[0340] This application provides a computer-readable storage medium. The computer-readable storage medium stores a program or instructions. When the instructions are executed on a communication device, the communication methods shown in the embodiments of communication methods 100 to 400 are implemented.

[0341] This application provides a computer program product. The computer program product includes instructions. When the instructions are executed on a communication device, they implement the communication methods shown in the embodiments of communication methods 100 to 400.

[0342] This application provides a chip or chip system including at least one processor and an interface, the interface and at least one processor being interconnected via a circuit, the at least one processor being used to run computer programs or instructions to perform communication methods as shown in the embodiments of communication methods 100 to 400.

[0343] The interfaces in the chip can be input / output interfaces, pins, or circuits, etc.

[0344] The aforementioned chip system can be a system on chip (SOC) or a baseband chip, etc. The baseband chip may include a processor, channel encoder, digital signal processor, modem and interface module, etc.

[0345] In one implementation, the chip or chip system described above in this application further includes at least one memory, which stores instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0346] The technical solutions provided in this application can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media, etc.

[0347] In this application, provided there is no logical contradiction, the various embodiments may reference each other. For example, the methods and / or terms between method embodiments may reference each other, the functions and / or terms between device embodiments may reference each other, and the functions and / or terms between device embodiments and method embodiments may reference each other.

[0348] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Determine the first time point, which is associated with the uplink data transmission time or the uplink data arrival time; Starting from the first time point, the Physical Downlink Control Channel (PDCCH) is detected, and the PDCCH is used to schedule data transmission.

2. The method according to claim 1, characterized in that, The method further includes: A second time point is determined, which is later than the first time point; The step of detecting PDCCH starting from the first time point includes: PDCCH is detected between the first time point and the second time point.

3. The method according to claim 2, characterized in that, Determining the first time point includes: Receive first indication information from a network device, the first indication information being used to indicate a first time point; Based on the first indication information, the first time point is determined.

4. The method according to claim 3, characterized in that, The first indication information is also used to indicate the second time point.

5. The method according to claim 2, characterized in that, Determining the first time point includes: The earliest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the transmission time of the uplink data, is determined as the first time point.

6. The method according to claim 2 or 5, characterized in that, Determining the second time point includes: The latest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the transmission time of the uplink data, is determined as the second time point.

7. The method according to claim 1, or 2, or 5, or 6, characterized in that, The method further includes: Send a second instruction message to the network device; The second indication information is used to indicate the first time point; or, the second indication information is used to indicate both the first time point and the second time point.

8. The method according to claim 3 or 4, characterized in that, The method further includes: The capability information is sent to the network device, which indicates that the terminal device has the capability to support a dynamic activation period.

9. The method according to any one of claims 5 to 7, characterized in that, The method further includes: The terminal device receives first configuration information from the network device, the first configuration information being used to indicate that the terminal device is allowed to initiate a dynamic activation period function.

10. The method according to any one of claims 1 to 9, characterized in that, The step of detecting PDCCH starting from the first time point includes: Starting from the first time point, PDCCH is periodically detected based on the first cycle.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Starting from the third time point, based on the second cycle, PDCCH is periodically detected; The third time point is the time point at which the PDCCH is detected.

12. A communication method, characterized in that, The method is applied to a network device, and the method includes: Determine the first time point, which is associated with the uplink data transmission time or the uplink data arrival time; Based on the first time point, a Physical Downlink Control Channel (PDCCH) is sent to the terminal device, and the PDCCH is used to schedule data transmission.

13. The method according to claim 12, characterized in that, The method further includes: A second time point is determined, which is later than the first time point; Sending PDCCH to the terminal device according to the first time point includes: Between the first time point and the second time point, a PDCCH is sent to the terminal device.

14. The method according to claim 13, characterized in that, Determining the first time point includes: Receive second indication information from the terminal device, the second indication information being used to indicate a first time point; Based on the second indication information, the first time point is determined.

15. The method according to claim 14, characterized in that, The second indication information is also used to indicate the second time point.

16. The method according to claim 13, characterized in that, Determining the first time point includes: The earliest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the arrival time of the uplink data, is determined as the first time point.

17. The method according to claim 13 or 16, characterized in that, Determining the second time point includes: The latest time point at which the downlink data associated with the uplink data arrives at the network device, estimated based on the arrival time of the uplink data, is determined as the second time point.

18. The method according to claim 16 or 17, characterized in that, The method further includes: Send a first indication message to the terminal device, the first indication message being used to indicate the first time point.

19. The method according to claim 18, characterized in that, The first indication information is also used to indicate the second time point.

20. The method according to claim 14 or 15, characterized in that, The method further includes: Send first configuration information to the terminal device, the first configuration information being used to indicate that the terminal device is allowed to activate the dynamic activation period function.

21. The method according to any one of claims 16 to 19, characterized in that, The method further includes: The terminal device receives capability information, which indicates that the terminal device has the capability to support a dynamic activation period.

22. The method according to any one of claims 12 to 21, characterized in that, The method further includes: Receive the second configuration information. The second configuration information includes a first data packet latency budget (PDB) and a second PDB. Wherein, the first PDB is used to schedule the first data packet, the second PDB is used to schedule the second data packet, the first data packet is the first N data packets in the downlink data associated with the uplink data, and the second data packet is the data packet in the downlink data excluding the first N data packets, where N is a positive integer; Sending PDCCH to the terminal device according to the first time point includes: Based on the first time point, a PDCCH for scheduling the first data packet is sent to the terminal device based on the first PDB, and a PDCCH for scheduling the second data packet is sent to the terminal device based on the second PDB.

23. A communication device, characterized in that, The communication device includes a module for performing the method according to any one of claims 1 to 11, or includes a module for performing the method according to any one of claims 12 to 22.

24. A communication device, characterized in that, The communication device includes a processor configured to perform the method according to any one of claims 1 to 11, or configured to perform the method according to any one of claims 12 to 22.

25. A chip, characterized in that, It includes at least one processor, the processor being configured to execute instructions to cause a communication device including the chip to perform a communication method as described in any one of claims 1 to 11, or to perform a communication method as described in any one of claims 12 to 22.

26. The chip according to claim 25, characterized in that, The chip also includes an interface circuit for receiving the executed instructions and transmitting them to the processor.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed on a communication device, implement the method according to any one of claims 1 to 11, or implement the method according to any one of claims 12 to 22.

28. A computer program product containing instructions, characterized in that, When the instructions are executed on the communication device, they implement the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 22.

Images