Data transmission method, an apparatus, computer-readable medium, and electronic device

Abstract

Embodiments of the present application provide a data transmission method, an apparatus, a computer-readable medium, and an electronic device. The data transmission method comprises: identifying a synchronization relationship between a plurality of quality of service (QoS) flows; if it is identified that the plurality of QoS flows have a synchronization relationship, acquiring a synchronization parameter between the plurality of QoS flows; and if it is determined, on the basis of network transmission quality, that packet loss processing needs to be performed, discarding a target data packet in the plurality of QoS flows on the basis of the synchronization parameter. In the technical solution of the embodiments of the present application, a synchronization parameter can be introduced to make a packet loss decision for a plurality of QoS flows, ensuring that synchronization between different QoS flows and overall QoS can still be maintained during network congestion.

Description

Data transmission methods, apparatus, computer-readable media and electronic devices

[0001] This application claims priority to Chinese Patent Application No. 202411865694.5, filed on December 16, 2024, entitled "Data Transmission Method, Apparatus, Computer-Readable Medium and Electronic Device". Technical Field

[0002] This application relates to the fields of computer and communication technology, and more specifically, to a data transmission method, apparatus, computer-readable medium, and electronic device. Background Technology

[0003] In 5th-generation mobile communication technology (5G) and its subsequent evolution systems (such as 5G-A (5G-Advanced), 6G, etc.), high-bandwidth interactive services are important service types, such as cloud gaming, virtual reality (VR), augmented reality (AR), mixed reality (MR), extended reality (XR), cinematic reality (CR), XR and media services (XRM). These high-bandwidth interactive services not only have high requirements for transmission timeliness, but also typically contain multiple media types, such as audio, video, haptic, or other media types. During transmission, different media type service flows may be mapped to different Quality of Service (QoS) flows.

[0004] However, while supporting a large number of users for various immersive media services, the wireless transmission portion of the network is prone to congestion. In such cases, packet loss processing may be necessary to resolve network congestion. Related technologies typically use packet loss processing based on packet importance; however, this approach may lead to data asynchrony issues for different media types when dealing with multiple correlated QoS streams. Summary of the Invention

[0005] Embodiments of this application provide a data transmission method, apparatus, computer-readable medium, and electronic device that can introduce synchronization parameters to make packet loss decisions for multiple QoS flows, ensuring that synchronization and overall service quality between different QoS flows can be maintained even under network congestion.

[0006] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part by practice of this application.

[0007] In a first aspect, embodiments of this application provide a data transmission method, comprising: identifying a synchronization relationship between multiple QoS flows; if a synchronization relationship is identified between the multiple QoS flows, obtaining synchronization parameters between the multiple QoS flows; if it is determined that packet loss processing is required based on network transmission quality, discarding target data packets in the multiple QoS flows according to the synchronization parameters.

[0008] Secondly, embodiments of this application provide a data transmission apparatus, including: an identification unit configured to identify a synchronization relationship between multiple QoS flows; an acquisition unit configured to acquire synchronization parameters between the multiple QoS flows if a synchronization relationship is identified between them; and a processing unit configured to discard target data packets in the multiple QoS flows according to the synchronization parameters if packet loss processing is required based on network transmission quality.

[0009] Thirdly, embodiments of this application provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the data transmission method as described in the above embodiments.

[0010] Fourthly, embodiments of this application provide an electronic device, including: one or more processors; and a storage device for storing one or more computer programs, wherein when the one or more computer programs are executed by the one or more processors, the electronic device enables the data transmission method as described in the above embodiments.

[0011] Fifthly, embodiments of this application provide a computer program product comprising a computer program stored in a computer-readable storage medium. A processor of an electronic device reads from and executes the computer program from the computer-readable storage medium, causing the electronic device to perform the data transmission methods provided in the various embodiments described above.

[0012] In some embodiments of this application, when a synchronization relationship is identified between multiple QoS flows, a synchronization parameter between these multiple QoS flows is obtained. When it is determined that packet loss processing is required based on network transmission quality, the target data packets in multiple QoS flows are discarded according to the synchronization parameter. This allows the introduction of a synchronization parameter to make packet loss decisions for multiple QoS flows, realizing a more intelligent packet loss mechanism between multiple QoS flows with a synchronization relationship. In this way, the synchronization between different QoS flows and the overall service quality can be maintained even under network congestion.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0014] Figure 1 illustrates a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of this application can be applied;

[0015] Figure 2 illustrates a schematic diagram of the transmission process of multimedia data packets according to various embodiments of this application;

[0016] Figure 3 illustrates a schematic diagram of data transmission via multiple QoS streams according to various embodiments of this application;

[0017] Figure 4 illustrates a flowchart of a data transmission method according to various embodiments of this application;

[0018] Figure 5 illustrates a flowchart of a data transmission method according to various embodiments of this application;

[0019] Figure 6 illustrates a flowchart of a data transmission method according to various embodiments of this application;

[0020] Figure 7 shows a block diagram of a data transmission apparatus according to various embodiments of the present application;

[0021] Figure 8 shows a schematic diagram of the structure of a computer system suitable for implementing various embodiments of the present application. Detailed Implementation

[0022] Example implementations will now be described in a more comprehensive manner with reference to the accompanying drawings. However, the example implementations can be implemented in various forms and should not be construed as being limited to these examples.

[0023] Furthermore, the features, structures, or characteristics described in this application can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to provide a full understanding of the embodiments of this application. However, those skilled in the art will recognize that when implementing the technical solutions of this application, not all the detailed features in the embodiments may be used, one or more specific details may be omitted, or other methods, elements, devices, steps, etc., may be employed.

[0024] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. For example, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0026] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0027] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0028] With the development of 5G and its subsequent evolution systems (such as 5G-A, 6G, etc.), many multimedia services requiring high data volumes and low latency have been applied. These include cloud gaming, VR, AR, MR, XR, CR, and other interactive services.

[0029] For example, in the cloud gaming scenario shown in Figure 1, cloud server 101 is used to run cloud games. Cloud server 101 can render game screens, encode audio signals and rendered images, and finally transmit the encoded data obtained through the encoding process to various game clients via the network. The game client can be a user equipment (UE) with basic streaming media playback capabilities, human-computer interaction capabilities, and communication capabilities, such as smartphones, tablets, laptops, desktop computers, smart TVs, smart home devices, in-vehicle terminals, aircraft, etc.; or the game client can be an application running on a terminal device. For example, the game client can decode the encoded data transmitted by cloud server 101 to obtain analog audio and video signals, and then play them.

[0030] It should be understood that Figure 1 is merely an exemplary representation of the system architecture of a cloud gaming system and does not limit the specific architecture of the cloud gaming system; for example, in other embodiments, the cloud gaming system may also include a backend server for scheduling, etc. Furthermore, the cloud server 101 can be an independent physical server, a server cluster composed of multiple physical servers, or a distributed system. It can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The game client and the cloud server 101 can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0031] In the various multimedia-based interactive service application scenarios mentioned above, multimedia data packets are enormous. For example, even a single multimedia service frame or a Group of Packets (GoP) can be quite large in bytes. Therefore, they need to be split into multiple data packets for transmission. Specifically, as shown in Figure 2, taking a 5G system as an example, the user plane mainly includes the application server, User Plane Function (UPF), next generation nodeB (gNB), and UE. Multimedia data packet transmission in some typical service scenarios is mainly in the downlink direction, such as from the application server (AS) to the UPF, and then sent to the UE via the gNB. During transmission, the multimedia data packets (taking XR data packets I and P as examples in Figure 2) are split at the application layer of the application server. The split sub-data packets (sub-data packets I1, I2… and sub-data packets P1, P2…) arrive at the UPF as IP packets from the application server. The 5G system then transmits the sub-data packets to the UE through Protocol Data Unit (PDU) sessions. At the UE end, sub-data packets are submitted level by level upwards through the protocol stack and reassembled to recover the multimedia data packet. The protocol stack at the UE end, from bottom to top, includes the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and IP layer.

[0032] In the system shown in Figure 2, Layer L1 refers to the Physical Layer, which ensures that raw data can be transmitted over various physical media. Layer L2 refers to the Data Link Layer, which provides services to the Network Layer based on the services provided by the Physical Layer. The Internet Protocol (IP) layer is the Network Layer, used to implement data transmission between two end systems. UDP stands for User Datagram Protocol. GTP-U stands for GPRS (General Packet Radio Service) Tunneling Protocol. PHY stands for Physical, the Physical Layer. MAC stands for Media Access Control. RLC stands for Radio Link Control, the Radio Link Control layer protocol. PDCP stands for Packet Data Convergence Protocol. SDAP stands for Service Data Adaptation Protocol.

[0033] As mentioned earlier, for multimedia services (such as XRM services), it is common to transmit a single multimedia data frame through multiple data packets. The data formed by a single multimedia service frame or a Group of Packets (GoP) can also be quite large in bytes, and can be carried by a series of IP packets. These IP packets have a certain correlation, and processing them according to this correlation can effectively save wireless network bandwidth. For example, assuming that multiple IP packets are used for transmission, these multiple IP packets can form a PDU set.

[0034] Multimedia services (such as XRM services) typically include multiple media types in their service flows, such as audio, video, haptic, or other media types. As shown in Figure 3, during transmission, to ensure quality of service, different media type service flows between the user equipment and the application server may be mapped to different Quality of Service (QoS) flows. Different QoS flows may have different transmission latencies; for example, the transmission latencies between the Radio Access Network (RAN) and the UPF may differ. This can lead to asynchrony between different media type service data when the receiving end (e.g., the user equipment) generates and plays media content based on the received multiple media type service flows.

[0035] Meanwhile, while supporting a large number of users for various immersive media services, the wireless transmission portion of the network is prone to congestion. This not only affects the user experience but may also lead to the ineffective processing of redundant data generated during media encoding and decoding. Related technologies typically handle packet loss based on the importance of data packets when network congestion occurs. However, this approach may encounter asynchrony issues for different media types when dealing with multiple related QoS streams.

[0036] For example, in scenarios where audio and video streams are transmitted using different QoS streams, assuming the audio and video streams need to be synchronized, and the data packets in the audio stream are more important than those in the video stream, then in the event of network congestion, related technologies would prioritize dropping data packets from the video stream. In this case, if the latency of the audio stream is greater (e.g., greater than that of the video stream), then even if data packets from the video stream are dropped to ensure the continued transmission of data packets from the audio stream, it will not benefit the synchronization of the audio and video streams. In other words, the packet loss handling schemes proposed in related technologies based on importance lack consideration for the synchronization between different QoS streams. Therefore, when network congestion occurs, this packet loss handling mechanism may not be able to effectively maintain the synchronization between multimodal data streams, thus affecting the end-user experience.

[0037] Based on the above problems, the technical solution of this application proposes a new data transmission scheme, which can introduce synchronization parameters to make packet loss decisions for multiple QoS streams. This realizes a more intelligent packet loss mechanism between multiple QoS streams with synchronization relationships, thereby maintaining the synchronization and overall service quality between different QoS streams even under network congestion. This solves the problem in related technologies where packet loss processing is based solely on packet importance, which may lead to asynchrony of service data for different media types.

[0038] The implementation details of the technical solutions in the embodiments of this application are described in detail below:

[0039] Figure 4 illustrates a flowchart of a data transmission method according to various embodiments of this application. This data transmission method can be executed by an access network element, such as a base station device. Of course, the technical solution of the embodiment shown in Figure 4 can also be executed by other electronic devices with computing processing capabilities, such as a user equipment or a UPF. Referring to Figure 4, the data transmission method includes steps S410 to S420, which are described in detail below:

[0040] In S410, the synchronization relationship between multiple QoS flows is identified.

[0041] In some embodiments, multiple QoS streams can be derived by mapping data streams of different media types from a multimedia service. Media types may include audio, video, haptic, or other media types. Service data packets of different media types may have different or the same QoS requirements. If service data packets of different media types have different QoS requirements, then these different media type service data packets can be mapped to different QoS streams.

[0042] Multimedia services can include cloud gaming, VR, AR, MR, XR, XRM, and CR services. Data packets for multimedia services can be transmitted using a set of Program Data Units (PDUs). This is because if a single multimedia service frame or GoP forms a data packet, its size may be quite large; therefore, it needs to be split into a series of data packets for transmission. These series of data packets have a certain correlation, hence the term "PDU set." In other embodiments of this application, the service data stream can also be transmitted per-packet.

[0043] Taking cloud gaming as an example, cloud gaming services may include audio data packets, video data packets, and haptic or other types of data packets. Since these multi-media data packets are associated with the same multimedia service, if they are mapped to different QoS streams during transmission, these QoS streams will be related. For example, there may be synchronization requirements between these QoS streams, meaning that the latency between these QoS streams should be consistent or within a certain latency range.

[0044] In some embodiments, the synchronization relationship between multiple QoS flows can be identified by receiving indication information sent by core network elements and then using this indication information. For example, the indication information can be used to identify whether multiple QoS flows within the same PDU session are synchronized, or to identify whether QoS flows within different PDU sessions are synchronized. This method involves explicit identification.

[0045] For example, the indication information sent by the core network element may be a multi-modality service ID (MMSID), which is used to indicate that multiple QoS flows within the same PDU session have a synchronization relationship.

[0046] In some embodiments, the synchronization relationship between multiple QoS flows can also be identified implicitly. For example, the synchronization relationship between multiple QoS flows can be identified based on the PDU session and the user equipment context information (UE context).

[0047] Specifically, in the UE Context, QoS is typically associated with a specific session (such as the Bearer in EPS or the QoS flow in 5GS). These QoS parameters may include: priority, used to determine the transmission order of data packets; rate limits, such as Maximum Bit Rate (MBR) and Guaranteed Bit Rate (GBR), used to control the speed of data transmission; packet filter sets, used to associate data packets in the network with specific QoS rules; and QoS rule identifiers (such as 5QI, ARP, etc.), used to uniquely identify QoS rules. When identifying whether there is a synchronization relationship between QoS flows through the session level contained in the UE Context, QoS parameters associated with a specific session can be looked up in the UE Context, and then the synchronization relationship between multiple QoS flows can be identified based on these parameters. In various embodiments of this application, "parameter" can refer to a measurable attribute (the parameter itself), a parameter value, or both.

[0048] In some embodiments, when identifying whether there is a synchronization relationship between multiple QoS flows in an implicit manner, the synchronization relationship between multiple QoS flows can be identified based on the QoS parameters at the QoS flow level.

[0049] Specifically, QoS flows represent the finest QoS differentiation granularity within a PDU session. Each QoS flow is configured and managed based on a series of QoS parameters. These parameters not only define the characteristics of the QoS flow but also indirectly reflect the correlation between QoS flows. QoS flow-level QoS parameters may include QoS Flow Identifier (QFI), QoS Class Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), and Maximum Flow Bit Rate (MFBR), among others.

[0050] QFI is used to identify QoS flows. 5QI is used to index a 5G QoS feature; different 5QI values ​​represent different QoS categories, and QoS flows with the same 5QI value may have similar QoS processing. ARP parameters define the priority, preemption capability, and preemptibility of a QoS flow; QoS flows with the same ARP parameters may be subject to the same processing strategy during resource allocation. For GBR QoS flows, GFBR and MFBR represent the guaranteed bit rate and maximum bit rate, respectively; QoS flows with similar GFBR and MFBR values ​​may be correlated in terms of rate guarantees. Therefore, QoS parameters at the QoS flow level can be used to identify whether multiple QoS flows have a synchronization relationship. For example, QFI can be used to identify whether different QoS flows have the same ARP parameters or the same delay parameters. If they have the same or similar delay parameters (e.g., the delay parameter value is less than a preset threshold), then it indicates that different QoS flows are synchronized.

[0051] For example, in addition to the QoS parameters mentioned above, for service data packets transmitted via PDU sets, the corresponding QoS parameters may also include at least one of the following: PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), Maximum Data Burst Volume (MDBV), and Packet Delay Variation (PDV). For service data packets transmitted per-packet, the corresponding QoS parameters may also include at least one of the following: Packet Delay Budget (PDB), Packet Error Rate (PER), and Maximum Data Burst Volume.

[0052] In some embodiments, when identifying whether multiple QoS flows have a synchronization relationship implicitly, multiple QoS flows contained in the same PDU session can be identified as having a synchronization relationship if the core network element indicates a synchronization requirement. That is, in this embodiment, multiple QoS flows contained in the same PDU session are identified as QoS flows with a synchronization relationship without the need for other parameters to indicate this.

[0053] In S420, if a synchronization relationship is identified between multiple QoS flows, the synchronization parameters between the multiple QoS flows are obtained.

[0054] In some embodiments, obtaining the synchronization parameter between multiple QoS flows can be a threshold for the synchronization time difference between the multiple QoS flows. This threshold indicates the maximum value of the time synchronization error between the multiple QoS flows. In other words, this synchronization parameter can be used to indicate the conditions under which multiple QoS flows achieve synchronization. For example, if the time synchronization error between two QoS flows exceeds this threshold, it indicates that the two QoS flows have lost synchronization.

[0055] It can receive synchronization parameter indication information sent by core network elements, and obtain the synchronization parameters configured by the core network elements through the indication information.

[0056] The synchronization parameters between multiple QoS streams can also be determined based on their types. For example, the maximum value of the time synchronization error between different types of QoS streams can be preset. When transmitting multiple QoS streams, the maximum value of the time synchronization error can be determined based on the types of these QoS streams. Specifically, if the maximum value of the time synchronization error between an audio stream and a video stream is preset to 20ms, then if an audio stream and a video stream with a synchronization relationship are identified, the synchronization parameter between the audio stream and the video stream can be determined to be 20ms, that is, the maximum value of the time synchronization error between the audio stream and the video stream is 20ms.

[0057] In S430, if it is determined that packet loss processing is required based on network transmission quality, then target data packets from multiple QoS flows are dropped according to synchronization parameters. For example, target data packets from the multiple QoS flows are dropped to satisfy the synchronization requirements determined by the synchronization parameters.

[0058] In some embodiments, if network transmission quality is poor, it can be determined that packet loss processing is necessary. Poor network transmission quality can be determined by setting indicators, such as packet loss rate, latency, jitter, throughput, retransmission rate, signal strength, and signal quality.

[0059] Packet Loss Rate (PLR) refers to the proportion of data packets that fail to reach their destination during network transmission out of the total number of data packets sent. A high packet loss rate is usually an indicator of network congestion or failure. For real-time communication services such as voice calls and video conferencing, even a small amount of packet loss can significantly impact the user experience. Latency refers to the time interval between when data is sent from the sender and when it is received by the receiver. Low latency is crucial for real-time applications. For example, in online games and AR / VR experiences, excessive latency can lead to significant data lag at the receiving end, affecting the interactive experience. Jitter refers to the difference in arrival times between adjacent data packets, i.e., the amount of latency variation. Large jitter can affect the smoothness of audio and video stream playback, causing stuttering, especially in real-time interactive scenarios. Throughput represents the amount of data transmitted through the network per unit of time. When the actual throughput is lower than expected, it may indicate insufficient network bandwidth or other limiting factors, such as channel interference or device performance bottlenecks. Retransmission rate measures the proportion of data packets that need to be retransmitted due to loss or corruption in a network connection. Frequent retransmissions not only increase latency but also waste valuable network resources and reduce overall transmission efficiency. Signal strength can be measured by Reference Signal Received Power (RSRP), and signal quality by Reference Signal Receiving Quality (RSRQ). Weak signal strength or poor signal quality leads to a higher bit error rate and a lower transmission rate.

[0060] In some embodiments, when discarding target data packets from multiple QoS streams based on synchronization parameters, the target QoS stream that does not meet the synchronization requirements with other QoS streams can be identified based on the synchronization requirements determined by the synchronization parameters among these multiple QoS streams. Then, some data packets from the target QoS stream are selected as target data packets for discarding. This embodiment's technical solution allows for the priority discarding of some data packets from QoS streams that do not meet synchronization requirements when network transmission quality is poor. For example, when synchronously transmitting audio and video streams, if the audio stream has a large latency and cannot be synchronized with the video stream, then when network quality is poor, some data packets from the audio stream can be prioritized for discarding. This ensures that data packets from the audio stream that do not meet synchronization requirements are discarded, and instead, data packets from the audio stream that can be synchronized with the video stream are transmitted. This maximizes the time consistency of multimodal data streams and ensures the quality of user experience.

[0061] In some embodiments, if the transmission delay between a target QoS stream and other QoS streams is detected to be greater than or equal to a delay threshold indicated by a synchronization parameter, it can be determined that the target QoS stream does not meet the synchronization requirements with the other QoS streams. For example, this delay threshold is mainly used to indicate the maximum value of the time synchronization error between multiple QoS streams. If the transmission delay between two QoS streams is greater than this delay threshold, it indicates that the time synchronization error between these two QoS streams is also greater than the set maximum value of the time synchronization error. In this case, it can be determined that these two QoS streams no longer meet the synchronization requirements, and the QoS stream with the larger delay can be identified as the target QoS stream.

[0062] In some embodiments, if it is determined that packet loss processing is required based on network transmission quality, but the synchronization requirements determined by the synchronization parameters between multiple QoS flows are satisfied, then some data packets from these multiple QoS flows can be selected as the target data packets and discarded in ascending order of data packet priority. In other words, in the embodiments of this application, if it is determined that packet loss processing is required based on network transmission quality, some data packets from QoS flows that do not meet the synchronization requirements can be discarded first. If all data packets meet the synchronization requirements, then they are discarded in ascending order of data packet priority. For example, when discarding data packets from multiple QoS flows in ascending order of data packet priority, packet loss processing can be performed for each QoS flow in ascending order of data packet priority; or packet loss processing can be performed for a portion of these multiple QoS flows (such as randomly selected QoS flows, lower-priority QoS flows, etc.) in ascending order of data packet priority; or data packets from multiple QoS flows can be grouped together and discarded in ascending order of priority.

[0063] In some embodiments, if network transmission quality is detected to have returned to normal during packet loss processing, packet loss processing for multiple QoS flows can be stopped. For example, network transmission quality returning to normal means that network transmission quality has returned to stability and there are no congestion or other problems, so packet loss processing can be discontinued. This can also be determined using the indicators set in the above embodiments.

[0064] In some embodiments, during packet loss processing, if the proportion of dropped packets in a QoS stream (or a PDU set) reaches a set tolerable packet loss ratio, packet loss processing for that QoS stream (or the PDU set) can be stopped. This tolerable packet loss ratio represents the maximum allowable packet loss ratio, such as the maximum proportion of packets allowed to be dropped while ensuring the data receiver can normally decode other packets in the service data stream. This embodiment ensures that when the proportion of dropped packets in a QoS stream (or a PDU set) reaches the set tolerable packet loss ratio, packets in that QoS stream (or PDU set) are no longer dropped, preventing the data receiver from being unable to recover other packets in that QoS stream (or PDU set) due to excessive packet loss. In other words, the tolerable packet loss ratio can be specific to either the QoS stream or the PDU set.

[0065] In some embodiments, the tolerable packet loss ratio can be determined based on the forward error correction (FEC) configuration parameters of the business data flow. For example, if the business data flow uses forward error correction and can tolerate 10% packet loss, then the tolerable packet loss ratio is 10%.

[0066] In some embodiments, the tolerable packet loss ratio can be determined based on the attribute parameters of the service data stream, such as one or more of the frame rate and resolution of the service data stream. Specifically, if the frame rate or resolution settings of the service data stream allow lost frames to be recovered through interpolation or fitting, then it means that dropping some data packets is tolerable, and the tolerable packet loss ratio can be set accordingly.

[0067] In some embodiments, the tolerable packet loss ratio can also be related to the latency requirements of the business data stream. For example, if the latency requirements of the business data stream are exceeded, then even if the data packets in the business data stream are transmitted to the receiver, they may be of little use. Therefore, a larger tolerable packet loss ratio can be set after the latency of the business data stream exceeds the latency requirements. For example, the latency requirements of the business data stream can be PSDB, PDB, etc.

[0068] In some embodiments, the tolerable packet loss ratio of the business data stream can be determined based on two or all of the forward error correction configuration parameters of the business data stream, the attribute parameters of the business data stream, and the latency requirements of the business data stream.

[0069] Figure 5 illustrates flowcharts of data transmission methods according to various embodiments of this application. This data transmission method can be executed by an access network element, such as a base station device. Of course, the technical solution of the embodiment shown in Figure 5 can also be executed by other electronic devices with computing processing capabilities, such as a user equipment or a UPF. Referring to Figure 5, the data transmission method includes S510 and S540, which are described in detail below:

[0070] In S510, the synchronization relationship between multiple QoS flows is identified.

[0071] For example, the specific implementation details of S510 can be referred to the relevant description of S410 in the aforementioned embodiments, and will not be repeated here.

[0072] In S520, if a synchronization relationship is identified among multiple QoS flows, resource allocation is performed on the multiple QoS flows according to this synchronization relationship, so that the multiple QoS flows meet the synchronization requirements when transmitting based on the allocated transmission resources. The synchronization requirements are preset and / or indicated by synchronization parameters sent by core network elements.

[0073] In some embodiments, when allocating resources to multiple QoS flows based on their synchronization relationships, if transmitting multiple QoS flows over the same Data Radio Bearer (DRB) satisfies the synchronization requirements, then the same DRB can be used to transmit the multiple QoS flows, ensuring that the synchronization requirements are met when the multiple QoS flows are transmitted over the same DRB. If transmitting multiple QoS flows over the same DRB does not satisfy the synchronization requirements, then different DRBs can be allocated to the multiple QoS flows, ensuring that the synchronization requirements are met when the multiple QoS flows are transmitted over different DRBs.

[0074] In S530, after resource allocation processing is performed on multiple QoS streams according to synchronization relationships, delay monitoring is performed on the transmission process of multiple QoS streams.

[0075] Data packets can be transmitted in three modes: Transparent Mode (TM), Acknowledged Mode (AM), and Unacknowledged Mode (UM). In Transparent Mode (TM), the transmitting device or system is "transparent" to the transmitted data; for example, it does not modify or process the data content. In Unacknowledged Mode (UM), data transmission does not require confirmation from the receiver; the sender does not wait for any feedback after sending data. Therefore, data transmission efficiency is relatively high, suitable for scenarios with high real-time requirements but relatively low accuracy requirements. Acknowledged Mode (AM) is a more reliable transmission mode. In AM mode, the sender waits for an acknowledgment message from the receiver after sending data to ensure correct reception. If the receiver does not receive the data or the data is incorrect, it sends a Negative Acknowledgment (NACK) message to the sender, requesting retransmission. This mechanism ensures data integrity and accuracy but also increases transmission latency.

[0076] In some embodiments, if the transmission mode of the multiple QoS streams is unacknowledged, then the RLC instance used to receive the multiple QoS streams performs delay monitoring on the uplink transmission process of the multiple QoS streams, and the RLC instance used to send the multiple QoS streams performs delay monitoring on the downlink transmission process of the multiple QoS streams.

[0077] In some embodiments, if the transmission mode of the multiple QoS streams is acknowledgment mode, then since the RLC instance for receiving the multiple QoS streams and the RLC instance for sending the multiple QoS streams are the same, the transmission process of the multiple QoS streams can be monitored for delay by the RLC instance used to receive the multiple QoS streams and send the multiple QoS streams.

[0078] In some embodiments, when monitoring the delay of the transmission process of multiple QoS streams, the monitoring can be performed either by data packets or by transport blocks (TBs).

[0079] In some embodiments, if the transmission delay between multiple QoS data packets is within a set threshold range, it can be determined that the multiple QoS streams can meet the synchronization requirements during transmission; if the transmission delay between multiple QoS data packets is not within the set threshold range, it can be determined that the multiple QoS streams cannot meet the synchronization requirements during transmission. This embodiment ensures that multiple QoS streams are considered synchronized when their transmission delays are within a certain range, avoiding misjudgments caused by latency jitter.

[0080] In some embodiments, when monitoring the delay of multiple QoS streams during transmission, a state machine can be used to indicate synchronous and asynchronous states. For example, based on the delay monitoring results of multiple QoS streams, different states of the state machine can indicate whether the multiple QoS streams can meet the synchronization requirements during transmission; wherein, the state machine includes synchronous and asynchronous states. Of course, the state machine can also include other states, such as an impending asynchronous state, a slightly asynchronous state, a severely asynchronous state, etc. These states can be set according to the degree of QoS stream delay.

[0081] In S540, if multiple QoS streams are detected to be unable to meet synchronization requirements during transmission, the transmission resource allocation for the multiple QoS streams will be adjusted.

[0082] In some embodiments, if a QoS flow experiences significant latency, more transmission resources or less busy transmission links can be allocated to that QoS flow to reduce its latency. If, after adjusting the transmission resource allocation for multiple QoS flows and allowing a set time interval, the multiple QoS flows still fail to meet synchronization requirements, a notification message can be sent to the core network element to adjust the transmission parameters for the multiple QoS flows. For example, the core network element can adjust the QoS parameters for multiple QoS flows through a PDU session modification procedure, or it can adjust the synchronization parameters between QoS flows.

[0083] The implementation details of the technical solution of this application embodiment will be described in detail below with reference to Figure 6, taking a 5G system as an example:

[0084] The technical solution of this application embodiment can identify the synchronization relationship between QoS flows at the NG-RAN base station. During data transmission, based on the synchronization between QoS flows, redundant data is selected from multiple data flows for discarding, thereby providing a more intelligent packet loss mechanism for multimodal data flows with synchronization requirements, better handling congestion, and improving the ability of subsequent evolution systems such as 5G, 5G-A, and 6G networks to cope with network congestion. Specifically, referring to Figure 6, the steps may include:

[0085] S601, NG-RAN acquires synchronization indication and synchronization parameters.

[0086] In some embodiments, NG-RAN can obtain one or more synchronization indication information between QoS flows from 5GC network elements such as PCF, SMF, AMF, etc. This synchronization indication information may include synchronization indications and synchronization parameters.

[0087] For example, synchronization indicators can be used to indicate multiple QoS flows that are synchronized. Specifically, core network elements can provide the NG-RAN with the synchronization relationship of multiple QoS flows by indicating different QoS flows in the same PDU session, or by explicitly associating multiple QoS flows in different PDU sessions.

[0088] Synchronization parameters are used to represent the synchronization requirements between multiple QoS flows, such as specific synchronization requirement thresholds. A synchronization parameter can be defined as the maximum synchronization time difference between different QoS flows; for example, 20ms means the time synchronization difference between QoS flow 1 and QoS flow 2 does not exceed 20ms.

[0089] After obtaining the synchronization indication and synchronization parameters, NG-RAN can use one or more DRBs for data transmission and monitor the latency of different service flows.

[0090] In some embodiments, in order to ensure synchronization between multiple QoS flows, if multiple data flows can use the same 5QI, or the same PDB metric, or the same PDU metric, as well as the PER metric or MDBV metric, or if NG-RAN determines that the QoS of multiple service flows can be guaranteed even if the same DRB is used, the same DRB can be used for transmission, and the same DRB can achieve the same latency characteristics.

[0091] In some embodiments, different QoS flows may have different characteristics. For example, different QoS flows may include different XRM media streams / types, or different PDU sets, and the importance information (PDU set importance, PSI) of the PDU sets may be different. Or, although the latency is the same, the PER may be different, that is, the reliability indicators between different QoS flows are different. These factors make it impossible to use the same DRB. In the above cases, NG-RAN can use different DRBs to transmit multiple QoS flows.

[0092] In some embodiments, to ensure that different QoS flows meet the same latency requirements, the base station can perform latency monitoring on multiple QoS flows with synchronization requirements. For example, in RLC UM mode, if it is an uplink (UL) transmission, the latency can be monitored by the receive (RX) RLC instance; if it is a downlink (DL) transmission, the latency can be monitored by the transmit (TX) RLC instance.

[0093] For example, in RLC AM mode, if UL and DL share an RLC instance, the trend of sequence number delay changes can be analyzed through this RLC instance to determine whether the delay of multiple QoS flow services can meet the synchronization requirements.

[0094] In some embodiments, if NG-RAN detects that the transmission between multiple QoS flows can meet the synchronization requirements, the transmission can continue; if the synchronization requirements cannot be met, NG-RAN can adjust the resource transmission algorithm to make the multiple QoS flows meet the synchronization requirements. If the synchronization requirements still cannot be met within a set time period, a notification message can be sent to the 5G core network (5G Core, 5GC) so that the 5GC can trigger the update of the QoS flow parameters after receiving the notification that the synchronization requirements cannot be met.

[0095] For example, after receiving a notification that synchronization requirements cannot be met, the 5GC can send the notification to the AF, which can then make adaptive adjustments. For instance, the AF can regenerate QoS requirement information for multiple QoS flows and send it to the core network elements to adjust the processing strategy for those flows.

[0096] In some embodiments, the determination of whether multiple QoS flows meet the synchronization requirements can be performed packet by packet or once per MAC TB transmission. However, this method may not be suitable for situations where the wireless channel changes drastically. Therefore, to improve system scalability, the determination of synchronization requirements can be designed as a state machine or threshold judgment, implemented in the user plane RLC or MAC instance.

[0097] Specifically, a threshold can be set when performing threshold judgment. When the change in packet transmission delay is within the threshold range, it can be considered that the synchronization requirement is met, and the reporting process will not be triggered. If the change in packet transmission delay exceeds the threshold range, it is considered that the synchronization requirement is not met, and the reporting process needs to be triggered.

[0098] When making judgments using a state machine, a state machine can be designed that includes two states: synchronous and asynchronous, or it can include other states, so that it can dynamically change with the delay state of data packet transmission.

[0099] In some embodiments, the state machine approach and the threshold-based approach can be implemented in combination or separately.

[0100] Referring to Figure 6, in S602, NG-RAN can select lost packets from multiple QoS flows for dropping based on synchronization parameters and other information.

[0101] In some embodiments, if poor network transmission quality is detected, NG-RAN can select dropped packets from multiple QoS streams based on synchronization parameters and other information. For example, some packets in QoS streams that do not meet synchronization requirements can be dropped first. For instance, when synchronously transmitting audio and video streams, if the audio stream has a large latency and cannot be synchronized with the video stream, some packets in the audio stream can be dropped first when network quality is poor. This ensures that packets in the audio stream that do not meet synchronization requirements are dropped, and instead, packets in the audio stream that can be synchronized with the video stream are transmitted, thereby maximizing the time consistency of multimodal data streams and ensuring the quality of user experience.

[0102] In some embodiments, if it is determined that packet loss is necessary based on network transmission quality, but the synchronization parameters between multiple QoS flows determine that the multiple QoS flows meet the synchronization requirements, then some data packets from these multiple QoS flows can be dropped in ascending order of packet priority. In other words, if it is determined that packet loss is necessary based on network transmission quality, then some data packets from QoS flows that do not meet the synchronization requirements can be dropped first. If all data packets meet the synchronization requirements, then they can be dropped in ascending order of packet priority. For example, when dropping data packets from multiple QoS flows in ascending order of packet priority, packet loss can be performed for each QoS flow in ascending order of packet priority; or packet loss can be performed for a subset of the multiple QoS flows (such as randomly selected QoS flows, lower-priority QoS flows, etc.) in ascending order of packet priority; or data packets from multiple QoS flows can be dropped together in ascending order of priority.

[0103] In S603, it is determined whether the packet loss rate meets the preset packet loss rate condition or whether network congestion has been alleviated. If so, S604 is executed; otherwise, S602 is executed to handle packet loss.

[0104] In some embodiments, if network congestion is detected to have eased during packet loss processing, it indicates that network transmission quality has returned to normal, and packet loss processing for multiple QoS flows can be stopped.

[0105] In some embodiments, during packet loss processing, if the packet loss rate of a certain QoS flow is detected to reach a set tolerable packet loss ratio, packet loss processing for that QoS flow can be stopped. This tolerable packet loss ratio represents the maximum allowable packet loss ratio, such as the maximum percentage of packets allowed to be dropped while ensuring the data receiver can normally decode other packets in the service data flow. Alternatively, packet loss processing for a certain PDU set can be stopped when the packet loss rate of that PDU set is detected to reach the set tolerable packet loss ratio. This embodiment ensures that when the percentage of dropped packets in a certain QoS flow (or a certain PDU set) reaches the set tolerable packet loss ratio, packets in that QoS flow (or PDU set) are no longer dropped, preventing the data receiver from being unable to recover other packets in that QoS flow (or PDU set) due to excessive packet loss.

[0106] In S604, packet loss processing is stopped for the current QoS flow or PDU set.

[0107] The technical solutions of the above embodiments of this application enable the introduction of synchronization parameters to make packet loss decisions for multiple QoS flows, realizing a more intelligent packet loss mechanism between multiple QoS flows with synchronization relationships, thereby maintaining the synchronization and overall service quality between different QoS flows even under network congestion.

[0108] The technical solutions of this application are applicable not only to 5G systems, but also to future mobile communication systems. Furthermore, the technical solutions of this application can be applied not only to data transmission in NG-RAN, but also to data transmission in other devices (such as terminal devices, UPFs, etc.).

[0109] The following describes an apparatus embodiment of this application, which can be used to execute the data transmission method in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the data transmission method described above.

[0110] Figure 7 shows a block diagram of a data transmission apparatus according to various embodiments of this application. This data transmission apparatus can be applied to access network elements, such as base station equipment. Of course, the data transmission apparatus shown in Figure 7 can also be applied to other electronic devices with computing processing capabilities (such as user equipment, UPF, etc.).

[0111] Referring to FIG7, a data transmission apparatus 700 according to various embodiments of the present application includes: an identification unit 702, an acquisition unit 704, and a processing unit 706.

[0112] The identification unit 702 is configured to identify the synchronization relationship between multiple QoS flows; the acquisition unit 704 is configured to acquire the synchronization parameters between the multiple QoS flows if a synchronization relationship is identified between them; and the processing unit 706 is configured to discard the target data packets in the multiple QoS flows according to the synchronization parameters if packet loss processing is required based on network transmission quality.

[0113] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: determine, according to the synchronization requirements determined by the synchronization parameters, a target QoS flow among the plurality of QoS flows that does not meet the synchronization requirements with other QoS flows; and select one or more data packets from the target QoS flow as the target data packets.

[0114] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: if the transmission delay between the target QoS stream and other QoS streams in the plurality of QoS streams is detected to be greater than or equal to the delay threshold indicated by the synchronization parameter, then determine that the target QoS stream and other QoS streams do not meet the synchronization requirement.

[0115] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: if it is determined that the plurality of QoS flows meet the synchronization requirements according to the synchronization requirements determined by the synchronization parameters, then select one or more data packets from the data packets in the plurality of QoS flows as the target data packets in order of priority from low to high.

[0116] In some embodiments of this application, based on the foregoing scheme, the identification unit 702 is configured to: receive indication information sent by a core network element, and, based on the indication information, identify whether the multiple QoS flows within the same Protocol Data Unit (PDU) session have a synchronization relationship, or identify whether the multiple QoS flows within different PDU sessions have a synchronization relationship. Alternatively, it may search for QoS parameters associated with a specific session in the User Equipment (UE) context, and then identify whether the multiple QoS flows have a synchronization relationship based on the QoS parameters. Or, it may identify whether the multiple QoS flows have a synchronization relationship based on QoS parameters at the QoS flow level.

[0117] In some embodiments of this application, based on the foregoing scheme, the acquisition unit 704 is configured to: receive indication information of the synchronization parameter sent by the core network element, and obtain a threshold of the synchronization time difference between the plurality of QoS flows based on the indication information of the synchronization parameter, wherein the threshold is used to indicate the maximum value of the time synchronization error between the plurality of QoS flows.

[0118] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is further configured to: use the same data radio bearer to transmit the multiple QoS streams according to the synchronization relationship, so that the multiple QoS streams satisfy the synchronization requirement when transmitted based on the same data radio bearer; or allocate different data radio bearers to the multiple QoS streams according to the synchronization relationship, so that the multiple QoS streams satisfy the synchronization requirement when transmitted based on different data radio bearers. The synchronization requirement is either preset or indicated.

[0119] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is further configured to: perform resource allocation processing on the plurality of QoS streams according to the synchronization relationship, so that the plurality of QoS streams meet the synchronization requirements when they are transmitted based on the allocated transmission resources; after performing resource allocation processing on the plurality of QoS streams according to the synchronization relationship, perform delay monitoring on the transmission process of the plurality of QoS streams; if the delay monitoring detects that the plurality of QoS streams cannot meet the synchronization requirements during transmission, then adjust the transmission resource allocation for the plurality of QoS streams.

[0120] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured as follows: if the transmission mode of the plurality of QoS streams is unacknowledged mode, then the Radio Link Control (RLC) instance for receiving the plurality of QoS streams performs delay monitoring on the uplink transmission process of the plurality of QoS streams, and the RLC instance for sending the plurality of QoS streams performs delay monitoring on the downlink transmission process of the plurality of QoS streams; if the transmission mode of the plurality of QoS streams is acknowledged mode, then the RLC instance for receiving the plurality of QoS streams and sending the plurality of QoS streams performs delay monitoring on the transmission process of the plurality of QoS streams.

[0121] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: monitor whether the plurality of QoS flows meet the synchronization requirements on a data packet basis; or monitor whether the plurality of QoS flows meet the synchronization requirements on a transport block basis.

[0122] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: if the transmission delay between the data packets of the plurality of QoS is within a set threshold range, then determine that the plurality of QoS streams can meet the synchronization requirement during transmission; if the transmission delay between the data packets of the plurality of QoS is not within the set threshold range, then determine that the plurality of QoS streams cannot meet the synchronization requirement during transmission.

[0123] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is configured to: indicate whether the multiple QoS streams can meet the synchronization requirements during transmission by using different states of the state machine according to the delay monitoring results of the multiple QoS streams; wherein, the state machine includes a synchronized state and an asynchronous state.

[0124] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is further configured to: after adjusting the transmission resource allocation for the plurality of QoS flows and after a set time period, if the plurality of QoS flows still cannot meet the synchronization requirements, send a notification message to the core network element so that the core network element adjusts the synchronization parameters for the plurality of QoS flows.

[0125] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is further configured to: if it is detected that the proportion of dropped data packets in any of the plurality of QoS flows reaches a set tolerable packet loss proportion, then stop performing packet loss processing on the QoS flow, wherein the tolerable packet loss proportion is used to represent the maximum allowable packet loss proportion.

[0126] In some embodiments of this application, based on the foregoing scheme, the processing unit 706 is further configured to: if it is detected that the network transmission quality has returned to normal, then stop performing packet loss processing on the plurality of QoS flows.

[0127] Figure 8 shows a schematic diagram of a computer system suitable for implementing an electronic device according to the embodiments of this application. The electronic device may be an access network element in the foregoing embodiments, such as a base station device.

[0128] It should be noted that the computer system 800 of the electronic device shown in Figure 8 is only an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0129] As shown in Figure 8, the computer system 800 may include a Central Processing Unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 802 or programs loaded from storage portion 808 into Random Access Memory (RAM) 803, such as performing the methods described in the above embodiments. The RAM 803 also stores various programs and data required for system operation. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0130] The following components can be connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. Removable media 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 810 as needed so that computer programs read from them can be installed into storage section 808 as needed.

[0131] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by central processing unit (CPU) 801, it performs various functions defined in the system of this application.

[0132] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a computer program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0133] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and a computer program.

[0134] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0135] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more computer programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0136] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0137] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause an electronic device to execute the method according to the embodiments of this application. For example, the electronic device can be an access network element, and the access network element can execute the data transmission method shown in Figures 4 and 5.

[0138] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0139] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A data transmission method, characterized by, include: Identify the synchronization relationships between multiple Quality of Service (QoS) flows; If a synchronization relationship is identified among the multiple QoS flows, then the synchronization parameters among the multiple QoS flows are obtained; If it is determined that packet loss processing is required based on network transmission quality, then the target data packets in the multiple QoS flows are discarded according to the synchronization parameters.

2. The data transmission method of claim 1, wherein, Discarding target data packets in the plurality of QoS flows according to the synchronization parameter includes: Based on the synchronization requirements determined by the synchronization parameters, a target QoS flow that does not meet the synchronization requirements with other QoS flows is identified among the plurality of QoS flows; Select one or more packets from the target QoS flow as the target packets.

3. The data transmission method of claim 2, wherein, Based on the synchronization requirements determined by the synchronization parameters, the target QoS flow among the plurality of QoS flows that does not meet the synchronization requirements with other QoS flows is identified, including: If the transmission delay between the target QoS stream and other QoS streams is detected to be greater than or equal to the delay threshold indicated by the synchronization parameter, then it is determined that the target QoS stream and other QoS streams do not meet the synchronization requirements.

4. The data transmission method according to claim 2 or 3, characterized in that, Discarding target data packets in the plurality of QoS flows according to the synchronization parameter further includes: If the synchronization requirement is determined based on the synchronization parameter, and it is determined that the plurality of QoS flows meet the synchronization requirement, then one or more data packets from the plurality of QoS flows are selected as the target data packet in ascending order of priority of the data packets in the plurality of QoS flows.

5. The data transmission method according to any one of claims 1 to 4, characterized in that, Identify synchronization relationships between multiple Quality of Service (QoS) flows, including: Receive indication information sent by a core network element, and based on the indication information, identify whether the multiple QoS flows within the same Protocol Data Unit (PDU) session have a synchronization relationship, or identify whether the multiple QoS flows within different PDU sessions have a synchronization relationship; or The system locates QoS parameters associated with a specific session in the user equipment (UE) context, and then identifies whether there is a synchronization relationship between the multiple QoS flows based on the QoS parameters; or Based on the QoS parameters at the QoS flow level, identify whether there is a synchronization relationship between the multiple QoS flows.

6. The data transmission method according to any one of claims 1 to 5, characterized in that, Obtaining synchronization parameters among the multiple QoS flows includes: The system receives indication information of the synchronization parameters sent by the core network element, and obtains a threshold for the synchronization time difference between the multiple QoS flows based on the indication information of the synchronization parameters. The threshold is used to indicate the maximum value of the time synchronization error between the multiple QoS flows.

7. The data transmission method according to any one of claims 1 to 6, characterized in that, The data transmission method further includes: According to the synchronization relationship, the multiple QoS streams are transmitted using the same data radio bearer so that the multiple QoS streams satisfy the synchronization requirement when transmitted based on the same data radio bearer, wherein the synchronization requirement is preset or indicated; or Based on the synchronization relationship, different data radio bearers are allocated to the multiple QoS streams so that the multiple QoS streams satisfy the synchronization requirements when they are transmitted based on different data radio bearers.

8. The data transmission method according to any one of claims 1 to 7, characterized in that, The data transmission method further includes: Resource allocation processing is performed on the plurality of QoS streams according to the synchronization relationship, so that the plurality of QoS streams meet the synchronization requirements when they are transmitted based on the allocated transmission resources, wherein the synchronization requirements are preset or indicated. After allocating resources to the plurality of QoS streams according to the synchronization relationship, the transmission process of the plurality of QoS streams is monitored for delay. If the latency monitoring detects that the multiple QoS streams cannot meet the synchronization requirements during transmission, the transmission resource allocation for the multiple QoS streams will be adjusted.

9. The data transmission method of claim 8, wherein, Delay monitoring is performed on the transmission process of the multiple QoS streams, including: If the transmission mode of the plurality of QoS streams is unacknowledged mode, then the Radio Link Control (RLC) instance used to receive the plurality of QoS streams performs delay monitoring on the uplink transmission process of the plurality of QoS streams, and the RLC instance used to send the plurality of QoS streams performs delay monitoring on the downlink transmission process of the plurality of QoS streams. If the transmission mode of the multiple QoS streams is acknowledgment mode, then the RLC instance used to receive and send the multiple QoS streams will perform latency monitoring on the transmission process of the multiple QoS streams.

10. The data transmission method according to claim 8 or 9, characterized in that, Delay monitoring is performed on the transmission process of the multiple QoS streams, including: For the multiple QoS flows, monitor whether the multiple QoS flows meet the synchronization requirements on a packet-by-packet basis; or For the multiple QoS streams, the synchronization requirements are monitored on a per-transmission-block basis.

11. The data transmission method according to any one of claims 8 to 10, characterized in that, Delay monitoring is performed on the transmission process of the multiple QoS streams, including: If the transmission delay between the multiple QoS data packets is within the set threshold range, then it is determined that the multiple QoS streams can meet the synchronization requirements during transmission. If the transmission delay between the multiple QoS data packets is not within the set threshold range, then it is determined that the multiple QoS streams cannot meet the synchronization requirements during transmission.

12. The data transmission method of any of claims 8 to 11, characterized in that, Delay monitoring is performed on the transmission process of the multiple QoS streams, including: Based on the delay monitoring results of the multiple QoS streams, different states of the state machine indicate whether the multiple QoS streams can meet the synchronization requirements during transmission; wherein, the state machine includes a synchronized state and an asynchronous state.

13. The data transmission method of any of claims 8 to 12, wherein, The data transmission method further includes: If, after adjusting the transmission resource allocation for the multiple QoS flows and after a set time period, the multiple QoS flows still cannot meet the synchronization requirements, a notification message is sent to the core network element so that the core network element adjusts the synchronization parameters for the multiple QoS flows.

14. The data transmission method of any of claims 1 to 13, wherein, The data transmission method further includes any of the following steps: If it is detected that the proportion of dropped packets in any of the plurality of QoS flows reaches the set tolerable packet loss proportion, then the packet loss processing is stopped for that QoS flow. The tolerable packet loss proportion is used to represent the maximum packet loss proportion that can be allowed. If the network transmission quality is detected to have returned to normal, then the packet loss processing for the multiple QoS flows is stopped.

15. A data transmission apparatus, characterized by comprising: include: The identification unit is configured to identify the synchronization relationship between multiple QoS flows; The acquisition unit is configured to acquire synchronization parameters between the multiple QoS flows if a synchronization relationship is detected between them. The processing unit is configured to discard target data packets in the plurality of QoS flows according to the synchronization parameter if it is determined that packet loss processing is required based on network transmission quality.

16. A computer readable medium having stored thereon a computer program, characterized in that, When the computer program is executed by a processor, it implements the data transmission method according to any one of claims 1 to 14.

17. A computer device, comprising: include: One or more processors; A memory for storing one or more computer programs, which, when executed by one or more processors, cause the computer device to implement the data transmission method according to any one of claims 1 to 14.

18. A computer program product, characterised in that, The computer program product includes a computer program stored in a computer-readable storage medium, wherein a processor of a computer device reads from the computer-readable storage medium and executes the computer program, causing the computer device to perform the data transmission method according to any one of claims 1 to 14.

Images