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

Abstract

The embodiment of the invention provides a service quality processing method and device, a computer readable medium and electronic equipment. The QoS processing method comprises the following steps: generating QoS demand information corresponding to the fact that service flow data packets of various media types are mapped to the same QoS flow; and providing the QoS demand information corresponding to the service flow data packets of the multiple media types to a core network element, so that the core network element generates QoS strategy information corresponding to the multiple media types according to the QoS demand information. According to the technical scheme provided by the embodiment of the invention, more fine-grained QoS processing can be carried out on service data packets of different media types, and the resource utilization rate and the user experience can be improved.

Description

Technical Field

[0001] This application relates to the fields of computer and communication technologies. Specifically, it relates to a method and apparatus for processing quality of service (QoS), a computer-readable medium, and an electronic device. Background Art

[0002] In the fifth-generation mobile communication technology (5G) and its subsequent evolved systems (such as 5G-A, 6G, etc.), high-bandwidth interactive services are important service types, such as cloud gaming, virtual reality (VR), augmented reality (AR), mixed reality (MR), extended reality (XR), cinematic reality (CR), XR and media services (XR and M), etc.

[0003] These high-bandwidth interactive services not only have very high requirements for transmission timeliness, but also, with the improvement of indicators such as resolution and frame rate, the amount of data generated at the application layer has increased greatly. Therefore, the content of data packets generated at the application layer of this type of service usually uses a series of related data packets for transmission, and this series of data packets is called a protocol data unit (PDU) set. For the transmission process of this series of data packets, how to effectively perform transmission control to cope with the challenges of high-bandwidth interactive services to wireless network transmission is a technical problem to be solved urgently. Summary of the Invention

[0004] Embodiments of this application provide a method and apparatus for processing quality of service (QoS), a computer-readable medium, and an electronic device, which can implement more fine-grained QoS processing for service data packets of different media types, and is conducive to improving resource utilization and user experience.

[0005] Other features and advantages of this application will become apparent through the following detailed description, or will be partially learned through the practice of this application.

[0006] In a first aspect, embodiments of this application provide a QoS processing method, including: generating QoS requirement information corresponding to service flow data packets of multiple media types mapped to the same QoS flow respectively; providing the QoS requirement information corresponding to the service flow data packets of the multiple media types to a 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.

[0007] Second aspect, an embodiment of the present application provides a QoS processing method, including: obtaining QoS requirement information respectively corresponding to service flow data packets of multiple media types mapped to the same QoS flow; generating 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; 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 for a processing device of the service flow data packets according to the QoS policy information.

[0008] Third aspect, an embodiment of the present application provides a QoS processing method, including: receiving QoS policy information for processing service flow data packets of multiple media types sent by a policy control function network element, where the QoS policy information is generated according to QoS requirement information respectively corresponding to the service flow data packets of the multiple media types mapped to the same QoS flow; generating QoS processing related information respectively corresponding to various processing devices of the service flow data packets according to the QoS policy information; and configuring the QoS processing related information for the processing devices of the service flow data packets.

[0009] Fourth aspect, an embodiment of the present application provides a QoS processing apparatus, including: a generating unit configured to generate QoS requirement information respectively corresponding to service flow data packets of multiple media types mapped to the same QoS flow; and a sending unit configured to provide the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types to a 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.

[0010] Fifth aspect, an embodiment of the present application provides a QoS processing apparatus, including: an obtaining unit configured to obtain QoS requirement information respectively corresponding to service flow data packets of multiple media types 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; and 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 for a processing device of the service flow data packets according to the QoS policy information.

[0011] 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 service flow data packets of multiple media types, where the QoS policy information is generated according to QoS requirement information respectively corresponding to the service flow data packets of multiple media types being mapped to the same QoS flow; a generating unit configured to generate QoS processing related information corresponding to respective processing devices of the service flow data packets according to the QoS policy information; a sending unit configured to configure the QoS processing related information to the processing devices of the service flow data packets.

[0012] Seventh aspect, an embodiment of the present application provides a computer-readable medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the QoS processing method as described in the above embodiments.

[0013] Eighth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a storage device for storing one or more computer programs, and 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.

[0014] Ninth aspect, an embodiment of the present application provides a computer program product, which includes 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, so that the electronic device executes the QoS processing method provided in the above various alternative embodiments.

[0015] In the technical solutions provided in some embodiments of the present application, by generating QoS requirement information respectively corresponding to service flow data packets of multiple media types being mapped to the same QoS flow, and then providing the QoS requirement information to a core network element, and further the core network element generates QoS policy information corresponding to multiple media types according to the QoS requirement information, it is possible to perform more fine-grained (i.e., finer than the QoS flow) QoS processing on service data packets of different media types when service flow data packets of multiple media types share the same QoS flow, which is beneficial to improving the resource utilization rate of processing service flow data packets and the user experience, so as to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

[0016] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1A schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied is shown;

[0018] Figure 2 A schematic diagram of the transmission process of a multimedia data packet according to an embodiment of the present application is shown;

[0019] Figure 3 A flowchart of a QoS processing method according to an embodiment of the present application is shown;

[0020] Figure 4 A flowchart of a QoS processing method according to an embodiment of the present application is shown;

[0021] Figure 5 A flowchart of a QoS processing method according to an embodiment of the present application is shown;

[0022] Figure 6 A schematic diagram of the architecture of key network elements in a 5G network is shown;

[0023] Figure 7 A flowchart of a QoS processing method according to an embodiment of the present application is shown;

[0024] Figure 8 A flowchart of a QoS processing method according to an embodiment of the present application is shown;

[0025] Figure 9 A block diagram of a QoS processing device according to an embodiment of the present application is shown;

[0026] Figure 10 A block diagram of a QoS processing device according to an embodiment of the present application is shown;

[0027] Figure 11 A block diagram of a QoS processing device according to an embodiment of the present application is shown;

[0028] Figure 12 A schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of the present application is shown. Detailed implementation manners

[0029] Now, the exemplary embodiments will be described in a more comprehensive manner with reference to the accompanying drawings. However, the exemplary embodiments can be implemented in various forms and should not be construed as being limited to these examples; on the contrary, these embodiments are provided so that the present application is more comprehensive and complete, and the concept of the exemplary embodiments is fully conveyed to those skilled in the art.

[0030] In addition, the features, structures, or characteristics described in this application may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to enable a thorough understanding of the embodiments of this application. However, those skilled in the art should recognize that when implementing the technical solutions of this application, not all the detailed features in the embodiments are required, one or more specific details may be omitted, or other methods, elements, devices, steps, etc. may be adopted.

[0031] In the embodiments of this application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one 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 a part of an overall module or unit that includes the function of that module or unit.

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

[0033] The flowcharts shown in the drawings are only illustrative and do not necessarily include all the content and operations / steps, nor are they necessarily executed in the described order. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.

[0034] It should be noted that: "a plurality of" mentioned in this article refers to two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0035] With the development of 5G and its subsequent evolved systems (such as 5G-A, 6G, etc.), many multimedia services that require large amounts of data and short delays have been applied. Such as cloud gaming services, interactive services such as VR, AR, MR, XR, and CR.

[0036] For example, in Figure 1In the cloud game scenario shown, the cloud server 101 is used to run cloud games. The cloud server 101 can render game scenes, encode the audio signals and the rendered images, and finally transmit the encoded data obtained through encoding to each game client via the network. The game client can be a user equipment (UE) with basic streaming media playback capabilities, human-computer interaction capabilities, communication capabilities, etc., such as a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart TV, a smart home device, a vehicle-mounted terminal, an aircraft, etc.; or the game client can be an application program running on a terminal device. Specifically, the game client can decode the encoded data transmitted by the cloud server 101 to obtain analog audio and video signals and play them.

[0037] It should be understood that Figure 1 only exemplarily represents the system architecture of the cloud game system and does not limit the specific architecture of the cloud game system; for example, in other embodiments, the cloud game system may further include a background server for scheduling, etc. And 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 network (CDN), and big data and artificial intelligence platforms. The game client and the cloud server 101 can be directly or indirectly connected through wired or wireless communication methods, and this application does not limit this.

[0038] In the above various application scenarios of multimedia-based interactive services, due to the huge size of multimedia data packets, they need to be split into multiple data packets for transmission during transmission. Specifically, as Figure 2 shown, taking the 5G system as an example, the user plane mainly includes an application server, a user plane function (UPF), a base station (next generation node B, gNB), and a UE. The transmission of multimedia data packets is mainly in the downlink direction for some typical service scenarios, 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 (taking the XR data packet as an example in Figure 2 ) is split at the application layer of the application server. After the split data packets reach the UPF as IP packets, the 5G system transmits the sub-packets to the UE side through a PDU session, and at the UE side, they are submitted step by step from the protocol stack and recombined to restore the multimedia data packet.

[0039] Among them, in the Figure 2 system shown, Layer L1 refers to the physical layer, which is used to ensure that the original data can be transmitted on various physical media; Layer L2 refers to the data link layer, and the data link layer 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 realize the data transfer between two end systems; UDP is the User Datagram Protocol, and its Chinese name is the User Datagram Protocol; GTP-U is the GPRS (General Packet Radio Service) Tunneling Protocol, and its Chinese name is the user plane of the General Packet Radio Service Tunneling Protocol; PHY is the abbreviation of Physical, and its Chinese name is the physical layer; MAC is the Media Access Control, and its Chinese name is the Media Access Control; RLC is the Radio Link Control, and its Chinese name is the radio link control layer protocol; PDCP is the Packet Data Convergence Protocol, and its Chinese name is the Packet Data Convergence Protocol; SDAP is the Service Data Adaptation Protocol, and its Chinese name is the Service Data Adaptation Protocol.

[0040] As mentioned above, for multimedia services (such as XRM services), it is a common situation to divide a frame of multimedia data packets into multiple data packets for transmission. The data packets formed by a single multimedia service frame or a group of packets (GoP) may also have a relatively large byte volume and need to be carried by a series of IP data packets. There is a certain correlation between these IP data packets, and processing these packets according to the correlation can effectively save the wireless network bandwidth.

[0041] For example, assume that during transmission, multiple IP data packets are used for transmission, and these multiple IP data packets can form a PDU set (PDU set). If some data packets in the PDU set are lost, it may cause the entire frame, GoP, or other video parts to be unable to be decoded, and then the remaining data in the PDU set is also meaningless to the decoding end. However, if application layer forward error correction (FEC) or other mechanisms are introduced and the media application layer has a certain packet loss recovery ability or packet loss resistance ability, then the remaining data in the PDU set can still be recovered and decoded after discarding some packets, which means that the remaining data in the PDU set is still meaningful for the receiving end to decode.

[0042] In addition, if different PDU sets are distinguished according to the correlation of application layer data packets in the QoS processing mechanism, then for PDU sets with high rates but tolerable packet loss rates or latency exceedance rates, processing can continue. In other words, the processing method for multimedia services can be more flexible. At the same time, the QoS flow mapping method used by the 5G System (5GS) may map different PDU sets to different QoS flows, or may map different PDU sets to the same QoS flow. However, regardless of which mapping method is used, the QoS processing granularity actually provided by 5GS is only the 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 supports for these multiple service flows, which is insufficient for supporting multi-modal multimedia service flows.

[0043] Based on the above problems, the technical solution of the embodiment of the present application proposes a new QoS processing solution, so that when service flow data packets of multiple media types share the same QoS flow, more fine-grained (i.e., finer than the QoS flow) QoS processing can be achieved for service data packets of different media types, thereby facilitating the improvement of the resource utilization rate and user experience of processing service flow data packets to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

[0044] The implementation details of the technical solution of the embodiment of the present application are elaborated in detail below:

[0045] Figure 3 The flowchart of the QoS processing method according to an embodiment of the present application is shown. This QoS processing method can be executed by an Application Function (AF) network element, or can also be executed by other network elements. Refer to Figure 3 As shown, this QoS processing method at least includes S310 to S320, which are introduced in detail as follows:

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

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

[0048] Optionally, the traffic flow data packets of these multiple media types may be included in a certain multimedia service. For example, in a cloud gaming service, there may be traffic flow data packets of audio type, traffic flow data packets of video type, and there may also be traffic flow data packets of tactile or other types, etc. Since these multiple media type traffic 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 type traffic flow data packets may have different QoS requirement information. Therefore, in the embodiments of the present application, more fine-grained (i.e., a finer granularity than the QoS flow) QoS processing can be provided.

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

[0050] Optionally, there may also be no correlation between the traffic flow data 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 a relatively large number of QoS flows, if no more QoS flows can be added to carry more traffic flow data packets, then the traffic flow data packets of multiple media types can be mapped to one QoS flow, that is, one QoS flow is used to carry the traffic flow data packets of multiple media types. And these traffic flow data packets of different media types may have different QoS requirement information. Therefore, in the embodiments of the present application, more fine-grained QoS processing can be provided.

[0051] It should be noted that the multimedia services in the embodiments of the present application may be, in addition to cloud gaming services and VR services, also AR services, MR services, XR services, XRM services, CR services, etc.

[0052] In some optional embodiments, service flow data packets can be transmitted in the form of a service data packet set (i.e., PDU set) when being transmitted. For example, a single service frame of a certain media type or a data packet formed by a GoP may have a relatively large byte volume and needs to be split into a series of data packets for carrying. These data packets are correlated with each other. Therefore, these correlated data packets can be called a PDU set and are transmitted in the form of a PDU set during transmission. For service flow data packets transmitted in the form of a PDU set, the QoS parameters in the corresponding QoS requirement information include at least one of the following parameters: PDU set delay budget (PDUSetDelayBudget, PSDB), PDU set error rate (PDU Set Error Rate, PSER), maximum data burst volume (MaximumDataBurstVolume, MDBV), packet delay variation / jitter (Packet Delay Variation, PDV).

[0053] Optionally, service flow data packets can also be transmitted not in the form of a PDU set but in the form of a single data packet (per-packet) when being transmitted. In this case, the QoS parameters in the corresponding QoS requirement information include at least one of the following parameters: packet delay budget (PacketDelayBudget, PDB), packet loss rate (Packet Error Rate, PER), maximum data burst volume, etc.

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

[0055] Continue to refer to Figure 3 As shown, in S320, the QoS requirement information corresponding to 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 multiple media types according to the QoS requirement information.

[0056] In some alternative embodiments, if traffic flow data packets of multiple media types are mapped to the same QoS flow for processing, then the traffic flow data packets can perform corresponding QoS processing according to the QoS requirements of the traffic flow data packets of different media types during the transmission process. In this case, devices such as UPF, base stations, and UEs that monitor the QoS of traffic flow data packets can identify the traffic flow data packets of different media types and perform corresponding QoS processing based on the traffic flow data packets of different media types.

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

[0058] Optionally, the differentiation method between traffic flow data packets of different media types can also be sent by network element devices such as AF or AS to the core network elements. For example, when sending the QoS requirement information corresponding to traffic flow data packets of multiple media types mapped to the same QoS flow to the core network elements, the differentiation method between these media type traffic flow data packets is sent to the core network elements together, or before or after sending the QoS requirement information corresponding to traffic flow data packets of multiple media types to the core network elements, the differentiation method between these media type traffic flow data packets is sent to the core network elements, so that the core network elements (such as the policy control function network element, session management function network element, etc.) can consider this differentiation method when generating QoS-related policies or rules, so that the traffic flow data packet processing devices (UEs, base stations, UFPs, etc.) can detect and distinguish traffic flow data packets of different media types according to the QoS-related policies or rules.

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

[0060] In some alternative embodiments, the method for differentiating service flow data packets of multiple media types is used to differentiate service flow data packets of different media types and can be used to identify service flow data packets of various media types.

[0061] Optionally, service flow data packets of multiple media types may be encapsulated by different media encapsulation methods. In this case, when providing the method for differentiating service flow data packets of multiple media types to the core network element, the media encapsulation methods corresponding to the service flow data packets of multiple media types may be provided to the core network element respectively.

[0062] In some alternative 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 different QUIC stream identifiers, or different QUIC connection identifiers and different QUIC stream identifiers.

[0063] In some alternative 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 differentiated using different payload types. It should be noted that different PayloadType (PT) values are used to indicate the media type included in the RTP packet, such as audio type, video type, etc. Optionally, dynamic PT values may also be used to indicate different media types.

[0064] In some alternative embodiments, the service flow data packets can be encapsulated using the Web Real-Time Communication (WebRTC) protocol. In this case, the service flow data packets of different media types can be differentially encapsulated using the protocol stack of the WebRTC protocol.

[0065] Optionally, the RTCPeerConnection (RTC peer connection) interface in the WebRTC protocol stack provides the function of establishing and maintaining an end-to-end connection, and processes the changes in the connection state and the transmission of media data through the events of RTCPeerConnection. Therefore, different transmission options, such as the transport protocol, transport layer port, etc., can be set in RTCPeerConnection to distinguish the data transmission of different media types. For another example, the RTCDataChannel (RTC data channel) interface in the WebRTC protocol stack provides the function of end-to-end arbitrary binary data transmission. Through RTCDataChannel, any type of data, including text, images, files, etc., can be sent and received. Therefore, different data type identifiers can be set for the data packets of different media types to facilitate the differentiation of the service flow data packets of different media types.

[0066] In some alternative embodiments, the service flow data packets can be encapsulated using WebTransport. In this case, the service flow data packets of different media types can be differentially encapsulated using the protocol stack of WebTransport.

[0067] Optionally, WebTransport supports multiple transport layer protocols, such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), etc. Therefore, different transport layer protocols can be specified in the signaling to distinguish the data of different media types in the protocol stack of WebTransport. For example, TCP can be used to transmit haptic data, while UDP can be used to transmit audio and video data.

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

[0069] For another example, the protocol stack of WebTransport supports multiple payload types, and each payload type corresponds to a specific media format or encoding method. By specifying different payload types in the signaling, data of different media types can be distinguished in the WebTransport protocol stack. For example, payload type 1 can be used to transmit audio data, while payload type 2 can be used to transmit video data.

[0070] For yet another example, WebTransport supports creating multiple data channels, and each channel can be used to transmit data of different media types. By specifying different data channels in the signaling, data of different media types can be distinguished in the WebTransport protocol stack. For example, channel 1 can be used to transmit tactile data, while channel 2 can be used to transmit audio-visual data.

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

[0072] In some alternative embodiments, when providing the QoS requirement information corresponding to the service flow data packets of multiple media types to the core network element, the QoS requirement information corresponding to the service flow data packets of multiple media types can be directly sent to the policy control function network element. Or the QoS requirement information corresponding to the service flow data packets of multiple media types can also be sent to the network exposure function network element, and then forwarded by the network exposure function network element to the policy control function network element. Or the service level agreement (SLA) can be negotiated with the policy control function network element to transfer the QoS requirement information corresponding to the service flow data packets of multiple media types to the policy control function network element.

[0073] Optionally, if it is necessary to send the differentiation method between the service flow data packets of multiple media types to the core network element, a similar method can also be adopted. That is, the differentiation method between the service flow data packets of multiple media types can be directly sent to the policy control function network element. Or the differentiation method between the service flow data packets of multiple media types can also be sent to the network exposure function network element, and then forwarded by the network exposure function network element to the policy control function network element. Or the service level agreement can be negotiated with the policy control function network element to transfer the differentiation method between the service flow data packets of multiple media types to the policy control function network element.

[0074] The above has described the technical solution of the embodiment of the present application from the perspective of the application function network element. The following further elaborates on 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: Figure 4 The flowchart of the QoS processing method according to an embodiment of the present application is shown. This QoS processing method can be executed by the policy control function network element, or can also be executed by other network elements. Refer to

[0075] Figure 4 As shown, this QoS processing method at least includes S410 to S430, and is introduced in detail as follows: Figure 4 As shown, this QoS processing method at least includes S410 to S430, and is introduced in detail as follows:

[0076] In S410, obtain the QoS requirement information respectively corresponding to the service flow data packets of multiple media types mapped to the same QoS flow.

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

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

[0079] It should be noted that: the relevant descriptions of the QoS requirement information and the differentiation method between the service flow data packets of different media types can refer to the technical solution of the foregoing embodiment, and will not be elaborated here.

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

[0081] In some alternative embodiments, the QoS policy information for processing traffic flow packets of multiple media types may include whether to map the traffic data flows of multiple media types to different QoS flows. For example, the traffic flow packets of multiple media types may include traffic flow packets of audio type, traffic flow packets of video type, traffic flow packets of tactile type, etc. Then, the QoS policy information for processing traffic flow packets of multiple media types may include whether to map the traffic flow packets of different media types to different QoS flows, that is, the traffic flow packets of various media types use separate QoS flows. Of course, the QoS policy information for processing traffic flow packets of multiple media types may directly include indication information for mapping the traffic flow packets of different media types to different QoS flows, or include indication information for not mapping the traffic flow packets of different media types to different QoS flows (such as mapping the traffic flow packets of different media types to the same QoS flow).

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

[0083] In some alternative embodiments, the QoS policy information for processing traffic flow packets of multiple media types may include the way to distinguish between the traffic flow packets of multiple media types. For example, since the importance information of the traffic packet set can be used to indicate the importance of the traffic flow packets of different media types, the importance information of the traffic packet set can be used to indicate the traffic flow packets of different media types. Or the traffic flow packets of different media types can also be indicated by the media encapsulation method. For example, in the foregoing embodiments, the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. are used for encapsulation to distinguish the traffic flow packets of different media types.

[0084] In some alternative embodiments, the QoS policy information for processing traffic flow packets of multiple media types may also include a combination of two or more of the above-mentioned information.

[0085] It should be noted that, in the embodiments of the present application, when transmitting service flow data packets of multiple media types, the PDU set method can be used for transmission, or the form of a single data packet can be used for transmission. For example, all service flow data packets of multiple media types can be transmitted using the PDU set method; or all can be transmitted in the form of a single data packet; or some service flow data packets of certain media types can be transmitted using the PDU set method, while other service flow data packets of certain media types are transmitted in the form of a single data packet.

[0086] 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 for the processing device of the service flow data packet according to the QoS policy information.

[0087] 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 can 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 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 (SMPolicyContextData IE).

[0088] Optionally, the process of the session management function network element configuring QoS processing related information for the processing device of the service flow data packet according to the QoS policy information can refer to the following Figure 5 illustrated embodiments.

[0089] Figure 5 shows a flowchart of a QoS processing method according to an embodiment of the present application. This QoS processing method can be executed by a session management function (Session Management Function, SMF) network element, or can also be executed by other network elements. Referring to Figure 5 shown, this QoS processing method at least includes S510 to S530, which are introduced in detail as follows:

[0090] In S510, receive the QoS policy information sent by the policy control function network element for processing service flow data packets of multiple media types. This QoS policy information is generated according to the QoS requirement information corresponding to the service flow data packets of multiple media types being mapped to the same QoS flow.

[0091] It should be noted that: When generating QoS policy information, the policy control function network element can also consider the differentiation method between service flow data packets of multiple media types, that is, the policy control function network element can generate QoS policy information according to the QoS requirement information corresponding to service flow data packets of multiple media types mapped to the same QoS flow respectively, and the differentiation method between service flow data packets of multiple media types. Optionally, the relevant descriptions of the QoS requirement information and the differentiation method between service flow data packets of different media types can refer to the technical solutions of the foregoing embodiments and will not be elaborated herein.

[0092] In S520, QoS processing-related information corresponding to various processing devices of the service flow data packets is generated according to the QoS policy information used to process the service flow data packets of multiple media types.

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

[0094] In some alternative embodiments, the session management function network element can generate a service data flow (SDF) template (SDFTemplate) corresponding to the user plane function network element for processing the service flow data packets according to the QoS policy information used to process the service flow data packets of multiple media types.

[0095] Optionally, the service data flow template may include a differentiation method between service flow data packets of multiple media types. Among them, the differentiation method between service flow data packets of multiple media types can be indicated by the importance information of the service data packet set. Or it can also indicate service flow data packets of different media types through the media encapsulation method. For example, in the foregoing embodiments, the QUIC protocol, the RTP protocol, the WebRTC protocol, the WebTransport protocol stack, etc. are used for encapsulation to differentiate service flow data packets of different media types.

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

[0097] Optionally, the service data flow template may include QoS parameter information corresponding to service flow data packets of multiple media types, so that 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 service flow data packets of different media types.

[0098] Optionally, the service data flow template may include two or all of the following: a way to distinguish 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 QoS parameter information corresponding to service flow data packets of multiple media types respectively.

[0099] In some alternative embodiments, the session management function network element may generate a QoS configuration file (QoS profiles) corresponding to the base station device for processing service flow data packets according to QoS policy information for processing service flow data packets of multiple media types.

[0100] Optionally, the QoS configuration file includes a way to distinguish between service flow data packets of multiple media types. Among them, the way to distinguish between service flow data packets of multiple media types may be indicated by the importance information of the service data packet set. Or different media types of service flow data packets may be indicated by the media encapsulation method. For example, in the foregoing embodiments, different media types of service flow data packets are encapsulated by means of the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. to distinguish them.

[0101] Optionally, when the base station device does not support processing service flow data packets of multiple media types with different QoS requirements in the same QoS flow, the QoS configuration file may indicate that the base station processes service flow data packets of multiple media types through different QoS flows. Specifically, indicating that the base station processes service flow data packets of multiple media types through different QoS flows may be to indicate that the base station maps service flow data packets of different media types to different QoS flows.

[0102] Optionally, if there is a correlation between the traffic flow data packets of multiple media types, for example, these traffic flow data packets of multiple media types may be included in a certain multimedia service. For example, in a cloud game service, there may be associated traffic flow data packets of the audio type, traffic flow data packets of the video type, and there may also be traffic flow data packets of the tactile type, etc. Another example is that these traffic flow data packets of multiple media types may also be included in multiple different multimedia services. For example, the cloud game service and the VR service are integrated to form a cloud game service with a virtual reality experience. Then there is also a certain correlation between these traffic flow data packets of multiple media types. Then when the QoS profile instructs the base station to process the traffic flow data packets of multiple media types through different QoS flows, it can further indicate the correlation between different QoS flows, so that through this indication information of the correlation, it is ensured that the associated traffic flow data packets can be processed associatively. For example, it can be achieved that the synchronization between the traffic data packets of different media types (such as the synchronization between the traffic flow data packets of the audio type and the traffic flow data packets of the video type) can be controlled.

[0103] Optionally, if the QoS profile instructs the base station to process the traffic flow data packets of multiple media types through different QoS flows, the QoS profile may also include maintaining the synchronization between the traffic flow data packets corresponding to different QoS flows through the PDU set delay budget or the packet delay budget. Among them, the PDU set delay budget is applicable to the synchronization between the traffic flow data packets transmitted in the PDUset manner; the packet delay budget is applicable to the synchronization between the traffic flow data packets transmitted in the packet manner.

[0104] Optionally, the QoS profile may include the QoS parameter information corresponding to the traffic flow data packets of multiple media types respectively, so that even if the traffic flow data packets of multiple media types are mapped to the same QoS flow, the QoS processing of the traffic flow data packets of different media types can be implemented according to the QoS parameter information corresponding to the traffic flow data packets of different media types.

[0105] Optionally, the QoS profile may also include a combination of two or more of the above information.

[0106] In some alternative embodiments, the session management function network element may generate QoS rule information (QoS rules) corresponding to the user equipment for processing traffic flow data packets according to the QoS policy information for processing traffic flow data packets of multiple media types.

[0107] Optionally, the QoS rule information may include a way to distinguish between traffic data packets of multiple media types. Among them, the way to distinguish between traffic data packets of multiple media types may be indicated by the importance information of the traffic data packet set. Or it may also indicate traffic data packets of different media types through the media encapsulation method. For example, in the foregoing embodiments, the QUIC protocol, RTP protocol, WebRTC protocol, WebTransport protocol stack, etc. are used for encapsulation to distinguish traffic data packets of different media types.

[0108] Optionally, the QoS rule information may include indication information for indicating mapping traffic data packets of multiple media types to the same QoS flow.

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

[0110] Optionally, the QoS rule information may include two or all of the way to distinguish between traffic data packets of multiple media types, the indication information for indicating mapping traffic data packets of multiple media types to the same QoS flow, and the QoS parameter information corresponding to traffic data packets of multiple media types respectively.

[0111] In S530, the QoS processing related information is configured to the processing device of the traffic data packet.

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

[0113] Specifically, taking the 5G system as an example, as Figure 6Shown is the key network element architecture of the 5G network defined by the 3rd Generation Partnership Project (3GPP). Among them, the Access and Mobility Management Function (AMF), SMF, UPF, PCF, Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Unified Data Management (UDM), etc. are the core network elements of the 5G network. The UE can be a 5G terminal such as a mobile phone or a tablet computer; the (R)AN ((Radio) Access Network) can be a 5G base station; the DN (Data Network) is the data network, that is, the service server accessed by the UE.

[0114] Among them, the AMF is responsible for terminating the N2 interface of the base station control plane and implementing the encoding and decoding of the Next Generation Application Protocol (NGAP) based on the Stream Control Transmission Protocol (SCTP). The base station and the AMF transmit the application layer NGAP protocol through the SCTP transport layer protocol and carry the non-access stratum (NAS) signaling data of the UE in the NGAP. The AMF is also responsible for terminating the N1 interface of the UE, implementing NAS encryption and integrity protection, and is responsible for functions such as UE access verification, authorization management, registration, connection, reachability, and mobility management, as well as for transparent transmission of session management messages between the UE and the SMF.

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

[0116] Based on Figure 6 the system architecture shown, 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 equipment.

[0117] It can be seen that for an application layer service flow that may include different media type PDU sets, the technical solution of the embodiment of the present application may use a finer-grained flow differentiation method than the five-tuple. Then, 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 data packets of different media types sharing a QoS flow to meet the QoS requirements of the service flow data packets of different media types.

[0118] Specifically, as Figure 7 shown, the QoS processing method according to an embodiment of the present application includes the following steps:

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

[0120] In some optional embodiments, if the multimedia service flow includes different media types (such as audio, video, haptic or other media types), then these media types can start or not start the PDUset mechanism, that is, they can choose whether to use the PDUset method for data transmission. And, the service flow data packets of these different media types can have different QoS requirements and different upper layer protocol encapsulation methods.

[0121] It should be noted that the QoS requirements provided for the media types that do not start the PDUset mechanism may include QoS parameters for data packets, such as PER, PDB, etc. And the QoS requirements provided for the media types that start the PDUset mechanism may include QoS parameters for the PDUset, such as PSDB, PSER, MDBV, PDV, etc.

[0122] Optionally, the QoS requirements provided for the media types that start the PDUset mechanism may 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 the PDUset are added to the QoS requirements. Of course, a new QoS requirement for the PDUset can also be used to include the QoS parameter information for the PDUset.

[0123] In some alternative embodiments, if the upper-layer protocol of the service flow data packet uses the QUIC protocol, such as RTP over QUIC, then service flow 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 as well.

[0124] In some alternative 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 by using different dynamic RTP protocol types (i.e., payload types). For example, 96 represents a video frame and 97 represents an audio frame.

[0125] In some alternative 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 setting different data type identifiers in the RTCPeerConnection.

[0126] In some alternative embodiments, if the service flow data packet is encapsulated using the WebTransport protocol stack, 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.

[0127] The AF can form auxiliary information according to the upper-layer protocol encapsulation method adopted by the service flow data packets of different media types and provide it to the 5GS, which is associated with the QoS requirements of the service flow data packets of different media types to support finer-grained QoS processing of the service flow data packets.

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

[0129] In some alternative embodiments, in order to reduce the amount of information exchanged between the AF and the 5G core network (5G Core, 5GC), the AF and the 5GC can also reflect the QoS requirement information of service flow data packets of different media types by negotiating the SLA. In this case, the SLA can include the QoS requirement information for service flow data packets of different media types.

[0130] It should be noted that in other embodiments of the present application, the AF may not provide the upper layer media type information and protocol bearer information to distinguish different media types. Instead, other network element devices can distinguish them by detecting the characteristics of traffic data packets of various media types (such as frame rate, resolution, data types included, etc.). Or the network element devices can also distinguish the traffic data packets of different media types in a pre-agreed manner.

[0131] S702, the PCF generates fine-grained PCC rules.

[0132] In some optional embodiments, after the AF sends the upper layer protocol encapsulation method adopted by the traffic data packets of different media types and the QoS requirements of the traffic 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 can generate the PCC rules required for finer-grained QoS processing according to the user's subscription information or the SLA with the AF, including but not limited to the following information:

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

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

[0135] In some optional embodiments, the QoS processing-related information generated by the SMF for the UPF can be an SDF Template, which includes the fine-grained identification and detection methods for the traffic data packets of different media types, including but not limited to (assuming the UPF has the identification and processing ability within the five-tuple):

[0136] 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 by using different QUIC connection IDs, or by using different stream IDs, or by using different QUIC connection IDs and different stream IDs.

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

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

[0139] If the upper-layer protocol of the service flow data packet uses the WebTransport protocol, then the 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.

[0140] In some alternative embodiments, the SDFTemplate generated by the SMF for the UPF may further include mapping rules for QoS flows, that is, mapping service flow data packets of different media types (indicating downlink data packets for the UPF) to the same QoS flow, and performing discrimination detection in the above manner.

[0141] In some alternative embodiments, the QoS processing-related information generated by the SMF for the NG-RAN 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, then the NG-RAN can still adopt QoS processing at the QoS flow granularity, but the QoS profiles may include correlation information between multiple QoS flows. In this case, the synchronization of data in different QoS flows can be ensured through the PSDB of the PDU set or the PDB per packet.

[0142] In some alternative embodiments, the QoS processing related information generated by the SMF for the UE can be QoS rules, which include fine-grained identification and detection methods for traffic flow data packets of different media types (specifically as described in the above embodiments), and can also include mapping rules for QoS flows, that is, mapping traffic flow data packets of different media types (referring to uplink data packets indicated for the UE) to the same QoS flow, and performing differentiated detection in the above manner.

[0143] S703, the SMF configures SDFTemplate, QoS profiles, and QoS rules for the UPF, NG-RAN, and the UE.

[0144] In some alternative embodiments, the SMF configures the SDFTemplate for the UPF through the N4 interface, which includes more fine-grained detection and QoS rules for traffic flow data packets of different media types, etc.

[0145] Meanwhile, the SMF configures QoS profiles for the NG-RAN through the AMF to support more fine-grained detection of traffic flow data packets of different media types; and the SMF configures more fine-grained detection and QoS rules for traffic flow data packets of different media types for the UE through the AMF+NAS connection.

[0146] S704, the UPF, NG-RAN, and the UE perform more fine-grained QoS processing.

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

[0148] The following refers to Figure 8 As shown, a specific example is used to elaborate in detail on the technical solution of the embodiment of the present application, which specifically includes the following steps:

[0149] S801. After the PDU session is successfully established, the AF performs signaling interaction with the 5G system (5GS) to indicate more fine-grained QoS requirements and the upper-layer protocol encapsulation method.

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

[0151] Optionally, the QoS processing-related information generated by the SMF for each device includes an SDF Template for the UPF, QoS profiles for the NG-RAN, and QoS rules for the UE.

[0152] S803. The 5GC configures the QoS processing-related information to the UPF, the base station, and the UE.

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

[0154] S804. The PDU set identification and marking are used to cooperate with the RAN to monitor and count for more fine-grained QoS rules.

[0155] S805. Process the PDU set in combination with more fine-grained QoS rules.

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

[0157] The technical solution of the embodiment of the present application proposes a more fine-grained traffic flow processing solution, which can perform fine-grained identification and processing on traffic flow packets of different media types in the case of sharing a QoS flow for traffic flow packets of different media types, so as to meet the QoS requirements of traffic flow packets of different media types, and further improve resource utilization when the 5GS bears services such as XRM that include traffic flow packets of multiple media types, so as to better support immersive XRM services.

[0158] The following introduces the device embodiments of the present application, which can be used to execute the QoS processing method in the above embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the embodiments of the QoS processing method above of the present application.

[0159] Figure 9 The block diagram of a QoS processing device according to an embodiment of the present application is shown. The QoS processing device can be applied to an AF or other network elements.

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

[0161] Among them, the generating unit 902 is configured to generate QoS requirement information respectively corresponding to service 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 respectively corresponding to the service flow data packets of the multiple media types to a 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.

[0162] In some embodiments of the present application, based on the foregoing solution, the sending unit 904 is further configured to: provide the differentiation method between the service flow data packets of the multiple media types to the core network element, so that the core network element generates QoS policy information corresponding to the multiple media types according to the differentiation method and the QoS requirement information.

[0163] In some embodiments of the present application, based on the foregoing solution, the service flow data packets of the multiple media types are encapsulated by different media encapsulation methods; the sending unit 904 is configured to: provide the media encapsulation methods respectively corresponding to the service flow data packets of the multiple media types to the core network element.

[0164] In some embodiments of the present application, based on the foregoing solution, the service flow data packets are encapsulated by at least one of the following media encapsulation methods:

[0165] Encapsulated using the Quick UDP Internet Connections (QUIC) protocol, and service flow data packets of different media types use different QUIC connection identifiers and / or different QUIC stream identifiers;

[0166] Encapsulated using the Real-Time Transport Protocol (RTP), and service flow data packets of different media types use different payload types;

[0167] Encapsulated in a differentiated manner using the protocol stack of the Web Real-Time Communication (WebRTC) protocol;

[0168] Encapsulated in a differentiated manner using the protocol stack of the WebTransport protocol for network transmission.

[0169] In some embodiments of the present application, based on the foregoing solution, the service flow data packets of the multiple media types are respectively transmitted in the form of a service data packet set; wherein, 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) set delay budget, PDU set bit error rate, maximum data burst volume, and packet delay jitter.

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

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

[0172] 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 by negotiating a service level agreement with the policy control function network element.

[0173] Figure 10 The block diagram of a QoS processing device according to an embodiment of the present application is shown. The QoS processing device can be applied to a policy control function network element or other network elements.

[0174] Refer to Figure 10 As shown, a QoS processing device 1000 according to an embodiment of the present application includes: an obtaining unit 1002, a generating unit 1004, and a sending unit 1006.

[0175] Among them, the obtaining unit 1002 is configured to obtain the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types mapped to the same QoS flow; the generating unit 1004 is 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 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 for the processing device of the service flow data packets according to the QoS policy information.

[0176] In some embodiments of the present application, based on the foregoing solution, the obtaining unit 1002 is further configured to: obtain the differentiation method between the service flow data packets of the multiple media types; the generating unit 1004 is configured to: generate QoS policy information for processing the service flow data packets of the multiple media types according to the differentiation method and the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types.

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

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

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

[0180] The differentiation method between the service flow data packets of the multiple media types.

[0181] In some embodiments of the present application, based on the foregoing solution, the differentiation method between the service flow data packets of the multiple media types is indicated by at least one of the following methods: indicating the service flow data packets of different media types through the importance information of the service data packet set; indicating the service flow data packets of different media types through the media encapsulation method.

[0182] Figure 11 The block diagram of a QoS processing device according to an embodiment of the present application is shown. The QoS processing device can be applied to a session management function network element or other network elements.

[0183] Refer to Figure 11 As shown, a QoS processing device 1100 according to an embodiment of the present application includes: a receiving unit 1102, a generating unit 1104, and a transmitting unit 1106.

[0184] Among them, the receiving unit 1102 is configured to receive the policy information for performing QoS processing on the service flow data packets of multiple media types sent by a policy control function network element, and the policy information is generated according to the QoS requirement information respectively corresponding to the service 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 respectively corresponding to various processing devices of the service flow data packets according to the policy information; the transmitting unit 1106 is configured to configure the QoS processing related information to the processing devices of the service flow data packets.

[0185] In some embodiments of the present application, based on the foregoing solution, the generating unit 1104 is configured to: generate a service data flow template corresponding to a user plane function network element for processing the service flow data packet according to the policy information, where the service data flow template includes at least one of the following information: a distinguishing method between service flow data packets of the multiple media types; indication information indicating mapping service flow data packets of the multiple media types to the same QoS flow; QoS parameter information corresponding to service flow data packets of the multiple media types respectively.

[0186] In some embodiments of the present application, based on the foregoing solution, the generating unit 1104 is configured to: generate a QoS configuration file corresponding to a base station device for processing the service flow data packet according to the policy information, where the QoS configuration file includes at least one of the following information:

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

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

[0189] If the base station device does not support processing service flow data packets of multiple media types with different QoS requirements in the same QoS flow, it is indicated that the base station processes the service flow data packets of the multiple media types through different QoS flows, and the correlation between the different QoS flows is indicated.

[0190] In some embodiments of the present application, based on the foregoing solution, 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 further includes maintaining synchronization between service flow data packets corresponding to the different QoS flows through PDU set delay budget or packet delay budget.

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

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

[0193] Indication information indicating mapping service flow data packets of the multiple media types to the same QoS flow;

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

[0195] Figure 12 FIG. 1200 shows a schematic structural diagram of a computer system of an electronic device suitable for implementing the embodiments 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 foregoing embodiments.

[0196] It should be noted that Figure 12 the computer system 1200 of the electronic device shown is only an example, and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

[0197] As Figure 12 shown, the computer system 1200 may include a central processing unit (CPU) 1201, which may 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 section 1208 into the random access memory (RAM) 1203, such as executing the methods described in the foregoing embodiments. In the RAM 1203, various programs and data required for system operation are also stored. The CPU 1201, ROM 1202, and RAM 1203 are connected to each other via a bus 1204. The input / output (I / O) interface 1205 is also connected to the bus 1204.

[0198] The following components may be connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a local area network (LAN) card, a modem, etc. 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 required. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as required, so that the computer program read from it can be installed into the storage section 1208 as required.

[0199] 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 execute the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and / or installed from the removable medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, various functions defined in the system of the present application are executed.

[0200] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium that contains or stores a computer program, and the computer program can be used by or combined with an instruction execution system, apparatus, or device. In the present application, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable computer program. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium can send, propagate, or transmit a program for use by or combined with an instruction execution system, apparatus, or device. The computer program included on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0201] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the above-mentioned module, program segment, or part of 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 boxes may occur in a different order from that marked in the accompanying drawings. For example, two consecutive boxes shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, as well as the combination of boxes in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and a computer program.

[0202] The units involved in the embodiments described in the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not, in some cases, constitute a limitation on the unit itself.

[0203] On the other hand, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The above computer-readable medium carries one or more computer programs, and when the above one or more computer programs are executed by an electronic device, the electronic device implements the method described in the above embodiments.

[0204] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, such a division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0205] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software or by a combination of software and necessary hardware. Therefore, the technical solutions 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 (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable an electronic device to execute the method according to the embodiments of the present application.

[0206] For example, the electronic device may be an application function network element, and then the application function network element may execute Figure 3 the QoS processing method shown; again, the electronic device may be a policy control function network element, and then the policy control function network element may execute Figure 4 the QoS processing method shown; furthermore, the electronic device may be a session management function network element, and then the session management function network element may execute Figure 5 the QoS processing method shown.

[0207] After considering the specification and practicing the disclosed embodiments herein, those skilled in the art will readily conceive of other embodiments of the present application. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present application.

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

Claims

1. A method for processing Quality of Service (QoS), characterized in that, Including: Generating QoS requirement information corresponding to the service flow data packets of multiple media types mapped to the same QoS flow respectively; Providing the QoS requirement information corresponding to the service flow data packets of the multiple media types to a 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, wherein The method further includes: Providing the differentiation method between the service flow data packets of the multiple media types to the core network element, so that the core network element generates QoS policy information corresponding to the multiple media types according to the differentiation method and the QoS requirement information.

3. The method according to claim 2, characterized in that The service flow data packets of the multiple media types are encapsulated by different media encapsulation methods; Providing the differentiation method between the service flow data packets of the multiple media types to the core network element includes: providing the media encapsulation methods corresponding to the service flow data packets of the multiple media types to the core network element.

4. The method according to claim 3, characterized in that, The service flow data packets are encapsulated by at least one of the following media encapsulation methods: Encapsulating using the Quick UDP Internet Connections (QUIC) protocol, and the service flow data packets of different media types use different QUIC connection identifiers and / or different QUIC stream identifiers; Encapsulating using the Real-time Transport Protocol (RTP), and the service flow data packets of different media types use different payload types; Performing differential encapsulation using the protocol stack of the Web Real-Time Communication (WebRTC) protocol; Performing differential encapsulation using the protocol stack of the WebTransport for network transmission.

5. The method according to claim 1, characterized in that, The service flow data packets of the multiple media types are transmitted respectively in the form of service data packet sets; Among them, 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) set delay budget, PDU set bit error rate, maximum data burst volume, packet delay jitter.

6. The method according to any one of claims 1 to 5, characterized in that Providing the QoS requirement information corresponding to the service flow data packets of the multiple media types to the core network element includes: Directly sending the QoS requirement information corresponding to the service flow data packets of the multiple media types to a Policy Control Function (PCF) network element; or Sending the QoS requirement information corresponding to the service flow data packets of the multiple media types to a Network Exposure Function (NEF) network element, so that the NEF network element forwards it to the PCF network element; or Negotiating a Service Level Agreement (SLA) with the PCF network element to provide the QoS requirement information corresponding to the service flow data packets of the multiple media types to the PCF network element.

7. A QoS processing method, characterized in that, Including: Obtaining the QoS requirement information corresponding to the service flow data packets of multiple media types mapped to the same QoS flow respectively; Generating QoS policy information for processing the service flow data packets of the multiple media types according to the QoS requirement information corresponding to the service flow data packets of the multiple media types; 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 for 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 includes: obtaining a differentiation method between service flow data packets of the multiple media types; Generate QoS policy information for processing 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, including: generate QoS policy information for processing service flow data packets of the multiple media types according to the differentiation method and the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types.

9. The method according to claim 7, wherein The QoS policy information for processing service flow data packets of the multiple media types includes at least one of the following information: Whether to map service flow data packets of the multiple media types to different QoS flows; Whether to map service flow data packets of the multiple media types to the same QoS flow; The differentiation method between service flow data packets of the multiple media types.

10. The method according to claim 9, wherein Indicate the differentiation method between service flow data packets of the multiple media types through at least one of the following methods: Indicate service flow data packets of different media types through the importance information of the service data packet set; Indicate service flow data packets of different media types through the media encapsulation method.

11. A QoS processing method, characterized in that, Include: Receive QoS policy information for processing service flow data packets of multiple media types sent by the policy control function network element, where the QoS policy information is generated according to the QoS requirement information respectively corresponding to the service flow data packets of the multiple media types mapped to the same QoS flow; Generate QoS processing-related information respectively corresponding to various processing devices of the service flow data packet according to the QoS policy information; Configure the QoS processing-related information to the processing device of the service flow data packet.

12. The method according to claim 11, wherein, Generate QoS processing-related information respectively corresponding to various processing devices of the service flow data packet according to the QoS policy information, including: Generate a service data flow template corresponding to the user plane function network element for processing the service flow data packet according to the QoS policy information, where the service data flow template contains at least one of the following information: The differentiation method between service flow data packets of the multiple media types; An indication information for indicating that service flow data packets of the multiple media types are mapped to the same QoS flow; The QoS parameter information respectively corresponding to service flow data packets of the multiple media types.

13. The method according to claim 11, characterized in that, Generate QoS processing-related information respectively corresponding to various processing devices of the service flow data packet according to the QoS policy information, including: Generate a QoS configuration file corresponding to the base station device for processing the service flow data packet according to the QoS policy information, where the QoS configuration file contains at least one of the following information: The differentiation method between service flow data packets of the multiple media types; The QoS parameter information respectively corresponding to service flow data packets of the multiple media types; If the base station device does not support processing service flow data packets of multiple media types with different QoS requirements in the same QoS flow, it is indicated that the base station processes the service flow data 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, wherein 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 further includes maintaining synchronization between the service flow data packets corresponding to the different QoS flows through PDU set delay budget or packet delay budget.

15. The method according to claim 11, wherein Generate QoS processing related information corresponding to each type of processing device for 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 packets according to the QoS policy information, and the QoS rule information includes at least one of the following information: The differentiation method between the service flow data packets of the multiple media types; The indication information used to indicate mapping the service flow data packets of the multiple media types to the same QoS flow; The QoS parameter information corresponding to the service flow data packets of the multiple media types respectively.

16. A QoS processing device, characterized in that, Including: A generating unit, configured to generate QoS requirement information corresponding to the service flow data packets of multiple media types mapped to the same QoS flow respectively; A sending unit, configured to provide the QoS requirement information corresponding to the service flow data packets of the multiple media types respectively 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.

17. A QoS processing device, characterized in that, Including: An obtaining unit, configured to obtain the QoS requirement information corresponding to the service flow data packets of multiple media types mapped to the same QoS flow respectively; 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 corresponding to the service flow data packets of the multiple media types respectively; A sending unit, 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 for the processing device of the service flow data packets according to the QoS policy information.

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

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

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

Images