Data transmission method and apparatus

Abstract

A data transmission method and apparatus, relating to the technical field of communications. The method comprises: receiving first information, the first information being used for indicating a preset duration, and the preset duration corresponding to synchronization delay information between a first QoS flow and a second QoS flow; sending a first data packet, the first data packet being transmitted by means of the first QoS flow, and the moment at which the first data packet is sent by a first network device being a first moment; and sending a second data packet on the basis of the first moment and the preset duration, wherein the second data packet is transmitted by means of the second QoS flow, and the second data packet is associated with the first data packet. The first network device can send a synchronization data packet on the basis of the moment at which a reference data packet is sent and the preset duration for indicating the synchronization delay information, thereby achieving synchronization between the synchronization data packet and the reference data packet. Therefore, the data transmission method provided by the embodiments of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

Description

Data transmission method and device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on November 2, 2023, with application number 202311454220.7 and application name “Data Transmission 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 communication technology, and more specifically, to a data transmission method and device. Background Art

[0003] In scenarios such as virtual reality (VR), augmented reality (AR), extended reality (XR), and the metaverse, to meet user immersion needs, the data to be transmitted has evolved from single audio or video data to data from multiple modalities, including audio, video, and touch. Data from different modalities can be divided into different data streams, such as auditory data streams, visual data streams, and tactile data streams. When multiple modalities coexist, data synchronization is required to avoid synchronization issues between auditory, visual, and tactile senses.

[0004] However, how to improve the data synchronization effect of multiple data streams is an urgent problem to be solved.

[0005] Summary of the Invention

[0006] The present application provides a data transmission method and device, which can improve the data synchronization effect of multiple data streams.

[0007] In a first aspect, a data transmission method is provided. The method can be performed by a first network device, or by a component (e.g., a processor, a chip, or a chip system) in the first network device, or by a logic module or software that implements all or part of the functions of the first network device. The method includes: receiving first information indicating synchronization delay information between a first quality of service (QoS) flow and a second QoS flow; sending a first data packet at a first time, the first data packet being transmitted via the first QoS flow; and sending a second data packet based on the first time and the synchronization delay information, the second data packet being transmitted via the second QoS flow, and the second data packet being associated with the first data packet.

[0008] Optionally, the first network device may be an access network device. It is understood that the time when the first data packet is sent by the first network device is the first time. Optionally, the synchronization delay information between the first QoS flow and the second QoS flow corresponds to a preset duration.

[0009] Based on the above solution, the first network device can send a synchronization data packet based on the time when the reference data packet was sent and the synchronization delay information. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization between the synchronization data packet and the reference data packet. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

[0010] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving second information, where the second information is used to determine an association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0011] Based on the above solution, the first network device can determine the association between the data packets of the reference stream and the data packets of the synchronization stream based on the second information, wherein synchronization is required between the associated data packets. Therefore, the above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams, thereby enhancing the user experience.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the first data packet corresponds to the second information, and the second data packet corresponds to the second information, wherein the method further includes: when the second information corresponding to the first data packet is the same as the second information corresponding to the second data packet, determining the association between the second data packet and the first data packet.

[0013] For example, the second information is a first identifier. When the first identifier corresponding to the first data packet is the same as the first identifier corresponding to the second data packet, the first network device determines that the second data packet is associated with the first data packet.

[0014] Based on the above solution, the first network device can determine that data packets carrying the same second information are associated with each other, wherein synchronization is required between the associated data packets. Therefore, the above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between data streams and thus enhancing the user experience.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the first data packet corresponds to the second information, wherein the method further includes: receiving the first data packet from the second network device, and the second information is also used to indicate that the first data packet is a synchronization reference for the data packet of the second QoS flow.

[0016] For example, the second information is a second identifier, the first network device receives the first data packet from the second network device, the first data packet corresponds to the second identifier, and the second identifier is also used to indicate that the first data packet is a synchronization reference for the data packet of the second QoS flow.

[0017] Based on the above scheme, the second information can indicate the first data packet as the reference data packet of the second QoS flow, which enables the first network device to identify the reference data packet and synchronization data packet that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0018] In combination with the first aspect, in some implementations of the first aspect, the method further includes: after the first network device receives the first data packet, when the first network device receives the second data packet from the second network device, determining that the second data packet is associated with the first data packet.

[0019] Based on the above solution, the second identifier can indicate that the first data packet serves as a reference data packet for data packets in the synchronization stream. The first network device can then determine that data packets in the synchronization stream received after the reference data packet are associated with the reference data packet. This solution enables the first network device to identify the reference data packet and the synchronization data packet that require synchronization, further improving the synchronization between data streams and thereby enhancing the user experience.

[0020] In combination with the first aspect, in some implementations of the first aspect, the second network device is a user plane function network element.

[0021] In combination with the first aspect, in certain implementations of the first aspect, the second information also indicates a first duration, wherein the method further includes: determining the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow based on the moment when the first network device receives the data packets of the first QoS flow, the first duration and the moment when the first network device receives the data packets of the second QoS flow.

[0022] Based on the above solution, the first network device can determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the time when the first network device receives the data packets on the reference stream, the first duration, and the time when the first network device receives the data packets on the synchronization stream. The above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams, thereby enhancing the user experience.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow is determined based on the moment when the first network device receives the data packet of the first QoS flow, the first duration, and the moment when the first network device receives the data packet of the second QoS flow, including: when the first network device receives the second data packet within the first duration from the time when the first network device receives the first data packet, determining that the second data packet is associated with the first data packet.

[0024] Based on the above scheme, the first network device can determine that the data packets received within the first time period after receiving the reference data packet are synchronization data packets, which enables the first network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0025] In combination with the first aspect, in certain implementations of the first aspect, the first duration is determined based on first jitter information and / or second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0026] Based on the above scheme, the first duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0027] In combination with the first aspect, in certain implementations of the first aspect, the association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow is determined based on the moment when the first network device receives the data packet of the first QoS flow, the first duration, and the moment when the first network device receives the data packet of the second QoS flow, including: determining the second duration based on the first jitter information and / or the second jitter information, and the first duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; within the second duration from the time when the first network device receives the first data packet, if the first network device receives the second data packet, determining that the second data packet is associated with the first data packet.

[0028] Based on the above solution, the first network device takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the first duration to obtain the second duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0029] In combination with the first aspect, in certain implementations of the first aspect, the synchronization delay information between the first QoS flow and the second QoS flow corresponds to a preset duration, wherein sending the second data packet according to the first moment and the synchronization delay information includes: sending the second data packet within the preset duration from the first moment.

[0030] Based on the above solution, the first network device can send the synchronization data packet within the preset time length after the reference data packet is received. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization between the synchronization data packet and the reference data packet. The synchronization data packet and the reference data packet belong to data streams of different modes. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

[0031] In combination with the first aspect, in certain implementations of the first aspect, the first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

[0032] Based on the above solution, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modalities, thereby improving user experience.

[0033] In combination with the first aspect, in some implementations of the first aspect, the first information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow.

[0034] Based on the above scheme, the first information can be carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. Therefore, the first network device can obtain the synchronization delay information between the baseline flow and the synchronization flow, thereby improving the synchronization effect between the baseline flow and the synchronization flow.

[0035] In combination with the first aspect, in certain implementations of the first aspect, the first information is also used to instruct the first network device to perform synchronization between the first QoS flow and the second QoS flow based on at least two associated data packets, and the at least two associated data packets are data packets with an associated relationship on the first QoS flow and the second QoS flow, respectively.

[0036] Based on the above solution, the first network device can determine to perform synchronization between multiple QoS flows at the granularity of associated data packets based on the first information. The method provided in the embodiment of the present application can perform synchronization between multiple QoS flows at a finer granularity, thereby improving the synchronization effect.

[0037] In a second aspect, a data transmission method is provided. The method can be performed by a second network device, or by a component (e.g., a processor, chip, or chip system) in the second network device, or by a logic module or software that implements all or part of the functions of the second network device. The method includes: obtaining second information indicating an association between a data packet of a first QoS flow and a data packet of a second QoS flow; and sending the second information to the first network device.

[0038] Optionally, the second network device may be a user plane function network element.

[0039] Based on the above scheme, the second network device can send the second information to the first network device, so that the first network device can determine the association between the data packets of the first QoS flow and the data packets of the second QoS flow based on the second information, thereby enabling the first network device to identify the baseline data packets and synchronization data packets that need to be synchronized, thereby realizing synchronization between multiple data streams.

[0040] In combination with the second aspect, in certain implementations of the second aspect, the first data packet corresponds to the second information, and the second data packet corresponds to the second information, wherein sending the second information to the first network device includes: sending the first data packet and the second data packet to the first network device, wherein the first data packet is transmitted through the first QoS flow, and the second data packet is transmitted through the second QoS flow.

[0041] For example, the second information is a first identifier, wherein the first data packet corresponds to the first identifier, and the second data packet corresponds to the first identifier.

[0042] Based on the above solution, the second network device can cause associated data packets to correspond to the same second information, where synchronization is required between the associated data packets. Therefore, the above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between data streams and thus enhancing the user experience.

[0043] In combination with the second aspect, in certain implementations of the second aspect, the second information is also used to indicate at least one data packet of the synchronization reference of the data packets of the second QoS flow, wherein sending the second information to the first network device includes: sending a first data packet to the first network device, wherein the first data packet corresponds to the second information.

[0044] For example, the second information is a second identifier, wherein the first data packet corresponds to the second identifier, and the second identifier is used to indicate that the first data packet is a synchronization reference of a data packet of the second QoS flow.

[0045] Based on the above solution, the second network device indicates the reference data packet through the second information. The reference data packet can serve as a synchronization reference for the data packets of the synchronization stream. This solution enables the first network device to identify the reference data packet and the synchronization data packet that need to be synchronized, further improving the synchronization effect between data streams and thus enhancing the user experience.

[0046] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving indication information from a third network device, the indication information being used to trigger the second network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow; wherein, obtaining the second information includes: determining the second information based on the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0047] Based on the above solution, after receiving the indication information, the second network device can identify the association between the data packets of the reference stream and the data packets of the synchronization stream. Therefore, the first network device can identify the reference data packets and synchronization data packets that need to be synchronized based on the second information determined and sent by the second network device. The above solution further improves the synchronization effect between data streams, thereby improving the user experience.

[0048] In combination with the second aspect, in some implementations of the second aspect, the method also includes: receiving a target identifier from an application function network element, wherein the target identifier is used to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0049] Based on the above solution, the second network device can determine the association between the data packets of the reference stream and the data packets of the synchronization stream based on the target identifier, where synchronization is required between the associated data packets. Therefore, the above solution enables the second network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams and thus enhancing the user experience.

[0050] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving a first data packet and a second data packet from the application function network element, wherein the first data packet corresponds to the target identifier and the second data packet corresponds to the target identifier; when the target identifier corresponding to the second data packet is the same as the target identifier corresponding to the first data packet, determining that the first data packet and the second data packet are associated.

[0051] Based on the above solution, the second network device can determine that data packets carrying the same identifier are associated with each other, where synchronization is required between the associated data packets. Therefore, the above solution enables the second network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between data streams and thus enhancing the user experience.

[0052] In combination with the second aspect, in certain implementations of the second aspect, the target identifier is also used to indicate at least one data packet of the synchronization reference of the data packet of the second QoS flow, wherein receiving the target identifier from the application function network element includes: receiving a first data packet, the first data packet corresponding to the target identifier, and after the second network device receives the first data packet, when the second network device receives a second data packet, determining that the second data packet is associated with the first data packet.

[0053] Based on the above solution, the target identifier can indicate that the first data packet serves as a reference data packet for the synchronization stream, and the second network device can determine that data packets of the synchronization stream received after the reference data packet are associated with the reference data packet. The above solution enables the first network device to identify the reference data packet and the synchronization data packet that need to be synchronized, further improving the synchronization effect between data streams, thereby enhancing the user experience.

[0054] In combination with the second aspect, in certain implementations of the second aspect, the indication information is also used to indicate a third duration, wherein the method further includes: determining the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow based on the moment when the second network device receives the data packets of the first QoS flow, the third duration and the moment when the second network device receives the data packets of the second QoS flow.

[0055] Based on the above solution, the second network device can determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the time when the second network device receives the data packets on the reference stream, the third duration, and the time when the second network device receives the data packets on the synchronization stream. This solution enables the second network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between the data streams and thereby enhancing the user experience.

[0056] In combination with the second aspect, in certain implementations of the second aspect, the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow is determined based on the moment when the second network device receives the data packet of the first QoS flow, the third time duration and the moment when the second network device receives the data packet of the second QoS flow, including: if the second network device receives the second data packet within the third time duration from the time when the second network device receives the first data packet, determining that the second data packet is associated with the first data packet.

[0057] Based on the above scheme, the second network device can determine that the data packets received within the third time period after receiving the reference data packet are synchronization data packets, which enables the second network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0058] In combination with the second aspect, in some implementations of the second aspect, the third duration is determined based on first jitter information and / or second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0059] Based on the above scheme, the third duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0060] In combination with the second aspect, in certain implementations of the second aspect, the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow is determined based on the moment when the second network device receives the data packet of the first QoS flow, the third time duration and the moment when the second network device receives the data packet of the second QoS flow, including: determining a fourth time duration based on the first jitter information and / or the second jitter information, and the third time duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; within the fourth time duration from the time when the second network device receives the first data packet, if the second network device receives the second data packet, it is determined that the second data packet is associated with the first data packet.

[0061] Based on the above solution, the second network device takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the third duration to obtain a fourth duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0062] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving the first data packet from the application function network element; determining a target identifier corresponding to the first data packet, the target identifier being used to indicate the first data packet as a synchronization reference for the data packet of the second QoS flow; wherein, sending the first data packet to the first network device includes: sending the first data packet to the first network device, the first data packet corresponding to the second information.

[0063] Based on the above solution, the target identifier can indicate that the first data packet serves as a reference data packet for the data packets on the synchronization stream. Upon recognizing that the first data packet corresponds to the target identifier, the second network device can cause the first data packet sent to the first network device to correspond to the second identifier. Therefore, the above solution enables the first network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between data streams and thereby enhancing the user experience. Furthermore, in the above solution, the second network device does not need to identify the reference and synchronization data packets, thereby improving data transmission efficiency.

[0064] In combination with the second aspect, in certain implementations of the second aspect, the first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

[0065] Based on the above solution, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modalities, thereby improving user experience.

[0066] In a third aspect, a data transmission method is provided. The method can be performed by a third network device, or by a component (e.g., a processor, chip, or chip system) within the third network device, or by a logic module or software capable of implementing all or part of the functions of the third network device. The method includes: obtaining first information, wherein the first information is used to indicate synchronization delay information between a first QoS flow and a second QoS flow; and sending the first information to the first network device.

[0067] Optionally, the third network device may be a session management network element.

[0068] Based on the above solution, the third network device can obtain the synchronization delay information between the reference stream and the synchronization stream and send it to the first network device, so that the first network device can send the data packets on the reference stream and the data packets on the synchronization stream according to the synchronization delay information. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization between the synchronization data packet and the reference data packet. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

[0069] In combination with the third aspect, in certain implementations of the third aspect, the indication information is used to trigger the second network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow, wherein the method also includes: sending the indication information to the second network device.

[0070] Based on the above solution, the third network device can send indication information to the second network device, so that the second network device can identify the association between the data packets of the reference stream and the data packets of the synchronization stream. The above solution further improves the synchronization effect between data streams, thereby improving the user experience.

[0071] In combination with the third aspect, in certain implementations of the third aspect, the indication information is further used to indicate a third duration, and the third duration is used to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0072] Based on the above solution, the third network device can also indicate a third duration to the second network device via indication information, so that the second network device can determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the third duration. This solution enables the second network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between the data streams and thereby enhancing the user experience.

[0073] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving third information from an application function network element, the third information being used to indicate a fifth duration; determining the third duration based on the first jitter information and / or the second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0074] Based on the above scheme, the third duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0075] In combination with the third aspect, in certain implementations of the third aspect, the second information is used to indicate a first duration, wherein the first duration is used to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow, wherein the method also includes: sending the second information to the first network device.

[0076] Based on the above solution, the third network device can indicate the first duration to the first network device via the second information, allowing the first network device to determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the first duration. This solution enables the first network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between the data streams and thereby enhancing the user experience.

[0077] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving third information from an application function network element, the third information being used to indicate a fifth duration; determining the first duration based on the first jitter information and / or the second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0078] Based on the above solution, the third network device can take into account the jitter of the first QoS flow and / or the jitter of the second QoS flow based on the fifth duration indicated by the application function network element to obtain the first duration. In the event of a delay in receiving data packets, the solution provided by the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0079] In combination with the third aspect, in some implementations of the third aspect, the method further includes: receiving fourth information from the second network device, where the fourth information is used to indicate the first jitter information and / or the second jitter information.

[0080] Based on the above solution, the third network device can obtain the first jitter information and / or the second jitter information from the second network device, thereby taking into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the fifth duration indicated by the application function network element to obtain the first duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0081] In combination with the third aspect, in certain implementations of the third aspect, the first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

[0082] Based on the above solution, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modalities, thereby improving user experience.

[0083] In combination with the third aspect, in certain implementations of the third aspect, the first information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow.

[0084] Based on the above scheme, the first information can be carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. Therefore, the third network device can indicate the synchronization delay information between the baseline flow and the synchronization flow to the first network device, thereby improving the synchronization effect between the baseline flow and the synchronization flow.

[0085] In combination with the third aspect, in certain implementations of the third aspect, the first information is also used to instruct the first network device to perform synchronization between the first QoS flow and the second QoS flow based on at least two associated data packets, and the at least two associated data packets are data packets that have an associated relationship on the first QoS flow and the second QoS flow, respectively.

[0086] Based on the above solution, the first network device can determine to perform synchronization between multiple QoS flows at the granularity of associated data packets based on the first information. The method provided in the embodiment of the present application can perform synchronization between multiple QoS flows at a finer granularity, thereby improving the synchronization effect.

[0087] In a fourth aspect, a communication device is provided, comprising a processor, wherein the processor is configured to, by executing a computer program or instruction, or by processing a circuit, enable the communication device to execute the first aspect and any possible method of the first aspect, or enable the communication device to execute the second aspect and any possible method of the second aspect, or enable the communication device to execute the third aspect and any possible method of the third aspect.

[0088] In one possible implementation, the communication device further includes a memory for storing the computer program or instructions. Furthermore, the processor is specifically configured to call and execute the computer program or computer instructions stored in the memory, so that the processor implements any one of the first, second, or third aspects.

[0089] In one possible implementation, the communication device further includes a transceiver (also referred to as a communication interface), the transceiver being configured to input and / or output signals via the communication interface, and the processor being configured to control the transceiver to transmit and receive signals.

[0090] In a fifth aspect, a communication device is provided, comprising a processing circuit (also referred to as a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used to input and / or output signals, the processing circuit being used to execute the first aspect and any possible method of the first aspect; or the processing circuit being used to execute the second aspect and any possible method of the second aspect; or the processing circuit being used to execute the third aspect and any possible method of the third aspect.

[0091] In one possible implementation, the processor is configured to communicate with other devices via an interface circuit and execute the method in any one of the implementations of the first, second, or third aspects.

[0092] In a sixth aspect, a communication device is provided. The communication device may be a first network device, or a device or module for performing the functions of the first network device; the communication device may be a second network device, or a device or module for performing the functions of the second network device; the communication device may be a third network device, or a device or module for performing the functions of the third network device.

[0093] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0094] In another possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0095] In another possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0096] In the seventh aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the first aspect and any possible method of the first aspect are executed; or, the second aspect and any possible method of the second aspect are executed; or, the third aspect and any possible method of the third aspect are executed.

[0097] In an eighth aspect, a computer program product is provided, comprising a computer program or instructions, which, when run on a computer, causes the first aspect and any possible method of the first aspect to be executed; or causes the second aspect and any possible method of the second aspect to be executed; or causes the third aspect and any possible method of the third aspect to be executed.

[0098] In a ninth aspect, a communication device is provided, comprising a processor connected to a memory and configured to call a program stored in the memory to execute any possible method of the first, second, or third aspects. The memory may be located within or outside the communication device. The processor may include one or more processors.

[0099] In one implementation, the communication device of the fourth, fifth, and sixth aspects may be a chip or a chip system.

[0100] In a tenth aspect, a chip device is provided, comprising a processor for calling a computer program or computer instruction in a memory so that the processor executes any one of the implementations of the first, second or third aspects above.

[0101] Optionally, the processor is coupled to the memory via an interface.

[0102] In the eleventh aspect, a communication system is provided, which includes a first network device, a second network device and a third network device; the first network device is used to execute the method shown in the first aspect, the second network device is used to execute the method shown in the second aspect, and the third network device is used to execute the method shown in the third aspect.

[0103] The description of the advantageous effects of any of the fourth to eleventh aspects etc. may refer to the description of the advantageous effects of the first or second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0104] FIG1 is a schematic diagram of a network architecture of a communication system applicable to an embodiment of the present application.

[0105] FIG2 is a schematic diagram of data transmission.

[0106] FIG3 is a schematic flowchart of a data transmission method provided in an embodiment of the present application.

[0107] FIG4 is a schematic diagram of a data transmission method provided in an embodiment of the present application.

[0108] FIG5 is a schematic flowchart of another data transmission method provided in an embodiment of the present application.

[0109] FIG6 is a schematic diagram of a method for associating data packets of different data streams provided in an embodiment of the present application.

[0110] FIG7 is a schematic flowchart of another data transmission method provided in an embodiment of the present application.

[0111] FIG8 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0112] FIG9 is a schematic block diagram of another communication device according to an embodiment of the present application.

[0113] FIG10 is a schematic block diagram of another communication device according to an embodiment of the present application.

[0114] FIG11 is a schematic block diagram of yet another communication device according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0116] The technical solution provided by this application can be applied to various communication systems, such as the fifth generation (5 th generation, 5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation (6 th The technical solution provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0117] Figure 1 shows a schematic diagram of the network architecture of a communication system applicable to an embodiment of the present application. The network architecture includes terminal equipment, access network equipment, access and mobility management network element, session management network element, user plane function network element, policy control network element, network slice selection network element, network warehouse function network element, network data analysis network element, unified data management network element, unified data storage network element, authentication service function network element, network capability exposure network element, application function network element, and a data network (DN) connected to the operator's network. The terminal equipment can send service data to the data network through the access network equipment and user plane function network element, and receive service data from the data network.

[0118] A terminal device is a device with wireless transceiver capabilities, which can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can communicate with the core network via the radio access network (RAN) and exchange voice and / or data with the RAN. The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver capabilities, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of this application do not limit the application scenarios. Terminal devices may also be referred to as user equipment (UE), mobile stations, and remote stations. The embodiments of this application do not limit the specific technology, device form, or name of the terminal devices.

[0119] Access network equipment is a device in the network used to connect terminal devices to the wireless network. Access network equipment can be a node in the radio access network, which can also be called a base station, or a radio access network ((radio) access network, (R)AN) node (or device). In addition, (R)AN can also be equivalent to the next generation radio access network (NG-RAN) in the layer 3 relay architecture. In other words, (R)AN can be NG-RAN. For ease of description, RAN is sometimes used below to refer to access network equipment. It is understandable that RAN can also be AN.

[0120] The access network equipment may include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or an evolved LTE system (LTE-Advanced, LTE-A), such as a traditional macro base station eNB and a micro base station eNB in ​​a heterogeneous network scenario, or may also include a next generation node B (gNB) in a 5G or NR system, or may also include a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a transmission reception point (TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), a base band pool BBU pool, or a WiFi access point (AP), etc., or may also include a centralized unit (CU) and a distributed unit (CU) in a cloud radio access network (CloudRAN) system. Unit (DU), not limited in the embodiments of the present application. In a separate deployment scenario where the access network equipment includes a CU and a DU, the CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU mainly supports the radio link control layer (RLC), media access control layer (MAC), and physical layer protocols.

[0121] The access and mobility management network element is mainly used for the attachment and tracking area update processes of terminals in mobile networks. The access and mobility management network element can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocation of tracking area list (TA list), legal monitoring, access authorization, authentication and mobility management, etc., and transparently route session management (SM) messages to the session management network element. In the fifth generation (5G) communication system, the access and mobility management network element can be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the mobility management network element can still be the AMF network element, or it can have other names, which is not limited in this application.

[0122] The session management network element is mainly used for session and bearer management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to terminals and selecting user plane function network elements that provide message forwarding functions. In 5G communication systems, the session management network element can be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element can still be an SMF network element, or it can have other names, which are not limited by this application.

[0123] The user plane function network element is mainly used to process user messages, such as forwarding, billing, legal interception, etc. In addition, the user plane function network element can be used for routing and forwarding, threshold control, traffic monitoring, verification and other functions of user plane data. The user plane function network element can also be used for the management of UE IP addresses, the management of core network (CN) tunnel information, etc. The user plane function network element can also be called a protocol data unit (PDU) session anchor (PSA). In a 5G communication system, the user plane function network element can be a user plane function (UPF). In future communication systems (such as 6G communication systems), the user plane function network element can still be a UPF network element, or it can have other names, which is not limited in this application.

[0124] The policy control network element includes user subscription data management functions, policy control functions, billing policy control functions, QoS control, etc. In the 5G communication system, the policy control network element can be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or it can have other names, which is not limited in this application.

[0125] The network slice selection function network element is mainly used to select a suitable network slice for the service of the terminal device. In the 5G communication system, the network slice selection network element can be a network slice selection function (NSSF) network element. In future communication systems (such as 6G communication systems), the network slice selection network element can still be an NSSF network element, or it can have other names, which is not limited by this application.

[0126] The network repository function network element is mainly used to provide registration and discovery functions for network elements or services provided by network elements. In 5G communication systems, the network repository function network element can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network repository function network element can still be an NRF network element, or it can have other names, which is not limited by this application.

[0127] The network data analysis network element can collect data from various network functions (NFs), such as policy control network elements, session management network elements, user plane function network elements, access and mobility management network elements, and application function network elements (through network capability exposure function network elements), and perform analysis and prediction. In a 5G communication system, the network data analysis network element can be a network data analysis function (NWDAF). In future communication systems (such as 6G communication systems), the network data analysis network element can still be an NWDAF network element, or it can have other names, which is not limited by this application.

[0128] The unified data management network element is mainly used to manage the contract information of terminal devices. In the 5G communication system, the unified data management network element can be unified data management (UDM). In future communication systems (such as 6G communication systems), the unified data management network element can still be the UDM network element, or it can have other names, which is not limited by this application.

[0129] The unified data storage network element is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format. In the 5G communication system, the unified data storage network element can be a unified data repository (UDR). In future communication systems (such as 6G communication systems), the unified data storage network element can still be a UDR network element, or it can have other names, which is not limited by this application.

[0130] The authentication service function network element is mainly used to perform security authentication on the terminal device. In the 5G communication system, the authentication service function network element can be the authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function network element can still be the AUSF network element, or it can have other names, which is not limited by this application.

[0131] A network capability exposure network element can controllably expose some network functions to applications. In a 5G communication system, a network capability exposure network element can be a network exposure function (NEF). In future communication systems (such as a 6G communication system), the network capability exposure network element can still be an NEF network element, or it can have other names, which are not limited by this application.

[0132] The application function network element can provide service data of various applications to the control plane network elements of the operator's communication network, or obtain network data information and control information from the control plane network elements of the communication network. In the 5G communication system, the application function network element can be an application function (AF). In future communication systems (such as 6G communication systems), the application function network element can still be an AF network element, or it can have other names, which is not limited by this application. For example, the application function network element can also be called an application server or a service server. In addition, the application function network element can be deployed in the operator network or by a third party.

[0133] Data networks are primarily used to provide data transmission services to terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or proprietary networks deployed jointly by operators, such as those configured with IP multimedia core network subsystem (IMS) services. Data networks can also be provided by third parties.

[0134] In the architecture shown in Figure 1, the interface names and functions between the various network elements are as follows:

[0135] 1. N1: The interface between AMF and UE, which can be used to deliver QoS control rules to UE.

[0136] 2. N2: The interface between AMF and (R)AN, which can be used to transmit radio bearer control information from the core network side to the RAN.

[0137] 3. N3: Interface between RAN and UPF, used to transfer uplink or downlink user plane data between RAN and UPF.

[0138] 4. N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.

[0139] 5. N6: Interface between UPF and DN, used to transmit uplink or downlink user data flow between UPF and DN.

[0140] 6. The service-oriented interfaces Nnssf, Nnef, Nausf, Nnrf, Namf, Npcf, Nsmf, and Nudm are respectively provided by the above-mentioned NSSF network element, NEF network element, AUSF network element, NRF network element, AMF network element, PCF network element, SMF network element, and UDM network element, and are used to call corresponding service-oriented operations.

[0141] It should be understood that the above-mentioned network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the above-mentioned network elements or functions can be implemented by one device, or by multiple devices together, or can be a functional module within a device, and the embodiments of the present application do not specifically limit this. Optionally, the above-mentioned network elements can be specific network elements of the 5G core network in the Layer 3 relay architecture.

[0142] It should also be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above networks may continue to use the terminology in 5G, or other names may be used. The interface name between the various network elements in Figure 1 is only an example. The name of the interface in the specific implementation may be other names, and this application does not make specific limitations on this. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

[0143] It should be noted that the aforementioned "network element" may also be referred to as an entity, device, apparatus, or module, and this application does not specifically limit this. Furthermore, in this application, for ease of understanding and explanation, the term "network element" is omitted in some descriptions. For example, the PCF network element is referred to as PCF. In this case, the "PCF" should be understood as a PCF network element or PCF entity. The following descriptions of identical or similar situations are omitted.

[0144] As mentioned above, how to improve the data synchronization effect of multiple modal data flows is an urgent problem to be solved. For example, the application function network element can provide the synchronization requirements of multiple modal service data flows (SDFs), as shown in Table 1.

[0145] Table 1

[0146] Refer to Table 1. For hearing and vision, if RAN sends visual data first, the auditory data associated with the visual data must be sent within 20ms after the visual data is sent; if RAN sends auditory data first, the visual data associated with the auditory data must also be sent within 20ms after the auditory data is sent. For hearing and touch, if RAN sends tactile data first, the auditory data associated with the tactile data must be sent within 25ms after the tactile data is sent; if RAN sends auditory data first, the tactile data associated with the auditory data must be sent within 12ms after the auditory data is sent. For vision and touch, if RAN sends tactile data first, the visual data associated with the tactile data must be sent within 20ms after the tactile data is sent; if RAN sends visual data first, the tactile data associated with the visual data must be sent within 30ms after the visual data is sent.

[0147] If it is later than the above threshold, the data of the SDF of the two modes corresponding to the threshold are considered to be out of sync. For example, for hearing and vision, if the visual data is sent first, and the auditory data associated with the visual data is sent 20ms after the visual data is sent, the user may perceive that the vision and hearing are out of sync, which reduces the viewing experience. It should be noted that the synchronization requirements provided by the application function network element are not limited to the above Table 1. For example, the requirement for tactile delay compared to visual can also be 5ms.

[0148] The data included in the data stream is represented below in units of data packets. For example, in the present application, a data packet can be a data message based on a protocol data unit (PDU) (for example, a PDU can refer to an IP packet), or a set (PDU set) composed of one or more PDUs, and this application does not impose specific restrictions. Among them, a PDU set can refer to a payload that carries an information unit generated by the application layer. For example, a PDU set can be one or more frames for an XR service, or one or more video slices, etc.

[0149] In addition, data streams can be divided into triplets, quintuples, or application identifiers. For example, when data streams are divided into triplets, data packets with the same protocol type, local IP address, and local port (or destination IP address and destination port) are divided into the same data stream. For another example, when data streams are divided into quintuples, data packets with the same protocol type, local IP address, local port, destination IP address, and destination port are divided into the same data stream. For another example, when data streams are divided into application identifiers, data packets with the same application identifier are divided into the same data stream.

[0150] However, synchronization requirements at the data stream level don't reflect the specific packets in the data stream that require synchronization, making accurate synchronization impossible. For example, for one or more packets in the visual data stream, it's unclear which packets in the tactile data stream are associated with which packets in the visual data stream. Figure 2 illustrates this in detail.

[0151] FIG2 is a schematic diagram of data transmission.

[0152] As shown in Figure 2 , data stream 1 and data stream 2 may belong to different modes. Data stream 1 contains packets 11 to 15, while data stream 2 contains packets 21 and 22. The horizontal axis represents the time when the RAN sends packets, with the further to the right the later the packets are sent.

[0153] Packets 11 through 13 in data flow 1 arrive at the RAN first, while packet 21 in data flow 2 arrives later. In other words, the RAN sends packets 11 through 13 in data flow 1 before packet 21 in data flow 2. If the aforementioned data flow-based granularity solution is adopted, the RAN only receives synchronization requests at the data flow granularity from the application function network element. It is unclear which packet 11 through 13 packet 21 needs to synchronize with, and therefore cannot accurately determine the transmission delay of packet 21.

[0154] For example, data stream 1 is a tactile data stream, and data stream 2 is a visual data stream. If packet 21 needs to be synchronized with packet 11 (i.e., packet 11 is a tactile data stream associated with visual packet 21), but the RAN sends packet 21 based on the transmission time of packet 12 or packet 13, packet 21 is sent later and may not meet the synchronization requirement, causing the user to perceive a tactile and visual asynchrony. In other words, if packet 21 is a synchronization packet and packet 11 is a reference packet, and the RAN mistakenly determines that packet 12 or packet 13 is a reference packet, the synchronization requirement may not be met. Hereinafter, the data stream that transmits the reference packet is referred to as the reference stream, and the data stream that transmits the synchronization packet is referred to as the synchronization stream. It should be understood that if some packets transmitted on a data stream are reference packets and other packets are synchronization packets, the data stream will be used as the reference stream when transmitting the reference packets and as the synchronization stream when transmitting the synchronization packets. Alternatively, the data stream may be always referred to as the reference stream, but packets within the data stream may sometimes be used as reference packets and sometimes as synchronization packets. The synchronization packets are transmitted based on the reference packets.

[0155] The above solution will cause multiple data streams to be out of sync, resulting in a poor user experience.

[0156] FIG3 is a schematic flow chart of a data transmission method 300 provided in an embodiment of the present application. Method 300 can improve the data synchronization effect of multiple data streams. An embodiment of method 300 is described below with reference to FIG3.

[0157] S310: A third network device obtains first information, where the first information is used to indicate synchronization delay information between a first QoS flow and a second QoS flow.

[0158] Exemplarily, the first network device may be an access network device, and the third network device may be a session management network element.

[0159] Synchronization delay information can be a reflection of synchronization requirements. The synchronization delay information between the first QoS flow and the second QoS flow can correspond to a preset duration. This application does not limit the specific value of the preset duration. With reference to Table 1 above, when the first QoS flow is a visual flow and the second QoS flow is an auditory flow, the preset duration value can be 20ms. However, the preset duration value can also be selected without reference to Table 1. For example, the preset duration can be any value.

[0160] The first information may directly indicate the preset duration. The first information may also include or carry information about the preset duration, and indicate the preset duration through the information about the preset duration. In other words, the information about the preset duration may be carried in the first information.

[0161] It should be understood that the synchronization delay information between the first QoS flow and the second QoS flow can be understood as the presence of a synchronization requirement between the first QoS flow and the second QoS flow. For example, the synchronization delay information can be represented by a synchronization delay budget (SyncDB), and the preset duration can correspond to the value of the SyncDB. The synchronization delay information can also be represented by other names, which are not limited in this application. For example, the synchronization delay information can be represented by other names such as delay budget, delay difference, synchronization delay difference, transmission time difference or arrival time difference. Furthermore, the synchronization delay information can also be understood as the synchronization delay information between the data packets that are associated with the first QoS flow and the second QoS flow.

[0162] As an example, the first information can be used only to indicate the preset duration, so that the first network device can determine through another information that there is an association relationship or synchronization requirement between the first QoS flow and the second QoS flow. Therefore, the first network device can determine through the first information and the other information that the synchronization delay information between the first QoS flow and the second QoS flow is the preset duration. For example, the first information indicates that the value of the preset duration is 20ms, and the other information indicates that the first QoS flow is associated with the second QoS flow or has a synchronization requirement. The first network device can determine that the synchronization delay information between the first QoS flow and the second QoS flow is 20ms. The association relationship between the first QoS flow and the second QoS flow can also be understood as there is a synchronization requirement between the first QoS flow and the second QoS flow.

[0163] As another example, the first information can also be used to indicate the synchronization delay information between the first QoS flow and the second QoS flow. That is, the first network device can determine that the synchronization delay information between the first QoS flow and the second QoS flow is a preset duration only through the first information. For example, the first information can be (20ms, first QoS flow, second QoS flow). The first network device can determine that the synchronization delay information between the first QoS flow and the second QoS flow is 20ms based on the first information. For another example, the first information can indirectly indicate the relevance to the first QoS flow in other ways (for example, the first information is carried in the configuration information of the first QoS flow), and indicate the first QoS flow and the preset duration. The first network device can determine the synchronization delay information between the first QoS flow and the second QoS flow based on the first information.

[0164] Optionally, in some other implementation scenarios of the above embodiment, the first information is further used to indicate that synchronization between the first QoS flow and the second QoS flow is performed based on at least two associated data packets, where the at least two associated data packets are data packets with an associated relationship on the first QoS flow and the second QoS flow, respectively. It is understandable that in this case, the first information is also used to indicate that synchronization between the first QoS flow and the second QoS flow is performed based on packet granularity. S320: The first network device receives the first information. Accordingly, the third network device sends the first information to the first network device.

[0165] The third network device may directly send the first information to the first network device, or may send the first information to another network device, and the other network device may send the first information to the first network device.

[0166] Optionally, in other implementation scenarios of the above embodiment, the first information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. For example, the configuration information may be a QoS profile. Alternatively, the first information is carried in an N2 message sent by the third network device to the first network device. The third network device may send the N2 message directly to the first network device, or may send the N2 message to another network device, which in turn sends the N2 message to the first network device.

[0167] For example, the first information can be carried in the configuration information of the first QoS flow, and the first information can be "20ms->identifier of the second QoS flow", where "->" can mean "corresponding to", "relative to", or "based on". The first network device can determine that the synchronization delay information between the first QoS flow and the second QoS flow is 20ms. That is to say, the first QoS flow has a synchronization requirement relative to the second QoS flow, wherein the second QoS flow can be regarded as a reference data flow, and the first QoS flow can be regarded as a synchronization data flow. Alternatively, the second QoS flow has a synchronization requirement relative to the first QoS flow, wherein the first QoS flow can be regarded as a reference data flow, and the second QoS flow can be regarded as a synchronization data flow.

[0168] For another example, the first information can be carried in the configuration information of the second QoS flow, and the first information can be "20ms->identifier of the first QoS flow". The first network device can determine that the synchronization delay information between the second QoS flow and the first QoS flow is 20ms. In other words, the second QoS flow has a synchronization requirement relative to the first QoS flow, wherein the first QoS flow can be regarded as a reference data flow, and the second QoS flow can be regarded as a synchronization data flow. Alternatively, the first QoS flow has a synchronization requirement relative to the second QoS flow, wherein the second QoS flow can be regarded as a reference data flow, and the first QoS flow can be regarded as a synchronization data flow.

[0169] The first two examples can be understood as "unidirectional requirements," meaning one QoS flow has a synchronization requirement on the other, while the other QoS flow has no synchronization requirement on the first. For example, the tactile flow has a synchronization requirement on the visual flow, but the visual flow has no synchronization requirement on the tactile flow. However, this application is not limited to this. For example, it can also be a "bidirectional requirement," meaning that both QoS flows have synchronization requirements on each other. For example, the tactile flow has a synchronization requirement on the visual flow, but the visual flow also has a synchronization requirement on the tactile flow.

[0170] In the case of "bidirectional demand", it can be understood that the first information includes two parts, one part is the synchronization demand of one QoS flow for another QoS flow, and the other part is the synchronization demand of another QoS flow for this QoS. The corresponding preset duration can include two durations.

[0171] For the case of "bidirectional requirements", the configuration method of the first information can be to carry the first information in the configuration information of the first QoS flow or in the configuration information of the second QoS flow, or another method can be to carry the first information in the configuration information of the first QoS flow and the configuration information of the second QoS flow. For the first method, the first information can be carried in the configuration information of the first QoS flow. For example, the first information is "20ms->identifier of the second QoS flow, identifier of the second QoS flow->10ms", which means that the synchronization requirement of the second QoS flow relative to the first QoS flow is 20ms, and the synchronization requirement of the first QoS flow relative to the second QoS flow is 10ms, or the synchronization requirement of the first QoS flow relative to the second QoS flow is 20ms, and the synchronization requirement of the second QoS flow relative to the first QoS flow is 10ms. For the first method, the first information can also be carried in the configuration information of the second QoS flow. For example, the first information is "20ms->identifier of the first QoS flow, identifier of the first QoS flow->10ms", which means that the synchronization requirement of the first QoS flow relative to the second QoS flow is 20ms, and the synchronization requirement of the second QoS flow relative to the first QoS flow is 10ms, or, the synchronization requirement of the second QoS flow relative to the first QoS flow is 20ms, and the synchronization requirement of the first QoS flow relative to the second QoS flow is 10ms.

[0172] Another way of "bidirectional demand" may be to carry the first information in the configuration information of the first QoS flow and the configuration information of the second QoS flow. It should be understood that the first information includes two parts. One of the parts can be configured in the configuration information of the first QoS flow, and the other part can be configured in the configuration information of the second QoS flow. For example, one part of the first information is carried in the configuration information of the first QoS flow, which may be "20ms->identifier of the second QoS flow"; the other part of the first information is carried in the configuration information of the second QoS flow, which may be "20ms->identifier of the first QoS flow". In this way, the first QoS flow has a synchronization requirement relative to the second QoS flow, and the second QoS flow also has a synchronization requirement relative to the first QoS flow. The first QoS flow and the second QoS flow are each other's reference data flow and synchronization data flow.

[0173] The above configuration information may be configuration information in a QoS profile or other forms of configuration information. For example, it may be an N2 message sent by a third network device to a first network device. The third network device may send the N2 message directly to the first network device or send the N2 message to another network device, which in turn sends the N2 message to the first network device.

[0174] Based on the above scheme, the first information can be carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. Therefore, the first network device can obtain the synchronization delay information between the baseline flow and the synchronization flow, thereby improving the synchronization effect between the baseline flow and the synchronization flow.

[0175] It should be noted that the present application does not limit the first information to be carried in the configuration information. For example, the first information may also be carried in other information.

[0176] Optionally, in some other implementation scenarios of the above embodiments, the first information is also used to instruct the first network device to perform synchronization between the first QoS flow and the second QoS flow based on at least two associated data packets, and the at least two associated data packets are data packets with an associated relationship on the first QoS flow and the second QoS flow respectively.

[0177] According to the indication of the first information, the first network device needs to identify the association between the data packets of the first QoS flow and the data packets of the second QoS flow, and then apply the synchronization requirements between the first QoS flow and the second QoS flow to the transmission of the data packets with an association relationship on the first QoS flow and the second QoS flow. For the transmission of data packets that are not associated on the first QoS flow and the second QoS flow, there is no need to consider the synchronization requirements between the first QoS flow and the second QoS flow, that is, during the transmission process, they can be transmitted according to the packet delay budget (PDB) or PDU set delay budget (PSDB) of the first QoS flow and the second QoS flow respectively.

[0178] Based on the above solution, the first network device can determine to perform synchronization between multiple QoS flows at the granularity of associated data packets based on the first information. The method provided in the embodiment of the present application can perform synchronization between multiple QoS flows at a finer granularity, thereby improving the synchronization effect.

[0179] S330: The first network device sends a first data packet, the first data packet is transmitted through the first QoS flow, and the time when the first data packet is sent by the first network device is a first time. In other words, the first network device sends the first data packet at the first time.

[0180] The first data packet is transmitted through the first QoS flow. Therefore, the first data packet can also be referred to as the first data packet of the first QoS flow, or the first data packet on the first QoS flow.

[0181] For example, the first network device may send the first data packet to the terminal device, but this application is not limited thereto, and the first network device may also send the data packet to other devices.

[0182] The following assumes that the second QoS flow has synchronization requirements relative to the first QoS flow, and the first data packet is sent before the second data packet. The first data packet can be regarded as the reference data packet. This application does not limit the order in which the first network device receives the first data packet and the second data packet. The first data packet can be received by the first network device before the second data packet, and the second data packet can also be received by the first network device before the first data packet. The second data packet can be understood as the payload portion of the N6 data packet or the N3 data packet.

[0183] In the above embodiment, the first moment is the moment when the first network device sends the first data packet. In other embodiments, the first moment may be the moment when the first network device receives the first data packet.

[0184] S340: The first network device sends the second data packet according to the first moment and the preset duration, wherein the second data packet is transmitted through the second QoS flow, and wherein the second data packet is associated with the first data packet.

[0185] The first data packet is associated with the second data packet, or in other words, there is an association between the first data packet and the second data packet. This can also be understood as the first data packet and the second data packet being data packets in the first QoS flow and the second QoS flow that require synchronization. It should be understood that after receiving the first data packet and the second data packet, the first network device needs to determine whether the first data packet is associated with the second data packet. There are multiple solutions for how the first network device determines the association between the first data packet and the second data packet. The transmission time difference between the associated data packets needs to be within a preset time period so that the associated data packets meet the synchronization requirements. In other words, the associated data packets need to be synchronized based on the synchronization delay information so that the associated data packets meet the synchronization requirements. In other words, the association between the first data packet and the second data packet indicates that the first network device needs to send the first data packet and the second data packet based on the synchronization delay information. In other words, the first data packet and the second data packet are sent by the first network device based on the synchronization delay information. The first information can also be used to indicate the synchronization delay information between the first data packet and the second data packet.

[0186] For example, method 300 may further include: receiving second information, where the second information is used by the first network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow. Accordingly, the second network device sends the second information to the first network device. Alternatively, the third network device sends the second information to the first network device. The second information sent by the second network device or the third network device to the first network device may come from other network devices (e.g., an application function network element) or may be determined by the second network device or the third network device. Optionally, in the embodiment where the third network device sends the second information to the first network device, the second information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. In other words, the configuration information of the first QoS flow and / or the configuration information of the second QoS flow may include the second information. For example, the configuration information may be a QoS profile or other forms. For example, it may be an N2 message sent by the third network device to the first network device. In the implementation mode in which the second network device sends the second information to the first network device, the second information may be included in the data sent by the second network device to the first network device. For example, the second information may be included in the packet header information corresponding to the data packet sent by the second network device to the first network device. For details, please refer to the description of Figures 5 and 6 below, which will not be repeated here.

[0187] The third network device may directly send the second information to the first network device, or may send the second information to another network device, and the other network device may send the second information to the first network device.

[0188] Optionally, in some other implementation scenarios of the above embodiment, S340 includes: sending the second data packet within the preset time length starting from the first moment. Based on this solution, the first network device can send the synchronization data packet within the preset time length after the reference data packet is received. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization between the synchronization data packet and the reference data packet. Among them, the synchronization data packet and the reference data packet can belong to data streams of different modes respectively. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

[0189] It should be noted that the preset duration can also correspond to synchronization delay information between more QoS flows. For example, the preset duration can correspond to synchronization delay information between the first QoS flow, the second QoS flow, and the third QoS flow. The first network device can also send a third data packet according to the first moment and the preset duration, wherein the third data packet is transmitted through the third QoS flow, wherein the third data packet is associated with the first data packet. In other words, the first network device can send multiple data packets of different QoS flows according to the first moment and the preset duration. This application only takes two QoS flows as an example, and can also be applied to a larger number of QoS flows.

[0190] Figure 4 is a schematic diagram of a data transmission method 300 provided in an embodiment of the present application. The relationship between the preset duration, the first moment, the first data packet, and the second data packet is described below with reference to Figure 4. It is worth noting that the horizontal axis for the second QoS flow in Figure 4 represents the reception time. Moving rightward along the horizontal axis indicates that the first network device receives the data packet of the second QoS flow later.

[0191] Referring to Figure 4, the first QoS flow in Figure 4 corresponds to data flow 1 in Figure 2, and the second QoS flow in Figure 4 corresponds to data flow 2 in Figure 2, which will not be described in detail here. It should be noted that Figure 4 is only exemplary, and method 300 does not limit the specific sending and receiving conditions of the data packets of the first QoS flow and the data packets of the second QoS flow. The data packets of the first QoS flow and the data packets of the second QoS flow can also be more or less than those in Figure 4, and the sending intervals and receiving intervals of the data packets of the first QoS flow and the data packets of the second QoS flow can be larger or smaller than those in Figure 4. The sending intervals can be equal intervals or unequal intervals. The receiving intervals can be equal intervals or unequal intervals. In other words, Figure 4 does not constitute any limitation on the method 300 of the present application. Figure 4 is only an example given for the convenience of understanding.

[0192] Referring to FIG4 (a), assuming that data packet 12 is the first data packet, the time at which the first data packet is sent is the first time. Assuming that data packet 21 is the second data packet, the second data packet must be sent within the preset time period shown in FIG4. In other words, the first network device must send the second data packet before the latest sending time shown in FIG4.

[0193] If the first network device does not send the second data packet within the preset time period from the first moment, the first QoS flow and the second QoS flow will be out of synchronization, resulting in a poor user experience.

[0194] Based on the above solution, the first network device can send the synchronization data packet within the preset time length after the reference data packet is received. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization between the synchronization data packet and the reference data packet. Among them, the synchronization data packet and the reference data packet can respectively belong to data streams of different modes. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modes, thereby improving the user experience.

[0195] Referring to (b) and (c) in Figure 4, assuming that the time when the first data packet is sent is T1 (i.e., the first time is T1) and the time when the second data packet is received is T2, the actual budget of the second data packet can be obtained according to the following formula: Actual budget = preset duration - (T2 - T1)

[0196] Referring to (b) and (c) in Figure 4, the packet budget can be PSDB, which can represent the budget delay of a PDU set in a data stream. After the first network device receives a PDU set, it must send the PDU set out in the PSDB. In order to ensure user experience, each PDU set needs to be transmitted within a certain time interval. The so-called transmission refers to the transmission from the sending end to the receiving end of the PDU set. For downlink data transmission, PSDB can be the upper limit of the time delay of the transmission of the PDU set from the UPF to the UE, or the upper limit of the time that the data packet may be delayed between the UPF and the N6 termination point of the terminal. If the transmission time of a PDU set exceeds the PSDB, the user may perceive a large delay, which will cause a decline in user experience.

[0197] Alternatively, the PSDB mentioned above can be replaced by PDB. PDB and PSDB have similar meanings, but differ in that PSDB targets PDU sets, while PDB targets packets. In other words, the packet budget mentioned above can also be a PDB.

[0198] According to the size relationship between the actual budget and the packet budget, the sending time of the second data packet can be further determined. For example, referring to (b) in Figure 4, when the packet budget is greater than or equal to the actual budget, the second data packet can be sent according to the actual budget. In other words, the second data packet will be sent by the first network device before the actual budget, or in other words, the second data packet will be sent by the first network device before the latest sending time. For another example, referring to (c) in Figure 4, when the packet budget is less than or equal to the actual budget, the second data packet can be sent according to the packet budget. In other words, the second data packet will be sent by the first network device before the packet budget. The above scheme can also be understood as the first network device sending the second data packet according to the smaller value between the actual budget and the packet budget.

[0199] It can be understood that in the situations shown in (b) and (c) in Figure 4, the second data packet is sent by the first network device before the latest sending time, that is, it is sent by the first network device within the preset time length starting from the first moment.

[0200] The first network device can schedule and transmit the second data packet based on the actual budget, thereby ensuring a good user experience. Alternatively, the first network device can discard the data packet based on a specific policy. For example, if the current resource scheduling fails to meet the actual budget, the second data packet can be discarded. This is because failing to meet the actual budget means failing to meet synchronization requirements, which impacts the user experience. Therefore, the data packet can be discarded to conserve network resources.

[0201] As an example, the first network device may use different data radio bearers (DRBs) to transmit the first QoS flow and the second QoS flow respectively. For example, the first QoS flow corresponds to DRB1 transmission, and the second QoS flow corresponds to DRB2 transmission. After the first network device receives the first data packet, it may notify DRB2 corresponding to the second QoS flow to start a timer with a preset duration. If the second data packet is received while the timer is running, the first network device may determine the actual budget of the second data packet based on the remaining length of the timer, and the second data packet needs to be transmitted before the timer expires.

[0202] It should be noted that, as mentioned above, the preset duration can be configured in the reference flow (such as the first QoS flow) or in the synchronization flow (such as the second QoS flow). If the preset duration is configured in the reference flow, the first network device can use the preset duration in the configuration of the reference flow to determine the timer parameters of the DRB of the synchronization flow when configuring the DRB of the synchronization flow. If the preset duration is configured in the synchronization flow, the first network device can directly use the preset duration in the configuration of the synchronization flow to determine the timer parameters of the DRB of the synchronization flow when configuring the DRB of the synchronization flow.

[0203] Based on the above scheme, the first network device can send a synchronization data packet according to the time when the reference data packet is sent and the preset duration for indicating the synchronization delay information. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization of the synchronization data packet and the reference data packet. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience. Moreover, based on the above scheme, the third network device can obtain the synchronization delay information between the reference stream and the synchronization stream, and send it to the first network device, so that the first network device can send the data packet on the reference stream and the data packet on the synchronization stream according to the preset duration. In this way, the delay between the reference data packet and the synchronization data packet can meet the synchronization requirements, thereby achieving synchronization of the synchronization data packet and the reference data packet. Therefore, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of multiple data streams, thereby improving the user experience.

[0204] FIG5 is a schematic flow chart of another data transmission method 500 provided in an embodiment of the present application. Method 500 can improve the data synchronization effect of multiple data streams. An embodiment of method 500 is described below in conjunction with FIG5. It should be noted that method 500 can be combined with method 300.

[0205] S510: The second network device obtains second information, where the second information is used to indicate an association relationship between data packets of the first QoS flow and data packets of the second QoS flow.

[0206] As an example, the second network device obtaining the second information may include: the second network device determining an association relationship between packets of the first QoS flow and packets of the second QoS flow, and determining the second information based on the association relationship. As another example, the second network device may obtain the second information through other means without determining the association relationship between packets of the first QoS flow and packets of the second QoS flow. Examples of obtaining the second information through other means are described below.

[0207] S520: The second network device sends the second information to the first network device.

[0208] Optionally, in some other implementation scenarios of the above embodiments, the second information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow. In other words, the configuration information of the first QoS flow and / or the configuration information of the second QoS flow may include the second information. For example, the configuration information may be a QoS profile or other forms. For example, the configuration information may be an N2 message sent by a third network device to a first network device. In the implementation method in which the second information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow, the second information may be sent by a third network device to the first network device. Among them, the third network device may send the second information directly to the first network device, or may send the second information to another network device, and the other network device may send the second information to the first network device.

[0209] In other implementation scenarios, the second information may be carried in the data of the first QoS flow and / or the second QoS flow sent to the first network device. For example, the second information may be carried in the packet header information corresponding to the data packet of the first QoS flow and / or the second QoS flow. In the implementation method where the second information is carried in the data sent to the first network device, the second information may be sent by the second network device to the first network device. In other words, the second information may be carried in the data of the first QoS flow and / or the second QoS flow sent by the second network device to the first network device. For details, please refer to the description of Figures 5 and 6 below, which will not be repeated here.

[0210] Method 500 can be combined with method 300. Hereinafter, method 300 will be described first. For an embodiment of method 500, please refer to the description of FIG5 and FIG6 below.

[0211] Optionally, in other implementation scenarios of the above embodiment, method 300 further includes: receiving second information, where the second information is used by the first network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow. Accordingly, the second network device sends the second information to the first network device. That is, the second network device executes S520. Alternatively, a third network device sends the second information to the first network device. Alternatively, another network device (e.g., an application function network element) sends the second information to the first network device.

[0212] The third network device may directly send the second information to the first network device, or may send the second information to another network device, and the other network device may send the second information to the first network device.

[0213] Based on the above solution, the first network device can determine the association between the data packets of the reference stream and the data packets of the synchronization stream based on the second information, wherein synchronization is required between the associated data packets. Therefore, the above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams, thereby enhancing the user experience.

[0214] FIG6 is a schematic diagram of a method for associating data packets of different QoS flows provided by an embodiment of the present application. The following specifically describes an embodiment in which the second information is used by the first network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow, in conjunction with FIG6. It should be noted that the horizontal axis in FIG6 is the reception time of the data packet, which can be the reception time when the first network device receives the data packet, or the reception time when the second network device receives the data packet. The following first introduces an embodiment in which the reception time is the reception time when the first network device receives the data packet.

[0215] Optionally, in some other implementation scenarios of the above embodiment, the second information is a first identifier, wherein S520 includes: when the first identifier corresponding to the first data packet is the same as the first identifier corresponding to the second data packet, the first network device determines that the second data packet is associated with the first data packet. Correspondingly, the second network device sends the second information as the first identifier to the first network device, wherein the method 500 also includes: the second network device sends the first data packet and the second data packet to the first network device, wherein the first data packet corresponds to the first identifier, the second data packet corresponds to the first identifier, the first data packet is transmitted through the first QoS flow, and the second data packet is transmitted through the second QoS flow.

[0216] Exemplarily, the first identifier may be a synchronization sequence number (SSN). For example, the first data packet corresponds to an SSN, and the second data packet also corresponds to the same SSN.

[0217] The first identifier can be carried in the packet header information corresponding to the first data packet or the second data packet. For example, the packet header information can be the packet header information of an N3 data packet, and the packet header information of the N3 data packet can be understood as a general packet radio service tunneling protocol user plane (GTP-U) packet header. It should be noted that the first identifier may not be in the packet header information corresponding to the first data packet or the second data packet. For example, the first identifier can be a parameter independent of the first data packet or the second data packet. In the case where the first identifier is an independent parameter, the first identifier can include the identifier of the data packet, so that the first network device can determine the data packet corresponding to the first identifier based on the identifier of the data packet. For example, the first identifier can include the identifier of the first data packet.

[0218] Before the second network device sends the first data packet and the second data packet to the first network device, the method 500 may further include: determining that the first data packet and the second data packet have an association relationship; and adding the first identifier to first packet header information corresponding to the first data packet and first packet header information corresponding to the second data packet. The first packet header information may be packet header information of the N3 data packet.

[0219] Before the second network device sends the first data packet and the second data packet to the first network device, the method 500 may further include: determining that the first data packet and the second data packet have an association relationship; determining a first identifier, the first identifier corresponding to the first data packet, and the first identifier corresponding to the second data packet.

[0220] Referring to (a) in FIG6 , data packet 12 of the first QoS flow includes a first identifier 1, and data packet 21 of the second QoS flow also includes the first identifier 1. Therefore, the first network device can determine that data packet 12 with the first identifier 1 is associated with data packet 21. In addition, data packet 14 of the first QoS flow includes a first identifier 2, and data packet 22 of the second QoS flow also includes the first identifier 2. Therefore, the first network device can determine that data packet 14 with the first identifier 2 is associated with data packet 22. It can be understood that the first identifier 1 and the first identifier 2 are different first identifiers.

[0221] Furthermore, among the data packets with the same first identifier, the data packet that arrives at the first network device first can serve as a reference for the data packets that arrive later. In other words, among the data packets with the same first identifier, the data packet that arrives at the first network device first can serve as the reference data packet, and the data packet that is associated with the data packet that arrives at the first network device first and arrives at the first network device later can serve as the synchronization data packet.

[0222] Based on the above scheme, the first network device can determine that there is an association relationship between data packets carrying the same identifier, wherein there is a synchronization requirement between the data packets with the association relationship. Therefore, the above scheme enables the first network device to identify the baseline data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience. Moreover, based on the above scheme, the second network device can make the data packets with the association relationship have the same identifier, wherein there is a synchronization requirement between the data packets with the association relationship. Therefore, the above scheme enables the first network device to identify the baseline data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0223] Optionally, in some other implementation scenarios of the above embodiment, the second information is a second identifier, wherein S520 includes: the first network device receives the first data packet, the first data packet corresponds to the second identifier, and the second identifier is used to indicate that the first data packet serves as a synchronization reference for the data packet of the second QoS flow. Correspondingly, the second network device sends the second information as the second identifier to the first network device, wherein the method 500 also includes: the second network device sends the first data packet to the first network device, wherein the first data packet corresponds to the second identifier, and the second identifier is used to indicate that the first data packet serves as a synchronization reference for the data packet of the second QoS flow.

[0224] As an example, the second identifier can be any identifier that, after being identified by the first network device, is used to determine that the data packet corresponding to the second identifier is used as a synchronization reference for the data packets of the second QoS flow. As another example, the second identifier can be used to indicate a starting time, which is the time when the first network device receives the data packet corresponding to the second identifier. After this starting time, the data packets of the second QoS flow received by the first network device use the data packet received at the starting time as a synchronization reference.

[0225] The first data packet serves as a synchronization reference for the data packets of the second QoS flow. This can be understood as the first data packet serving as a benchmark data packet for the data packets of the second QoS flow, or as associating the first data packet with the data packets of the second QoS flow.

[0226] The second identifier may be carried in the header information corresponding to the first data packet or the second data packet. For example, the header information may be the header information of the N3 data packet. The second identifier may also not be in the header information corresponding to the first data packet or the second data packet. For example, the second identifier may be a parameter independent of the first data packet or the second data packet.

[0227] Before the second network device sends the first data packet and the second data packet to the first network device, the method 500 may further include: determining that the first data packet and the second data packet have an association relationship; and adding the second identifier to first packet header information corresponding to the first data packet. The first packet header information may be packet header information of the N3 data packet.

[0228] Before the second network device sends the first data packet and the second data packet to the first network device, the method 500 may further include: determining that the first data packet and the second data packet have an association relationship; and determining a second identifier, where the second identifier corresponds to the first data packet.

[0229] It should be noted that, in other embodiments, the second network device may determine the second identifier without determining whether the first data packet has an association relationship with the second data packet. Detailed descriptions will be given in the following embodiments and will not be repeated here.

[0230] Based on the above solution, the second identifier can indicate that the first data packet serves as a reference data packet for the data packets of the second QoS flow. This enables the first network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience. In addition, based on the above solution, the second network device indicates the reference data packet through the second information, and the reference data packet can serve as a synchronization reference for the data packets of the synchronization flow. The above solution enables the first network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0231] Optionally, in some other implementation scenarios of the above embodiments, the method 300 further includes: after the first network device receives the first data packet, when the first network device receives the second data packet, determining that the second data packet is associated with the first data packet.

[0232] Referring to (b) in FIG6 , data packet 12 includes or carries the second identifier. Therefore, the first network device can determine that data packet 21 is associated with data packet 12 because data packet 21 is received before data packet 12. Data packet 12 can be understood as the first data packet, and data packet 21 can be understood as the second data packet.

[0233] As an example, the method 300 also includes: after receiving the second data packet, receiving a third data packet, the third data packet corresponds to a second identifier, the second identifier is used to indicate that the third data packet serves as a synchronization reference for the data packet of the second QoS flow, and the third data packet is transmitted through the first QoS flow.

[0234] Furthermore, the method 300 further includes: after the first network device receives the first data packet and before the first network device receives the third data packet, associating the data packet of the second QoS flow received by the first network device with the first data packet.

[0235] 6 (b), since the first network device receives data packet 21 after receiving data packet 12 (corresponding to the first data packet) and before receiving data packet 14, the first network device can determine that data packet 21 is associated with data packet 12.

[0236] Furthermore, the method 300 further includes: after the first network device receives the third data packet, associating the data packet of the second QoS flow received by the first network device with the third data packet.

[0237] For example, data packet 14 includes or carries the second identifier, so the first network device can determine that data packet 22 is associated with data packet 14 because data packet 22 is received before data packet 14. Data packet 14 can be understood as a third data packet.

[0238] It can be understood that the second identifier corresponding to the third data packet and the second identifier corresponding to the first data packet can be the same identifier or different identifiers.

[0239] For the second identifier corresponding to the third data packet, the second identifier can be used to indicate the starting time and can also be used to indicate the ending time. The starting time is the time when the first network device receives the third data packet. After the starting time, the data packets of the second QoS flow received by the first network device use the third data packet received at the starting time as a synchronization reference. The ending time is also the time when the first network device receives the third data packet. Before the ending time, the data packets of the second QoS flow received by the first network device use the previous data packet (such as the first data packet) as a synchronization reference. In other words, in the time period between the starting time indicated by the second identifier corresponding to the first data packet and the ending time indicated by the second identifier corresponding to the third data packet, the data packets of the second QoS flow received by the first network device use the first data packet as a synchronization reference.

[0240] Referring to (b) in FIG6 , since the first network device receives data packet 21 within the time period from the start time indicated by the second identifier corresponding to data packet 12 to the end time indicated by the second identifier corresponding to data packet 14, data packet 21 uses data packet 12 as a synchronization reference.

[0241] Based on the above solution, the second identifier can indicate that the first data packet serves as a reference data packet for data packets in the synchronization stream. The first network device can then determine that data packets in the synchronization stream received after the reference data packet are associated with the reference data packet. This solution enables the first network device to identify the reference data packet and the synchronization data packet that require synchronization, further improving the synchronization between data streams and thereby enhancing the user experience.

[0242] Optionally, in some other implementation scenarios of the above embodiment, the receiving of the second information includes: receiving the second information from a second network device.

[0243] Optionally, in some other implementation scenarios of the above embodiments, the second information is used to indicate the first duration, wherein the method 300 also includes: determining the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow based on the moment when the first network device receives the data packets of the first QoS flow, the first duration and the moment when the first network device receives the data packets of the second QoS flow.

[0244] It is understood that the preset duration functions to determine the transmission delay of synchronization data packets, and the first duration functions to determine associated data packets. The first duration and the preset duration may be the same or different. The first duration and the preset duration may be a single parameter or two parameters. When the preset duration and the first duration are the same parameter, the parameter serves both to determine associated data packets and to determine the transmission delay.

[0245] The first duration may also have other names, such as associated time window, time window, associated duration, etc. This application limits the specific name of the first duration.

[0246] It should be noted that, when the second information is used to indicate the first duration, the second information can be received by the first network device from the third network device, or from the second network device. Although Figure 5 only shows a scenario in which the first network device receives the second information from the second network device, this application is not limited to this, and the first network device can also receive the second information from the third network device.

[0247] The second information sent by the second network device or the third network device to the first network device may come from another network device (e.g., an application function network element) or may be determined by the second network device or the third network device. In other words, the first network device may receive the second information from the third network device, where the second information indicates the first duration. The first network device may receive the second information from the second network device, where the second information indicates the first duration.

[0248] Referring to FIG6(c), the associated time period corresponding to a packet of the first QoS flow is determined by taking the first duration as the length of the associated time period, starting from the start position of the associated time period corresponding to the packet received. For example, packet 11 corresponds to associated time period 1, packet 12 corresponds to associated time period 2, packet 13 corresponds to associated time period 3, and packet 14 corresponds to associated time period 4. It should be noted that, to better illustrate the above solution in conjunction with FIG5, the associated time periods in FIG6(b) are not aligned on the horizontal axis; however, the lengths of the associated time periods (i.e., the first duration) are consistent.

[0249] Continuing to refer to (c) in Figure 6, the data packet 21 of the second QoS flow is located in the associated time period 2, and the associated time period 2 corresponds to the data packet 12. Therefore, the data packet 21 is associated with the data packet 12; the data packet 22 of the second QoS flow is located in the associated time period 4, and the associated time period 4 corresponds to the data packet 14. Therefore, the data packet 22 is associated with the data packet 14.

[0250] If a synchronization data packet is within the associated time period of multiple reference data packets, the synchronization data packet may use any one of the multiple reference data packets as a synchronization reference, or the synchronization data packet may use the data packet that is first received by the first network device among the multiple reference data packets as a synchronization reference.

[0251] As an example, the first network device may start a timer with a first duration based on the reception time of the data packet 12. Before the timer expires, the data packets received on the second QoS flow are data packets associated with the data packet 12.

[0252] Based on the above solution, the first network device can determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the time when the first network device receives the data packets on the reference stream, the first duration, and the time when the first network device receives the data packets on the synchronization stream. The above solution enables the first network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams, thereby enhancing the user experience.

[0253] Optionally, in other implementation scenarios of the above embodiments, the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow is determined based on the moment when the first network device receives the data packet of the first QoS flow, the first duration and the moment when the first network device receives the data packet of the second QoS flow, including: when the first network device receives the second data packet within the first duration from the time when the first network device receives the first data packet, determining that the second data packet is associated with the first data packet.

[0254] That is, the first network device may directly use the first duration received by the first network device as the associated time window to determine the associated data packet.

[0255] Based on the above scheme, the first network device can determine that the data packets received within the first time period after receiving the reference data packet are synchronization data packets, which enables the first network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0256] Optionally, in some other implementation scenarios of the above embodiments, the first duration is related to first jitter information and / or second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0257] That is, the second network device or the third network device can determine the first duration based on the first jitter information and / or the second jitter information. The second network device or the third network device determines the first duration based on the first jitter information and / or the second jitter information similarly to the embodiment in which the first network device determines the second duration based on the first duration. The embodiment in which the first network device determines the second duration based on the first duration is described below and is not repeated here.

[0258] The first jitter information can reflect the jitter of the N6 data packet corresponding to the data packet of the first QoS flow. The second jitter information can reflect the jitter of the N6 data packet corresponding to the data packet of the second QoS flow. However, the present application is not limited to this. For example, the jitter information can also reflect the jitter of the N3 data packet corresponding to the data packet of a QoS flow. Jitter information can be understood as delay information. The jitter information of the N6 data packet can be determined by the second network device. The second network device can send the jitter information of the N6 data packet to other network devices. The other network devices receive the jitter information of the N6 data packet and determine the first duration based on the jitter information of the N6 data packet.

[0259] The jitter information may be a numerical value, for example, 1 ms (millisecond); the jitter information may also be a numerical range, for example, 1-5 ms.

[0260] Based on the above scheme, the first duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0261] Optionally, in other implementation scenarios of the above embodiments, the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow is determined based on the moment when the first network device receives the data packet of the first QoS flow, the first duration and the moment when the first network device receives the data packet of the second QoS flow, including: determining the second duration based on the first jitter information and / or the second jitter information, and the first duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; and determining that the second data packet is associated with the first data packet when the first network device receives the second data packet within the second duration from the time when the first network device receives the first data packet.

[0262] That is, after receiving the second information indicating the first duration, the first network device may determine the second duration according to the first jitter information and / or the second jitter information and the first duration.

[0263] As mentioned above, jitter information can also reflect the jitter of N6 packets corresponding to a QoS flow, the jitter of N3 packets, and the jitter of packets on other interfaces. Jitter information can be understood as delay information.

[0264] The above solution can be understood as follows: the first network device determines the final association time window (corresponding to the second duration) based on the original association time window (corresponding to the first duration) and jitter information indicated by the core network device. In other words, the first network device can adjust the length of the association time window based on the jitter information. For example, if the duration of the association time window (corresponding to the first duration) is 10ms and the jitter information is plus or minus 1ms, the adjusted length of the association time window (corresponding to the second duration) is 11-9ms.

[0265] The jitter information may indicate jitter of the data packet. A positive jitter indicates that the data packet arrives at the target device (e.g., the first network device, the second network device, or another device) later, while a negative jitter indicates that the data packet arrives at the target device earlier.

[0266] By integrating the jitter information of at least one data stream among the multiple data streams, an adjusted correlation time window (corresponding to the second duration) can be determined. In some embodiments, the duration of the adjusted correlation time window can be calculated by the following formula: Second duration = first duration - jitter of the reference stream

[0267] For example, if the first QoS flow is the reference flow and the jitter of the data packets on the first QoS flow is 1, the second duration can be set to the first duration minus 1. If the reference flow arrives at the destination device earlier than the theoretical arrival time, the jitter of the reference flow is positive, and the second duration is smaller than the first duration. If the reference flow arrives at the destination device later than the theoretical arrival time, the jitter of the reference flow is negative, and the second duration is larger than the first duration.

[0268] In some other embodiments, the adjusted duration of the correlation time window can be calculated by the following formula: Second duration = first duration + jitter of the synchronization data stream

[0269] For example, if the second QoS flow is a synchronous flow and the jitter of the data packets on the second QoS flow is jitter 2, the second duration can be set to the first duration plus jitter 1. If the synchronous flow arrives at the destination device earlier than the theoretical arrival time, the jitter of the synchronous flow is positive, and the second duration is longer than the first duration. If the synchronous flow arrives at the destination device later than the theoretical arrival time, the jitter of the synchronous flow is negative, and the second duration is shorter than the first duration.

[0270] In some other embodiments, the duration of the adjusted correlation time window can be calculated by the following formula: Second duration = first duration - jitter of the reference data stream + jitter of the synchronization data stream

[0271] This calculation method can be a combination of the first two calculation methods. For examples, please refer to the first two embodiments, which will not be described here.

[0272] Based on the above solution, the first network device takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the second duration to obtain the first duration. In the event of jitter in the received data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0273] The second network device or the third network device determines the first duration according to the first jitter information and / or the second jitter information in a similar manner to the above embodiment in which the first network device determines the second duration according to the first duration, and thus will not be described in detail.

[0274] Optionally, in other implementation scenarios of the above embodiments, the method 300 also includes: the third network device sends second information to the first network device, and the second information is used to indicate a first duration, wherein the first duration is used by the first network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0275] The third network device may directly send the second information to the first network device, or may send the second information to another network device, and the other network device may send the second information to the first network device.

[0276] Based on the above solution, the third network device can indicate the first duration to the first network device via the second information, allowing the first network device to determine the association between the data packets on the reference stream and the data packets on the synchronization stream based on the first duration. This solution enables the first network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between the data streams and thereby enhancing the user experience.

[0277] Optionally, in other implementation scenarios of the above embodiments, the method 300 also includes: the third network device receives third information from the application function network element, and the third information is used to indicate the fifth duration; the third network device determines the first duration based on the first jitter information and / or the second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0278] The embodiment in which the third network device determines the third duration based on the first jitter information and / or the second jitter information and the fifth duration is similar to the embodiment in which the first network device determines the second duration based on the first duration. The difference is that in this embodiment, the first duration is replaced by the fifth duration, the second duration is replaced by the third duration, and the device for determining the adjusted association time window is replaced by the third network device instead of the first network device. For details, refer to the above embodiment and are not repeated here.

[0279] Based on the above solution, the third network device can take into account the jitter of the first QoS flow and / or the jitter of the second QoS flow based on the fifth duration indicated by the application function network element to obtain the first duration. In the event of a delay in receiving data packets, the solution provided by the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0280] Optionally, in some other implementation scenarios of the above embodiment, the method 300 further includes: the third network device receives fourth information from the second network device, where the fourth information is used to indicate the first jitter information and / or the second jitter information.

[0281] Based on the above solution, the third network device can obtain the first jitter information and / or the second jitter information from the second network device, thereby taking into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the fifth duration indicated by the application function network element to obtain the first duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0282] Optionally, in other implementation scenarios of the above embodiment, the first QoS flow and the second QoS flow are respectively used to transmit at least two data flows of different modes of the target service.

[0283] The modality of the first QoS flow is different from the modality of the second QoS flow. For example, if the first QoS flow is an auditory flow, the second QoS flow can be a visual flow or a tactile flow. However, this application does not limit the specific modalities of the first QoS flow and the second QoS flow.

[0284] Based on the above solution, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modalities, thereby improving user experience.

[0285] It should be noted that, in other embodiments, the first QoS flow and the second QoS flow can be used to transmit data flows of the same mode of the target service.

[0286] An embodiment of the method 500 is described in detail below with reference to FIG. 5 .

[0287] Referring to Figure 5, based on method 500, the second network device can send second information to the first network device, so that the first network device can determine the association between the data packets of the first QoS flow and the data packets of the second QoS flow based on the second information, thereby enabling the first network device to identify the reference data packets and synchronization data packets that need to be synchronized, thereby realizing synchronization between multiple data streams.

[0288] Optionally, in other implementation scenarios of the above embodiments, the method 500 also includes: the second network device receives indication information from the third network device, and the indication information is used to trigger the second network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow; wherein, S510 includes: determining the second information based on the indication information.

[0289] Correspondingly, the method 300 further includes: the third network device sending indication information to the second network device.

[0290] For example, the third network device may send the indication information to the second network device via an N4 session establishment message or an N4 session modification message. This application does not limit the specific message carried by the indication information, and the third network device may send the indication information to the second network device via other messages. For example, the indication information may be carried in a request message, a configuration message, or other message.

[0291] It is understandable that the indication information can trigger the second network device to determine the association relationship between the data packets of multiple QoS flows. This application does not limit the name of the indication information, for example, the name of the indication information can also be request information, configuration information or other names.

[0292] In some embodiments, the indication information is further used to instruct the second network device to send the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow to the first network device. In other words, the indication information can be used to trigger the second network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow and send the association relationship to the first network device.

[0293] Based on the above solution, after receiving the indication information, the second network device can identify the association between the data packets of the baseline stream and the data packets of the synchronization stream. Therefore, the first network device can identify the baseline data packets and synchronization data packets that need to be synchronized through the second information determined and sent by the second network device. The above solution further improves the synchronization effect between data streams, thereby improving the user experience. In addition, based on the above solution, the third network device can send indication information to the second network device, so that the second network device can identify the association between the data packets of the baseline stream and the data packets of the synchronization stream. The above solution further improves the synchronization effect between data streams, thereby improving the user experience.

[0294] Optionally, in other implementation scenarios of the above embodiments, the method 500 further includes: receiving a target identifier from an application function network element, wherein the target identifier is used to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0295] Exemplarily, the target identifier may be similar to the aforementioned first identifier. When at least one data packet of the second QoS flow from the application function network element corresponds to the target identifier, the second network device may determine that the at least one data packet is associated with the first data packet.

[0296] Exemplarily, the target identifier can be similar to the aforementioned second identifier. After the second network device receives the first data packet from the application function network element, at least one data packet of the second QoS flow from the application function network element received by the second network device is associated with the first data packet.

[0297] Based on the above solution, the second network device can determine the association between the data packets of the reference stream and the data packets of the synchronization stream based on the target identifier, where synchronization is required between the associated data packets. Therefore, the above solution enables the second network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization effect between the data streams and thus enhancing the user experience.

[0298] Optionally, in some other implementation scenarios of the above embodiments, receiving a target identifier from an application function network element includes: receiving a first data packet and a second data packet from the application function network element, wherein the first data packet corresponds to the target identifier and the second data packet corresponds to the target identifier; when the target identifier corresponding to the second data packet is the same as the target identifier corresponding to the first data packet, determining that the first data packet and the second data packet are associated.

[0299] The specific embodiment is similar to the aforementioned embodiment related to the first identifier, for example, see (a) in FIG6 . The difference is that the first identifier in (a) in FIG6 is replaced by the target identifier (not shown in FIG6 ), and the horizontal axis in (a) in FIG6 represents the reception time of the data packet received by the third network device.

[0300] Based on the above solution, the second network device can determine that data packets carrying the same identifier are associated with each other, where synchronization is required between the associated data packets. Therefore, the above solution enables the second network device to identify the reference data packets and synchronization data packets that require synchronization, further improving the synchronization effect between data streams and thus enhancing the user experience.

[0301] Optionally, in some other implementation scenarios of the above embodiments, the target identifier is also used to indicate at least one data packet of the synchronization reference of the data packet of the second QoS flow, wherein receiving the target identifier from the application function network element includes: receiving a first data packet, the first data packet corresponding to the target identifier, and after the second network device receives the first data packet, when the second network device receives a second data packet, determining that the second data packet is associated with the first data packet.

[0302] The specific embodiment is similar to the aforementioned embodiment related to the second identifier, for example, see (b) in FIG6 . The difference is that the second identifier in (b) in FIG6 is replaced by the target identifier (not shown in FIG6 ), and the horizontal axis in (b) in FIG6 represents the reception time of the data packet received by the third network device.

[0303] Based on the above solution, the target identifier can indicate that the first data packet serves as a reference data packet for the synchronization stream, and the second network device can determine that data packets of the synchronization stream received after the reference data packet are associated with the reference data packet. The above solution enables the first network device to identify the reference data packet and the synchronization data packet that need to be synchronized, further improving the synchronization effect between data streams, thereby enhancing the user experience.

[0304] Optionally, in some other implementation scenarios of the above embodiments, the indication information is also used to indicate a third duration, wherein the method 500 also includes: the second network device determines the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow based on the moment when the second network device receives the data packets of the first QoS flow, the third duration and the moment when the second network device receives the data packets of the second QoS flow.

[0305] That is, the third duration is used by the second network device to determine the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

[0306] The specific embodiment is similar to the aforementioned embodiment related to the first duration, for example, see (c) in FIG6 . The difference is that the first duration in (c) in FIG6 is replaced by a third duration (not shown in FIG6 ), and the horizontal axis in (c) in FIG6 represents the reception time of the data packet received by the third network device.

[0307] Based on the above scheme, the second network device can determine the association relationship between the data packets on the reference stream and the data packets on the synchronization stream according to the time when the second network device receives the data packets on the reference stream, the third duration and the time when the data packets on the synchronization stream are received. The above scheme enables the second network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between the data streams, thereby improving the user experience. Moreover, based on the above scheme, the third network device can also indicate the third duration to the second network device through indication information, so that the second network device can determine the association relationship between the data packets on the reference stream and the data packets on the synchronization stream according to the third duration. The above scheme enables the second network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between the data streams, thereby improving the user experience.

[0308] Optionally, in other implementation scenarios of the above embodiments, the method 300 also includes: the third network device receives third information from the application function network element, and the third information is used to indicate a fifth duration; the third network device determines the third duration based on the first jitter information and / or the second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0309] The embodiment in which the third network device determines the first duration based on the first jitter information and / or the second jitter information and the fifth duration is similar to the embodiment in which the first network device determines the second duration based on the first duration. The difference is that in this embodiment, the first duration in the aforementioned embodiment is replaced with the fifth duration, the second duration in the aforementioned embodiment is replaced with the first duration, and the device for determining the adjusted association time window is replaced by the third network device instead of the first network device. For details, refer to the aforementioned embodiment and are not further described here.

[0310] It should be noted that the third duration is indicated by the indication information. The indication information can trigger the process of the second network device identifying the associated data packets of multiple QoS flows and can also indicate the third duration. The first duration is indicated by the second information. The second information is different from the indication information. The second information may not trigger the process of the second network device identifying the associated data packets of multiple QoS flows. In other words, the process of triggering the second network device to identify the associated data packets of multiple QoS flows and the associated time window can be coupled or decoupled. The first duration and the third duration can be the same or different.

[0311] Based on the above scheme, the third duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0312] Optionally, in some other implementation scenarios of the above embodiment, the method 300 further includes: the third network device receives fourth information from the second network device, where the fourth information is used to indicate the first jitter information and / or the second jitter information.

[0313] Based on the above solution, the third network device can obtain the first jitter information and / or the second jitter information from the second network device, thereby taking into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the fifth duration indicated by the application function network element to obtain the first duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0314] Optionally, in other implementation scenarios of the above embodiments, the second network device determines the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow based on the moment when the second network device receives the data packets of the first QoS flow, the third time duration and the moment when the second network device receives the data packets of the second QoS flow, including: within the third time duration from the time when the second network device receives the first data packet, if the second network device receives the second data packet, the second network device determines that the second data packet is associated with the first data packet.

[0315] That is, the second network device may directly use the third duration as the correlation time window to determine the associated data packet.

[0316] Based on the above scheme, the second network device can determine that the data packets received within the third time period after receiving the reference data packet are synchronization data packets, which enables the second network device to identify the reference data packets and synchronization data packets that need to be synchronized, further improving the synchronization effect between data streams, thereby improving the user experience.

[0317] Optionally, in some other implementation scenarios of the above embodiments, the third duration is related to the first jitter information and / or the second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

[0318] That is, the third network device may determine the third duration according to the first jitter information and / or the second jitter information. Specific embodiments are described later in the embodiment of the third network device, which will not be described in detail here.

[0319] Jitter information reflects the jitter of packets corresponding to a QoS flow. Jitter information can be understood as delay information. For other meanings of jitter information, see the description of jitter information above and will not be repeated here.

[0320] Based on the above scheme, the third duration takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow. In the case of a delay in receiving data packets, the scheme provided in the embodiment of the present application can still accurately identify the reference data packets and synchronization data packets that need to be synchronized, thereby improving the applicability of the data transmission method.

[0321] Optionally, in other implementation scenarios of the above embodiments, the second network device determines the association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow based on the moment when the second network device receives the data packet of the first QoS flow, the third time duration and the moment when the second network device receives the data packet of the second QoS flow, including: the second network device determines a fourth time duration based on the first jitter information and / or the second jitter information, and the third time duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; within the fourth time duration from the second network device receiving the first data packet, if the second network device receives the second data packet, the second network device determines that the second data packet is associated with the first data packet.

[0322] That is to say, after receiving the indication information indicating the third duration, the second network device can determine the fourth duration based on the first jitter information and / or the second jitter information and the third duration. This scheme is similar to the above-mentioned embodiment in which the first network device determines the second duration based on the first jitter information and / or the second jitter information and the first duration, except that, in this scheme, the third duration is replaced by the first duration, and the second duration is replaced by the fourth duration, and the device for determining the adjusted associated time window is replaced by the second network device by the first network device. For details, please refer to the above embodiment, which will not be repeated here.

[0323] Based on the above solution, the second network device takes into account the jitter of the first QoS flow and / or the jitter of the second QoS flow on the basis of the third duration to obtain a fourth duration. In the event of a delay in receiving a data packet, the solution provided by the embodiment of the present application can still accurately identify the reference data packet and the synchronization data packet that need to be synchronized, thereby improving the applicability of the data transmission method.

[0324] Optionally, in some other implementation scenarios of the above embodiments, the method 500 also includes: the second network device receives the first data packet from the application function network element; determines the target identifier corresponding to the first data packet, and the target identifier is used to indicate that the first data packet serves as a synchronization reference for the data packet of the second QoS flow; wherein, sending the first data packet to the first network device includes: sending the first data packet to the first network device, and the first data packet corresponds to the second identifier.

[0325] The target identifier and the second identifier may be carried in the header information corresponding to the first data packet. For example, the first header information may be the header information of an N6 data packet, the first header information may include the target identifier, and the first header information may be the header information of the first data packet encapsulated by the application function network element. The second header information may be the header information of an N3 data packet, the second header information may include the second identifier, and the second header information may be the header information of the first data packet encapsulated by the second network device. The first data packet may be understood as the payload portion of an N6 data packet or an N3 data packet.

[0326] The target identifier and the second identifier may not be in the packet header information corresponding to the first data packet. For example, the target identifier and the second identifier may be parameters independent of the first data packet.

[0327] It should be noted that, in the above solution, the second network device may not determine the association relationship between the first data packet and the data packet of the second QoS flow. The above solution can be understood as follows: after the second network device receives the first data packet from the application function network element, if the second network device identifies or parses the first data packet corresponding to the identifier for indicating that the first data packet is a synchronization reference for the data packet of the second QoS flow, then the second network device may correspond the identifier indicating that the first data packet is a synchronization reference for the data packet of the second QoS flow to the first data packet during the process of sending the first data packet.

[0328] The second identifier may be the same as or different from the target identifier.

[0329] Based on the above solution, the target identifier can indicate that the first data packet serves as a reference data packet for the data packets on the synchronization stream. Upon recognizing that the first data packet corresponds to the target identifier, the second network device can cause the first data packet sent to the first network device to correspond to the second identifier. Therefore, the above solution enables the first network device to identify the reference and synchronization data packets that require synchronization, further improving the synchronization between data streams and thereby enhancing the user experience. Furthermore, in the above solution, the second network device does not need to identify the reference and synchronization data packets, thereby improving data transmission efficiency.

[0330] Optionally, in other implementation scenarios of the above embodiment, the first QoS flow and the second QoS flow are respectively used to transmit at least two data flows of different modes of the target service.

[0331] Based on the above solution, the data transmission method provided in the embodiment of the present application can improve the synchronization effect of data streams of multiple modalities, thereby improving user experience.

[0332] FIG7 is a schematic flowchart of another data transmission method 700 provided in an embodiment of the present application.

[0333] 7 , the data transmission method 700 involves the interaction between multiple core network elements and access network devices. FIG7 is merely exemplary and does not constitute a limitation of the present application. The method 700 is described below in conjunction with FIG7 .

[0334] S710: The AF sends the service requirements of multiple SDFs to the PCF, wherein the service requirements include the transmission requirements corresponding to each SDF and the synchronous delay budget (SyncDB) between the multiple SDFs.

[0335] Taking the above multiple SDFs as two SDFs as an example, the modes of the two SDFs SDF1 and SDF2 can be different. For example, SDF1 corresponds to the first QoS flow in the above method 300, and SDF2 corresponds to the second QoS flow in the above method 300.

[0336] Service requirements can be unidirectional. For example, the service requirement for SDF1 can be expressed as {SDF1: PSDB1}. The service requirement for SDF2 can be expressed as {SDF2: PSDB2, SyncDB->SDF1, associated time window->SDF1}. These unidirectional requirements can be understood as requiring SDF1 to receive and send data normally without requiring synchronization, while SDF2 must consider how to synchronize with SDF1.

[0337] Business requirements can also be bidirectional. For example, the business requirements of SDF1 can be expressed as {SDF1: PSDB1, SyncDB->SDF2, associated time window->SDF2}. The business requirements of SDF2 can be expressed as {SDF2: PSDB2, SyncDB->SDF1, associated time window->SDF1}. These bidirectional requirements can be understood as SDF1 needing to consider how to synchronize with SDF2, and SDF2 also needing to consider how to synchronize with SDF1. Alternatively, SDF2 needs to synchronize with SDF1 based on SDF1, and SDF1 also needs to synchronize with SDF2 based on SDF2. In other words, SDF1 and SDF2 both need to synchronize with each other.

[0338] The above service requirements may not include an associated time window. For example, the service requirement of SDF1 can be expressed as {SDF1: PSDB1}. The service requirement of SDF2 can be expressed as {SDF2: PSDB2, SyncDB->SDF1}. For another example, the service requirement of SDF1 can be expressed as {SDF1: PSDB1, SyncDB->SDF2}. The service requirement of SDF2 can be expressed as {SDF2: PSDB2, SyncDB->SDF1}.

[0339] It should be noted that, in addition to being provided by the AF, the above-mentioned association time window can also be determined by the UPF itself. Alternatively, the association time window can also be provided by other network elements (e.g., NWDAF). For example, after the other network element determines the association time window, the other network element can send information indicating the association time window to the SMF, and the SMF sends the information indicating the association time window to the access network device.

[0340] The PSDB can also be replaced by packet delay budget (PDB). PDB and PSDB have similar meanings, but the difference is that PSDB targets PDU sets, while PDB targets packets.

[0341] The value of SyncDB can be the aforementioned preset duration. SyncDB is the estimated delay for synchronizing an SDF with a reference SDF. For example, if packet 11 in the reference SDF arrives at the access network device at time t0, packet 21 in the SDF associated with packet 11 should be sent within the SyncDB from time t0.

[0342] The value of the association time window can be the aforementioned first, second, third, fourth, or fifth duration. For example, based on the association time window, packets requiring synchronization can be determined on other SDFs associated with the reference SDF relative to the reference SDF. Taking "Association Time Window -> SDF1" as an example, with SDF1 as the reference SDF, packet 11 on SDF1 arrives at the access network device at time t0, or the access network device sends packet 11 at time t0. Assuming the association time window is Δt, then packets on SDF2 within Δt starting at time t0, i.e., within t0+Δt, are associated with packet 11 (or require synchronization).

[0343] In some embodiments, S710 may include: the AF sends service requirements of multiple SDFs to a network exposure function (NEF), and the NEF sends the service requirements of the multiple SDFs to the PCF.

[0344] The NEF is located between the 5G core network and external third-party application functions (in some embodiments, the NEF also includes part of the AF), and is responsible for managing network data open to the outside world. The AF can send information directly to the PCF or send information to the PCF through the NEF. The NEF can provide corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, providing functions such as the opening of external application QoS customization capabilities, mobility status event subscription, and AF request distribution.

[0345] S720: The PCF generates a policy and charging control (PCC) rule based on the service requirements and sends the PCC rule to the SMF. The PCC rule includes the SDF description information and the SDF service requirements, that is, the service requirements provided by the AF in S710.

[0346] S730, SMF sends indication information to UPF, where the indication information is used to determine associated data packets on an associated QoS flow.

[0347] For example, the SMF may send indication information to the UPF via an N4 session establishment message or an N4 session modification message.

[0348] In this way, the UPF can send the above indication information (ie, the indication information in S730) to the access network device via a GTP-U message. Specific processes can be found in S760 and S770 below, which will not be described here in detail.

[0349] S740: The SMF determines the synchronization requirement between multiple QoS flows according to the PCC rule, and sends the synchronization requirement to the access network device.

[0350] For example, SMF can establish QoS flow 1 (corresponding to SDF1) and QoS flow 2 (corresponding to SDF2) according to PCC rule, determine the synchronization requirement between QoS flow 1 and QoS flow 2, and then send the synchronization requirement to the access network device.

[0351] For example, the SMF sends an N2 SM message to the access network device. The QoS profile of the N2 SM message includes a synchronization requirement, which includes the QoS flow identifier associated with a QoS flow and the SyncDB. Taking a unidirectional requirement as an example, the synchronization requirement can be configured on the reference flow or on the synchronized flow, for example:

[0352] QoS Profile 1 {5QI, PSDB, SyncDB->QFI2} QoS Profile 2 {5QI, PSDB}, or,

[0353] QoS Profile 1 {5QI, PSDB} QoS Profile 2 {5QI, PSDB, SyncDB <- QFI1}

[0354] The 5G QoS identifier (5QI) is a standardized scalar whose value corresponds one-to-one with some 5G QoS features. The QoS flow identifier (QFI) is the identifier of the QoS flow. The QFI can be generated by the SMF and can be the same as or different from the 5QI.

[0355] QoS profile 1 can be understood as the QoS profile corresponding to QoS flow 1 (QoS flow with QFI of 1), and QoS profile 2 can be understood as the QoS profile corresponding to QoS flow 2 (QoS flow with QFI of 2).

[0356] The first information may include a preset duration, for example, the first information may be the aforementioned SyncDB. The first information may also be used to indicate an association between multiple QoS flows, for example, the first information may be the aforementioned SyncDB->QFI2 or SyncDB<-QFI1. The first information may also be configuration information for a QoS flow, for example, the first information may be the aforementioned QoS profile 1 or profile 2.

[0357] In addition, the N2 SM message sent by the SMF to the access network device may also include another indication information, which is used to instruct the RAN to synchronize QoS flow 1 and QoS flow 2 based on at least two associated data packets, where the at least two associated data packets are data packets associated with QoS flow 1 and QoS flow 2, respectively. In other words, this other indication information is used to instruct the RAN to synchronize multiple QoS flows based on the granularity of associated data packets. In this way, the access network device can obtain information about data packets associated with different QoS flows by parsing the GTP-U message from the UPF. Alternatively, the access network device can identify data packets associated with different QoS flows based on the associated time window.

[0358] The aforementioned another indication information may be the first information. In other words, the first information may have the function of the aforementioned another indication information.

[0359] It should be noted that the SMF can send the N2 SM message to the access network device through the AMF. For example, the SMF sends the Namf_Communication_N1N2MessageTansfer containing the N2 SM message to the AMF, and the AMF sends the N2 SM message to the access network device through the N2 PDU Session Request message. The AMF does not parse the N2 SM message and only performs transparent transmission.

[0360] S750: After receiving the downlink data, the UPF determines the associated data packets on the associated QoS flow.

[0361] For example, after receiving data packet 21 on QoS flow2, UPF can determine which of the multiple data packets (data packet 11, data packet 12 and data packet 13) received on QoS flow1 that are associated with data packet 21 is associated with data packet 21.

[0362] There are many specific ways to do this, which are introduced below.

[0363] For example, see the embodiment related to (a) in Figure 6 . This embodiment is similar to the previous embodiment, except that the data packet here is an N6 data packet, so the first identifier can be carried in the N6 packet header. Furthermore, the execution entity here is the UPF, not the access network device. Furthermore, if this approach is adopted, there is no need to provide an associated time window in S710.

[0364] For another example, see the embodiment related to (c) in Figure 6 . This embodiment is similar to the previous embodiment, except that the data packet here is an N6 data packet, so the second identifier can be carried in the N6 packet header. Furthermore, the execution entity here is the UPF, not the access network device. Furthermore, if this approach is adopted, there is no need to provide an associated time window in S710.

[0365] For another example, please refer to the embodiment related to (c) in Figure 6, which is similar to the solution of the previous embodiment, except that the execution entity here is UPF, not the access network device.

[0366] S760: UPF provides the access network device with the association relationship between the data packets with synchronization requirements on different QoS flows through GTP-U.

[0367] For example, you can refer to the embodiments related to (a), (b) or (c) in Figure 6. The scheme here is similar to the aforementioned embodiment, except that the execution entity here is the UPF in the core network device.

[0368] S770: After receiving the data packet, the access network device determines the transmission delay of the data packet with synchronization requirements based on the reception time of the reference data packet, the reception time of the synchronization data packet, the synchronization requirements in the QoS configuration information, and the PDB / PSDB of the synchronization data packet. In other words, the access network device performs the corresponding steps of the aforementioned method embodiment.

[0369] Based on the above solution, the preset duration can be sent by the SMF to the access network device, which can then determine the synchronization requirements between packets requiring synchronization on different data streams. The association time window can be sent by the SMF to the UPF, which can then determine the packets requiring synchronization on different data streams based on the association time window.

[0370] The present application also provides a data transmission method, comprising: an application function network element sending a synchronization requirement between a first service flow and a second service flow to a policy control network element; the policy control network element generating a synchronization policy based on the synchronization requirement; the policy control network element sending the synchronization policy to a session management network element; the session management network element generating a synchronization configuration based on the synchronization policy; and the session management network element sending the synchronization configuration to an access network device. In other words, the application function network element configures the synchronization requirement between the first service flow and the second service flow on the access network device.

[0371] In some embodiments, the application function network element initiates data transmission of the first business flow and the second business flow to the terminal device. The first business flow and the second business flow pass through the user plane function network element and the access network device and reach the terminal device. The first business flow and the second business flow meet the synchronization requirement.

[0372] In some embodiments, the application function network element initiates data transmission of a first data packet and a second data packet to a terminal device. The first data packet and the second data packet pass through the user plane function network element and the access network device and reach the terminal device. The first data packet and the second data packet meet the synchronization requirement, wherein the first data packet is associated with the second data packet, the first data packet is transmitted through a first service flow, and the second data packet is transmitted through a second service flow.

[0373] In some embodiments, the application function network element receives a first service request message or a first service subscription message from a terminal device, and the first service request corresponds to a first service or a first application. The first service or the first application corresponds to at least two service flows, including the above-mentioned first service flow and the second service flow, that is, the execution of the first service or the first application requires the application function network element to transmit at least two service flows. The first service request message or the first service subscription message also carries a first identifier, and the first identifier is used to indicate the first service or the first application, wherein the first service or the first application corresponds to a first provider. Exemplarily, the service includes but is not limited to games, virtual reality (VR), augmented reality (AR), extended reality (XR) and other services, and the corresponding service flows include but are not limited to multimodal service flows such as auditory service flows, visual service flows, and tactile service flows, and the provider is the provider of the service.

[0374] In some embodiments, the application function network element sends the synchronization requirement between the first service flow and the second service flow to the policy control network element in response to the first service request message or the first service subscription message.

[0375] In some embodiments, the application function network element spontaneously sends the synchronization requirement between the first service flow and the second service flow to the policy control network element.

[0376] The present application also provides a data transmission method, including: receiving a first message from a first terminal device through a first interface, wherein the first message corresponds to a first service or a first application; determining a first synchronization strategy and at least two service flows corresponding to the first service or the first application based on the first message; completing the synchronization configuration according to the first synchronization strategy and sending the at least two service flows to the first terminal device or other terminal devices.

[0377] Exemplarily, the first message may be a first service request message or a first service subscription message; the at least two service flows sent to the first terminal device or other terminal devices meet the synchronization requirements of the first service or the first application.

[0378] In some embodiments, an application function network element receives the first message and, based on the first service or first application corresponding to the first message, determines at least two service flows and synchronization requirement information corresponding to the first service or first application. The application function network element also sends the at least two service flows and synchronization requirement information corresponding to the first service or first application to a policy control network element. The policy control network element generates synchronization policy information based on the synchronization requirement information and sends it to the session management network element. The session management network element generates synchronization configuration information based on the received information and sends it to the access network device. The access network device completes configuration based on the synchronization configuration information, synchronizes the at least two received service flows, and then sends them to the terminal via the second interface.

[0379] In some embodiments, the synchronization configuration information generated by the session management network element is used to indicate synchronization between two associated data packets on the at least two service flows. The two data packets are transmitted by the at least two service flows respectively, not by the same service flow.

[0380] In some embodiments, the application function network element, the policy control network element, the image management network element and the access network device are configured to implement the solutions in the aforementioned embodiments.

[0381] In some embodiments, the first synchronization strategy is determined based on synchronization requirement information, which may be a specific value, a value range, a delay threshold, or a qualitative description (such as "low", "medium", etc.).

[0382] Optionally, in some embodiments, the synchronization information may be preconfigured.

[0383] Optionally, in some embodiments, the first message further carries a first requirement, where the requirement includes a delay requirement, which can also be understood as a synchronization requirement, and is used to indicate synchronization information between data streams of corresponding services.

[0384] In some embodiments, the application function network element further receives data corresponding to the at least two aforementioned service flows. The data may be received through the first interface or through a preset second interface.

[0385] In some embodiments, the application function network element sends pre-stored data to the policy control network element.

[0386] The following is an introduction to the device embodiment corresponding to the method embodiment of the present application. The following is only a brief introduction to the device, and the specific implementation steps and details of the solution can be referred to the method embodiment above.

[0387] To implement the various functions of the methods provided herein, both terminal devices and network devices may include hardware structures and / or software modules, with the aforementioned functions implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0388] Figure 8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. Communication device 800 includes a processor 810 and a communication interface 820, which may be interconnected via a bus 830. Communication device 800 may be a first network device, a second network device, or a third network device.

[0389] Optionally, the communication device 800 may further include a memory 840. The memory 840 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). The memory 840 is used for related instructions and data. The memory 840 may be integrated with the processor 810 or provided separately.

[0390] The processor 810 may be one or more central processing units (CPUs). In the case where the processor 810 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 810 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuitry used for processing functions in the aforementioned processor, chip, or integrated circuit. In addition, the communication interface 820 may also be an input / output interface, which is used for inputting or outputting signals or data, or may be an input / output circuit.

[0391] When the communication device 800 is a first network device, exemplarily, the processor 810 is used to perform the following operations: receive first information, the first information being used to indicate a preset duration, the preset duration corresponding to the synchronization delay information between the first QoS flow and the second QoS flow; send a first data packet, the first data packet being transmitted through the first QoS flow, and the moment when the first data packet is sent by the first network device is the first moment; send the second data packet according to the first moment and the preset duration, wherein the second data packet is transmitted through the second QoS flow, and wherein the second data packet is associated with the first data packet.

[0392] When the communication apparatus 800 is a second network device, illustratively, the processor 810 is configured to perform the following operations: obtain second information, the second information being used to indicate an association relationship between data packets of the first QoS flow and data packets of the second QoS flow; and send the second information to the first network device.

[0393] When the communication device 800 is a third network device, exemplarily, the processor 810 is used to perform the following operations: obtain first information, wherein the first information is used to indicate a preset duration, which corresponds to the synchronization delay information between the first QoS flow and the second QoS flow; and send the first information to the first network device.

[0394] When the communication device 800 is the first network device, the second network device or the third network device, it will be responsible for executing the methods or steps related to the first network device, the second network device or the third network device in the above method embodiments.

[0395] It is understood that when the communication device 800 is a first network device, a second network device, or a third network device, the communication interface 820 may also be referred to as a transceiver. The transceiver may include a transmitter and a receiver, where the transmitter is configured to perform a transmission operation and the receiver is configured to perform a reception operation. For example, the processor 810 is configured to control the transceiver to receive and / or transmit signals.

[0396] It should be noted that the communication device 800 may include a transmitter but not a receiver. Alternatively, the communication device 800 may include a receiver but not a transmitter. The specific implementation depends on whether the above solution executed by the communication device 800 includes a sending action and a receiving action.

[0397] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG8 may also correspond to the corresponding description of the method embodiments shown in FIG3 to FIG7.

[0398] For example, the communication device 800 may be used to implement the solution shown in FIG. 3 or FIG. 5 .

[0399] When the communication device 800 is a first network device: the communication interface 820 is used to receive first information, which is used to indicate a preset duration, and the preset duration corresponds to the synchronization delay information between the first quality of service QoS flow and the second QoS flow; the communication interface 820 is also used to send a first data packet, which is transmitted through the first QoS flow, and the moment when the first data packet is sent by the first network device is the first moment; the communication interface 820 is also used to send the second data packet according to the first moment and the preset duration, wherein the second data packet is transmitted through the second QoS flow, and wherein the second data packet is associated with the first data packet.

[0400] When the communication apparatus 800 is a second network device, the processor 810 is configured to obtain second information indicating an association relationship between data packets of the first QoS flow and data packets of the second QoS flow; and the communication interface 820 is configured to send the second information to the first network device.

[0401] When the communication device 800 is a second network device: the processor 810 is used to obtain first information, wherein the first information is used to indicate a preset duration, which corresponds to the synchronization delay information between the first QoS flow and the second QoS flow; the communication interface 820 is used to send the first information to the first network device.

[0402] For other implementations, please refer to the detailed description of the embodiment shown in Figure 3 or Figure 5 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0403] Figure 9 is a schematic block diagram of another communication device 900 according to an embodiment of the present application. Communication device 900 may be a first network device, a second network device, or a third network device, or may be a chip or module within the first network device, the second network device, or the third network device, and is configured to implement the methods described in the embodiments of Figures 3 to 8. For details, please refer to the relevant descriptions in the aforementioned method embodiments.

[0404] The communication device 900 includes a transceiver unit 910. The transceiver unit 910 is described below by way of example.

[0405] The transceiver unit 910 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the embodiments of the present application combine the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later. The transceiver unit 910 can implement corresponding communication functions. The transceiver unit 910 can also be referred to as a communication interface or communication module.

[0406] It should be noted that the communication device 900 may include a sending unit but not a receiving unit. Alternatively, the communication device 900 may include a receiving unit but not a sending unit. The specific implementation depends on whether the above solution executed by the communication device 900 includes a sending action and a receiving action.

[0407] When the communication device 900 is a first network device, illustratively, the transceiver unit 910 is used to receive first information and the like.

[0408] Optionally, the communication apparatus 900 may further include a processing unit 920 configured to execute steps such as processing and coordination of the first network device.

[0409] When the communication device 900 is a second network device, illustratively, the transceiver unit 910 is configured to send second information, etc. to the first network device.

[0410] Optionally, the communication apparatus 900 may further include a processing unit 920 configured to execute steps such as processing and coordination of the second network device.

[0411] When the communication device 900 is a third network device, illustratively, the transceiver unit 910 is configured to send first information, etc. to the first network device.

[0412] Optionally, the communication apparatus 900 may further include a processing unit 920 configured to execute the content of steps involving processing, coordination, etc. of the third network device.

[0413] When the communication device 900 is the first network device, the second network device or the third network device, it will be responsible for executing the methods or steps related to the first network device, the second network device or the third network device in the above method embodiments.

[0414] Optionally, the communication device 900 further includes a storage unit 930, which is configured to store a program or code for executing the aforementioned method. Alternatively, the storage unit 930 may be configured to store instructions and / or data, and the processing unit 920 may read the instructions and / or data in the storage unit 930 to enable the communication device 900 to implement the aforementioned method embodiment. For example, the communication device 900 may be configured to execute the solution shown in FIG. 3 .

[0415] When the communication device 900 is a first network device: the transceiver unit 910 is used to receive first information, where the first information is used to indicate a preset duration, and the preset duration corresponds to the synchronization delay information between the first QoS flow and the second QoS flow; the transceiver unit 910 is also used to send a first data packet, which is transmitted through the first QoS flow, and the moment when the first data packet is sent by the first network device is the first moment; the transceiver unit 910 is also used to send the second data packet according to the first moment and the preset duration, wherein the second data packet is transmitted through the second QoS flow, and wherein the second data packet is associated with the first data packet.

[0416] When the communication device 900 is a second network device: the processing unit 920 is used to obtain second information, which is used to indicate the association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow; the transceiver unit 910 is used to send the second information to the first network device.

[0417] When the communication device 900 is a third network device: the processing unit 920 is used to obtain first information, wherein the first information is used to indicate a preset duration, which corresponds to the synchronization delay information between the first QoS flow and the second QoS flow; the transceiver unit 910 is used to send the first information to the first network device.

[0418] For other implementations, please refer to the detailed description of the embodiment shown in Figure 3 or Figure 5 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0419] The device embodiments shown in Figures 8 and 9 are used to implement the contents described in Figures 3 to 8. The specific execution steps and methods of the devices shown in Figures 8 and 9 can refer to the contents described in the above method embodiments.

[0420] The present application further provides an apparatus 1000, which may be a first network device, a processor in the first network device, or a chip. The apparatus 1000 may be used to execute the operations performed by the first network device in the above method embodiment.

[0421] When apparatus 1000 is a first network device, FIG10 shows a simplified schematic diagram of the structure of the first network device. As shown in FIG10 , the first network device includes a processor, a memory, and a transceiver. The memory can store computer program code, and the transceiver includes a transmitter 1031, a receiver 1032, a radio frequency circuit (not shown), and an antenna 1033.

[0422] The processor is mainly used to process the communication protocol and communication data; control the first network device, execute the software program and process the data of the software program, etc.

[0423] Memory is mainly used to store software programs and data.

[0424] Radio frequency circuits are mainly used for conversion between baseband signals and radio frequency signals and for processing radio frequency signals.

[0425] Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.

[0426] When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal to the outside in the form of electromagnetic waves via the antenna. When data is sent to the first network device, the RF circuit receives the RF signal via the antenna. The RF circuit converts the RF signal into a baseband signal and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of illustration, Figure 10 shows only one memory, processor, and transceiver. In an actual first network device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be set independently of the processor or integrated with the processor, and this embodiment of the application does not limit this.

[0427] Sections 1010 and 1020 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control device 1000. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an alternative embodiment, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0428] In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver functions may be regarded as the transceiver module of the first network device, and the processor with processing function may be regarded as the processing module of the first network device.

[0429] As shown in Figure 10, the first network device includes a processor 1010, a memory 1020, and a transceiver 1030. The processor 1010 may also be referred to as a processing unit, a processing board, a processing module, or a processing device. The transceiver 1030 may also be referred to as a transceiver unit, a transceiver, or a transceiver device.

[0430] Optionally, the device in transceiver 1030 that implements the receiving function is considered a receiving module, and the device in transceiver 1030 that implements the transmitting function is considered a transmitting module. That is, transceiver 1030 includes a receiver and a transmitter. A transceiver may also be sometimes referred to as a transceiver, a transceiver module, or a transceiver circuit. A receiver may also be sometimes referred to as a receiver, a receiving module, or a receiving circuit. A transmitter may also be sometimes referred to as a transmitter, a transmitting module, or a transmitting circuit.

[0431] The processor 1010 is configured to execute the processing actions on the first network device side in the embodiment shown in Fig. 3. The transceiver 1030 is configured to execute the transceiver actions on the first network device side in the embodiment shown in Fig. 3.

[0432] When the apparatus 1000 is a chip, the chip includes a processor, a memory, and a transceiver. The transceiver may be an input / output circuit or a communication interface. The processor may be a processing module, a microprocessor, or an integrated circuit integrated on the chip. In the above method embodiment, the sending operation of the first network device may be understood as an output of the chip, and the receiving operation of the first network device in the above method embodiment may be understood as an input of the chip.

[0433] The present application further provides an apparatus 1100, which may be a second network device or a chip of the second network device. The apparatus 1100 may be used to perform the operations performed by the second network device in the embodiments shown in FIG. 3 to FIG. 7 .

[0434] Figure 11 shows a simplified structural diagram. Apparatus 1100 includes part 1110, part 1120 and part 1130.

[0435] Part 1110 is mainly used for baseband processing, etc.; Part 1110 is usually the control center of device 1100, which can usually be called a processor, used to control device 1100 to perform processing operations on the second network device side or the third network device side in the above method embodiment.

[0436] Part 1120 is mainly used to store computer program code and data.

[0437] Part 1130 is primarily used for receiving and transmitting RF signals and converting RF signals to baseband signals. Part 1130 can generally be referred to as a transceiver module, transceiver, transceiver circuit, or transceiver. The transceiver module in part 1130, which can also be referred to as a transceiver or transceiver, includes an antenna 1133 and a RF circuit (not shown in the figure), where the RF circuit is primarily used for RF processing. Optionally, the device used to implement the receiving function in part 1130 can be considered a receiver, and the device used to implement the transmitting function can be considered a transmitter, that is, part 1130 includes a receiver 1132 and a transmitter 1131. A receiver can also be referred to as a receiving module, a receiver, or a receiving circuit, and a transmitter can be referred to as a transmitting module, a transmitter, or a transmitting circuit.

[0438] Sections 1110 and 1120 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control device 1000. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an alternative embodiment, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0439] For example, in one implementation, the transceiver module in section 1130 is used to execute the transceiver-related processes performed by the second network device or the third network device in the embodiment shown in FIG3 or FIG5. The processor in section 1110 is used to execute the processing-related processes performed by the second network device or the third network device in the embodiment shown in FIG3 or FIG5.

[0440] When apparatus 1100 is a chip, the chip includes a transceiver, a memory, and a processor. The transceiver may be an input / output circuit or a communication interface; the processor may be a processor, microprocessor, or integrated circuit integrated on the chip. In the above method embodiments, the sending operation of the second or third network device can be understood as an output of the chip, and the receiving operation of the second or third network device in the above method embodiments can be understood as an input of the chip.

[0441] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0442] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0443] The present application also provides a processor, which is coupled to a memory and is used to execute the method and function involving the first network device, the second network device or the third network device in any of the above embodiments.

[0444] In another embodiment of the present application, a computer program product including a computer program or instructions is provided. When the computer program product is run on a computer, the method of the aforementioned embodiment is implemented.

[0445] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.

[0446] In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0447] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software 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 beyond the scope of this application.

[0448] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0449] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. 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. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0451] 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.

[0452] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0453] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data transmission method, applied to a first network device, characterized in that: include: Receiving first information, where the first information is used to indicate synchronization delay information between a first quality of service QoS flow and a second QoS flow; Sending a first data packet at a first moment, wherein the first data packet is transmitted through the first QoS flow; A second data packet is sent according to the first moment and the synchronization delay information, wherein the second data packet is transmitted through the second QoS flow, and wherein the second data packet is associated with the first data packet.

2. The method according to claim 1, characterized in that The method further comprises: Second information is received, where the second information is used to determine an association relationship between data packets of the first QoS flow and data packets of the second QoS flow.

3. The method according to claim 2, characterized in that The first data packet corresponds to the second information, and the second data packet corresponds to the second information, wherein the method further includes: When the second information corresponding to the first data packet is the same as the second information corresponding to the second data packet, it is determined that the second data packet is associated with the first data packet.

4. The method according to claim 2, characterized in that: The first data packet corresponds to the second information, wherein the method further comprises: The first data packet is received from a second network device, and the second information is further used to indicate that the first data packet is a synchronization reference of a data packet of the second QoS flow.

5. The method according to claim 4, characterized in that The method further comprises: After the first network device receives the first data packet, in a case where the first network device receives the second data packet from a second network device, it is determined that the second data packet is associated with the first data packet.

6. The method according to claim 4 or 5, characterized in that: The second network device is a user plane functional network element.

7. The method according to claim 2, characterized in that The second information further indicates a first duration, wherein the method further includes: Determine the association between the data packets of the first QoS flow and the data packets of the second QoS flow based on the time when the first network device receives the data packets of the first QoS flow, the first duration, and the time when the first network device receives the data packets of the second QoS flow.

8. The method according to claim 7, characterized in that The first duration is determined according to first jitter information and / or second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

9. The method according to claim 7, characterized in that: The determining, according to the time when the first network device receives the data packet of the first QoS flow, the first duration, and the time when the first network device receives the data packet of the second QoS flow, the association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow includes: Determine a second duration according to first jitter information and / or second jitter information, and the first duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; If the first network device receives the second data packet within the second time period after the first network device receives the first data packet, it is determined that the second data packet is associated with the first data packet.

10. The method according to any one of claims 1 to 9, characterized in that The synchronization delay information between the first QoS flow and the second QoS flow corresponds to a preset duration, wherein sending the second data packet according to the first moment and the synchronization delay information includes: The second data packet is sent within the preset time period from the first moment.

11. The method according to any one of claims 1 to 10, characterized in that The first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

12. The method according to any one of claims 1 to 11, characterized in that The first information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow.

13. The method according to any one of claims 1 to 12, characterized in that The first information is also used to instruct the first network device to perform synchronization between the first QoS flow and the second QoS flow according to at least two associated data packets, and the at least two associated data packets are data packets with an associated relationship on the first QoS flow and the second QoS flow respectively.

14. A data transmission method, applied to a second network device, characterized in that: include: Acquire second information, where the second information is used to indicate an association relationship between a data packet of the first quality of service QoS flow and a data packet of the second QoS flow; The second information is sent to the first network device.

15. The method according to claim 14, characterized in that The first data packet corresponds to the second information, and the second data packet corresponds to the second information, wherein sending the second information to the first network device includes: The first data packet and the second data packet are sent to the first network device, wherein the first data packet is transmitted through the first QoS flow, and the second data packet is transmitted through the second QoS flow.

16. The method according to claim 14, characterized in that The second information is further used to indicate at least one data packet of a synchronization reference of the data packets of the second QoS flow, wherein the sending the second information to the first network device includes: A first data packet is sent to the first network device, wherein the first data packet corresponds to the second information.

17. The method according to any one of claims 14 to 16, characterized in that The method further comprises: Receiving indication information from a third network device, where the indication information is used to trigger determination of an association relationship between a data packet of the first QoS flow and a data packet of the second QoS flow; wherein obtaining the second information includes: The second information is determined according to an association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

18. The method according to claim 17, characterized in that The method further comprises: A target identifier is received from an application function network element, wherein the target identifier is used to determine an association relationship between a data packet of the first QoS flow and a data packet of the second QoS flow.

19. The method according to claim 18, characterized in that The method further comprises: receiving a first data packet and a second data packet from the application function network element, wherein the first data packet corresponds to the target identifier, and the second data packet corresponds to the target identifier; When the target identifier corresponding to the second data packet is the same as the target identifier corresponding to the first data packet, it is determined that the first data packet is associated with the second data packet.

20. The method according to claim 18 or 19, characterized in that The target identifier is also used to indicate at least one data packet of a synchronization reference of the data packet of the second QoS flow, wherein the receiving the target identifier from the application function network element includes: receiving a first data packet, wherein the first data packet corresponds to the target identifier; After the second network device receives the first data packet, in the case where the second network device receives a second data packet, it is determined that the second data packet is associated with the first data packet.

21. The method according to claim 17, characterized in that The indication information is further used to indicate a third duration, wherein the method further includes: Determine the association between the data packets of the first QoS flow and the data packets of the second QoS flow based on the time when the second network device receives the data packets of the first QoS flow, the third duration and the time when the second network device receives the data packets of the second QoS flow.

22. The method according to claim 21, characterized in that The determining, according to the time when the second network device receives the data packet of the first QoS flow, the third duration, and the time when the second network device receives the data packet of the second QoS flow, an association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow comprises: If the second network device receives a second data packet within the third time period after the second network device receives the first data packet, it is determined that the second data packet is associated with the first data packet.

23. The method according to claim 22, characterized in that The third duration is determined according to first jitter information and / or second jitter information, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

24. The method according to claim 21, characterized in that The determining, according to the time when the second network device receives the data packet of the first QoS flow, the third duration, and the time when the second network device receives the data packet of the second QoS flow, an association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow comprises: A fourth duration is determined based on the first jitter information and / or the second jitter information, and the third duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow; within the fourth duration from the time when the second network device receives the first data packet, if the second network device receives the second data packet, it is determined that the second data packet is associated with the first data packet.

25. The method according to claim 16, characterized in that The method further comprises: Receiving the first data packet from the application function network element; Determine a target identifier corresponding to the first data packet, where the target identifier is used to indicate that the first data packet is a synchronization reference for a data packet of the second QoS flow; wherein sending the first data packet to the first network device includes: The first data packet is sent to the first network device, where the first data packet corresponds to the second information.

26. The method according to any one of claims 14 to 25, characterized in that The first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

27. A data transmission method, applied to a third network device, characterized in that: include: Acquire first information, wherein the first information is used to indicate synchronization delay information between the first quality of service QoS flow and the second QoS flow; The first information is sent to a first network device.

28. The method according to claim 27, characterized in that The indication information is used to trigger the second network device to determine an association relationship between the data packet of the first QoS flow and the data packet of the second QoS flow, wherein the method further includes: Send the indication information to the second network device.

29. The method according to claim 28, characterized in that The indication information is further used to indicate a third duration, and the third duration is used to determine an association relationship between the data packets of the first QoS flow and the data packets of the second QoS flow.

30. The method according to claim 29, characterized in that The method further comprises: receiving third information from the application function network element, where the third information is used to indicate a fifth duration; The third duration is determined according to first jitter information and / or second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

31. The method according to claim 27 or 28, characterized in that The second information is used to indicate a first duration, wherein the first duration is used to determine an association relationship between a data packet of the first QoS flow and a data packet of the second QoS flow, wherein the method further includes: The second information is sent to the first network device.

32. The method according to claim 31, characterized in that The method further comprises: receiving third information from the application function network element, where the third information is used to indicate a fifth duration; The first duration is determined according to first jitter information and / or second jitter information, and the fifth duration, wherein the first jitter information is related to the first QoS flow, and the second jitter information is related to the second QoS flow.

33. The method according to claim 30 or 32, characterized in that The method further comprises: Fourth information is received from a second network device, where the fourth information is used to indicate the first jitter information and / or the second jitter information.

34. The method according to any one of claims 27 to 33, characterized in that The first QoS flow and the second QoS flow are used to transmit at least two of data flows of different modes of the target service.

35. The method according to any one of claims 27 to 34, characterized in that The first information is carried in the configuration information of the first QoS flow and / or the configuration information of the second QoS flow.

36. The method according to any one of claims 27 to 35, characterized in that The first information is also used to instruct the first network device to perform synchronization between the first QoS flow and the second QoS flow according to at least two associated data packets, and the at least two associated data packets are data packets with an associated relationship on the first QoS flow and the second QoS flow respectively.

37. A communication device, characterized in that: It comprises a processing circuit and an input-output interface, wherein the input-output interface is used to input and / or output signals, and the processing circuit is used to execute the method described in any one of claims 1 to 13, or the processing circuit is used to execute the method described in any one of claims 14 to 26, or the processing circuit is used to execute the method described in any one of claims 27 to 36.

38. A communication device, characterized in that: The method comprises at least one module, wherein the at least one module is used to execute the method as claimed in any one of claims 1 to 13, or the at least one module is used to execute the method as claimed in any one of claims 14 to 26, or the at least one module is used to execute the method as claimed in any one of claims 27 to 36.

39. A communication system, characterized in that: The method comprises a first network device, a second network device and a third network device, wherein the first network device is used to execute the method as claimed in any one of claims 1 to 13, the second network device is used to execute the method as claimed in any one of claims 14 to 26, and the third network device is used to execute the method as claimed in any one of claims 27 to 36.

40. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions, and when the computer program or the instructions are executed on a computer, the method described in any one of claims 1 to 13 is executed, or the method described in any one of claims 14 to 26 is executed, or the method described in any one of claims 27 to 36 is executed.

41. A computer program product, characterized in that Comprising computer program code, when the computer program code is executed, implementing the method according to any one of claims 1 to 13, or implementing the method according to any one of claims 14 to 26, or implementing the method according to any one of claims 27 to 36.

Images