Quality of service assurance system and quality of service assurance method

Abstract

This invention discloses a quality of service (QoS) assurance system and method. The IoT terminal identifies the type of service it is running and receives configuration instructions, configuring service source ports for different service flows according to the configuration instructions. The terminal management platform controls the IoT terminal and obtains its terminal information to generate service flow information. The terminal management platform also generates configuration instructions based on the service flow information and sends these instructions to the IoT terminal. The enhanced AF layer obtains the service flow information from the terminal management platform and constructs enhancement requests based on the service flow information. The 5G core network layer obtains the enhancement requests and generates and executes service policies based on the enhancement requests. This invention can provide differentiated services and ensure the QoS of various service flows.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to a service quality assurance system and service quality assurance method. Background Technology

[0002] With the widespread application of 5G technology in IoT scenarios, stringent requirements have been placed on latency, bandwidth, and reliability of service transmission in fields such as industrial control and telemedicine. Existing 5G network QoS (Quality of Service) assurance schemes are mainly based on the 3GPP standard architecture, achieving coordination between the application layer and the network side through the N5 interface.

[0003] However, existing service quality assurance solutions rely on information such as destination IP address and destination port to identify service flows, and cannot distinguish between different service flows within the same terminal (sharing the same source IP address). For example, in smart manufacturing scenarios, real-time control commands and periodic status reports of industrial robots are both sent to the same cloud platform. Existing technologies cannot accurately distinguish between the two types of services, leading to network resource mismatch or insufficient protection of critical services, thereby reducing service quality. Summary of the Invention

[0004] This invention provides a service quality assurance system and a service quality assurance method, aiming to solve the problem of poor service quality caused by the inability of current service quality assurance schemes to distinguish between different services.

[0005] In a first aspect, embodiments of the present invention also provide a Quality of Service (QoS) assurance system, comprising an IoT terminal, a terminal management platform, an enhanced AF layer, and a 5G core network layer; the IoT terminal is used to identify the service type it is running and receive configuration instructions, and configure service source ports for different service flows according to the configuration instructions; the terminal management platform is used to control the IoT terminal and obtain terminal information of the IoT terminal to generate service flow information, wherein the service flow information includes IMEI information, source IP address, the service source port, the service type, and requirement parameters, and the IMEI information is bound one-to-one with the source IP address, and the service source port is bound to a combination of the IMEI information and the source IP address and to the service type and the requirement parameters, respectively; the terminal management platform is also used to generate configuration instructions according to the service flow information and send the configuration instructions to the IoT terminal; the enhanced AF layer is used to obtain the service flow information from the terminal management platform and construct enhancement requests according to the service flow information; the 5G core network layer is used to obtain the enhancement requests and generate and execute service policies according to the enhancement requests.

[0006] Furthermore, the 5G core network layer also includes PCF, SMF, and UPF; the PCF is used to obtain the enhancement request and generate the service policy according to the requirement parameters in the enhancement request, and send the service policy to the SMF, the SMF is used to forward the service policy to the UPF, and the UPF is used to execute the service policy.

[0007] Furthermore, the PCF is also used to parse the enhancement request to obtain IMEI information and generate a policy log based on the IMEI information.

[0008] Furthermore, the 5G core network layer includes a UDM, which is used to store the permanent subscription data of the IoT terminal.

[0009] In a second aspect, embodiments of the present invention provide a service quality assurance method for controlling the service quality assurance system described in any of the above claims, the method comprising: The enhanced AF layer obtains the service flow information from the terminal management platform, constructs the enhancement request based on the service flow information, and then sends the enhancement request to the 5G core network layer. The service flow information includes port configuration information, which is used to configure the service type of the service source port, and one service source port is matched with one service type. The 5G core network layer obtains the enhancement request and generates the service policy based on the enhancement request to ensure service quality.

[0010] This invention provides a Quality of Service (QoS) assurance system and method. The QoS assurance system includes an IoT terminal, a terminal management platform, an enhanced AF layer, and a 5G core network layer. The IoT terminal can identify the type of service it is running, receive configuration instructions, and configure corresponding service source ports for different service flows according to the configuration instructions. The terminal management platform can manage and control the IoT terminal, obtain the terminal information of the IoT terminal, and generate service flow information. The service flow information includes IMEI information, source IP address, service source port, service type, and requirement parameters. The IMEI information and source IP address are bound one-to-one. The service source port is bound to both the combination of IMEI information and source IP address, as well as to the service type and requirement parameters. In addition, the terminal management platform will formulate configuration instructions based on the generated service flow information and send the configuration instructions to the IoT terminal. The enhanced AF layer can obtain the above service flow information from the terminal management platform and construct enhancement requests based on the service flow information. The 5G core network layer can obtain the enhancement request, generate corresponding service policies based on the enhancement request, and execute the policies. Through the coordinated operation of components at each layer, this system can accurately identify and control different business flows of IoT terminals, adapt corresponding network service guarantee strategies for different business flows, thereby providing differentiated services and ensuring the service quality of various business flows. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a block diagram of the service quality assurance system provided in an embodiment of the present invention; Figure 2 This is a sequence diagram of the core business process of the service quality assurance system provided in this embodiment of the invention; Figure 3 This is a diagram illustrating the fusion architecture of IMEI information and port configuration information in the Quality of Service Assurance System provided in this embodiment of the invention. Figure 4 This is a flowchart illustrating the service quality assurance method provided in an embodiment of the present invention. Detailed Implementation

[0013] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] It should be understood that, when used in this specification and the appended claims, the terms “comprising” and “including” indicate the presence of the described features, integrals, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, operations, elements, components and / or collections thereof.

[0015] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this specification and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes such combinations.

[0016] See Figures 1 to 3 , Figure 1 This is a block diagram of the service quality assurance system provided in an embodiment of the present invention; Figure 2 This is a sequence diagram of the core business process of the service quality assurance system provided in this embodiment of the invention; Figure 3 This is a diagram illustrating the fusion architecture of IMEI information and port configuration information in the Quality of Service Assurance System provided in this embodiment of the invention. Figure 1As shown, the Quality of Service (QoS) assurance system includes an IoT terminal 10, a terminal management platform 20, an enhanced AF layer 30, and a 5G core network layer 40. The IoT terminal 10 is used to identify the service type it is running and receive configuration instructions, and configure service source ports for different service flows according to the configuration instructions. The terminal management platform 20 is used to control the IoT terminal 10 and obtain the terminal information of the IoT terminal 10 to generate service flow information. The service flow information includes IMEI information, source IP address, the service source port, the service type, and requirement parameters. The IMEI information is bound one-to-one with the source IP address, and the service source port is bound to a combination of the IMEI information and the source IP address, as well as to the service type and the requirement parameters. The terminal management platform 20 is also used to generate configuration instructions based on the service flow information and send the configuration instructions to the IoT terminal. The enhanced AF layer 30 is used to obtain the service flow information from the terminal management platform 20 and construct enhancement requests based on the service flow information. The 5G core network layer 40 is used to obtain the enhancement requests and generate and execute service policies based on the enhancement requests.

[0017] Specifically, the quality of service assurance system may include an IoT terminal 10, a terminal management platform 20, an enhanced AF layer 30, and a 5G core network layer 40, with the following specific functions: As the origin of business data, it can integrate an SDK (Software Development Kit) and has the ability to configure and use multiple service source ports. It is the foundation for realizing terminal-side business perception and execution. Each service source port uniquely matches a service type (such as real-time control commands, status data reporting, 4K ultrasonic video streams, etc.). The terminal can actively identify the various service types it is running through the SDK, and also has dynamic port configuration capabilities. It supports receiving port configuration commands issued by the terminal management platform 20, and completes the dynamic binding of service flows and service source ports. This ensures that data packets of different services are sent from the specified source port, laying the foundation for accurate identification of multiple services on one terminal on the network side. At the same time, the IoT terminal 10 uses IMEI as the core unique identifier and actively reports the terminal status, service status, and port configuration execution results to the terminal management platform 20. It is the starting point for the system to form a configuration and management closed loop.

[0018] The terminal management platform 20, as the core collaborative hub of the entire system, uses IMEI information as the core index to achieve centralized management and control of the entire lifecycle of the IoT terminal 10. Its core functions include: Based on the business characteristics and QoS requirements of typical high-demand IoT scenarios such as Industrial Internet, telemedicine, and intelligent connected vehicles, a standardized pre-configured rule base is implemented. First, business priorities are divided into high, medium, and low levels according to business type (e.g., real-time control commands, 4K video streams, status data reporting, etc.). Dedicated source port pool ranges are then bound to different priority services. Simultaneously, the port pools are fixedly associated with corresponding QoS (Quality of Service) requirement parameters (5QI value, GBR bandwidth, latency / packet loss rate thresholds), forming a standardized mapping rule of business type-priority-port pool range-QoS parameter. The rule base supports on-demand expansion and dynamic updates, allowing for the addition of new business types and adjustments to port pool ranges or QoS parameter matching relationships based on the customized needs of different industries.

[0019] Based on the aforementioned pre-built rule base, the terminal management platform 20 allocates primary service source ports within the corresponding priority port pools for different service flows of the terminal, while reserving sufficient spare port resources for each port pool. During the allocation process, the port usage status is monitored in real time. If port conflicts occur (such as duplicate port allocation for multiple service flows on the same terminal, or port reuse conflicts across terminals), the platform will automatically allocate an available spare port from the priority spare port pool corresponding to that service, completing the dynamic switching of ports. At the same time, the platform will update the real-time global mapping table of IMEI-source IP address-service source port in real time and send the new port configuration command to the IoT terminal. In addition, the platform also supports the dynamic reclamation of port resources. When a certain service of the terminal stops running, the platform will release the source port corresponding to that service and return it to the corresponding port pool, realizing the efficient reuse of port resources.

[0020] The terminal management platform 20 can receive information such as service identifier and service operation status reported by the IoT terminal SDK (Software Development Kit). Based on the service type of the terminal, it matches the platform's pre-set service-port-QoS mapping rule library, allocates port pools with corresponding priorities and QoS requirement parameters to it, realizes real-time mapping and command issuance from service status to port configuration and QoS requirements, and ensures that the terminal's service flow is accurately matched with the source port and QoS policy.

[0021] Terminal management platform 20 can provide enhanced AF layer 30 with complete service flow information including IMEI (International Mobile Equipment Identity), source IP address, service source port, service type, and QoS requirement parameters. It supports two data synchronization modes: real-time push and on-demand query, ensuring the accuracy and timeliness of information obtained by enhanced AF layer. This allows AF layer to proactively and accurately perceive terminal service intent, breaking away from the passivity of traditional solutions that can only initiate requests based on coarse destination addresses.

[0022] The enhanced AF (Application Function) layer 30 can serve as a bridge connecting the terminal management platform 20 and the 5G core network layer 40 for IoT business entities (such as industrial control platforms, medical management systems, etc.). It can obtain accurate service flow information including IMEI from the terminal management platform 20 through standardized APIs, and construct enhanced requests, namely enhanced N5 requests, in strict accordance with the service flow information and following the 3GPP standards. This enhanced N5 request abandons the traditional coarse-grained description based on destination IP / port, and can accurately specify the source IP address + service source port as the precise identifier of the service flow. At the same time, it can also explicitly carry IMEI information in the terminal context extension field, establish a strong association between policy and terminal identity, and solve the core defect of traditional N5 requests that cannot distinguish multiple service flows of the same terminal. In addition, the enhanced AF layer 30 also has policy lifecycle management capabilities, and can dynamically initiate the creation, update and deletion operations of enhanced N5 requests according to the service status changes synchronized by the terminal management platform 20.

[0023] The 5G core network layer 40 can be a 5G core network that conforms to the 3GPP standard. Its core function is to receive enhancement requests sent by the enhanced AF layer 30, generate differentiated service policies that match different service flows based on the precise content contained in the request, such as the source IP address, service source port, and IMEI information, and execute the service policies through network element division of labor. This ensures that each service flow meets the requirements of key indicators such as latency, bandwidth, reliability, and packet loss rate, thereby achieving differentiated QoS guarantee for IoT service flows.

[0024] As a further embodiment, the 5G core network layer 40 further includes PCF, SMF and UPF; the PCF is used to obtain the enhancement request and generate the service policy according to the requirement parameters in the enhancement request, and send the service policy to the SMF, the SMF is used to forward the service policy to the UPF, and the UPF is used to execute the service policy.

[0025] To achieve standardized generation, forwarding, and execution of service policies, the 5G core network layer 40 in this embodiment is further optimized into a three-tier architecture of PCF, SMF, and UPF, as detailed below: The Policy Control Function (PCF) receives enhancement requests from the Enhanced AF layer 30, parses the requirement parameters in the request (such as the QoS level, bandwidth requirements, and latency requirements corresponding to the service source port), and generates a targeted service policy by combining user subscription data and locally pre-configured policies. For example, for the control command port 44005 of an industrial robotic arm, if its requirement parameters are parsed as "latency ≤ 20ms, packet loss rate ≤ 0.1%, GBR = 2Mbps", a service policy of "src-ip = 192.168.10.1, src-port = 44005 → 5QI = 83, GBR = 2Mbps" is generated. After generation, the PCF sends the service policy to the SMF.

[0026] After receiving the service policy issued by the PCF, the SMF (Session Management Function) establishes a dedicated QoSFlow for the service flow that matches the policy and assigns a unique QoSFlow identifier. Then, it forwards the service policy and QoSFlow configuration to the UPF to ensure accurate policy delivery.

[0027] UPF (User Plane Function) can accurately identify different service flows based on the service policies issued by SMF, using a combination of "source IP address + service source port" to perform differentiated processing such as priority scheduling, bandwidth guarantee, and packet loss control. For example, high-priority scheduling is performed on the control command flow (port 44005) to ensure latency meets the target; stable bandwidth allocation is performed on the status reporting flow (port 44015) to avoid traffic surges.

[0028] As a further embodiment, the PCF is also used to parse the enhancement request to obtain IMEI information, and associate the IMEI information with the session ID to generate a policy log.

[0029] To address the difficulties in fault tracing and the lack of terminal-level security control in existing solutions, this embodiment adds IMEI-based tracing capabilities to the PCF, specifically implemented as follows: After receiving an enhancement request, PCF, in addition to parsing the required parameters, also extracts the terminal's unique IMEI information through the extended fields in the request. For example, the IMEI is parsed as "869123000000001" from the enhancement request of an industrial robotic arm, and as "867854000000001" from the enhancement request of an ultrasonic device.

[0030] PCF associates the parsed IMEI with the generated service policy and session ID to generate a policy log containing the terminal identity tag. The log content includes, but is not limited to: IMEI, source IP address, service source port, service type, service policy parameters (5QI value, GBR value, etc.), policy session establishment / update / deletion time, QoS indicator feedback results, etc.

[0031] When the UPF reports an abnormal QoS metric for a service flow (such as excessive latency or abnormal bandwidth usage), operations and maintenance personnel can quickly locate the specific physical terminal (rather than the abstract source IP address) using the IMEI in the policy log, thereby shortening the fault location time. Simultaneously, IMEI-based log recording can be used for resource abuse monitoring and security auditing, effectively preventing the risk of unauthorized terminals impersonating legitimate terminals to steal high-priority network resources.

[0032] like Figure 3 As shown, IMEI information is a unique identification tag for the terminal, which can be bound to the source IP address. That is, an IoT terminal 10 corresponds to only one source IP address (a fixed / dynamic IP assigned when the terminal accesses the network).

[0033] A single terminal may run multiple types of services (such as service type A and service type B). Each type of service can be assigned a dedicated service source port. For example, service type A (such as control commands) is bound to service source port 44005; service type B (such as status reporting) is bound to service source port 44015. Then, through the combination of "source IP address + service source port", the single service flow can be accurately identified (under the same IP, different ports correspond to different services). Based on this unique identifier, UPF can accurately match the QoS requirements corresponding to the service flow, and then execute differentiated service strategies (such as low latency strategy for service A and stable bandwidth strategy for service B).

[0034] As a further embodiment, the 5G core network layer 40 includes a UDM, which is used to store the permanent subscription data of the Internet of Things terminal 10.

[0035] In this embodiment, the 5G core network layer 40 further includes UDM (Unified Data Management), whose core function is to store the permanent subscription data of the IoT terminal 10. The permanent subscription data stored in UDM includes network access subscription information of the terminal / user (such as the user's permanent identifier), default QoS parameter templates, subscribed DNN (data network name), and other underlying policy baseline data. This data is a prerequisite for the terminal to legally access the network and obtain basic QoS guarantees.

[0036] When generating service policies, the PCF queries the subscription data in the UDM to verify whether the terminal is authorized to use the requested QoS level or service type. For example, if an IoT terminal 10 has a QoS level cap of 5QI=83, and its requested service flow QoS requirement is 5QI=90 (higher priority), the PCF will reject the request based on the subscription data in the UDM to ensure compliant allocation of network resources.

[0037] UDM can also provide the underlying policy benchmark for network access and service subscription. The terminal management platform 20 then implements fine-grained management of services in IoT scenarios (such as service-port mapping, IMEI whitelist authorization, etc.) on top of this benchmark, jointly ensuring the compliance and accuracy of the system.

[0038] The terminal management platform 30 can form a complementary and data-interoperable two-layer control system with the UDM. Together, they constitute the foundation for the full-process control of IoT terminals from network access to service transmission. The UDM serves as the underlying network access contract benchmark, while the terminal management platform is the core of upper-layer service-level policy control. The specific collaborative logic is as follows: UDM provides a standardized network access subscription benchmark: As a 5G core network element defined by the 3GPP standard, UDM is responsible for storing and managing the permanent network access subscription data of terminals / users, including SUPI verification, DNN (Data Network Name), default QoS parameter templates, etc., which is the foundation for IoT terminals to complete 5G network access. Terminals must first complete network access identity authentication and basic subscription checks in UDM to obtain network access permissions before they can initiate a registration request to the terminal management platform. UDM provides the network-level access and subscription compliance basis for the entire QoS guarantee system.

[0039] The terminal management platform 30 conducts upper-layer service-level control based on the UDM network access subscription benchmark. It uses IMEI as the core to realize refined control such as service-port mapping, dynamic allocation of port pools, and integration of service flow information. At the same time, it provides accurate service flow information to the AF layer to realize the conversion of terminal service intent to network QoS policy.

[0040] UDM and the terminal management platform have 30 functions that do not overlap and are mutually verifiable. UDM ensures that the terminal can access the network, while the terminal management platform ensures that the terminal can obtain accurate network QoS guarantees according to business needs. Together, they form a two-layer closed-loop system of underlying network access control and upper-layer service transmission control, achieving refined control of the entire process from network access to service transmission while adhering to 3GPP standards.

[0041] like Figure 2 As shown, Figure 2 The sequence diagram for the core business process is as follows, with the interaction logic as follows: Step 1: Basic Terminal Access and Service Registration 5G Registration and Authentication: IoT terminal 10 initiates 5G network access identity authentication to UDM (based on 3GPP standard procedures) to complete the legality verification of network access; Network access license: After the UDM verification is passed, a network access license is issued to IoT terminal 10, allowing the terminal to access the 5G network; Business layer registration (IMEI reporting): After accessing the network, IoT terminal 10 initiates business layer registration with terminal management platform 20 and reports its unique identity identifier (IMEI) to establish a business association between the terminal and the management platform; Step 2: Port Configuration Synchronization Port configuration information is issued: Based on the service type requirements of the terminal, the terminal management platform 20 issues a matching configuration of "service type - dedicated port" to the IoT terminal 10 (such as the control command corresponding to port 44005). Configuration confirmation feedback: After receiving and completing the port configuration, IoT terminal 10 sends a confirmation message to terminal management platform 20 to ensure that the configuration takes effect; Step 3: Interaction between business flow information and contract data Obtaining terminal information: Enhanced AF layer 30 requests information about the target terminal from terminal management platform 20; Terminal information return: The terminal management platform 20 returns complete terminal information (including port configuration, IMEI, and service type) to the enhanced AF layer 30. Query subscription data: Enhanced AF layer 30 queries UDM for the network subscription data of this terminal; Returning Subscription Data: UDM returns the terminal's permanent subscription data to Enhanced AF Layer 30 as the basis for policy generation; Step 4: Enhance request and policy generation and execution Sending an enhancement request: The enhanced AF layer 30 constructs an enhancement request containing "source IP + service source port + IMEI" based on terminal information and subscription data, and sends it to the PCF; Generate service strategies: PCF parses enhanced requests and generates differentiated service strategies (such as low-latency rules for controlling command flow) that match the business source port. Service policy distribution / forwarding: The PCF distributes the service policy to the SMF, and the SMF then forwards the policy to the UPF; Service policy execution: UPF performs quality of service processing such as priority scheduling and bandwidth guarantee on different service flows of the terminal (distinguished by source port) based on the policy; Step 5: Real-time indicator feedback Real-time metrics statistics: UPF periodically calculates real-time metrics (latency, bandwidth, packet loss rate, etc.) for each service source port. Forwarding real-time metrics: SMF forwards the UPF's real-time metrics to PCF, which can then be synchronized to the terminal management platform 20 for abnormal behavior judgment and dynamic policy adjustment.

[0042] The IoT terminal of the service quality assurance system provided by this invention can identify the type of service it is running and receive configuration instructions. It can also configure corresponding service source ports for different service flows according to these instructions. The terminal management platform can control the IoT terminal, acquire its terminal information, and generate service flow information. This service flow information includes IMEI information, source IP address, service source port, service type, and requirement parameters. The IMEI information and source IP address are bound one-to-one, and the service source port is bound to both the combination of IMEI information and source IP address, as well as the service type and requirement parameters. Furthermore, the terminal management platform will formulate configuration instructions based on the generated service flow information and send these instructions to the IoT terminal. The enhanced AF layer can obtain the aforementioned service flow information from the terminal management platform and construct enhancement requests based on this information. The 5G core network layer can obtain the enhancement request, generate corresponding service policies based on the enhancement request, and execute the policies. Through the coordinated operation of components at each layer, this system can accurately identify and control different service flows of the IoT terminal, adapt corresponding network service assurance policies for different service flows, thereby providing differentiated services and ensuring the service quality of various service flows.

[0043] Please see Figure 4 The present invention also provides a service quality assurance method. This service quality assurance method, according to embodiments of the present invention, is used to control the service quality assurance system described in any of the above embodiments, and is used to configure different service strategies for different service source ports to ensure service quality, such as... Figure 4 As shown, the method includes steps S110 to S120.

[0044] S110, the enhanced AF layer obtains the service flow information from the terminal management platform, constructs the enhancement request based on the service flow information, and then sends the enhancement request to the 5G core network layer. The service flow information includes port configuration information, which is used to configure the service type of the service source port, and one service source port matches one service type.

[0045] In this embodiment of the invention, by enhancing the collaboration between the AF layer and the terminal management platform, accurate service flow information containing multi-dimensional correlation information can be obtained and enhanced requests can be constructed, providing a core basis for the 5G core network layer to generate differentiated service strategies. Moreover, this service flow information is also the basis for the terminal management platform to issue port configuration instructions to IoT terminals.

[0046] When the enhanced AF layer needs to request QoS guarantees for the service flow of a target terminal, it first calls the service flow information interface of the terminal management platform through a standardized API to obtain the complete service flow information of the terminal. This service flow information includes IMEI information, source IP address, service source port, service type, and requirement parameters, and follows strict binding rules: the IMEI information and the source IP address are bound one-to-one. The service source port is uniquely bound to the combination of IMEI information and source IP address, and is also precisely bound to the service type and requirement parameters. The terminal management platform will generate corresponding configuration instructions based on this service flow information and send the configuration instructions to the IoT terminal to guide the terminal to complete the configuration of the service source port.

[0047] Based on the obtained complete service flow information, the enhanced AF layer constructs an enhanced request. This enhanced request abandons the traditional coarse-grained identification method and uses the source IP address + service source port as the precise identifier of the service flow in the flow descriptor, integrating requirement parameters into the policy request dimension, for example: permitoutipfrom192.168.10.1toanysrc-port=44005 At the same time, the terminal IMEI information is explicitly carried in the terminal context extension field of the enhanced request, establishing a strong association between the service flow, requirement parameters, and the physical identity of the terminal, for example: imei:869123000000001 After the enhancement request is constructed, the enhancement AF layer sends the enhancement request to the policy control function (PCF) of the 5G core network layer through the N5 interface of the 3GPP standard, providing accurate and complete information support for the subsequent generation of PCC rules and the execution of differentiated service policies.

[0048] In some embodiments, such as this embodiment, constructing the enhanced request based on the service flow information includes: The enhanced AF layer obtains the service source port, the IMEI information, the source IP address, and the service type from the service flow information; The enhanced AF layer obtains the preset mapping rules and constructs the enhanced request based on the service source port, the IMEI information, the source IP address, and the service type.

[0049] In this embodiment of the invention, the enhanced AF layer extracts four core types of information—service source port, IMEI information, source IP address, and service type—from the complete service flow information obtained from the terminal management platform, providing basic data support for the construction of enhanced requests. At the same time, the enhanced AF layer obtains pre-configured preset mapping rules, which are standardized mapping rules conforming to 3GPP standards. These rules pre-define the correspondence between service source port / service type and QoS requirement parameters (5QI value, guaranteed bit rate GBR, etc.), service flow description field format, and terminal context extension field configuration requirements, which are the key basis for realizing the standardized construction of enhanced requests.

[0050] The enhanced AF layer combines the extracted four types of core information with preset mapping rules to construct the enhanced request step by step according to the 3GPP standard N5 request format. The specific process is as follows: Based on the preset mapping rules, the flow description field format corresponding to the source IP address and service source port is used to accurately describe the service flow in the flowDescriptions field using a combination of source IP address and service source port, replacing the traditional coarse-grained description based on destination address. For example, for control services with source IP 192.168.10.1 and service source port 44005, the flow description statement is generated as: "permitoutipfrom192.168.10.1toanysrc-port=44005"; Based on the QoS requirement parameters corresponding to the service source port and service type in the preset mapping rules, the corresponding 5QI value, GBR and other QoS parameters are matched for each service flow and incorporated into the policy reference field of the enhanced request to form a differentiated QoS policy request basis. Based on the configuration requirements of the terminal context extension field in the preset mapping rules, the extracted IMEI information is explicitly carried in the terminalContext extension field. At the same time, the terminal type, port allocation source and other related information are supplemented in combination with the service type to establish a strong association between the service flow and the physical identity of the terminal. Through the above steps, core service flow information is integrated with standardized preset mapping rules to ultimately form a complete enhanced request that conforms to 3GPP standards and contains accurate service flow identifiers and terminal identity information.

[0051] S120, the 5G core network layer obtains the enhancement request and generates the service policy based on the enhancement request to ensure service quality.

[0052] In this embodiment of the invention, the 5G core network layer is a core network that follows the 3GPP standard architecture. Its network elements work together to process enhancement requests and generate and execute service policies according to their respective functions: The PCF (Policy Control Function) of the core network layer first receives the enhancement request sent by the enhancement AF layer through the N5 interface, performs a comprehensive analysis of the request content, and extracts related information such as the source IP address + service source port service flow precise identifier, IMEI information and terminal type, as well as QoS policy reference information matching the service source port and service type; then the PCF initiates a query to the UDM (Unified Data Management) to obtain the standardized network access subscription data of the terminal (such as SUPI verification information, DNN, default QoS parameter template, etc.), and completes the subscription compliance verification of the terminal QoS service request. The UDM provides the underlying network access subscription benchmark for policy decision-making, forming a complementary network-service dual-layer control system with the service-level control of the terminal management platform.

[0053] Based on the accurate parsed business flow information, IMEI terminal identity information, and UDM contract compliance verification results, the PCF generates a unique PCC rule for each source IP address and business source port corresponding to the business flow. Multiple PCC rules are combined to form a complete service policy for that terminal. Simultaneously, the PCF associates and records the IMEI information with the policy session, generating a policy log with a terminal identity tag, enabling precise traceability of the policy session and providing a basis for subsequent fault location and security auditing. The PCF then distributes the generated service policy (PCC rule) to the SMF (Session Management Function) via the N7 interface.

[0054] After receiving the service policy, the SMF establishes a dedicated QoSFlow for each service flow corresponding to the PCC rule and assigns it a unique QoS flow identifier. Then, it forwards the policy configuration and QoSFlow information to the UPF (User Plane Function) through the N4 interface. After receiving the configuration, the UPF accurately identifies the service flows in the network based on the combined identifier of the source IP address and the service source port. It performs differentiated QoS operations such as priority scheduling, bandwidth guarantee, and packet loss control for different service flows. It assigns matching 5QI values, GBR (Guaranteed Bit Rate), and other parameters to each service flow according to the service policy, ultimately achieving fine-grained quality of service assurance for each service flow at the user plane. At the same time, the UPF will collect QoS indicators such as latency, packet loss rate, and throughput of each service flow in real time and feed them back to the PCF through the SMF, forming a closed loop of state feedback for policy execution.

[0055] For example, in a remote medical ultrasound diagnostic scenario, the PCF resolves the device's IMEI (867854000000001), source IP (192.168.20.1), and precise information about the 4K ultrasound video stream (port 44025) and the doctor's control command stream (port 44035). After compliance verification using the UDM's contract data, a PCC rule of "5QI=71, GBR=5Mbps, packet loss rate ≤0.01%" is generated for port 44025, and a rule of "5QI=83, GBR=5Mbps" is generated for port 44035. The PCC rule of "1Mbps, latency ≤50ms" is combined with the other two rules to form the complete service policy for this ultrasound device. At the same time, the PCF associates the policy session with IMEI: 867854000000001. The UPF, based on this policy, allocates high bandwidth resources to the 4K ultrasound video stream and strictly controls the packet loss rate. It also performs high-priority scheduling for the doctor's control command stream to reduce transmission latency, ensuring that both types of services meet the stringent QoS requirements of the telemedicine scenario. If the subsequent video stream has a packet loss rate exceeding the standard, the maintenance personnel can quickly locate the specific ultrasound device through the IMEI.

[0056] In some embodiments, such as this embodiment, generating the service policy based on the enhanced request includes: The 5G core network layer parses the enhancement request to obtain the demand parameters, wherein one of the service source ports corresponds to one demand parameter; The 5G core network layer generates service rules that match the demand parameters based on the demand parameters, wherein one service rule corresponds to one service source port; The 5G core network layer generates the service policy based on multiple service rules.

[0057] In this embodiment of the invention, after receiving the enhancement request, the PCF of the 5G core network layer parses the flow descriptor and QoS requirements corresponding to each service source port to obtain the unique requirement parameters for each service source port. For example, the requirement parameters for port 44005 are: "Service type = control command, IP = 192.168.10.1, latency ≤ 20ms, packet loss rate ≤ 0.1%, bandwidth requirement = 2Mbps"; the requirement parameters for port 44015 are: "Service type = status reporting, source IP = 192.168.10.1, bandwidth stability = 1Mbps, packet loss rate ≤ 0.5%".

[0058] For each requirement parameter, PCF combines 3GPP QoS standards and terminal subscription data to generate corresponding service rules. Each service rule uniquely matches a service source port, and its core content includes: Service flow identifier: source IP address + service source port (e.g., src-ip=192.168.10.1, src-port=44005). QoS parameters: standard value (5QI value) and guaranteed bit rate (GBR), such as "5QI=83, GBR=2Mbps" and "5QI=71, GBR=1Mbps".

[0059] PCF integrates the service rules corresponding to all service source ports to form a complete service policy for the IoT terminal, ensuring that different service flows of the same terminal can obtain differentiated QoS guarantees.

[0060] In some embodiments, such as this one, the 5G core network layer generates service rules that match the demand parameters based on the demand parameters, including: The 5G core network layer parses the required parameters to obtain standard values ​​and guaranteed bit rates; The 5G core network layer generates the service rules based on the source IP address of the IoT terminal, the standard value, and the guaranteed bit rate.

[0061] In this embodiment of the invention, when resolving the PCF requirement parameters of the 5G core network layer, three core parameters are extracted: Source IP address of IoT terminal: used to accurately locate the initiating terminal of the business flow; Standard value: 5QI (5G QoS identifier), defined by the 3GPP standard, corresponds to basic parameters such as priority, latency, and bit error rate of packet forwarding and processing (e.g., 5QI=83 corresponds to high priority and low latency requirements, and 5QI=71 corresponds to medium-high priority and stable bandwidth requirements). Guaranteed Bit Rate (GBR): Ensures the minimum bandwidth resources available to the service flow to avoid service quality degradation due to insufficient bandwidth (e.g., control command flow GBR=2Mbps, status reporting flow GBR=1Mbps).

[0062] PCF associates the three core parameters mentioned above to construct service rules. For example, combining "source IP=192.168.10.1, standard value=5QI=83, guaranteed bit rate=2Mbps", the service rule "src-ip=192.168.10.1, src-port=44005→5QI=83, GBR=2Mbps" is generated; combining "source IP=192.168.10.1, standard value=5QI=71, guaranteed bit rate=1Mbps", the service rule "src-ip=192.168.10.1, src-port=44015→5QI=71, GBR=1Mbps" is generated.

[0063] In some embodiments, such as this embodiment, the quality of service assurance method further includes: The 5G core network layer periodically collects real-time metrics for each of the service source ports. The terminal management platform acquires the real-time indicators and determines whether the IoT terminal exhibits abnormal behavior based on the real-time indicators. When the IoT terminal exhibits abnormal behavior, the terminal management platform updates the enhancement request.

[0064] In this embodiment of the invention, the UPF of the 5G core network layer counts the real-time QoS indicators of each service source port according to a preset period (e.g., 100ms), including latency, packet loss rate, throughput, bandwidth utilization, etc., and feeds the real-time indicators back to the PCF through the SMF, and then synchronizes them to the terminal management platform.

[0065] After receiving real-time metrics, the terminal management platform compares them with preset QoS thresholds (such as control command latency ≤20ms, status reporting bandwidth fluctuation ≤±5%) to determine whether the IoT terminal exhibits abnormal behavior. Abnormal behavior includes, but is not limited to: continuously exceeding QoS limits, frequent switching of service source ports by the terminal, and sudden surges in bandwidth usage.

[0066] When abnormal behavior is detected on the terminal, the terminal management platform triggers a dynamic adjustment mechanism: If the port is abnormal (e.g., the port is occupied), a spare port will be reassigned and the port configuration information will be updated. If the service status changes (such as the terminal entering standby mode), then adjust the corresponding QoS requirement parameters. The terminal management platform synchronizes the updated service flow information to the enhanced AF layer, which then initiates enhancement request updates (including the establishment, modification, or deletion of policy sessions) to achieve dynamic adaptation of service policies.

[0067] For example, when the industrial robotic arm enters standby mode, the terminal management platform notifies the enhanced AF layer to update the enhancement request, releasing the GBR resources of control command port 44005 to avoid resource waste; when the terminal frequently changes ports, the terminal management platform reallocates spare ports and updates the policy to prevent security risks.

[0068] In some embodiments, such as this embodiment, the quality of service assurance method further includes: The IoT terminal sends registration information to the terminal management platform, wherein the registration information includes the terminal information; The terminal management platform verifies the identity of the IoT terminal and configures the port configuration information for the IoT terminal after the verification is successful.

[0069] In this embodiment of the invention, after the IoT terminal goes online, it first completes network access identity authentication and basic contract check in UDM through the standard 5G registration process; then, the terminal sends registration information to the terminal management platform through the SDK. The registration information includes terminal information such as IMEI information, terminal model, and terminal capabilities (such as supported service types).

[0070] After receiving the registration information, the terminal management platform queries the preset IMEI whitelist to verify the legitimacy of the terminal identity, rejects unauthorized terminal access, and ensures system security.

[0071] After identity verification is successful, the terminal management platform configures port configuration information for the terminal based on the terminal's business type requirements from the preset "business type-source port range" mapping library, identifies the exclusive business source port corresponding to each business type, and sends the port configuration information to the IoT terminal to complete the configuration synchronization between the terminal and the platform.

[0072] For example, after a robotic arm (IMEI=869123000000001) in a smart manufacturing scenario is registered, the terminal management platform configures its port configuration information as "control command - port 44005 (high priority port pool 44005-44010), status reporting - port 44015 (medium priority port pool 44011-44020)" to ensure accurate binding of services to ports.

[0073] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0074] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0075] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0076] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or 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 to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0077] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0078] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0079] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A service quality assurance system, characterized in that, include: The Internet of Things (IoT) terminal is used to identify the type of service it is running and receive configuration instructions, and configure the service source port for different service flows according to the configuration instructions; A terminal management platform is configured to control the IoT terminal and acquire its terminal information to generate service flow information. The service flow information includes IMEI information, source IP address, service source port, service type, and requirement parameters. The IMEI information is bound one-to-one with the source IP address, and the service source port is bound to a combination of the IMEI information and the source IP address, as well as to the service type and the requirement parameters. The terminal management platform is also configured to generate configuration instructions based on the service flow information and send these instructions to the IoT terminal. An enhanced AF layer is used to obtain the service flow information from the terminal management platform and construct an enhanced request based on the service flow information. The 5G core network layer is used to obtain the enhancement request and generate and execute service policies based on the enhancement request.

2. The service quality assurance system as described in claim 1, characterized in that, The 5G core network layer also includes PCF, SMF, and UPF; The PCF is used to obtain the enhancement request and generate the service policy according to the requirement parameters in the enhancement request, and send the service policy to the SMF. The SMF is used to forward the service policy to the UPF, and the UPF is used to execute the service policy.

3. The service quality assurance system as described in claim 2, characterized in that, The PCF is also used to parse the enhancement request to obtain IMEI information, and associate the IMEI information with the session ID to generate a policy log.

4. The service quality assurance system as described in claim 2, characterized in that, The 5G core network layer includes a UDM, which is used to store the permanent subscription data of the IoT terminal.

5. A service quality assurance method, characterized in that, The method for controlling the service quality assurance system as described in any one of claims 1-4 includes: The enhanced AF layer obtains the service flow information from the terminal management platform, constructs the enhancement request based on the service flow information, and then sends the enhancement request to the 5G core network layer. The service flow information includes IMEI information, source IP address, service source port, service type, and requirement parameters. The IMEI information is bound one-to-one with the source IP address, and the service source port is bound to a combination of the IMEI information and the source IP address, as well as to the service type and the requirement parameters. The terminal management platform is also used to generate configuration instructions based on the service flow information and send the configuration instructions to the IoT terminal. The 5G core network layer obtains the enhancement request and generates the service policy based on the enhancement request to ensure service quality.

6. The method as described in claim 5, characterized in that, Constructing the enhanced request based on the service flow information includes: The enhanced AF layer obtains the service source port, the IMEI information, the source IP address, and the service type from the service flow information; The enhanced AF layer obtains the preset mapping rules and constructs the enhanced request based on the service source port, the IMEI information, the source IP address, and the service type.

7. The method as described in claim 5, characterized in that, The step of generating the service policy based on the enhanced request includes: The 5G core network layer parses the enhancement request to obtain the requirement parameters, wherein one service source port corresponds to one requirement parameter; The 5G core network layer generates service rules that match the demand parameters based on the demand parameters, wherein one service rule corresponds to one service source port; The 5G core network layer generates the service policy based on multiple service rules.

8. The method as described in claim 7, characterized in that, The 5G core network layer generates service rules that match the demand parameters based on the demand parameters, including: The 5G core network layer parses the required parameters to obtain standard values ​​and guaranteed bit rates; The 5G core network layer generates the service rules based on the source IP address of the IoT terminal, the standard value, and the guaranteed bit rate.

9. The method as described in claim 5, characterized in that, The method further includes: The 5G core network layer periodically collects real-time metrics for each of the service source ports. The terminal management platform acquires the real-time indicators and determines whether the IoT terminal exhibits abnormal behavior based on the real-time indicators. When the IoT terminal exhibits abnormal behavior, the terminal management platform updates the enhancement request.

10. The method as described in claim 5, characterized in that, The method further includes: The IoT terminal sends registration information to the terminal management platform, wherein the registration information includes the terminal information; The terminal management platform verifies the identity of the IoT terminal and configures the port configuration information for the IoT terminal after the verification is successful.

Images