QoS (Quality of Service) fine-grained configuration method and device and medium
By introducing the Service Data Adaptation Protocol (SDAP) sublayer and triplet rules into the 5G network, the QoS flow is refined into multiple QoS subflows, which solves the problem of the existing 5G network QoS control framework being too coarse and achieves more efficient resource utilization and improved user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-07
- Publication Date
- 2026-04-14
AI Technical Summary
The existing 5G network QoS control framework is based on QoS flow, which is too coarse-grained and makes it difficult to distinguish between different sub-services. This results in insufficient utilization of network resources, difficulty in implementing differentiated services, and impact on user experience.
By introducing the Service Data Adaptation Protocol (SDAP) sublayer, and combining core network functional entities, application service entities, and user plane functional units (UPF), the QoS flow is refined into multiple QoS sub-flows using triple rules and service tags, thereby achieving fine-grained control.
It improves the efficiency of network resource utilization, meets the specific needs of different services, reduces lag and latency, enhances user experience, and adapts to complex and ever-changing communication requirements.
Smart Images
Figure CN121865334A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of wireless communication technology, and specifically relates to a QoS fine-grained configuration method, apparatus and medium. Background Technology
[0002] The widespread adoption of smart terminals and the development of information technology have led to a rapid increase in 5G network traffic and service types. In complex and diverse service data environments, 5G networks need to support numerous mobile applications and services while ensuring Quality of Service (QoS). Current 5G QoS control frameworks, based on QoS flows, are too coarse-grained and lack flexibility, making it difficult to distinguish different sub-services within a QoS flow. This results in insufficient utilization of network resources, difficulty in implementing differentiated services, and negatively impacts user experience.
[0003] Current 5G networks primarily rely on QoS streams to manage network resources. QoS streams allow the network to allocate different bandwidths and priorities based on service demands. For example, in video streaming services, the network assigns higher priority to video data to reduce buffering and latency. However, this approach typically merges multiple IP streams into a single QoS stream, making fine-grained control over individual IP streams difficult.
[0004] To address the aforementioned issues, 5G New Radio introduced the Service Data Adaptation Protocol (SDAP) sublayer to support QoS flow implementation. SDAP is responsible for mapping between IP flows and QoS flows, ensuring that data packets are transmitted according to predetermined QoS rules. While this increases network flexibility, it still appears insufficiently granular when facing complex and ever-changing service requirements.
[0005] Therefore, a fine-grained QoS configuration method is needed that can reduce coarse granularity and adapt to complex and ever-changing communication requirements. Summary of the Invention
[0006] This application provides a fine-grained QoS configuration method, including, The core network functional entity sends a QoS enable notification to the core network storage management entity; The core network functional entity obtains triple rules, specifically the triple rule information established by the core network storage management entity. The triple rules established by the core network storage management entity are created by uploading QoS configuration information and a triple rule establishment request to the core network storage management entity through the application service entity; the QoS configuration information includes service tags. The core network functional entity generates a QoS parameter set containing service labels based on the triplet rules and sends it to the user plane function UPF.
[0007] Furthermore, the application service entity uploads QoS configuration information to the application function AF. The application function AF receives the QoS configuration information and initiates a triple rule establishment request to the core network storage management entity.
[0008] Furthermore, the core network functional entity is equipped with a Network Exposure Function (NEF), which receives triple rule establishment requests initiated by the Application Function (AF).
[0009] Furthermore, the core network storage management entity includes a unified data management unit (UDM) and a unified data storage unit (UDR). The unified data management unit (UDM) receives requests from the network exposure function (NEF) to store triple rules. The unified data management unit (UDM) establishes triple rules based on QoS configuration information and writes the triple rules into the unified data storage unit (UDR).
[0010] Furthermore, the core network functional entity obtains the triple rule establishment request initiated by the application function (AF) and queries the unified data management (UDM) to establish the triple rule.
[0011] Furthermore, the QoS fine-grained control and optimization method also includes the application service entity obtaining the QoS configuration submission results submitted to the Network Exposure Function (NEF).
[0012] Furthermore, the core network functional entity generates QoS parameters containing service labels based on the triplet rules and sends them to the user plane function UPF, including the following steps: The core network functional entity obtains requests from the application service entity stored in the core network storage management entity; The core network functional entity obtains the triplet rules based on the request from the application service entity; The core network functional entity generates a QoS parameter set containing service labels according to the triplet rules and sends it to the session management function (SMF). The Session Management Function (SMF) sends a set of QoS parameters containing service labels to the User Plane Function (UPF).
[0013] Furthermore, the QoS configuration information also includes the IP 5-tuple and QoS requirements.
[0014] This application also provides a QoS fine-grained configuration device, including, The issuing device, the core network functional entity, issues a QoS enable notification to the core network storage management entity; The acquisition device, the core network functional entity acquires triplet rules, wherein the core network functional entity acquires triplet rule information established by the core network storage management entity. The triplet rules established by the core network storage management entity are established by uploading QoS configuration information and triplet rule establishment requests to the core network storage management entity through the application service entity; the QoS configuration information contains service tags. The generation device, the core network functional entity, generates a QoS parameter set containing service labels according to the triplet rules and sends it to the user plane function UPF.
[0015] This application also provides a QoS fine-grained configuration apparatus, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described above.
[0016] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described above.
[0017] Beneficial effects: 1. The QoS fine-grained configuration method of the present invention sends a QoS enable notification to the core network storage management entity through the core network functional entity; the core network functional entity obtains triple rules, wherein the core network functional entity obtains triple rule information established by the core network storage management entity. The triple rules established by the core network storage management entity are established by uploading QoS configuration information and a triple rule establishment request to the core network storage management entity through the application service entity; the QoS configuration information includes service tags; the core network functional entity generates a QoS parameter set containing service tags according to the triple rules and sends it to the user plane function UPF. By adding a series of processing logic based on service tags, the core network user is given the ability to recognize user traffic data, so as to make intelligent decisions on the air interface side or between the central / edge user plane functions. The introduction of service tags strengthens the collaboration between service providers and network operators, enabling service providers to participate more directly in the management and optimization of network resources.
[0018] 2. The QoS configuration information in the fine-grained QoS configuration method of the present invention also includes IP 5-tuples and QoS requirements. The synergistic effect of IP 5-tuples and service tags allows for the direct determination of the corresponding QoS Flow Identifier (QFI) based on the service tag for traffic carrying the service tag, thereby providing finer-grained QoS control for these traffic flows. By subdividing the QoS flow into multiple QoS sub-flows through the synergistic effect of IP 5-tuples and service tags, the present invention can more accurately allocate network resources to meet the specific needs of different services, thereby improving the utilization efficiency of network resources. Due to the use of service tags to achieve refined QoS control, the present invention can provide priority protection for critical services, reduce lag and latency, and significantly improve user experience. The present invention can adapt to the diverse needs of different application scenarios, providing highly personalized service quality for different services and meeting the diverse service objectives of 5G networks.
[0019] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description and the accompanying drawings. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 A schematic diagram of the interaction process of the QoS fine-grained configuration method in an embodiment of this application is shown.
[0022] Figure 2 A flowchart illustrating the QoS fine-grained configuration method in an embodiment of this application is shown.
[0023] Figure 3 A flowchart of the QoS fine-grained configuration device in Embodiment 3 of this application is shown.
[0024] Figure 4 A flowchart of the QoS fine-grained configuration device in Embodiment 4 of this application is shown. Detailed Implementation
[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0026] This disclosure provides a fine-grained configuration method, apparatus, and computer storage medium for QoS flows to match service traffic characteristics and terminal power consumption management, thereby ensuring service requirements and user experience.
[0027] According to an aspect of the present disclosure, a method for fine-grained configuration of a quality of service (QoS) flow is provided, which can be applied to a core network function entity in a communication system, such as a policy control function (PCF) entity. The application service entity includes an application service provider (ASP) and an application function (AF); the core network storage management entity includes a unified data management (UDM) and a unified data repository (UDR).
[0028] Embodiment 1 Reference Figure 1 , a QoS fine-grained configuration method includes: The core network function entity sends a notification to enable QoS to the core network storage management entity; The core network function entity obtains a triple rule. Among them, the core network function entity obtains the triple rule information established by the core network storage management entity. The triple rule established by the core network storage management entity is established by uploading QoS configuration information and a triple rule establishment request to the core network storage management entity through the application service entity; the business label is included in the QoS configuration information; The core network function entity generates a QoS parameter set containing the business label according to the triple rule and sends it to the user plane function (UPF).
[0029] By adding a series of processing logics based on the business label, the core network user plane is given the ability to recognize user traffic data, so as to make intelligent decisions between the air interface side or the central / edge user plane functions later. It includes supporting the call of the open network element function interface, communicating with the external application service provider (ASP), and managing the triple configuration file <IP quintuple, business label, quality of service (QoS) requirement>; the business label is easy to define and set, which is convenient for the application service provider (ASP) to insert and is also convenient for the core network to identify; the control plane network element UDM (unified data management) can store and maintain the business label triples uploaded by the application service provider; the policy control function (PCF), session management function (SMF) (Session Management Function), etc. can allocate appropriate QoS flows for the current protocol data unit session according to the business label triples; the user plane function supports real-time identification of the packet business label.
[0030] By introducing the business label, the cooperation between the service provider and the network operator is strengthened, enabling the service provider to more directly participate in the management and optimization of network resources.
[0031] Protect a method for mapping service labels to QoS requirements, and a specific technical implementation for embedding these service labels into data streams, including defining the correspondence between service labels and QoS parameters, and a mechanism for embedding service labels in data packets.
[0032] Furthermore, the application service entity uploads QoS configuration information to the application function AF. The application function AF receives the QoS configuration information and initiates a triple rule establishment request to the core network storage management entity.
[0033] Furthermore, the core network functional entity is equipped with a network exposure function (NEF), which receives triple rule establishment requests initiated by the application function (AF).
[0034] Furthermore, the core network storage management entity includes a unified data management unit (UDM) and a unified data storage unit (UDR). The unified data management unit (UDM) receives a request from the network exposure function (NEF) to store triple rules. The unified data management unit (UDM) establishes triple rules based on QoS configuration information and writes the triple rules into the unified data storage unit (UDR).
[0035] Furthermore, the core network functional entity obtains the triple rule establishment request initiated by the application function (AF); the core network functional entity queries the unified data management (UDM) to establish triple rules.
[0036] Furthermore, the QoS fine-grained control and optimization method also includes the application service entity obtaining the QoS configuration submission results submitted to the Network Exposure Function (NEF).
[0037] Furthermore, the core network functional entity generates QoS parameters containing service labels according to the triplet rules and sends them to the user plane function UPF, including the following steps: The core network functional entity obtains the request of the application service entity stored in the core network storage management entity; the core network functional entity obtains the triple rule according to the request of the application service entity; the core network functional entity generates a QoS parameter set containing service labels according to the triple rule and sends it to the session management function (SMF); the session management function (SMF) sends the QoS parameter set containing service labels to the user plane function (UPF).
[0038] Furthermore, the QoS configuration information also includes the IP 5-tuple and QoS requirements.
[0039] The synergistic effect of the IP five-tuple and the service label. For traffic carrying a service label, the corresponding QoS flow identifier QFI can be directly determined according to its service label, thereby providing finer-grained QoS control for this traffic; by subdividing the QoS flow into multiple QoS sub-flows through the synergistic effect of the IP five-tuple and the service label, the present invention can more accurately allocate network resources, meet the specific requirements of different services, and thus improve the utilization efficiency of network resources.
[0040] Due to the implementation of refined QoS control by setting service labels, the present invention can provide priority guarantee for key services, reduce lag and latency, and significantly improve the user experience.
[0041] The present invention can adapt to the diverse requirements of different application scenarios, provide highly personalized quality of service for different services, and meet the diverse service objectives of 5G networks.
[0042] Embodiment 2 The present invention proposes a QoS fine-grained configuration method, which subdivides a QoS flow into several QoS sub-flows according to the QoS requirements of data packets. In this method, the application service provider APS negotiates with the core network to clarify the specific QoS requirements of the application scenario. This includes the bandwidth, latency, reliability, and other key metrics of the application. These requirements are translated into service labels and then embedded in the transmitted data stream to indicate the required quality of service. The core network comprehensively considers the information of these service labels and the Internet protocol five-tuple, and jointly decides to allocate appropriate QoS flow identifiers, and then different resources can be allocated according to the QoS flow identifiers between the user plane functions and on the air interface side, providing highly personalized quality of service for different application scenarios.
[0043] Before data is sent, the application service provider ASP interacts with the core network control plane (core network storage management entity) and uploads a triple configuration file containing <IP five-tuple, service label, quality of service QoS requirements>. This configuration enables the core network to allocate appropriate network resources for different data traffic according to the QoS requirements of the application service provider ASP, ensuring transmission efficiency and quality.
[0044] After the protocol data unit PDU session is established, when the application service provider ASP communicates with the user UE, it can actively insert the service label into the data packet, enabling the user plane function UPF to perceive the service label when processing and forwarding traffic, realizing data traffic identification and priority division within the core network, and thus refining QoS control.
[0045] The core network control plane (including Network Exposure Function (NEF), Core Network Storage Management Entity, Core Network Function Entity, and Session Management Function (SMF)) acts as both the communicator between the Application Service Provider (ASP) and the core network, and the manager of QoS configuration information. The core network control plane first receives the triplet configuration file uploaded by the ASP through an open interface. Then, it coordinates with network elements such as the Policy Control Function (PCF) and Session Management Function (SMF) to parse the configuration and generate the final QoS configuration file. These files specify in detail the processing methods for each data flow, including assigning QoS Flow Identifier (QFI) values to specified service traffic. The control plane also interacts with the air interface through the Access and Mobility Management Function (AMF) to guide the Radio Access Network (RAN) in allocating radio resources according to the issued QoS policies, thereby optimizing the user experience.
[0046] Application Service Providers (ASPs) need to create triplet configuration rules before establishing a Protocol Data Unit (PDU) session. Application Functions (AFs) and Network Exposure Functions (NEFs) act as bridges between the 5G network and external applications. If an AF is a trusted AF within the operator, it can communicate directly with network elements such as the Coordinating Policy Control Function (PCF); otherwise, it needs to forward requests to the core network through the NEF. The ASP transmits the triplet configuration file to the core network via the AF, which is ultimately structured and stored by the Unified Data Storage Unit (UDR), which then returns the execution results. The PCF needs to subscribe to the Unified Data Storage Unit (UDR) to receive AF request information; the specific process is as follows (see reference). Figure 2 ): S1: The Collaborative Policy Control Function (PCF) enables QoS notification control and requests notifications from the application function AF through the User Data Management (UDM) subscription service, unified data storage (UDR) application function. S2: After receiving the QoS configuration information from the application service provider ASP, the application function AF calls the NEF session QoS interface to initiate a triplet configuration rule establishment request to the network exposure function NEF. S3: Network Exposure Function (NEF) creates services through User Data Management (UDM) and creates and stores new rules in Unified Data Storage (UDR); S4: The Network Exposure Function (NEF) returns a request to the Application Function (AF) and receives a response; S5: The Unified Data Storage UDR notifies the subscribed Collaborative Policy Control Function (PCF) of the Application Function AF request; S6: The Collaborative Policy Control Function (PCF) obtains application function (AF) requests from the Unified Data Storage (UDR) through the User Data Management (UDM) query service. S7: Protocol Data Unit (PDU) session establishment. When the Cooperative Policy Control Function (PCF) generates Policy and Charging Control (PCC) rules, it derives a QoS parameter set containing service label definitions for charging control based on the QoS reference parameters and sends it to the Session Management Function (SMF). The SMF converts the received policy context data into executable configurations for the User Plane Function (UPF) and distributes them. The UPF then processes the data stream accordingly.
[0047] When a Protocol Data Unit (PDU) session has been established and the Application Service Provider (ASP) triggers a rule update, the system employs a Dynamic Billing Control (PCC) rule mechanism: the Cooperative Policy Control Function (PCF) immediately deletes the old rules upon detecting a change in the Application Function (AF) service, and issues new rules through the PDU session modification process. This mechanism enables operators to dynamically optimize resource allocation based on real-time network status, user behavior, and service demands, providing more personalized and flexible network services.
[0048] When a data packet arrives at the user plane, the User Plane Function (UPF) identifies the IP packet through the Packet Forwarding Control Protocol (PFCP) session. Each PFCP session is configured with a Packet Inspection Rule (PDR). The UPF matches PDRs sequentially from highest to lowest priority until a rule matching the incoming data packet is found. The PDR contains Packet Inspection Information (PDI), which is identified by information element identifiers and matched against packet header fields. A successful match is confirmed when all fields of the data packet match the specified fields in the PDI. By adding service tags to the PDI matching fields, traffic identification becomes more accurate. After a successful match, the UPF processes the traffic according to the service flow template associated with the PDR. The introduction of service tags allows each service flow template to correspond to a more granular QoS flow, ensuring that data packets receive accurate QoS processing according to their service requirements.
[0049] Service tag configuration: Service tags are a key component of the fine-grained QoS control framework, with each tag representing a specific set of QoS requirements. These tags allow the previously coarse-grained QoS flow to be refined into several more granular sub-QoS flows, thereby providing more refined services. In this method, service tags are embedded in the Differentiated Services Code Point (DSCP) field of the IP header. The DSCP field contains 6 bits, theoretically allowing for the definition of 64 different service tags, each representing a specific QoS service requirement. For known common traffic types, recommended DSCP values can be used for definition. For special QoS service requirements that cannot be represented using common DSCP values, the DSCP field can be defined using the format 0bxxxx10, where the last two bits are fixed at 10. Through this method, service providers (ASPs) can further customize and define specific service tags. This method not only improves the flexibility of network traffic management but also meets the fine-grained QoS requirements of specific applications, enabling more dynamic and flexible network traffic and QoS management to adapt to diverse network application needs.
[0050] QoS Flow Design: In the existing 5G QoS framework, QoS flow represents the smallest granularity of QoS control. With the introduction of service labels, support for service labels needs to be added to the existing data structure. This involves several key files for QoS flow configuration: QoS rules, QoS data configuration, and Service Data Flow Template (SDF) template. The generation of these files depends on the Policy Context data received by the Session Management Function (SMF) from the Policy Control Function (PCF). The SDF template is transmitted from the SMF to the User Plane Function (UPF) via the N4 interface using Packet Forwarding Control Protocol (PFCP) messages. The priority value of the UPF template is consistent with the priority value of the Policy and Charging Control (PCC) rule that generated the SDF template. The QoS configuration file is transmitted by the SMF to the next base station (gNB) via the N2 interface through the Access and Mobility Management Function (AMF), dividing the QoS flow into Guaranteed Bit Rate (GBR) flows and Non-Guaranteed Bit Rate (Non-GBR) flows. QoS rules are transmitted to the User Equipment (UE) via N1 messages through the Mobility Management Function (AMF). A key component of these rules is the packet filter generated based on PCC rules. Additionally, the Data Network Name (DNN), UE IP address, and network slicing information are also transmitted to the UE via N1 messages during the signaling process of establishing the Protocol Data Unit (PDU) session.
[0051] With the introduction of service tags, a more precise method can now be used to determine the QoS Flow Identifier (QFI), combining the synergy of IP 5-tuples and service tags. For traffic carrying service tags, the corresponding QoS Flow Identifier (QFI) can be directly determined based on the service tag, providing finer-grained QoS control for this traffic. For traffic without service tags, the existing 5G network processing mechanism remains unchanged, i.e., the appropriate QoS Flow Identifier (QFI) is determined based on the IP 5-tuple. For traffic carrying service tags, the system parses the service tag to clarify the specific QoS requirements it represents and directly determines the corresponding QoS Flow Identifier (QFI) accordingly. This method allows the allocation of the most suitable QoS flow based on the actual QoS requirements of the traffic. For traffic without service tags, the traffic type and service requirements are identified by analyzing the IP 5-tuple, and the appropriate QoS Flow Identifier (QFI) is determined according to the standard procedures of the existing 5G network. Once the QoS Flow Identifier (QFI) is determined, the corresponding QoS rules and policies are applied to the traffic to ensure that it is transmitted according to the determined QoS requirements. By using this method, not only is the fine-grained control over traffic enhanced, but a more flexible and precise way to meet the QoS requirements of different applications and services is also provided. For traffic that supports service labels, a more direct and efficient QoS flow identifier (QFI) allocation is implemented. For regular traffic, the traditional processing mechanism is retained, ensuring broad network compatibility and service quality optimization.
[0052] Example 3 refer to Figure 3 A QoS fine-grained configuration device, comprising, The issuing device, the core network functional entity, issues a QoS enable notification to the core network storage management entity.
[0053] The acquisition device acquires triple rules from the core network functional entity. Specifically, the core network functional entity acquires triple rule information established by the core network storage management entity. The triple rules established by the core network storage management entity are created by uploading QoS configuration information and a triple rule establishment request to the core network storage management entity through the application service entity. The QoS configuration information includes service tags.
[0054] The generation device, the core network functional entity, generates a QoS parameter set containing service labels according to the triplet rules and sends it to the user plane function UPF.
[0055] Example 4 refer to Figure 4A fine-grained QoS configuration device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the method described in Embodiment 1 or 2. Specifically, the fine-grained QoS configuration device can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. The fine-grained QoS configuration device may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that the schematic diagram is merely an example of a fine-grained QoS configuration device and does not constitute a limitation on the fine-grained QoS configuration device. It may include more or fewer components than illustrated, or combine certain or different components. For example, the fine-grained QoS configuration device may also include a power supply component, input / output interfaces, network access devices, a bus, etc.
[0056] Example 5 A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method as described in Embodiment 1.
[0057] Specifically, the computer program can be divided into one or more modules / units, which are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the QoS fine-grained configuration device.
[0058] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A fine-grained QoS configuration method, characterized in that, include, The core network functional entity sends a QoS enable notification to the core network storage management entity; The core network functional entity obtains triple rules, wherein the core network functional entity obtains triple rule information established by the core network storage management entity. The triple rules established by the core network storage management entity are established by uploading QoS configuration information and triple rule establishment requests to the core network storage management entity through the application service entity; the QoS configuration information includes service tags. The core network functional entity generates a QoS parameter set containing service labels based on the triplet rules and sends it to the user plane function UPF.
2. The QoS fine-grained configuration method according to claim 1, characterized in that, The application service entity uploads QoS configuration information to the application function AF. The application function AF receives the QoS configuration information and initiates a triple rule establishment request to the core network storage management entity.
3. The QoS fine-grained configuration method according to claim 2, characterized in that, The core network functional entity is equipped with a network exposure function (NEF), which receives triple rule establishment requests initiated by the application function (AF).
4. The QoS fine-grained configuration method according to claim 3, characterized in that, The core network storage management entity includes a unified data management unit (UDM) and a unified data storage unit (UDR). The unified data management unit (UDM) receives a request from the network exposure function (NEF) to store triple rules. The unified data management unit (UDM) establishes triple rules based on QoS configuration information and writes the triple rules into the unified data storage unit (UDR).
5. The QoS fine-grained configuration method according to claim 4, characterized in that, The core network functional entity obtains the triple rule establishment request initiated by the application function AF and queries the unified data management UDM to establish triple rules.
6. A QoS fine-grained configuration method according to claim 4 or 5, characterized in that, The QoS fine-grained control and optimization method also includes the application service entity obtaining the QoS configuration submission results submitted to the Network Exposure Function (NEF).
7. The QoS fine-grained configuration method according to claim 1, characterized in that, The core network functional entity generates QoS parameters containing service labels according to the triplet rules and sends them to the user plane function UPF, including the following steps: The core network functional entity obtains requests from the application service entity stored in the core network storage management entity; The core network functional entity obtains the triple rule according to the request of the application service entity; The core network functional entity generates a QoS parameter set containing service labels according to the triplet rules and sends it to the session management function (SMF). The Session Management Function (SMF) sends a set of QoS parameters containing service labels to the User Plane Function (UPF).
8. A QoS fine-grained configuration method according to claim 1, characterized in that, The QoS configuration information also includes the IP 5-tuple and QoS requirements.
9. A QoS fine-grained configuration device, characterized in that, include, The issuing device, the core network functional entity, issues a QoS enable notification to the core network storage management entity; The acquisition device acquires triplet rules from the core network functional entity. Specifically, the core network functional entity acquires triplet rule information established by the core network storage management entity. The triplet rules established by the core network storage management entity are established by uploading QoS configuration information and a triplet rule establishment request to the core network storage management entity through the application service entity. The QoS configuration information includes service tags. The generation device, the core network functional entity, generates a QoS parameter set containing service labels according to the triplet rules and sends it to the user plane function UPF.
10. A QoS fine-grained configuration apparatus, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-8.
11. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-8.