Communication method and apparatus

Abstract

The present application relates to the technical field of wireless communications, and provides a communication method and apparatus. The method comprises: a first entity of a terminal device receives first information from a first data radio bearer (DRB), wherein the first information is related to first data, and the first data belongs to the first DRB; and the first entity of the terminal device determines a first duration on the basis of the first information, wherein the first duration is a duration in which second data is expected to be transmitted, and the second data belongs to a second DRB. The first duration is used for determining delay information of a status report, and / or, the first duration is used for triggering sending of a status report. The first entity is a packet data convergence protocol (PDCP) entity corresponding to the second DRB, or, the first entity is a media access control (MAC) entity for processing the second data.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 4, 2023, with application number 202311134761.1 and invention name “A communication method and device”, and the Chinese patent application filed with the State Intellectual Property Office of China on March 30, 2024, with application number 202410385996.6 and invention name “A communication method and device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a communication method and device. Background Art

[0003] Currently, extended reality (XR) services can transmit multiple data streams, such as video, audio, and tactile data. When multiple streams coexist, synchronization is required. For example, when a user sees an image, the corresponding audio must also play within a certain timeframe. Otherwise, the audio and video will be out of sync, impacting the user experience.

[0004] In a wireless communication system, a terminal device can send a status report to a network device. The status report includes latency information of the data to be transmitted, so that the network device can allocate transmission resources to the terminal device based on the latency information to implement uplink scheduling.

[0005] However, the status report in the current technology may affect the synchronization between multiple streams of data.

[0006] Summary of the Invention

[0007] In order to solve the above technical problems, the present application provides a communication method and device, which can enable the delay information of the status report to trigger the status report more accurately or timely, thereby improving the possibility of synchronization between different data.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] On the first aspect, a communication method is provided, which can be executed by a first entity of a terminal device, or by a module (such as a processor, a chip, or a chip system, etc.) applied to the first entity. Below, the method is described by taking the first entity executing the method as an example. The method includes: the first entity of the terminal device receives first information from a first data radio bearer DRB. The first information is related to the first data, and the first data belongs to the first DRB. The first entity of the terminal device determines a first duration based on the first information. The first duration is the duration for which the second data is expected to be transmitted, and the second data belongs to the second DRB. The first duration is used to determine the delay information of the status report, and / or the first duration is used to trigger the sending of the status report.

[0010] For example, the first entity is a Packet Data Convergence Protocol (PDCP) entity corresponding to the second DRB.

[0011] For another example, the first entity is a media access control MAC entity that processes the second data.

[0012] In the present application, the first information is related to the first data, which can be understood as the first data being able to trigger the sending of the first information.

[0013] In the present application, the first duration is the duration during which the second data is expected to be transmitted. It can be understood that if the second data is transmitted within the first duration, the first data is synchronized with the second data.

[0014] That is, the first entity of the terminal device refers to the first information when determining the expected duration for transmission of the second data (i.e., the first duration). Since the first information is related to the first data in the first DRB, the first duration determined based on the first information takes the first data into account, avoiding consideration of the transmission delay of only a single data (i.e., the second data), thereby laying the foundation for synchronization between the first data and the second data.

[0015] For example, when the first duration is used to determine the delay information of the status report, since the first duration refers to the duration of the synchronization requirement between the first data and the second data, the delay information also takes into account the synchronization requirement of the second data, thereby improving the accuracy of the delay information and helping to achieve the effect of synchronization between the first data and the second data.

[0016] For another example, when the first duration is used to trigger the sending of the status report, since the first duration is based on the duration of the synchronization requirement between the first data and the second data, the triggering of the status report also takes into account the synchronization requirement of the second data, thereby improving the accuracy of the status report triggering and helping to achieve the effect of synchronization between the first data and the second data.

[0017] In one possible design, the first information indicates a second duration or a first moment. The starting moment of the second duration is the moment when the first data arrives at the Packet Data Convergence Protocol (PDCP) entity corresponding to the first DRB, and the first moment is the ending moment of the second duration. The second duration is used to determine the first duration.

[0018] In the present application, the second duration can be understood as, when the first data arrives at the PDCP entity corresponding to the first DRB, if the second data arrives at the PDCP entity corresponding to the second DRB and is transmitted within the second duration, then the first data is synchronized with the second data.

[0019] In the present application, the first moment can be understood as, when the first data arrives at the PDCP entity corresponding to the first DRB, if the second data arrives at the PDCP entity corresponding to the second DRB and is transmitted before the first moment, then the first data is synchronized with the second data.

[0020] That is, the first information can represent the synchronization requirement of the second data.

[0021] In a possible design, the first entity of the terminal device determines a first duration based on the first information, including: the first entity determines the duration of a first timer based on the first information. The start time of the first timer is the second moment, and the second moment is the moment when the second data arrives at the terminal device. Exemplarily, the second moment in this article takes the moment when the second data arrives at the PDCP entity corresponding to the second DRB as an example. The end time of the first timer is the first moment. The first entity determines the first duration based on the duration of the first timer. The start time of the first duration is the second moment, and the end time of the first duration is the end time of the first timer.

[0022] That is to say, the first entity updates the duration of the first timer based on the first information, and then determines the first duration based on the duration of the first timer. Since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the second data, the duration of the first timer determined based on the first information is a duration that takes into account the synchronization requirements between the first data and the second data. In the case where the first duration is determined based on the duration of the first timer, if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved.

[0023] In one possible design, the method further includes: the first entity starting a second timer in response to receiving the first information.

[0024] The first entity determines the first duration based on the first information, including: determining the first duration based on the value of the second timer. The end time of the second timer is the first time. The start time of the first duration is the second time, the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB; and the end time of the first duration is the end time of the second timer.

[0025] That is, the first entity starts the second timer in response to receiving the first information, and then determines the first duration based on the value of the second timer. Because the second duration or the first moment indicated by the first information can meet the synchronization requirements of the second data. In this way, the second timer is started based on the first information, and the duration of the second timer is a duration that takes into account the synchronization requirements between the first data and the second data. When the first duration is determined based on the value of the second timer, if the second data is transmitted within the first duration, the first data and the second data can be synchronized.

[0026] In one possible design, the first entity of the terminal device determines the first duration based on the first information, including: determining the first duration based on the first information and second information; wherein the second information indicates the moment when the second data is discarded.

[0027] That is to say, the first entity refers to both the first information and the second information in the process of determining the first duration. When the first information is used to determine the first duration, since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the second data, when the first duration is determined based on the first information, if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved. Moreover, when the second information is used to determine the first duration, since the moment indicated by the second information can enable the first entity to know the transmission delay requirements of the second data, when the first duration is determined based on the second information, if the second data is transmitted within the first duration, the transmission delay requirements of the second data can be met.

[0028] In one possible design, the second information comes from a network device.

[0029] That is, the time indicated by the second information is configured by the network device.

[0030] In one possible design, the starting moment of the first duration is the second moment, and the second moment is the moment when the second data arrives at the PDCP entity corresponding to the second DRB.

[0031] When the first moment is earlier than the discarding moment, the end moment of the first duration is the first moment; or when the discarding moment is earlier than or equal to the first moment, the end moment of the first duration is the discarding moment. It can be understood that the end time of the first duration is the earlier of the first moment and the discarding moment, thereby meeting the synchronization and transmission delay requirements of the second data.

[0032] In one possible design, the first entity of the terminal device determines the first duration based on the first information and the second information, including: the first entity determines the duration of the first timer based on the first information and the second information. The start time of the first timer is the second moment, and the second moment is the moment when the second data arrives at the PDCP entity corresponding to the second DRB; when the first moment is earlier than the moment of discarding, the end time of the first timer is the first moment; or, when the moment of discarding is earlier than or equal to the first moment, the end time of the first timer is the moment of discarding. The first entity determines the first duration based on the duration of the first timer. The start time of the first duration is the second moment, and the end time of the first duration is the end time of the first timer.

[0033] That is to say, the first entity updates the duration of the first timer based on the first information and the second information, and then determines the first duration based on the duration of the first timer. Since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the second data, and the moment indicated by the second information can enable the first entity to know the transmission delay requirements of the second data, the duration of the first timer determined based on the first information and the second information takes into account both the synchronization requirements between the first data and the second data and the transmission delay requirements of the second data. In the case of determining the first duration based on the duration of the first timer, if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved, and the transmission delay requirements of the second data can be met.

[0034] In one possible design, the method further includes: the first entity of the terminal device starts a second timer in response to receiving the first information.

[0035] The first entity of the terminal device determines the first duration based on the first information and the second information, including: determining the first duration based on the value of the first timer and the value of the second timer; or determining the first duration based on the end time of the first timer and the end time of the second timer. The start time of the first timer is the second time, the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB; the end time of the first timer is the time of discarding. The end time of the second timer is the first time. The starting time of the first duration is the second time; when the first time is earlier than the time of discarding, the end time of the first duration is the end time of the second timer, or when the time of discarding is earlier than or equal to the first time, the end time of the first duration is the end time of the first timer.

[0036] That is, in response to receiving the first information, the first entity starts the second timer and then determines the first duration based on the values ​​of the first timer and the second timer, or determines the first duration based on the end time of the first timer and the end time of the second timer. Because the second duration or the first time indicated by the first information can meet the synchronization requirements of the second data, the second timer is started based on the first information, and the duration of the second timer is a duration that takes into account the synchronization requirements between the first and second data. Furthermore, the time indicated by the second information enables the first entity to know the transmission delay requirements of the second data. Therefore, the first timer is started based on the second information, and the duration of the first timer is a duration that takes into account the transmission requirements of the second data. When the first duration is determined based on the values ​​of the first timer and the second timer, or when the first duration is determined based on the end time of the first timer and the end time of the second timer, if the second data is transmitted within the first duration, the first data is synchronized with the second data and the transmission delay requirements of the second data are met.

[0037] In one possible design, the start time of the second timer is the reception time of the first information.

[0038] In one possible design, the first timer is a packet loss timer.

[0039] In one possible design, when the first duration is used to determine delay information of the status report, the method further includes: the terminal device sending the status report through a media access control MAC entity. The MAC entity is used to process the second data.

[0040] For example, the status report is a Delay Status Report DSR.

[0041] Since the first duration refers to the duration required for synchronization between the first data and the second data, the delay information determined based on the first duration also takes into account the synchronization requirements of the second data. In other words, the terminal device can report "delay information that takes into account the synchronization requirements between different data" to the network device. Accordingly, if the network device schedules transmission resources for the terminal device based on the delay information so that the second data is transmitted within the first duration, the first data is synchronized with the second data, which helps to improve the user experience.

[0042] In one possible design, the delay information of the status report includes a remaining transmission delay budget, where the remaining transmission delay budget is determined based on the first duration.

[0043] In one possible design, the starting time of the remaining transmission delay budget is: the sending time of the status report. The ending time of the remaining transmission delay budget is: the ending time of the first duration.

[0044] In one possible design, the method further includes: the terminal device receiving a first threshold from the network device. The first duration is used to trigger the sending of the status report, including: when the remaining transmission delay budget determined by the first duration is less than or equal to the first threshold, the first duration is used to trigger the sending of the status report, and the remaining transmission delay budget determined by the first duration is the remaining transmission delay budget of the first data.

[0045] Because the first duration is based on the duration required for synchronization between the first data and the second data, the terminal device promptly sends a status report to the network device when the remaining transmission delay budget determined based on the first duration is less than or equal to the first threshold. In this way, the network device can promptly schedule transmission resources for the terminal device based on the status report, so that the second data can be transmitted within the first duration as much as possible, thereby achieving synchronization between the first data and the second data, which helps to improve the user experience.

[0046] On the second aspect, a communication method is provided, which can be executed by a second entity of a terminal device, or by a module (such as a processor, a chip, or a chip system, etc.) applied to the second entity. Below, the method is described by taking the second entity executing the method as an example. The method includes: the second entity of the terminal device sends first information. The first information is related to the first data, and the first data belongs to the first data radio bearer DRB. The first information is used to determine a first duration, which is the duration for which the second data is expected to complete transmission, and the second data belongs to the second DRB.

[0047] For example, the second entity is a Packet Data Convergence Protocol (PDCP) entity corresponding to the first DRB.

[0048] That is to say, the second entity of the terminal device sends the first information so that the receiving entity of the first information determines the first duration, that is, the duration in which the second data is expected to be transmitted. Since the first information is related to the first data in the first DRB, the first duration determined based on the first information takes the first data into account, avoiding considering only the transmission delay of a single data (that is, the second data), and laying the foundation for the synchronization of the first data and the second data. For example, if the second data is transmitted within the first duration, the first data is synchronized with the second data, achieving the effect of synchronization between different data.

[0049] In one possible design, the first information indicates a second duration or a first moment. The starting moment of the second duration is the moment when the first data arrives at the Packet Data Convergence Protocol (PDCP) entity corresponding to the first DRB, and the first moment is the ending moment of the second duration. The second duration is used to determine the first duration.

[0050] In one possible design, the method further includes: the second entity of the terminal device starting a third timer in response to receiving the first data, wherein the duration of the third timer is the second duration, or the end time of the third timer is the first time.

[0051] That is, the reception of the first data can trigger the start or restart of the third timer, and the duration of the third timer or the end time of the third timer can represent the synchronization requirement of the second data.

[0052] In one possible design, the start time of the third timer is the time when the first data arrives at the PDCP entity corresponding to the first DRB.

[0053] In one possible design, the method further includes: the second entity of the terminal device receiving first indication information. The first indication information is used to indicate starting or restarting a third timer. The duration of the third timer is the second duration, or the end time of the third timer is the first time.

[0054] That is, the second entity may start or restart the third timer according to the first indication information. The duration of the third timer or the end time of the third timer may represent the synchronization requirement of the second data.

[0055] In one possible design, the second entity of the terminal device sends the first information, including: sending the first information according to the first indication information.

[0056] That is to say, the first indication information can trigger the sending of the first information.

[0057] In one possible design, the method further includes: the terminal device receives configuration information, and the configuration information is used to configure the duration of the third timer to be the second duration.

[0058] That is, the duration of the third timer can be configured by the network device.

[0059] In one possible design, the first DRB and the second DBR are the same DRB.

[0060] In a third aspect, a communication method is provided. The method can be performed by a sixth entity of a terminal device, or by a module (e.g., a processor, a chip, or a chip system) applied to the sixth entity. The sixth entity can be a Packet Data Convergence Protocol (PDCP) entity. The following describes the method using the sixth entity as an example. The method includes:

[0061] Obtain third information, where the third information is related to third data, and the third data belongs to a third data wireless bearer DRB; determine a fourth duration based on the third information, where the fourth duration is the duration for which the fourth data is expected to be transmitted, and the fourth data belongs to the third DRB; the fourth duration is used to determine the delay information of the status report, and / or the fourth duration is used to trigger the sending of the status report.

[0062] That is, in determining the expected duration for transmission of the fourth data (i.e., the fourth duration), the third information is referenced. Since the third information is related to the third data in the third DRB, the fourth duration determined based on the third information takes the third data into account, avoiding consideration of the transmission delay of only a single data (i.e., the fourth data), thereby laying the foundation for synchronization between the third data and the fourth data.

[0063] For example, when the fourth time duration is used to determine the delay information of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the delay information also takes into account the synchronization requirement of the fourth data, thereby improving the accuracy of the delay information and helping to achieve the effect of synchronization between the third data and the fourth data.

[0064] For another example, when the fourth time duration is used to trigger the sending of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the triggering of the status report also takes into account the synchronization requirements of the fourth data, thereby improving the accuracy of the status report triggering and helping to achieve the effect of synchronization between the third data and the fourth data.

[0065] In one possible design, the third information indicates a third duration or a third moment; wherein, the starting moment of the third duration is the moment when the third data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the third DRB, and the third moment is the end moment of the third duration; the third duration is used to determine the fourth duration.

[0066] In one possible design, the fourth duration is determined according to the third information, including: determining the duration of the fifth timer according to the third information; wherein the start time of the fifth timer is the fourth moment, and the fourth moment is the moment when the fourth data arrives at the PDCP entity corresponding to the third DRB; the end time of the fifth timer is the third moment; determining the fourth duration according to the duration of the fifth timer; wherein the start time of the fourth duration is the fourth moment, and the end time of the fourth duration is the end time of the fifth timer.

[0067] Because the third duration or the third moment indicated by the third information can satisfy the synchronization requirement of the fourth data, the duration of the fifth timer determined based on the third information is a duration that takes into account the synchronization requirements between the third data and the fourth data. When the fourth duration is determined based on the duration of the fifth timer, if the fourth data is transmitted within the fourth duration, synchronization between the third data and the fourth data is achieved.

[0068] In one possible design, determining the fourth duration based on the third information includes: determining the fourth duration based on the third information and fourth information; wherein the fourth information indicates the moment when the fourth data is discarded.

[0069] That is to say, the sixth entity refers to both the third information and the fourth information in the process of determining the fourth duration. When the third information is used to determine the fourth duration, since the third duration or the third moment indicated by the third information can meet the synchronization requirements of the fourth data, when the fourth duration is determined based on the third information, if the fourth data is transmitted within the fourth duration, the third data can be synchronized with the fourth data. Moreover, when the fourth information is used to determine the fourth duration, since the moment indicated by the fourth information can enable the sixth entity to know the transmission delay requirements of the fourth data, when the fourth duration is determined based on the fourth information, if the fourth data is transmitted within the fourth duration, the transmission delay requirements of the fourth data can be met.

[0070] In one possible design, the starting moment of the fourth duration is the fourth moment, and the fourth moment is the moment when the fourth data arrives at the PDCP entity corresponding to the third DRB; when the third moment is earlier than the moment when the fourth data is discarded, the end moment of the fourth duration is the third moment; or, when the moment when the fourth data is discarded is earlier than or equal to the third moment, the end moment of the fourth duration is the moment when the fourth data is discarded.

[0071] In one possible design, the fourth duration is determined according to the third information and the fourth information, including: determining the duration of a fifth timer according to the third information and the fourth information; wherein, the start time of the fifth timer is the fourth moment, and the fourth moment is the moment when the fourth data arrives at the PDCP entity corresponding to the third DRB; when the third moment is earlier than the moment when the fourth data is discarded, the end time of the fifth timer is the third moment; or, when the moment when the fourth data is discarded is earlier than or equal to the third moment, the end time of the fifth timer is the moment when the fourth data is discarded; determining the fourth duration according to the duration of the fifth timer; wherein, the start time of the fourth duration is the fourth moment, and the end time of the fourth duration is the end time of the fifth timer.

[0072] That is, the sixth entity updates the duration of the fifth timer based on the third information and the fourth information, and then determines the fourth duration based on the duration of the fifth timer. Since the third duration or the third moment indicated by the third information can meet the synchronization requirement of the fourth data, and the moment indicated by the fourth information can enable the sixth entity to know the transmission delay requirement of the fourth data, the duration of the fifth timer determined based on the third information and the fourth information takes into account both the synchronization requirement between the third data and the fourth data and the transmission delay requirement of the fourth data. When the fourth duration is determined based on the duration of the fifth timer, if the fourth data is transmitted within the fourth duration, the third data can be synchronized with the fourth data and the transmission delay requirement of the fourth data can be met.

[0073] In one possible design, the fifth timer is a packet loss timer.

[0074] In one possible design, obtaining the third information includes: starting a fourth timer in response to receiving the third data; determining the third information based on the fourth timer; wherein the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time.

[0075] That is, the fourth timer can be understood as a synchronization timer to indicate the duration of the synchronization requirement between the third data and the fourth data.

[0076] In one possible design, the start time of the fourth timer is the time when the third data arrives at the PDCP entity corresponding to the third DRB.

[0077] In one possible design, the third information includes fifth information, the third data includes fifth data, the fourth data includes sixth data, and the fourth duration includes sixth duration.

[0078] In a fourth aspect, a communication method is provided. The method can be performed by a seventh entity of a terminal device, or by a module (e.g., a processor, a chip, or a chip system) applied to the seventh entity. The seventh entity can be a media access control (MAC) entity. The following description uses the seventh entity performing the method as an example, and the method includes:

[0079] Obtain second indication information, where the second indication information indicates a fourth duration, and the fourth duration is determined based on third information, the third information is related to third data, and the third data belongs to a third data radio bearer DRB; the fourth duration is the duration for which the fourth data is expected to be transmitted; determine the delay information of the status report based on the fourth duration, and / or trigger the sending of the status report based on the fourth duration.

[0080] That is, the fourth duration (i.e., the duration during which the fourth data is expected to be transmitted) refers to the duration determined by the third information. Since the third information is related to the third data in the third DRB, the fourth duration determined based on the third information takes the third data into account, avoiding consideration of the transmission delay of only a single data (i.e., the fourth data), thereby laying the foundation for synchronization between the third data and the fourth data.

[0081] For example, when the fourth time duration is used to determine the delay information of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the delay information also takes into account the synchronization requirement of the fourth data, thereby improving the accuracy of the delay information and helping to achieve the effect of synchronization between the third data and the fourth data.

[0082] For another example, when the fourth time duration is used to trigger the sending of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the triggering of the status report also takes into account the synchronization requirements of the fourth data, thereby improving the accuracy of the status report triggering and helping to achieve the effect of synchronization between the third data and the fourth data.

[0083] In one possible design, the delay information of the status report includes a remaining transmission delay budget, where the remaining transmission delay budget is determined based on the fourth duration.

[0084] In one possible design, the starting time of the remaining transmission delay budget is: the sending time of the status report; the ending time of the remaining transmission delay budget is: the ending time of the fourth duration.

[0085] In one possible design, the fourth data belongs to the third DRB, or the DRB to which the fourth data belongs is different from the third DBR.

[0086] In one possible design, the method also includes: receiving a first threshold from a network device; triggering the sending of the status report according to the fourth duration, including: determining a remaining transmission delay budget based on the fourth duration, and triggering the sending of the status report when the remaining transmission delay budget is less than or equal to the first threshold, the remaining transmission delay budget being the remaining transmission delay budget of the fourth data.

[0087] Because the fourth duration is based on the duration required for synchronization between the third data and the fourth data, the terminal device promptly sends a status report to the network device when the remaining transmission delay budget determined based on the fourth duration is less than or equal to the first threshold. In this way, the network device can promptly schedule transmission resources for the terminal device based on the status report, so that the fourth data can be transmitted within the fourth duration as much as possible, thereby achieving synchronization between the third data and the fourth data, which helps to improve the user experience.

[0088] In one possible design, the third information includes fifth information, the third data includes fifth data, the fourth data includes sixth data, and the fourth duration includes sixth duration.

[0089] In a fifth aspect, a communication method is provided. The method can be performed by a seventh entity of a terminal device, or by a module (e.g., a processor, a chip, or a chip system) applied to the seventh entity. The seventh entity can be a media access control (MAC) entity. The following description uses the seventh entity performing the method as an example. The method includes:

[0090] Receive third information, where the third information is related to third data, and the third data belongs to a third data radio bearer DRB; determine a fourth duration based on the third information, where the fourth duration is the duration for which the fourth data is expected to be transmitted; determine delay information of the status report based on the fourth duration, and / or trigger the sending of the status report based on the fourth duration.

[0091] That is, in determining the expected duration for transmission of the fourth data (i.e., the fourth duration), the third information is referenced. Since the third information is related to the third data in the third DRB, the fourth duration determined based on the third information takes the third data into account, avoiding consideration of the transmission delay of only a single data (i.e., the fourth data), thereby laying the foundation for synchronization between the third data and the fourth data.

[0092] For example, when the fourth time duration is used to determine the delay information of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the delay information also takes into account the synchronization requirement of the fourth data, thereby improving the accuracy of the delay information and helping to achieve the effect of synchronization between the third data and the fourth data.

[0093] For another example, when the fourth time duration is used to trigger the sending of the status report, since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, the triggering of the status report also takes into account the synchronization requirements of the fourth data, thereby improving the accuracy of the status report triggering and helping to achieve the effect of synchronization between the third data and the fourth data.

[0094] In one possible design, the third information indicates a third duration or a third moment; wherein, the starting moment of the third duration is the moment when the third data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the third DRB, and the third moment is the end moment of the third duration; the third duration is used to determine the fourth duration.

[0095] In one possible design, determining the fourth duration based on the third information includes: determining the fourth duration based on the third information and fourth information; wherein the fourth information indicates the moment when the fourth data is discarded.

[0096] That is to say, the seventh entity refers to both the third information and the fourth information in the process of determining the fourth duration. When the third information is used to determine the fourth duration, since the third duration or the third moment indicated by the third information can meet the synchronization requirements of the fourth data, when the fourth duration is determined based on the third information, if the fourth data is transmitted within the fourth duration, the third data can be synchronized with the fourth data. Moreover, when the fourth information is used to determine the fourth duration, since the moment indicated by the fourth information can enable the seventh entity to know the transmission delay requirements of the fourth data, when the fourth duration is determined based on the fourth information, if the fourth data is transmitted within the fourth duration, the transmission delay requirements of the fourth data can be met.

[0097] In one possible design, the starting moment of the fourth duration is the fourth moment, and the fourth moment is the moment when the fourth data arrives at the PDCP entity corresponding to the third DRB; when the third moment is earlier than the moment when the fourth data is discarded, the end moment of the fourth duration is the third moment; or, when the moment when the fourth data is discarded is earlier than or equal to the third moment, the end moment of the fourth duration is the moment when the fourth data is discarded.

[0098] In one possible design, the third information is determined based on a fourth timer, wherein the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time.

[0099] That is, the fourth timer can be understood as a synchronization timer to indicate the duration of the synchronization requirement between the third data and the fourth data.

[0100] In one possible design, the start time of the fourth timer is the time when the third data arrives at the PDCP entity corresponding to the third DRB.

[0101] In one possible design, the delay information of the status report includes a remaining transmission delay budget, where the remaining transmission delay budget is determined based on the fourth duration.

[0102] In one possible design, the starting time of the remaining transmission delay budget is: the sending time of the status report; the ending time of the remaining transmission delay budget is: the ending time of the first duration.

[0103] In one possible design, the method also includes: receiving a first threshold from a network device; triggering the sending of the status report according to the fourth duration, including: determining a remaining transmission delay budget based on the fourth duration, and triggering the sending of the status report when the remaining transmission delay budget is less than or equal to the first threshold, the remaining transmission delay budget being the remaining transmission delay budget of the fourth data.

[0104] Because the fourth duration is based on the duration required for synchronization between the third data and the fourth data, the terminal device promptly sends a status report to the network device when the remaining transmission delay budget determined based on the fourth duration is less than or equal to the first threshold. In this way, the network device can promptly schedule transmission resources for the terminal device based on the status report, so that the fourth data can be transmitted within the fourth duration as much as possible, thereby achieving synchronization between the third data and the fourth data, which helps to improve the user experience.

[0105] In one possible design, the fourth data belongs to the third DRB, or the DRB to which the fourth data belongs is different from the third DBR.

[0106] In one possible design, the third information includes fifth information, the third data includes fifth data, the fourth data includes sixth data, and the fourth duration includes sixth duration.

[0107] In a sixth aspect, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the methods, which can be implemented through hardware, software, or hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions.

[0108] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module may be configured to implement the processing functionality of any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively configured to implement the receiving functionality and the transmitting functionality of any of the above aspects and any possible implementations thereof.

[0109] In some possible designs, the transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0110] In a seventh aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method described in any one of the aspects.

[0111] In an eighth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instruction so that the communication device executes the method described in any aspect.

[0112] In a ninth aspect, a communication device is provided, comprising: at least one processor; the processor is configured to execute a computer program or instruction stored in a memory, so that the communication device performs the method described in any one of the aspects. The memory may be coupled to the processor, or may be independent of the processor.

[0113] In a tenth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the aspects.

[0114] In an eleventh aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to perform the method described in any one of the aspects.

[0115] In a twelfth aspect, a communication device is provided (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the functions involved in any aspect.

[0116] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0117] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0118] The communication device provided in any one of the sixth aspect to the twelfth aspect may be the first entity of the terminal device in the first aspect, or the device contained in the first entity, such as a chip or a chip system; or, the communication device may be the second entity of the terminal device in the second aspect, or the device contained in the second entity, such as a chip or a chip system; or, the communication device may be the sixth entity of the terminal device in the third aspect, or the device contained in the sixth entity, such as a chip or a chip system; or, the communication device may be the seventh entity of the terminal device in the fourth aspect, or the device contained in the seventh entity, such as a chip or a chip system; or, the communication device may be the seventh entity of the terminal device in the fifth aspect, or the device contained in the seventh entity, such as a chip or a chip system.

[0119] It can be understood that when the communication device provided in any one of the sixth to twelfth aspects is a chip, the sending action / function of the communication device can be understood as output information, and the receiving action / function of the communication device can be understood as input information.

[0120] Among them, the technical effects brought about by any design method in the sixth to twelfth aspects can refer to the technical effects brought about by different design methods in the first to fifth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0121] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application.

[0122] FIG2 a is a schematic diagram of a user plane communication protocol stack provided in an embodiment of the present application.

[0123] Figure 2b is a schematic diagram of a control plane communication protocol stack provided in an embodiment of the present application.

[0124] FIG3 a is a schematic diagram of the structure of a status report provided in an embodiment of the present application.

[0125] FIG3 b is a schematic diagram of the structure of another status report provided in an embodiment of the present application.

[0126] FIG3 c is a schematic diagram of the structure of another status report provided in an embodiment of the present application.

[0127] FIG4 is a schematic diagram of a scenario provided in an embodiment of the present application.

[0128] FIG5a is a schematic diagram showing the principle of a status report provided in an embodiment of the present application.

[0129] FIG5 b is a schematic diagram showing the principle of another reporting status report provided in an embodiment of the present application.

[0130] FIG6 is a flow chart of a communication method provided in an embodiment of the present application.

[0131] FIG7 is a diagram showing a working principle according to an embodiment of the present application.

[0132] FIG8 is a schematic diagram of another scenario provided in an embodiment of the present application.

[0133] FIG9 is a flow chart of another communication method provided in an embodiment of the present application.

[0134] FIG10 is a flow chart of another communication method provided in an embodiment of the present application.

[0135] FIG11 is a flow chart of another communication method provided in an embodiment of the present application.

[0136] FIG12 is a flow chart of another communication method provided in an embodiment of the present application.

[0137] FIG13a is a flow chart of another communication method provided in an embodiment of the present application.

[0138] FIG13 b is another working principle diagram provided in an embodiment of the present application.

[0139] FIG14 is a flow chart of another communication method provided in an embodiment of the present application.

[0140] FIG15 is another working principle diagram provided in an embodiment of the present application.

[0141] FIG16 is a flow chart of another communication method provided in an embodiment of the present application.

[0142] FIG17 is a flow chart of another communication method provided in an embodiment of the present application.

[0143] FIG18 is a flow chart of another communication method provided in an embodiment of the present application.

[0144] FIG19 is a flow chart of another communication method provided in an embodiment of the present application.

[0145] Figure 20 is a flow chart of another communication method provided in an embodiment of the present application.

[0146] FIG21 is another working principle diagram provided in an embodiment of the present application.

[0147] Figure 22 is a flow chart of another communication method provided in an embodiment of the present application.

[0148] Figure 23 is a flow chart of another communication method provided in an embodiment of the present application.

[0149] Figure 24 is a flow chart of another communication method provided in an embodiment of the present application.

[0150] Figure 25 is a structural diagram of a communication device provided in an embodiment of the present application.

[0151] Figure 26 is a structural diagram of another communication device provided in an embodiment of the present application.

[0152] Figure 27 is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0153] The technical solution in this application will be described below with reference to the accompanying drawings.

[0154] Throughout this application, the term "system" and "network" are interchangeable. This application presents various aspects, embodiments, or features centered around a system that may include multiple devices, components, modules, and the like. It should be understood that each system may include additional devices, components, modules, and the like, and / or may not include all of the devices, components, modules, and the like discussed in conjunction with the accompanying figures. Furthermore, combinations of these aspects may also be used.

[0155] Additionally, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as an "example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "example" is intended to present concepts in a concrete manner.

[0156] In the embodiments of the present application, “of”, “corresponding”, “relevant” and “corresponding” may sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0157] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0158] FIG1 is a schematic diagram of the architecture of a communication system 1000 used in an embodiment of the present application. As shown in FIG1 , the communication system 1000 includes at least one network device (such as 110a and 110b in FIG1 ) and at least one terminal device (such as 120a-120j in FIG1 ). The terminal device can communicate with the network device wirelessly. Alternatively, different network devices can communicate with each other. Alternatively, different terminal devices can communicate with each other.

[0159] It should be pointed out that Figure 1 is only a schematic diagram. Although not shown, the communication system 1000 can also include other network devices. For example, the communication system 1000 can also include one or more core network (CN) devices, wireless relay devices and wireless backhaul devices, which are not specifically limited here.

[0160] The network device can be connected to the core network device via wireless or wired communication. The core network device and the network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the network device can be integrated into the same physical device, or the functions of some core network devices and some network devices can be integrated into one physical device. This embodiment of the present application does not specifically limit this.

[0161] Optionally, the network device is a network-side device with wireless transceiver functions. The network device may be a device in a radio access network (RAN) that provides wireless communication functions for terminal devices, referred to as a RAN device. The RAN may be an access network in the 3rd Generation Partnership Project (3GPP), for example, 4G, 5G, or the future-oriented 6G network. The RAN may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network of two or more of the above networks. The RAN device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation base station (next generation nodeB, gNB) in a fifth-generation (5G) mobile communication system, a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, a wireless fidelity (WiFi) system, a long-range radio (LoRa) system, or an access node in a vehicle networking system. RAN equipment can also be a module or unit that performs some of the functions of a base station. For example, it can be a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). The CU here performs the functions of the base station's radio resource control protocol and packet data convergence protocol (PDCP), and can also perform the functions of the service data adaptation protocol (SDAP); the DU performs the functions of the base station's radio link control layer and medium access control (MAC) layer, and can also perform some or all of the physical layer functions. For detailed descriptions of each of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The CU and DU can be set up separately, or they can be included in the same network element, such as the baseband unit (BBU).The RU may be included in a radio frequency device or radio frequency unit, for example, a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in an ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, and RU may also be called O-RU. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. The radio access network device may be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), a relay node, a donor node, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the radio access network device. For ease of description, network device is referred to as the abbreviation of radio access network device, and base station is used as an example of radio access network device.

[0162] Optionally, the terminal device accesses the core network via a network device. The terminal device includes a device that provides voice and / or data connectivity to the user. Specifically, it includes a device that provides voice to the user, a device that provides data connectivity to the user, or a device that provides both voice and data connectivity to the user. For example, it may include a handheld device with wireless connectivity or a processing device connected to a wireless modem. The terminal device can communicate with the core network via the radio access network, exchange voice or data with the RAN, or exchange voice and data with the RAN. The terminal device may include user equipment (UE), wireless terminal device, mobile terminal device, D2D terminal device, V2X terminal device, machine-to-machine / machine-type communications (M2M / MTC) terminal device, Internet of Things (IoT) terminal device, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, it may include a mobile phone (or so-called "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). Also included are limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.

[0163] The various terminal devices introduced above, if located on a vehicle (eg, placed in or installed in a vehicle), can be considered as vehicle-mounted terminal devices, which are also called on-board units (OBUs).

[0164] In the embodiment of the present application, the terminal device may further include a relay. Alternatively, it can be understood that anything that can communicate data with a base station can be considered a terminal device.

[0165] In the embodiments of the present application, the device for implementing the functions of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the functions, such as a chip system, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in the embodiments of the present application, the device for implementing the functions of the terminal is a terminal device as an example for description.

[0166] It should be understood that network devices and terminal devices can be fixed or mobile. Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of network devices and terminal devices.

[0167] The roles of network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. To terminal devices 120j that access the wireless access network through 120i, terminal device 120i is a network device; however, to network device 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a network device. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with network device functionality, and 120a-120j in Figure 1 can be referred to as communication devices with terminal device functionality.

[0168] Network devices and terminal devices, network devices and network devices, and terminal devices and terminal devices can communicate through authorized spectrum, unauthorized spectrum, or both. Communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz simultaneously. The embodiments of the present application do not limit the spectrum resources used for wireless communications.

[0169] In the embodiments of the present application, the functions of the network device may also be performed by a module (such as a chip) in the network device, or by a control subsystem that includes the network device functions. The control subsystem that includes the network device functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device that includes the terminal device functions.

[0170] In an embodiment of the present application, a network device sends a downlink signal or downlink information to a terminal device, and the downlink information is carried on a downlink channel; the terminal device sends an uplink signal or uplink information to the network device, and the uplink information is carried on an uplink channel. In order to communicate with the network device, the terminal device needs to establish a wireless connection with the cell controlled by the network device. The cell with which the terminal device has established a wireless connection is called the serving cell of the terminal device. When the terminal device communicates with the serving cell, it will also be interfered with by signals from neighboring cells.

[0171] It should be noted that the solutions in the embodiments of the present application can also be applied to other communication systems, and the corresponding names can also be replaced by the names of corresponding functions in other communication systems.

[0172] To facilitate understanding of the embodiments of the present application, the following briefly describes the terms used in the embodiments of the present application. It should be understood that these descriptions are only for facilitating understanding of the embodiments of the present application and should not constitute any limitation on the present application.

[0173] 1. Synchronization requirements for different data

[0174] At present, with the increasing demand for immersion, users are no longer satisfied with visual and auditory experiences. Extended Reality (XR) services have gradually evolved from the transmission of audio and video to multimodal content presentation, such as providing additional tactile experience.

[0175] However, when multiple transmission streams (such as video, audio, and haptics) exist simultaneously, additional requirements and challenges arise. For example, to avoid the situation where audio, video, and haptics are out of sync, there is a need for multi-stream data synchronization.

[0176] Taking audio and video synchronization as an example, when a user sees a frame of image, the corresponding audio signal must also be played within a certain period of time. Therefore, certain restrictions are placed on the transmission time of various data types. For example, when considering only video data, the uplink air interface transmission delay of a frame of image is 30ms. However, when transmitting the video data corresponding to an audio signal, the actual transmission delay requirement may be more stringent. For example, the corresponding video data must be transmitted within 20ms after the audio data is transmitted. In this case, if the transmission is still based on the 30ms transmission delay, the audio and video will be out of sync.

[0177] For example, 3GPP shows synchronization thresholds between different data, as shown in Table 1:

[0178] Table 1

[0179] In Table 1, the auditory delay is 20ms compared to the visual delay. This means that when visual data is sent first, the associated auditory data must be transmitted within 20ms. If the delay exceeds this threshold, the user will perceive that the audio and video are out of sync, which reduces the viewing experience. The rest of the examples are similar and will not be elaborated on here.

[0180] 2. Wireless access network protocol stack

[0181] The protocol stack on the wireless access network side can be divided into a user plane protocol stack and a control plane protocol stack.

[0182] See Figure 2a, which is a schematic diagram of the user plane protocol stack architecture. The user plane protocol stack may include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0183] In Figure 2a, for XR services, after service data reaches the terminal device, each protocol layer processes the data sequentially in the order shown in Figure 2a, from top to bottom, and ultimately transmits it to the network device via the air interface. After receiving the data over the air interface, the network device processes the data in the reverse order of the terminal device. The data processing at each protocol layer is implemented by the multifunctional entity corresponding to that protocol layer. For details, please refer to the relevant 3GPP technical specifications and will not be repeated here.

[0184] It is easy to understand that the user plane protocol stack shown in FIG2a does not constitute any limitation to the solution of the present application. In actual applications, the user plane protocol stack may include more or fewer protocol layers than shown in the figure.

[0185] 2b is a schematic diagram of the architecture of a control plane protocol stack, which may include a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and a radio resource control (RRC) layer.

[0186] As shown in Figures 2a and 2b, the MAC layer can provide services to higher layers (such as the RLC layer) via logical channels (LCHs). Depending on the type of information being transmitted, logical channels can be categorized as control channels used to transmit control information on the control plane and traffic channels used to transmit user data on the user plane.

[0187] When a network device configures a logical channel for a terminal device, it also indicates the logical channel group (LCG) to which the logical channel belongs. That is, the network device knows which LCG each logical channel belongs to.

[0188] A radio bearer (RB) is a set of connection formats between a terminal device and a network device (such as a base station), and can include configurations related to physical channels, transport channels, and logical channels. RBs can be divided into signaling radio bearers (SRBs) for transmitting control information on the control plane and data radio bearers (DRBs) for transmitting user data on the user plane.

[0189] In the present application, as a possible understanding, in a narrow sense, LCH is the channel between the RLC layer and the MAC layer. DRB is the channel between the PDCP layer and the RLC layer. One LCH corresponds to one DRB, and different LCHs correspond to different DRBs, that is, there is a corresponding relationship between LCH and DRB, for example, one DRB corresponds to one LCH, and it can also be applicable to one DRB corresponding to multiple LCHs. In this application, DRB is taken as an example for introduction. Of course, this application does not exclude the possibility of other expressions (such as LCH) to express the same or similar meanings. Any modifications, equivalent replacements, improvements, etc. that meet the characteristics described in this application, that is, within the spirit and principles of this application, should be included in the scope of protection of this application.

[0190] In this application, as another understanding, in a broad sense, a DRB includes a DRB in a narrow sense and an LCH. Accordingly, the DRB in this application can be understood as a DRB in a broad sense.

[0191] 3. Buffer Status Reporting (BSR)

[0192] In uplink transmission scenarios, the terminal device can send a BSR to the network device to report the amount of uplink data to be sent. The network device can allocate appropriate uplink resources to the terminal device based on the BSR to implement uplink scheduling.

[0193] Currently, BSR is a media access control (MAC) control element (CE), and therefore may also be referred to as BSR MAC CE.

[0194] 4. Delay Status Reporting (DSR)

[0195] Traditional BSRs only report data volume. However, latency-sensitive services, such as XR services, have stringent requirements for air interface transmission latency. Since base stations cannot obtain data latency information based on traditional BSRs, the resources they schedule may not enable data to be transmitted within the required air interface time. This not only wastes air interface transmission resources but also impacts the user experience. Therefore, a solution has been proposed: a report indicating the latency of the data to be transmitted can be submitted by the terminal device, thereby notifying the base station of the transmission latency requirement for the data to be transmitted. This report carrying the latency information of the data to be transmitted is called a DSR.

[0196] It should be pointed out that DSR is only an exemplary name currently provided. The report carrying the delay information of the transmitted data may also have other names, which is not limited in the embodiments of the present application.

[0197] It should be noted that currently, how DSR reports the delay information (or delay information and data volume) of the data to be transmitted has not been specified. In one possible implementation, similar to BSR MAC CE, DSR can also be a MAC CE, which can be called DSR MAC CE.

[0198] Optionally, the DSR may also indicate the amount of data to be transmitted. It is understood that if the DSR can simultaneously indicate the amount of data to be transmitted and the delay information of the data to be transmitted, the DSR may also be understood as a BSR that expands new functions based on the original functions.

[0199] The following are some examples of possible ways to trigger DSR:

[0200] Method 1: Triggering DSR based on the storage duration of the data to be transmitted.

[0201] It can be understood that DSR triggering can be triggered by the storage duration of the data to be transmitted equaling or exceeding a threshold. For example, the terminal device receives threshold information indicating a threshold. When the storage duration of certain data on the terminal device (such as an XR device) reaches (equals or exceeds) the threshold, DSR is triggered.

[0202] In the present application, for uplink transmission, the starting time of the stored duration of the data can be understood as the time when the data arrives at the terminal device. For example, it can be the time when the data arrives at the access stratum (AS) layer, or the time when the data arrives at the service data adaptation protocol (SDAP) layer, or the time when the data arrives at the packet data convergence protocol (PDCP) layer, or the time when the data arrives at the radio link control (RLC) layer, or the time when the data arrives at the logical channel (LCH), or the time when the data arrives at the media access control (MAC) layer, and the embodiments of the present application do not limit this.

[0203] It should be noted that, in this application, data is introduced as follows: data may be a protocol data unit (PDU), or data may be a protocol data unit set (PDU set), or data may be a data burst.

[0204] A PDU set includes at least one PDU. The different PDUs in a PDU set carry information units generated by an application (or application layer). For example, a video frame with a large amount of data usually needs to be divided into multiple PDUs for transmission.

[0205] A data burst can be understood as at least one PDU generated and sent by an application (or application layer) within a short period of time. Different PDUs in the same data burst can come from one or more PDU sets.

[0206] When data is understood as a PDU set (or data burst), the time when the data arrives at the terminal device can be understood as the time when a PDU in the PDU set (or data burst) arrives at the terminal device, which is generally the time corresponding to the first PDU in the PDU set (or data burst) to arrive at the terminal device. It should be understood that the first PDU to arrive at the terminal device can be the first PDU in the PDU set (or data burst) in the order of generation or transmission, or it can be a non-first PDU in the PDU set (or data burst) in the order of generation or transmission, such as the second PDU, etc., and this embodiment of the present application does not limit this.

[0207] In this application, the end time of the stored duration of the data can be understood as the current time of the communication system, that is, the stored duration is updated (e.g., increased) according to the operation of the system. The unit of the stored duration can be any time unit, such as milliseconds, or can be based on communication-related units, such as the number of time slots, the number of subframes, the number of system frames, etc., and this embodiment of the application is not limited to this.

[0208] Method 2: Triggering DSR based on the remaining transmission delay budget of the data to be transmitted.

[0209] It can be understood that DSR can also be triggered when the remaining transmission delay budget of the data to be transmitted is less than or equal to a threshold. For example, the terminal device receives threshold information indicating a threshold. When the remaining transmission delay budget of a certain data of the terminal device (such as an XR device) reaches (is less than or equal to) the threshold, DSR is triggered.

[0210] In this application, the remaining transmission delay budget can be understood as a duration. The starting time of the remaining transmission delay budget is the current system time, and the ending time of the remaining transmission delay budget is the time when the transmission delay budget of the data is about to time out or the time when the data is about to be discarded.

[0211] The transmission delay budget is described as follows:

[0212] For example, the transmission delay budget can be the packet delay budget (PDB) timeout corresponding to the data. The PDB can be understood as the delay requirement from the terminal device to the base station or to the user plane function (UPF) network element, that is, the time from when a PDU arrives at the terminal device to when the PDU is successfully received by the base station or UPF network element. Typically, the PDB is configured by the core network (CN) through the 5G Quality of Service (QoS) identifier (5G QoS identifier, 5QI).

[0213] Another example of a transmission delay budget is the timeout of the PDU set delay budget (PSDB) corresponding to the data. PSDB can be understood as the transmission delay requirement for a PDU set, such as the time from the first PDU in a PDU set arriving at the terminal device to the time when all PDUs in the PDU set are successfully received by the base station or UPF network element.

[0214] The moments when data is about to be discarded are described as follows:

[0215] The moment when data is about to be discarded can be understood as the moment when the packet loss timer corresponding to the data times out.

[0216] For example, the PDCP layer configures a packet loss timer for each service data unit (SDU). When an SDU from a higher layer reaches the PDCP layer, the packet loss timer is started for the PDCP SDU. When the packet loss timer expires, the corresponding SDU or PDU will be discarded.

[0217] Method 3: Triggering DSR based on the amount of data to be transmitted.

[0218] For example, when the data volume of an LCH or LCG exceeds (is greater than or equal to) a threshold, the DSR is triggered.

[0219] It should be understood that since a terminal device can have multiple LCHs and LCGs at the same time, the DSR triggered by any LCH or LCG may include the delay information of other LCGs or LCHs, or the delay information and related data volume.

[0220] The following is an example of the structure of some DSRs:

[0221] For example, a DSR structure may be shown in FIG3a. In FIG3a, each delay index represents a time interval (such as the interval of the remaining transmission delay budget), and the time interval may be as shown in Table 2:

[0222] Table 2

[0223] In Table 2, each value of the delay index can represent whether the MAC CE contains the amount of data in the time interval. When the delay index field indicates that the corresponding time interval has data, the MAC CE contains a corresponding buffer size field to carry the amount of data that meets the delay index time interval.

[0224] For example, when the bit corresponding to delay index i (e.g., i=0) is '1', the MAC CE includes the amount of data with a remaining transmission delay budget in the interval 'X≤5ms'. In this case, the MAC CE includes a word field that carries certain information used to indicate the amount of data with a remaining transmission delay budget in the interval 'X≤5ms'. When the bit corresponding to delay index i (e.g., i=0) is '0', the MAC CE does not include the amount of data with a remaining transmission delay budget in the interval 'X≤5ms'. In this case, the MAC CE does not include the word field used to indicate the remaining transmission delay budget in the interval 'X≤5ms', thereby saving overhead.

[0225] For example, another DSR structure can be shown in Figure 3b. In Figure 3b, the data volumes of multiple LCGs can be transmitted through a MAC CE. In this case, one byte of the MAC CE (such as the byte where LCG0-LCG7 are located) is used to indicate which LCG data volumes are transmitted in the MAC CE.

[0226] For example, when the bit corresponding to LCGi (e.g., i=0) is '1', the MAC CE includes the amount of data in LCG0. In this case, the MAC CE contains information indicating the amount of data and delay in LCG0, as shown in Figure 3a. Specifically, each LCG in the MAC CE corresponds to several delay indices, and each delay index indicates whether there is data in the corresponding time interval for that LCG. For example, when the bit corresponding to LCGi (e.g., i=0) is '1', and when the bit corresponding to delay index i (e.g., i=0) is '1', the MAC CE includes the amount of data in LCG0 with a remaining transmission delay budget within the interval 'X≤5ms'. In this case, the MAC CE contains a field that carries information indicating the amount of data in LCG0 with a remaining transmission delay budget within the interval 'X≤5ms'. Therefore, Figure 3b can be understood as each LCG corresponding to the content of Figure 3a. If the MAC CE indicates that a certain LCG has data volume to report, the MAC CE includes the delay information and data volume corresponding to the LCG as shown in FIG3 a .

[0227] In addition, when LCGi='0', it means that no data volume in LCGi is reported in the MAC CE, and the data volume and delay information indication field corresponding to LCGi does not appear in the MAC CE, thereby reducing the overhead of the MAC CE.

[0228] For example, another DSR structure may be shown in Figure 3c. In Figure 3c, data volumes of multiple LCGs may be transmitted via a single MAC CE. A byte of the MAC CE (e.g., the byte containing LCG0-LCG7) indicates which LCG data volumes are transmitted in the MAC CE.

[0229] For example, when LCG i (e.g. i=0) When the corresponding bit is '1', the MAC CE contains the amount of data in LCG0. In this case, the MAC CE contains information indicating the amount of data and delay in LCG0. Specifically, each LCG in the MAC CE corresponds to a table index field, a delay information indication field, and a cache size field. When LCG i (e.g. i=0) When the corresponding bit is '1', the MAC CE contains a table index field in LCG0, a delay information indication field, and a cache size field. The delay information indication field is used to indicate a remaining transmission delay budget. Specifically, the remaining transmission delay budget can be the corresponding LCG iThe remaining transmission delay budget of the data with the shortest remaining transmission delay budget among all the data to be transmitted. The buffer size field is used to indicate the corresponding LCG i The amount of data for which the remaining transmission delay budget is lower than the delay threshold among all the data to be transmitted. The delay threshold can be obtained through a semi-static message such as RRC signaling. In addition, the table index field can be used to indicate the LCG i The data amount indicated by the corresponding cache size field refers to the cache status list. For example, when the terminal device or LCG i When multiple cache status lists are configured (such as a long cache status list), it is necessary to use the table index field to determine the cache status list corresponding to the cache size field. i Or when the terminal device is not configured with multiple cache status lists, the table index field may not appear, such as being regarded as a reserved field, or the table index field may be ignored.

[0230] In addition, when LCG i ='0', it means LCG i If no data volume is reported in the MAC CE, then LCG i The corresponding data volume, delay information indication field and table index field do not appear in the MAC CE, thereby reducing the overhead of the MAC CE.

[0231] In some embodiments, for the MAC CE in Figure 3a, Figure 3b, or Figure 3c, the latency information of the MAC CE is determined based on a packet loss timer. The packet loss timer is configured via RRC signaling. For example, when a PDCP SDU arrives at the PDCP layer, a packet loss timer is started (or restarted) for the SDU. The latency information of the SDU can be determined based on the real-time value of the packet loss timer.

[0232] In other embodiments, for the MAC CE in FIG3a or FIG3b , the delay information of the MAC CE is generally determined based on the transmission delay budget. For example, for a PDCP SDU arriving at the PDCP layer, the transmission delay budget of the SDU can be determined based on the 5QI, and the delay information of the SDU can be determined based on the transmission delay budget and the stored duration.

[0233] Since the packet loss timer or transmission delay budget only considers the transmission requirements of a single data (such as video data, audio data, or tactile data), the reported delay information may be greater than the actual delay requirement for considering the synchronization of multiple data transmissions. When the network device schedules based on the incorrect delay information, the scheduled data may exceed the synchronization requirements of the application end, affecting the user experience.

[0234] Taking Figure 4 as an example, at 0ms, the tactile data arrives at the PDCP layer of the terminal device. At 5ms, the visual data arrives at the PDCP layer of the terminal device. Among them, the tactile data is associated with the visual data. It can be seen from Table 1 that when the tactile data reaches the terminal device first, the visual data associated with the tactile data needs to be transmitted within 20ms, as shown in the dotted box in Figure 4. However, considering a single data, the transmission delay budget of the visual data is 30ms, as shown by the packet loss timer in Figure 4. In the related art, when the terminal device reports the DSR at a certain moment (such as the 12ms), the delay information of the visual data is determined according to the packet loss timer, without considering the need for synchronization between multiple data. When the transmission resources of the visual data are after 20ms, that is, the visual data is not transmitted within 20ms, the tactile and visual data will be out of sync, affecting the user experience.

[0235] In addition, related technologies also provide a method for reducing the data transmission delay budget. For example, considering a single data stream, the transmission delay budget for visual data is reduced from 30ms to 20ms (or other values ​​less than 30ms). Since the time when each type of data in the multi-stream data arrives at the terminal device is not fixed, there is still a phenomenon that the transmission delay budget of a single data stream is greater than the delay requirement for the synchronization of multiple data transmissions. Therefore, even if the data transmission delay budget is reduced, the delay information in the DSR may be inaccurate, and synchronization between different data cannot be guaranteed.

[0236] In other embodiments, for the MAC CE in FIG3a or FIG3b, the latency information of the MAC CE is determined based on the stored duration. The start time of the stored duration of the data may be determined based on the time when the data arrives at the terminal device. The end time of the stored duration of the data may be determined based on the time when the DSR is reported.

[0237] Taking Figure 5a as an example, the start time of the data storage duration is the time when the data arrives at the terminal device, that is, the 0th millisecond. The end time of the data storage duration is the time when the DSR is reported, that is, the 20th millisecond. Accordingly, the storage duration is 20 milliseconds.

[0238] In other embodiments, for the MAC CE in Figure 3a or Figure 3b, the MAC CE delay information is determined based on the remaining transmission delay budget. When the remaining transmission delay budget is determined based on a packet loss timer, the end time of the remaining transmission delay budget is the end time of the packet loss timer, and the start time of the remaining transmission delay budget is the DSR reporting time. The start time of the packet loss timer is the time when the data arrives at the PDCP layer.

[0239] Taking Figure 5b as an example, the start time of the data storage duration is the moment the data arrives at the terminal device, that is, the 0th millisecond. Accordingly, the packet loss timer starts at the 0th millisecond. The end time of the data storage duration is the time the DSR is reported, that is, the 10th millisecond. Accordingly, the start time of the data's remaining transmission delay budget is the time the DSR is reported, that is, the 10th millisecond. The end time of the data's remaining transmission delay budget is the end time of the packet loss timer, that is, the 20th millisecond.

[0240] It should be pointed out that in Figure 5a or Figure 5b, the delay information reported by the DSR only considers the transmission requirements of a single data (such as video data, audio data, or tactile data), but does not consider the delay requirements for the synchronization of multiple data transmissions. It is still possible that the scheduled data has exceeded the synchronization requirements of the application side, affecting the user experience.

[0241] In summary, DSR in related technologies affects the synchronization between multiple streams. For example, DSR in related technologies does not consider the need to affect the synchronization between multiple streams, resulting in inaccurate latency information in the DSR, or DSR is not triggered in a timely manner, both of which affect the synchronization between different streams.

[0242] In view of this, an embodiment of the present application provides a communication method, which can be applied to the communication system shown in Figure 1. In the communication method provided in the embodiment of the present application, the first entity of the terminal device receives first information from the first DRB. The first information is related to the first data, and the first data belongs to the first DRB. The first entity of the terminal device determines a first duration based on the first information. The first duration is the duration for which the second data is expected to be transmitted. The second data belongs to the second DRB. The first entity may be the PDCP entity corresponding to the second DRB, or the first entity is a MAC entity that processes the second data. The first duration is used to determine the delay information of the status report (for example, the delay information of the status report includes the delay information of the second data, and the first duration is used to determine the delay information of the second data), and / or, the first duration is used to trigger the sending of the status report.

[0243] That is, the first entity of the terminal device refers to the first information when determining the expected duration for the second data to be transmitted (i.e., the first duration). Since the first information is related to the first data in the first DRB, the first duration determined based on the first information takes the first data into account, avoiding considering only the transmission delay of a single data (i.e., the second data), thereby laying the foundation for synchronization between the first data and the second data.

[0244] For example, when the first duration is used to determine the delay information of the status report (for example, the delay information of the status report includes the delay information of the second data, and the first duration is used to determine the delay information of the second data), since the first duration refers to the duration of the synchronization requirement between the first data and the second data, the delay information also takes into account the synchronization requirement of the second data, thereby improving the accuracy of the delay information and helping to achieve the effect of synchronization between the first data and the second data.

[0245] For example, when the first duration is used to trigger the sending of the status report, since the first duration is based on the duration of the synchronization requirement between the first data and the second data, the triggering of the status report also takes into account the synchronization requirement of the second data, thereby improving the accuracy of the status report triggering and helping to achieve the effect of synchronization between the first data and the second data.

[0246] It should be understood that the message names between the devices or the names of the parameters in the messages in the following embodiments of the present application are only examples, and other names may be used in specific implementations. The embodiments of the present application do not specifically limit this.

[0247] Example 1

[0248] The following is introduced by taking the case where the first entity is the PDCP entity corresponding to the second DRB as an example.

[0249] The communication method 600 proposed in the embodiment of the present application is described in detail below with reference to FIG6 to FIG13b. The communication method 600 proposed in the embodiment of the present application includes the following operations:

[0250] S601: The terminal device obtains first data and second data.

[0251] For example, the terminal device is introduced as follows:

[0252] The terminal device can be the terminal device in Figure 1, or it can be a component applied to the terminal device, such as a processor, chip, or chip system, etc., or it can be a logical module or software that can realize all or part of the terminal device functions. This application does not limit this.

[0253] Illustratively, S601 includes S601a and S601b:

[0254] S601a. ​​The first entity of the terminal device receives second data.

[0255] The first entity is described as follows:

[0256] For example, the first entity may be the PDCP entity corresponding to the second DRB. Taking FIG7 as an example, the second DRB is DRB#1, and the first entity is PDCP entity 1.

[0257] It should be understood that the first entity may also be other entities corresponding to the second DRB, such as an SDAP entity, an RLC entity, etc. In the communication method 600 of the present application, the first entity is introduced by taking the PDCP entity as an example.

[0258] Among them, the second data is introduced as follows:

[0259] In this application, the second data belongs to the second DRB. It can be understood that the second data is transmitted via the second DRB. For example, the second data is transmitted to the RLC entity corresponding to the second DRB via the PDCP entity corresponding to the second DRB.

[0260] Illustratively, the second data may be a PDU, or a PDU set, or a data burst. For details, please refer to the introduction in the glossary section and will not be repeated here.

[0261] Exemplarily, the second data may be visual data, or tactile data, or audio data.

[0262] Taking Figure 4 as an example, the second data may be visual data. Taking Figure 8 as an example, the second data may be tactile data. Figures 4 and 8 illustrate the synchronization requirements for video data and digital data.

[0263] In the case where the first entity is a PDCP entity, taking the second data as an SDU as an example, S601a includes: the PDCP entity corresponding to the second DRB receives an SDU.

[0264] S601b. The second entity of the terminal device receives the first data.

[0265] The second entity is described as follows:

[0266] Exemplarily, the second entity may be the PDCP entity corresponding to the first DRB. Taking FIG7 as an example, the first DRB is DRB#0 and the second entity is PDCP entity 0.

[0267] It should be understood that the second entity may also be other entities corresponding to the first DRB, such as an SDAP entity, an RLC entity, etc. In the communication method 600 of the present application, the second entity is introduced by taking the PDCP entity as an example.

[0268] Among them, the introduction of the first data is as follows:

[0269] In this application, the first data belongs to the first DRB. It can be understood that the first data is transmitted via the first DRB. For example, the first data is transmitted from the corresponding PDCP entity to the RLC entity corresponding to the first DRB via the first DRB.

[0270] Illustratively, the first data may be a PDU, or a PDU set, or a data burst. For details, please refer to the introduction in the glossary section and will not be repeated here.

[0271] In some embodiments, the first data may be in SDU granularity, that is, each SDU that reaches the PDCP entity (that is, the PDCP entity corresponding to the first DRB) may be regarded as a first data. Alternatively, the first data may not be in SDU granularity, for example, an SDU after every several SDUs may be regarded as a first data. Among them, the several SDUs may be a fixed number of SDUs, for example, the third SDU in every three SDUs is regarded as a first data, such as the first data is the third SDU, or the first data is the sixth SDU, or the first data is the ninth SDU, etc. That is, the appearance of the first data is periodic, and the period value is determined according to the number of SDUs. Alternatively, the several SDUs may also be SDUs with uneven data amounts. After receiving three SDUs at a time, the fourth SDU is regarded as the first data. And after receiving four SDUs at another time, the fifth SDU is regarded as the first data.

[0272] As another possible example, the first data may be determined based on indication information X. The indication information X may be obtained from within the terminal device. Alternatively, the first DRB may include an SDU carrying indication information X. For example, the SDU may include an indication information X in a user plane general packet radio service (GPRS) tunneling protocol (GTP-U) header. The indication information X in the GTP-U header may indicate that the SDU is the first data. Alternatively, when the third timer is started, the indication information X in the GTP-U header may indicate that the third timer is restarted. For details, see the introduction to S621, which will not be described here.

[0273] Exemplarily, the first data may be visual data, or tactile data, or audio data.

[0274] Taking FIG4 as an example, the first data may be tactile data. Taking FIG8 as an example, the first data may be visual data.

[0275] Exemplarily, taking the first data as an SDU as an example, S601 includes: the PDCP entity corresponding to the first DRB receives an SDU.

[0276] It is easy to understand that the terminal device may execute S601b first and then execute S601a. ​​In other words, the first data arrives at the terminal device first and the second data arrives at the terminal device later.

[0277] It is easy to understand that the first data and the second data can be different data in the same service, such as audio data and tactile data, or audio data and video data of the same service. For example, the same service can be understood as data from the same server or the same group of servers. In some examples, the server can send an indication to determine whether different data belong to the same service.

[0278] It is easy to understand that in this application, the first DRB is associated with the second DRB. This means that for the data of the second DRB, such as the second data mentioned above, in the process of determining the expected transmission duration of the second data (i.e., the first duration mentioned above), it is necessary to refer to the first information provided by the first DRB. Please refer to the introduction of S602 and S603 for details, which will not be repeated here.

[0279] It is easy to understand that in the present application, the association relationship between the first DRB and the second DRB can be configured by high-level signaling, such as RRC signaling configuring the first DRB to be associated with the second DRB. Alternatively, the terminal device itself determines the association between the first DRB and the second DRB. Alternatively, the first DRB and the second DRB are pre-configured to be associated. Alternatively, the network device dynamically indicates the association relationship between different DRBs, such as the network device sending an indication message. The indication message indicates that the first DRB is associated with the second DBR. The present application does not limit how the terminal device determines the association relationship between the first DRB and the second DRB.

[0280] For the second entity of the terminal device, after receiving the first data, the second entity executes S602:

[0281] S602: The second entity of the terminal device sends first information to the first entity. Correspondingly, the first entity receives the first information from the second entity.

[0282] In the present application, since the second entity is the entity corresponding to the first DRB, such as a PDCP entity, it can also be understood that the first entity receives the first information from the first DRB.

[0283] The first information is as follows:

[0284] Exemplarily, the first information indicates a second duration or a first moment. The starting moment of the second duration is the moment when the first data arrives at the PDCP entity corresponding to the first DRB, or the starting moment of the second duration is the moment when the first information is received, or the starting moment of the second duration is indicated by the first information. The first moment is the end moment of the second duration.

[0285] Taking Figure 4 as an example, the second duration may be the duration between 0ms and 20ms, as shown by the dotted box where the 'synchronization requirement' is located. The first moment is the 20ms, ie, the end moment of the dotted box where the 'synchronization requirement' is located.

[0286] In this application, the second duration can be understood as, when the first data arrives at the terminal device first, the moment the first data arrives at the terminal device is used as the starting moment, and the second data is transmitted within the second duration, thereby synchronizing the first data with the second data. Conversely, if the second data is not transmitted within the above-mentioned second duration, the first data and the second data are out of sync, affecting the user experience. The moment the first data arrives at the terminal device can be understood as the moment the first data arrives at the PDCP entity corresponding to the first DRB.

[0287] It is easy to understand that, as an example, the second duration can be semi-statically configured or pre-configured, such as indicated to the first DRB (or second entity) through high-layer signaling or core network signaling. Exemplarily, the value of the second duration can be determined according to Table 1. For example, when the first data is tactile data, the second data is visual data, and the first data arrives at the terminal device first, it can be seen from Table 1 that the second duration is 20ms. When the moment when the first data arrives at the terminal device is known, the first moment can be determined based on the second duration.

[0288] It is easy to understand that, on the second entity side, as an example, when the second entity receives the first data, the second entity sends the first information to the first entity based on the first data. In other words, the first information is related to the first data, and it can be understood that the first data can trigger the sending of the first information.

[0289] As another example, when the second entity receives indication information X, the second entity sends the first information to the first entity. The indication information X can be control plane signaling or user plane information, such as indication information X carried by the first data. For information about indication information X, refer to the description of S621 and are not described here. Alternatively, indication information X can be internal signaling of the terminal device, such as from the application layer of the terminal device. For example, after the second entity of the terminal device receives the first data or indication information X, it executes S602.

[0290] For the first entity of the terminal device, after receiving the first information, the first entity executes S603:

[0291] S603. The first entity of the terminal device determines a first duration according to the first information.

[0292] Among them, the introduction of the first period is as follows:

[0293] In this application, the first duration is the duration during which the second data is expected to be transmitted. It can be understood that the first duration is a duration determined with reference to the synchronization requirement between the first data and the second data.

[0294] Taking Figure 4 as an example, the second data is visual data. The first duration starts at 5 ms, i.e., when the visual data arrives at the terminal device, or when the second data arrives at the PDCP entity corresponding to the second DRB. The first duration ends at 20 ms, i.e., when the second duration ends. If the second data is transmitted within the first duration, the first data and the second data are synchronized.

[0295] It should be understood that the first duration may also have other names, such as the effective transmission duration of the second data, or the transmission delay budget of the second data. The embodiment of the present application takes the first duration as an example for introduction.

[0296] Next, for the first entity side, the process of determining the first duration is introduced:

[0297] Solution 1: The first duration is determined based on the first information.

[0298] In solution 1, as a first example, as shown in FIG9 , S603 includes S6031 and S6032:

[0299] S6031. The first entity of the terminal device determines the duration of the first timer based on the first information.

[0300] Among them, the introduction of the first timer is as follows:

[0301] Exemplarily, when the first timer expires, the terminal device discards the second data. In other words, the moment the first timer expires is the moment the second data is discarded. The first timer may be a packet loss timer. It should be understood that with the evolution of communication technology, packet loss timers may have other names. This application uses the packet loss timer as an example, and this should not be construed as limiting this application.

[0302] Exemplarily, the first timer (or packet loss timer) is started at the second time. The second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB. Taking Figure 4 as an example, the second data is visual data, and the second time is 5 ms.

[0303] Exemplarily, the end time of the first timer (or packet loss timer) is the first time. The first time can be referred to in the introduction of S602 and will not be described in detail. It can be understood that, in related technologies, the duration or end time of the first timer (or packet loss timer) is obtained by RRC signaling configuration. In the present application, the end time of the first timer (or packet loss timer) is obtained from the first information.

[0304] S6032. The first entity of the terminal device determines a first duration according to the duration of the first timer.

[0305] Among them, the introduction of the first period is as follows:

[0306] Exemplarily, the starting time of the first duration is: the second time. The second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB. Please refer to the introduction of S6031 and no further details will be given.

[0307] For example, the end time of the first duration is the end time of the first timer (or packet loss timer). The end time of the first timer (or packet loss timer) can be found in the introduction of S6031 and will not be described in detail.

[0308] That is to say, the terminal device updates the duration of the first timer (or packet loss timer) based on the first information, and then determines the first duration based on the duration of the first timer (or packet loss timer). Since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the first data and the second data, the duration of the first timer (or packet loss timer) determined based on the first information is a duration that takes into account the synchronization requirements between the first data and the second data. In the case where the first duration is determined based on the duration of the first timer (or packet loss timer), if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the second data in the DSR MAC CE can be determined based on the updated first timer (or packet loss timer).

[0309] In Solution 1, as a second example, as shown in FIG9 , the embodiment of the present application further includes S604:

[0310] S604: The first entity starts a second timer in response to receiving the first information.

[0311] For example, when the first entity receives the first information, the first entity of the terminal device starts the second timer.

[0312] In the present application, starting the second timer may be understood as starting or restarting the second timer.

[0313] The second timer is described as follows:

[0314] Exemplarily, the second timer may be a synchronization timer. For example, the synchronization timer corresponding to the first entity side is recorded as synchronization timer 1, or RX_SYNC_TIMER. Of course, the second timer may also have other names. This application uses the second timer as an example for description, and should not be understood as limiting this application.

[0315] Exemplarily, the start time of the second timer is: the time of receiving the first information.

[0316] For example, when the first entity is the PDCP entity corresponding to the second DRB, the second timer is started at the moment when the PDCP entity corresponding to the second DRB (such as PDCP entity 1 in Figure 7) receives the first information. It can be understood that there is a second timer for the PDCP entity corresponding to the second DRB. Each time a first information is received, the second timer is started or restarted.

[0317] Alternatively, the start time of the second timer may also be indicated by the first information. It can be understood that there is a second timer for the PDCP entity corresponding to the second DRB. Each time a first information is received, the second timer is started or restarted.

[0318] Alternatively, the start time of the second timer may be the second time. The second time is the time when the second data arrives at the first entity. In this case, it can be understood that each second data corresponds to a second timer, which is used to determine the first duration corresponding to the corresponding second data. The number of second timers may be one or more.

[0319] It is easy to understand that in this application, it can be considered that the time when the first entity receives the first information is the same as or close to the time when the first data arrives at the PDCP entity corresponding to the first DRB. Taking Figure 4 as an example, the start time of the second timer can be 0 ms.

[0320] Exemplarily, the end time of the second timer is: the first time, wherein the first time can refer to the introduction of S602 and will not be repeated here.

[0321] Alternatively, the description may be replaced by: the duration of the second timer is the second duration, wherein the second duration can be referred to in the introduction of S602 and will not be repeated here.

[0322] When the terminal device executes S604, as shown in FIG9 , S603 includes S6033:

[0323] S6033. The first entity of the terminal device determines the first duration according to the value of the second timer.

[0324] For example, the first entity determines the first duration according to the real-time value of the second timer.

[0325] As a possible alternative description, the first entity of the terminal device determines the first duration according to the end time of the second timer.

[0326] Among them, the introduction of the first period is as follows:

[0327] Exemplarily, the starting time of the first duration is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, as described in S6031 for details, which will not be repeated here.

[0328] For example, the end time of the first duration is the end time of the second timer. The end time of the second timer can be found in the introduction of S604 and will not be described in detail.

[0329] That is to say, the first entity starts the second timer in response to the reception of the first information, and then determines the first duration based on the value of the second timer (or the end time of the second timer). Since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the first data and the second data, the second timer is started based on the first information, and the duration of the second timer is a duration that takes into account the synchronization requirements between the first data and the second data. In the case where the first duration is determined based on the value of the second timer (or the end time of the second timer), if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the second data in the DSR MAC CE can be determined based on the second timer.

[0330] Solution 2: The first duration is determined based on the first information and the second information.

[0331] In solution 2, as shown in FIG9 , S603 includes S6034:

[0332] S6034. The first entity of the terminal device determines a first duration based on the first information and the second information.

[0333] The second information is introduced as follows:

[0334] In the present application, the second information indicates a time point when the second data is discarded.

[0335] Exemplarily, the second information may be RRC signaling, see the introduction in the glossary section, which will not be repeated here.

[0336] Exemplarily, the second information comes from the network device, that is, the second information is information sent by the network device to the terminal device.

[0337] It should be understood that for the first entity of the terminal device, the first entity can first receive the first information and then receive the second information, or first receive the second information and then receive the first information, or receive the first information and the second information at the same time. The embodiments of the present application do not limit this.

[0338] It should be pointed out that in this application, the network device can be the network device in Figure 1, or it can be a component applied to the network device, such as a processor, chip, or chip system, etc. It can also be a logical module or software that can realize all or part of the functions of the network device. A unified explanation is given here and no further details will be given later.

[0339] Among them, the introduction of the first period is as follows:

[0340] Exemplarily, the starting time of the first duration is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, as described in S6031 for details, which will not be repeated here.

[0341] Exemplarily, the end time of the first duration is: the earlier time between the first time and the discarding time (ie, the time indicated by the second information).

[0342] For example, when the first moment is earlier than the discarding moment (ie, the moment indicated by the second information), the end moment of the first duration is the first moment.

[0343] Taking FIG4 as an example, the first moment is 20 ms, the discarding moment (ie, the moment indicated by the second information) is 35 ms, and the end moment of the first duration is the first moment, ie, 20 ms.

[0344] For another example, when the discarding moment (ie, the moment indicated by the second information) is earlier than or equal to the first moment, the end moment of the first duration is the discarding moment (ie, the moment indicated by the second information).

[0345] Taking FIG8 as an example, the first moment is 30 ms, the discarding moment (ie, the moment indicated by the second information) is 10 ms. The end moment of the first duration is the discarding moment (ie, the moment indicated by the second information), ie, 10 ms.

[0346] That is to say, in the process of determining the first duration, the terminal device refers to both the first information and the second information. In the case of determining the first duration with reference to the first information, since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the first data and the second data, when the first duration is determined based on the first information, if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved. Moreover, in the case of determining the first duration with reference to the second information, since the moment indicated by the second information can enable the terminal device to know the transmission delay requirements of the second data, when the first duration is determined based on the second information, if the second data is transmitted within the first duration, the transmission delay requirements of the second data can be met.

[0347] In solution 2, as a first example, as shown in FIG10 , S6034 includes S6034a and S6034b:

[0348] S6034a. The first entity of the terminal device determines the duration of the first timer based on the first information and the second information.

[0349] Among them, the introduction of the first timer is as follows:

[0350] Exemplarily, the first timer may be a packet loss timer, for which reference may be made to the introduction of S6031 and will not be described in detail.

[0351] Exemplarily, the start time of the first timer (or packet loss timer) is: the second time. The second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB. Please refer to the introduction of S6031 and no further details will be given.

[0352] Exemplarily, the end time of the first timer (or packet loss timer) is: the earlier time between the first time and the time of discarding (ie, the time indicated by the second information).

[0353] For example, when the first moment is earlier than (or equal to) the discarding moment (ie, the moment indicated by the second information), the end moment of the first timer (or packet loss timer) is the first moment.

[0354] For another example, when the discarding moment (ie, the moment indicated by the second information) is earlier than or equal to the first moment, the end moment of the first timer (or packet loss timer) is the discarding moment (ie, the moment indicated by the second information).

[0355] It can be understood that in the related art, the end time of the first timer (or packet loss timer) is obtained by RRC signaling configuration. In the present application, the end time of the first timer (or packet loss timer) is obtained by first information and second information. The second information can be information in the above-mentioned RRC signaling, such as indication information of the time when the second data is discarded.

[0356] S6034b. The first entity of the terminal device determines the first duration according to the duration of the first timer.

[0357] Among them, the introduction of the first period is as follows:

[0358] Exemplarily, the starting time of the first duration is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, as described in S6031 for details, which will not be repeated here.

[0359] Exemplarily, the end time of the first duration is the end time of the first timer (or packet loss timer). The end time of the first timer (or packet loss timer) can be found in the introduction of S6034a and will not be described in detail.

[0360] That is to say, the terminal device updates the duration of the first timer (or packet loss timer) based on the first information and the second information, and then determines the first duration based on the duration of the first timer (or packet loss timer). Since the second duration or the first moment indicated by the first information can meet the synchronization requirements of the first data and the second data, and the moment indicated by the second information can enable the terminal device to know the transmission delay requirements of the second data, the duration of the first timer (or packet loss timer) determined based on the first information and the second information takes into account both the synchronization requirements between the first data and the second data and the transmission delay requirements of the second data. In the case where the first duration is determined based on the duration of the first timer (or packet loss timer), if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved, and the transmission delay requirements of the second data can be met. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the second data in the DSR MAC CE can be determined based on the updated first timer (or packet loss timer).

[0361] In Solution 2, as a second example, as shown in FIG10 , the embodiment of the present application further includes S605:

[0362] S605: The first entity starts a second timer in response to receiving the first information.

[0363] The implementation process of S605 can refer to the introduction of S604 and will not be described in detail.

[0364] When the terminal device executes S605, as shown in FIG10 , S6034 includes S6034c:

[0365] S6034c. The first entity of the terminal device determines a first duration according to the value of the first timer and the value of the second timer.

[0366] For example, the first entity determines the first duration according to the real-time value of the first timer and the real-time value of the second timer.

[0367] Among them, the introduction of the first timer is as follows:

[0368] Exemplarily, the first timer may be a packet loss timer, for which reference may be made to the introduction of S6031 and will not be described in detail.

[0369] Exemplarily, the start time of the first timer (or packet loss timer) is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, which can be referred to the introduction of S6031 and will not be repeated here.

[0370] Exemplarily, the end time of the first timer (or packet loss timer) is the time of discard (ie, the time indicated by the second information). It can be understood that the duration or end time of the first timer (or packet loss timer) is obtained according to the RRC signaling configuration.

[0371] The second timer can be found in the introduction of S604 and will not be described in detail.

[0372] Among them, the introduction of the first period is as follows:

[0373] Exemplarily, the starting time of the first duration is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, as described in S6031 for details, which will not be repeated here.

[0374] Exemplarily, the end time of the first duration is: the earlier of the end time of the first timer (or the packet loss timer) and the end time of the second timer.

[0375] For example, when the first time is earlier than (or equal to) the abandonment time (ie, the time indicated by the second information), the end time of the first duration is the end time of the second timer.

[0376] For another example, when the discarding moment (ie, the moment indicated by the second information) is earlier than or equal to the first moment, the end moment of the first duration is the end moment of the first timer (or packet loss timer).

[0377] That is, in response to receiving the first information, the first entity starts the second timer and then determines the first duration based on the values ​​of the first timer and the second timer. Because the second duration or first moment indicated by the first information can meet the synchronization requirements between the first and second data, when the second timer is started based on the first information, the duration of the second timer takes into account the synchronization requirements between the first and second data. Furthermore, the moment indicated by the second information enables the terminal device to learn the transmission delay requirements of the second data. When the first duration is determined based on the values ​​of the first timer (or packet loss timer) and the second timer, if the second data is transmitted within the first duration, synchronization between the first and second data is achieved, and the transmission delay requirements of the second data are met. In this case, when synchronization requirements exist between multiple types of data, the remaining transmission delay budget for the second data in the DSR MAC CE can be determined based on the first and second timers. For example, the MAC entity determines the remaining transmission delay budget for the second data in the DSR MAC CE based on the first and second timers.

[0378] In Solution 2, as a third example, as shown in FIG10 , the embodiment of the present application further includes S605:

[0379] S605: The first entity starts a second timer in response to receiving the first information.

[0380] The implementation process of S605 can refer to the introduction of S604 and will not be described in detail.

[0381] When the terminal device executes S605, as shown in FIG10 , S6034 includes S6034d:

[0382] S6034d. The first entity of the terminal device determines the first duration according to the end time of the first timer and the end time of the second timer.

[0383] Exemplarily, the end time of the first timer (or packet loss timer) is: the time of discard (i.e., the time indicated by the second information). It can be understood that the duration or end time of the first timer (or packet loss timer) is obtained according to the RRC signaling configuration. Please refer to the introduction of S6034c and will not be repeated here.

[0384] Exemplarily, the end time of the second timer is the first time, and reference may be made to the introduction of S604, which will not be repeated here.

[0385] Among them, the introduction of the first period is as follows:

[0386] Exemplarily, the starting time of the first duration is: the second time, wherein the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB, as described in S6034d for details.

[0387] Exemplarily, the end time of the first duration is: the earlier end time of the first timer (or packet loss timer) and the second timer. For details, see the introduction of S6034c and will not be repeated here.

[0388] That is, the first entity starts the second timer in response to receiving the first information, and then determines the first duration based on the end time of the first timer and the end time of the second timer. Since the second duration or the first time indicated by the first information can meet the synchronization requirements of the first data and the second data, in this way, the second timer is started based on the first information, and the duration of the second timer is a time that takes into account the synchronization requirements between the first data and the second data. In addition, the time indicated by the second information can enable the terminal device to know the transmission delay requirements of the second data. In this way, the first timer is started based on the second information, and the duration of the first timer is a time that takes into account the transmission requirements of the second data. In the case where the first duration is determined based on the end time of the first timer (or packet loss timer) and the end time of the second timer, if the second data is transmitted within the first duration, the synchronization of the first data and the second data can be achieved, and the transmission delay requirements of the second data can be met. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the second data in the DSR MAC CE can be determined based on the first timer and the second timer.

[0389] In some embodiments, as shown in the dotted box where “Case 1” is located in FIG11 , the communication method according to the embodiment of the present application further includes S611:

[0390] S611. The MAC entity of the terminal device sends a status report.

[0391] For example, the MAC entity of the terminal device sends a status report to the network device, where the status report includes the delay information of the second data. Correspondingly, the network device receives the status report from the terminal device.

[0392] The MAC entity of the terminal device is used to process the second data.

[0393] Taking Figure 7 as an example, when the first entity of the terminal device is the PDCP entity corresponding to the first DRB (such as PDCP entity 1 in Figure 7), the first entity provides the first duration to the MAC entity.

[0394] The status report is described as follows:

[0395] Exemplarily, the status report may be a DSR, which is described in detail in the glossary section and will not be repeated here.

[0396] Exemplarily, the delay information of the status report is determined based on the first duration. It can be understood that the status report includes the delay information of the second data, and the delay information of the second data is determined based on the first duration.

[0397] For example, if the latency information of the second data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on the first duration. For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the end time of the first duration.

[0398] For another example, the delay information of the second data is determined based on the stored duration. The stored duration is determined based on the first duration. For example, the starting time of the stored duration is the starting time of the first duration. The ending time of the stored duration is the sending time of the status report.

[0399] That is to say, when the terminal device reports the status report, the delay information of the second data carried in the status report is determined based on the first duration. Since the first duration refers to the duration of the synchronization requirement between the first data and the second data, the delay information determined based on the first duration also takes into account the synchronization requirement of the second data. This means that the terminal device can report "delay information that takes into account the synchronization requirements between different data" to the network device. Accordingly, if the network device schedules transmission resources for the terminal device based on the delay information so that the second data is transmitted within the first duration, the first data is synchronized with the second data, which helps to improve the user experience.

[0400] In some embodiments, as shown in the dotted box where "Case 2" is located in FIG11, the communication method of the embodiment of the present application further includes S612 and S613:

[0401] S612: The network device sends threshold information to the terminal device. Correspondingly, the terminal device receives the threshold information from the network device.

[0402] The threshold information is used to indicate a first threshold.

[0403] S613. The MAC entity of the terminal device determines to trigger a status report based on the first threshold and the first duration.

[0404] Exemplarily, the status report includes delay information of the second data, where the delay information of the second data is determined according to the first duration.

[0405] For example, if the delay information of the second data is the remaining transmission delay budget, the starting time of the remaining transmission delay budget is the current time of the system. It should be understood that the current time of the system changes over time. The current time of the system can be expressed in units of seconds, milliseconds, time slots, subframes, frames, etc., which are not limited in this application.

[0406] The end time of the remaining transmission delay budget is: the end time of the first duration. If the remaining transmission delay budget is less than or equal to the first threshold, the MAC entity triggers a status report. If the remaining transmission delay budget is greater than the first threshold, the MAC entity does not trigger a status report.

[0407] After the MAC entity of the terminal device triggers a status report, if there is an available uplink resource, if the triggering of the status report has not been canceled, or if the uplink resource cannot carry the data volume of all the data indicated by the status report, the status report is sent on the uplink resource. Accordingly, the network device receives the status report from the terminal device.

[0408] For example, the MAC entity and status report can be found in the introduction of S611 and will not be described in detail.

[0409] It can be understood that the triggering of the status report is determined based on the first duration. Since the first duration refers to the duration of the synchronization requirement between the first data and the second data, when the terminal device determines whether to trigger the status report with reference to the first duration, the network device can promptly schedule transmission resources for the terminal device based on the status report, so that the second data can be transmitted within the first duration as much as possible, thereby achieving the effect of synchronization between the first data and the second data, which helps to improve the user experience.

[0410] Next, for the second entity side, some operations of the second entity are introduced:

[0411] In some embodiments, as shown in FIG12 , the communication method 600 according to the embodiment of the present application further includes S621:

[0412] S621: The second entity starts a third timer in response to receiving the first data. For example, when the second entity of the terminal device receives the first data, the second entity starts the third timer.

[0413] In the present application, starting the third timer may be understood as starting or restarting the third timer.

[0414] Among them, the introduction of the third timer is as follows:

[0415] Exemplarily, the third timer may be a synchronization timer. For example, the synchronization timer corresponding to the second entity side is recorded as synchronization timer 0 or TX_SYNC_TIMER. Of course, the third timer may also have other names. This application uses the third timer as an example for description, and should not be understood as limiting this application.

[0416] Exemplarily, the start time of the third timer is: the reception time of the first data.

[0417] For example, when the second entity is the PDCP entity corresponding to the first DRB (such as PDCP entity 0 in Figure 7), the start time of the third timer is: the time when the PDCP entity corresponding to the first DRB receives the first data.

[0418] As a possible alternative, S621 may be replaced by the second entity starting a third timer in response to receipt of the indication information X.

[0419] The indication information X is used to instruct to start or restart the third timer.

[0420] Exemplarily, the indication information X may be control plane signaling, such as RRC layer signaling received by the terminal device from a network device. Alternatively, the indication information X may be user plane information, such as the indication information X carried by the first data. For example, if the first data is an SDU, the GTP-U header of the SDU carries the indication information X. Alternatively, the indication information X may be internal signaling of the terminal device, such as from the application layer of the terminal device. Exemplarily, the start time of the third timer may be the time when the first data is received or the time when the indication information X is received.

[0421] For example, taking the first data carrying indication information X as an example, the indication information X can be distinguished by different values. For example, when the indication information X is the first value, the second entity starts or restarts the third timer. Conversely, when the indication information X is the second value, the second entity does not need to start (or does not start or restart) the third timer.

[0422] Exemplarily, the indication information X may further indicate the time of starting or restarting the third timer. The time indicated by the indication information X may be earlier than, equal to, or later than the time of receiving the first data, which is not limited in this application.

[0423] It is easy to understand that under the above two methods of starting the third timer, the end time of the third timer is: the first time. The first time can be described in S602 and will not be repeated here. Alternatively, it can be described that the duration of the third timer is the second duration. The second duration can be described in S602 and will not be repeated here.

[0424] It is easy to understand that, in the present application, the duration or end time of the third timer can represent the synchronization requirement of the second data. In addition, the duration (i.e., the above-mentioned second duration) or end time (i.e., the above-mentioned first time) of the third timer can be indicated by the first information and provided to the PDCP entity corresponding to the second DRB, so that the PDCP entity corresponding to the second DRB can determine the duration for which the second data is expected to be transmitted. For details, see the introduction of S602 and S603, which will not be repeated here.

[0425] In some embodiments, as shown in FIG12 , the communication method 600 according to the embodiment of the present application further includes S622:

[0426] S622: The network device sends configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information from the network device.

[0427] The configuration information is used to configure the duration of the third timer to be the second duration. The second duration can be referred to in the introduction of S602 and will not be described in detail. That is, the network device configures the second duration for the terminal device.

[0428] For the terminal device, after the second entity of the terminal device obtains the configuration information, it sets the second duration configured in the configuration information as the duration of the third timer.

[0429] Example 2

[0430] An introduction is given by taking the example that the first entity is a MAC entity that processes the second data.

[0431] The communication method proposed in the embodiment of the present application is described in detail below with reference to FIG13a and FIG13b. The communication method 1300 proposed in the embodiment of the present application includes the following operations:

[0432] S1301. The terminal device obtains first data and second data.

[0433] For example, the terminal device can refer to the introduction of S601 and will not be described in detail.

[0434] For example, S1301 includes S1301a and S1301b:

[0435] S1301a. The first entity of the terminal device receives second data.

[0436] The first entity is described as follows:

[0437] The first entity may be a MAC entity that processes the second data, such as the MAC entity in FIG. 13b .

[0438] The second data can be found in the introduction of S601a and will not be described in detail.

[0439] In the case where the first entity is a MAC entity, taking the second DRB as DRB#1 as an example, data from different DRBs is aggregated to the MAC entity. Accordingly, the MAC entity receives the second data of DRB#1.

[0440] S1301b. The second entity of the terminal device receives the first data.

[0441] For S1301b, please refer to the introduction of S601b, which will not be described in detail.

[0442] For the second entity of the terminal device, after receiving the first data, the second entity executes S1302:

[0443] S1302: The second entity of the terminal device sends first information to the first entity. Correspondingly, the first entity receives the first information from the second entity.

[0444] In this application, the first entity in S602 is the PDCP entity corresponding to the second DRB. In S1302, the first entity is the MAC entity that processes the second data, i.e., the execution entities are different. Accordingly, when the first entity is the MAC entity, the second entity sends the first information to the MAC entity. Accordingly, the MAC entity receives the first information from the second entity.

[0445] The first information can be found in the introduction of S602 and will not be described in detail.

[0446] For the first entity of the terminal device, after receiving the first information, the first entity executes S1303:

[0447] S1303. The first entity of the terminal device determines a first duration based on the first information.

[0448] The first duration can be found in the introduction of S603 and will not be described in detail.

[0449] In this application, the first entity in S603 is the PDCP entity corresponding to the second DRB. In S1303, the first entity is the MAC entity that processes the second data, i.e., the execution entities are different. Accordingly, when the first entity is the MAC entity, the MAC entity determines the first duration based on the first information.

[0450] For example, the implementation process of S1303 is introduced in combination with two solutions (the following solution 3 and solution 4):

[0451] Solution 3: The first duration is determined based on the first information.

[0452] In solution 3, as a first example, S1303 includes the following operations:

[0453] First, the MAC entity of the terminal device determines the duration of the first timer based on the first information.

[0454] For example, the first timer is started at the second moment, ie, the moment when the second data arrives at the PDCP entity corresponding to the second DRB, and the first timer ends at the first moment.

[0455] Then, the MAC entity of the terminal device determines the first duration according to the duration of the first timer.

[0456] The starting time of the first duration is the second time, and the ending time of the first duration is the ending time of the first timer. Please refer to the introduction of S6032 and will not be repeated here.

[0457] In Solution 3, as a second example, the embodiment of the present application further includes the following operations:

[0458] First, the MAC entity of the terminal device starts or restarts the second timer in response to receiving the first information.

[0459] The second timer can be described in S604 and will not be described in detail. Then, S1303 includes the following operations: the MAC entity of the terminal device determines the first duration according to the value of the second timer.

[0460] The end time of the second timer is the first time, and reference may be made to the introduction of S6033, which will not be described in detail.

[0461] Among them, the starting moment of the first duration is the second moment, that is, the moment when the second data arrives at the PDCP entity corresponding to the second DRB. Please refer to the introduction of S6033 and will not be repeated here.

[0462] The end time of the first duration is the end time of the second timer.

[0463] Solution 4: The first duration is determined based on the first information and the second information.

[0464] In solution 4, S1303 includes the following operations:

[0465] The MAC entity of the terminal device determines the first duration based on the first information and the second information.

[0466] Among them, the second information indicates the time when the second data is discarded. Please refer to the introduction of S6034 and will not be repeated here.

[0467] It should be understood that for the MAC entity of the terminal device, the MAC entity can first receive the first information and then the second information, or first receive the second information and then the first information, or simultaneously receive the first information and the second information. The embodiments of the present application do not limit this.

[0468] Among them, the starting time of the first duration is: the second time, that is, the time when the second data arrives at the PDCP entity corresponding to the second DRB. For details, please see the introduction of S6034 and will not be repeated here.

[0469] The end time of the first duration is the earlier of the first time and the discarding time (ie, the time indicated by the second information). For details, please refer to the introduction of S6034 and will not be repeated here.

[0470] In solution 4, as a first example, S1303 includes the following operations:

[0471] First, the MAC entity of the terminal device determines the duration of the first timer based on the first information and the second information.

[0472] Among them, the start time of the first timer (or packet loss timer) is: the second moment, that is, the moment when the second data arrives at the PDCP entity corresponding to the second DRB. Please refer to the introduction of S6031 and will not repeat it here.

[0473] Among them, the end time of the first timer (or packet loss timer) is: the earlier time between the first time and the time of discarding (that is, the time indicated by the second information). Please refer to the introduction of S6034a and will not be repeated here.

[0474] Then, the MAC entity of the terminal device determines the first duration according to the duration of the first timer.

[0475] Among them, the starting moment of the first duration is: the second moment, that is, the second moment is the moment when the second data arrives at the PDCP entity corresponding to the second DRB. For details, please see the introduction of S6031 and will not be repeated here.

[0476] The end time of the first duration is the end time of the first timer (or packet loss timer). For details, see the introduction of S6034b and will not be repeated here.

[0477] In Solution 4, as a second example, the embodiment of the present application further includes the following operations:

[0478] First, the MAC entity starts a second timer in response to receiving the first information.

[0479] The second timer can be described in S604 and will not be described in detail.

[0480] Then, S1303 includes the following operations:

[0481] The MAC entity of the terminal device determines the first duration based on the value of the first timer and the value of the second timer.

[0482] Among them, the start time of the first timer (or packet loss timer) is: the second moment, that is, the moment when the second data arrives at the PDCP entity corresponding to the second DRB. Please refer to the introduction of S6031 and will not repeat it here.

[0483] Among them, the end time of the first timer (or packet loss timer) is: the time of discarding (that is, the time indicated by the second information). Please refer to the introduction of S6034c and will not be repeated here.

[0484] Among them, the starting time of the first duration is: the second time, that is, the time when the second data arrives at the PDCP entity corresponding to the second DRB. For details, please see the introduction of S6031 and will not be repeated here.

[0485] The end time of the first duration is: the earlier of the end time of the first timer (or packet loss timer) and the end time of the second timer. For details, please refer to the introduction of S6034c and will not be repeated here.

[0486] In Solution 4, as a third example, the embodiment of the present application further includes the following operations:

[0487] First, the MAC entity starts a second timer in response to receiving the first information.

[0488] The second timer can be described in S605 and will not be described in detail.

[0489] Then, S1303 includes the following operations: the MAC entity of the terminal device determines the first duration according to the end time of the first timer and the end time of the second timer.

[0490] Among them, the first timer and the second timer can be referred to the introduction of the second example of Solution 4, and will not be repeated here.

[0491] Among them, the starting time of the first duration is: the second time, that is, the time when the second data arrives at the PDCP entity corresponding to the second DRB. For details, please see the introduction of S6034d and will not be repeated here.

[0492] The end time of the first duration is the earlier of the end times of the first timer (or packet loss timer) and the second timer. For details, please refer to the introduction of S6034c and will not be repeated here.

[0493] In Solution 4, as a fourth example, the embodiment of the present application further includes the following operations:

[0494] First, the PDCP entity starts a third timer in response to receiving the first information.

[0495] The third timer can be described in S621 and will not be described in detail. For example, the second entity starts the third timer in response to receiving the first data.

[0496] Then, S1303 includes the following operations: the MAC entity of the terminal device determines the first duration according to the end time of the first timer and the end time of the third timer.

[0497] Among them, the first timer can be referred to the introduction of the first example of Solution 4, which will not be repeated here.

[0498] The start time of the third timer is: the time when the first data is received, or the time when the first data arrives at the first DRB. The end time of the third timer is the first time.

[0499] Among them, the starting time of the first duration is: the second time, that is, the time when the second data arrives at the PDCP entity corresponding to the second DRB. For details, please see the introduction of S6034d and will not be repeated here.

[0500] The end time of the first duration is: the earlier end time of the first timer (or packet loss timer) and the third timer.

[0501] In some embodiments, after the MAC entity determines the first duration, it sends a status report. For details, see the introduction of S611 and will not be repeated here.

[0502] In some embodiments, after the MAC entity determines the first duration, the MAC entity of the terminal device triggers a status report based on the first duration, such as triggering a status report based on the first duration and the first threshold. For details, see the introduction of S612 and S613 and will not be repeated here.

[0503] In some embodiments, on the second entity side, the second entity starts a third timer in response to receiving the first data. For details, see the introduction of S621 and will not be repeated here.

[0504] Example 3

[0505] The following is introduced by taking the case where the third entity is the PDCP entity corresponding to the third DRB as an example.

[0506] As shown in FIG14 , the communication method 1400 proposed in this embodiment of the present application includes the following operations:

[0507] S1401. A third entity of the terminal device receives third data.

[0508] The third entity is introduced as follows:

[0509] For example, the third entity may be the PDCP entity corresponding to the third DRB. Taking Figure 15 as an example, the third DRB is DRB#2.

[0510] It should be understood that the third entity may also be other entities corresponding to the third DRB, such as an SDAP entity, an RLC entity, etc. In the communication method 1400 of the present application, the third entity is introduced by taking the PDCP entity as an example.

[0511] Among them, the third data is introduced as follows:

[0512] In this application, the third data belongs to the third DRB. It can be understood that the third data is transmitted via the third DRB. For example, the third data is transmitted from the PDCP entity corresponding to the third DRB to the RLC entity corresponding to the third DRB.

[0513] Illustratively, the third data may be a PDU, a PDU set, or a data burst. For details, please refer to the introduction in the glossary section and will not be repeated here.

[0514] Exemplarily, the third data may be visual data, or tactile data, or audio data.

[0515] Taking Figure 4 as an example, the third data may be tactile data. Taking Figure 8 as an example, the third data may be visual data. Taking Figure 15 as an example, the third data may be Data#2. Figures 4 and 8 illustrate the synchronization requirements for video data and tactile data.

[0516] In the case where the third entity is a PDCP entity, taking the third data as an SDU as an example, S1401 includes: the PDCP entity corresponding to the third DRB (ie, the third entity) receives an SDU.

[0517] Optionally, in response to receiving the third data, some related operations of the third entity are introduced:

[0518] In some embodiments, as shown in FIG14 , the communication method 1400 according to the embodiment of the present application further includes S1402:

[0519] (Optionally) S1402. The third entity of the terminal device starts a fourth timer in response to receiving the third data.

[0520] For example, when the third entity receives the third data, the third entity of the terminal device starts a fourth timer.

[0521] In the present application, starting the fourth timer may be understood as starting or restarting the fourth timer.

[0522] Among them, the fourth timer is introduced as follows:

[0523] Exemplarily, the fourth timer may be a synchronization timer. Of course, the fourth timer may also have other names. This application is introduced using the fourth timer as an example, which should not be understood as limiting this application.

[0524] The start time of the fourth timer is as follows:

[0525] Exemplarily, the fourth timer is started at the time of receiving the third data.

[0526] For example, when the third entity is the PDCP entity corresponding to the third DRB, the fourth timer is started at the time when the PDCP entity corresponding to the third DRB receives the third data. It can be understood that there is a fourth timer for the PDCP entity corresponding to the third DRB. Each time a piece of third data is received, the fourth timer is started or restarted.

[0527] Taking FIG. 4 as an example, the start time of the fourth timer may be 0 ms.

[0528] The duration or end time of the fourth timer is as follows:

[0529] Exemplarily, the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time. The start time of the third duration is the time when the third data arrives at the PDCP entity corresponding to the third DRB. The third time is the end time of the third duration.

[0530] Taking Figure 4 as an example, the third duration may be the duration between 0ms and 20ms, as shown by the dotted box where the 'synchronization requirement' is located. The third moment is 20ms, ie, the end moment of the dotted box where the 'synchronization requirement' is located.

[0531] In this application, the third duration can be understood as, when the third data arrives at the terminal device first, the fourth data is transmitted within the third duration, starting from the moment the third data arrives at the terminal device, so that the third data is synchronized with the fourth data. Conversely, if the fourth data is not transmitted within the third duration, the third data and the fourth data are out of sync, affecting the user experience. The moment the third data arrives at the terminal device can be understood as the moment the third data arrives at the PDCP entity corresponding to the third DRB.

[0532] It is easy to understand that, as an example, the third duration can be semi-statically configured or pre-configured, for example, indicated to the third DRB (or third entity) through high-layer signaling or core network signaling. Exemplarily, the value of the third duration can be determined according to Table 1, and the description of the determination process of the second duration can be referred to.

[0533] As a possible alternative, S1402 may be replaced by the third entity starting the fourth timer in response to receiving the indication information Y. The indication information Y is used to instruct to start or restart the fourth timer.

[0534] Exemplarily, the indication information Y may be control plane signaling, such as RRC layer signaling received by the terminal device from the network device. Alternatively, the indication information Y may be user plane information, such as the indication information Y carried by the third data. Taking the third data as an SDU as an example, the GTP-U packet header of the SDU carries the indication information Y. Alternatively, the indication information Y may be internal signaling of the terminal device, such as from the application layer of the terminal device. That is, exemplarily, the start time of the fourth timer may be the time of receiving the third data or the time of receiving the indication information Y.

[0535] For example, taking the third data carrying indication information Y as an example, the indication information Y can be distinguished by different values. For example, when the indication information Y is a first value, the third entity starts or restarts the fourth timer. Conversely, when the indication information Y is a second value, the third entity does not need to start (or does not start or restart) the fourth timer.

[0536] Exemplarily, the indication information Y may further indicate the time of starting or restarting the fourth timer. The time indicated by the indication information Y may be earlier than, equal to, or later than the time of receiving the third data, which is not limited in this application.

[0537] It should be added that, when the third entity starts the fourth timer in response to receiving the indication information Y, the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time.

[0538] Optionally, the duration of the fourth timer can be configured by the network device. For example, the network device sends configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information from the network device. The configuration information is used to configure the duration of the fourth timer to be the third duration. In other words, the network device configures the third duration for the terminal device. Upon receiving the configuration information, the third entity of the terminal device sets the third duration configured in the configuration information as the duration of the fourth timer.

[0539] S1403. The third entity of the terminal device determines the third information.

[0540] The third information is introduced as follows:

[0541] The third information includes a third duration or a third moment, wherein the starting moment of the third duration is the moment when the third data arrives at the PDCP entity corresponding to the third DRB, and the third moment is the ending moment of the third duration, as described in S1402.

[0542] Exemplarily, when S1402 is executed, the third entity determines the third information according to the fourth timer.

[0543] It is easy to understand that, on the third entity side, as an example, when the third entity receives the third data, the third entity determines the third information based on the third data. In other words, the third information is related to the third data, and it can be understood that the third data can trigger the determination of the third information.

[0544] As another example, when the third entity receives indication information Y, the third entity determines the third information. In other words, the third information is related to information Y, which can be understood as information Y triggering the determination of the third information. The indication information Y can be found in the description of S1402 and will not be further described.

[0545] S1404. The third entity of the terminal device receives fourth data.

[0546] Among them, the fourth data is introduced as follows:

[0547] In this application, the fourth data also belongs to the third DRB.

[0548] Illustratively, the fourth data may be a PDU, a PDU set, or a data burst. For details, please refer to the introduction in the glossary section and will not be repeated here.

[0549] In some embodiments, the fourth data may be SDU-granular, i.e., each SDU arriving at the third PDCP entity (i.e., the PDCP entity corresponding to the third DRB) may be considered as one piece of fourth data. Alternatively, the fourth data may not be SDU-granular, for example, an SDU after every several SDUs may be considered as one piece of fourth data. For details, please refer to the introduction of S601b and will not be repeated here.

[0550] Exemplarily, the fourth data may be visual data, or tactile data, or audio data.

[0551] Taking Figure 4 as an example, the fourth data may be visual data. Taking Figure 8 as an example, the fourth data may be tactile data. Taking Figure 15 as an example, the fourth data may be Data#1.

[0552] Exemplarily, taking the fourth data as an SDU as an example, S1404 includes: the PDCP entity corresponding to the third DRB receives an SDU.

[0553] It is easy to understand that the terminal device may execute S1401 first and then execute S1404. In other words, the third data arrives at the terminal device first and the fourth data arrives at the terminal device later.

[0554] It is easy to understand that when S1402 is executed, the terminal device can execute S1402 and S1404 at the same time, or execute S1402 first and then S1404, or execute S1404 first and then S1402. This application does not limit this.

[0555] It is easy to understand that the terminal device can execute S1403 and S1404 at the same time, or execute S1403 first and then S1404, or execute S1404 first and then S1403. This application does not limit this.

[0556] It is easy to understand that the first, third and fourth data can be different types of data. For example, the third data is video data and the fourth data is audio data. For another example, the third data is video data and the fourth data is tactile data. For another example, the third data is audio data and the fourth data is tactile data. Second, there is a synchronization requirement between the third data and the fourth data. For example, in the process of determining the expected transmission time of the fourth data (such as the fourth time period described below), it is necessary to refer to the third data. See the introduction of S1405 for details:

[0557] S1405. The third entity of the terminal device determines a fourth duration based on the third information.

[0558] Among them, the introduction of the fourth period is as follows:

[0559] In this application, the fourth duration is the duration during which the fourth data is expected to be transmitted. It can be understood that the fourth duration is determined with reference to the synchronization requirement between the third data and the fourth data.

[0560] Taking Figure 4 as an example, the fourth data is visual data. The fourth duration starts at 5 ms, i.e., when the visual data arrives at the terminal device, or when the fourth data arrives at the PDCP entity corresponding to the third DRB. The fourth duration ends at the end of the third duration, i.e., 20 ms. If the fourth data is transmitted within the fourth duration, the third and fourth data are synchronized.

[0561] It should be understood that the fourth duration may also have other names, such as the effective transmission duration of the fourth data, or the transmission delay budget of the fourth data. The embodiment of the present application takes the fourth duration as an example for introduction.

[0562] Next, we will introduce the process of determining the fourth duration:

[0563] Solution 1: The fourth duration is determined based on the third information.

[0564] In solution 1, as shown in FIG16 , S1405 includes S14051 and S14052:

[0565] S14051. The third entity of the terminal device determines the duration of the fifth timer based on the third information.

[0566] Among them, the introduction of the fifth timer is as follows:

[0567] Exemplarily, when the fifth timer times out, the terminal device discards the fourth data. In other words, the moment the fifth timer times out is the moment the fourth data is discarded. The fifth timer may be a packet loss timer. It should be understood that as communication technologies evolve, packet loss timers may have other names. This application uses the packet loss timer as an example, and this should not be construed as limiting this application.

[0568] Exemplarily, the start time of the fifth timer (or packet loss timer) is the fourth time. The fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB. Taking Figure 4 as an example, the fourth data is visual data, and the fourth time is 5 ms.

[0569] Exemplarily, the end time of the fifth timer (or packet loss timer) is the third time. For the third time, please refer to the introduction of S1402 and will not be repeated here. It can be understood that in related technologies, the duration or end time of the fifth timer (or packet loss timer) is obtained by configuring high-layer signaling (such as RRC signaling). In the present application, the end time of the fifth timer (or packet loss timer) is obtained from the third information.

[0570] In other words, taking the execution of S1402 as an example, it can be understood that the value of the fifth timer (or packet loss timer) refers to the real-time value of the fourth timer (or synchronization timer). For example, the real-time value of the fourth timer (or synchronization timer) is assigned to the fifth timer (or packet loss timer). In other words, the value of the fifth timer (or packet loss timer) is not obtained by higher-layer signaling (such as RRC signaling), but is determined based on the fourth timer (or synchronization timer).

[0571] Among them, the real-time value of the fourth timer (or synchronization timer) can be understood as: the current value of the fourth timer (or synchronization timer) when the fifth timer (or packet loss timer) is turned on; or, the current value of the fourth timer (or synchronization timer) when the fourth data arrives at the terminal device.

[0572] S14052. The third entity of the terminal device determines a fourth duration based on the duration of the fifth timer.

[0573] Among them, the introduction of the fourth period is as follows:

[0574] Exemplarily, the starting time of the fourth duration is: the fourth time. The fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB. Please refer to the introduction of S14051 and no further details will be given.

[0575] For example, the end time of the fourth duration is the end time of the fifth timer (or packet loss timer). The end time of the fifth timer (or packet loss timer) can be found in the introduction of S14051 and will not be described in detail.

[0576] That is to say, the terminal device updates the duration of the fifth timer (or packet loss timer) according to the third information, and then determines the fourth duration according to the duration of the fifth timer (or packet loss timer). Since the third duration or third moment indicated by the third information can meet the synchronization requirements of the third data and the fourth data, the duration of the fifth timer (or packet loss timer) determined based on the third information is a duration that takes into account the synchronization requirements between the third data and the fourth data. In the case where the fourth duration is determined based on the duration of the fifth timer (or packet loss timer), if the fourth data is transmitted within the fourth duration, the synchronization of the third data and the fourth data can be achieved. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the fourth data in the DSR MAC CE can be determined based on the updated fifth timer (or packet loss timer).

[0577] Solution 2: The fourth duration is determined based on the third information and the fourth information.

[0578] In solution 2, as shown in FIG17 , S1405 includes S14053:

[0579] S14053. The third entity of the terminal device determines a fourth duration based on the third information and the fourth information.

[0580] The fourth information is introduced as follows:

[0581] In the present application, the fourth information indicates a time point when the fourth data is discarded.

[0582] Exemplarily, the fourth information may be RRC signaling, see the introduction in the glossary section, which will not be repeated here.

[0583] Exemplarily, the fourth information comes from the network device, that is, the fourth information is information sent by the network device to the terminal device.

[0584] It should be understood that, for the third entity of the terminal device, the third entity may first receive the fourth information and then determine the third information.

[0585] Among them, the introduction of the fourth period is as follows:

[0586] Exemplarily, the starting time of the fourth duration is: the fourth time. The fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB. For details, see the introduction of S14051 and will not be repeated here.

[0587] Exemplarily, the end time of the fourth duration is: the earlier time between the third time and the time of discarding (ie, the time indicated by the fourth information).

[0588] For example, when the third moment is earlier than the moment of abandonment (ie, the moment indicated by the fourth information), the end moment of the fourth duration is the third moment.

[0589] Taking FIG4 as an example, the third moment is 20 ms, the discarding moment (ie, the moment indicated by the fourth information) is 35 ms, and the end moment of the fourth duration is the third moment, ie, 20 ms.

[0590] For another example, when the moment of abandonment (ie, the moment indicated by the fourth information) is earlier than or equal to the third moment, the end moment of the fourth duration is the moment of abandonment (ie, the moment indicated by the fourth information).

[0591] Taking FIG8 as an example, the third moment is 30 ms, the discarding moment (ie, the moment indicated by the fourth information) is 10 ms. The end moment of the fourth duration is the discarding moment (ie, the moment indicated by the fourth information), ie, 10 ms.

[0592] That is to say, in the process of determining the fourth duration, the terminal device refers to both the third information and the fourth information. When the fourth duration is determined with reference to the third information, since the third duration or third moment indicated by the third information can meet the synchronization requirements of the third data and the fourth data, when the fourth duration is determined based on the third information, if the fourth data is transmitted within the fourth duration, the synchronization of the third data and the fourth data can be achieved. Moreover, when the fourth duration is determined with reference to the fourth information, since the moment indicated by the fourth information can enable the terminal device to know the transmission delay requirements of the fourth data, when the fourth duration is determined based on the fourth information, if the fourth data is transmitted within the fourth duration, the transmission delay requirements of the fourth data can be met.

[0593] In solution 2, as a possible example, as shown in FIG17 , S14053 includes S14053a and S14053b:

[0594] S14053a. The third entity of the terminal device determines the duration of the fifth timer based on the third information and the fourth information.

[0595] Among them, the introduction of the fifth timer is as follows:

[0596] Exemplarily, the fifth timer may be a packet loss timer, for which reference may be made to the introduction of S14051 and will not be described in detail.

[0597] Exemplarily, the start time of the fifth timer (or packet loss timer) is: the fourth time. The fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB. Please refer to the introduction of S14051 and no further details will be given.

[0598] Exemplarily, the end time of the fifth timer (or packet loss timer) is: the earlier time between the third time and the time of discarding (ie, the time indicated by the fourth information).

[0599] For example, when the third moment is earlier than (or equal to) the discarding moment (ie, the moment indicated by the fourth information), the end moment of the fifth timer (or packet loss timer) is the third moment.

[0600] For example, when the discarding moment (ie, the moment indicated by the fourth information) is earlier than or equal to the third moment, the end moment of the fifth timer (or packet loss timer) is the discarding moment (ie, the moment indicated by the fourth information).

[0601] It can be understood that, in the related art, the end time of the fifth timer (or packet loss timer) is obtained by RRC signaling configuration. In the present application, the end time of the fifth timer (or packet loss timer) is obtained by the third information and the fourth information. The fourth information can be information in the above-mentioned high-layer signaling (such as RRC signaling), such as the indication of the time when the fourth data is discarded.

[0602] In other words, taking the execution of S1402 as an example, it can be understood that whether the fifth timer (or packet loss timer) is updated depends on the smaller value of the real-time value of the fourth timer (or synchronization timer) and the real-time value of the fifth timer (or packet loss timer).

[0603] Specifically, taking the end time of the fifth timer (or packet loss timer) configured by RRC signaling as an example, the value of the fifth timer (or packet loss timer) when it is started is configured by RRC signaling. When the real-time value of the fourth timer (or synchronization timer) is less than the real-time value of the fifth timer (or packet loss timer), the fifth timer (or packet loss timer) is updated, such as assigning the real-time value of the fourth timer (or synchronization timer) to the fifth timer (or packet loss timer). Conversely, when the real-time value of the fourth timer (or synchronization timer) is greater than or equal to the real-time value of the fifth timer (or packet loss timer), there is no need to update the fifth timer (or packet loss timer), and the real-time value of the fifth timer (or packet loss timer) remains unchanged.

[0604] S14053b. The third entity of the terminal device determines the fourth duration according to the duration of the fifth timer.

[0605] Among them, the introduction of the fourth period is as follows:

[0606] Exemplarily, the starting time of the fourth duration is: the fourth time. The fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB. For details, see the introduction of S14051 and will not be repeated here.

[0607] Exemplarily, the end time of the fourth duration is the end time of the fifth timer (or packet loss timer). The end time of the fifth timer (or packet loss timer) can be found in the introduction of S14053a and will not be described in detail.

[0608] That is to say, the terminal device updates the duration of the fifth timer (or packet loss timer) based on the third information and the fourth information, and then determines the fourth duration based on the duration of the fifth timer (or packet loss timer). Since the third duration or third moment indicated by the third information can meet the synchronization requirements of the third data and the fourth data, and the moment indicated by the fourth information can enable the terminal device to know the transmission delay requirements of the fourth data, in this way, the duration of the fifth timer (or packet loss timer) determined based on the third information and the fourth information takes into account both the synchronization requirements between the third data and the fourth data and the transmission delay requirements of the fourth data. In the case where the fourth duration is determined based on the duration of the fifth timer (or packet loss timer), if the fourth data is transmitted within the fourth duration, the synchronization of the third data and the fourth data can be achieved, and the transmission delay requirements of the fourth data can be met. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the fourth data in the DSR MAC CE can be determined based on the updated fifth timer (or packet loss timer).

[0609] In some embodiments, the MAC entity of the terminal device also sends a status report. The delay information included in the status report is determined based on the fourth duration, as described in S1411-S1412 in Figure 18 for details:

[0610] S1411. The MAC entity of the terminal device obtains a fourth duration.

[0611] For example, after the third entity of the terminal device executes S1405, the third entity sends indication information of the fourth duration to the MAC entity. Accordingly, the MAC entity receives the indication information of the fourth duration from the third entity. The indication information of the fourth duration may indicate the end time of the fourth duration. Alternatively, the indication information of the fourth duration may indicate the start time of the fourth duration and the duration of the fourth duration.

[0612] For another example, after the third entity of the terminal device executes S1403, the third entity sends third information to the MAC entity. Accordingly, the MAC entity receives the third information from the third entity. The MAC entity determines a fourth duration based on the third information. For example, the fourth duration is determined based on the third information, or the fourth duration is determined based on the third information and the fourth information. For details, see the introduction to S1405, which will not be repeated here. Furthermore, in this case, it can be understood that the third entity does not execute S1405.

[0613] S1412. The MAC entity of the terminal device sends a status report.

[0614] For example, the content of the status report is as follows:

[0615] As a possible description: the status report includes delay information of the fourth data, and the delay information of the fourth data is determined according to the fourth duration.

[0616] For example, if the latency information of the fourth data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on the fourth duration. For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the end time of the fourth duration.

[0617] For another example, the delay information of the fourth data is determined based on the stored duration. The stored duration is determined based on the fourth duration. For example, the starting time of the stored duration is the starting time of the fourth duration. The ending time of the stored duration is the sending time of the status report.

[0618] As another possible description, taking the fifth timer (e.g., packet loss timer) as an example, the status report includes latency information of the fourth data. The latency information of the fourth data is determined based on the fifth timer (e.g., packet loss timer). The fifth timer (e.g., packet loss timer) can be found in the description of S14051 or S14053a and is not further described here.

[0619] For example, if the delay information of the fourth data is a remaining transmission delay budget, the starting time of the remaining transmission delay budget is: the sending time of the status report, such as the sending time of the initial transmission. The ending time of the remaining transmission delay budget is: the ending time of the fifth timer (such as the packet loss timer).

[0620] For another example, the latency information of the fourth data is determined based on a stored duration, where the stored duration is determined based on the first duration. For example, the start time of the stored duration is the start time of a fifth timer (e.g., a packet loss timer). The end time of the stored duration is the time when the status report is sent.

[0621] That is to say, when the terminal device reports the status report, the delay information of the fourth data carried in the status report is determined based on the fourth time length. Since the fourth time length refers to the duration of the synchronization requirement between the third data and the fourth data, the delay information determined based on the fourth time length (such as the delay information of the fourth data) also takes into account the synchronization requirement of the fourth data. This means that the terminal device can report to the network device 'delay information that takes into account the synchronization requirements between different data'. Accordingly, if the network device schedules transmission resources for the terminal device based on the delay information so that the fourth data is transmitted within the fourth time length, the third data is synchronized with the fourth data, which helps to improve the user experience.

[0622] Exemplarily, on the other hand, the triggering of the status report is described as follows:

[0623] As a possible description: the MAC entity of the terminal device triggers a status report according to the fourth time duration.

[0624] Exemplarily, the MAC entity triggers a status report according to delay information of the fourth data, wherein the delay information of the fourth data is determined according to a fourth duration.

[0625] For example, if the delay information of the fourth data is the remaining transmission delay budget, the starting time of the remaining transmission delay budget is the current time of the system. It should be understood that the current time of the system changes over time. The current time of the system can be expressed in units of seconds, milliseconds, time slots, subframes, frames, etc., which are not limited in this application.

[0626] The end time of the remaining transmission delay budget is: the end time of the fourth duration. When the remaining transmission delay budget is less than or equal to the first threshold, the MAC entity triggers a status report. When the remaining transmission delay budget is greater than the first threshold, the MAC entity does not trigger a status report. The first threshold can be found in the introduction of S612 and S613 and will not be repeated here.

[0627] As another possible description: Taking the fifth timer (e.g., packet loss timer) as an example, the triggering of the status report is determined based on the fifth timer (e.g., packet loss timer). For example, the triggering of the status report is determined based on the real-time value of the fifth timer (e.g., packet loss timer). The fifth timer (e.g., packet loss timer) can be found in the introduction to S14051 or S14053a and will not be further described.

[0628] In other words, the triggering of the status report is determined based on the fourth time duration. Since the fourth time duration refers to the time duration required for synchronization between the third data and the fourth data, when the terminal device determines whether to trigger the status report based on the fourth time duration, the network device can promptly schedule transmission resources for the terminal device based on the status report, so that the fourth data can be transmitted within the fourth time duration as much as possible, thereby achieving the effect of synchronization between the third data and the fourth data, which helps to improve the user experience.

[0629] Example 4

[0630] The following is introduced by taking the case where the third entity is the PDCP entity corresponding to the third DRB as an example.

[0631] As shown in FIG19 , the communication method 1400 proposed in this embodiment of the present application includes the following operations:

[0632] S1401. A third entity of the terminal device receives third data.

[0633] (Optionally) S1402. The third entity of the terminal device starts a fourth timer in response to receiving the third data.

[0634] S1403: The third entity of the terminal device determines third information, wherein the third information includes a third duration or a third time.

[0635] S1404. The third entity of the terminal device receives fourth data.

[0636] (Optionally) S1421. The third entity of the terminal device starts an eighth timer in response to receiving the fourth data.

[0637] For example, when the third entity receives the fourth data, the third entity of the terminal device starts an eighth timer.

[0638] In the present application, starting the eighth timer may be understood as starting or restarting the eighth timer.

[0639] Among them, the introduction of the eighth timer is as follows:

[0640] Exemplarily, the eighth timer may be a packet loss timer. Of course, the eighth timer may also have other names. This application is introduced using the eighth timer as an example, which should not be understood as limiting this application.

[0641] The start time of the eighth timer is as follows:

[0642] Exemplarily, the start time of the eighth timer is: the reception time of the fourth data.

[0643] For example, when the third entity is the PDCP entity corresponding to the third DRB, the start time of the eighth timer is: the time when the PDCP entity corresponding to the third DRB receives the fourth data. It can be understood that there is an eighth timer for the PDCP entity corresponding to the third DRB. Each time a fourth data is received, the eighth timer is started or restarted.

[0644] Taking FIG. 4 as an example, the start time of the eighth timer may be 5 ms.

[0645] The end time of the eighth timer is as follows:

[0646] Exemplarily, the end time of the eighth timer is indicated by higher layer signaling (such as RRC signaling).

[0647] For the third entity, after determining the third information, the third entity executes S1422:

[0648] S1422: The third entity of the terminal device sends third information to the MAC entity. Correspondingly, the MAC entity receives the third information from the third entity.

[0649] S1423. The MAC entity of the terminal device sends a status report based on the third information.

[0650] Exemplarily, the MAC entity determines a fourth duration based on the third information and sends a status report based on the fourth duration. The fourth duration is the duration during which the fourth data is expected to be transmitted. For example, the end time of the fourth duration is the third time.

[0651] Alternatively, illustratively, the fourth duration (such as the transmission delay budget of the fourth data) is determined based on the fourth timer (such as the synchronization timer) and the eighth timer (such as the packet loss timer). For example, the fourth duration (such as the transmission delay budget of the fourth data) depends on the smaller value of the real-time value of the eighth timer (such as the packet loss timer) and the real-time value of the fourth timer (such as the synchronization timer). Specifically, when the real-time value of the eighth timer (such as the packet loss timer) is less than (or equal to) the real-time value of the fourth timer (such as the synchronization timer), the fourth duration (such as the transmission delay budget of the fourth data) can be determined based on the real-time value of the eighth timer (such as the packet loss timer). Conversely, when the real-time value of the fourth timer (such as the synchronization timer) is less than (or equal to) the real-time value of the eighth timer (such as the packet loss timer), the fourth duration (such as the transmission delay budget of the fourth data) can be determined based on the real-time value of the fourth timer (such as the synchronization timer). Among them, the fourth timer (such as the synchronization timer) can refer to the introduction of S1402, and the eighth timer (such as the packet loss timer) can refer to the introduction of S1421, which will not be repeated here.

[0652] For example, the content of the status report is as follows:

[0653] As a possible description: the status report includes delay information of the fourth data, the delay information of the fourth data is determined according to the third information, or the delay information of the fourth data is determined according to the fourth duration.

[0654] For example, if the latency information of the fourth data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on the fourth duration. For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the end time of the fourth duration.

[0655] Alternatively, it can be understood that the remaining transmission delay budget is determined based on the third information. For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is determined based on the third information, such as the ending time of the remaining transmission delay budget is the third time indicated by the third information.

[0656] For another example, if the latency information of the fourth data is the stored duration, the stored duration is determined based on the fourth duration. For example, the start time of the stored duration is the start time of the fourth duration, and the end time of the stored duration is the time when the status report is sent.

[0657] As another possible description: taking the fourth timer (such as the synchronization timer) as an example, the status report includes delay information of the fourth data, and the delay information of the fourth data is determined according to the fourth timer (such as the synchronization timer).

[0658] For example, if the delay information of the fourth data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on a fourth timer (e.g., a synchronization timer). For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the ending time of the fourth timer (e.g., the synchronization timer).

[0659] In other words, when a terminal device submits a status report, the latency information for the fourth data included in the status report is determined based on the third information. Because the third information can characterize the synchronization requirements between the third and fourth data, the latency information determined based on the third information also takes into account the synchronization requirements for the fourth data. This means that the terminal device can report latency information that takes into account the synchronization requirements between different data types to the network device. Accordingly, if the network device schedules transmission resources for the terminal device based on the latency information, synchronizing the third and fourth data, this helps improve the user experience.

[0660] Exemplarily, on the other hand, the triggering of the status report is described as follows:

[0661] As a possible description: the MAC entity of the terminal device triggers a status report according to the fourth time duration.

[0662] Exemplarily, the status report includes delay information of the fourth data, and the delay information of the fourth data is determined based on the fourth duration. Taking the delay information of the fourth data as the remaining transmission delay budget as an example, the starting moment of the remaining transmission delay budget is: the current moment of the system. It should be understood that the current moment of the system changes with time. Among them, the unit of the current moment of the system can be one of the following: seconds, milliseconds, time slots, subframes, frames, etc., which is not limited in this application. The end moment of the remaining transmission delay budget is: the end moment of the fourth duration. When the remaining transmission delay budget is less than or equal to the first threshold, the MAC entity triggers a status report. When the remaining transmission delay budget is greater than the first threshold, the MAC entity does not trigger a status report.

[0663] Among them, the fourth duration is determined based on the third information, which can also be understood as: the MAC entity of the terminal device triggers a status report based on the third information.

[0664] As another possible description: Taking the fourth timer (such as the synchronization timer) as an example, the triggering of the status report is determined based on the fourth timer (such as the synchronization timer). For example, the triggering of the status report is determined based on the real-time value of the fourth timer (such as the synchronization timer).

[0665] In other words, the triggering of the status report is determined based on the third information. Since the third information can represent the synchronization requirement between the third data and the fourth data, when the terminal device triggers the sending of the status report based on the third information, the network device can promptly schedule transmission resources for the terminal device based on the status report, so as to achieve the synchronization effect between the third data and the fourth data, thereby helping to improve the user experience.

[0666] Example 5

[0667] The fourth entity determines the synchronization information (fifth information described below) as an example for introduction.

[0668] First, the data transmission process is described as follows:

[0669] In the fifth embodiment, data enters the access layer of the terminal device in the form of a QoS flow. For example, the data first passes through the non-access stratum (NAS) and then through the SDAP layer to enter different DRBs. The SDAP layer is used to map data of different QoS flows to different DRBs.

[0670] Then, with reference to FIG20 , the communication method 2000 proposed in the embodiment of the present application is introduced as follows:

[0671] S2001. The fourth entity of the terminal device obtains fifth data.

[0672] Among them, the fourth entity is the NAS layer entity, as shown in Figure 21.

[0673] Exemplarily, the fifth data may be visual data, or tactile data, or audio data.

[0674] Exemplarily, the fourth entity obtains the fifth data, which can be understood as the fifth data reaching the fourth entity.

[0675] Optionally, in response to receiving the fifth data, some related operations of the fourth entity are introduced:

[0676] In some embodiments, as shown in FIG. 20 , the communication method 2000 according to the embodiment of the present application further includes S2002:

[0677] (Optionally) S2002. The fourth entity of the terminal device starts a sixth timer in response to arrival of the fifth data.

[0678] For example, when the fifth data arrives at the fourth entity, the fourth entity of the terminal device starts a sixth timer.

[0679] In the present application, starting the sixth timer may be understood as starting or restarting the sixth timer.

[0680] Exemplarily, the sixth timer may be a synchronization timer. Of course, the sixth timer may also have other names. This application uses the sixth timer as an example for introduction, which should not be understood as limiting this application.

[0681] Exemplarily, the start time of the sixth timer is: the arrival time of the fifth data.

[0682] It can be understood that the fourth entity has a sixth timer, and starts or restarts the sixth timer every time it receives a piece of fifth data.

[0683] Taking FIG. 4 as an example, the start time of the sixth timer may be 0 ms.

[0684] Exemplarily, the duration of the sixth timer is the fifth duration, or the end time of the sixth timer is the fifth time. The start time of the fifth duration is the time when the fifth data arrives at the fourth entity, and the fifth time is the end time of the fifth duration.

[0685] Taking Figure 4 as an example, the fifth duration may be the duration between 0ms and 20ms, as shown by the dotted box where 'synchronization requirement' is located. The fifth moment is 20ms, ie, the end moment of the dotted box where 'synchronization requirement' is located.

[0686] In this application, the fifth duration can be understood as, if the fifth data arrives at the terminal device first, starting at the moment the fifth data arrives at the terminal device, and the sixth data is transmitted within the fifth duration, thereby synchronizing the fifth data with the sixth data. Conversely, if the sixth data is not transmitted within the fifth duration, the fifth and sixth data are out of sync, affecting the user experience. The moment the fifth data arrives at the terminal device can be understood as the moment the fifth data arrives at the fourth entity.

[0687] It is easy to understand that, as an example, the fifth duration can be semi-statically configured or pre-configured, for example, indicated to the fourth entity through high-layer signaling or core network signaling, or can be determined by the terminal device itself. Exemplarily, the value of the fifth duration can be determined according to Table 1, and the description of the determination process of the second duration can be referred to, which will not be repeated here.

[0688] Optionally, the duration of the sixth timer can be configured by the network device side. Please refer to the introduction of S1401 for details and will not be repeated here.

[0689] S2003. The fourth entity of the terminal device obtains sixth data.

[0690] Exemplarily, the sixth data may be visual data, or tactile data, or audio data.

[0691] Exemplarily, the fourth entity obtains the sixth data, which can be understood as the sixth data reaching the fourth entity.

[0692] Taking FIG. 4 as an example, the sixth data may be visual data.

[0693] It is easy to understand that the terminal device may execute S2001 first and then execute S2003. In other words, the fifth data arrives at the terminal device first and the sixth data arrives at the terminal device later.

[0694] It is easy to understand that when S2002 is executed, the terminal device can execute S2002 and S2003 simultaneously, or execute S2002 first and then S2003, or execute S2003 first and then S2002. This application does not limit this.

[0695] It is easy to understand that the first, fifth, and sixth data can be different types of data. For example, the fifth data is video data and the sixth data is audio data. For another example, the fifth data is video data and the sixth data is tactile data. For another example, the fifth data is audio data and the sixth data is tactile data. Second, there is a synchronization requirement between the fifth and sixth data. Based on this, the fourth entity of the terminal device further executes S2004:

[0696] S2004. The fourth entity of the terminal device determines fifth information.

[0697] For example, the fourth entity determines the fifth information according to the data type of the fifth data and the data type of the sixth data.

[0698] The fifth information is as follows:

[0699] The fifth information includes a fifth duration or a fifth time, wherein the starting time of the fifth duration is the time when the fifth data arrives at the fourth entity, and the fifth time is the ending time of the fifth duration, which can be referred to the introduction of S2002.

[0700] Exemplarily, when S2002 is executed, the fourth entity determines the fifth information according to the sixth timer.

[0701] It is easy to understand that, on the fourth entity side, as an example, when the fourth entity obtains the fifth data, the fourth entity determines the fifth information based on the fifth data. In other words, the fifth information is related to the fifth data, and it can be understood that the fifth data can trigger the determination of the fifth information.

[0702] It is easy to understand that in Example 5, the fifth information can be used to determine the sixth duration. For example, if the fifth information is used to determine the transmission delay budget of the sixth data, please refer to the introduction of S2012 or S2032 and will not be repeated here.

[0703] It is easy to understand that in the fifth embodiment, the fourth entity can transmit the fifth information to a lower layer, such as a PDCP entity of the PDCP layer or a MAC entity of the MAC layer. Next, two cases are introduced:

[0704] In case 1, the fourth entity transmits the fifth information to the PDCP entity.

[0705] As shown in FIG. 22 , the communication method 2000 of the present application further includes the following operations:

[0706] S2011: The fourth entity of the terminal device sends fifth information to the fifth entity. Correspondingly, the fifth entity receives the fifth information from the fourth entity.

[0707] Among them, the fifth entity is the PDCP entity corresponding to the sixth data.

[0708] For example, as a possible implementation, the fifth data and the sixth data may belong to the same DRB. For example, the fifth data and the sixth data may belong to the fourth DRB. The fifth entity may be the PDCP entity corresponding to the fourth DRB. Taking Figure 21 as an example, the fourth DRB is DRB#3, and the fifth entity is PDCP entity 3.

[0709] It should be understood that the fifth entity may also be other entities corresponding to the fourth DRB, such as an SDAP entity, an RLC entity, etc. In the communication method 2000 of the present application, the fifth entity is introduced by taking the PDCP entity as an example.

[0710] As another possible implementation, the fifth data and the sixth data may belong to different DRBs. For example, the fifth data belongs to the fifth DRB, and the sixth data belongs to the sixth DRB. The fifth entity may be the PDCP entity corresponding to the fifth DRB. Taking Figure 21 as an example, the fifth entity is PDCP entity 1, the fifth DRB is DRB#1, and the sixth DRB is DRB#2.

[0711] It should be understood that the fifth entity may also be other entities corresponding to the fifth DRB, such as an SDAP entity, an RLC entity, etc. In the communication method 2000 of the present application, the fifth entity is introduced by taking the PDCP entity as an example.

[0712] S2012. The fifth entity of the terminal device determines a sixth duration based on the fifth information.

[0713] Among them, the introduction of the sixth period is as follows:

[0714] In this application, the sixth duration is the duration during which the sixth data is expected to be transmitted. It can be understood that the sixth duration is determined with reference to the synchronization requirement between the fifth data and the sixth data.

[0715] Taking Figure 4 as an example, the sixth data is visual data. The start time of the sixth duration is 5 ms, that is, the time when the visual data arrives at the terminal device, or the sixth data arrives at the fourth entity (such as the entity at the NAS layer) or the fifth entity (such as the PDCP entity corresponding to the sixth data). The end time of the sixth duration is the end time of the fifth duration, that is, 20 ms. If the sixth data is transmitted within the sixth duration, the fifth data can be synchronized with the sixth data.

[0716] It should be understood that the sixth duration may also have other names, such as the effective transmission duration of the sixth data, or the transmission delay budget of the sixth data. The embodiment of the present application takes the sixth duration as an example for introduction.

[0717] Next, we will introduce the process of determining the sixth duration in Case 1 (see Options 1 and 2 below for details):

[0718] Solution 1: The sixth duration is determined based on the fifth information.

[0719] In solution 1, S2012 includes the following steps 1 and 2:

[0720] Step 1: The fifth entity of the terminal device determines the duration of the seventh timer based on the fifth information.

[0721] Exemplarily, when the seventh timer times out, the terminal device discards the sixth data. In other words, the time when the seventh timer times out is the time when the sixth data is discarded. The seventh timer may be a packet loss timer. It should be understood that with the evolution of communication technology, packet loss timers may have other names. This application uses the packet loss timer as an example, and this should not be construed as limiting this application.

[0722] Exemplarily, the start time of the seventh timer (or packet loss timer) is the sixth time, wherein the sixth time is the time when the sixth data arrives at the fifth entity (eg, the fifth data corresponds to the PDCP entity).

[0723] Exemplarily, the end time of the seventh timer (or packet loss timer) is the fifth time. The fifth time can be described in S2002 and will not be described in detail. It can be understood that in related technologies, the duration or end time of the seventh timer (or packet loss timer) is obtained by configuring high-layer signaling (such as RRC signaling). In the present application, the end time of the seventh timer (or packet loss timer) is obtained from the fifth information.

[0724] In other words, taking the execution of S2002 as an example, it can be understood that the value of the seventh timer (or packet loss timer) refers to the real-time value of the sixth timer (or synchronization timer). For example, the real-time value of the sixth timer (or synchronization timer) is assigned to the seventh timer (or packet loss timer). In other words, the value of the seventh timer (or packet loss timer) is not obtained by high-level signaling (such as RRC signaling), but is determined based on the real-time value of the sixth timer (or synchronization timer).

[0725] Step 2: The fifth entity of the terminal device determines the sixth duration based on the duration of the seventh timer.

[0726] Exemplarily, the starting time of the sixth duration is: the sixth time. The sixth time is the time when the sixth data arrives at the fifth entity (eg, the fifth data corresponds to the PDCP entity).

[0727] Exemplarily, the end time of the sixth duration is the end time of the seventh timer (or packet loss timer).

[0728] That is to say, the terminal device updates the duration of the seventh timer (or packet loss timer) according to the fifth information, and then determines the sixth duration according to the duration of the seventh timer (or packet loss timer). Since the fifth duration or the fifth moment indicated by the fifth information can meet the synchronization requirements of the fifth data and the sixth data, the duration of the seventh timer (or packet loss timer) determined based on the fifth information is a duration that takes into account the synchronization requirements between the fifth data and the sixth data. In the case of determining the sixth duration based on the duration of the seventh timer (or packet loss timer), if the sixth data is transmitted within the sixth duration, the synchronization of the fifth data and the sixth data can be achieved. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the sixth data in the DSR MAC CE can be determined based on the updated seventh timer (or packet loss timer).

[0729] Solution 2: The sixth duration is determined based on the fifth information and the sixth information.

[0730] In solution 2, S2012 includes: the fifth entity of the terminal device determines the sixth duration based on the fifth information and the sixth information.

[0731] Among them, the introduction of the sixth information is as follows:

[0732] In the present application, the sixth information indicates the time when the sixth data is discarded.

[0733] Exemplarily, the sixth information may be RRC signaling, please refer to the introduction in the glossary section and will not be repeated here.

[0734] Exemplarily, the sixth information comes from the network device, that is, the sixth information is information sent by the network device to the terminal device.

[0735] It should be understood that for the fifth entity of the terminal device, the fifth entity can first receive the fifth information and then receive the sixth information, or it can first receive the sixth information and then receive the fifth information, or it can receive the fifth information and the sixth information at the same time. The embodiment of the present application does not limit this.

[0736] Among them, the introduction of the sixth period is as follows:

[0737] Exemplarily, the starting time of the sixth duration is: the sixth time, wherein the sixth time is the time when the sixth data arrives at the fifth entity (eg, the sixth data corresponds to the PDCP entity).

[0738] Exemplarily, the starting time of the sixth duration may also be: the time when the fifth data arrives at the fourth entity.

[0739] Exemplarily, the end time of the sixth duration is the earlier of the fifth time and the time of discarding (ie, the time indicated by the sixth information).

[0740] For example, when the fifth moment is earlier than the discarding moment (ie, the moment indicated by the sixth information), the end moment of the sixth duration is the fifth moment.

[0741] For another example, when the moment of abandonment (ie, the moment indicated by the sixth information) is earlier than or equal to the fifth moment, the end moment of the sixth duration is the moment of abandonment (ie, the moment indicated by the sixth information).

[0742] That is to say, in the process of determining the sixth duration, the terminal device refers to both the fifth information and the sixth information. When the sixth duration is determined with reference to the fifth information, since the fifth duration or fifth moment indicated by the fifth information can meet the synchronization requirements of the fifth data and the sixth data, when the sixth duration is determined based on the fifth information, if the sixth data is transmitted within the sixth duration, the synchronization of the fifth data and the sixth data can be achieved. Moreover, when the sixth duration is determined with reference to the sixth information, since the moment indicated by the sixth information can enable the terminal device to know the transmission delay requirements of the sixth data, when the sixth duration is determined based on the sixth information, if the sixth data is transmitted within the sixth duration, the transmission delay requirements of the sixth data can be met.

[0743] In solution 2, as a possible example, the fifth entity of the terminal device determines the sixth duration based on the fifth information and the sixth information, which may specifically include:

[0744] Step 3: The fifth entity of the terminal device determines the duration of the seventh timer based on the fifth information and the sixth information.

[0745] Among them, the introduction of the seventh timer is as follows:

[0746] Exemplarily, the seventh timer may be a packet loss timer.

[0747] Exemplarily, the start time of the seventh timer (or packet loss timer) is the sixth time, which is the time when the sixth data arrives at the fifth entity (eg, the sixth data corresponds to the PDCP entity).

[0748] Exemplarily, the end time of the seventh timer (or packet loss timer) is: the earlier time between the fifth time and the time of discarding (ie, the time indicated by the sixth information).

[0749] For example, when the fifth moment is earlier than (or equal to) the discarding moment (ie, the moment indicated by the sixth information), the end moment of the seventh timer (or packet loss timer) is the fifth moment.

[0750] For example, when the discarding moment (ie, the moment indicated by the sixth information) is earlier than or equal to the fifth moment, the end moment of the seventh timer (or packet loss timer) is the discarding moment (ie, the moment indicated by the sixth information).

[0751] It can be understood that, in related technologies, the end time of the seventh timer (or packet loss timer) is obtained by RRC signaling configuration. In the present application, the end time of the seventh timer (or packet loss timer) is obtained by the fifth information and the sixth information. The sixth information can be information in the above-mentioned high-layer signaling (such as RRC signaling), such as the indication of the time when the sixth data is discarded.

[0752] In other words, taking the execution of S2002 as an example, it can be understood that whether the seventh timer (or packet loss timer) is updated depends on the smaller value of the real-time value of the sixth timer (or synchronization timer) and the real-time value of the seventh timer (or packet loss timer).

[0753] Specifically, taking the end time of the seventh timer (or packet loss timer) configured by RRC signaling as an example, the value of the seventh timer (or packet loss timer) when it is started is configured by RRC signaling. When the real-time value of the sixth timer (or synchronization timer) is less than the real-time value of the seventh timer (or packet loss timer), the seventh timer (or packet loss timer) is updated, such as assigning the real-time value of the sixth timer (or synchronization timer) to the seventh timer (or packet loss timer). Conversely, when the real-time value of the sixth timer (or synchronization timer) is greater than or equal to the real-time value of the seventh timer (or packet loss timer), there is no need to update the seventh timer (or packet loss timer), and the real-time value of the seventh timer (or packet loss timer) remains unchanged.

[0754] Step 4: The fifth entity of the terminal device determines the sixth duration based on the duration of the seventh timer.

[0755] Among them, the introduction of the sixth period is as follows:

[0756] Exemplarily, the starting time of the sixth duration is: the sixth time, wherein the sixth time is the time when the sixth data arrives at the fifth entity (eg, the sixth data corresponds to the PDCP entity).

[0757] Exemplarily, the starting time of the sixth duration may also be: the time when the fifth data arrives at the fourth entity.

[0758] Exemplarily, the end time of the sixth duration is the end time of the seventh timer (or packet loss timer).

[0759] That is to say, the terminal device updates the duration of the seventh timer (or packet loss timer) based on the fifth information and the sixth information, and then determines the sixth duration based on the duration of the seventh timer (or packet loss timer). Since the fifth duration or the fifth moment indicated by the fifth information can meet the synchronization requirements of the fifth data and the sixth data, and the moment indicated by the sixth information can enable the terminal device to know the transmission delay requirements of the sixth data, in this way, the duration of the seventh timer (or packet loss timer) determined based on the fifth information and the sixth information takes into account both the synchronization requirements between the fifth data and the sixth data and the transmission delay requirements of the sixth data. In the case where the sixth duration is determined based on the duration of the seventh timer (or packet loss timer), if the sixth data is transmitted within the sixth duration, the synchronization of the fifth data and the sixth data can be achieved, and the transmission delay requirements of the sixth data can be met. At this time, when there is a synchronization requirement between multiple data, the remaining transmission delay budget of the sixth data in the DSR MAC CE can be determined based on the updated seventh timer (or packet loss timer).

[0760] Furthermore, in case 1, the MAC entity of the terminal device may also send a status report. The delay information included in the status report is determined based on the sixth duration, and / or whether to trigger the status report is determined based on the sixth duration, as shown in FIG22 . Specific descriptions are as follows:

[0761] S2021. The MAC entity of the terminal device obtains the sixth duration.

[0762] For example, after the fifth entity of the terminal device executes S2012, the fifth entity sends indication information of the sixth duration to the MAC entity. Accordingly, the MAC entity receives the indication information of the sixth duration from the fifth entity. The indication information of the sixth duration may indicate the end time of the sixth duration. Alternatively, the indication information of the sixth duration may indicate the start time of the sixth duration and the duration of the sixth duration.

[0763] For another example, taking the seventh timer (e.g., packet loss timer) as an example, the MAC entity of the terminal device obtains the sixth duration based on the seventh timer (e.g., packet loss timer). For example, the end time of the seventh timer (e.g., packet loss timer) is the end time of the sixth duration. The seventh timer (e.g., packet loss timer) can be described in step 1 or step 3 of S2012 and will not be repeated here.

[0764] S2022. The MAC entity of the terminal device sends a status report.

[0765] For example, the content of the status report is as follows:

[0766] As a possible description: the status report includes delay information of the sixth data, and the delay information of the sixth data is determined according to the sixth time length.

[0767] For example, if the delay information of the sixth data is the remaining transmission delay budget, the remaining transmission delay budget is determined based on the sixth duration. For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the end time of the sixth duration.

[0768] For another example, the delay information of the sixth data is determined based on the stored duration. The stored duration is determined based on the sixth duration. For example, the starting time of the stored duration is the starting time of the sixth duration. The ending time of the stored duration is the sending time of the status report.

[0769] As another possible description, taking the seventh timer (e.g., packet loss timer) as an example, the status report includes latency information of the sixth data, and the latency information of the sixth data is determined based on the seventh timer (e.g., packet loss timer). The seventh timer (e.g., packet loss timer) can be found in the description of step 1 or step 3 in S2012 and is not further described.

[0770] For example, if the delay information of the sixth data is the remaining transmission delay budget, the starting time of the remaining transmission delay budget is: the sending time of the status report, such as the sending time of the initial transmission. The ending time of the remaining transmission delay budget is: the ending time of the seventh timer (such as the packet loss timer).

[0771] For another example, the delay information of the sixth data is determined based on a stored duration. The stored duration is determined based on a seventh timer (e.g., a packet loss timer). For example, the start time of the stored duration is the start time of the seventh timer (e.g., a packet loss timer). The end time of the stored duration is the time when the status report is sent.

[0772] That is to say, when the terminal device reports the status report, the delay information of the sixth data carried in the status information is determined based on the sixth time length. Since the sixth time length refers to the duration of the synchronization requirement between the fifth data and the sixth data, the delay information determined based on the sixth time length also takes into account the synchronization requirement of the sixth data. This means that the terminal device can report "delay information that takes into account the synchronization requirements between different data" to the network device. Accordingly, if the network device schedules transmission resources for the terminal device based on the delay information so that the sixth data is transmitted within the sixth time length, the fifth data is synchronized with the sixth data, which helps to improve the user experience.

[0773] Exemplarily, on the other hand, the triggering of the status report is described as follows:

[0774] As a possible description: the MAC entity of the terminal device triggers a status report according to the sixth time duration.

[0775] Exemplarily, the status report includes the delay information of the sixth data, and the delay information of the sixth data is determined based on the sixth duration. Taking the delay information of the sixth data as the remaining transmission delay budget as an example, the starting time of the remaining transmission delay budget is: the current time of the system. It should be understood that the current time of the system changes with time. Among them, the unit of the current time of the system can be one of the following: seconds, milliseconds, time slots, subframes, frames, etc., which are not limited in this application. The end time of the remaining transmission delay budget is: the end time of the sixth duration. When the remaining transmission delay budget is less than or equal to the first threshold, the MAC entity triggers a status report. When the remaining transmission delay budget is greater than the first threshold, the MAC entity does not trigger a status report. Among them, the first threshold can be found in the introduction of S612 and S613. Among them, the remaining transmission delay budget can be found in the introduction of the previous paragraph and will not be repeated.

[0776] As another possible description: Taking the seventh timer (e.g., packet loss timer) as an example, the MAC entity of the terminal device triggers a status report based on the seventh timer (e.g., packet loss timer). The seventh timer (e.g., packet loss timer) can be found in the introduction of step 1 or step 3 in S2012 and will not be repeated here.

[0777] After the status report is triggered, when there are available uplink resources, if the triggering of the status report is not cancelled, or the uplink resources cannot carry the data volume of all data indicated by the status report, the status report is sent on the uplink resources.

[0778] Case 2: The fourth entity transmits the fifth information to the MAC entity.

[0779] As shown in FIG. 23 , the communication method 2000 of the present application further includes the following operations:

[0780] S2031. The fourth entity of the terminal device sends fifth information to the MAC entity. Correspondingly, the MAC entity receives the fifth information from the fourth entity.

[0781] For example, the fourth entity sends the fifth information to the MAC entity through the DRB. Correspondingly, the MAC entity receives the fifth information from the fourth entity through the DRB. The DRB for transmitting the fifth information is described as follows: If the fifth data and the sixth data belong to the same DRB, such as the fourth DRB, then the DRB can be the fourth DRB. If the fifth data and the sixth data belong to different DRBs, such as the fifth data belongs to the fifth DRB and the sixth data belongs to the sixth DRB, then the DRB can be either the fifth DRB or the sixth DRB.

[0782] It should be noted that the PDCP entity in Figure 23 is described as follows: If the fifth data and the sixth data belong to the same DRB, such as the fourth DRB, the PDCP entity in Figure 23 is the PDCP entity corresponding to the fourth DRB. If the fifth data and the sixth data belong to different DRBs, such as the fifth data belongs to the fifth DRB and the sixth data belongs to the sixth DRB, the PDCP entity in Figure 23 can be the PDCP corresponding to the fifth DRB or the PDCP corresponding to the sixth DRB.

[0783] For another example, the fourth entity sends the fifth information to the MAC entity via control plane signaling. Correspondingly, the MAC entity receives the fifth information from the fourth entity via control plane signaling.

[0784] Alternatively, the fourth entity may also send the fifth information to the MAC entity in other ways. This application does not limit how the MAC entity obtains the fifth information.

[0785] S2032. The MAC entity of the terminal device determines a sixth duration based on the fifth information.

[0786] For example, the sixth duration is determined based on the fifth information, or the sixth duration is determined based on the fifth information and the sixth information. The sixth information indicates the moment when the sixth data is discarded. Please refer to the introduction of S2012 and will not be repeated here.

[0787] It should be noted that in the fifth embodiment, the sixth information indicates the time when the sixth data is discarded. The sixth information in S2012 may be RRC signaling, and the sixth information in S2032 may be determined based on a ninth timer (such as a packet loss timer). For details, see the introduction of FIG. 24 and will not be described in detail here.

[0788] Furthermore, in case 2, the terminal device may further execute S2033:

[0789] S2033. The MAC entity of the terminal device sends a status report, wherein the status report includes delay information of the sixth data, the delay information of the sixth data is determined according to the sixth duration, and / or the triggering of the status report is determined according to the sixth duration.

[0790] Regarding the content of the status report, for example, if the delay information of the sixth data is the remaining transmission delay budget, the remaining transmission delay budget is determined based on the sixth duration. For example, the starting time of the remaining transmission delay budget is the time the status report is sent, such as the time the initial transmission is sent. The ending time of the remaining transmission delay budget is the end time of the sixth duration.

[0791] On the other hand, regarding triggering the status report, taking the example of the sixth data delay information being the remaining transmission delay budget, the remaining transmission delay budget is determined based on the sixth duration. For example, the starting time of the remaining transmission delay budget is the current time of the system, and the ending time of the remaining transmission delay budget is the ending time of the sixth duration.

[0792] Next, a description of possible replacements is given:

[0793] As a possible alternative description: taking the sixth timer (such as the synchronization timer) as an example, the status report includes the delay information of the sixth data, and the delay information of the sixth data is determined according to the sixth timer (such as the synchronization timer).

[0794] For example, if the delay information of the sixth data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on a sixth timer (e.g., a synchronization timer). For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the ending time of the sixth timer (e.g., the synchronization timer).

[0795] In this case, it can also be understood that the triggering of the status report is determined according to the sixth timer (such as the synchronization timer).

[0796] As another possible replacement description: taking the sixth timer (such as a synchronization timer) and the ninth timer (such as a packet loss timer) as an example, the status report includes the delay information of the sixth data, and the delay information of the sixth data is determined based on the sixth timer (such as a synchronization timer) and the ninth timer (such as a packet loss timer).

[0797] For example, if the delay information of the sixth data is a remaining transmission delay budget, the remaining transmission delay budget is determined based on a sixth timer (e.g., a synchronization timer) and a ninth timer (e.g., a packet loss timer). For example, the starting time of the remaining transmission delay budget is the time when the status report is sent, such as the time when the initial transmission is sent. The ending time of the remaining transmission delay budget is the earlier of the ending time of the sixth timer (e.g., the synchronization timer) and the ending time of the ninth timer (e.g., the packet loss timer).

[0798] In this case, it can also be understood that the triggering of the status report is determined according to the sixth timer (such as the synchronization timer) and the ninth timer (such as the packet loss timer).

[0799] Among them, the sixth timer (such as the synchronization timer) can be found in the introduction of 2002 in detail.

[0800] The ninth timer (such as the packet loss timer) is described as follows:

[0801] As shown in FIG24 , for the fourth entity, after obtaining the sixth data, the fourth entity performs the following operations:

[0802] S2041: The fourth entity sends sixth data to the PDCP entity. Correspondingly, the PDCP entity receives the sixth data from the fourth entity.

[0803] S2042. In response to receiving the sixth data, the PDCP entity starts a ninth timer.

[0804] For example, when the PDCP entity receives the sixth data, the PDCP entity starts a ninth timer.

[0805] In the present application, starting the ninth timer may be understood as starting or restarting the ninth timer.

[0806] Among them, the ninth timer is introduced as follows:

[0807] Exemplarily, the ninth timer may be a packet loss timer. Of course, the ninth timer may also have other names. This application is introduced using the ninth timer as an example, which should not be understood as limiting this application.

[0808] The start time of the ninth timer is as follows:

[0809] Exemplarily, the ninth timer is started at the time when the sixth data is received.

[0810] The end time of the ninth timer is as follows:

[0811] Exemplarily, the end time of the ninth timer is indicated by higher layer signaling (such as RRC signaling).

[0812] S2043: The PDCP entity sends the sixth information to the MAC entity. Correspondingly, the MAC entity receives the sixth information from the PDCP entity.

[0813] The sixth information indicates the moment when the sixth data is discarded.

[0814] Exemplarily, the sixth information is determined according to the ninth timer. For example, the sixth information indicates the end time of the ninth timer.

[0815] It should be noted that, in this application, the PDCP entity executing S2041-S2043 can be understood as the PDCP entity corresponding to the sixth data. Specifically, if the fifth data and the sixth data belong to the same DRB, such as the fourth DRB, then the PDCP entity in Figure 24 is the PDCP entity corresponding to the fourth DRB. If the fifth data and the sixth data belong to different DRBs, such as the fifth data belongs to the fifth DRB and the sixth data belongs to the sixth DRB, then the PDCP entity in Figure 24 is the PDCP corresponding to the fifth DRB.

[0816] It is understood that in each of the above embodiments, the methods and / or steps implemented by the first entity of the terminal device may also be implemented by components applicable to the first entity (e.g., a processor, chip, chip system, circuit, logic module, or software); or the methods and / or steps implemented by the second entity of the terminal device may also be implemented by components applicable to the second entity (e.g., a processor, chip, chip system, circuit, logic module, or software). The chip system may be composed of a chip, or the chip system may include a chip and other discrete devices.

[0817] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0818] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be pointed out that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0819] Figure 25 shows a schematic diagram of the structure of a communication device 2500. The communication device 2500 includes a processing module 2501 and a transceiver module 2502. The communication device 2500 can be used to implement the functions of the first entity of the terminal device described above. Alternatively, the communication device 2500 can be used to implement the functions of the second entity of the terminal device described above.

[0820] In some embodiments, the communication device 2500 may further include a storage module (not shown in FIG. 25 ) for storing program instructions and data.

[0821] In some embodiments, the transceiver module 2502, which may also be referred to as a transceiver unit, is configured to implement a transmitting and / or receiving function. The transceiver module 2502 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0822] In some embodiments, the transceiver module 2502 may include a receiving module and a sending module, which are respectively used to execute the transceiver type (such as receiving and / or sending type) steps performed by the first entity or the second entity of the terminal device in the above method embodiment, and / or used to support other processes of the technology described herein; the processing module 2501 may be used to execute the processing type (such as determination, etc.) steps performed by the first entity or the second entity in the above method embodiment, and / or used to support other processes of the technology described herein.

[0823] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0824] Optionally, in this application, "the transceiver module receives / sends information" can also be understood as the processing module receiving / sending information via the transceiver module. "The processing module receives / sends information via the transceiver module" can also be understood as the processing module controlling the transceiver module to receive / send information. Alternatively, "the processing module sends information via the transceiver module" can be understood as the processing module outputs information to the transceiver module, which then sends the information; "the processing module receives information via the transceiver module" can be understood as the transceiver module receiving the information and inputting the information to the processing module.

[0825] In the present application, the communication device 2500 may be presented in the form of functional modules divided in an integrated manner. The "module" here may refer to a specific application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0826] In some embodiments, when the communication device 2500 in Figure 25 is a chip or a chip system, the function / implementation process of the transceiver module 2502 can be implemented through the input and output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 2501 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0827] Since the communication device 2500 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0828] As a possible product form, the first entity or the second entity of the terminal device described in the embodiment of the present application can also be implemented using the following: one or more field programmable gate arrays (FPGA), programmable logic devices (PLD), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0829] As another possible product form, the entities of the terminal device described in the embodiment of the present application, such as the first entity to the fifth entity, can be implemented by a general bus architecture.

[0830] For ease of explanation, refer to Figure 26, which is a schematic diagram of the structure of a communication device 2600 provided in an embodiment of the present application, wherein the communication device 2600 includes a processor 2601 and a transceiver 2602. The communication device 2600 can be one of the first to fifth entities of the terminal device, or a chip or chip system therein.

[0831] Figure 26 only shows the main components of the communication device 2600. In addition to the processor 2601 and the transceiver 2602, the communication device 2600 may further include a memory 2603 and input and output devices (not shown).

[0832] Optionally, processor 2601 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. Memory 2603 is primarily used to store software programs and data. Transceiver 2602 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0833] Optionally, the processor 2601, the transceiver 2602, and the memory 2603 may be connected via a communication bus.

[0834] When the communication device is turned on, the processor 2601 can read the software program in the memory 2603, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 2601 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 2601. The processor 2601 converts the baseband signal into data and processes the data.

[0835] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0836] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device 2500 may take the form of the communication device 2600 shown in FIG. 26 .

[0837] As an example, the functions / implementation process of the processing module 2501 in FIG25 can be implemented by the processor 2601 in the communication device 2600 shown in FIG26 calling the computer-executable instructions stored in the memory 2603. The functions / implementation process of the transceiver module 2502 in FIG25 can be implemented by the transceiver 2602 in the communication device 2600 shown in FIG26.

[0838] As another possible product form, any one of the first to fifth entities of the terminal device in this application may adopt the structure shown in Figure 27, or include the components shown in Figure 27. Figure 27 is a schematic diagram of the structure of a communication device 2700 provided in this application.

[0839] As shown in FIG27 , a communication device 2700 includes at least one processor 2701. Optionally, the communication device further includes a communication interface 2702.

[0840] When the program instructions are executed in the at least one processor 2701, the apparatus 2700 can implement the method provided in any of the aforementioned embodiments and any possible designs thereof. Alternatively, the processor 2701 implements the method provided in any of the aforementioned embodiments and any possible designs thereof through logic circuits or by executing code instructions.

[0841] The communication interface 2702 can be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 2702 can be used for the communication device 2700 to communicate with other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 2702 can be used to receive signals from devices other than the communication device 2700 and transmit them to the processor 2701, or to send signals from the processor 2701 to other communication devices other than the communication device 2700.

[0842] Optionally, the communication interface 2702 may be a code and / or data read and write interface circuit, or the communication interface 2702 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0843] Optionally, the communication device 2700 may further include at least one memory 2703, which may be used to store required program instructions and / or data. It should be noted that the memory 2703 may exist independently of the processor 2701 or may be integrated with the processor 2701. The memory 2703 may be located within the communication device 2700 or outside the communication device 2700, without limitation.

[0844] Optionally, the communication device 2700 may further include a power supply circuit 2704, which may be used to supply power to the processor 2701. The power supply circuit 2704 may be located in the same chip as the processor 2701, or in another chip other than the chip where the processor 2701 is located.

[0845] Optionally, the communication device 2700 may further include a bus 2705 , and various parts of the communication device 2700 may be interconnected via the bus 2705 .

[0846] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 2500 shown in FIG. 25 may take the form of the communication device 2700 shown in FIG. 27 .

[0847] As an example, the functions / implementation process of the processing module 2501 in FIG25 can be implemented by the processor 2701 in the communication device 2700 shown in FIG27 calling the computer-executable instructions stored in the memory 2703. The functions / implementation process of the transceiver module 2502 in FIG25 can be implemented by the communication interface 2702 in the communication device 2700 shown in FIG27.

[0848] It should be noted that the structure shown in FIG27 does not constitute a specific limitation on the first entity or the second entity. For example, in other embodiments of the present application, any of the first to fifth entities may include more or fewer components than shown, or combine or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0849] Optionally, the processor in the present application may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0850] Optionally, the memory in the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), or direct rambus RAM (DR RAM).

[0851] Optionally, the power supply circuit described in the embodiment of the present application includes but is not limited to at least one of the following: a power supply line, a power supply subsystem, a power management chip, a power consumption management processor, or a power consumption management control circuit.

[0852] In some embodiments, an embodiment of the present application further provides a communication device, which includes a processor for implementing the method in any of the above method embodiments.

[0853] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary computer programs and data. The computer program may include instructions, and the processor may invoke the instructions in the computer program stored in the memory to instruct the communication device to perform any of the above-described method embodiments. Of course, the memory may not be located in the communication device.

[0854] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, and the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.

[0855] As another possible implementation, the communication device further includes a communication interface, where the communication interface is used to communicate with a module outside the communication device.

[0856] It can be understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or include chips and other discrete devices. The embodiments of the present application do not specifically limit this.

[0857] The present application also provides a computer-readable storage medium having a computer program or instruction stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.

[0858] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0859] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the above-described systems, devices, and units may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0860] It is understood that the systems, devices, and methods described in this application may also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be through some interface, indirect coupling or communication connection of devices or units, and may be electrical, mechanical, or other forms.

[0861] The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Components shown as units may or may not be physical units. Some or all of these units may be selected to achieve the objectives of this embodiment as needed.

[0862] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0863] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)). In the embodiment of the present application, the computer may include the aforementioned device.

[0864] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0865] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: The method comprises: Receiving first information from a first data radio bearer DRB; wherein the first information is related to first data, and the first data belongs to the first DRB; Based on the first information, a first duration is determined; wherein the first duration is the duration in which the second data is expected to be transmitted, and the second data belongs to a second DRB; the first duration is used to determine the delay information of the status report, and / or the first duration is used to trigger the sending of the status report.

2. The method according to claim 1, characterized in that The first information indicates a second duration or a first moment; The starting time of the second duration is the time when the first data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the first DRB, and the first time is the end time of the second duration; The second duration is used to determine the first duration.

3. The method according to claim 2, characterized in that Determining the first duration according to the first information includes: Determine the duration of a first timer according to the first information; wherein the start time of the first timer is the second time, the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB; the end time of the first timer is the first time; The first duration is determined according to the duration of the first timer; wherein the start time of the first duration is the second time, and the end time of the first duration is the end time of the first timer.

4. The method according to claim 2, characterized in that: The method further comprises: In response to receiving the first information, starting a second timer; Determining the first duration according to the first information includes: determining the first duration according to the value of the second timer; The end time of the second timer is the first time; The starting time of the first duration is the second time, and the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB; the end time of the first duration is the end time of the second timer.

5. The method according to claim 2, characterized in that: Determining the first duration according to the first information includes: determining the first duration according to the first information and second information; wherein the second information indicates a moment when the second data is discarded.

6. The method according to claim 5, characterized in that The second information comes from a network device.

7. The method according to claim 5 or 6, characterized in that: The starting time of the first duration is a second time, and the second time is a time when the second data arrives at the PDCP entity corresponding to the second DRB; When the first moment is earlier than the discarding moment, the end moment of the first duration is the first moment; or, When the discarding moment is earlier than or equal to the first moment, the end moment of the first duration is the discarding moment.

8. The method according to claim 5 or 6, characterized in that: Determining the first duration according to the first information and the second information includes: Determine the duration of a first timer according to the first information and the second information; wherein the start time of the first timer is the second time, and the second time is the time when the second data arrives at the PDCP entity corresponding to the second DRB; when the first time is earlier than the discarding time, the end time of the first timer is the first time; or, when the discarding time is earlier than or equal to the first time, the end time of the first timer is the discarding time; The first duration is determined according to the duration of the first timer; wherein the start time of the first duration is the second time, and the end time of the first duration is the end time of the first timer.

9. The method according to claim 5 or 6, characterized in that: The method further comprises: In response to receiving the first information, starting a second timer (a synchronization timer for the second data); Determining the first duration according to the first information and the second information includes: Determine the first duration according to the value of the first timer and the value of the second timer; or determine the first duration according to the end time of the first timer and the end time of the second timer; The start time of the first timer is the second time, and the second time is the time when the second data arrives at the second DRB. The time corresponding to the PDCP entity; the end time of the first timer is the time of discarding; The end time of the second timer is the first time; The starting time of the first duration is the second time; when the first time is earlier than the abandonment time, the end time of the first duration is the end time of the second timer, or, when the abandonment time is earlier than or equal to the first time, the end time of the first duration is the end time of the first timer.

10. The method according to claim 4 or 9, characterized in that: The start time of the second timer is the reception time of the first information.

11. The method according to claim 3, 8 or 9, characterized in that: The first timer is a packet loss timer.

12. The method according to any one of claims 1 to 11, characterized in that In a case where the first duration is used to determine the delay information of the status report, the method further includes: The status report is sent via a media access control MAC entity, wherein the MAC entity is used to process the second data.

13. The method according to claim 12, characterized in that The delay information of the status report includes a remaining transmission delay budget, and the remaining transmission delay budget is determined according to the first duration.

14. The method according to claim 13, characterized in that The starting time of the remaining transmission delay budget is: the sending time of the status report; The end time of the remaining transmission delay budget is: the end time of the first duration.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: receiving a first threshold from a network device; The first duration is used to trigger the sending of the status report, including: when the remaining transmission delay budget determined by the first duration is less than or equal to the first threshold, the first duration is used to trigger the sending of the status report, and the remaining transmission delay budget determined by the first duration is the remaining transmission delay budget of the first data.

16. The method according to any one of claims 1 to 11, characterized in that The method is executed by a first entity; the first entity is a PDCP entity corresponding to the second DRB, or the first entity is a MAC entity processing the second data.

17. A communication method, characterized in that: The method comprises: Sending the first message; The first information is related to first data, and the first data belongs to a first data radio bearer DRB; The first information is used to determine a first duration, where the first duration is the duration in which the second data is expected to be transmitted, and the second data belongs to a second DRB.

18. The method according to claim 17, characterized in that The first information indicates a second duration or a first moment; The starting time of the second duration is the time when the first data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the first DRB, and the first time is the end time of the second duration; The second duration is used to determine the first duration.

19. The method according to claim 18, characterized in that The method further comprises: In response to receiving the first data, starting a third timer; The duration of the third timer is the second duration, or the end time of the third timer is the first time.

20. The method according to claim 19, characterized in that The start time of the third timer is the time when the first data arrives at the PDCP entity corresponding to the first DRB.

21. The method according to claim 18, characterized in that The method further comprises: receiving first indication information; The first indication information is used to indicate starting or restarting a third timer; The duration of the third timer is the second duration, or the end time of the third timer is the first time.

22. The method according to claim 21, characterized in that Sending the first information includes: sending the first information according to the first indication information.

23. The method according to any one of claims 19 to 22, characterized in that The method further comprises: Configuration information is received, where the configuration information is used to configure a duration of the third timer to be the second duration.

24. The method according to any one of claims 17 to 20, characterized in that The method is executed by a second entity, which is a PDCP entity corresponding to the first DRB.

25. The method according to any one of claims 17 to 24, characterized in that The first DRB and the second DBR are the same DRB.

26. A communication method, characterized in that: The method comprises: Acquire third information, where the third information is related to third data, and the third data belongs to a third data radio bearer DRB; Based on the third information, a fourth duration is determined, where the fourth duration is the duration in which the fourth data is expected to be transmitted, and the fourth data belongs to the third DRB; the fourth duration is used to determine the delay information of the status report, and / or the fourth duration is used to trigger the sending of the status report.

27. The method according to claim 26, characterized in that The third information indicates a third duration or a third time; The starting time of the third duration is the time when the third data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the third DRB, and the third time is the end time of the third duration; The third duration is used to determine the fourth duration.

28. The method according to claim 27, characterized in that Determining the fourth duration according to the third information includes: Determine the duration of a fifth timer according to the third information; wherein the start time of the fifth timer is the fourth time, the fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB; the end time of the fifth timer is the third time; The fourth duration is determined according to the duration of the fifth timer; wherein the starting time of the fourth duration is the fourth moment, and the ending time of the fourth duration is the ending time of the fifth timer.

29. The method according to claim 27, characterized in that Determining the fourth duration according to the third information includes: determining the fourth duration according to the third information and fourth information; wherein the fourth information indicates a moment when the fourth data is discarded.

30. The method according to claim 29, characterized in that The starting time of the fourth duration is a fourth time, and the fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB; When the third moment is earlier than the moment when the fourth data is discarded, the end moment of the fourth duration is the third moment; or, When the moment when the fourth data is discarded is earlier than or equal to the third moment, the end moment of the fourth duration is the moment when the fourth data is discarded.

31. The method according to claim 29 or 30, characterized in that Determining the fourth duration according to the third information and the fourth information includes: Determine the duration of a fifth timer according to the third information and the fourth information; wherein the start time of the fifth timer is the fourth time, and the fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB; when the third time is earlier than the time when the fourth data is discarded, the end time of the fifth timer is the third time; or, when the time when the fourth data is discarded is earlier than or equal to the third time, the end time of the fifth timer is the time when the fourth data is discarded; The fourth duration is determined according to the duration of the fifth timer; wherein the starting time of the fourth duration is the fourth moment, and the ending time of the fourth duration is the ending time of the fifth timer.

32. The method according to claim 28 or 31, characterized in that The fifth timer is a packet loss timer.

33. The method according to any one of claims 27 to 32, characterized in that Acquiring the third information includes: In response to receiving the third data, starting a fourth timer; The third information is determined according to the fourth timer; wherein the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time.

34. The method according to claim 33, characterized in that The start time of the fourth timer is the time when the third data arrives at the PDCP entity corresponding to the third DRB.

35. A communication method, characterized in that: The method comprises: Acquire second indication information, where the second indication information indicates a fourth duration, where the fourth duration is determined according to third information, where the third information is related to third data, and the third data belongs to a third data radio bearer DRB; and the fourth duration is a duration during which the fourth data is expected to be transmitted; Delay information of the status report is determined according to the fourth duration, and / or sending of the status report is triggered according to the fourth duration.

36. The method according to claim 35, characterized in that The delay information of the status report includes a remaining transmission delay budget, and the remaining transmission delay budget is determined according to the fourth duration.

37. The method according to claim 36, characterized in that The starting time of the remaining transmission delay budget is: the sending time of the status report; The end time of the remaining transmission delay budget is: the end time of the fourth duration.

38. The method according to any one of claims 35 to 37, characterized in that The fourth data belongs to the third DRB, or the DRB to which the fourth data belongs is different from the third DBR.

39. The method according to any one of claims 35 to 38, characterized in that The method further comprises: receiving a first threshold from a network device; Triggering the sending of the status report according to the fourth duration includes: A remaining transmission delay budget is determined according to the fourth duration, and when the remaining transmission delay budget is less than or equal to the first threshold, sending of the status report is triggered, where the remaining transmission delay budget is the remaining transmission delay budget of the fourth data.

40. A communication method, characterized in that: The method comprises: receiving third information, where the third information is related to third data, and the third data belongs to a third data radio bearer DRB; Determine a fourth duration according to the third information, where the fourth duration is a duration during which the fourth data is expected to be transmitted; Delay information of the status report is determined according to the fourth duration, and / or sending of the status report is triggered according to the fourth duration.

41. The method according to claim 40, characterized in that The third information indicates a third duration or a third time; The starting time of the third duration is the time when the third data arrives at the Packet Data Convergence Protocol PDCP entity corresponding to the third DRB, and the third time is the end time of the third duration; The third duration is used to determine the fourth duration.

42. The method according to claim 41, characterized in that Determining the fourth duration according to the third information includes: determining the fourth duration according to the third information and fourth information; wherein the fourth information indicates a moment when the fourth data is discarded.

43. The method according to claim 42, characterized in that The starting time of the fourth duration is a fourth time, and the fourth time is the time when the fourth data arrives at the PDCP entity corresponding to the third DRB; When the third moment is earlier than the moment when the fourth data is discarded, the end moment of the fourth duration is the third moment; or, When the moment when the fourth data is discarded is earlier than or equal to the third moment, the end moment of the fourth duration is the moment when the fourth data is discarded.

44. The method according to claim 42 or 43, characterized in that The third information is determined according to a fourth timer, wherein the duration of the fourth timer is the third duration, or the end time of the fourth timer is the third time.

45. The method according to claim 44, characterized in that The start time of the fourth timer is the time when the third data arrives at the PDCP entity corresponding to the third DRB.

46. ​​The method according to any one of claims 40 to 45, characterized in that The delay information of the status report includes a remaining transmission delay budget, and the remaining transmission delay budget is determined according to the fourth duration.

47. The method according to claim 46, characterized in that The starting time of the remaining transmission delay budget is: the sending time of the status report; The end time of the remaining transmission delay budget is: the end time of the first duration.

48. The method according to any one of claims 40 to 47, characterized in that The method further comprises: receiving a first threshold from a network device; Triggering the sending of the status report according to the fourth duration includes: A remaining transmission delay budget is determined according to the fourth duration, and when the remaining transmission delay budget is less than or equal to the first threshold, sending of the status report is triggered, where the remaining transmission delay budget is the remaining transmission delay budget of the fourth data.

49. The method according to any one of claims 40 to 48, characterized in that The fourth data belongs to the third DRB, or the DRB to which the fourth data belongs is different from the third DBR.

50. The method according to any one of claims 26 to 49, characterized in that The third information includes fifth information, the third data includes fifth data, the fourth data includes sixth data, and the fourth duration includes sixth duration.

51. A communication device, characterized in that: include: A processor and a memory, wherein the processor and the memory are coupled, and the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the method of any one of claims 1 to 16 is implemented, or the method of any one of claims 17 to 25 is implemented, or the method of any one of claims 26 to 34 is implemented, or the method of any one of claims 35 to 39 is implemented, or the method of any one of claims 40 to 50 is implemented.

52. A chip comprising a processor and a memory coupled to the processor, characterized in that: The memory stores a computer program, and when the processor executes the computer program, the method of any one of claims 1 to 16 is implemented, or the method of any one of claims 17 to 25 is implemented, or the method of any one of claims 26 to 34 is implemented, or the method of any one of claims 35 to 39 is implemented, or the method of any one of claims 40 to 50 is implemented.

53. A computer-readable storage medium storing a computer program or instruction, characterized in that: When the computer program or instruction is executed, the method described in any one of claims 1 to 16 is implemented, or the method described in any one of claims 17 to 24 is implemented, or the method described in any one of claims 26 to 34 is implemented, or the method described in any one of claims 35 to 39 is implemented, or the method described in any one of claims 40 to 50 is implemented.

Images