Service data stream processing method and apparatus, computer-readable medium, and device

Abstract

Embodiments of the present application provide a service data stream processing method and apparatus, a computer-readable medium, and a device. The service data stream processing method comprises: if a plurality of service data streams need to meet a synchronization requirement during transmission, generating processing policy information of the plurality of service data streams on the basis of the synchronization requirement; and sending the processing policy information to a session management function network element, such that the session management function network element can configure Quality of Service (QoS) processing-related information for a processing device of the plurality of service data streams on the basis of the processing policy information.

Description

Methods, apparatus, computer-readable media and devices for processing business data streams

[0001] This application claims priority to Chinese Patent Application No. 202411053106.8, filed on August 1, 2024, entitled "Method, Apparatus, Computer-readable Medium and Device for Processing Business Data Flow". Technical Field

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

[0003] In 5th-Generation (5G) mobile communication technology 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), etc.

[0004] These high-bandwidth interactive services not only have high requirements for transmission timeliness, but their service flows typically include 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. Different QoS flows may have different transmission latency, potentially causing data asynchrony between different media types when the receiving end generates and plays media content based on the received multiple media type service flows. Summary of the Invention

[0005] Embodiments of this application provide a method, apparatus, computer-readable medium, and device for processing business data streams.

[0006] This application provides a method for processing service data streams, including: if multiple service data streams need to meet synchronization requirements during transmission, generating processing strategy information for the multiple service data streams according to the synchronization requirements, wherein the processing strategy information is used to provide a first strategy for configuring first quality of service (QoS) processing related information for the transmission synchronization of the multiple service data streams; and sending the processing strategy information to a session management function network element.

[0007] This application provides a method for processing service data streams, including: generating synchronization requirements among multiple service data streams, wherein the synchronization requirements are used to indicate that the multiple service data streams need to meet synchronization requirements during transmission, and are used to generate processing strategy information for the multiple service data streams, wherein the processing strategy information is used to provide a first strategy for the transmission synchronization of the multiple service data streams and configure a first quality of service (QoS) processing related information; and providing the synchronization requirements to core network elements.

[0008] This application provides a service data stream processing apparatus, including: a generation unit configured to generate processing strategy information for multiple service data streams if they need to meet synchronization requirements during transmission, the processing strategy information being used to provide a first strategy for configuring first quality of service (QoS) processing related information for the transmission synchronization of the multiple service data streams; and a sending unit configured to send the processing strategy information to a session management function network element.

[0009] This application provides a service data stream processing apparatus, comprising: a generation unit configured to generate synchronization requirements among multiple service data streams, the synchronization requirements being used to indicate that the multiple service data streams need to meet synchronization requirements during transmission, and to generate processing strategy information for the multiple service data streams, the processing strategy information being used to provide a first strategy for configuring first quality of service (QoS) processing related information for the transmission synchronization of the multiple service data streams; and a sending unit configured to provide the synchronization requirements to core network elements.

[0010] This application provides a computer-readable medium storing a computer program thereon, which, when executed by a processor, implements the business data stream processing method as described in the above embodiments.

[0011] This application provides an electronic device, including: one or more processors; and a storage device for storing one or more computer programs, which, when executed by the one or more processors, enable the electronic device to implement the business data stream processing method described in the above embodiments.

[0012] This application provides a computer program product comprising a computer program stored in a computer-readable storage medium. An electronic device's processor reads and executes the computer program from the computer-readable storage medium, causing the electronic device to perform the business data stream processing methods provided in the various example embodiments described above.

[0013] In some embodiments of this application, when a core network element determines that multiple service data streams need to meet synchronization requirements during transmission, it can generate processing strategy information for the multiple service data streams based on these synchronization requirements. This processing strategy information is then sent to a session management function network element, enabling the session management function network element to configure QoS processing-related information for the processing devices of the multiple service data streams according to the processing strategy information. Therefore, the technical solution of this application allows the core network element to generate processing strategy information for multiple service data streams when they need to meet synchronization requirements. This enables these multiple service data streams to achieve transmission delays with minimal or equal differences during transmission, improving the problem of different service data streams having different or excessively large delays in their mapped QoS flows, leading to asynchronous playback content. This is beneficial for improving the user experience of multimedia services. 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 an embodiment of this application;

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

[0017] Figure 4 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0018] Figure 5 shows a schematic diagram of a key network element architecture for a 5G network.

[0019] Figure 6 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0020] Figure 7 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0021] Figure 8 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0022] Figure 9 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0023] Figure 10 shows a flowchart of a business data flow processing method according to an embodiment of this application;

[0024] Figure 11 shows a block diagram of a processing apparatus for a business data stream according to an embodiment of this application;

[0025] Figure 12 shows a block diagram of a processing apparatus for a business data stream according to an embodiment of this application;

[0026] Figure 13 shows a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application. Detailed Implementation

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

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

[0029] In this application, 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.

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

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

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

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

[0034] 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 graphics, encode audio signals and rendered images, and finally transmit the encoded data obtained through the encoding process to various game clients via the network. Game clients can be 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, and head-mounted displays. Alternatively, 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.

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

[0036] In the various multimedia-based interactive service application scenarios mentioned above, even a single multimedia service frame or GoP (Group of Packets) may have a large number of bytes, so it needs to be split into multiple data packets for transmission.

[0037] Specifically, as shown in Figure 2, taking a 5G system as an example, a 5G communication network typically includes a core network (CN), a radio access network (RAN), a transport network, a user interface (UE), and an application layer.

[0038] The radio access network (RAN) is responsible for connecting user equipment to a network (such as the Internet) and handling data transmission. A RAN may include a base station (Next-Generation NodeB, gNB).

[0039] The core network includes, for example, User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), and so on.

[0040] The User Equipment (UE) process handles data transmission between user equipment (UE) and the network, including packet forwarding, routing, and QoS (Quality of Service) management. The UE also handles packet encryption and decryption. The Access Management Function (AMF) handles access, mobility management, and session management with UEs. The AMF is responsible for authentication, authorization, and key management with UEs, as well as location updates, session establishment, and release. The Service Management Function (SMF) manages UE data transmission sessions, including session establishment, maintenance, and release. The SMF also manages data transmission policies to ensure efficient and reliable data transmission. The PCF provides Access and Mobility Policy Control (APC) and Session Management Policy Control (SMP). The User Data Management Function (UDM) is responsible for the unified management of user data, including user identity, subscription information, and authentication data. It serves as the central storage and management point for user data in the 5G network.

[0041] As shown in Figure 2, the user plane includes, for example, an application server, a UPF, a base station, and a UE. The user plane is responsible for transmitting user data. Multimedia data packet transmission, in some typical service scenarios, can occur in the downlink direction, such as from the application server (AS) to the UPF, and then to the UE via the gNB. During transmission, multimedia data packets (taking XR 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 via Protocol Data Unit (PDU) sessions. At the UE, the sub-data packets are submitted upwards through the protocol stack and reassembled to recover the multimedia data packet. The UE's protocol stack, from bottom to top, includes the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and IP layer.

[0042] 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. PDCP stands for Packet Data Convergence Protocol. SDAP stands for Service Data Adaptation Protocol.

[0043] 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 Group of Packets (GoP) 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 transmitted during transmission, these multiple IP packets can form a PDU set.

[0044] 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. These different QoS flows may have different transmission delays, such as the delay between the Radio Access Network (RAN) and the UPF. 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.

[0045] Based on the above problems, this application proposes a new service data stream processing scheme, which enables the core network to generate processing strategy information for multiple service data streams when multiple service data streams need to meet synchronization requirements. This allows these multiple service data streams to achieve transmission delays with minimal or equal differences during transmission based on the processing strategy information. This improves the problem of different service data streams having different or excessively large delays in their QoS flows, which leads to asynchronous playback content and enhances the user experience for multimedia services.

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

[0047] Figure 4 shows a flowchart of a service data flow processing method according to an embodiment of this application. This service data flow processing method can be executed by a Policy Control Function (PCF) network element, or it can be executed by other network elements. Referring to Figure 4, the service data flow processing method may include steps S410 to S420.

[0048] In step S410, if multiple service data streams need to meet synchronization requirements during transmission, processing strategy information for the multiple service data streams is generated based on these synchronization requirements. The processing strategy information is used to provide a first strategy for configuring first Quality of Service (QoS) processing-related information for the transmission synchronization of the multiple service data streams.

[0049] A service data flow (SDF) can be a set of data packets or one or more IP data flows. One or more IP data flows with the same source IP address, destination IP address, source port, destination port, and protocol ID can be designated as a service data flow. A service data flow can be a multimedia service data flow. Multimedia services include, for example, cloud gaming, VR, AR, MR, XR, XRM, and CR services. Service data flows can be transmitted using a set of service data packets (PDUs). This is because if a single multimedia service frame or GOP forms a data packet, its size may be 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, service data flows can also be transmitted per-packet.

[0050] In some example embodiments, multiple service data streams can be service data streams of different media types, such as audio, video, haptic, or other media types. Service data streams of different media types may have different QoS requirements or they may have the same QoS requirements. These multiple service data streams can be mapped to the same QoS stream or to different QoS streams during transmission. For example, if these multiple service data streams of different media types have different QoS requirements, then these different media type service data streams can be mapped to different QoS streams for transmission.

[0051] Take cloud gaming as an example. A cloud gaming service may contain a first service data stream of audio type, a second service data stream of video type, and a third service data stream of haptic or other types. These three media types of service data streams are associated with the same multimedia service. Therefore, during transmission, if these three service data streams are mapped to different QoS streams, then these QoS streams are related; for example, there are synchronization requirements between these QoS streams. Synchronization requirements mean that the latency information between these QoS streams should be consistent or within a certain latency range. Multiple service data streams associated with the same multimedia service may contain one or more identifiers such as the same service ID, the same session ID, the same UE address, etc., or be associated with the same descriptive information.

[0052] In some example embodiments, the processing method of the service data stream shown in Figure 4, executed by the PCF, is illustrated as an example. The PCF can receive synchronization requirements for multiple service data streams sent by the Application Function (AF) network element. These synchronization requirements indicate that the multiple service data streams need to meet synchronization requirements during transmission. The PCF can then generate processing strategy information for the multiple service data streams based on these synchronization requirements. In various embodiments of this application, the processing strategy information for multiple service data streams can refer to processing strategy information corresponding to multiple service data streams. There can be one or more processing strategy information entries. One processing strategy information entry can be applied to one or more service data streams.

[0053] In some example embodiments, if it is determined that the multiple service data streams are transmitted through the same Protocol Data Unit (PDU) session, then it is determined that the multiple service data streams need to meet synchronization requirements during transmission. For example, the PCF may also consider multiple service data streams transmitted through the same PDU session as service data streams that need to meet synchronization requirements. Alternatively, the PCF can identify multiple service data streams transmitted in the same PDU session as service data streams with synchronization requirements. Multiple service data streams transmitted in the same PDU session can be determined using associated PDU session IDs and / or Tunnel Endpoint IDs (TEIDs), etc.

[0054] In some example embodiments, when generating processing policy information for multiple service data streams, processing policy information can be generated based on the synchronization requirements of the multiple service data streams when they are mapped to different QoS streams for processing. This processing policy information is used to indicate that the different QoS streams obtained by mapping the multiple service data streams need to meet synchronization requirements. In other words, multiple service data streams can be mapped to different QoS streams, thus obtaining multiple QoS streams, and the PCF can generate processing policy information for these multiple QoS streams. For example, a processing policy information is generated for each of these multiple QoS streams, or the number of multiple QoS streams and the processing policy information are not in a one-to-one correspondence.

[0055] Referring again to Figure 4, in step S420, the processing policy information is sent to the session management function network element. The session management function network element configures QoS processing (or first QoS processing) related information to the processing devices of multiple service data streams according to the processing policy information.

[0056] In some example embodiments, the process by which the PCF sends processing policy information to the Session Management Function (SMF) network element may include: the PCF and SMF interacting through the Session Management (SM) Policy Association Establishment signaling procedure or through the Session Management (SM) Policy Association Modification signaling procedure, and then the PCF sending the relevant processing policy information to the SMF through the Session Management Policy Context Data IE.

[0057] In some example embodiments, the processing equipment for the service data stream may include a UPF, a base station device, and / or a user equipment. For example, the SMF can generate a first N4 rule based on the service data stream processing policy information, which includes rules such as multiple QoS streams needing to meet synchronization requirements, and then send the first N4 rule to the UPF. The SMF can generate first QoS profiles based on the service data stream processing policy information, which includes information such as multiple QoS streams needing to meet synchronization requirements, and then send the first QoS profiles to the base station. The SMF can generate first QoS rules based on the service data stream processing policy information, which includes rules such as multiple QoS streams needing to meet synchronization requirements, and then send the first QoS rules to the UE.

[0058] Taking a 5G system as an example, Figure 5 shows the key network element architecture of a 5G network as defined by the 3rd Generation Partnership Project (3GPP). In a 5G system, the Access and Mobility Management Function (AMF), SMF, UPF, PCF, Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), and Unified Data Management (UDM) are core network elements of the 5G network. The UE can be a 5G terminal such as a mobile phone or tablet. The Radio Access Network (RAN) can be a 5G base station. The Data Network (DN) is the data network, i.e., the application server (AS) accessed by the UE.

[0059] The AMF is responsible for terminating the N2 interface of the base station control plane and implementing the encoding and decoding of the Next Generation Application Protocol (NGAP) based on the Stream Control Transmission Protocol (SCTP). The base station and AMF transmit the NGAP application layer protocol via the SCTP transport layer protocol, carrying the UE's Non-Access Stratum (NAS) signaling data within the NGAP. The AMF is also responsible for terminating the UE's N1 interface, implementing NAS encryption and integrity protection, and handling UE access authentication, authorization management, registration, connection, reachability, and mobility management functions, as well as the transparent transmission of session management messages between the UE and the SMF.

[0060] Additionally, (R)AN interacts with UPF via interface N3. UPFs interact with each other via interface N9. UPFs interact with SMF via interface N4. UPFs interact with DN via interface N6. SMFs interact with AMFs via interface N11. SMFs interact with PCFs via interface N7. SMFs interact with UDMs via interface N10. PCFs interact with Application Functions (AFs) via interface N5. AMFs interact with each other via interface N14. AMFs interact with PCFs via interface N15. AMFs interact with UDMs via interface N8. AMFs interact with NSSFs via interface N22. AMFs interact with AUSSFs via interface N12. AUSFs interact with UDMs via interface N13.

[0061] Based on the system architecture shown in Figure 5, the SMF can configure the first and other N4 rules generated to the UPF through the N4 interface, configure the first and other QoS Profiles to the (R)AN through the AMF, and / or configure the first and other QoS rules to the UE through the AMF+NAS connection.

[0062] Based on the technical solution of the embodiment shown in FIG4, and referring to FIG6, in the embodiment of this application, the service data stream processing method may include steps S610 and S620 in addition to steps S410 to S420.

[0063] In step S610, synchronization monitoring strategy information for multiple service data streams is generated. This synchronization monitoring strategy information is used to provide a second strategy for configuring second QoS processing information to monitor the synchronization of the multiple service data streams. In various embodiments of this application, the synchronization monitoring strategy information for multiple service data streams may refer to synchronization monitoring strategy information corresponding to multiple service data streams. There may be one or more synchronization monitoring strategy information entries. One synchronization monitoring strategy information entry may correspond to one or more service data streams.

[0064] In some example embodiments, the PCF can act as a consumer for monitoring the synchronization of service data streams or QoS streams. The PCF can then generate synchronization monitoring policy information for multiple service data streams according to its own needs. For example, if the PCF determines that multiple service data streams need to meet synchronization requirements during transmission, it generates processing policy information for the multiple service data streams based on these synchronization requirements. Alternatively, the PCF can also receive synchronization monitoring requests for service data streams sent by application function network elements. These synchronization monitoring requests instruct the monitoring of the transmission synchronization of multiple service data streams, and the PCF can then generate synchronization monitoring policy information for the multiple service data streams based on these synchronization monitoring requests.

[0065] In step S620, the synchronization monitoring policy information is sent to the session management function network element. The session management function network element can configure QoS processing-related information to the processing devices of multiple service data streams according to the synchronization monitoring policy information, so as to monitor the synchronization of multiple service data streams.

[0066] In some example embodiments, the process of the PCF sending synchronization monitoring policy information to the SMF network element may include: the PCF and SMF interact by establishing a signaling flow association through a session management policy association, or by modifying a signaling flow association through a session management policy association, and then the PCF sends the synchronization monitoring policy information to the SMF through the session management policy context data information element.

[0067] Similarly, the processing equipment for service data streams may include UPF, base station equipment, and / or user equipment. For example, the SMF can generate a second N4 rule based on synchronization monitoring policy information, which includes information such as synchronization monitoring requirements for multiple QoS streams, and then send the second N4 rule to the UPF. The SMF can generate second QoS profiles based on synchronization monitoring policy information, which includes information such as synchronization monitoring requirements for multiple QoS streams, and then send the second QoS profiles to the base station. The SMF can generate third QoS rules based on synchronization monitoring policy information, which includes information such as synchronization monitoring requirements for multiple QoS streams, and then send the third QoS rules to the UE.

[0068] In some example embodiments, after sending monitoring policy information to the session management function network element, the PCF can also receive synchronization monitoring results reported by access network elements (such as base stations), as well as synchronization monitoring results reported by other core network elements. The synchronization monitoring results reported by the access network element can be the synchronization monitoring results of the Uu interface; other core network elements can be, for example, the UPF, and the synchronization monitoring results reported by the UPF can be the synchronization monitoring results of the N3 or N9 interface.

[0069] In some example embodiments, the PCF can also adjust the QoS parameter information of service data streams based on the end-to-end latency and synchronization requirements of multiple service data streams, as well as the transmission latency of multiple service data streams within the core network. The adjusted QoS parameter information of the service data streams can serve as the processing strategy information for the service data streams. For example, if the service data stream is transmitted via PDU sets, one or more parameters such as PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), Maximum Data Burst Volume (MDBV), and Packet Delay Variation (PDV) can be adjusted. If the service data stream is transmitted per-packet, one or more parameters such as Packet Delay Budget (PDB), Packet Error Rate (PER), and Maximum Data Burst Volume can be adjusted.

[0070] Let's take adjusting the PDB as an example. The PCF can adjust the PDB on the access network side or the PDB on the core network side.

[0071] The technical solutions of the embodiments of this application have been described above from the perspective of PCF. The implementation details of the technical solutions of the embodiments of this application will be described below from the perspective of AF.

[0072] Figure 7 shows a flowchart of a service data stream processing method according to an embodiment of this application. This service data stream processing method can be executed by an AF (Automatic Front-End) or by other network elements. Referring to Figure 7, the service data stream processing method may include steps S710 to S720.

[0073] In step S710, synchronization requirements are generated among multiple service data streams. These synchronization requirements indicate that the multiple service data streams need to meet synchronization requirements during transmission. These synchronization requirements can also be used to generate processing strategy information for the multiple service data streams. This processing strategy information provides a first strategy for configuring first Quality of Service (QoS) processing-related information for the transmission synchronization of the multiple service data streams.

[0074] The relevant descriptions of multiple business data flows can be found in the technical solutions of the aforementioned various embodiments, and will not be repeated here.

[0075] In step S720, the synchronization requirement is provided to the core network element. The core network element can generate processing strategy information for multiple service data streams based on the synchronization requirement. This processing strategy information is used to indicate that different QoS streams mapped from multiple service data streams need to meet the synchronization requirement.

[0076] The process by which the AF provides synchronization requirements between multiple service data streams to core network elements may specifically include: if the AF is trusted, it can directly send the synchronization requirements between multiple service data streams to the PCF; if the AF is untrusted, it can send the synchronization requirements between multiple service data streams to the NEF, which then forwards them to the PCF. In various embodiments of this application, "trusted / untrusted" for example refers to being trusted / untrusted from the perspective of the PCF.

[0077] The description of the processing strategy information for core network elements to generate multiple service data streams according to synchronization requirements can be referred to the technical solutions of the aforementioned embodiments, and will not be repeated here.

[0078] Based on the technical solution of the embodiment shown in FIG7, and referring to FIG8, in the embodiment of this application, the service data stream processing method may include steps S810 and S820 in addition to steps S710 to S720.

[0079] In step S810, a synchronization monitoring requirement for the business data stream is generated.

[0080] This synchronization monitoring requirement is used to instruct the monitoring of the transmission synchronization of multiple service data streams in order to determine whether the multiple service data streams can meet the synchronization requirements during transmission.

[0081] In step S820, the synchronization monitoring requirement is provided to the core network elements. The core network elements can generate synchronization monitoring strategy information corresponding to multiple service data streams based on the synchronization monitoring requirement.

[0082] The process by which the AF provides synchronization monitoring requests to core network elements can specifically include: if the AF is trusted, then the AF can directly send the synchronization monitoring requests to the PCF; if the AF is untrusted, then the AF can send the synchronization monitoring requests to the NEF, and then the NEF will forward them to the PCF.

[0083] The description of the synchronization monitoring strategy information generated by the core network elements for multiple service data streams according to the synchronization monitoring requirements can be referred to the technical solutions of the aforementioned embodiments, and will not be repeated here.

[0084] In some example embodiments, after providing synchronization monitoring requirements to core network elements, the AF can also receive synchronization monitoring results reported by access network elements (such as base stations), as well as synchronization monitoring results reported by other core network elements. For example, the synchronization monitoring results reported by access network elements can be synchronization monitoring results of the Uu interface. If other core network elements can be, for example, UPF, then the synchronization monitoring results reported by UPF can be synchronization monitoring results of the N3 interface or the N9 interface.

[0085] The technical solutions of the above embodiments of this application enable core network elements to generate processing strategy information for multiple service data streams when multiple service data streams need to meet synchronization requirements. This allows these multiple service data streams to achieve transmission delays with minimal or equal differences during transmission based on the processing strategy information. This improves the problem of different service data streams having different or excessively large delays in their QoS flows, which leads to asynchronous playback content and enhances the user experience for multimedia services.

[0086] The following section takes the processing of XRM services in a 5G system as an example to further explain the implementation details of the technical solution in the application embodiment.

[0087] In this embodiment, core network elements can generate PCC rules (processing policy information) based on the synchronization requirements between multiple QoS flows, and satisfy the synchronization requirements of multiple QoS flows by monitoring the synchronization between different QoS flows. Specifically, the PCC rule generated during the PDU session establishment phase includes the synchronization requirements for multiple QoS flows. This requirement can be indicated individually, for example, by the AF indicating the synchronization requirement. Alternatively, it can be assumed that XRM service flows within the PDU session must meet the synchronization requirements; in this case, no separate indication is needed. Then, the corresponding control plane network elements, user plane network elements, and NG-RAN perform the appropriate processing according to the PCC rules.

[0088] Referring to Figure 9, the technical solution of this application embodiment will be described in detail below with a specific example, which includes the following steps:

[0089] Step S901: After the PDU session is established (e.g., the UE establishes a PDU session through RAN, UPF, SMF, PCF), the AF (which can be one or more AFs) and 5GS exchange signaling information regarding the synchronization requirements or needs between multiple (different) Service Data Flows (SDFs). Through this step, the AF can provide the synchronization requirements or needs to the core network elements. These multiple service data flows include service data flows within the same PDU session and service data flows between different PDU sessions. For example, the synchronization requirements or needs between multiple service data flows can also be obtained implicitly. For instance, multiple service data flows (e.g., two or more) within the same PDU session can be identified as needing to meet synchronization requirements.

[0090] Step S902: According to the AF instruction, the PCF generates corresponding first PCC rules. Based on the synchronization requirements of multiple service data streams interacted with by the AF, the PCF generates first PCC rules for multiple service data streams. These first PCC rules include synchronization requirements for multiple QoS streams, which are mapped from the multiple service data streams. In this step, if the PCF determines that multiple service data streams need to meet synchronization requirements during transmission, it generates processing policy information (the first PCC rules) for the multiple service data streams according to the synchronization requirements. Then, the PCF can configure the corresponding rule information for the UPF, RAN, and / or UE respectively through the SMF.

[0091] In step S903, the 5GC configures the first PCC rule supporting multi-QoS stream synchronization transmission to the UPF, RAN, and / or UE. Specifically, after generating the first PCC rule in step S902, the PCF can send the first PCC rule to the SMF. The SMF will then configure the first N4 rule generated by combining the first PCC rule to the UPF, configure the first QoS profiles to the NG-RAN, and / or configure the first QoS rules to the UE.

[0092] Step S904: When a downlink data packet from the AS arrives at the UPF, the UPF processes the data of multiple QoS streams according to the first N4 rule, including support / processing for the synchronization of multiple QoS streams.

[0093] In step S905, the base station processes the transmission of multiple QoS streams according to the first QoS profiles to ensure the synchronization requirements of the multiple QoS streams. Synchronization on the base station side refers to the transmission delay differences of the corresponding QoS streams on the Uu interface being within a specific range, or being completely identical.

[0094] In some example implementations, after the PDU session is established, a QoS monitoring mechanism can be used to monitor the segmented latency between the UPF and NG-RAN, and between the NG-RAN and the UE, and then the synchronization of multiple QoS flows can be confirmed through QoS monitoring. If these multiple QoS flows are not synchronized, the synchronization requirements of multiple QoS flows can be met by adjusting one or more QoS parameters of the multiple QoS flows, such as PDB or PSDB.

[0095] Specifically, as shown in Figure 10, the steps include the following:

[0096] In step S1001, the AF (which can be one or more AFs) interacts with the 5GS via signaling to instruct the monitoring of synchronization between multiple different service data streams. In this step, the AF can generate synchronization monitoring requirements for multiple service data streams. These requirements are used to instruct the monitoring of the transmission synchronization of the multiple service data streams to determine whether the multiple service data streams can meet the synchronization requirements during transmission, and the synchronization monitoring requirements are provided to the core network elements of the 5GS.

[0097] In step S1002, according to the AF instruction, the PCF generates corresponding second PCC rules. These second PCC rules include synchronization monitoring requirements for multiple QoS flows, which are mapped from multiple service data flows. Then, the corresponding rule information is configured to the UPF, RAN and / or UE through the SMF.

[0098] In step S1003, the 5GC configures the second policy information supporting multi-QoS flow synchronization monitoring to the UPF, RAN, and / or UE. Specifically, the PCF generates a second PCC rule and sends it to the SMF. The SMF configures the second N4 rule generated by combining the second PCC rule to the UPF, the second QoS profiles to the NG-RAN, and / or the second QoS rules to the UE.

[0099] Step S1004: When a downlink data packet from the AS arrives at the UPF, the UPF processes the data of multiple QoS streams according to the second N4 rule, including support for the synchronization monitoring of multiple QoS streams.

[0100] In step S1005, the base station processes the transmission of multiple QoS streams according to the second QoS profiles to ensure the synchronization monitoring requirements of multiple QoS streams. The synchronization on the base station side refers to the fact that the transmission delay difference of the corresponding QoS stream data on the Uu interface is within a specific range or is completely the same.

[0101] In step S1006, the RAN and 5GC network elements report the synchronization monitoring results of multiple QoS flows to the corresponding consumer network elements, which may be AF, PCF, or other network elements.

[0102] In one embodiment of this application, the PCF can adjust QoS parameters, such as adjusting the PSDB or PDB, based on the latency of the N6 interface (i.e., between DN / AS and UPF) and the end-to-end latency and synchronization requirements of the service data flow itself. Taking the adjustment of PDB as an example, the PCF can adjust the PDB on the access network side (i.e., AN-PDB) or the PDB on the core network side (i.e., CN-PDB).

[0103] For example, if the end-to-end latency requirement of a business data stream is T0ms, and the actual latency on the N6 port is T1ms, then the total latency within 5GC should be less than T0-T1, and the latency jitter should be limited to a certain range.

[0104] In summary, the technical solution of this application can solve the problem from an end-to-end perspective that after multimedia service flows are mapped into multiple QoS flows, the different transmission delays between these QoS flows in 5G / 6G and other mobile communication networks affect the playback synchronization of multimedia services at the receiving end, and can reduce the processing load on the NG-RAN base station. Furthermore, this solution can also incorporate the latency variations of the N6 interface, enabling the PCF-generated strategy to compensate for these latency variations within the 5GS, thus better adapting to changes in real-time transmission conditions of end-to-end multimedia services.

[0105] 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 are not only applicable to XRM services, but also to the processing of other multimedia service streams.

[0106] The following describes an apparatus embodiment of this application, which can be used to execute the service data stream processing method described 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 service data stream processing method described above.

[0107] Figure 11 shows a block diagram of a service data flow processing apparatus according to an embodiment of the present application. The service data flow processing apparatus can be applied to a PCF or other network elements.

[0108] Referring to FIG11, the service data stream processing apparatus 1100 according to an embodiment of the present application includes: a generation unit 1102 and a transmission unit 1104.

[0109] The generation unit 1102 is configured to generate processing strategy information for multiple service data streams if they need to meet synchronization requirements during transmission. The processing strategy information is used to provide a first strategy for configuring first quality of service (QoS) processing related information for the transmission synchronization of the multiple service data streams. The sending unit 1104 is configured to send the processing strategy information to the session management function network element so that the session management function network element configures QoS processing related information for the processing devices of the multiple service data streams according to the processing strategy information.

[0110] In some embodiments of this application, based on the foregoing scheme, the generation unit 1102 is further configured to: receive synchronization requirements of multiple service data streams sent by the application function network element, wherein the synchronization requirements are used to indicate that the multiple service data streams need to meet synchronization requirements during transmission; and determine, based on the synchronization requirements, that the multiple service data streams need to meet synchronization requirements during transmission.

[0111] In some embodiments of this application, based on the foregoing scheme, the generation unit 1102 is further configured to: treat multiple service data streams transmitted through the same Protocol Data Unit (PDU) session as service data streams that need to meet synchronization requirements. If it is determined that the multiple service data streams are transmitted through the same PDU session, then it is determined that the multiple service data streams need to meet synchronization requirements during transmission.

[0112] In some embodiments of this application, based on the foregoing scheme, the generation unit 1102 is configured to: generate processing strategy information when the multiple service data streams are mapped to different QoS streams for processing according to the synchronization requirements, wherein the processing strategy information is used to indicate that the different QoS streams mapped from the multiple service data streams need to meet the synchronization requirements.

[0113] In some embodiments of this application, based on the foregoing scheme, the generation unit 1102 is further configured to: generate synchronization monitoring strategy information corresponding to the plurality of service data streams, wherein the synchronization monitoring strategy information is used to provide a second strategy for configuring second QoS processing related information to monitor the synchronization of the plurality of service data streams; the sending unit 1104 is further configured to: send the synchronization monitoring strategy information to the session management function network element, so that the session management function network element configures QoS processing related information to the processing devices of the plurality of service data streams according to the synchronization monitoring strategy information to monitor the synchronization of the plurality of service data streams.

[0114] In some embodiments of this application, based on the foregoing scheme, the generation unit 1102 is configured to: receive synchronization monitoring requirements for the service data streams sent by the application function network element, and generate synchronization monitoring strategy information corresponding to the multiple service data streams according to the synchronization monitoring requirements.

[0115] In some embodiments of this application, based on the foregoing scheme, the service data flow processing device 1100 further includes: a receiving unit, configured to, after sending the monitoring strategy information to the session management function network element, perform at least one of the following processes: receiving synchronization monitoring results reported by the access network element; receiving synchronization monitoring results reported by other core network elements.

[0116] In some embodiments of this application, based on the foregoing scheme, the service data stream processing device 1100 further includes: a processing unit configured to adjust the quality of service parameters of the plurality of service data streams according to the synchronization requirements and end-to-end delay requirements of the plurality of service data streams, as well as the transmission delay of the plurality of service data streams in the core network.

[0117] Figure 12 shows a block diagram of a service data stream processing apparatus according to an embodiment of the present application. The service data stream processing apparatus can be applied to an AF or other network elements.

[0118] Referring to FIG12, a service data stream processing apparatus 1200 according to an embodiment of the present application includes: a generation unit 1202 and a transmission unit 1204.

[0119] The generation unit 1202 is configured to generate synchronization requirements among multiple service data streams. These synchronization requirements are used to indicate that the multiple service data streams need to meet synchronization requirements during transmission. The generation unit 1202 is also configured to generate processing strategy information for the multiple service data streams. This processing strategy information provides a first strategy for configuring first Quality of Service (QoS) processing related information for the transmission synchronization of the multiple service data streams. The sending unit 1204 is configured to provide the synchronization requirements to core network elements, so that the core network elements generate processing strategy information for the multiple service data streams based on the synchronization requirements. This processing strategy information indicates that different QoS streams mapped from the multiple service data streams need to meet synchronization requirements.

[0120] In some embodiments of this application, based on the foregoing scheme, the generation unit 1202 is further configured to: generate synchronization monitoring requirements for the plurality of service data streams, wherein the synchronization monitoring requirements are used to instruct the monitoring of the transmission synchronization of the plurality of service data streams to determine whether the plurality of service data streams can meet the synchronization requirements during transmission; the sending unit 1204 is further configured to: provide the synchronization monitoring requirements to the core network element, so that the core network element generates synchronization monitoring strategy information corresponding to the plurality of service data streams according to the synchronization monitoring requirements.

[0121] In some embodiments of this application, based on the foregoing scheme, the service data flow processing device 1200 further includes: a receiving unit, configured to, after providing the synchronization monitoring requirement to the core network element, perform at least one of the following processes: receiving synchronization monitoring results reported by the access network element; receiving synchronization monitoring results reported by other core network elements.

[0122] Figure 13 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 the PCF or AF in the foregoing embodiments.

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

[0124] As shown in Figure 13, the computer system 1300 may include a Central Processing Unit (CPU) 1301, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 1302 or programs loaded from storage portion 1308 into Random Access Memory (RAM) 1303, such as performing the methods described in the above embodiments. The RAM 1303 also stores various programs and data required for system operation. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via a bus 1304. An Input / Output (I / O) interface 1305 is also connected to the bus 1304.

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

[0126] 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 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit (CPU) 1301, it performs various functions defined in the system of this application.

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

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

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

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

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

[0132] From 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, and includes several instructions to cause an electronic device to execute the method according to the embodiments of this application.

[0133] For example, an electronic device can be a PCF, in which case the PCF can execute the business data flow processing methods shown in Figures 4 and 6; another example is that an electronic device can be an AF, in which case the AF can execute the business data flow processing methods shown in Figures 7 and 8.

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

[0135] 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 method of processing a service data flow, characterized by, The method comprises the following steps: If multiple service data streams need to meet synchronization requirements during transmission, processing strategy information of the multiple service data streams is generated according to the synchronization requirements, the processing strategy information is used to provide transmission synchronization of the multiple service data streams, and a first policy of configuring first quality of service (QoS) processing related information is configured. The processing strategy information is sent to a session management function network element.

2. The method of claim 1, wherein, The method further comprises the following steps: Synchronization requirements of multiple service data streams sent by an application function network element are received, the synchronization requirements are used to indicate that the multiple service data streams need to meet synchronization requirements during transmission. It is determined that the multiple service data streams need to meet synchronization requirements during transmission according to the synchronization requirements.

3. The method according to claim 1 or 2, characterized in that, The method further comprises the following steps: If it is determined that the multiple service data streams are transmitted through a same protocol data unit (PDU) session, it is determined that the multiple service data streams need to meet synchronization requirements during transmission.

4. The method according to any one of claims 1 to 3, characterized in that, The processing strategy information of the multiple service data streams is generated, comprising the following steps: Processing strategy information of the multiple service data streams when the multiple service data streams are mapped to different QoS streams for processing is generated, the processing strategy information is used to indicate that different QoS streams obtained by mapping of the multiple service data streams need to meet synchronization requirements.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises the following steps: Synchronization monitoring strategy information of the multiple service data streams is generated, the synchronization monitoring strategy information is used to provide a second policy of configuring second QoS processing related information to monitor synchronization of the multiple service data streams; The synchronization monitoring strategy information is sent to a session management function network element.

6. The method of claim 5, wherein, The synchronization monitoring strategy information of the multiple service data streams is generated, comprising the following steps: Synchronization monitoring requirements for the service data streams sent by an application function network element are received, and the synchronization monitoring strategy information of the multiple service data streams is generated according to the synchronization monitoring requirements.

7. The method according to claim 5 or 6, characterized in that, After the monitoring strategy information is sent to a session management function network element, the method further comprises at least one of the following steps: Synchronization monitoring results reported by an access network element are received; Synchronization monitoring results reported by other core network elements are received.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises the following steps: Quality of service parameters of the multiple service data streams are adjusted according to synchronization requirements and end-to-end delay requirements of the multiple service data streams and transmission delay of the multiple service data streams in a core network.

9. A method of processing a service data flow, characterized by, The method comprises the following steps: Synchronization requirements between multiple service data streams are generated, the synchronization requirements are used to indicate that the multiple service data streams need to meet synchronization requirements during transmission, and the synchronization requirements are used to generate processing strategy information of the multiple service data streams, the processing strategy information is used to provide transmission synchronization of the multiple service data streams, and a first policy of configuring first quality of service (QoS) processing related information is configured. The synchronization requirements are provided to a core network element.

10. The method of claim 9, wherein, The method further comprises the following steps: Synchronization monitoring requirements for the multiple service data streams are generated, the synchronization monitoring requirements are used to indicate that transmission synchronization of the multiple service data streams is monitored to determine whether the multiple service data streams can meet synchronization requirements during transmission; The synchronization monitoring requirements are provided to a core network element. providing the synchronism monitoring requirement to a core network element.

11. The method according to claim 9 or 10, characterized in that, After providing the synchronism monitoring requirement to a core network element, the method further comprises at least one of the following steps: receiving a synchronism monitoring result reported by an access network element; receiving a synchronism monitoring result reported by another core network element.

12. An apparatus for processing a service data stream, characterized by comprising: comprising: a generating unit, configured to determine that a plurality of service data flows need to meet a synchronism requirement when being transmitted, and to generate processing strategy information of the plurality of service data flows according to the synchronism requirement, the processing strategy information being used to provide transmission synchronism for the plurality of service data flows and configure a first policy of first quality of service (QoS) processing related information; a sending unit, configured to send the processing strategy information to a session management function network element.

13. An apparatus for processing a service data stream, characterized by comprising: comprising: a generating unit, configured to generate a synchronism requirement between a plurality of service data flows, the synchronism requirement being used to indicate that the plurality of service data flows need to meet a synchronism requirement when being transmitted, and to generate processing strategy information of the plurality of service data flows, the processing strategy information being used to provide transmission synchronism for the plurality of service data flows and configure a first policy of first quality of service (QoS) processing related information; a sending unit, configured to provide the synchronism requirement to a core network element.

14. A computer readable medium having stored thereon a computer program, characterized in that, The computer program is executed by a processor to implement the processing method of the service data flow in any one of claims 1 to 11.

15. An electronic device, comprising: comprising: one or more processors; a memory, used to store one or more computer programs, when the one or more computer programs are executed by the one or more processors, the electronic device implements the processing method of the service data flow in any one of claims 1 to 11.

16. A computer program product, characterised in that, The computer program product comprises a computer program stored in a computer readable storage medium, and a processor of an electronic device reads and executes the computer program from the computer readable storage medium, so that the electronic device executes the processing method of the service data flow in any one of claims 1 to 11.

Images