QoS guarantee method, electronic equipment and access network equipment

Abstract

The invention provides a QoS guarantee method, electronic equipment and access network equipment, and relates to the technical field of communication. The method comprises the following steps that: a session management function (SMF) network element sends a latest quality of service (QoS) parameter to a user plane function (UPF) network element and sends a strategy updating instruction to an access and mobility management function (AMF) network element under the condition of detecting a change of a service demand; wherein the latest QoS parameter comprises a resource reservation rule, the strategy updating instruction is used for requesting the AMF network element to send the latest QoS parameter to the access network equipment, and the resource reservation rule is used for requesting to reserve resources. The QoS parameter transmission synchronization of the core network and the access network is ensured, that is, the QoS parameter transmission cooperation of the core network and the access network is ensured, and finally the QoS of the low-delay service is really ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a QoS guarantee method, electronic device, and access network device. Background Technology

[0002] With the widespread adoption of fifth-generation mobile communication technology (5G), its supported application scenarios are becoming increasingly diverse, primarily covering three major application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-Reliable and Low-Latency Communications (uRLLC). Among these, uRLLC scenarios, such as autonomous driving, telemedicine, and industrial automation control, place extremely stringent requirements on network Quality of Service (QoS), typically requiring end-to-end latency of less than 1 millisecond (ms) and reliability exceeding 99.999%. Therefore, ensuring QoS is crucial, especially for low-latency services.

[0003] Currently, QoS assurance primarily relies on the collaborative work of multiple core network elements. The PCF (Policy Control Function) element is responsible for updating QoS policies based on network conditions, while the UPF (User Plane Function) element is responsible for executing specific QoS rules. This means the UPF element needs to receive the updated QoS policy, and the QoS policy needs to be transmitted to the access network equipment via the AMF (Access and Mobility Management Function) element to ensure that radio-side resources match the core network's policy requirements. However, when service demands change dynamically, the SMF (Session Management Function) element does not simultaneously send new QoS parameters to the UPF element and the access network equipment. This lack of synchronization in the transmission of QoS parameters between the core network and the access network, coupled with a lagging coordination mechanism, prevents true QoS assurance for low-latency services. Summary of the Invention

[0004] This application provides a QoS guarantee method, electronic device, and access network device to solve the problem of lack of synchronization in the transmission of QoS parameters between the core network and the access network, realize the synchronization of QoS parameter transmission between the core network and the access network, and truly guarantee the QoS of low-latency services.

[0005] Firstly, this application provides a QoS guarantee method applied to a Session Management Function (SMF) network element, the QoS guarantee method comprising: Upon detecting changes in service requirements, the latest Quality of Service (QoS) parameters are sent to the User Plane Function (UPF) network element, and a policy update command is sent to the Access and Mobility Management Function (AMF) network element. The latest QoS parameters include resource reservation rules. The policy update instruction is used to request the AMF network element to send the latest QoS parameters to the access network device, and the resource reservation rules are used to request resource reservation.

[0006] Secondly, this application also provides a QoS guarantee method applied to Access and Mobility Management Function (AMF) network elements, the QoS guarantee method comprising: Upon receiving a policy update instruction from the Session Management Function (SMF) network element, the latest QoS parameters are sent to the access network device. The latest QoS parameters include resource reservation rules, which are used to request the access network device to reserve resources.

[0007] Thirdly, this application also provides a QoS guarantee method applied to a User Plane Function (UPF) network element, the QoS guarantee method comprising: Receive the latest QoS parameters sent by the Session Management Function (SMF) network element; The latest QoS parameters include resource reservation rules, which are used to request the UPF network element to reserve resources.

[0008] Fourthly, this application also provides a QoS guarantee method applied to a policy control function (PCF) network element, the QoS guarantee method comprising: Upon receiving a slice identifier sent by the Session Management Function (SMF) network element, a new QoS identifier corresponding to the slice identifier is determined based on the pre-configured slice-QoS identifier mapping relationship; the slice-QoS identifier mapping relationship is used to indicate the one-to-one correspondence between multiple slice identifiers and multiple QoS identifiers. Based on the new QoS identifier, determine the declared QoS policy; Send the declared QoS policy to the SMF network element.

[0009] Fifthly, this application also provides a QoS guarantee method applied to network element analysis, the QoS guarantee method comprising: Based on the collected data, a third QoS policy is generated; the collected data includes at least one of the following: resource status data reported by one or more core network elements, traffic characteristics of QoS flows, and resource status data of access network devices. The third QoS policy is sent to one or more target core network elements.

[0010] Sixthly, this application also provides a QoS guarantee method applied to access network equipment, the QoS guarantee method comprising: Receive data packets sent by the User Plane Function (UPF) network element; If the data packet includes a display congestion notification flag, the data packet is processed with priority.

[0011] In a seventh aspect, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, applied to a Session Management Function (SMF) network element, wherein the processor executes the computer program to implement any of the QoS guarantee methods applied to the SMF network element described above.

[0012] Eighthly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, applied to an Access and Mobility Management Function (AMF) network element, wherein the processor executes the computer program to implement the QoS guarantee method applied to the AMF network element as described above.

[0013] Ninthly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, applied to a User Plane Function (UPF) network element, wherein when the processor executes the computer program, it implements the QoS guarantee method applied to the UPF network element as described above.

[0014] In a tenth aspect, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, applied to a policy control function (PCF) network element, wherein when the processor executes the computer program, it implements the QoS guarantee method applied to the PCF network element as described above.

[0015] Eleventhly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, applied to an analysis network element, wherein the processor executes the computer program to implement the QoS guarantee method applied to the analysis network element as described above.

[0016] In a twelfth aspect, this application also provides an access network device, including a memory, a transceiver, and a processor; A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Receive data packets sent by the User Plane Function (UPF) network element; If the data packet includes a display congestion notification flag, the data packet is processed with priority.

[0017] The QoS guarantee method, electronic device, and access network device provided in this application, upon detecting a change in service requirements, have the SMF network element send the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element. The policy update instruction requests the AMF network element to send the latest QoS parameters to the access network device. These latest QoS parameters include resource reservation rules, which are used to request resource reservations. Thus, when the SMF network element detects a change in service requirements, it simultaneously sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element, ensuring that the latest QoS parameters are sent to both the UPF network element and the access network device. This means that policy adjustments to the UPF network element and the access network are initiated synchronously, ensuring synchronized QoS parameter transmission between the core network and the access network, and ultimately guaranteeing the QoS of low-latency services. Simultaneously, when the SMF network element detects a change in service requirements... The system sends the latest QoS parameters to the UPF network element and a policy update command to the AMF network element, eliminating the need to wait for the statically configured QoS policy adjustment process. This allows for rapid response to changes in service requirements, enabling dynamic QoS policy adjustments and resolving the issue of delayed QoS parameter transmission. Real-time QoS parameter transmission is achieved, meaning real-time response to changes in service requirements. This allows for real-time collaborative adjustment of core and access network resources, reducing latency fluctuations caused by resource contention and ultimately ensuring true QoS for low-latency services. Simultaneously, the system sends the latest QoS parameters to the UPF network element and a policy update command to the AMF network element. The policy update command requests the AMF network element to send the latest QoS parameters to the access network equipment. Therefore, the resource reservations to be performed by both the UPF and access network equipment originate from the latest QoS parameters determined by the SMF network element at the same time, ensuring consistency in resource reservations between the UPF and access network equipment and ultimately guaranteeing true QoS for low-latency services. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying 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.

[0019] Figure 1 This is one of the flowcharts illustrating the QoS guarantee method provided in the embodiments of this application; Figure 2 This is a second flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 3 This is the third flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 4 This is the fourth flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 5 This is the fifth flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 6 This is the sixth flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 7 This is the seventh flowchart illustrating the QoS guarantee method provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application; Figure 9 This is a schematic diagram of the structure of the access network device provided in the embodiments of this application. Detailed Implementation

[0020] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0021] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0022] 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 a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0023] Currently, the path by which the SMF (Session Management Function) sends QoS (Quality of Service) parameters to the UPF (User Plane Function) network element, and the path by which the SMF transmits QoS parameters to the access network equipment through the AMF (Access and Mobility Management Function) network element, are two independent and non-coordinated processes. This lag in the QoS parameter transmission and coordination mechanism between the core network and the access network makes it impossible to truly guarantee the QoS of low-latency services.

[0024] Based on the above problems, this application proposes the following embodiments. The following is in conjunction with... Figures 1-7 Describe the QoS guarantee method of this application.

[0025] Figure 1 This is one of the flowcharts illustrating the QoS guarantee method provided in the embodiments of this application, such as... Figure 1 As shown, the QoS guarantee method includes step 110. This QoS guarantee method is applied to SMF network elements.

[0026] Step 110: Upon detecting a change in service requirements, send the latest Quality of Service (QoS) parameters to the User Plane Function (UPF) network element and send a policy update instruction to the Access and Mobility Management Function (AMF) network element.

[0027] Here, business requirements specifically refer to a set of specific requirements for network transmission performance that a terminal's business or application must meet to operate normally and with high quality; that is, the performance indicators that the network must meet when transmitting data. For example, business requirements are quantified as a set of specific network performance parameters (such as transmission latency, transmission reliability, jitter, and bandwidth). Furthermore, business requirements can also be described as network performance requirements.

[0028] Here, "change in business requirements" refers to a change in the network transmission performance requirements of the same business or application at different operational stages. For example, a change in business requirements means that the required network performance parameters for the same application or session change significantly at different operational stages. Minor changes can be considered as unchanged business requirements, and changes less than a threshold are considered minor changes.

[0029] In one embodiment, the service requirement can be a service mode; a change in the service requirement is a switch in the service mode, such as an application switching from browsing mode to interactive mode. In another embodiment, the service requirement can be a QoS level; a change in the service requirement is a switch in the QoS level, such as an application switching from the third priority to the highest priority. In yet another embodiment, the service requirement can be a session state; a change in the service requirement is a change in the session state. Of course, the service requirement can also be other information, which is not specifically limited here.

[0030] In one embodiment, changes in service requirements are detected based on traffic characteristics of the QoS flow. This QoS flow can be detected by a UPF network element, and the traffic characteristics may include, but are not limited to, at least one of the following: burst packet rate, packet size, packet arrival interval, and total traffic volume. The entity performing the detection of changes in service requirements can be an SMF network element or a UPF network element. For example, when an SMF network element detects a sudden increase in QoS flow traffic, it determines that the service requirements have changed.

[0031] In another embodiment, a NAS (Non-Access Stratum) message sent by a receiving terminal is received; this NAS message includes a QoS identifier; the QoS identifier in the NAS message is used to determine whether the service requirements have changed. That is, if the terminal actively declares that the service requirements have changed, it indicates a new QoS identifier in the NAS message, such as upgrading the QoS identifier from 9 to 2.

[0032] In another embodiment, other devices or functional network elements detect whether service requirements have changed. For example, the following analysis network element can be used to detect whether service requirements have changed. It should be noted that even if the service requirements themselves have not changed, if network resources cannot guarantee the service requirements, the service requirements will be adjusted. For example, if congestion is predicted to occur in a certain base station cell, resources will be adjusted in advance for that service.

[0033] Here, the UPF network element is used to execute the latest QoS policy issued by the SMF network element on the specific service data packets flowing through it on the user data plane.

[0034] Here, the latest QoS parameters are those in the QoS policy recently obtained by the SMF network element. These latest QoS parameters include resource reservation rules, which are used to request resource reservations. Furthermore, these resource reservation rules also indicate the name and quantity of the reserved resources. For example, the resource reservation rule could be a GBR (Guaranteed Bit Rate) reservation rule, or a GBR parameter.

[0035] In one embodiment, the latest QoS parameter may also include a QoS identifier. For example, the QoS identifier may be 5QI (5G QoS Identifier, the quality of service identifier for fifth-generation mobile communications).

[0036] The policy update command is used to request the AMF network element to send the latest QoS parameters to the access network device. In other words, the AMF network element is used to send the latest QoS parameters to the access network device.

[0037] Here, the access network device can be a network-side device, such as a base station; in a 5G scenario, it can be a gNB (next-generation Node B).

[0038] In one specific embodiment, the latest QoS parameters are sent to the UPF network element via a PFCP (Packet Forwarding Control Protocol) message on the N4 interface. More specifically, the latest QoS parameters are sent to the UPF network element via a PFCP SessionModification Request message.

[0039] In one specific embodiment, a policy update command is sent to the AMF network element via NGAP (Next Generation Application Protocol). More specifically, the policy update command is sent to the AMF network element via NGAP messages.

[0040] For AMF network elements, upon receiving a policy update instruction from an SMF network element, the AMF network element sends the latest QoS parameters to the access network device. The resource reservation rule is used to request the access network device to reserve resources; for example, the resource reservation rule is used to request the access network device to reserve PRBs (Physical Resource Blocks).

[0041] For example, the SMF network element sends a GBR reservation to the UPF network element through the PFCP Session Modification Request message, and at the same time requests a PRB reservation from the gNB through the NGAP message, thus forming a resource reservation linkage.

[0042] It should be understood that sending the latest QoS parameters to the UPF network element and sending the policy update instruction to the AMF network element, "in parallel" means that the two transmissions are simultaneous and synchronous. That is, the QoS control of the UPF network element by the SMF network element and the QoS control of the access network by the SMF network element are not separate but synchronous, thereby solving the problem of lag in the existing N2 interface's dynamic transmission of QoS parameters that depends on the request-response process.

[0043] The QoS guarantee method provided in this application embodiment, upon detecting a change in service demand, sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element. The policy update instruction requests the AMF network element to send the latest QoS parameters to the access network device. The latest QoS parameters include resource reservation rules, which are used to request resource reservation. Thus, when the SMF network element detects a change in service demand, it simultaneously sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element, ensuring that the latest QoS parameters are sent to both the UPF network element and the access network device simultaneously. This means that policy adjustments to the UPF network element and the access network are initiated synchronously, ensuring synchronized QoS parameter transmission between the core network and the access network, and ultimately ensuring true QoS guarantee for low-latency services. Simultaneously, when the SMF network element detects a change in service demand, it sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element. The PF network element sends the latest QoS parameters and a policy update command to the AMF network element. This eliminates the need to wait for the statically configured QoS policy adjustment process, enabling rapid response to changes in service requirements and dynamic QoS policy adjustment. This solves the problem of delayed QoS parameter transmission, achieving real-time QoS parameter delivery and responding to changes in service requirements in real time. It also allows for real-time collaborative adjustment of core and access network resources, reducing latency fluctuations caused by resource contention and ultimately ensuring the true QoS guarantee for low-latency services. Simultaneously, the PF network element sends the latest QoS parameters to the UPF network element and a policy update command to the AMF network element. The policy update command requests the AMF network element to send the latest QoS parameters to the access network devices. Therefore, the resource reservations to be performed by the UPF network element and the access network devices are derived from the latest QoS parameters determined by the SMF network element at the same time, ensuring consistency in resource reservations between the UPF network element and the access network devices, ultimately guaranteeing the true QoS guarantee for low-latency services.

[0044] Based on any of the above embodiments, before the steps of sending the latest Quality of Service (QoS) parameters to the User Plane Function (UPF) network element and sending a policy update instruction to the Access and Mobility Management Function (AMF) network element, the method further includes: Send the first policy update request to the policy control function (PCF) network element; Receive the updated first QoS policy returned by the PCF network element.

[0045] The first policy update request is used to request the PCF (Policy Control Function) network element to update the QoS policy.

[0046] In one specific embodiment, for a PCF network element, the PCF network element generates an updated QoS policy based on network status and / or new service requirements. It should be noted that the PCF network element is specifically used to determine the QoS policy; therefore, the specific method for updating the QoS policy can refer to existing technologies and will not be elaborated here.

[0047] The first QoS policy includes the latest QoS parameters. It should be noted that if a first policy update request is sent to the PCF network element upon detecting a change in service requirements, the latest QoS parameters will be those included in the updated first QoS policy. Conversely, if no first policy update request is sent to the PCF network element, and the PCF network element proactively returns the latest QoS policy, then the latest QoS parameters will be those included in the latest QoS policy.

[0048] In one specific embodiment, a first policy update request is sent to the PCF network element via the N7 interface. The updated first QoS policy is received from the PCF network element via the N7 interface; that is, the PCF network element sends the updated first QoS policy to the SMF network element via the N7 interface. Furthermore, the first policy update request is sent to the PCF network element via the Nsmf_PDUSession_ContextUpdate interface.

[0049] The QoS guarantee method provided in this application embodiment involves an SMF network element sending a first policy update request to a PCF network element. The first policy update request is used to request the PCF network element to update the QoS policy. The SMF network element receives the updated first QoS policy returned by the PCF network element, and the first QoS policy includes the latest QoS parameters. Thus, the PCF network element determines the latest QoS parameters, ensuring that the dynamically adjusted QoS parameters meet the requirements of each policy, thereby enhancing the accuracy and compliance of QoS guarantee.

[0050] Based on any of the above embodiments, in this method, the UPF network element is determined in the following way: The Network Resource Function (NRF) network element initiates a service discovery request, which is used to query the UPF network element based on the location of the access network device.

[0051] Specifically, the service discovery request is used to query the UPF network element closest to the access network device based on the device's location. This service discovery request is initiated by the NRF (Network Repository Function) network element. It should be noted that the UPF network element is deployed at the edge.

[0052] In one embodiment, the UPF network element is managed as an independent service by the SCP (Service Communication Proxy). The SMF network element discovers the UPF network element through the NRF network element to negotiate resources. That is, the UPF network element is deployed in a service-oriented manner, and the NRF network element discovers and selects the UPF network element closest to the access network device.

[0053] UPF network elements adopt a service-oriented deployment approach, enabling plug-and-play functionality through edge computing platforms such as KubeEdge. UPF instances are deployed in edge data centers, close to gNBs (access network devices) to reduce transmission latency. UPF network elements utilize vCPU aggregation technology to achieve micro-stream scheduling, improving processing efficiency. Furthermore, UPF network elements support dynamic scaling, automatically adjusting resources based on service load.

[0054] It should be understood that placing UPF network elements close to access network equipment can reduce the number of transmission hops. Therefore, querying the optimal UPF network element based on the location of the access network equipment can reduce end-to-end latency. For example, the distance between the UPF network element and the access network equipment can be controlled within one hop, thereby significantly reducing transmission latency.

[0055] Furthermore, the UPF network element enables vCPU (virtual central processing unit) aggregation technology to achieve micro-flow scheduling and load balancing, thereby improving processing efficiency.

[0056] Furthermore, a first service discovery request is initiated through the NRF network element. This first service discovery request is used to query access network devices based on resources from multiple candidate access network devices. A second service discovery request is also initiated through the NRF network element. This second service discovery request is used to query UPF network elements based on the location of the access network devices. The multiple candidate access network devices are one or more access network devices that are to be selected, and this access network device is the one with the largest PRB resources among the multiple candidate access network devices. Based on this, when selecting a UPF network element, the SMF network element queries the PRB resources supported by multiple candidate access network devices through NRF network element discovery, thereby selecting the access network device with the largest PRB resources. This ensures that the UPF network element can synchronize with the resource reservation of the access network devices, ultimately ensuring the true QoS of low-latency services.

[0057] The QoS guarantee method provided in this application embodiment involves the SMF network element initiating a service discovery request through the NRF network element. The service discovery request is used to query the UPF network element based on the location of the access network device, thereby shortening the number of hops and physical distance of user data transmission, thereby reducing end-to-end transmission latency, and ultimately ensuring the QoS of low-latency services.

[0058] Based on any of the above embodimentsFigure 2 This is a second flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as shown below. Figure 2 As shown, the QoS guarantee method also includes steps 210 and 220.

[0059] Step 210: If the traffic characteristics of the QoS flow determine that the service corresponding to the QoS flow is a low-latency service, send a second policy update request to the PCF network element.

[0060] In one embodiment, the QoS flow is detected by the UPF network element, and it is the service data flow corresponding to the service. Further, the entity that determines whether the service corresponding to the QoS flow is a low-latency service based on the traffic characteristics of the QoS flow can be an SMF network element or a UPF network element.

[0061] Here, traffic characteristics are used to characterize the features of a QoS flow, which may include, but are not limited to, at least one of the following: burst packet rate, packet size, and packet arrival interval, etc.

[0062] Here, low-latency services refer to services with high latency requirements, such as uRLLC (Ultra-Reliable and Low Latency Communications) services. For example, low-latency services require a PDB (Packet Delay Budget) ≤ 1ms, a PER (Packet Error Rate) ≤ 0.001%, and a reliability ≥ 99.999%.

[0063] The second policy update request is used to request the PCF network element to update the QoS policy of the QoS flow. The QoS policy includes a QoS identifier. For example, the QoS identifier is 5QI.

[0064] In one specific embodiment, the QoS policy of the QoS flow is updated based on traffic characteristics, network performance indicators (such as congestion rate), and / or user experience data (such as service interruption frequency). This involves dynamically classifying services and assigning corresponding QoS identifiers and QoS parameters to different services. It should be noted that the PCF network element is used to determine the QoS policy; therefore, the specific method for updating the QoS policy can refer to existing technologies and will not be elaborated here.

[0065] In one embodiment, based on the comparison between the traffic characteristics of the QoS flow and a preset traffic characteristic threshold, it is determined whether the service corresponding to the QoS flow is a low-latency service. This preset traffic characteristic threshold can be set according to actual conditions. For example, the traffic characteristics include burst packet rate and packet size. If the burst packet rate is greater than 100 packets per second, or the packet size is less than 100 bytes, the service corresponding to the QoS flow is determined to be a low-latency service, thereby triggering the SMF network element to renegotiate the QoS identifier.

[0066] In one specific embodiment, a second policy update request is sent to the PCF network element via the N7 interface. Additionally, a second policy update request is sent to the PCF network element via the Nsmf_PDUSession_ContextUpdate interface.

[0067] In other words, QoS identifiers are dynamically adjusted based on traffic characteristic analysis. For example, bursty small packets trigger SMF network elements to reconfigure QoS parameters, thereby achieving low-latency service identification and dynamic classification.

[0068] Step 220: Receive the updated second QoS policy returned by the PCF network element.

[0069] In one specific embodiment, the updated second QoS policy returned by the PCF network element is received through the N7 interface, that is, the PCF network element sends the updated second QoS policy to the SMF network element through the N7 interface.

[0070] The QoS guarantee method provided in this application embodiment allows the SMF network element to send a second policy update request to the PCF network element when the SMF network element determines that the service corresponding to the QoS flow is a low-latency service based on the traffic characteristics of the QoS flow. This enables the SMF network element to dynamically identify low-latency services based on real-time traffic characteristics, thereby enabling more refined and real-time judgment and classification of the actual service type carried. This provides an accurate QoS policy for subsequent QoS guarantee, thus improving the accuracy of QoS guarantee.

[0071] Based on any of the above embodiments, before the step of sending the second policy update request to the PCF network element, the method further includes: steps 230, 240 and 250.

[0072] Step 230: Receive the non-access stratum (NAS) message sent by the terminal.

[0073] Here, the terminal can be a UE (User Equipment). This terminal can proactively declare that it requires low latency.

[0074] The NAS (Non-Access Stratum) message includes a claim message, which includes a QoS identifier and / or a slice identifier.

[0075] The QoS identifier in this declaration message is an identifier declared by the terminal. For example, if the QoS identifier is 5QI, where 5QI = 1-5 corresponds to low-latency service scenarios, then the PCF network element can change to the QoS policy corresponding to the low-latency service scenario based on the QoS identifier.

[0076] In one specific embodiment, when a terminal initiates an initial registration or Service Request, it declares the corresponding QoS identifier according to the service requirements. For example, the uRLLC service can declare 5QI=1-5.

[0077] It should be noted that adding the function of carrying QoS identifiers in NAS messages allows terminals to actively declare that their services are low-latency services, thereby enabling more refined and real-time classification of the actual service types carried, providing accurate QoS policies for subsequent QoS assurance, and thus improving the accuracy of QoS assurance.

[0078] Here, the slice identifier is used to uniquely identify a network slice, for example, it is S-NSSAI (Single Network Slice Selection Assistance Information).

[0079] It should be noted that adding the function of carrying slice identifiers in NAS messages allows terminals to actively declare that their services are low-latency services, thereby enabling more refined and real-time classification of the actual service types carried, providing accurate QoS policies for subsequent QoS assurance, and thus improving the accuracy of QoS assurance.

[0080] Step 240: Send a declaration message to the PCF network element.

[0081] The declaration message is used to instruct the PCF network element to determine the declared QoS policy. Furthermore, this declared QoS policy can be considered the initial QoS policy for the service.

[0082] For PCF network elements, when the declaration message includes a QoS identifier, the PCF network element determines the declared QoS policy based on the QoS identifier included in the declaration message; when the declaration message includes a slice identifier, the PCF network element determines a new QoS identifier corresponding to the slice identifier based on the pre-configured slice-to-QoS identifier mapping relationship. This slice-to-QoS identifier mapping relationship is used to indicate the one-to-one correspondence between multiple slice identifiers and multiple QoS identifiers. Based on the new QoS identifier, the declared QoS policy is determined.

[0083] Step 250: Receive the declared QoS policy returned by the PCF network element.

[0084] In one specific embodiment, the declared QoS policy returned by the PCF network element is received through the N7 interface, that is, the PCF network element sends the declared QoS policy to the SMF network element through the N7 interface.

[0085] The QoS guarantee method provided in this application embodiment involves an SMF network element receiving a NAS message sent by a terminal, wherein the NAS message includes a declaration message, which includes a QoS identifier and / or a slice identifier. The SMF network element then sends the declaration message to a PCF network element, which instructs the PCF network element to determine the declared QoS policy. Thus, the determination of the QoS policy can be based on the active declaration of the terminal, ensuring the accurate transmission of QoS parameters from the service source. This allows the most suitable QoS policy to be matched at the beginning of the session establishment, avoiding the delay of subsequent dynamic adjustment of the QoS policy, and ultimately ensuring the true QoS guarantee of low-latency services.

[0086] Based on any of the above embodiments, after step 220, the method further includes: Send the QoS identifier from the second QoS policy to the UPF network element.

[0087] For the UPF network element, the UPF network element receives the QoS identifier in the second QoS policy sent by the SMF network element; based on the pre-configured mapping relationship between the QoS identifier and DSCP, it determines the DSCP corresponding to the QoS identifier in the second QoS policy; the mapping relationship between the QoS identifier and DSCP is used to indicate the one-to-one correspondence between multiple QoS identifiers and multiple DSCPs; based on the DSCP, the data packets in the QoS flow are marked so that the marked data packets are sent to the access network device.

[0088] It should be understood that, considering that existing QoS mechanisms use QoS flows as the smallest scheduling unit, they cannot perform fine-grained control on frames or data packets. In scenarios such as industrial control and remote surgery, mistransmission or omission of a single data packet may lead to the failure of decoding the entire frame, affecting service continuity. Based on this, the embodiments of this application use DSCP to mark data packets in the QoS flow so that the marked data packets are sent to the access network device. This eliminates the need to mark the entire QoS flow and allows for priority processing of DSCP-marked data packets, thereby reducing end-to-end transmission latency.

[0089] The QoS guarantee method provided in this application embodiment involves the SMF network element sending an updated QoS identifier from the second QoS policy to the UPF network element when it determines that the service corresponding to the QoS flow is a low-latency service. This enables the UPF network element to obtain an accurate and up-to-date QoS identifier, thereby executing subsequent DSCP marking and accurately mapping the QoS policy of the core network to the IP network. This allows data packets to be correctly identified and prioritized during subsequent forwarding, thereby reducing end-to-end transmission latency and ultimately ensuring the true QoS guarantee of low-latency services.

[0090] Based on any of the above embodiments, the method further includes: Send SMF network element resource status data to the analysis network element; The third QoS policy sent by the analysis network element is received and analyzed; the third QoS policy is determined by the analysis network element based on the resource status data of the SMF network element.

[0091] Here, the analysis network element is used to perform data analysis to determine the updated third QoS policy based on the collected data (including resource status data of the SMF network element). In one embodiment, the analysis network element is an AI (Artificial Intelligence) analysis engine, which can determine the updated third QoS policy based on AI algorithms; further, the analysis network element is a GPM (Global Processing Module), as detailed in the following embodiments.

[0092] In one embodiment, the collected data only includes resource status data of SMF network elements, meaning the updated third QoS policy can be determined by the analysis network element based solely on the resource status data of the SMF network elements. In another embodiment, the collected data may further include at least one of the following: resource status data reported by other core network elements besides SMF network elements, traffic characteristics of QoS flows, and resource status data of access network devices. It should be noted that the updated content of the QoS policy will differ based on different collected data.

[0093] Here, resource status data is used to indicate the resource status of network elements, which may include, but is not limited to, at least one of the following: CPU (Central Processing Unit) utilization, memory usage, bandwidth usage, etc.

[0094] In one specific embodiment, the resource status data of the SMF network element is sent to the analysis network element through the Telemetry interface.

[0095] In one specific embodiment, resource status data of the SMF network element is sent to the analysis network element in real time.

[0096] Furthermore, based on network load, the data collection frequency is determined; based on the data collection frequency, resource status data of the SMF network element is sent to the analysis network element. Therefore, the data collection frequency can be dynamically adjusted according to network load, for example, increasing the data collection frequency during high load periods, thereby improving the decision-making accuracy of the third QoS strategy.

[0097] In one specific embodiment, for the analysis network element, the analysis network element generates a third QoS policy based on the collected data. The collected data includes resource status data of the SMF network element, and may also include at least one of the following: resource status data reported by other core network elements, traffic characteristics of QoS flows, and resource status data of access network devices.

[0098] It should be understood that, considering that existing QoS parameter configurations are mostly static policies, they cannot dynamically reserve bandwidth or adjust priorities based on service bursts (such as emergency braking signals in autonomous driving). In high-load scenarios, low-latency services may experience increased latency due to resource contention. Therefore, in this embodiment, the core network element reports resource status data to the analysis network element, which then determines a third QoS policy based on the resource status data. This optimizes dynamic resource management, solves the problem of existing static policies failing to cope with dynamic network changes, and improves network resource utilization and efficiency while ensuring the QoS of low-latency services.

[0099] The QoS guarantee method provided in this application improves network resource utilization and efficiency by analyzing network elements and adjusting QoS policies in advance, thereby guaranteeing the QoS of low-latency services.

[0100] Based on any of the above embodiments, this application also provides a QoS guarantee method applied to AMF network elements. Figure 3 This is the third flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as shown below. Figure 3 As shown, the QoS guarantee method includes step 310.

[0101] Step 310: Upon receiving a policy update instruction from the Session Management Function (SMF) network element, send the latest QoS parameters to the access network device.

[0102] The policy update command is used to request the AMF network element to send the latest QoS parameters to the access network device. This access network device can be a network-side device, such as a base station; in a 5G scenario, it can be a gNB.

[0103] The latest QoS parameters include resource reservation rules, which are used to request access network devices to reserve resources. Furthermore, these rules also indicate the name and quantity of the reserved resources; for example, the resource reservation rule might be a GBR reservation rule, or a GBR parameter. For instance, a resource reservation rule might be used to request access network devices to perform PRB reservations.

[0104] In one embodiment, the latest QoS parameter may also include a QoS identifier. For example, the QoS identifier is 5QI.

[0105] In one specific embodiment, the latest QoS parameters are sent to the access network device via a PDU SESSION RESOURCE MODIFY REQUEST message. More specifically, a PDU SESSION RESOURCE MODIFY REQUEST message, including the latest QoS parameters, is sent to the access network device through a triangular redirection mechanism. In other words, resource reservation (such as PRB resource reservation) is negotiated with the access network device through the N2 interface to ensure resource consistency between the core network and the access network.

[0106] The QoS guarantee method provided in this application embodiment involves the SMF network element sending the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element when it detects a change in service demand. Upon receiving the policy update instruction from the SMF network element, the AMF network element sends the latest QoS parameters to the access network device. These latest QoS parameters include resource reservation rules used to request resource reservation. Thus, when the SMF network element detects a change in service demand, it simultaneously sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element, ensuring that the latest QoS parameters are sent to both the UPF network element and the access network device. This means that policy adjustments to the UPF network element and the access network are initiated synchronously, ensuring synchronized QoS parameter transmission between the core network and the access network, and ultimately guaranteeing the QoS of low-latency services. Simultaneously, when the SMF network element detects a change in service demand, it sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element. The PF network element sends the latest QoS parameters and a policy update command to the AMF network element. This eliminates the need to wait for the statically configured QoS policy adjustment process, enabling rapid response to changes in service requirements and dynamic QoS policy adjustment. This solves the problem of lag in QoS parameter transmission, achieving real-time QoS parameter delivery and responding to changes in service requirements in real time. It also allows for real-time collaborative adjustment of core and access network resources, reducing latency fluctuations caused by resource contention and ultimately ensuring the true QoS guarantee for low-latency services. Simultaneously, the SMF network element sends the latest QoS parameters to the UPF network element and a policy update command to the AMF network element. Upon receiving the policy update command from the SMF network element, the AMF network element sends the latest QoS parameters to the access network devices. Therefore, the resource reservations to be performed by the UPF network element and the access network devices are based on the latest QoS parameters determined by the SMF network element at the same time, ensuring consistency in resource reservations between the UPF network element and the access network devices, ultimately guaranteeing the true QoS guarantee for low-latency services.

[0107] Based on any of the above embodiments, the method further includes: Send AMF network element resource status data to the analysis network element; The third QoS policy sent by the analysis network element is received and analyzed; the third QoS policy is determined by the analysis network element based on the resource status data of the AMF network element.

[0108] Here, the analysis network element is used to perform data analysis to determine the updated third QoS policy based on the collected data (including resource status data of the AMF network element). In one embodiment, the analysis network element is an AI analysis engine, which can determine the updated third QoS policy based on AI algorithms; further, the analysis network element is GPM, as detailed in the following embodiments.

[0109] In one embodiment, the collected data only includes resource status data of AMF network elements, meaning the updated third QoS policy can be determined by the analysis network element based solely on the resource status data of AMF network elements. In another embodiment, the collected data may further include at least one of the following: resource status data reported by other core network elements besides AMF, traffic characteristics of QoS flows, and resource status data of access network devices. It should be noted that the updated content of the QoS policy will differ based on different collected data.

[0110] Here, resource status data is used to indicate the resource status of network elements, which may include, but is not limited to, at least one of the following: CPU utilization, memory usage, bandwidth usage, etc.

[0111] In one specific embodiment, the resource status data of the AMF network element is sent to the analysis network element through the Telemetry interface.

[0112] In one specific embodiment, the resource status data of the AMF network element is sent to the analysis network element in real time.

[0113] Furthermore, based on network load, the data acquisition frequency is determined; based on the data acquisition frequency, the resource status data of the AMF network element is sent to the analysis network element. Therefore, the data acquisition frequency can be dynamically adjusted according to network load, for example, increasing the data acquisition frequency during high load periods, thereby improving the decision-making accuracy of the third QoS strategy.

[0114] In one specific embodiment, for the analysis network element, a third QoS policy is generated based on the collected data. This collected data includes resource status data of the AMF network element, and may also include at least one of the following: resource status data reported by other core network elements, traffic characteristics of QoS flows, and resource status data of access network devices.

[0115] It should be understood that, considering that existing QoS parameter configurations are mostly static policies, they cannot dynamically reserve bandwidth or adjust priorities based on service bursts (such as emergency braking signals in autonomous driving). In high-load scenarios, low-latency services may experience increased latency due to resource contention. Therefore, in this embodiment, the core network element reports resource status data to the analysis network element, which then determines a third QoS policy based on the resource status data. This optimizes dynamic resource management, solves the problem of existing static policies failing to cope with dynamic network changes, and improves network resource utilization and efficiency while ensuring the QoS of low-latency services.

[0116] The QoS guarantee method provided in this application improves network resource utilization and efficiency by analyzing network elements and adjusting QoS policies in advance, thereby guaranteeing the QoS of low-latency services.

[0117] Based on any of the above embodiments, this application also provides a QoS guarantee method applied to UPF network elements. Figure 4 This is the fourth flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as follows: Figure 4 As shown, the QoS guarantee method includes step 410.

[0118] Step 410: Receive the latest QoS parameters sent by the Session Management Function (SMF) network element.

[0119] The latest QoS parameters include resource reservation rules, which are used to request UPF network elements to reserve resources. Furthermore, these resource reservation rules also indicate the name and quantity of the reserved resources; for example, the resource reservation rule may be a GBR reservation rule, or a GBR parameter. For instance, the resource reservation rule is used to request UPF network elements to perform GBR reservations.

[0120] In one embodiment, the latest QoS parameter may also include a QoS identifier. For example, the QoS identifier is 5QI.

[0121] The QoS guarantee method provided in this application embodiment involves the SMF network element sending the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element when it detects a change in service demand. Upon receiving the policy update instruction from the SMF network element, the AMF network element sends the latest QoS parameters to the access network device. These latest QoS parameters include resource reservation rules used to request resource reservation. Thus, when the SMF network element detects a change in service demand, it simultaneously sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element, ensuring that the latest QoS parameters are sent to both the UPF network element and the access network device. This means that policy adjustments to the UPF network element and the access network are initiated synchronously, ensuring synchronized QoS parameter transmission between the core network and the access network, and ultimately guaranteeing the QoS of low-latency services. Simultaneously, when the SMF network element detects a change in service demand, it sends the latest QoS parameters to the UPF network element and a policy update instruction to the AMF network element. The PF network element sends the latest QoS parameters and a policy update command to the AMF network element. This eliminates the need to wait for the statically configured QoS policy adjustment process, enabling rapid response to changes in service requirements and dynamic QoS policy adjustment. This solves the problem of lag in QoS parameter transmission, achieving real-time QoS parameter delivery and responding to changes in service requirements in real time. It also allows for real-time collaborative adjustment of core and access network resources, reducing latency fluctuations caused by resource contention and ultimately ensuring the true QoS guarantee for low-latency services. Simultaneously, the SMF network element sends the latest QoS parameters to the UPF network element and a policy update command to the AMF network element. Upon receiving the policy update command from the SMF network element, the AMF network element sends the latest QoS parameters to the access network devices. Therefore, the resource reservations to be performed by the UPF network element and the access network devices are based on the latest QoS parameters determined by the SMF network element at the same time, ensuring consistency in resource reservations between the UPF network element and the access network devices, ultimately guaranteeing the true QoS guarantee for low-latency services.

[0122] Based on any of the above embodiments, the method further includes: In the event of network congestion, packets in the QoS flow are marked based on explicit congestion notification marking, so that the marked packets are sent to the access network device.

[0123] Here, explicit congestion notification is marked with the ECN (Explicit Congestion Notification) flag.

[0124] The explicit congestion notification flag is used to instruct access network devices to prioritize data packets marked with the explicit congestion notification flag. For access network devices, when receiving data packets from UPF network elements, they prioritize packets containing the explicit congestion notification flag.

[0125] Accordingly, the terminal supports the TCP Prague algorithm, adjusting the transmission rate based on the ECN tag to avoid the sawtooth waveform rate variations of traditional TCP algorithms. More specifically, the terminal and the core network coordinate to adjust the transmission rate, implementing the TCP Prague algorithm. Based on this, a balance between low latency and high throughput is achieved.

[0126] Furthermore, the UPF network element enables microflow scheduling technology and optimizes the transmission rate by combining it with the L4S TCPPrague algorithm.

[0127] Here, the QoS flow is detected by the UPF network element, and it is the service data flow corresponding to the service.

[0128] In one specific embodiment, an explicit congestion notification flag is set in the IP (Internet Protocol) header of data packets in the QoS flow.

[0129] It is understandable that implementing low-latency queue management strategies in core network UPF elements and access network equipment, combined with L4S (Low Latency, Low Loss, Scalable throughput) technology, can reduce end-to-end latency, for example, ensuring that end-to-end latency is stable within 1ms.

[0130] In one embodiment, the low-latency queues configured in the UPF network element and access network equipment may include dedicated queues and hybrid queues. Dedicated queues are used to process high-priority low-latency services, ensuring they receive sufficient resources. Hybrid queues are used to process ordinary services, with weight allocation ensuring priority processing of low-latency services. Furthermore, a priority-based scheduling algorithm, combined with weight allocation and resource reservation, is employed to ensure priority processing of low-latency services. The scheduling algorithm may employ LLQ (Low-Latency Queuing), WFQ, etc., dynamically adjusting parameters according to service requirements.

[0131] It should be understood that traditional FIFO (First In First Out) or PQ (Priority Queuing) mechanisms may cause high-priority packets to jitter due to queuing at intermediate nodes, while mechanisms such as CQ (Custom Queuing) / WFQ (Weighted Fair Queuing) require complex configuration and lack intelligence. In low-latency service scenarios, latency jitter needs to be controlled within 100µs, which existing mechanisms cannot meet. Based on this, the embodiments of this application provide more granular network congestion feedback through ECN marking, avoiding the long-tail delay of traditional queue management. In other words, it solves the problem that traditional congestion control relies on packet loss, leading to high latency, and achieves proactive and lossless congestion warning. It can coordinate with access network devices to actively decelerate without packet loss, thereby controlling latency jitter within 100µs.

[0132] The QoS guarantee method provided in this application embodiment involves the UPF network element marking data packets in the QoS flow based on explicit congestion notification marking when network congestion is detected. The marked data packets are then sent to the access network device. The explicit congestion notification marking is used to instruct the access network device to prioritize the processing of data packets marked with explicit congestion notification marking. This provides more granular network congestion feedback through ECN marking, thereby reducing latency jitter and ensuring service stability.

[0133] Based on any of the above embodiments, the method further includes: Receive the QoS identifier from the second QoS policy sent by the SMF network element; Based on the pre-configured mapping relationship between QoS identifiers and Differential Service Code Points (DSCPs), the DSCPs corresponding to the QoS identifiers in the second QoS policy are determined; the mapping relationship between QoS identifiers and DSCPs is used to indicate the one-to-one correspondence between multiple QoS identifiers and multiple DSCPs. Based on DSCP, packets in the QoS flow are marked so that the marked packets can be sent to the access network equipment.

[0134] Here, the mapping relationship between QoS identifiers and DSCP (Differentiated Services Code Point) is pre-configured. For example, the UPF network element deploys a QoS rule engine, which has a mapping relationship between QoS identifiers and DSCP. This allows for dynamic setting of DSCP flags based on the QoS identifiers; for instance, 5QI=2 (low-latency service) is mapped to DSCP=46 (EF PHB), ensuring low latency and low jitter. In other words, PHB (Per-Hop Behavior) uses fields such as DSCP and 802.1p for priority marking. For example, EF PHB (Expedited Forwarding Per-Hop Behavior) is used for video conferencing (low latency, low jitter).

[0135] In one specific embodiment, tagged data packets are transmitted to the access network device via the GTP-U (GPRS Tunnelling Protocol).

[0136] For access network devices, the device performs corresponding processing based on the DSCP in the data packet. For example, the access network device implements the corresponding PHB based on the DSCP in the data packet. That is, the access network device adopts frame-level priority scheduling based on the DSCP and reserves dedicated PRB resources.

[0137] It should be understood that, through the above methods, frame-level scheduling can be achieved, controlling the end-to-end latency of low-latency services to within 1ms, meeting the rigid requirements of scenarios such as industrial control and remote surgery, that is, improving the guarantee capability of low-latency services.

[0138] The QoS guarantee method provided in this application embodiment, when determining that the service corresponding to the QoS flow is a low-latency service, the UPF network element receives the QoS identifier in the second QoS policy sent by the SMF network element, so that the UPF network element obtains the accurate and up-to-date QoS identifier. Based on the pre-configured mapping relationship between the QoS identifier and DSCP, the DSCP corresponding to the QoS identifier in the second QoS policy is determined, so as to accurately map the QoS policy of the core network to the IP network. This allows the data packets in the QoS flow to be correctly identified and prioritized in the subsequent forwarding process, thereby reducing the end-to-end transmission latency and ultimately ensuring the QoS of low-latency services.

[0139] Based on any of the above embodiments, the method further includes: Send the resource status data of the UPF network element to the analysis network element; The third QoS policy sent by the analysis network element is received and analyzed; the third QoS policy is determined by the analysis network element based on the resource status data of the UPF network element.

[0140] Here, the analysis network element is used to perform data analysis to determine the updated third QoS policy based on the collected data (including resource status data of the SMF network element). In one embodiment, the analysis network element is an AI analysis engine, which can determine the updated third QoS policy based on AI algorithms; further, the analysis network element is GPM, as detailed in the following embodiments.

[0141] In one embodiment, the collected data only includes resource status data of UPF network elements, meaning the updated third QoS policy can be determined by the analysis network element based solely on the resource status data of the UPF network elements. In another embodiment, the collected data may further include at least one of the following: resource status data reported by other core network elements besides the UPF network elements, traffic characteristics of QoS flows, and resource status data of access network devices. It should be noted that the updated content of the QoS policy will differ based on different collected data.

[0142] Here, resource status data is used to indicate the resource status of network elements, which may include, but is not limited to, at least one of the following: CPU utilization, memory usage, bandwidth usage, etc.

[0143] In one specific embodiment, the resource status data of the UPF network element is sent to the analysis network element through the Telemetry interface.

[0144] In one specific embodiment, the resource status data of the UPF network element is sent to the analysis network element in real time.

[0145] Furthermore, based on network load, the data collection frequency is determined; based on the data collection frequency, the resource status data of the UPF network element is sent to the analysis network element. Therefore, the data collection frequency can be dynamically adjusted according to network load, for example, increasing the data collection frequency during high load periods, thereby improving the decision-making accuracy of the third QoS strategy.

[0146] In one specific embodiment, for the analysis network element, a third QoS policy is generated based on the collected data. The collected data includes resource status data of the UPF network element, and may also include at least one of the following: resource status data reported by other core network elements, traffic characteristics of QoS flows, and resource status data of access network devices.

[0147] It should be understood that, considering that existing QoS parameter configurations are mostly static policies, they cannot dynamically reserve bandwidth or adjust priorities based on service bursts (such as emergency braking signals in autonomous driving). In high-load scenarios, low-latency services may experience increased latency due to resource contention. Therefore, in this embodiment, the core network element reports resource status data to the analysis network element, which then determines a third QoS policy based on the resource status data. This optimizes dynamic resource management, solves the problem of existing static policies failing to cope with dynamic network changes, and improves network resource utilization and efficiency while ensuring the QoS of low-latency services.

[0148] The QoS guarantee method provided in this application improves network resource utilization and efficiency by analyzing network elements and adjusting QoS policies in advance, thereby guaranteeing the QoS of low-latency services.

[0149] Based on any of the above embodiments, this application also provides a QoS guarantee method applied to PCF network elements. Figure 5 This is the fifth flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as shown below. Figure 5 As shown, the QoS guarantee method includes steps 510, 520 and 530.

[0150] Step 510: Upon receiving the slice identifier sent by the Session Management Function (SMF) network element, determine the new QoS identifier corresponding to the slice identifier based on the pre-configured slice-QoS identifier mapping relationship.

[0151] Here, the slice identifier is used to uniquely identify a network slice, for example, it is S-NSSAI.

[0152] The slice-to-QoS identifier mapping relationship is used to indicate the one-to-one correspondence between multiple slice identifiers and multiple QoS identifiers.

[0153] In one specific embodiment, the mapping relationship between slices and QoS identifiers is a mapping table. For example, the slice-QoS identifier mapping table is pre-configured in the PCF network element. For instance, uRLLC slice SST (Slice / Service Type) = 1 is bound to 5QI = 2 by default. When the terminal selects a uRLLC slice, the PCF network element automatically assigns the corresponding 5QI value to ensure that the service type and QoS parameters are automatically associated.

[0154] Step 520: Determine the declared QoS policy based on the new QoS identifier.

[0155] It should be noted that when a QoS identifier is received from an SMF network element, the declared QoS policy is determined directly based on the QoS identifier included in the declaration message.

[0156] Step 530: Send the declared QoS policy to the SMF network element.

[0157] In one specific embodiment, the declared QoS policy is sent to the SMF network element via the N7 interface.

[0158] The QoS guarantee method provided in this application embodiment determines the QoS policy based on the active declaration of the terminal, ensuring the accurate transmission of QoS parameters from the service source. This allows the most suitable QoS policy to be matched at the beginning of the session establishment, avoiding the delay of subsequent dynamic adjustment of the QoS policy, and ultimately ensuring the true QoS guarantee of low-latency services. At the same time, the PCF network element determines the new QoS identifier corresponding to the slice identifier based on the pre-configured slice-QoS identifier mapping relationship, and determines the declared QoS policy based on the new QoS identifier. Thus, the QoS policy can be automatically determined based on the slice identifier, realizing the automatic binding of network slices and QoS policies without the need for a lot of other processing, thereby simplifying the QoS guarantee process and improving the QoS guarantee efficiency. Moreover, the pre-configured slice-QoS identifier mapping relationship ensures the consistency of QoS policies for the same network slice.

[0159] Based on any of the above embodiments, this application also provides a QoS guarantee method applied to network element analysis. Figure 6 This is the sixth flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as shown below. Figure 6 As shown, the QoS guarantee method includes steps 610 and 620.

[0160] Step 610: Generate a third QoS policy based on the collected data.

[0161] Here, the analysis network element is used to perform data analysis to determine an updated third QoS policy based on the collected data. In one embodiment, the analysis network element is an AI analysis engine, which can determine the updated third QoS policy based on AI algorithms.

[0162] The collected data includes at least one of the following: resource status data reported by one or more core network elements, traffic characteristics of QoS flows, and resource status data of access network devices. In one embodiment, the collected data is collected in real time.

[0163] Here, one or more core network elements may include, but are not limited to, at least one of the following: AMF network element, SMF network element, UPF network element, etc.

[0164] Here, the resource status data reported by the core network elements is used to indicate the resource status of the core network elements, which may include, but is not limited to, at least one of the following: CPU utilization, memory usage, bandwidth usage, etc.

[0165] Here, the QoS flow is detected by the UPF network element, and it is the service data flow corresponding to the service. Traffic characteristics are used to characterize the features of the QoS flow, which may include, but are not limited to, at least one of the following: burst packet rate, packet size, and packet arrival interval, etc.

[0166] Here, the resource status data of the access network device may include, but is not limited to, at least one of the following: PRB utilization, channel quality, etc. For the access network device, it shares its resource status data with the analysis network element through the X2 / Xn interface.

[0167] It should be noted that the updates to the QoS policy will differ based on different collected data. The collected data provides the basis for QoS policy decisions. This third QoS policy may include, but is not limited to, at least one of the following: priority adjustment, resource reservation, path switching, etc. For example, when congestion is predicted in a cell, the priority of uRLLC services within that cell can be adjusted in advance to ensure they receive sufficient resources.

[0168] In one specific embodiment, the collected data is input into a policy generation model to obtain a third QoS policy output by the policy generation model, which is trained based on the sample collected data. Further, the policy generation model is trained on an initial network model based on the sample collected data and its corresponding third QoS policy label.

[0169] Step 620: Send the third QoS policy to one or more target core network elements.

[0170] Here, one or more target core network elements are related network elements, and one or more target core network elements may include, but are not limited to, at least one of the following: SMF network element, UPF network element, and AMF network element, etc.

[0171] In one specific embodiment, a third QoS policy is sent to one or more target core network elements through a service-oriented interface.

[0172] Furthermore, based on network conditions, the policy distribution frequency is determined; based on the policy distribution frequency, a third QoS policy is sent to one or more target core network elements. Therefore, the policy distribution frequency can be dynamically adjusted according to network conditions, for example, increasing the policy distribution frequency when congestion is high, thereby ensuring timely adjustment of QoS policies and reducing transmission latency.

[0173] It should be understood that, considering that existing QoS parameter configurations are mostly static policies, they cannot dynamically reserve bandwidth or adjust priorities based on service bursts (such as emergency braking signals in autonomous driving). In high-load scenarios, low-latency services may experience increased latency due to resource contention. Therefore, in this application embodiment, core network elements or access network devices report resource status data to an analysis network element. The analysis network element then determines a third QoS policy based on the resource status data and the traffic characteristics of the QoS flow, thereby optimizing dynamic resource management. This solves the problem of existing systems relying on static policies and being unable to cope with dynamic network changes. Furthermore, by adjusting QoS policies in advance (such as resource reservation or priority adjustment) through the analysis network element, network resource utilization and efficiency are improved while ensuring the QoS of low-latency services. In other words, by fusing multi-source data for prediction, the approach is upgraded from "passive response" to "active prediction," thereby achieving efficient network resource utilization and stable low-latency service assurance in complex scenarios.

[0174] The QoS guarantee method provided in this application improves network resource utilization and efficiency by analyzing network elements and adjusting QoS policies in advance.

[0175] Based on any of the above embodiments, in this method, step 610 includes: The collected data is input into the network congestion prediction model to obtain the network congestion prediction results output by the network congestion prediction model. A third QoS policy is generated based on the network congestion prediction results.

[0176] The network congestion prediction model is trained based on sample collection data. This model is a machine learning model. It can be constructed using algorithms such as Random Forest and LSTM (Long Short-Term Memory), which will not be elaborated upon here. Furthermore, the network congestion prediction model is trained on an initial neural network model based on the sample collection data and its corresponding network congestion prediction result labels.

[0177] In one embodiment, the network congestion prediction model includes a feature extraction layer and a prediction layer connected in sequence. Specifically, the collected data is input to the feature extraction layer to obtain the feature vector output by the feature extraction layer, and the feature vector is input to the prediction layer to obtain the network congestion prediction result output by the prediction layer.

[0178] Here, network congestion prediction results may include, but are not limited to, at least one of the following: congestion probability, latency prediction value, and available resource quantity, etc. These network congestion prediction results can be used to indicate whether a QoS policy needs to be updated, and if so, to indicate the QoS parameters or QoS rules that need to be updated.

[0179] Furthermore, the collected data and historical network status data are input into the network congestion prediction model to obtain the network congestion prediction results output by the model. Based on this, the accuracy of network congestion prediction is further improved, thereby enhancing the accuracy of the third QoS strategy generation.

[0180] It should be noted that after predicting network congestion trends, a dynamic third QoS policy can be generated. That is, the network congestion prediction results are used to provide a basis for QoS policy decisions. This third QoS policy can include, but is not limited to, at least one of the following: priority adjustment, resource reservation, path switching, etc. For example, when congestion is predicted in a certain cell, the priority of uRLLC services within that cell can be adjusted in advance to ensure they receive sufficient resources.

[0181] Furthermore, a third QoS policy is generated based on the network congestion prediction results and collected data. This further improves the accuracy of the generated third QoS policy. In one specific embodiment, the network congestion prediction results and collected data are input into the policy generation model to obtain the third QoS policy output by the policy generation model. This policy generation model is trained based on sample network congestion prediction results and sample collected data.

[0182] The QoS guarantee method provided in this application provides a method that analyzes network elements to predict network congestion prediction results, thereby adjusting QoS policies in advance. This improves network resource utilization and efficiency while guaranteeing the QoS of low-latency services.

[0183] Based on any of the above embodiments, the network element being analyzed is the GPM (Global Processing Module).

[0184] In one embodiment, GPM maintains user-node binding relationships (such as a user-node binding relationship table), which records each user's QoS identifier, the currently serving UPF network element / access network device node, resource reservation status, etc.

[0185] In one embodiment, GPM manages the binding relationship between users and AMF nodes through a state machine mechanism, ensuring that the same user registers only on one AMF node and avoiding context conflicts.

[0186] In one embodiment, the GPM maintains user context information, which may include, but is not limited to, user identity, service type, QoS parameters, etc. Based on this, when a user moves between different nodes, the GPM ensures seamless migration of the user context, avoiding service interruption. For example, when a terminal switches from one access network device to another, the GPM notifies the target access network device to reserve resources in advance, ensuring low latency during the handover process.

[0187] In one embodiment, the GPM adopts a distributed architecture and is deployed on the core network control plane.

[0188] In one embodiment, the GPM has a global resource coordination function. The GPM maintains the binding relationship between users and the optimal resource node and dynamically adjusts the QoS policy according to the real-time resource status. More specifically, it generates parameters such as 5QI, DSCP, and PRB reservation based on the collected data, and selects the optimal UPF through NRF service discovery.

[0189] It should be understood that the third QoS policy generated by GPM is a global policy. For example, when resource constraints are detected in a certain UPF network element, GPM triggers the SMF network element to redirect new users to other UPF network elements.

[0190] In one specific embodiment, a third QoS policy is sent to one or more target core network elements via the HTTP / 2 protocol, thereby ensuring the timeliness and effectiveness of policy distribution.

[0191] The QoS guarantee method provided in this application can ensure global policy adjustment by adjusting the QoS policy in advance through GPM, and can improve the accuracy of the generation of the third QoS policy, thereby improving network resource utilization and network resource utilization efficiency while guaranteeing the QoS of low-latency services.

[0192] Based on any of the above embodiments, this application also provides a QoS guarantee method applied to access network devices. Figure 7 This is the seventh flowchart illustrating the QoS guarantee method provided in the embodiments of this application, as shown below. Figure 7 As shown, the QoS guarantee method includes steps 710 and 720.

[0193] Step 710: Receive data packets sent by the User Plane Function (UPF) network element.

[0194] Step 720: If the data packet includes a display congestion notification flag, the data packet is processed preferentially.

[0195] Accordingly, the terminal supports the TCP Prague algorithm, adjusting the transmission rate based on the ECN tag to avoid the sawtooth waveform rate variations of traditional TCP algorithms. More specifically, the terminal and the core network coordinate to adjust the transmission rate, implementing the TCP Prague algorithm. Based on this, a balance between low latency and high throughput is achieved.

[0196] In one specific embodiment, if an explicit congestion notification flag is set in the packet's IP header, the packet is processed with priority.

[0197] In one specific embodiment, when a data packet includes an explicit congestion notification flag, low-latency queue scheduling is triggered to avoid traditional queue congestion. Specifically, the access network device is configured with a low-jitter queue to prioritize processing data packets with explicit congestion notification flags.

[0198] Understandably, implementing low-latency queue management strategies in core network UPF elements and access network equipment, combined with L4S technology, reduces end-to-end latency, for example, ensuring that end-to-end latency is consistently below 1ms. In other words, through low-jitter queue management and L4S technology, latency jitter for URLLC services is controlled to within 100µs, ensuring service stability.

[0199] It should be understood that traditional FIFO or PQ mechanisms may cause high-priority data packets to jitter due to queuing at intermediate nodes, while mechanisms such as CQ / WFQ require complex configuration and lack intelligence. In low-latency service scenarios, latency jitter needs to be controlled within 100µs, which existing mechanisms cannot meet. Based on this, the embodiments of this application provide more granular network congestion feedback through ECN marking, avoiding the long-tail delay of traditional queue management. In other words, it solves the problem that traditional congestion control relies on packet loss, resulting in high latency, and achieves proactive and lossless congestion warning. It can coordinate with access network devices to actively decelerate without packet loss, thereby controlling latency jitter within 100µs.

[0200] The QoS guarantee method provided in this application prioritizes data packets when the data packet includes an explicit congestion notification tag, thereby providing more granular network congestion feedback through the ECN tag, thereby reducing latency jitter and ensuring service stability.

[0201] Based on the above embodiments, this application provides a QoS guarantee method supporting low-latency services. By optimizing the coordination mechanism between the core network and the access network, it achieves refined QoS guarantee for low-latency services such as URLLC, addressing the shortcomings of existing 5G core network QoS mechanisms in low-latency service scenarios. Furthermore, through refined QoS guarantee, the stability and reliability of low-latency services are ensured, significantly improving the user experience.

[0202] Figure 8An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 8 As shown, the electronic device may include: a processor 810, a communications interface 820, a memory 830, and a communications bus 840, wherein the processor 810, the communications interface 820, and the memory 830 communicate with each other through the communications bus 840.

[0203] This application also provides an electronic device applied to an SMF network element, wherein the processor 810 included therein can call logical instructions in the memory 830 to execute the QoS guarantee method of any of the above embodiments applied to the SMF network element.

[0204] This application also provides an electronic device applied to an AMF network element, wherein the processor 810 included therein can call logical instructions in the memory 830 to execute the QoS guarantee method of any of the above embodiments applied to the AMF network element.

[0205] This application also provides an electronic device applied to a UPF network element, wherein the processor 810 included therein can call logical instructions in the memory 830 to execute the QoS guarantee method of any of the above embodiments applied to the UPF network element.

[0206] This application also provides an electronic device applied to a PCF network element, wherein the processor 810 included therein can call logical instructions in the memory 830 to execute the QoS guarantee method of any of the above embodiments applied to the PCF network element.

[0207] This application also provides an electronic device applied to an analysis network element, wherein the processor 810 therein can call logical instructions in the memory 830 to execute the QoS guarantee method of any of the embodiments applied to the analysis network element described above.

[0208] Furthermore, the logical instructions in the aforementioned memory 830 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0209] Figure 9 This is a schematic diagram of the structure of the access network device provided in the embodiments of this application, such as... Figure 9 As shown, the access network device includes a memory 920, a transceiver 910, and a processor 900; wherein the processor 900 and the memory 920 can also be physically arranged separately.

[0210] The memory 920 is used to store computer programs; the transceiver 910 is used to receive and send data under the control of the processor 900.

[0211] Among them, Figure 9 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 910 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0212] The processor 900 is responsible for managing the bus architecture and general processing, while the memory 920 can store the data used by the processor 900 during operation.

[0213] Optionally, the processor 900 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0214] The processor 900 invokes a computer program stored in the memory 920 to execute any of the QoS guarantee methods provided in this application embodiment for access network devices according to the obtained executable instructions, including: Receive data packets sent by the User Plane Function (UPF) network element; If a packet includes a display congestion notification flag, that packet should be processed preferentially.

[0215] It should be noted that the access network device provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0216] On the other hand, embodiments of this application also provide a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the QoS guarantee methods provided by the above methods.

[0217] In another aspect, embodiments of this application also provide a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform the QoS guarantee methods provided by the methods described above.

[0218] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0219] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0220] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. 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. Such 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 QoS guarantee method, characterized in that, The QoS guarantee method applied to the Session Management Function (SMF) network element includes: Upon detecting changes in service requirements, the latest Quality of Service (QoS) parameters are sent to the User Plane Function (UPF) network element, and a policy update command is sent to the Access and Mobility Management Function (AMF) network element. The latest QoS parameters include resource reservation rules. The policy update instruction is used to request the AMF network element to send the latest QoS parameters to the access network device, and the resource reservation rules are used to request resource reservation.

2. The QoS guarantee method according to claim 1, characterized in that, Before sending the latest Quality of Service (QoS) parameters to the User Plane Function (UPF) network element and sending the policy update instruction to the Access and Mobility Management Function (AMF) network element, the method further includes: A first policy update request is sent to the policy control function (PCF) network element; the first policy update request is used to request the PCF network element to update the QoS policy. The updated first QoS policy returned by the PCF network element is received; the first QoS policy includes the latest QoS parameters.

3. The QoS guarantee method according to claim 1, characterized in that, The UPF network element is determined based on the following method: A service discovery request is initiated by the Network Resource Function (NRF) network element, which is used to query the UPF network element based on the location of the access network device.

4. The QoS guarantee method according to any one of claims 1 to 3, characterized in that, Also includes: If the traffic characteristics of the QoS flow determine that the service corresponding to the QoS flow is a low-latency service, a second policy update request is sent to the PCF network element. The second policy update request is used to request the PCF network element to update the QoS policy of the QoS flow, wherein the QoS policy includes a QoS identifier; Receive the updated second QoS policy returned by the PCF network element.

5. The QoS guarantee method according to claim 4, characterized in that, Before sending the second policy update request to the PCF network element, the method further includes: The receiver sends a non-access stratum (NAS) message; the NAS message includes a declaration message, which includes a QoS identifier and / or a slice identifier. The declaration message is sent to the PCF network element; the declaration message is used to instruct the PCF network element to determine the declared QoS policy; Receive the declared QoS policy returned by the PCF network element.

6. The QoS guarantee method according to claim 4, characterized in that, After receiving the updated second QoS policy returned by the PCF network element, the method further includes: Send the QoS identifier from the second QoS policy to the UPF network element.

7. The QoS guarantee method according to any one of claims 1 to 3, characterized in that, Also includes: Send the resource status data of the SMF network element to the analysis network element; Receive the third QoS policy sent by the analysis network element; The third QoS policy is determined by the analysis network element based on the resource status data.

8. A QoS guarantee method, characterized in that, The QoS guarantee method applied to Access and Mobility Management Function (AMF) network elements includes: Upon receiving a policy update instruction from the Session Management Function (SMF) network element, the latest QoS parameters are sent to the access network device. The latest QoS parameters include resource reservation rules, which are used to request the access network device to reserve resources.

9. The QoS guarantee method according to claim 8, characterized in that, Also includes: Send the resource status data of the AMF network element to the analysis network element; Receive the third QoS policy sent by the analysis network element; The third QoS policy is determined by the analysis network element based on the resource status data.

10. A QoS guarantee method, characterized in that, The QoS guarantee method, applied to User Plane Function (UPF) network elements, includes: Receive the latest QoS parameters sent by the Session Management Function (SMF) network element; The latest QoS parameters include resource reservation rules, which are used to request the UPF network element to reserve resources.

11. The QoS guarantee method according to claim 10, characterized in that, Also includes: In the event of network congestion, packets in the QoS flow are marked based on explicit congestion notification marking, so that the marked packets are sent to the access network device. The explicit congestion notification tag is used to instruct the access network device to prioritize processing data packets tagged with the explicit congestion notification tag.

12. The QoS guarantee method according to claim 10 or 11, characterized in that, Also includes: Receive the QoS identifier from the second QoS policy sent by the SMF network element; Based on the pre-configured mapping relationship between QoS identifiers and Differential Service Code Points (DSCPs), the DSCP corresponding to the QoS identifier in the second QoS policy is determined. The QoS identifier and DSCP mapping relationship is used to indicate the one-to-one correspondence between multiple QoS identifiers and multiple DSCPs; Based on the DSCP, data packets in the QoS flow are marked so that the marked data packets can be sent to the access network device.

13. The QoS guarantee method according to claim 10 or 11, characterized in that, Also includes: Send the resource status data of the UPF network element to the analysis network element; Receive the third QoS policy sent by the analysis network element; The third QoS policy is determined by the analysis network element based on the resource status data.

14. A QoS guarantee method, characterized in that, The QoS guarantee method, applied to the policy control function (PCF) network element, includes: Upon receiving a slice identifier sent by the Session Management Function (SMF) network element, a new QoS identifier corresponding to the slice identifier is determined based on the pre-configured slice-QoS identifier mapping relationship; the slice-QoS identifier mapping relationship is used to indicate the one-to-one correspondence between multiple slice identifiers and multiple QoS identifiers. Based on the new QoS identifier, determine the declared QoS policy; Send the declared QoS policy to the SMF network element.

15. A QoS guarantee method, characterized in that, Applied to network elements for analysis, the QoS guarantee method includes: Based on the collected data, a third QoS policy is generated; the collected data includes at least one of the following: resource status data reported by one or more core network elements, traffic characteristics of QoS flows, and resource status data of access network devices. The third QoS policy is sent to one or more target core network elements.

16. The QoS guarantee method according to claim 15, characterized in that, The generation of a third QoS policy based on the collected data includes: The collected data is input into the network congestion prediction model to obtain the network congestion prediction result output by the network congestion prediction model. Based on the network congestion prediction results, a third QoS policy is generated; The network congestion prediction model is trained based on sample collection data.

17. A QoS guarantee method, characterized in that, Applied to access network equipment, the QoS guarantee method includes: Receive data packets sent by the User Plane Function (UPF) network element; If the data packet includes a display congestion notification flag, the data packet is processed with priority.

18. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, Applied to a Session Management Function (SMF) network element, the processor, when executing the computer program, implements the QoS guarantee method as described in any one of claims 1 to 7.

19. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, Applied to the Access and Mobility Management Function (AMF) network element, the processor implements the QoS guarantee method as described in claim 8 or 9 when executing the computer program.

20. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, Applied to the User Plane Function (UPF) network element, the processor, when executing the computer program, implements the QoS guarantee method as described in any one of claims 10 to 13.

21. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, Applied to the policy control function PCF network element, the processor implements the QoS guarantee method as described in claim 14 when executing the computer program.

22. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, Applied to network elements for analysis, the processor, when executing the computer program, implements the QoS guarantee method as described in any one of claims 15 or 16.

23. An access network device, characterized in that, Includes memory, transceiver, and processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Receive data packets sent by the User Plane Function (UPF) network element; If the data packet includes a display congestion notification flag, the data packet is processed with priority.

Images