WO2026026751A1 - 业务数据流的处理方法、装置、计算机可读介质及设备 - Google Patents

业务数据流的处理方法、装置、计算机可读介质及设备

Info

Publication number
WO2026026751A1
WO2026026751A1 PCT/CN2025/111071 CN2025111071W WO2026026751A1 WO 2026026751 A1 WO2026026751 A1 WO 2026026751A1 CN 2025111071 W CN2025111071 W CN 2025111071W WO 2026026751 A1 WO2026026751 A1 WO 2026026751A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
data streams
synchronization
multiple service
processing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/111071
Other languages
English (en)
French (fr)
Inventor
雷艺学
贾宇航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology (Shenzhen) Co Ltd
Original Assignee
Tencent Technology (Shenzhen) Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology (Shenzhen) Co Ltd filed Critical Tencent Technology (Shenzhen) Co Ltd
Publication of WO2026026751A1 publication Critical patent/WO2026026751A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes

Definitions

  • 5G-Generation 5G-Generation
  • 5G-A 5G-Advanced
  • 6G-Advanced 6G
  • 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.
  • 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.
  • different media type service flows may be mapped to different Quality of Service (QoS) flows.
  • 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 multi-media service flows.
  • 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.
  • QoS quality of service
  • 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.
  • 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
  • QoS quality of service
  • 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.
  • QoS quality of service
  • 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 described in the above embodiments.
  • 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.
  • 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.
  • a core network element 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 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 to the processing devices of the multiple service data streams according to the processing strategy information. Therefore, the technical solutions of this application enable the core network element to generate processing strategy information for multiple service data streams when they need to meet synchronization requirements. This allows 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.
  • 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;
  • Figure 3 illustrates a schematic diagram of data transmission via multiple QoS streams according to an embodiment of this application
  • Figure 4 shows a flowchart of a business data flow processing method according to an embodiment of this application
  • Figure 5 shows a schematic diagram of a key network element architecture for a 5G network.
  • Figure 6 shows a flowchart of a business data flow processing method according to an embodiment of this application
  • Figure 8 shows a flowchart of a business data flow processing method according to an embodiment of this application.
  • Figure 9 shows a flowchart of a business data flow processing method according to an embodiment of this application.
  • Figure 10 shows a flowchart of a business data flow processing method according to an embodiment of this application.
  • Figure 11 shows a block diagram of a processing apparatus for a business data stream according to an embodiment of this application
  • Figure 12 shows a block diagram of a processing apparatus for a business data stream according to an embodiment of this application
  • Figure 13 shows a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application.
  • 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.
  • module refers 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.
  • a processor or multiple processors or memory
  • each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.
  • 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.
  • 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, and head-mounted displays.
  • the game client can be an application running on a terminal device.
  • the game client can decode the encoded data transmitted by cloud server 101 to obtain analog audio and video signals, and then play them.
  • 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.
  • 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 (CDN), 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.
  • 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.
  • CN core network
  • RAN radio access network
  • UE user interface
  • application layer an application layer
  • the radio access network is responsible for connecting user equipment to a network (such as the Internet) and handling data transmission.
  • the RAN may include base stations (Next-Generation NodeBs, gNBs).
  • 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.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • 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, and also handles UE 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 and Session Management Policy Control.
  • the User Data Management Function (UDM) is responsible for the unified management of user data, including user identity, subscription information, and authentication data. It is the central storage and management point for user data in the 5G network.
  • 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.
  • 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.
  • PDU Protocol Data Unit
  • 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.
  • 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.
  • IP Internet Protocol
  • 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 Service Data Adaptation Protocol.
  • multimedia services such as XRM services
  • multimedia services such as XRM services
  • the data formed by a single multimedia service frame or a 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.
  • Multimedia services typically include multiple media types in their service flows, such as audio, video, haptic, or other media types.
  • different media type service flows between the user equipment and the application server may be mapped to different Quality of Service (QoS) flows.
  • 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.
  • RAN Radio Access Network
  • 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.
  • FIG. 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.
  • PCF Policy Control Function
  • the service data flow processing method may include steps S410 to S420.
  • 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.
  • QoS Quality of Service
  • a service data flow 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.
  • 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.
  • 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.
  • the processing method of the service data stream shown in Figure 4, executed by the PCF is used as an example for illustration.
  • 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.
  • the processing strategy information for multiple service data streams can refer to processing strategy information corresponding to multiple service data streams.
  • One processing strategy information entry can be applied to one or more service data streams.
  • 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.
  • 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.
  • PDU Protocol Data Unit
  • TEIDs Tunnel Endpoint IDs
  • processing policy information 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.
  • 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.
  • 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.
  • 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.
  • 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 flow or through the Session Management (SM) Policy Association Modification signaling flow, and then the PCF sending the relevant processing policy information to the SMF through the Session Management Policy Context Data IE.
  • SM Session Management
  • SM Session Management
  • the processing equipment for the service data stream may include a UPF, a base station device, and/or a user equipment.
  • 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 a first QoS profile 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 profile to the base station.
  • the SMF can generate a first QoS 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 QoS rule to the UE.
  • Figure 5 shows the key network element architecture of a 5G network defined by the 3rd Generation Partnership Project (3GPP).
  • the core network elements include Access and Mobility Management Function (AMF), SMF, UPF, PCF, Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), and Unified Data Management (UDM).
  • the UE can be a 5G terminal such as a mobile phone or tablet.
  • the (R)AN Radio Access Network
  • DN Data Network
  • AS application server
  • 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, and carry 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.
  • (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 AUSFs via interface N12.
  • AUSFs interact with UDMs via interface N13.
  • 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.
  • the service data stream processing method may include steps S610 and S620 in addition to steps S410 to S420.
  • 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.
  • the synchronization monitoring strategy information for multiple service data streams may refer to synchronization monitoring strategy information corresponding to multiple service data streams.
  • One synchronization monitoring strategy information entry may correspond to one or more service data streams.
  • 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.
  • 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.
  • 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.
  • 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.
  • the processing equipment for service data streams may include UPF, base station equipment, and/or user equipment.
  • 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.
  • 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.
  • 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 be used 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.
  • PSDB PDU Set Delay Budget
  • PSER PDU Set Error Rate
  • MDBV Maximum Data Burst Volume
  • PV Packet Delay Variation
  • the PCF can adjust the PDB on the access network side or the PDB on the core network side.
  • FIG. 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.
  • the service data stream processing method may include steps S710 to S720.
  • 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.
  • QoS Quality of Service
  • 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.
  • 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.
  • trusted/untrusted for example refers to being trusted/untrusted from the perspective of the PCF.
  • the service data stream processing method may include steps S810 and S820 in addition to steps S710 to S720.
  • step S810 a synchronization monitoring requirement for the business data stream is generated.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the PCC rule generated during the PDU session establishment phase includes the synchronization requirements for multiple QoS flows, which can be indicated individually, for example, by the AF (Automatic Front-End). 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 based on the PCC rules.
  • 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).
  • SDFs Service Data Flows
  • 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.
  • 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.
  • processing policy information the first PCC rules
  • step S903 the 5GC configures the first PCC rule supporting multi-QoS stream synchronization transmission to the UPF, RAN, and/or UE.
  • 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.
  • 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.
  • 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.
  • 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.
  • the steps include the following:
  • 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.
  • 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.
  • step S1002 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.
  • the 5GC configures the second policy information supporting multi-QoS flow synchronization monitoring to the UPF, RAN, and/or UE.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • QoS parameters such as adjusting the PSDB or PDB
  • 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).
  • the total latency within 5GC should be less than T0-T1, and the latency jitter should be limited to a certain range.
  • the technical solution of this application can solve the problem from an end-to-end perspective that after multimedia service streams 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.
  • 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.
  • 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.
  • the service data stream processing apparatus 1100 includes: a generation unit 1102 and a transmission unit 1104.
  • 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.
  • QoS quality of service
  • 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.
  • 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.
  • 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.
  • PDU Protocol Data Unit
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a service data stream processing apparatus 1200 includes: a generation unit 1202 and a transmission unit 1204.
  • the generation unit 1202 is configured to generate synchronization requirements among multiple service data streams. These synchronization requirements indicate that the multiple service data streams need to meet synchronization requirements during transmission. It 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, enabling the core network elements to 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • I/O interface 1305 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.
  • 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.
  • the computer program can be downloaded and installed from a network via communication section 1309, and/or installed from removable medium 1311.
  • CPU central processing unit
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a non-volatile storage medium such as a CD-ROM, USB flash drive, external hard drive, etc.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请的实施例提供了一种业务数据流的处理方法、装置、计算机可读介质及设备。该业务数据流的处理方法包括：若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息；将所述处理策略信息发送给会话管理功能网元，以使所述会话管理功能网元根据所述处理策略信息向所述多个业务数据流的处理设备配置服务质量QoS处理相关信息。

Description

业务数据流的处理方法、装置、计算机可读介质及设备
本申请要求于2024年08月01日提交的申请号为202411053106.8、发明名称为“业务数据流的处理方法、装置、计算机可读介质及设备”的中国专利申请的优先权。
技术领域
本申请涉及计算机及通信技术领域，具体而言，涉及一种业务数据流的处理方法、装置、计算机可读介质及设备。
背景技术
在第五代移动通信技术(5th-Generation，5G)及其后续演进系统(如5G-A(5G-Advanced)、6G等)中，高带宽的交互型业务是重要的业务类型，诸如云游戏(Cloud gaming)、虚拟现实(Virtual Reality，VR)、增强现实(Augmented Reality，AR)、混合现实(Mixed Reality，MR)、扩展现实(Extended Reality，XR)、影像现实(Cinematic Reality，CR)、XR和媒体服务(XR and Media Services，XRM)等。
这些高带宽的交互型业务不仅对传输时效性要求很高，而且这种业务的业务流通常会包含多种媒体类型，比如音频(audio)、视频(video)和触觉(haptic)或其它媒体类型。在进行传输时，不同媒体类型的业务流可能会映射到不同的服务质量(Quality of Service，QoS)流(flow)上，而不同的QoS flow在传输时可能会有不同的时延，进而可能造成接收端在根据接收到的多种媒体类型的业务流生成媒体内容进行播放时，出现不同媒体类型的业务数据不同步的问题。
发明内容
本申请的实施例提供了一种业务数据流的处理方法、装置、计算机可读介质及设备。
本申请实施例提供了一种业务数据流的处理方法，包括：若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；将所述处理策略信息发送给会话管理功能网元。
本申请实施例提供了一种业务数据流的处理方法，包括：生成多个业务数据流之间的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求，并且用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；将所述同步性需求提供给核心网网元。
本申请实施例提供了一种业务数据流的处理装置，包括：生成单元，配置为若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；发送单元，配置为将所述处理策略信息发送给会话管理功能网元。
本申请实施例提供了一种业务数据流的处理装置，包括：生成单元，配置为生成多个业务数据流之间的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求，并且用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；发送单元，配置为将所述同步性需求提供给核心网网元。
本申请实施例提供了一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如上述实施例中所述的业务数据流的处理方法。
本申请实施例提供了一种电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个计算机程序，当所述一个或多个计算机程序被所述一个或多个处理器执行时，使得所述电子设备实现如上述实施例中所述的业务数据流的处理方法。
本申请实施例提供了一种计算机程序产品，该计算机程序产品包括计算机程序，该计算机程序存储在计算机可读存储介质中。电子设备的处理器从计算机可读存储介质读取并执行该计算机程序，使得该电子设备执行上述各种示例实施例中提供的业务数据流的处理方法。
在本申请的一些实施例所提供的技术方案中，核心网网元在确定多个业务数据流在传输时需要满足同步性要求时，可以根据该同步性需求生成多个业务数据流的处理策略信息，然后将该处理策略信息发送给会话管理功能网元，以使会话管理功能网元根据该处理策略信息向多个业务数据流的处理设备配置QoS处理相关信息。可见，本申请实施例的技术方案使得核心网网元可以在多个业务数据流需要满足同步性要求时，生成多个业务数据流的处理策略信息，进而可以使得这多个业务数据流在传输过程中可以根据该处理策略信息实现差异尽可能小的或同等的传输延迟，改善了不同的业务数据流映射得到的QoS flow有不同的时延或时延差异过大而导致播放内容不同步的问题，有利于提升用户对于多媒体业务的使用体验。
附图说明
图1示出了可以应用本申请实施例的技术方案的示例性系统架构的示意图；
图2示出了本申请实施例的多媒体数据包的传输过程示意图；
图3示出了根据本申请实施例的通过多个QoS流进行数据传输的示意图；
图4示出了本申请实施例的业务数据流的处理方法的流程图；
图5示出了一种5G网络重点网元架构示意图；
图6示出了本申请实施例的业务数据流的处理方法的流程图；
图7示出了本申请实施例的业务数据流的处理方法的流程图；
图8示出了本申请实施例的业务数据流的处理方法的流程图；
图9示出了本申请实施例的业务数据流的处理方法的流程图；
图10示出了本申请实施例的业务数据流的处理方法的流程图；
图11示出了根据本申请实施例的业务数据流的处理装置的框图；
图12示出了根据本申请实施例的业务数据流的处理装置的框图；
图13示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
具体实施方式
现在参考附图以更全面的方式描述示例实施方式。然而，示例的实施方式能够以各种形式实施，且不应被理解为仅限于这些范例。
此外，本申请所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，有许多具体细节从而可以充分理解本申请的实施例。然而，本领域技术人员应意识到，在实施本申请的技术方案时可以不需用到实施例中的所有细节特征，可以省略一个或更多特定细节，或者可以采用其它的方法、元件、装置、步骤等。
本申请实施例中，术语“模块”或“单元”是指有预定功能的计算机程序或计算机程序的一部分，并与其它相关部分一起工作以实现预定目标，并且可以通过使用软件、硬件(如处理电路或存储器)或其组合来全部或部分实现。同样的，一个处理器(或多个处理器或存储器)可以用来实现一个或多个模块或单元。此外，每个模块或单元都可以是包含该模块或单元功能的整体模块或单元的一部分。
附图中所示的方框图仅仅是功能实体，不一定必须与物理上独立的实体相对应。例如，可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
附图中所示的流程图仅是示例性说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解，而有的操作/步骤可以合并或部分合并，因此实际执行的顺序有可能根据实际情况改变。
在本文中提及的“多个”是指两个或两个以上。“和/或”描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
随着5G及其后续演进系统(如5G-A、6G等)的发展，使得许多要求多数据量、短时延的多媒体业务得到了应用。比如云游戏业务、VR、AR、MR、XR、CR等交互业务。
例如，在图1所示的云游戏场景中，云端服务器101用于运行云游戏，云端服务器101可以对游戏画面进行渲染，并将音频信号及渲染后的图像进行编码处理，最后将编码处理得到的编码数据通过网络传输至各个游戏客户端。游戏客户端可以是具有基本的流媒体播放能力、人机交互能力以及通信能力等的用户设备(User Equipment，UE)，例如，智能手机、平板电脑、笔记本电脑、台式计算机、智能电视、智能家居、车载终端、飞行器、头戴设备等。或者该游戏客户端可以是运行于终端设备中的应用程序。例如，游戏客户端可以将云端服务器101传输的编码数据进行解码，得到模拟音视频信号，并进行播放。
应理解的是，图1中只是示例性的表征云游戏系统的系统架构，并不对云游戏系统的具体架构进行限定；例如在其它实施例中，云游戏系统中还可包括用于调度的后台服务器等等。并且云端服务器101可以是独立的物理服务器，也可以是多个物理服务器构成的服务器集群或者分布式系统，还可以是提供云服务、云数据库、云计算、云函数、云存储、网络服务、云通信、中间件服务、域名服务、安全服务、内容分发网络(Content Delivery Network，CDN)、以及大数据和人工智能平台等基础云计算服务的云服务器。游戏客户端以及云端服务器101可以通过有线或无线通信方式进行直接或间接地连接，本申请在此不做限制。
在上述的各种基于多媒体的交互业务应用场景中，由于即使是单个多媒体业务帧或者GoP(Group of Packets，数据包组)，也可能字节量比较大，因此在传输时需要拆分为多个数据包进行传输。
具体而言，如图2所示，以5G系统为例。5G通信网络通常包括核心网(Core Network,CN)、无线接入网(Radio Access Network,RAN)、传输网、UE、应用层等。
无线接入网负责将用户设备连接到网络(例如互联网)，并处理数据传输。无线接入网可包括基站(Next-Generation NodeB，gNB)。
核心网例如包括用户面功能(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)等等。
UPF负责处理用户设备与网络之间的数据传输，包括数据包的转发、路由和QoS(服务质量)管理。UPF还负责处理数据包的加密和解密等功能。AMF负责处理与用户设备的接入、移动性管理和会话管理。AMF负责与用户设备的认证、鉴权和密钥管理，同时也负责处理用户设备的位置更新、会话建立和释放等功能。SMF负责管理用户设备的数据传输会话，包括会话的建立、维护和释放。SMF还负责管理数据传输策略，确保数据传输的高效性和可靠性。PCF提供了接入移动性策略控制(Access and Mobility Policy Control)和会话管理策略控制(Session Management Policy Control)。UDM负责统一管理用户数据，包括用户身份、订阅信息、认证数据等。它是5G网络中用户数据的中央存储和管理点。
如图2所示，用户面例如包括应用服务器、UPF、基站和UE。用户面负责用户数据的传输。多媒体数据包的传输对于一些典型业务场景可以是在下行方向，比如从应用服务器(Application Server，AS)到UPF，然后再通过gNB发送给UE。在进行传输时，多媒体数据包(在图2中以XR数据包I、P为例)在应用服务器的应用层进行拆分。拆分后的子数据包(子数据包I1,I2…和子数据包P1,P2…)作为IP包从应用服务器到达UPF后，5G系统通过协议数据单元(Protocol Data Unit，PDU)会话把子数据包传输到UE端。在UE端将子数据包从协议栈逐级向上递交并进行重组恢复出该多媒体数据包。UE端的协议栈自下而上包括PHY层、MAC层、RLC层、PDCP层、SDAP层、IP层。
其中，在图2所示的系统中，L1层是指物理层，其用于确保原始的数据可在各种物理媒体上传输。L2层指的是数据链路层，数据链路层在物理层提供的服务的基础上向网络层提供服务。网际互联协议(Internet Protocol，IP)层即为网络层，用于实现两个端系统之间的数据传送。UDP即为User Datagram Protocol，用户数据报协议。GTP-U即为GPRS(General packet radio service，通用分组无线业务)Tunneling Protocol，通用分组无线业务隧道协议用户面。PHY即为Physical的简称，物理层。MAC即为Media Access Control，媒体访问控制；RLC即为Radio Link Control，无线链路控制层协议。PDCP即为Packet Data Convergence Protocol，分组数据汇聚协议。SDAP即为Service Data Adaptation Protocol，服务数据适配协议。
如前所述，对多媒体业务(比如XRM业务)来说，把一帧多媒体数据通过多个数据包传输是很常见的情况。单个多媒体业务帧或者数据包组(Group of Packets，GoP)形成的数据可以由一系列IP数据包来承载。这些IP数据包之间存在一定的相关性，根据相关性来处理这些IP数据包能够有效节省无线网络带宽。举例来说，假设在进行传输时通过多个IP数据包进行传输，这多个IP数据包可以组成PDU set(PDU集合)。
多媒体业务(比如XRM业务)的业务流通常会包含多种媒体类型，比如音频(audio)、视频(video)和触觉(haptic)或其它媒体类型。如图3所示，在进行传输时，为了保障服务质量，用户设备与应用服务器之间的不同媒体类型的业务流可能会映射到不同的服务质量(Quality of Service，QoS)流(flow)上，而不同的QoS flow在传输时可能会有不同的时延，比如，在无线接入网(Radio Access Network，RAN)与UPF之间传输的时延，进而可能造成接收端(例如，用户设备)在根据接收到的多种媒体类型的业务流，生成媒体内容进行播放时，出现不同媒体类型的业务数据不同步的问题。
基于上述问题，本申请实施例提出了一种新的业务数据流的处理方案，使得核心网可以在多个业务数据流需要满足同步性要求时，生成多个业务数据流的处理策略信息，进而可以使得这多个业务数据流在传输过程中可以根据该处理策略信息实现差异尽可能小的或同等的传输延迟，改善了不同的业务数据流映射得到的QoS flow有不同的时延或时延差异过大而导致播放内容不同步的问题，有利于提升用户对于多媒体业务的使用体验。
以下对本申请实施例的技术方案的实现细节进行详细阐述。
图4示出了根据本申请实施例的业务数据流的处理方法的流程图。该业务数据流的处理方法可以由策略控制功能(Policy Control Function，PCF)网元来执行，或者也可以由其它网元来执行。参照图4所示，该业务数据流的处理方法可以包括步骤S410至步骤S420。
在步骤S410中，若多个业务数据流在传输时需要满足同步性要求，则根据该同步性需求，生成多个业务数据流的处理策略信息。所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略。
业务数据流(service data flow，SDF)可以是一组数据包，或一个或多个IP数据流。具有相同源IP地址、目的IP地址、源端口、目的端口以及协议ID的一个或多个IP数据流可以被指定为一个业务数据流。业务数据流可以是多媒体业务的业务数据流。多媒体业务比如可以是云游戏业务、VR业务、AR业务、MR业务、XR业务、XRM业务、CR业务等。业务数据流可以采用业务数据包集合(PDU set)的方式进行传输。这是由于如果单个多媒体业务帧或者GoP形成一个数据包，则可能字节量比较大，因此，需要拆分为一系列的数据包来进行承载。这些一系列的数据包之间具有一定的相关性，因此可以将这些具有相关性的数据包称之为PDU set。在本申请的其它实施例中，业务数据流也可以采用逐个业务数据包(per-packet)的方式进行传输。
在一些示例实施例中，多个业务数据流可以是不同媒体类型的业务数据流，比如媒体类型可以包括音频(audio)、视频(video)和触觉(haptic)或其它媒体类型等。不同媒体类型的业务数据流可能具有不同的QoS需求信息，也可能具有相同的QoS需求信息。这多个业务数据流在传输时可以映射到同一个QoS流上，也可以映射到不同的QoS流上。比如，若这多个不同媒体类型的业务数据流具有不同的QoS需求信息，那么这些不同媒体类型的业务数据流可以映射到不同的QoS流上进行传输。
以云游戏业务为例。云游戏业务中可能包含有音频类型的第一业务数据流、视频类型的第二业务数据流，也可能包含有触觉或其它类型的第三业务数据流等，这三种媒体类型的业务数据流关联至同一个多媒体业务。因此在进行传输时，如果这三个业务数据流被映射到不同的QoS流上，那么这些QoS流是存在关联关系的，比如，这些QoS流之间存在同步性要求。同步性要求是指这些QoS流之间的延迟信息应该保持一致或者处于一定的时延范围内。与同一个多媒体业务关联的多个业务数据流可以包含相同的业务ID、相同的会话ID、相同的UE地址等中的一个或多个标识符，或关联有相同的描述信息。
在一些示例实施例中，以图4所示的业务数据流的处理方法由PCF执行为例进行说明。PCF可以接收应用功能(Application Function，AF)网元发送的多个业务数据流的同步性需求，该同步性需求用于指示多个业务数据流在传输时需要满足同步性要求。进而PCF可以根据该同步性要求来生成多个业务数据流的处理策略信息。在本申请各种实施例中，多个业务数据流的处理策略信息可以是指多个业务数据流对应的处理策略信息。处理策略信息可以为一条或多条。一条处理策略信息可以应用于一个或多个业务数据流。
在一些示例实施例中，若确定所述多个业务数据流通过同一个协议数据单元(PDU)会话传输，则确定所述多个业务数据流在传输时需要满足同步性要求。例如，PCF也可以将通过同一个PDU会话所传输的多个业务数据流，作为需要满足同步性要求的业务数据流。或者说，PCF可以将同一个PDU会话中所传输的多个业务数据流识别为具有同步性要求的业务数据流。同一个PDU会话传输的多个业务数据流可通过相关联的PDU会话ID和/或隧道端点标识(Tunnel Endpoint ID，TEID)等判断。
在一些示例实施例中，在生成多个业务数据流的处理策略信息时，可以根据多个业务数据流的同步性需求，生成多个业务数据流在映射到不同的QoS流上进行处理时的处理策略信息。该处理策略信息用于指示多个业务数据流映射得到的不同QoS流需要满足同步性要求。换句话说，多个业务数据流可以映射到不同的QoS流上，这样可以得到多个QoS流，PCF可以生成针对这多个QoS流的处理策略信息。例如，针对这多个QoS流中的每个QoS流，生成一条处理策略信息，或者，多个QoS流的数量和处理策略信息不是一一对应。
继续参照图4所示，在步骤S420中，将处理策略信息发送给会话管理功能网元。会话管理功能网元根据处理策略信息向多个业务数据流的处理设备配置QoS处理(或称为第一QoS处理)的相关信息。
在一些示例实施例中，PCF将处理策略信息发送给会话管理功能(Session Management Function，SMF)网元的过程可以包括：PCF与SMF通过会话管理策略关联建立(Session Management(SM)Policy Association Establishment)信令流程进行交互，或者通过会话管理策略关联修改(SM Policy Association Modification)信令流程进行交互，然后PCF通过会话管理策略上下文数据信息元素(SM Policy Context Data IE)将相关的处理策略信息发送给SMF。
在一些示例实施例中，业务数据流的处理设备可以包含UPF、基站设备和/或用户设备。示例地，SMF可以根据业务数据流的处理策略信息生成第一N4规则，其中包含有多个QoS流需要满足同步性要求等规则，然后将第一N4规则发送给UPF。SMF可以根据业务数据流的处理策略信息生成第一QoS配置文件(QoS Profiles)，其中包含有多个QoS流需要满足同步性要求等信息，然后将第一QoS Profiles发送给基站。SMF可以根据业务数据流的处理策略信息生成第一QoS规则(QoS rules)，其中包含有多个QoS流需要满足同步性要求等规则，然后将第一QoS rules发送给UE。
以5G系统为例。如图5所示是第三代合作伙伴计划(The 3rd Generation Partnership Project，3GPP)组织定义的5G网络重点网元架构。在5G系统中，接入与移动性管理功能(Access and Mobility Management Function，AMF)、SMF、UPF、PCF、网络切片选择功能(Network Slice Selection Function，NSSF)、认证服务器功能(Authentication Server Function，AUSF)、统一数据管理功能(Unified Data Management，UDM)等为5G网络核心网网元。UE可以是手机、平板电脑等5G终端。(R)AN((Radio)Access Network，(无线)接入网))可以是5G基站。DN(Data Network)为数据网络，即UE访问的业务服务器(Application Server，AS)。
其中，AMF负责终结基站控制面的N2接口，并基于流控制传输协议(Stream Control Transmission Protocol，SCTP)协议实现下一代应用协议(Next Generation Application Protocol，NGAP)的编解码。基站与AMF通过SCTP传输层协议传输应用层NGAP协议，并在NGAP中承载UE的非接入层(Non-Access Stratum，NAS)信令数据。AMF同时也负责终结UE的N1接口，实现NAS的加密和完整性保护，并负责UE接入验证、授权管理、注册、连接、可达性和移动管理等功能，以及负责UE与SMF之间会话管理消息的透传。
另外，(R)AN与UPF之间通过N3接口交互。UPF之间可以通过N9接口交互。UPF与SMF之间通过N4接口交互。UPF与DN之间通过N6接口交互。SMF与AMF之间通过N11接口交互。SMF与PCF之间通过N7接口交互。SMF与UDM之间通过N10接口交互。PCF与应用功能(Application Function，AF)之间通过N5接口交互。AMF之间可以通过N14接口交互。AMF与PCF之间通过N15接口交互。AMF与UDM之间通过N8接口交互。AMF与NSSF之间通过N22接口交互。AMF与AUSF之间通过N12接口交互。AUSF与UDM之间通过N13接口交互。
基于图5所示的系统架构，SMF可以将生成的第一及其它N4规则通过N4接口配置给UPF，通过AMF向(R)AN配置第一及其它QoS Profiles，和/或通过AMF+NAS连接向UE配置第一及其它QoS rules。
基于图4所示实施例的技术方案，参照图6所示，在本申请的实施例中，业务数据流的处理方法除了包括步骤S410至步骤S420之外，还可以包括步骤S610和步骤S620。
在步骤S610中，生成多个业务数据流的同步性监测策略信息。所述同步性监测策略信息用于提供配置第二QoS处理相关信息，以对所述多个业务数据流的同步性进行监测的第二策略。在本申请各种实施例中，多个业务数据流的同步性监测策略信息可以指多个业务数据流对应的同步性监测策略信息。同步性监测策略信息可以为一条或多条。一条同步性监测策略信息可以与一个或多个业务数据流对应。
在一些示例实施例中，PCF可以作为业务数据流或QoS流同步性监测的消费者，那么PCF可以根据自身的需求来生成多个业务数据流对应的同步性监测策略信息。例如，若PCF确定多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息。或者PCF也可以接收应用功能网元发送的针对业务数据流的同步性监测需求，该同步性监测需求用于指示对多个业务数据流的传输同步性进行监测，那么PCF可以根据该同步性监测需求生成多个业务数据流对应的同步性监测策略信息。
在步骤S620中，将同步性监测策略信息发送给会话管理功能网元。会话管理功能网元可以根据同步性监测策略信息，向多个业务数据流的处理设备配置QoS处理相关信息，以对多个业务数据流的同步性进行监测。
在一些示例实施例中，PCF将同步性监测策略信息发送给SMF网元的过程可以包括：PCF与SMF通过会话管理策略关联建立信令流程进行交互，或者通过会话管理策略关联修改信令流程进行交互，然后PCF通过会话管理策略上下文数据信息元素，将同步性监测策略信息发送给SMF。
类似地，业务数据流的处理设备可以包含UPF、基站设备和/或用户设备。示例地，SMF可以根据同步性监测策略信息生成第二N4规则，其中包含有多个QoS流的同步性监测要求等信息，然后将第二N4规则发送给UPF。SMF可以根据同步性监测策略信息生成第二QoS配置文件(QoS Profiles)，其中包含有多个QoS流的同步性监测要求等信息，然后将第二QoS Profiles发送给基站。SMF可以根据同步性监测策略信息生成第三QoS rules，其中包含有多个QoS流的同步性监测要求等，然后将第三QoS rules发送给UE。
在一些示例实施例中，PCF在将监测策略信息发送给会话管理功能网元之后，还可以接收接入网网元(如基站)上报的同步性监测结果，也可以接收其它核心网网元上报的同步性监测结果。接入网网元上报的同步性监测结果可以是Uu口的同步性监测结果；其它核心网网元比如可以是UPF，那么UPF上报的同步性监测结果可以是N3或者N9接口的同步性监测结果。
在一些示例实施例中，PCF还可以根据多个业务数据流的端到端延迟要求和同步性要求，以及多个业务数据流在核心网内部的传输延迟来调整业务数据流的QoS参数信息。调整后的业务数据流的QoS参数信息可以作为业务数据流的处理策略信息。比如，若业务数据流在通过PDU集合的方式进行传输时，可以调整PDU集合延迟预算(PDU Set Delay Budget，PSDB)、PDU集合误码率(PDU Set Error Rate，PSER)、最大数据突发量(Maximum Data Burst Volume，MDBV)、包时延变化/抖动(Packet Delay Variation，PDV)等参数中的一个或者多个。若业务数据流在采用单个数据包(per-packet)的方式进行传输时，可以调整数据包延迟预算(Packet Delay Budget，PDB)、数据包丢包率(Packet Error Rate，PER)、最大数据突发量等参数中的一个或多个。
以调整PDB为例进行说明。PCF可以调整接入网侧的PDB，也可以调整核心网侧的PDB。
以上从PCF的角度对本申请实施例的技术方案进行了说明，以下从AF的角度对本申请实施例的技术方案的实现细节进行阐述。
图7示出了根据本申请实施例的业务数据流的处理方法的流程图，该业务数据流的处理方法可以由AF来执行，或者也可以由其它网元来执行。参照图7所示，该业务数据流的处理方法可以包括步骤S710至步骤S720。
在步骤S710中，生成多个业务数据流之间的同步性需求，该同步性需求用于指示多个业务数据流在传输时需要满足同步性要求。该同步性需求还可以用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略。
多个业务数据流的相关说明可以参照前述各种实施例的技术方案，不再赘述。
在步骤S720中，将同步性需求提供给核心网网元。核心网网元可以根据同步性需求生成多个业务数据流的处理策略信息，该处理策略信息用于指示多个业务数据流映射得到的不同QoS流需要满足同步性要求。
AF将多个业务数据流之间同步性需求提供给核心网网元的过程具体可以包括：若AF是可信的，那么AF可以直接将多个业务数据流之间的同步性需求发送给PCF；若AF是不可信的，那么AF可以将多个业务数据流之间的同步性需求发送给NEF，然后由NEF转发给PCF。在本申请各实施例中，AF是可信的/不可信的例如是指对于PCF而言可信的/不可信的。
其中，核心网网元根据同步性需求生成多个业务数据流的处理策略信息的相关描述可以参照前述各种实施例的技术方案，不再赘述。
基于图7所示实施例的技术方案，参照图8所示，在本申请的实施例中，业务数据流的处理方法除了包括步骤S710至步骤S720之外，还可以包括步骤S810和步骤S820。
在步骤S810中，生成针对业务数据流的同步性监测需求。
该同步性监测需求用于指示对多个业务数据流的传输同步性进行监测，以确定多个业务数据流在传输时是否能够满足同步性要求。
在步骤S820中，将同步性监测需求提供给核心网网元。核心网网元可以根据同步性监测需求生成多个业务数据流对应的同步性监测策略信息。
AF将同步性监测需求提供给核心网网元的过程具体可以包括：若AF是可信的，那么AF可以直接将同步性监测需求发送给PCF；若AF是不可信的，那么AF可以将同步性监测需求发送给NEF，然后由NEF转发给PCF。
其中，核心网网元根据同步性监测需求生成多个业务数据流对应的同步性监测策略信息的相关描述可以参照前述各种实施例的技术方案，不再赘述。
在一些示例实施例中，AF在将同步性监测需求提供给核心网网元之后，还可以接收接入网网元(如基站)上报的同步性监测结果，也可以接收其它核心网网元上报的同步性监测结果。例如，接入网网元上报的同步性监测结果可以是Uu口的同步性监测结果。若其它核心网网元比如可以是UPF，那么UPF上报的同步性监测结果可以是N3接口或者N9接口的同步性监测结果。
本申请上述实施例的技术方案使得核心网网元可以在多个业务数据流需要满足同步性要求时，生成多个业务数据流的处理策略信息，进而可以使得这多个业务数据流在传输过程中可以根据该处理策略信息实现差异尽可能小的或同等的传输延迟，改善了不同的业务数据流映射得到的QoS flow有不同的时延或时延差异过大而导致播放内容不同步的问题，有利于提升用户对于多媒体业务的使用体验。
以下以5G系统处理XRM业务为例，对申请实施例的技术方案的实现细节再次进行详细说明。
在本申请实施例中，核心网网元可以根据多个QoS flow之间的同步性要求，生成PCC规则(处理策略信息)，并通过对不同QoS flow之间同步性进行监测，满足多个QoS flow的同步性要求。其中，在PDU会话建立阶段生成的PCC rule中包括了对多个QoS flow的同步性要求，该要求可以单独进行指示，比如由AF指示同步性需求。当然，也可以默认PDU会话中的XRM业务流之间必须满足同步性要求，在这种情况下，不需要单独再进行指示。然后，在相应的控制面网元和用户面网元以及NG-RAN上根据PCC rules去做相应的处理。
以下参照图9所示，以一个具体的示例对本申请实施例的技术方案进行详细阐述，具体包括如下步骤：
步骤S901，当PDU会话建立完成之后(例如，UE通过RAN、UPF、SMF、PCF建立PDU会话)，AF(可以是一个AF或者多个AF)与5GS通过信令交互多个(不同的)业务数据流(Service Data Flow，SDF)之间的同步性要求或同步性需求。通过该步骤，AF可以将所述同步性要求或同步性需求提供给核心网网元。该多个业务数据流包括同一PDU会话以及不同PDU会话之间的业务数据流。示例地，多个业务数据流之间的同步性要求或同步性需求也可以通过隐式的方式来获取到。比如将同一个PDU会话中的多个业务数据流(例如，两个或两个以上)认定为需要满足同步性要求。
步骤S902，根据AF指示，PCF生成相应的第一PCC规则。根据AF交互的(指示的)多个业务数据流的同步性要求，PCF生成多个业务数据流的第一PCC规则。这些第一PCC规则包括了对多个QoS流的同步性要求，这多个QoS流是多个业务数据流映射得到的。在该步骤中，若PCF确定多个业务数据流在传输时需要满足同步性要求，则根据所述同步性要求，生成所述多个业务数据流的处理策略信息(所述第一PCC规则)。然后PCF可以通过SMF将针对UPF、RAN和/或UE的相应规则信息分别配置给UPF、RAN和/或UE。
步骤S903，5GC将支持多QoS流同步性传输的第一PCC规则配置到UPF、RAN和/或UE端。具体来说，PCF在步骤S902生成第一PCC规则之后，可以将第一PCC规则发送到SMF，SMF将结合第一PCC规则生成的第一N4规则配置到UPF，将第一QoS profiles配置到NG-RAN，和/或将第一QoS rules配置到UE。
步骤S904，当来自于AS的下行数据包到达UPF时，UPF根据第一N4规则对多个QoS流的数据进行处理，包括对多个QoS流同步性的支持/处理。
步骤S905，基站根据第一QoS profiles对多个QoS流传输进行处理，以保障多个QoS流的同步性要求。其中基站侧的同步性是指相应QoS流的数据在Uu口的传输时延差异在特定范围内，或者完全相同。
在一些示例实施例中，在PDU会话建立后，可以再通过QoS monitoring机制，监测UPF与NG-RAN、NG-RAN与UE之间的分段时延，然后通过QoS monitoring来确认多个QoS流的同步性。如果这多个QoS流不同步，则可以通过调整多个QoS流的一个或多个QoS参数，如PDB或者PSDB来满足多个QoS流的同步性要求。
具体地，如图10所示，具体包括如下步骤：
步骤S1001，AF(可以是一个AF或者多个AF)与5GS通过信令交互，以指示对多个不同业务数据流之间的同步性进行监测。在该步骤中，AF可以生成针对多个业务数据流的同步性监测需求，所述同步性监测需求用于指示对多个业务数据流的传输同步性进行监测，以确定多个业务数据流在传输时是否能够满足同步性要求，并将所述同步性监测需求提供给5GS的核心网网元。
步骤S1002，根据AF指示，PCF生成相应的第二PCC规则，这些第二PCC规则包括了对多个QoS流的同步性监测要求，这多个QoS流是多个业务数据流映射得到的，然后通过SMF将相应的规则信息配置给UPF、RAN和/或UE。
步骤S1003，5GC将支持多QoS流同步性监测的第二策略信息配置到UPF、RAN和/或UE端。具体来说，PCF生成第二PCC规则，并将其发送到SMF，SMF把结合第二PCC规则生成的第二N4规则配置到UPF，第二QoS profiles配置到NG-RAN，和/或第二QoS rules配置到UE。
步骤S1004，当来自于AS的下行数据包到达UPF时，UPF根据第二N4规则对多个QoS流的数据进行处理，包括对多个QoS流同步性监测的支持。
步骤S1005，基站根据第二QoS profiles对多个QoS流传输进行处理，以保障多个QoS流的同步性监测要求，其中基站侧的同步性是指相应QoS流的数据在Uu口的传输时延差异在特定范围内，或者完全相同。
步骤S1006，RAN以及5GC网元将多QoS流的同步性监测结果汇报给相应的消费者网元，该消费者网元比如可以是AF、或者PCF，也可以是其它网元。
在本申请的一个实施例中，PCF可以根据N6口(即DN/AS与UPF之间)的延迟，以及业务数据流本身的端到端延迟及同步性需求，来调整QoS参数，比如调整PSDB或者PDB等。以调整PDB为例进行说明，PCF可以调整接入网侧的PDB(即AN-PDB)，也可以调整核心网侧的PDB(即CN-PDB)。
举例来说，如果一个业务数据流的端到端延迟需求为T0ms，在N6口的延迟实际为T1ms，则在5GC内部的总时延应小于T0-T1，且时延抖动(jitter)应限定在一定范围内。
综上，本申请实施例的技术方案能够从端到端的角度解决多媒体业务流在映射成多个QoS flow后，由于多个QoS flow之间在5G/6G等移动通信网络中传输出现不同延迟，从而影响到接收端多媒体业务的播放同步，并能够减少对NG-RAN基站的处理负荷。此外，本方案还可以结合N6口的时延变动，使得PCF生成的策略能够在5GS内部对N6口的时延变动进行补偿，更好地适应端到端多媒体业务实时传输条件的变化。
本申请实施例的技术方案不仅适用于5G系统，而且也适用于未来演进的移动通信系统。同时，本申请实施例的技术方案不仅适用于XRM业务，也可以适用于对其它多媒体业务流的处理。
以下介绍本申请的装置实施例，可以用于执行本申请上述实施例中的业务数据流的处理方法。对于本申请装置实施例中未披露的细节，请参照本申请上述的业务数据流的处理方法的实施例。
图11示出了根据本申请实施例的业务数据流的处理装置的框图，该业务数据流的处理装置可以应用于PCF，或者也可以应用于其它网元。
参照图11所示，根据本申请实施例的业务数据流的处理装置1100，包括：生成单元1102和发送单元1104。
其中，生成单元1102配置为若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；发送单元1104配置为将所述处理策略信息发送给会话管理功能网元，以使所述会话管理功能网元根据所述处理策略信息向所述多个业务数据流的处理设备配置服务质量QoS处理相关信息。
在本申请的一些实施例中，基于前述方案，所述生成单元1102还配置为：接收应用功能网元发送的多个业务数据流的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求；根据所述同步性需求，确定所述多个业务数据流在传输时需要满足同步性要求。
在本申请的一些实施例中，基于前述方案，所述生成单元1102还配置为：将通过同一个协议数据单元(PDU)会话所传输的多个业务数据流作为需要满足同步性要求的业务数据流。若确定所述多个业务数据流通过同一个PDU会话传输，则确定所述多个业务数据流在传输时需要满足同步性要求。
在本申请的一些实施例中，基于前述方案，所述生成单元1102配置为：根据所述同步性需求，生成所述多个业务数据流在映射到不同的QoS流上进行处理时的处理策略信息，所述处理策略信息用于指示所述多个业务数据流映射得到的不同QoS流需要满足同步性要求。
在本申请的一些实施例中，基于前述方案，所述生成单元1102还配置为：生成所述多个业务数据流对应的同步性监测策略信息，所述同步性监测策略信息用于提供配置第二QoS处理相关信息，以对所述多个业务数据流的同步性进行监测的第二策略；所述发送单元1104还配置为：将所述同步性监测策略信息发送给会话管理功能网元，以使所述会话管理功能网元根据所述同步性监测策略信息向所述多个业务数据流的处理设备配置QoS处理相关信息，以对所述多个业务数据流的同步性进行监测。
在本申请的一些实施例中，基于前述方案，所述生成单元1102配置为：接收应用功能网元发送的针对所述业务数据流的同步性监测需求，根据所述同步性监测需求，生成所述多个业务数据流对应的同步性监测策略信息。
在本申请的一些实施例中，基于前述方案，所述业务数据流的处理装置1100还包括：接收单元，配置为在将所述监测策略信息发送给会话管理功能网元之后，执行以下过程中的至少一个：接收接入网网元上报的同步性监测结果；接收其它核心网网元上报的同步性监测结果。
在本申请的一些实施例中，基于前述方案，所述业务数据流的处理装置1100还包括：处理单元，配置为根据所述多个业务数据流的同步性要求和端到端延迟要求，以及所述多个业务数据流在核心网的传输延迟，调整所述多个业务数据流的服务质量参数。
图12示出了根据本申请实施例的业务数据流的处理装置的框图，该业务数据流的处理装置可以应用于AF，或者也可以应用于其它网元。
参照图12所示，根据本申请的一个实施例的业务数据流的处理装置1200，包括：生成单元1202和发送单元1204。
其中，生成单元1202配置为生成多个业务数据流之间的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求，并且用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；发送单元1204配置为将所述同步性需求提供给核心网网元，以使所述核心网网元根据所述同步性需求生成所述多个业务数据流的处理策略信息，所述处理策略信息用于指示所述多个业务数据流映射得到的不同QoS流需要满足同步性要求。
在本申请的一些实施例中，基于前述方案，所述生成单元1202还配置为：生成针对所述多个业务数据流的同步性监测需求，所述同步性监测需求用于指示对多个业务数据流的传输同步性进行监测，以确定多个业务数据流在传输时是否能够满足同步性要求；所述发送单元1204还配置为：将所述同步性监测需求提供给核心网网元，以使所述核心网网元根据所述同步性监测需求生成所述多个业务数据流对应的同步性监测策略信息。
在本申请的一些实施例中，基于前述方案，所述业务数据流的处理装置1200还包括：接收单元，配置为在将所述同步性监测需求提供给核心网网元之后，执行以下过程中的至少一个：接收接入网网元上报的同步性监测结果；接收其它核心网网元上报的同步性监测结果。
图13示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图，该电子设备可以是前述实施例中的PCF或者AF。
需要说明的是，图13示出的电子设备的计算机系统1300仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图13所示，计算机系统1300可以包括中央处理单元(Central Processing Unit，CPU)1301，其可以根据存储在只读存储器(Read-Only Memory，ROM)1302中的程序或者从存储部分1308加载到随机访问存储器(Random Access Memory，RAM)1303中的程序而执行各种适当的动作和处理，例如执行上述实施例中所述的方法。在RAM 1303中，还存储有系统操作所需的各种程序和数据。CPU 1301、ROM 1302以及RAM 1303通过总线1304彼此相连。输入/输出(Input/Output，I/O)接口1305也连接至总线1304。
以下部件可以连接至I/O接口1305：包括键盘、鼠标等的输入部分1306；包括诸如阴极射线管(Cathode Ray Tube，CRT)、液晶显示器(Liquid Crystal Display，LCD)等以及扬声器等的输出部分1307；包括硬盘等的存储部分1308；以及包括诸如LAN(Local Area Network，局域网)卡、调制解调器等的网络接口卡的通信部分1309。通信部分1309经由诸如因特网的网络执行通信处理。驱动器1310也根据需要连接至I/O接口1305。可拆卸介质1311，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器1310上，以便于从其上读出的计算机程序根据需要被安装入存储部分1308。
特别地，根据本申请的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序用于执行流程图所示的方法。在这样的实施例中，该计算机程序可以通过通信部分1309从网络上被下载和安装，和/或从可拆卸介质1311被安装。在该计算机程序被中央处理单元(CPU)1301执行时，执行本申请的系统中限定的各种功能。
需要说明的是，本申请实施例所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储计算机程序的有形介质，该计算机程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的计算机程序。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的计算机程序可以用任何适当的介质传输，包括但不限于：无线、有线等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。其中，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机程序的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现，所描述的单元也可以设置在处理器中。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个计算机程序，当上述一个或者多个计算机程序被一个该电子设备执行时，使得该电子设备实现上述实施例中所述的方法。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台电子设备执行根据本申请实施方式的方法。
比如，电子设备可以是PCF，那么PCF可以执行图4和图6所示的业务数据流的处理方法；再如，电子设备可以是AF，那么AF可以执行图7和图8所示的业务数据流的处理方法。
本领域技术人员在考虑说明书及实践这里公开的实施方式后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (16)

  1. 一种业务数据流的处理方法，其特征在于，包括：
    若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；
    将所述处理策略信息发送给会话管理功能网元。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收应用功能网元发送的多个业务数据流的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求；
    根据所述同步性需求，确定所述多个业务数据流在传输时需要满足同步性要求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    若确定所述多个业务数据流通过同一个协议数据单元(PDU)会话传输，则确定所述多个业务数据流在传输时需要满足同步性要求。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，生成所述多个业务数据流的处理策略信息，包括：
    生成所述多个业务数据流在映射到不同的QoS流上进行处理时的处理策略信息，所述处理策略信息用于指示所述多个业务数据流映射得到的不同QoS流需要满足同步性要求。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述方法还包括：
    生成所述多个业务数据流的同步性监测策略信息，所述同步性监测策略信息用于提供配置第二QoS处理相关信息，以对所述多个业务数据流的同步性进行监测的第二策略；
    将所述同步性监测策略信息发送给会话管理功能网元。
  6. 根据权利要求5所述的方法，其特征在于，生成所述多个业务数据流的同步性监测策略信息，包括：
    接收应用功能网元发送的针对所述业务数据流的同步性监测需求，根据所述同步性监测需求，生成所述多个业务数据流的同步性监测策略信息。
  7. 根据权利要求5或6所述的方法，其特征在于，在将所述监测策略信息发送给会话管理功能网元之后，所述方法还包括以下步骤中的至少一个：
    接收接入网网元上报的同步性监测结果；
    接收其它核心网网元上报的同步性监测结果。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述多个业务数据流的同步性要求和端到端延迟要求，以及所述多个业务数据流在核心网的传输延迟，调整所述多个业务数据流的服务质量参数。
  9. 一种业务数据流的处理方法，其特征在于，包括：
    生成多个业务数据流之间的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求，并且用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；
    将所述同步性需求提供给核心网网元。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    生成针对所述多个业务数据流的同步性监测需求，所述同步性监测需求用于指示对多个业务数据流的传输同步性进行监测，以确定多个业务数据流在传输时是否能够满足同步性要求；
    将所述同步性监测需求提供给核心网网元。
  11. 根据权利要求9或10所述的方法，其特征在于，在将所述同步性监测需求提供给核心网网元之后，所述方法还包括以下步骤中的至少一个：
    接收接入网网元上报的同步性监测结果；
    接收其它核心网网元上报的同步性监测结果。
  12. 一种业务数据流的处理装置，其特征在于，包括：
    生成单元，配置为确定若多个业务数据流在传输时需要满足同步性要求，则根据所述同步性需求，生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；
    发送单元，配置为将所述处理策略信息发送给会话管理功能网元。
  13. 一种业务数据流的处理装置，其特征在于，包括：
    生成单元，配置为生成多个业务数据流之间的同步性需求，所述同步性需求用于指示所述多个业务数据流在传输时需要满足同步性要求，并且用于生成所述多个业务数据流的处理策略信息，所述处理策略信息用于提供针对所述多个业务数据流的传输同步性，配置第一服务质量(QoS)处理相关信息的第一策略；
    发送单元，配置为将所述同步性需求提供给核心网网元。
  14. 一种计算机可读介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至11中任一项所述的业务数据流的处理方法。
  15. 一种电子设备，其特征在于，包括：
    一个或多个处理器；
    存储器，用于存储一个或多个计算机程序，当所述一个或多个计算机程序被所述一个或多个处理器执行时，使得所述电子设备实现权利要求1至11中任一项所述的业务数据流的处理方法。
  16. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序，所述计算机程序存储在计算机可读存储介质中，电子设备的处理器从所述计算机可读存储介质读取并执行所述计算机程序，使得所述电子设备执行权利要求1至11中任一项所述的业务数据流的处理方法。
PCT/CN2025/111071 2024-08-01 2025-07-29 业务数据流的处理方法、装置、计算机可读介质及设备 Pending WO2026026751A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202411053106.8 2024-08-01
CN202411053106.8A CN121463124A (zh) 2024-08-01 2024-08-01 业务数据流的处理方法、装置、计算机可读介质及设备

Publications (1)

Publication Number Publication Date
WO2026026751A1 true WO2026026751A1 (zh) 2026-02-05

Family

ID=98581795

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/111071 Pending WO2026026751A1 (zh) 2024-08-01 2025-07-29 业务数据流的处理方法、装置、计算机可读介质及设备

Country Status (2)

Country Link
CN (1) CN121463124A (zh)
WO (1) WO2026026751A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014475A1 (en) * 2019-04-01 2022-01-13 Huawei Technologies Co.,Ltd. Packet delay parameter obtaining method, system, and apparatus
US20230209406A1 (en) * 2020-09-02 2023-06-29 Huawei Technologies Co., Ltd. Multi-flow associated transmission method, apparatus, and system
CN117896813A (zh) * 2022-10-09 2024-04-16 中国电信股份有限公司 数据流传输方法、装置、电子设备及存储介质
CN118251941A (zh) * 2022-03-28 2024-06-25 Oppo广东移动通信有限公司 数据传输方法、装置、设备、存储介质及程序产品

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014475A1 (en) * 2019-04-01 2022-01-13 Huawei Technologies Co.,Ltd. Packet delay parameter obtaining method, system, and apparatus
US20230209406A1 (en) * 2020-09-02 2023-06-29 Huawei Technologies Co., Ltd. Multi-flow associated transmission method, apparatus, and system
CN118251941A (zh) * 2022-03-28 2024-06-25 Oppo广东移动通信有限公司 数据传输方法、装置、设备、存储介质及程序产品
CN117896813A (zh) * 2022-10-09 2024-04-16 中国电信股份有限公司 数据流传输方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN121463124A (zh) 2026-02-03

Similar Documents

Publication Publication Date Title
CN112437122B (zh) 通信方法、装置、计算机可读介质及电子设备
US20240397372A1 (en) Data processing method and apparatus, computer-readable medium, and electronic device
US20170019197A1 (en) System for synchronous playback of media using a hybrid bluetooth™ and wi-fi network
US20170104550A1 (en) System for media rebroadcasting for synchronized rendering across multiple devices
US20240406783A1 (en) Data processing method and apparatus, computer readable medium, and terminal device
WO2023000894A1 (zh) 一种数据传输方法、装置、服务器、存储介质及程序产品
WO2022022471A1 (zh) 一种媒体流切换方法及装置
US12610333B2 (en) Data transmission method, data transmission apparatus, computer-readable medium, and electronic device
CN120017880A (zh) 视频数据的处理方法和装置、存储介质及电子设备
WO2024066602A1 (zh) 数据传输方法、装置、存储介质、电子设备及产品
US20230353609A1 (en) Method and Apparatus for Mapping DASH to WebRTC Transport
WO2022100199A1 (zh) 数据传输方法、装置、介质、电子设备及网络接入设备
WO2025139499A1 (zh) 基于非3GPP接入的QoS处理方法、装置、可读介质及设备
WO2022160210A1 (zh) 业务数据流的传输方法、通信装置及通信系统
US9762412B2 (en) Redundant traffic encoding of encapsulated real time communications
CN121463124A (zh) 业务数据流的处理方法、装置、计算机可读介质及设备
WO2025130053A1 (zh) 服务质量处理方法、装置、计算机可读介质及电子设备
WO2025167395A1 (zh) 通信方法、装置、计算机可读介质及电子设备
WO2026066552A1 (zh) 业务数据流的处理方法、装置、计算机可读介质及设备
Li et al. Research on XR Standard and Key Technologies
WO2025139498A1 (zh) 基于有线接入的拥塞处理方法、装置、可读介质及设备
WO2025123700A1 (zh) 通信方法、装置、计算机可读介质及电子设备
WO2025130439A1 (zh) 业务数据包集合的QoS处理方法、装置、可读介质及设备
CN120456134A (zh) 服务质量处理方法、装置、计算机可读介质及电子设备
WO2025060986A1 (zh) 应用元数据的下行传输方法、相关设备及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25847184

Country of ref document: EP

Kind code of ref document: A1