Quality of service processing method and apparatus, computer readable medium, and electronic device

Abstract

Embodiments of the present application provide a quality of service (QoS) processing method and apparatus, a computer readable medium, and an electronic device. The QoS processing method comprises: generating QoS requirement information respectively corresponding to service flow data packets of a plurality of media types mapped to a same QoS flow; and providing, to a core network element, the QoS requirement information respectively corresponding to the service flow data packets of the plurality of media types, so that the core network element generates, on the basis of the QoS requirement information, QoS policy information corresponding to the plurality of media types. The technical solution provided in the embodiments of the present application can perform more fine-grained QoS processing on the service data packets of different media types, thereby facilitating improvement of the resource utilization rate and the user experience.

Description

Service quality processing method, device, computer-readable medium and electronic device

[0001] Priority information

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 22, 2023, with application number 202311793216.3 and application name “Service Quality Processing Method, Device, Computer-Readable Medium and Electronic Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of computer and communication technology, and in particular to a method, device, computer-readable medium, and electronic device for processing quality of service. Background Art

[0004] In the fifth-generation mobile communication technology (5G) and its subsequent evolution systems (such as 5G-A and 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 (XR and Media Services, XRM), etc.

[0005] These high-bandwidth interactive services not only require high transmission timeliness, but also significantly increase the amount of data generated by the application layer as performance metrics such as resolution and frame rate increase. Therefore, the data packets generated by the application layer for these services are typically transmitted using a series of related packets, known as a Protocol Data Unit (PDU). Effectively controlling the transmission of these packets to meet the challenges posed by high-bandwidth interactive services on wireless network transmission remains a pressing technical challenge.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a Quality of Service (QoS) processing method, apparatus, computer-readable medium, and electronic device, which can implement more fine-grained QoS processing of service data packets of different media types, thereby improving resource utilization and user experience.

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

[0009] In the first aspect, an embodiment of the present application provides a QoS processing method, including: generating QoS requirement information corresponding to business flow data packets of multiple media types being mapped to the same QoS flow; providing the QoS requirement information corresponding to the business flow data packets of the multiple media types to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types based on the QoS requirement information.

[0010] In the second aspect, an embodiment of the present application provides a QoS processing method, including: obtaining QoS requirement information corresponding to business flow data packets of multiple media types mapped to the same QoS flow; generating QoS policy information for processing business flow data packets of the multiple media types based on the QoS requirement information corresponding to the business flow data packets of the multiple media types; and sending the QoS policy information to a session management function network element so that the session management function network element configures QoS processing related information to the processing device of the business flow data packet according to the QoS policy information.

[0011] In the third aspect, an embodiment of the present application provides a QoS processing method, including: receiving QoS policy information sent by a policy control function network element for processing business flow data packets of multiple media types, the QoS policy information being generated based on the QoS requirement information corresponding to the business flow data packets of the multiple media types being mapped to the same QoS flow; generating QoS processing related information corresponding to each type of processing device of the business flow data packet according to the QoS policy information; and configuring the QoS processing related information to the processing device of the business flow data packet.

[0012] In the fourth aspect, an embodiment of the present application provides a QoS processing device, including: a generating unit, configured to generate QoS requirement information corresponding to business flow data packets of multiple media types being mapped to the same QoS flow; a sending unit, configured to provide the QoS requirement information corresponding to the business flow data packets of the multiple media types to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types based on the QoS requirement information.

[0013] In the fifth aspect, an embodiment of the present application provides a QoS processing device, including: an acquisition unit, configured to obtain QoS requirement information corresponding to business flow data packets of multiple media types mapped to the same QoS flow; a generation unit, configured to generate QoS policy information for processing business flow data packets of multiple media types based on the QoS requirement information corresponding to the business flow data packets of the multiple media types; a sending unit, configured to send the QoS policy information to a session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the business flow data packet according to the QoS policy information.

[0014] In the sixth aspect, an embodiment of the present application provides a QoS processing device, including: a receiving unit, configured to receive QoS policy information sent by a policy control function network element for processing business flow data packets of multiple media types, wherein the QoS policy information is generated based on the QoS requirement information corresponding to the business flow data packets of the multiple media types being mapped to the same QoS flow; a generating unit, configured to generate QoS processing-related information corresponding to each type of processing device of the business flow data packet according to the QoS policy information; and a sending unit, configured to configure the QoS processing-related information to the processing device of the business flow data packet.

[0015] In a seventh aspect, an embodiment of the present application provides a computer-readable medium on which a computer program is stored. When the computer program is executed by a processor, it implements the QoS processing method as described in the above embodiment.

[0016] In an eighth aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; a storage device for storing one or more computer programs, wherein when the one or more computer programs are executed by the one or more processors, the electronic device implements the QoS processing method as described in the above embodiments.

[0017] In a ninth aspect, an embodiment of the present application provides a computer program product, the computer program product including a computer program stored in a computer-readable storage medium. A processor of an electronic device reads and executes the computer program from the computer-readable storage medium, causing the electronic device to perform the QoS processing method provided in the various optional embodiments described above.

[0018] In the technical solutions provided in some embodiments of the present application, QoS requirement information corresponding to the same QoS flow is mapped to service flow data packets of multiple media types, and then the QoS requirement information is provided to the core network network element. The core network network element generates QoS policy information corresponding to multiple media types based on the QoS requirement information, so that when service flow data packets of multiple media types share the same QoS flow, more fine-grained (i.e., finer granularity than the QoS flow) QoS processing can be achieved for service data packets of different media types, which is beneficial to improving resource utilization and user experience of processing service flow data packets, so as to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

[0019] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram showing an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;

[0021] FIG2 is a schematic diagram showing a transmission process of a multimedia data packet according to an embodiment of the present application;

[0022] FIG3 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0023] FIG4 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0024] FIG5 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0025] FIG6 shows a schematic diagram of a 5G network key network element architecture;

[0026] FIG7 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0027] FIG8 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0028] FIG9 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0029] FIG10 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0030] FIG11 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0031] FIG12 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] Example embodiments will now be described in a more complete manner with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to these examples; rather, these embodiments are provided to make this application more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art.

[0033] In addition, the features, structures or characteristics described in the present application may be combined in one or more embodiments in any suitable manner. In the following description, there are many specific details so that the embodiments of the present application can be fully understood. However, it will be appreciated by those skilled in the art that when implementing the technical solution of the present application, it is not necessary to use all the detailed features in the embodiments, one or more specific details may be omitted, or other methods, elements, devices, steps, etc. may be adopted.

[0034] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0035] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0036] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0037] It should be noted that the term "plurality" used in this document refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. The character " / " generally indicates an "or" relationship between the associated objects.

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

[0039] For example, in the cloud gaming scenario shown in FIG1 , the cloud server 101 is used to run the cloud game. The cloud server 101 can render the game screen, encode the audio signal and the rendered image, and finally transmit the encoded data obtained by the encoding process to each game client through 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 a smartphone, tablet computer, laptop computer, desktop computer, smart TV, smart home, car terminal, aircraft, etc.; or the game client can be an application running in a terminal device. Specifically, the game client can decode the encoded data transmitted by the cloud server 101 to obtain an analog audio and video signal and play it.

[0040] It should be understood that FIG1 is only an exemplary representation of the system architecture of the 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 background server for scheduling, etc. The cloud server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, 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 in this application.

[0041] In the various multimedia-based interactive service application scenarios mentioned above, due to the huge size of multimedia data packets, they need to be split into multiple data packets for transmission. Specifically, as shown in Figure 2, taking the 5G system as an example, the user plane mainly includes the application server, the user plane function (UPF), the base station (next generation nodeB, gNB), and the UE. For some typical service scenarios, the transmission of multimedia data packets is mainly in the downlink direction, such as from the application server (AS) to the UPF, and then sent to the UE through the gNB. During transmission, the multimedia data packet (using the XR data packet as an example in Figure 2) is split at the application layer of the application server. After the split data packet reaches the UPF from the application server as an IP packet, the 5G system transmits the sub-data packet to the UE end through the PDU session. At the UE end, it is delivered up the protocol stack step by step and reassembled to restore the multimedia data packet.

[0042] In the system shown in Figure 2, the L1 layer refers to the physical layer, which is used to ensure that the original data can be transmitted on various physical media; the L2 layer 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, which is used to implement data transmission between two end systems; UDP is the User Datagram Protocol, and GTP-U is the GPRS (General Packet Radio Service) Tunneling Protocol; PHY is the abbreviation of Physical, and is also known as the physical layer in Chinese; MAC is Media Access Control; RLC is Radio Link Control; PDCP is the Packet Data Convergence Protocol; and SDAP is the Service Data Adaptation Protocol.

[0043] As mentioned earlier, for multimedia services (such as XRM), it's common to split a single multimedia data packet into multiple packets for transmission. A single multimedia service frame or group of packets (GoP) can also be quite large, requiring a series of IP packets to carry it. These IP packets are somewhat correlated, and processing them based on this correlation can effectively conserve wireless network bandwidth.

[0044] For example, assuming that the transmission is carried out through multiple IP data packets, these multiple IP data packets can form a PDU set. If some data packets in the PDU set are lost, the entire frame, GoP or other video content may not be decoded, and the remaining data in the PDU set will be meaningless to the decoding end. However, if application layer forward error correction (FEC) or other mechanisms are introduced, the media application layer has a certain packet loss recovery capability or anti-packet loss capability. After discarding some messages, the remaining data in the PDU set can still be recovered and decoded, which means that the remaining data in the PDU set is still meaningful for the receiving end to decode.

[0045] In addition, if the QoS processing mechanism distinguishes different PDU sets based on the relevance of application layer data packets, then for PDU sets with high rates but that can tolerate a certain percentage of packet loss rate or delay excess rate, they can continue to be processed. In other words, the processing method of multimedia services can be more flexible. At the same time, the QoS flow mapping method used by the 5G system (5G System, 5GS) may be to map different PDU sets to different QoS flows, or to map different PDU sets to the same QoS flow. However, no matter which mapping method is used, the QoS processing granularity that 5GS can actually provide is only QoS flow. In this case, if the application layer service flow contains service flows with multiple QoS requirements, and these multiple service flows share the same QoS flow, then the current 5GS is obviously unable to provide different QoS support for these multiple service flows, which is insufficient for supporting multimodal multimedia service flows.

[0046] It is precisely based on the above problems that the technical solution of the embodiment of the present application proposes a new QoS processing solution, so that when business flow data packets of multiple media types share the same QoS flow, it is possible to achieve more fine-grained (i.e., finer granularity than the QoS flow) QoS processing of business data packets of different media types, which is beneficial to improve the resource utilization and user experience of processing business flow data packets, so as to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

[0047] The following is a detailed description of the implementation details of the technical solution of the embodiment of the present application:

[0048] FIG3 shows a flow chart of a QoS processing method according to an embodiment of the present application. The QoS processing method can be executed by an application function (AF) network element, or can also be executed by other network elements. Referring to FIG3 , the QoS processing method includes at least S310 to S320, which are described in detail as follows:

[0049] In S310, QoS requirement information corresponding to service flow data packets of multiple media types are mapped to the same QoS flow.

[0050] In some optional embodiments, the media type may include audio, video, haptic or other media types, and service flow data packets of different media types may have different QoS requirement information or may have the same QoS requirement information.

[0051] Optionally, these multiple media types of business flow data packets may be included in a certain multimedia service. For example, a cloud gaming service may include audio type business flow data packets, video type business flow data packets, or tactile or other types of business flow data packets. Since these multiple media types of business flow data packets are associated with the same multimedia service, they may be mapped to the same QoS flow during transmission. However, these multiple media types of business flow data packets may have different QoS requirement information. Therefore, a more fine-grained (i.e., finer-grained than the QoS flow) QoS processing can be provided in the embodiments of the present application.

[0052] Optionally, these multiple media types of business flow data packets may also be included in multiple different multimedia services. For example, the cloud gaming service and the VR service are integrated with each other to form a cloud gaming service with a virtual reality experience. Then, these multiple media types of business flow data packets also have a certain correlation, so they may be mapped to the same QoS flow during transmission. However, these multiple media types of business flow data packets may have different QoS requirement information, so more fine-grained QoS processing can be provided in the embodiments of the present application.

[0053] Optionally, there may be no correlation between the business flow packets of multiple media types mapped to the same QoS flow. Specifically, since the number of QoS flows included in a PDU session is limited, when a PDU session already contains more QoS flows, if no more QoS flows can be added to carry more business flow packets, then business flow packets of multiple media types can be mapped to one QoS flow, that is, business flow packets of multiple media types are carried by one QoS flow, and these business flow packets of different media types may have different QoS requirement information. Therefore, more fine-grained QoS processing can be provided in the embodiments of the present application.

[0054] It should be noted that the multimedia services in the embodiments of the present application may include not only cloud gaming services and VR services, but also AR services, MR services, XR services, XRM services, CR services, etc.

[0055] In some optional embodiments, service flow data packets can be transmitted in the form of service data packet sets (i.e., PDU sets). For example, a single service frame or a data packet formed by a GoP of a certain media type may have a relatively large number of bytes and needs to be split into a series of data packets for carrying. These data packets have a certain correlation, so these related data packets can be called PDU sets, and are transmitted in the form of PDU sets. For service flow data packets transmitted in the form of PDU sets, the QoS parameters in the corresponding QoS requirement information include at least one of the following parameters: PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), Maximum Data Burst Volume (MDBV), and Packet Delay Variation / Jitter (PDV).

[0056] Optionally, service flow data packets may be transmitted as individual packets (per-packet) rather than as PDUs. In this case, the QoS parameters in the corresponding QoS requirement information include at least one of the following parameters: packet delay budget (PDB), packet error rate (PER), maximum data burst size, etc.

[0057] It should be noted that in the embodiments of the present application, business flow data packets of multiple media types can all be transmitted in the form of PDU sets; they can also all be transmitted in the form of single data packets; or business flow data packets of some media types can be transmitted in the form of PDU sets, while business flow data packets of other media types can be transmitted in the form of single data packets.

[0058] In S320, the QoS requirement information corresponding to the service flow data packets of multiple media types is provided to the core network element, so that the core network element generates QoS policy information corresponding to the multiple media types according to the QoS requirement information.

[0059] In some optional embodiments, if service flow packets of multiple media types are mapped to the same QoS flow for processing, the service flow packets can be processed according to the QoS requirements of the service flow packets of different media types during transmission. In this case, the UPF, base station, UE, and other devices that monitor the QoS of service flow packets can identify service flow packets of different media types and perform corresponding QoS processing based on the service flow packets of different media types.

[0060] Optionally, service flow data packets of different media types can be identified and distinguished based on the characteristics of the media type. For example, audio type and video type can be identified and distinguished by detecting whether they contain image frame data. Optionally, various devices in the network (such as UE, base station, UFP, etc.) can also negotiate a method for distinguishing service flow data packets of different media types. For example, identification information indicating the media type can be added to the protocol part or payload part of the service flow data packet, and then the media type is determined by identifying the identification information. This negotiation can be negotiated before the PDU session is established, or it can be configured by default in these devices, so that in the process of establishing the QoS flow, there is no need to transmit the method for distinguishing service flow data packets of different media types between these devices.

[0061] Optionally, the method of distinguishing between service flow packets of different media types can also be sent to the core network network element by network element devices such as AF or AS. For example, when service flow packets of multiple media types are mapped to the same QoS flow and the corresponding QoS requirement information is sent to the core network network element, the method of distinguishing between service flow packets of these media types is sent to the core network network element at the same time, or before or after the QoS requirement information corresponding to service flow packets of multiple media types are sent to the core network network element, the method of distinguishing between service flow packets of these media types is sent to the core network network element, so that the core network network elements (such as policy control function network elements, session management function network elements, etc.) can take into account the distinction method when generating QoS-related policies or rules, so that the service flow packet processing equipment (UE, base station, UFP, etc.) can detect and distinguish service flow packets of different media types according to the relevant QoS policies or rules.

[0062] Optionally, after providing the QoS requirement information corresponding to the service flow packets of multiple media types to the core network element, the core network element can generate the QoS policy information corresponding to the service flow packets of multiple media types being mapped to the same QoS flow for processing based on the QoS requirement information. Of course, the core network element can also decide whether to map the service flow packets of multiple media types to the same QoS flow for processing. If it is determined that the service flow packets of multiple media types are to be mapped to the same QoS flow for processing, then the corresponding QoS policy information will be generated; if it is determined that the service flow packets of multiple media types are not to be mapped to the same QoS flow for processing (for example, service flow packets of different media types are mapped to different QoS flows for processing), then QoS policy information corresponding to different QoS flows can be generated.

[0063] In some optional embodiments, the method of distinguishing between business flow data packets of multiple media types is used to distinguish business flow data packets of different media types, and can be used to identify business flow data packets of various media types.

[0064] Optionally, business flow data packets of multiple media types can be encapsulated using different media encapsulation methods. Then, when providing the method for distinguishing between business flow data packets of multiple media types to the core network element, the media encapsulation methods corresponding to the business flow data packets of multiple media types can be provided to the core network element.

[0065] In some optional embodiments, service flow data packets may be encapsulated using the Quick User Datagram Protocol Internet Connections (QUIC) protocol. In this case, service flow data packets of different media types use different QUIC connection identifiers, or use different QUIC stream identifiers, or use different QUIC connection identifiers and different QUIC stream identifiers.

[0066] In some optional embodiments, service flow data packets may be encapsulated using the Real-time Transport Protocol (RTP). In this case, service flow data packets of different media types are distinguished by using different payload types. It should be noted that different payload types (PT) are used to indicate the media type contained in the RTP message, such as audio type, video type, etc. Optionally, dynamic PT values ​​may also be used to indicate different media types.

[0067] In some optional embodiments, the traffic data packets may be encapsulated using the Web Real-Time Communication (WebRTC) protocol. In this case, traffic data packets of different media types may be differentiated and encapsulated using the WebRTC protocol stack.

[0068] Optionally, the RTC peer connection (RTCPeerConnection) interface in the WebRTC protocol stack provides the functionality for establishing and maintaining end-to-end connections, and handles changes in connection status and the transmission of media data through RTC peer connection events. Therefore, different transmission options, such as transport protocols and transport layer ports, can be set in the RTC peer connection to distinguish data transmissions of different media types. For another example, the RTC peer connection (RTCDataChannel) interface in the WebRTC protocol stack provides end-to-end arbitrary binary data transmission functionality. Any type of data, including text, images, and files, can be sent and received through the RTC peer connection. Therefore, different data type identifiers can be set for data packets of different media types to facilitate the distinction between service flow data packets of different media types.

[0069] In some optional embodiments, the traffic data packets can be encapsulated using WebTransport. In this case, traffic data packets of different media types can be encapsulated using the WebTransport protocol stack.

[0070] Optionally, WebTransport supports multiple transport layer protocols, such as the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). Therefore, by specifying different transport layer protocols in signaling, different media types of data can be distinguished within the WebTransport protocol stack. For example, haptic data can be transmitted using TCP, while audio and video data can be transmitted using UDP.

[0071] For example, in the WebTransport protocol stack, different media types can be distinguished by assigning different port numbers or addresses to data. For example, port number 10000 can be used to transmit tactile data, while port number 20000 can be used to transmit audio and video data.

[0072] For example, the WebTransport protocol stack supports multiple payload types, each corresponding to a specific media format or encoding method. By specifying different payload types in signaling, the WebTransport protocol stack can distinguish between different media types. For example, you might use payload type 1 to transmit audio data, while payload type 2 might be used to transmit video data.

[0073] For example, WebTransport supports the creation of multiple data channels, each of which can be used to transmit data of different media types. By specifying different data channels in signaling, different media types can be distinguished within the WebTransport protocol stack. For example, channel 1 can be used to transmit haptic data, while channel 2 can be used to transmit audio and video data.

[0074] In some optional embodiments, service flow data packets of different media types may be encapsulated using the same protocol or different protocols. If service flow data packets of different media types are encapsulated using different protocols, the protocols and encapsulation methods described in the above embodiments may be used for encapsulation, or other protocols may be used for encapsulation. However, it is necessary to ensure that the service flow data packets of different media types can be distinguished through the encapsulation method.

[0075] In some optional embodiments, when providing the QoS requirement information corresponding to the service flow packets of multiple media types to the core network element, the QoS requirement information corresponding to the service flow packets of multiple media types can be directly sent to the policy control function network element. Alternatively, the QoS requirement information corresponding to the service flow packets of multiple media types can be sent to the network open function network element, and then forwarded to the policy control function network element by the network open function network element. Alternatively, a service level agreement (SLA) can be negotiated with the policy control function network element to transmit the QoS requirement information corresponding to the service flow packets of multiple media types to the policy control function network element.

[0076] Optionally, if it is necessary to send the method for distinguishing between service flow packets of multiple media types to the core network element, a similar approach can be adopted. That is, the method for distinguishing between service flow packets of multiple media types can be sent directly to the policy control function element. Alternatively, the method for distinguishing between service flow packets of multiple media types can be sent to the network open function element, which can then forward it to the policy control function element. Alternatively, a service level agreement can be negotiated with the policy control function element to convey the method for distinguishing between service flow packets of multiple media types to the policy control function element.

[0077] The above describes the technical solution of the embodiment of the present application from the perspective of the application function network element. The following further describes the implementation details of the technical solution of the embodiment of the present application from the perspective of the policy control function (PCF) network element in conjunction with Figure 4:

[0078] FIG4 shows a flow chart of a QoS processing method according to an embodiment of the present application. The QoS processing method can be executed by a policy control function network element, or can also be executed by other network elements. Referring to FIG4 , the QoS processing method includes at least S410 to S430, which are described in detail as follows:

[0079] In S410, QoS requirement information corresponding to service flow data packets of multiple media types mapped to the same QoS flow is obtained.

[0080] In some optional embodiments, the process of obtaining the QoS requirement information corresponding to the business flow data packets of multiple media types being mapped to the same QoS flow can be: receiving the QoS requirement information corresponding to the business flow data packets of multiple media types sent by AF or other network elements being mapped to the same QoS flow.

[0081] Optionally, in addition to obtaining the QoS requirement information corresponding to the mapping of business flow data packets of multiple media types to the same QoS flow, the policy control function network element can also obtain the distinction method between business flow data packets of multiple media types, and then consider this distinction method when generating QoS policy information for processing business flow data packets of multiple media types, so that the business flow data packet processing equipment (UE, base station, UFP, etc.) can detect and distinguish business flow data packets of different media types according to relevant QoS policies or rules.

[0082] It should be noted that the description of QoS requirement information and the method of distinguishing between service flow data packets of different media types can refer to the technical solutions of the aforementioned embodiments and will not be repeated here.

[0083] In S420, QoS policy information for processing the service flow data packets of the multiple media types is generated according to the QoS requirement information corresponding to the service flow data packets of the multiple media types.

[0084] In some optional embodiments, the QoS policy information for processing business flow packets of multiple media types may include whether to map business data streams of multiple media types to different QoS streams. For example, business flow packets of multiple media types may include business flow packets of audio type, business flow packets of video type, business flow packets of tactile type, etc., then the QoS policy information for processing business flow packets of multiple media types may include whether to map business flow packets of different media types to different QoS streams, that is, business flow packets of various media types use separate QoS streams. Of course, the QoS policy information for processing business flow packets of multiple media types may directly include indication information for mapping business flow packets of different media types to different QoS streams, or include indication information for not mapping business flow packets of different media types to different QoS streams (for example, mapping business flow packets of different media types to the same QoS stream).

[0085] In some optional embodiments, the QoS policy information for processing service flow packets of multiple media types may include whether to map service flow packets of different media types to the same QoS flow, that is, service flow packets of different media types use the same QoS flow. Of course, the QoS policy information for processing service flow packets of multiple media types may directly include indication information for mapping service flow packets of different media types to the same QoS flow.

[0086] In some optional embodiments, the QoS policy information used to process business flow data packets of multiple media types may include a method for distinguishing between business flow data packets of multiple media types. For example, since the importance information of a business data packet set can be used to indicate the importance of business flow data packets of different media types, business flow data packets of different media types can be indicated by the importance information of a business data packet set. Alternatively, business flow data packets of different media types can be indicated by media encapsulation. For example, in the aforementioned embodiment, encapsulation is performed by the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. to distinguish business flow data packets of different media types.

[0087] In some optional embodiments, the QoS policy information used to process traffic flow data packets of multiple media types may also include a combination of two or more of the above information.

[0088] It should be noted that, in the embodiments of the present application, service flow data packets of multiple media types may be transmitted in the form of PDU sets or in the form of individual data packets. For example, service flow data packets of multiple media types may all be transmitted in the form of PDU sets; or all may be transmitted in the form of individual data packets; or service flow data packets of some media types may be transmitted in the form of PDU sets, while service flow data packets of other media types may be transmitted in the form of individual data packets.

[0089] In S430, the QoS policy information is sent to the session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service flow data packet according to the QoS policy information.

[0090] In some optional embodiments, the process of the policy control function network element sending the QoS policy information to the session management function network element may be that the policy control function network element and the session management function network element interact through the session management policy association establishment (SM Policy Association Establishment) signaling process, or interact through the session management policy association modification (SM Policy Association Modification) signaling process, and then the policy control function network element sends the relevant policy information to the session management function network element through the session management policy context data information element (SM Policy Context Data IE).

[0091] Optionally, the process of the session management function network element configuring QoS processing related information to the service flow data packet processing device according to the QoS policy information may refer to the embodiment shown in FIG. 5 below.

[0092] FIG5 shows a flow chart of a QoS processing method according to an embodiment of the present application. The QoS processing method can be executed by a Session Management Function (SMF) network element, or can also be executed by other network elements. Referring to FIG5 , the QoS processing method includes at least S510 to S530, which are described in detail as follows:

[0093] In S510, the QoS policy information for processing service flow packets of multiple media types sent by the receiving policy control function network element is generated based on the QoS requirement information corresponding to the service flow packets of multiple media types being mapped to the same QoS flow.

[0094] It should be noted that the policy control function network element may also consider the method of distinguishing between service flow packets of multiple media types when generating QoS policy information. That is, the policy control function network element may generate QoS policy information based on the QoS requirement information corresponding to the service flow packets of multiple media types being mapped to the same QoS flow, as well as the method of distinguishing between service flow packets of multiple media types. Optionally, the description of the QoS requirement information and the method of distinguishing between service flow packets of different media types can refer to the technical solutions of the aforementioned embodiments and will not be repeated here.

[0095] In S520, QoS processing related information corresponding to each type of processing device for the service flow data packet is generated according to the QoS policy information for processing the service flow data packets of multiple media types.

[0096] In some optional embodiments, various types of processing devices for service flow data packets may include user plane function network elements, base station devices, and user equipment. The following describes how the session management function network element generates QoS processing related information corresponding to the user plane function network element, base station device, and user equipment respectively:

[0097] In some optional embodiments, the session management function network element may generate a service data flow (SDF) template (SDF Template) corresponding to the user plane function network element for processing service flow data packets based on QoS policy information for processing service flow data packets of multiple media types.

[0098] Optionally, the service data flow template may include a method for distinguishing between service flow packets of multiple media types. The method for distinguishing between service flow packets of multiple media types may be indicated by the importance information of the service packet set. Alternatively, service flow packets of different media types may be indicated by media encapsulation. For example, in the aforementioned embodiment, service flow packets of different media types may be encapsulated using the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. to distinguish between them.

[0099] Optionally, the service data flow template may include indication information for indicating that service flow data packets of multiple media types are mapped to the same QoS flow.

[0100] Optionally, the service data flow template may include QoS parameter information corresponding to service flow data packets of multiple media types. In this way, even if service flow data packets of multiple media types are mapped to the same QoS flow, QoS processing of service flow data packets of different media types can be implemented according to the QoS parameter information corresponding to the service flow data packets of different media types.

[0101] Optionally, the service data flow template may include a method for distinguishing between service flow data packets of multiple media types, indication information for indicating that service flow data packets of multiple media types are mapped to the same QoS flow, and two or all of the QoS parameter information corresponding to service flow data packets of multiple media types.

[0102] In some optional embodiments, the session management function network element may generate QoS profiles corresponding to the base station device that processes the service flow data packets based on QoS policy information used to process service flow data packets of multiple media types.

[0103] Optionally, the QoS profile includes a method for distinguishing between service flow packets of multiple media types. The method for distinguishing between service flow packets of multiple media types can be indicated by importance information of a set of service flow packets. Alternatively, service flow packets of different media types can be indicated by media encapsulation. For example, in the aforementioned embodiment, service flow packets of different media types are encapsulated using the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. to distinguish between them.

[0104] Optionally, when the base station device does not support processing service flow packets of multiple media types with different QoS requirements in the same QoS flow, the QoS profile may instruct the base station to process service flow packets of multiple media types through different QoS flows. Specifically, instructing the base station to process service flow packets of multiple media types through different QoS flows may be instructing the base station to map service flow packets of different media types to different QoS flows.

[0105] Optionally, if there is a correlation between the service flow data packets of multiple media types, for example, the service flow data packets of these multiple media types may be included in a certain multimedia service, such as the cloud gaming service may contain associated audio type service flow data packets, video type service flow data packets, and may also contain tactile type service flow data packets, etc. For another example, the service flow data packets of these multiple media types may also be included in multiple different multimedia services, such as the cloud gaming service and the VR service are integrated to form a cloud gaming service with a virtual reality experience, then there is a certain correlation between the service flow data packets of these multiple media types. Then, when the QoS configuration file instructs the base station to process the service flow data packets of multiple media types through different QoS flows, it can also further indicate the correlation between different QoS flows, so that the indication information of the correlation can be used to ensure that the service flow data packets with correlation can be processed in an associated manner, such as synchronization between service data packets of different media types (such as synchronization between audio type service flow data packets and video type service flow data packets) can be achieved through control.

[0106] Optionally, if the QoS profile instructs the base station to process service flow packets of multiple media types through different QoS flows, the QoS profile may also include maintaining synchronization between service flow packets corresponding to different QoS flows through a PDU aggregate delay budget or a packet delay budget. The PDU aggregate delay budget is applicable to synchronization between service flow packets transmitted via a PDU aggregate; the packet delay budget is applicable to synchronization between service flow packets transmitted via packets.

[0107] Optionally, the QoS configuration file may include QoS parameter information corresponding to business flow data packets of multiple media types. In this way, even if business flow data packets of multiple media types are mapped to the same QoS flow, QoS processing of business flow data packets of different media types can be implemented according to the QoS parameter information corresponding to the business flow data packets of different media types.

[0108] Optionally, the QoS configuration file may also include a combination of two or more of the above information.

[0109] In some optional embodiments, the session management function network element may generate QoS rule information (QoS rules) corresponding to the user equipment for processing service flow data packets based on QoS policy information for processing service flow data packets of multiple media types.

[0110] Optionally, the QoS rule information may include a method for distinguishing between service flow packets of multiple media types. The method for distinguishing between service flow packets of multiple media types may be indicated by the importance information of the service packet set. Alternatively, service flow packets of different media types may be indicated by media encapsulation. For example, in the aforementioned embodiment, service flow packets of different media types may be distinguished by encapsulation using the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, or the like.

[0111] Optionally, the QoS rule information may include indication information for indicating that service flow data packets of multiple media types are mapped to the same QoS flow.

[0112] Optionally, the QoS rule information may include QoS parameter information corresponding to business flow data packets of multiple media types. In this way, even if business flow data packets of multiple media types are mapped to the same QoS flow, QoS processing of business flow data packets of different media types can be implemented according to the QoS parameter information corresponding to the business flow data packets of different media types.

[0113] Optionally, the QoS rule information may include a method for distinguishing between business flow data packets of multiple media types, indication information for indicating that business flow data packets of multiple media types are mapped to the same QoS flow, and two or all of the QoS parameter information corresponding to business flow data packets of multiple media types.

[0114] In S530, QoS processing related information is configured to the processing device of the service flow data packet.

[0115] In some optional embodiments, the process of configuring QoS processing related information to the processing device of the service flow data packet may include: sending the service data flow template to the user plane functional network element, sending the QoS configuration file to the base station device, and sending the QoS rule information to the user device.

[0116] Specifically, taking the 5G system as an example, Figure 6 shows the key 5G network element architecture defined by the 3rd Generation Partnership Project (3GPP). 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 5G core network elements. A UE can be a 5G terminal such as a mobile phone or tablet; a (Radio) Access Network (R)AN can be a 5G base station; and a DN (Data Network) is the data network, i.e., the service server accessed by the UE.

[0117] Among them, 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 application layer NGAP protocol through the SCTP transport layer protocol, and carry the UE's non-access stratum (NAS) signaling data in NGAP. AMF is also responsible for terminating the UE's N1 interface, implementing NAS encryption and integrity protection, and is responsible for UE access authentication, authorization management, registration, connection, reachability and mobility management functions, as well as transparent transmission of session management messages between the UE and SMF.

[0118] In addition, (R)AN and UPF can interact through the N3 interface; UPFs can interact through the N9 interface; UPF and SMF can interact through the N4 interface; UPF and DN can interact through the N6 interface; SMF and AMF can interact through the N11 interface; SMF and PCF can interact through the N7 interface; SMF and UDM can interact through the N10 interface; PCF and AF can interact through the N5 interface; AMFs can interact through the N14 interface; AMF and PCF can interact through the N15 interface; AMF and UDM can interact through the N8 interface; AMF and NSSF can interact through the N22 interface; AMF and AUSF can interact through the N12 interface; AUSF and UDM can interact through the N13 interface.

[0119] Based on the system architecture shown in Figure 6, the session management function network element can send the service data flow template to the user plane function network element through the N4 interface, send the QoS configuration file to the base station device through the AMF, and send the QoS rule information AMF+NAS connection to the user device.

[0120] As can be seen, the technical solution of the embodiments of the present application may use a finer-grained flow differentiation method than the quintuple for an application layer service flow that may contain a set of PDUs of different media types. In this case, when transmitted in the network, a QoS flow may be shared. In this case, it is necessary to perform fine-grained identification and processing on the service flow packets of different media types that share the same QoS flow to meet the QoS requirements of the service flow packets of different media types.

[0121] Specifically, as shown in FIG7 , a QoS processing method according to an embodiment of the present application includes the following steps:

[0122] S701: AF provides fine-grained QoS requirement information, as well as upper-layer media type information and protocol bearer information to distinguish different media types.

[0123] In some optional embodiments, if a multimedia service flow includes different media types (such as audio, video, tactile, or other media types), the PDU aggregation mechanism can be enabled or disabled for these media types, that is, the use of PDU aggregation for data transmission can be selected. Furthermore, the data packets of these service flows of different media types can have different QoS requirements and different upper-layer protocol encapsulation methods.

[0124] It should be noted that the QoS requirements provided for media types that do not have the PDU aggregation mechanism enabled can include QoS parameters for data packets, such as PER, PDB, etc. However, the QoS requirements provided for media types that have the PDU aggregation mechanism enabled can include QoS parameters for PDU aggregation, such as PSDB, PSER, MDBV, PDV, etc.

[0125] Optionally, the QoS requirements provided for media types with the PDU aggregation mechanism enabled can also include QoS parameters for data packets. In this case, it can be understood that the QoS requirements for data packets in the existing standard protocol are reused, that is, the QoS parameters for PDU aggregation are added to the QoS requirements. Of course, a new QoS requirement for PDU aggregation can also be used to include QoS parameter information for PDU aggregation.

[0126] In some optional embodiments, if the upper layer protocol of the service flow data packet uses the QUIC protocol, such as RTP over QUIC, then the service flow data packets of different media types can be distinguished using different QUIC connection IDs, or different stream IDs, or different QUIC connection IDs and different stream IDs.

[0127] In some optional embodiments, if the upper layer protocol of the service flow data packet uses the RTP protocol, then service flow data packets of different media types can be distinguished using different dynamic RTP protocol types (ie, payload types), such as 96 representing video frames and 97 representing audio frames.

[0128] In some optional embodiments, if the upper layer protocol of the service flow data packet uses the WebRTC protocol, then service flow data packets of different media types can be distinguished by setting different transmission options or different data type identifiers in the RTC peer connection.

[0129] In some optional embodiments, if the business flow data packets are encapsulated using the WebTransport protocol stack, then business flow data packets of different media types can be distinguished using one or more of different transport layer protocols, different port numbers, different payload types, and different data channels.

[0130] AF can provide auxiliary information to 5GS based on the upper-layer protocol encapsulation method used by service flow data packets of different media types, and associate it with the QoS requirements of service flow data packets of different media types to support more fine-grained QoS processing of service flow data packets.

[0131] In some optional embodiments, the QoS requirements and Policy Control and Charging (PCC) policy guidance information provided by the AF for service flow packets (e.g., PDU sets) are not PCC rules. Therefore, they can be described from the perspective of service requirements without providing every parameter of a PCC rule. For example, different parameter values ​​or parameter ranges can be provided for the QoS parameters of the PDU set (e.g., one or more of PSDB, PSER, MDBV, and PDV).

[0132] In some optional embodiments, to reduce the amount of information exchanged between the AF and the 5G Core (5GC), the AF and 5GC may also negotiate an SLA to reflect the QoS requirements for service flow packets of different media types. In this case, the SLA may include QoS requirements for service flow packets of different media types.

[0133] It should be noted that in other embodiments of the present application, the AF may not provide upper-layer media type information and protocol bearer information to distinguish different media types. Instead, other network element devices may distinguish between different media types by detecting the characteristics of service flow packets of various media types (such as frame rate, resolution, and data types included). Alternatively, each network element device may distinguish between service flow packets of different media types through a pre-agreed method.

[0134] S702: PCF generates fine-grained PCC rules.

[0135] In some optional embodiments, after the AF sends the upper layer protocol encapsulation mode used by service flow data packets of different media types and the QoS requirements of service flow data packets of different media types to the PCF, or sends them to the PCF through the NEF network element, or informs the PCF through SLA negotiation, the PCF may generate PCC rules required for finer-grained QoS processing based on the user's contract information or the SLA between the PCF and the AF, including but not limited to the following information:

[0136] Whether service flow packets of different media types should be mapped to different QoS flows; whether PDU set importance information (PSI) is used to distinguish service flow packets of different media types; whether information with higher granularity than PSI, such as different media layer encapsulation information, is used to indicate service flow packets of different media types; if service flow packets of different media types are mapped to the same QoS flow, the configured PCC rules need to be able to support UPF, NG-RAN and UE to perform corresponding finer-grained QoS processing.

[0137] In some optional embodiments, the PCF needs to send the part of the generated PCC rules required by the SMF to the SMF, so that the SMF can generate QoS processing related information corresponding to different devices (such as UPF, NG-RAN and UE) based on the information sent by the PCF.

[0138] In some optional embodiments, the QoS processing related information generated by the SMF for the UPF may be an SDF template, which includes a fine-grained identification and detection method for service flow packets of different media types, including but not limited to (assuming that the UPF has the identification and processing capability within five tuples):

[0139] If the upper layer protocol of the service stream data packet uses the QUIC protocol, such as RTP over QUIC, then service stream data packets of different media types can be distinguished by using different QUIC connection IDs, or by using different stream IDs, or by using different QUIC connection IDs and different stream IDs.

[0140] If the upper layer protocol of the service flow data packet uses the RTP protocol, then service flow data packets of different media types can be distinguished by using different dynamic RTP protocol types (ie, payload types), such as 96 for video frames and 97 for audio frames.

[0141] If the upper layer protocol of the service flow data packet uses the WebRTC protocol, then service flow data packets of different media types can be distinguished by setting different transmission options or different data type identifiers in the RTC peer connection.

[0142] If the upper layer protocol of the service flow data packet uses the WebTransport protocol, then service flow data packets of different media types can be distinguished by using one or more of different transport layer protocols, different port numbers, different payload types, and different data channels.

[0143] In some optional embodiments, the SDF Template generated by SMF for UPF may also include QoS flow mapping rules, that is, mapping service flow data packets of different media types (downlink data packets indicated for UPF) to the same QoS flow, and performing differentiated detection in the above manner.

[0144] In some optional embodiments, the NG-RAN-specific QoS processing related information generated by the SMF includes QoS profiles that support fine-grained QoS processing on the NG-RAN, and may also include the following: If the NG-RAN does not support fine-grained QoS processing, the NG-RAN may still use QoS flow-level QoS processing, but the QoS profile may include correlation information between multiple QoS flows. In this case, synchronization of data in different QoS flows can be guaranteed by using the PSDB of the PDU set or the PDB of the per-packet.

[0145] In some optional embodiments, the QoS processing related information generated by the SMF for the UE may be QoS rules, which include a fine-grained identification and detection method for service flow data packets of different media types (as specifically described in the above embodiments), and may also include QoS flow mapping rules, that is, mapping service flow data packets of different media types (indicated as uplink data packets for the UE) to the same QoS flow, and performing differentiated detection through the above method.

[0146] S703, SMF configures SDF Template, QoS profiles and QoS rules to UPF, NG-RAN and UE.

[0147] In some optional embodiments, the SMF configures the SDF Template to the UPF through the N4 interface, which includes more fine-grained detection and QoS rules for service flow data packets of different media types.

[0148] At the same time, SMF configures QoS profiles to NG-RAN through AMF to support more fine-grained detection of service flow packets of different media types; and SMF configures more fine-grained detection and QoS rules for service flow packets of different media types to UE through AMF+NAS connection.

[0149] S704: UPF, NG-RAN, and UE implement finer-grained QoS processing.

[0150] Optionally, when transmitting downlink data packets to the UE, if service flow data packets of multiple media types need to be mapped to the same QoS flow and have different QoS requirements, the UPF can distinguish the service flow data packets of these multiple media types through different upper-layer protocol encapsulation methods to ensure the QoS requirements of service flow data packets of various media types. When transmitting uplink data packets to the UPF, if service flow data packets of multiple media types need to be mapped to the same QoS flow and have different QoS requirements, the UE can distinguish the service flow data packets of these multiple media types through different upper-layer protocol encapsulation methods to ensure the QoS requirements of service flow data packets of various media types. When NG-RAN can transfer service flow data packets between the UE and the UPF, it can also implement more fine-grained detection of service flow data packets of different media types to ensure the QoS requirements of service flow data packets of different media types.

[0151] 8 , the technical solution of the embodiment of the present application is described in detail using a specific example, which specifically includes the following steps:

[0152] S801: After the PDU session is established, the AF performs signaling interaction with the 5G system (5G system, 5GS) to indicate finer-grained QoS requirements and upper-layer protocol encapsulation methods.

[0153] S802: Based on the information provided by the AF, the PCF generates finer-grained QoS policy information, and the SMF generates QoS processing related information for each device.

[0154] Optionally, the SMF generates QoS processing related information for each device, including the SDF Template for UPF, QoS profiles for NG-RAN, and QoS rules for UE.

[0155] S803, 5GC configures QoS processing related information to UPF, base station and UE.

[0156] In some optional embodiments, SMF configures the SDF Template to the UPF through the N4 interface; SMF configures QoS profiles to the NG-RAN through the AMF, and SMF configures QoS rules to the UE through the AMF+NAS connection.

[0157] S804: PDU set identification and marking, for more fine-grained QoS rules, in conjunction with RAN for monitoring and statistics.

[0158] S805: Process the PDU set in combination with finer-grained QoS rules.

[0159] For example, if it is monitored that one or more of the parameters such as PSDB, PSER, PDV of a certain media type of service flow data packet in the same QoS flow has exceeded the QoS requirements, a notification message is sent to the core network to trigger PDU session modification or other processes.

[0160] The technical solution of the embodiment of the present application proposes a more fine-grained service flow processing solution, which can perform fine-grained identification and processing of service flow data packets of different media types when service flow data packets of different media types share a QoS flow, so as to meet the QoS requirements of service flow data packets of different media types, thereby improving resource utilization when 5GS carries services such as XRM that contain service flow data packets of multiple media types, so as to better support immersive XRM services.

[0161] The following describes an embodiment of the device of the present application, which can be used to implement the QoS processing method in the above embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the QoS processing method in the above embodiment of the present application.

[0162] FIG9 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device can be applied to an AF or other network elements.

[0163] 9 , a QoS processing device 900 according to an embodiment of the present application includes: a generating unit 902 and a sending unit 904 .

[0164] Among them, the generating unit 902 is configured to generate QoS requirement information corresponding to the business flow data packets of multiple media types being mapped to the same QoS flow; the sending unit 904 is configured to provide the QoS requirement information corresponding to the business flow data packets of the multiple media types to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types according to the QoS requirement information.

[0165] In some embodiments of the present application, based on the aforementioned scheme, the sending unit 904 is also configured to: provide the method of distinguishing between the business flow data packets of the multiple media types to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types according to the distinction method and the QoS requirement information.

[0166] In some embodiments of the present application, based on the aforementioned scheme, the business flow data packets of the multiple media types are encapsulated using different media encapsulation methods; the sending unit 904 is configured to: provide the media encapsulation methods corresponding to the business flow data packets of the multiple media types to the core network network element.

[0167] In some embodiments of the present application, based on the aforementioned solution, the service flow data packet is encapsulated using at least one of the following media encapsulation methods:

[0168] The Fast User Datagram Protocol network connection QUIC protocol is used for encapsulation, and service flow data packets of different media types use different QUIC connection identifiers and / or different QUIC stream identifiers;

[0169] The real-time transport protocol (RTP) is used for encapsulation, and different media types of service flow data packets use different payload types;

[0170] Use the WebRTC protocol stack for differentiated encapsulation;

[0171] The WebTransport protocol stack is used for differentiated encapsulation.

[0172] In some embodiments of the present application, based on the aforementioned scheme, the business flow data packets of the multiple media types are respectively transmitted in the form of business data packet sets; wherein, the QoS parameters in the QoS requirement information corresponding to the business flow data packets of various media types include at least one of the following parameters: protocol data unit PDU set delay budget, PDU set bit error rate, maximum data burst size, and data packet delay jitter.

[0173] In some embodiments of the present application, based on the above solution, the sending unit 904 is configured to: directly send the QoS requirement information corresponding to the service flow data packets of the multiple media types to the policy control function network element; or

[0174] Sending the QoS requirement information corresponding to the service flow data packets of the multiple media types to the network open function network element, so that the network open function network element forwards it to the policy control function network element; or

[0175] The service level agreement is negotiated with the policy control function network element so as to provide the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types to the policy control function network element.

[0176] FIG10 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device can be applied to a policy control function network element or other network elements.

[0177] 10 , a QoS processing device 1000 according to an embodiment of the present application includes: an acquiring unit 1002 , a generating unit 1004 , and a sending unit 1006 .

[0178] Among them, the acquisition unit 1002 is configured to obtain the QoS requirement information corresponding to the business flow data packets of multiple media types mapped to the same QoS flow; the generation unit 1004 is configured to generate QoS policy information for processing the business flow data packets of the multiple media types according to the QoS requirement information corresponding to the business flow data packets of the multiple media types; the sending unit 1006 is configured to send the QoS policy information to the session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the business flow data packet according to the QoS policy information.

[0179] In some embodiments of the present application, based on the aforementioned scheme, the acquisition unit 1002 is further configured to: obtain a method for distinguishing between the business flow data packets of the multiple media types; the generation unit 1004 is configured to: generate QoS policy information for processing the business flow data packets of the multiple media types according to the distinction method and the QoS requirement information corresponding to the business flow data packets of the multiple media types.

[0180] In some embodiments of the present application, based on the aforementioned solution, the policy information for performing QoS processing on the traffic flow packets of the multiple media types includes at least one of the following information:

[0181] Whether to map the traffic flow data packets of the multiple media types to different QoS flows;

[0182] Whether to map the service flow data packets of the multiple media types to the same QoS flow;

[0183] A method for distinguishing between the business flow data packets of the multiple media types.

[0184] In some embodiments of the present application, based on the aforementioned scheme, the method of distinguishing between the business flow data packets of the multiple media types is indicated by at least one of the following methods: indicating business flow data packets of different media types by the importance information of the business data packet set; indicating business flow data packets of different media types by the media encapsulation method.

[0185] FIG11 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device can be applied to a session management function network element or other network elements.

[0186] 11 , a QoS processing device 1100 according to an embodiment of the present application includes: a receiving unit 1102 , a generating unit 1104 , and a sending unit 1106 .

[0187] Among them, the receiving unit 1102 is configured to receive policy information sent by the policy control function network element for QoS processing of business flow data packets of multiple media types, and the policy information is generated based on the QoS requirement information corresponding to the business flow data packets of the multiple media types being mapped to the same QoS flow; the generating unit 1104 is configured to generate QoS processing related information corresponding to each type of processing device of the business flow data packet according to the policy information; the sending unit 1106 is configured to configure the QoS processing related information to the processing device of the business flow data packet.

[0188] In some embodiments of the present application, based on the aforementioned scheme, the generation unit 1104 is configured to: generate a service data flow template corresponding to the user plane functional network element for processing the service flow data packet according to the policy information, and the service data flow template contains at least one of the following information: a method for distinguishing between the service flow data packets of the multiple media types; indication information for indicating that the service flow data packets of the multiple media types are mapped to the same QoS flow; and QoS parameter information corresponding to the service flow data packets of the multiple media types.

[0189] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1104 is configured to: generate a QoS profile corresponding to the base station device that processes the service flow data packet according to the policy information, where the QoS profile includes at least one of the following information:

[0190] A method for distinguishing between the service flow data packets of the multiple media types;

[0191] QoS parameter information corresponding to the service flow data packets of the multiple media types;

[0192] If the base station device does not support processing business flow packets of multiple media types with different QoS requirements in the same QoS flow, the base station is instructed to process the business flow packets of the multiple media types through different QoS flows, and the correlation between the different QoS flows is indicated.

[0193] In some embodiments of the present application, based on the aforementioned scheme, if the QoS profile indicates that the base station processes the service flow data packets of the multiple media types through different QoS flows, the QoS profile also includes maintaining synchronization between the service flow data packets corresponding to the different QoS flows through a PDU set delay budget or a data packet delay budget.

[0194] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1104 is configured to: generate QoS rule information corresponding to the user equipment for processing the service flow data packet according to the policy information, wherein the QoS rule information includes at least one of the following information:

[0195] A method for distinguishing between the service flow data packets of the multiple media types;

[0196] Instruction information for indicating that the service flow data packets of the multiple media types are mapped to the same QoS flow;

[0197] The QoS parameter information corresponding to the service flow data packets of the multiple media types.

[0198] Figure 12 shows a structural diagram of a computer system of an electronic device suitable for implementing an embodiment of the present application. The electronic device may be an application function network element, a policy control function network element, or a session management function network element in the aforementioned embodiment.

[0199] It should be noted that the computer system 1200 of the electronic device shown in FIG12 is merely an example and should not impose any limitations on the functions and scope of use of the embodiments of the present application.

[0200] As shown in Figure 12, the computer system 1200 may include a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1202 or the program loaded from the storage part 1208 into the random access memory (RAM) 1203, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 1203. The CPU 1201, ROM 1202 and RAM 1203 are connected to each other via a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0201] The following components can be connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output section 1207 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1208 including a hard disk; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. Removable media 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1210 as needed, so that computer programs read from the removable media can be installed in the storage section 1208 as needed.

[0202] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program is used to perform the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1209, and / or installed from a removable medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, the various functions defined in the system of the present application are performed.

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

[0204] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and a computer program.

[0205] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0206] As another aspect, the present application further provides a computer-readable medium, which may be included in the electronic device described in the above embodiments, or may exist independently without being incorporated into the electronic device. The computer-readable medium carries one or more computer programs, and when the one or more computer programs are executed by the electronic device, the electronic device implements the method described in the above embodiments.

[0207] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0208] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable an electronic device to execute the method according to the embodiments of the present application.

[0209] For example, the electronic device can be an application function network element, then the application function network element can execute the QoS processing method shown in Figure 3; for another example, the electronic device can be a policy control function network element, then the policy control function network element can execute the QoS processing method shown in Figure 4; for another example, the electronic device can be a session management function network element, then the session management function network element can execute the QoS processing method shown in Figure 5.

[0210] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0211] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for processing quality of service (QoS), characterized in that: include: Generate QoS requirement information corresponding to service flow data packets of multiple media types and mapped to the same QoS flow; The QoS requirement information corresponding to the service flow data packets of the multiple media types is provided to the core network element, so that the core network element generates QoS policy information corresponding to the multiple media types according to the QoS requirement information.

2. The method according to claim 1, characterized in that The method further comprises: The method of distinguishing between the business flow data packets of the multiple media types is provided to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types according to the distinction method and the QoS requirement information.

3. The method according to claim 2, characterized in that The business flow data packets of the multiple media types are encapsulated using different media encapsulation methods; Providing the core network network element with a method for distinguishing between the business flow data packets of the multiple media types, includes: providing the core network network element with media encapsulation methods respectively corresponding to the business flow data packets of the multiple media types.

4. The method according to claim 3, characterized in that: The service flow data packet is encapsulated using at least one of the following media encapsulation methods: The QUIC protocol is used for encapsulation, and different media types of service flow data packets use different QUIC connection identifiers and / or different QUIC flow identifiers; The real-time transport protocol RTP is used for encapsulation, and different media types of service flow data packets use different payload types; The protocol stack of WebRTC, a real-time network communication protocol, is used for differentiated encapsulation; The WebTransport protocol stack is used for differentiated encapsulation.

5. The method according to any one of claims 1 to 4, characterized in that The service flow data packets of the multiple media types are respectively transmitted in the form of service data packet sets; The QoS parameters in the QoS requirement information corresponding to the service flow data packets of various media types include at least one of the following parameters: Protocol data unit (PDU) aggregate delay budget, PDU aggregate bit error rate, maximum data burst size, and data packet delay jitter.

6. The method according to any one of claims 1 to 5, characterized in that Providing QoS requirement information corresponding to the service flow data packets of the multiple media types to the core network element, including: directly sending the QoS requirement information corresponding to the service flow data packets of the multiple media types to the policy control function network element; or Sending the QoS requirement information corresponding to the service flow data packets of the multiple media types to the network open function network element, so that the network open function network element forwards it to the policy control function network element; or The service level agreement is negotiated with the policy control function network element so as to provide the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types to the policy control function network element.

7. A QoS processing method, characterized in that: include: Obtaining QoS requirement information corresponding to service flow data packets of multiple media types mapped to the same QoS flow; Generate QoS policy information for processing the service flow data packets of the multiple media types according to the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types; The QoS policy information is sent to a session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service flow data packet according to the QoS policy information.

8. The method according to claim 7, characterized in that The method further comprises: obtaining a method for distinguishing between the service flow data packets of the plurality of media types; The method of generating QoS policy information for processing the business flow packets of the multiple media types according to the QoS requirement information respectively corresponding to the business flow packets of the multiple media types includes: generating QoS policy information for processing the business flow packets of the multiple media types according to the distinction method and the QoS requirement information respectively corresponding to the business flow packets of the multiple media types.

9. The method according to claim 7 or 8, characterized in that: The QoS policy information for processing the service flow data packets of the multiple media types includes at least one of the following information: Whether to map the service flow data packets of the multiple media types to different QoS flows; Whether to map the service flow data packets of the multiple media types to the same QoS flow; A method for distinguishing between the business flow data packets of the multiple media types.

10. The method according to claim 9, characterized in that The manner of distinguishing between the service flow data packets of the multiple media types is indicated by at least one of the following manners: Indicating service flow data packets of different media types through importance information of service data packet sets; Indicates business flow data packets of different media types through media encapsulation.

11. A QoS processing method, characterized in that: include: Receiving QoS policy information for processing service flow data packets of multiple media types sent by a policy control function network element, wherein the QoS policy information is generated according to QoS requirement information corresponding to the service flow data packets of the multiple media types being mapped to the same QoS flow; Generate QoS processing related information corresponding to various types of processing devices of the service flow data packets according to the QoS policy information; The QoS processing related information is configured to the processing device of the service flow data packet.

12. The method according to claim 11, characterized in that Generate QoS processing related information corresponding to various types of processing devices of the service flow data packets according to the QoS policy information, including: Generate a service data flow template corresponding to a user plane function network element for processing the service flow data packet according to the QoS policy information, wherein the service data flow template includes at least one of the following information: A method for distinguishing between the service flow data packets of the multiple media types; Indication information used to indicate mapping of service flow data packets of the multiple media types to the same QoS flow; The QoS parameter information corresponding to the business flow data packets of the multiple media types respectively.

13. The method according to claim 11, characterized in that Generate QoS processing related information corresponding to various types of processing devices of the service flow data packets according to the QoS policy information, including: Generate a QoS configuration file corresponding to the base station device that processes the service flow data packet according to the QoS policy information, wherein the QoS configuration file includes at least one of the following information: A method for distinguishing between the service flow data packets of the multiple media types; QoS parameter information corresponding to the service flow data packets of the multiple media types respectively; If the base station device does not support processing service flow packets of multiple media types with different QoS requirements in the same QoS flow, the base station is instructed to process the service flow packets of the multiple media types through different QoS flows, and the correlation between the different QoS flows is indicated.

14. The method according to claim 13, characterized in that If the QoS configuration file indicates that the base station processes the service flow data packets of the multiple media types through different QoS flows, the QoS configuration file also includes maintaining synchronization between the service flow data packets corresponding to the different QoS flows through a PDU set delay budget or a data packet delay budget.

15. The method according to claim 11, characterized in that Generate QoS processing related information corresponding to various types of processing devices of the service flow data packets according to the QoS policy information, including: Generate QoS rule information corresponding to the user equipment for processing the service flow data packet according to the QoS policy information, wherein the QoS rule information includes at least one of the following information: A method for distinguishing between the service flow data packets of the multiple media types; Indication information used to indicate mapping of service flow data packets of the multiple media types to the same QoS flow; The QoS parameter information corresponding to the business flow data packets of the multiple media types respectively.

16. A QoS processing device, characterized in that: include: A generating unit configured to generate QoS requirement information corresponding to service flow data packets of multiple media types being mapped to the same QoS flow; The sending unit is configured to provide the QoS requirement information corresponding to the business flow data packets of the multiple media types to the core network network element, so that the core network network element generates QoS policy information corresponding to the multiple media types according to the QoS requirement information.

17. A QoS processing device, characterized in that: include: An acquisition unit configured to acquire QoS requirement information corresponding to service flow data packets of multiple media types being mapped to the same QoS flow; A generating unit configured to generate QoS policy information for processing the service flow data packets of the multiple media types according to the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types; The sending unit is configured to send the QoS policy information to the session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service flow data packet according to the QoS policy information.

18. A QoS processing device, characterized in that: include: A receiving unit, configured to receive QoS policy information for processing service flow data packets of multiple media types sent by a policy control function network element, wherein the QoS policy information is generated according to QoS requirement information corresponding to the service flow data packets of the multiple media types being mapped to the same QoS flow; A generating unit, configured to generate QoS processing related information corresponding to various types of processing devices of the service flow data packets respectively according to the QoS policy information; The sending unit is configured to configure the QoS processing related information to the processing device of the service flow data packet.

19. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 15 is implemented.

20. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more computer programs, which, when executed by the one or more processors, enables the electronic device to implement the method as claimed in any one of claims 1 to 15.

Images