Charging method and device, equipment, storage medium and product
By generating service policy information containing normalized billing indication identifiers, the billing discrepancy between static predefined rules and dynamic rules is resolved, billing consistency is achieved, and the billing rule management of NWDAF network elements is simplified.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-31
- Publication Date
- 2026-04-03
AI Technical Summary
In modern communication networks, due to the inconsistency between static predefined rule technology and dynamic guarantee technology for poor quality of key services, there are billing differences between the static predefined rules before the start of quality guarantee and the dynamic rules after the start of quality guarantee, making it difficult to achieve billing consistency.
By generating business policy information, including a normalized billing indicator, traffic billing is uniformly performed according to the billing rules in the static predefined rules. The normalized billing indicator is also configured in the NWDAF network element to offload the billing rule management function that it should not bear, thus ensuring billing consistency.
It achieves uniformity in billing rules during the quality assurance process, resolves the billing differences between static predefined rules and dynamic rules, and simplifies the billing strategy management of NWDAF network elements.
Smart Images
Figure CN121792964A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of service billing technology for modern communication networks, and in particular to a billing method, apparatus, device, storage medium and product. Background Technology
[0002] In modern communication networks (such as 5G networks), static predefined rules are typically used for guaranteeing and billing specific services. With the introduction of "dynamic guarantee for poor quality in key services," after the predefined rule matching process is completed, service quality is assessed. If the service quality fails to meet standards, quality guarantee is activated and the corresponding billing method is applied. However, due to the inconsistency in service identification technologies between static predefined rules and dynamic guarantee for poor quality in key services, billing discrepancies can arise between the static predefined rules before quality guarantee activation and the dynamic rules after activation, making it difficult to achieve billing consistency. Summary of the Invention
[0003] This application provides a billing method, apparatus, device, storage medium, and product that can solve the technical problem that the inconsistency between static predefined rule technology and key business quality poor dynamic protection technology leads to billing differences between static predefined rules before quality poor protection is initiated and dynamic rules after quality poor protection is initiated, making it difficult to achieve billing consistency.
[0004] In view of the above, firstly, embodiments of this application provide a billing method applied to a first network element, the method comprising: Receive service quality poor request information from the second network element; Based on the poor service quality request information, service policy information is generated. The service policy information includes a normalized billing instruction identifier, which is used to instruct that traffic billing be uniformly performed according to the billing rules in the static predefined rules. Based on the aforementioned business strategy information, a request for quality assurance is made to the third network element.
[0005] Optionally, the first network element is an NWDAF network element, and the second network element is a UPF network element; The poor service quality request information includes: poor service application category and service flow description information.
[0006] Optionally, the first network element is a NEF network element, and the second network element is an AF network element; The service quality poor request information is information that provides quality assurance for a specified service request.
[0007] Optionally, the poor service quality request information includes the service flow description information and QoS parameters specified by the AF network element.
[0008] Optionally, the service policy information may further include: service flow description information and QoS parameters.
[0009] Secondly, this application also provides a billing method applied to a second network element, the method comprising: The system receives dynamic rules for quality assurance execution issued by the fourth network element. These dynamic rules include a normalized billing indicator, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. Based on the aforementioned quality assurance, dynamic rules are executed to implement service quality assurance, and based on the indication of the normalized billing indication identifier, traffic billing is performed according to the billing rules in the static predefined rules.
[0010] Optionally, the quality defect assurance execution dynamic rules also include: PDR and QER; Service quality assurance is implemented based on the PDR and QER.
[0011] Optionally, the second network element is a UPF network element, and the fourth network element is an SMF network element.
[0012] Optionally, before receiving the quality deviation guarantee execution dynamic rules issued by the fourth network element, the method further includes: The service is detected by the service identification feature library, and when the service quality is substandard, a service quality poor request information is reported to the first network element; The normalized billing indication identifier is issued by the first network element based on the received service quality poor request information.
[0013] Optionally, the first network element is an NWDAF network element.
[0014] Optionally, after the flow billing is performed according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier, it further includes: The normalized billing rules have been successfully installed in response to the fourth network element.
[0015] Thirdly, embodiments of this application also provide a billing method, including: For the established services of UEs registered with the core network, static predefined rules are used for traffic billing. The second network element sends a poor service quality request message to the first network element; The first network element generates service policy information based on the poor service quality request information and outputs it to the PCF network element. The service policy information includes a normalized billing instruction identifier. The PCF network element generates a quality assurance PCC dynamic rule based on the service policy information and sends it to the SMF network element. The quality assurance PCC dynamic rule includes the normalized billing indication identifier. The SMF network element converts the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element. The dynamic rules for quality assurance execution include the normalized billing indication identifier. The UPF network element implements service quality assurance based on the quality assurance execution dynamic rules, and performs traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier in the quality assurance execution dynamic rules.
[0016] Optionally, the first network element is an NWDAF network element, and the second network element is the UPF network element; The second network element sends a service quality poor request message to the first network element, including: The UPF network element detects services through the service identification feature library and reports the poor service quality request information to the NWDAF network element when the service quality is substandard.
[0017] Optionally, the poor service quality request information includes: poor service application category and service flow description information.
[0018] Optionally, the first network element is a NEF network element, and the second network element is an AF network element; The second network element sends a service quality poor request message to the first network element, including: The AF network element sends the poor service quality request information to the NEF network element for the specified service.
[0019] Optionally, the poor service quality request information includes the service flow description information and QoS parameters specified by the AF network element.
[0020] Optionally, the business strategy information further includes: business flow description information and QoS parameters; The quality assurance PCC dynamic rule also includes: the service flow description information and the QoS parameters; The dynamic rules for quality assurance also include PDR and QER, and the UPF network element implements service quality assurance based on the PDR and QER.
[0021] Optionally, after the UPF network element implements service quality assurance based on the quality assurance execution dynamic rules, and performs traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier in the quality assurance execution dynamic rules, it further includes: The UPF network element responds to the SMF network element that the normalized charging rules have been successfully installed; The SMF network element responds to the PCF network element that the quality difference guarantee PCC dynamic rule has been successfully executed. The PCF network element responded to the first network element that the quality guarantee was successfully executed.
[0022] Fourthly, embodiments of this application also provide a billing device applied to a first network element, the device comprising: The receiving module is used to receive service quality poor request information from the second network element; The generation module is used to generate business strategy information based on the poor service quality request information. The business strategy information includes a normalized billing indication identifier, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. The request module is used to request quality assurance from the third network element based on the business strategy information.
[0023] Fifthly, embodiments of this application also provide a billing device applied to a second network element, the device comprising: The receiving module is used to receive the quality guarantee execution dynamic rules issued by the fourth network element. The quality guarantee execution dynamic rules include: a normalized billing indication flag, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. The execution module is used to implement service quality assurance based on the quality assurance execution dynamic rules, and to perform traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier.
[0024] Sixthly, embodiments of this application also provide a computer device, including a memory and a processor; The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to invoke the computer programs so that the computer device executes the billing method described in either the first or second aspect.
[0025] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program adapted to be loaded by a processor and execute the billing method described in any one of the first or second aspects.
[0026] Eighthly, embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in either the first or second aspect.
[0027] The aforementioned billing methods, devices, computer equipment, computer-readable storage media, and computer program products can perform traffic billing based on the normalized billing instruction identifier and the billing rules in the static predefined rules for services that have initiated quality assurance. This solves the technical problem that the inconsistency between the static predefined rules before quality assurance is initiated and the dynamic rules after quality assurance is initiated due to the inconsistency between the static predefined rules technology and the key business quality assurance dynamic guarantee technology leads to billing differences and makes it difficult to achieve billing consistency. Attached Figure Description
[0028] Figure 1 This is a schematic diagram of the system architecture provided in the embodiments of this application.
[0029] Figure 2 This is one of the flowcharts illustrating the billing method provided in the embodiments of this application.
[0030] Figure 3 This is a second schematic flowchart of the billing method provided in the embodiments of this application.
[0031] Figure 4 This is one of the schematic diagrams illustrating the interaction process of the billing method provided in the embodiments of this application.
[0032] Figure 5 This is a second schematic diagram illustrating the interaction process of the billing method provided in this application embodiment.
[0033] Figure 6 This is one of the schematic diagrams of a billing device provided in an embodiment of this application.
[0034] Figure 7 This is a second schematic diagram of a billing device provided in an embodiment of this application.
[0035] Figure 8 A schematic diagram of a computer device provided in an embodiment of this application. Detailed Implementation
[0036] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all 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.
[0037] Typically, for specific services, protection and billing can be achieved using static predefined rules. This involves statically configuring predefined rules for specific services on the SMF network element, along with the corresponding billing URR (including URRID and associated billing rate group RG); simultaneously, statically configuring predefined rules (with names consistent with those on the SMF network element) on the UPF network element, along with the service flow description information (e.g., IP and / or URL) and the billing URR (including only the URR ID, consistent with the URR ID configured on the SMF network element).
[0038] When a user activates and creates a PDU session, the SMF network element requests the UPF network element to activate its predefined rules. The UPF network element then identifies and matches the user's services based on the service flow description information in its predefined rules. For matched traffic, the UPF network element accumulates the URR ID in the predefined rule and reports it to the SMF network element. The SMF network element then uses the billing rate group RG corresponding to the URR ID for billing and statistics of this reported traffic.
[0039] With the introduction of the "Dynamic Assurance for Poor Quality of Key Services" technology, a service identification feature library is introduced into the user plane for service identification. For successfully identified services, their service flow description information is extracted, and then a specific guaranteed QoS and billing rate group (RG) is assigned to this service flow.
[0040] Within the UPF network element, user services first undergo a predefined rule matching process. The user service is identified using the service flow description information (such as IP and / or URL) configured in the static predefined rules. Once the identification is successful, traffic billing is implemented based on the billing rate group RG configured according to the predefined rules.
[0041] After completing the predefined rule matching process, the service quality is judged. At this time, the UPF network element uses the service identification feature library to detect the service and starts QoS guarantee when the service quality is not up to standard. The UPF network element reports poor quality information (including poor quality application category, application type, and service flow description information) to the NWDAF network element. The NWDAF network element generates a charging rate group (RG) and QoS parameters based on the application type, and then assembles the service flow description information, charging rate group (RG), and QoS parameters reported by the UPF network element and sends them to the PCF network element through the N5 session. The PCF network element generates PCC dynamic rules from the information received in the N5 session and sends them to the SMF network element (this PCC dynamic rule includes service flow description information, QoS parameters, and charging rate group (RG)). The SMF network element generates PDR (based on service flow description information), QER (based on QoS parameters), and URR (based on charging rate group (RG)) according to the PCC dynamic rules and sends them to the UPF network element through the N4 session. Based on the principle that dynamic rules have higher priority than static rules, the UPF network element then implements QoS and traffic billing for the service flow corresponding to the received PDR.
[0042] Compared with static predefined rules and dynamic quality assurance technology for key business operations, the following technical problems exist: 1. Inconsistent business identification technologies lead to inconsistencies in business-based billing: For static predefined rule technology, the identification of services depends on pre-configured service flow description information (such as the service's IP and / or URL). The completeness and timeliness of the service flow description information configuration directly determine the accuracy of application service identification.
[0043] For the dynamic assurance technology for poor quality of key services, the identification of services depends on the service identification feature library capabilities of the user plane. The accuracy and update frequency of the service identification feature library determine the identification accuracy of application services.
[0044] Because the accuracy of business recognition rate directly affects the traffic billing statistics bound to the business (even if the same billing rate group RG is used), inconsistency in recognition accuracy will lead to billing differences between the static predefined rules before the quality guarantee is launched and the dynamic rules after the quality guarantee is launched, making it difficult to achieve billing consistency.
[0045] 2. In the dynamic guarantee technology for poor quality of key services, the current method of managing complex billing rules is to use the local configuration of NWDAF network elements. From the perspective of the definition of network element functional entities, this billing rule management function should not be undertaken by the NWDAF network element. It is necessary to unload this function from the NWDAF network element.
[0046] To address these issues, this application provides a billing method, billing device, computer equipment, computer-readable storage medium, and computer program product. The embodiments of this application will now be described in detail with reference to the accompanying drawings.
[0047] First, the relevant terms appearing in this application will be explained as follows (hereafter referred to only by English abbreviations):
[0048] Figure 1 The system architectures involved in the examples of this application are given below, along with the meanings of the relevant components and their roles in the specific examples of this application: UE: Terminal Equipment.
[0049] NG-RAN: Wireless Access Equipment.
[0050] AMF network element: Access and mobility management function equipment.
[0051] SMF network element: responsible for processing quality assurance dynamic PCC rules from PCF network element, including the management of service description information and billing rate group RG, and guiding UPF to implement corresponding flow identification and billing traffic statistics.
[0052] PCF network element: Receives service policies from the N5 interface, generates and sends quality assurance dynamic PCC rules (including service flow description information, QoS and normalized charging indication, etc.) to the SMF network element.
[0053] UPF network element: responsible for reporting service quality request information (including poor quality application category, application type and service flow description information) to NWDAF network element, and implementing service traffic statistics, billing reporting and QoS based on PDR, URR and QER issued by SMF network element.
[0054] NWDAF network element: Generates QoS parameters based on the application type reported by the UPF network element, and assembles the service flow description information, QoS parameters and normalized charging indication identifier reported by the UPF network element and sends them to the PCF network element through the N5 session.
[0055] NEF / AF: Applicable to capability open scenarios. In this case, the service flow description information and QoS parameters involved in the quality assurance request are specified by AF. AF requests the corresponding service quality assurance from 5GC by calling the northbound API service of NEF.
[0056] DN: Data Network Device, responsible for providing data access to users.
[0057] It should be noted that the embodiments of this application are not limited to the above system structure.
[0058] Figure 2 This is one of the flowcharts illustrating the billing method provided in this application. See also... Figure 2 This application provides a billing method applied to a first network element, comprising: 101, Receive service quality poor request information from the second network element.
[0059] Before step 101, traffic billing is performed on the established services of UEs registered to the core network using static predefined rules.
[0060] Specifically, within the UPF network element, user services first undergo a static predefined rule matching process. The user services are identified using the service flow description information (such as IP and / or URL) configured in the static predefined rules. Once the identification is successful, traffic billing is implemented based on the billing rate group RG configured in the static predefined rules.
[0061] In some embodiments, the first network element is an NWDAF network element and the second network element is a UPF network element.
[0062] In some embodiments, the service quality poor request information includes: poor quality application category and service flow description information. The poor quality application category is the application category to which the service with poor quality belongs. Specifically, the poor quality application category may include application category and application type.
[0063] It should be noted that while "service flow description information" is mentioned multiple times in this application, its expression across different network elements can be adapted according to protocol specifications or policy requirements. For example, the service flow description information reported by the UPF network element can be a specific five-tuple obtained based on deep packet inspection, while the service flow description information generated by the NWDAF network element or PCF network element can be a generalized or standardized flow matching rule. As long as it can be effectively associated with the same type of low-quality service flow, it belongs to the service flow description information of this application.
[0064] UPF network elements detect services through the service identification feature library and report poor service quality request information to NWDAF network elements when the service quality is substandard.
[0065] Specifically, after completing the static predefined rule matching process, a service quality defect judgment is performed. When the UPF network element detects a service through the service identification feature library and the service quality is substandard, it reports a service quality defect request to the NWDAF network element.
[0066] In some embodiments, the first network element is a NEF network element, and the second network element is an AF network element; the service quality deterioration request information is information for providing quality deterioration assurance for a specified service request. Specifically, when the AF network element expects to implement quality deterioration assurance for a specified service, it calls the northbound API service of the NEF network element to request quality deterioration assurance for the specified service from the 5GC. After receiving the northbound call from the AF network element, the NEF network element generates service policy information for the N5 session based on its local configuration.
[0067] Specifically, the poor service quality request information includes QoS parameters specified by the AF network element and service flow description information.
[0068] 102. Generate business strategy information based on poor service quality request information. The business strategy information includes a normalized billing indicator, which is used to instruct that traffic billing be uniformly performed according to the billing rules in the static predefined rules.
[0069] In some embodiments, the service policy information further includes: service flow description information and QoS parameters.
[0070] In one example, the NWDAF network element generates service policy information based on the poor service quality request information reported by the UPF network element. Specifically, the QoS parameters are generated for the first time by the NWDAF network element.
[0071] In one example, the NEF network element generates service policy information based on the poor service quality request information sent by the AF network element. Specifically, the QoS parameters are derived from the specifications of the AF network element.
[0072] 103. Based on business strategy information, request quality assurance from the third network element.
[0073] In some embodiments, service policy information is sent based on the N5 session.
[0074] In different examples, the NWDAF network element and the NEF network element respectively generate service policy information for the N5 session.
[0075] Specifically, a quality guarantee is requested from the third network element via the Npcf_PolicyAuthorization_Notify request message.
[0076] In some embodiments, the third network element is a PCF network element.
[0077] In some embodiments, after receiving service policy information, the PCF network element generates a quality assurance PCC dynamic rule based on the service policy information and sends it to the SMF network element. The quality assurance PCC dynamic rule includes a normalized billing indication identifier. The SMF network element converts the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element. The dynamic rules for quality assurance execution include a normalized billing indicator. UPF network elements implement service quality assurance based on dynamic rules and perform traffic billing according to the billing rules in static predefined rules, based on the normalized billing indication identifier in the dynamic rules for quality assurance.
[0078] In this embodiment, service policy information is generated based on the service quality poor request information. The service policy information includes a normalized billing indicator, which instructs that traffic billing be uniformly performed according to the billing rules in the static predefined rules. Therefore, when requesting quality assurance based on service policy information, traffic billing can be performed according to the billing rules in the static predefined rules based on the instruction of the normalized billing indicator. This solves the technical problem that inconsistencies in service identification technology between static predefined rules before quality assurance is initiated and dynamic rules after quality assurance is initiated can lead to billing differences, making it difficult to achieve billing consistency. Furthermore, when the first network element is an NWDAF network element, configuring a normalized billing indicator on the NWDAF network element offloads the billing rule management function that should not be borne by the NWDAF network element, simplifying its billing policy management.
[0079] Figure 3 This is a second schematic flowchart illustrating the billing method provided in an embodiment of this application. (See also...) Figure 3 This application provides a billing method applied to a second network element, comprising: 201. Receive the dynamic rules for quality assurance execution issued by the fourth network element. The dynamic rules for quality assurance execution include: normalized billing indicator. The normalized billing indicator is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules.
[0080] In some embodiments, the second network element is a UPF network element and the fourth network element is an SMF network element.
[0081] In some embodiments, before receiving the quality assurance execution dynamic rules issued by the fourth network element, the method further includes: The service is detected by the service identification feature library, and when the service quality is substandard, a service quality poor request information is reported to the first network element; The normalized billing indication is issued by the first network element based on the received service quality poor request information.
[0082] Before detecting services through the service identification feature library, traffic billing is performed on the established services of UEs registered with the core network using static predefined rules.
[0083] Specifically, within the UPF network element, user services first undergo a static predefined rule matching process. The user services are identified using the service flow description information (such as IP and / or URL) configured in the static predefined rules. Once the identification is successful, traffic billing is implemented based on the billing rate group RG configured in the static predefined rules.
[0084] Specifically, the first network element is the NWDAF network element.
[0085] Please combine Figure 4 In a specific example, the NWDAF network element generates service policy information based on the service quality poor request information reported by the UPF network element and sends it to the PCF network element. The service policy information includes a normalized billing instruction identifier. After receiving the service policy information, the PCF network element generates a quality guarantee PCC dynamic rule based on the service policy information and sends it to the SMF network element. The quality guarantee PCC dynamic rule includes a normalized billing indicator. The SMF network element converts the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element. The dynamic rules for quality assurance execution include normalized billing indication identifiers.
[0086] Please combine Figure 5 In some embodiments, before receiving the quality assurance execution dynamic rules issued by the fourth network element, when the AF network element expects to implement quality assurance for a specified service, it calls the northbound API service of the NEF network element to request quality assurance for the specified service from the core network. After receiving the northbound call from the AF network element, the NEF network element generates service policy information based on its local configuration and sends it to the PCF network element; After receiving the service policy information, the PCF network element generates a quality guarantee PCC dynamic rule based on the service policy information and sends it to the SMF network element, which is the fourth network element. The quality guarantee PCC dynamic rule includes a normalized billing indicator. The SMF network element transforms the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element, which is the second network element. The dynamic rules for quality assurance execution include a normalized billing indicator.
[0087] In some embodiments, the quality assurance execution dynamic rules also include: PDR and QER.
[0088] Specifically, the business policy information also includes business flow description information (Flows) and QoS parameters (qosReference). The quality assurance PCC dynamic rules also include business flow description information (flowinfos) and QoS parameters (qosDecs).
[0089] Specifically, the dynamic rules for ensuring poor quality are issued to UPF network elements based on the N4 session.
[0090] 202, Implement business quality quality assurance based on dynamic rules, and perform traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier.
[0091] In some embodiments, service quality assurance is implemented based on PDR and QER.
[0092] Please combine Figure 4 and Figure 5 In some embodiments, after the traffic is billed according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier, the method further includes: The normalized billing rules for the fourth network element have been successfully installed.
[0093] Specifically, in the N4 session update response message, the UPF network element responds to the SMF network element that the normalized billing rules have been successfully installed.
[0094] Specifically, after the UPF network element responds to the SMF network element that the normalized charging rules have been successfully installed, it also includes: Poor response quality from SMF network elements to PCF network elements ensures successful execution of PCC dynamic rules. The PCF network element responded to the first network element, indicating that the poor quality guarantee was successfully executed.
[0095] In this embodiment, the dynamic rules for quality assurance received by the second network element include a normalized billing indication identifier. Therefore, when the second network element implements service quality assurance based on these dynamic rules, it will perform traffic billing according to the billing rules in the static predefined rules, based on the indication of the normalized billing indication identifier. This solves the technical problem that inconsistencies in service identification technologies, such as those for static predefined rules and dynamic quality assurance for key services, lead to billing differences between the static predefined rules before quality assurance activation and the dynamic rules after quality assurance activation, making it difficult to achieve billing consistency.
[0096] Figure 4 and Figure 5 These are schematic diagrams illustrating the interaction process of the billing methods in two examples of this application. (See attached diagram.) Figure 4 and Figure 5 This application provides a billing method, which includes: 301. Static predefined rules are used for traffic billing of the established services of UEs registered to the core network.
[0097] Specifically, the UE accesses the core network via NG-RAN and completes registration via AMF.
[0098] In some embodiments, static predefined rules include service flow description information and billing URR.
[0099] In some embodiments, user services first undergo a static predefined rule matching process within the UPF network element. The user service is identified by the service flow description information (e.g., IP and / or URL) configured in the static predefined rules. If the identification is successful, traffic billing is implemented according to the billing rate group RG configured in the static predefined rules.
[0100] Specifically, the SMF network element is configured with static predefined rules for specific services, and the corresponding billing URR (including URR ID and associated billing rate group RG) is configured for the rule; at the same time, the UPF network element is configured with static predefined rules (with the same name as the static predefined rules of the SMF network element), and the service flow description information (such as IP and / or URL) and billing URR (including only URR ID, and consistent with the URR ID of the URR configured in the SMF network element) are configured for the rule.
[0101] When a user activates and creates a PDU session, the SMF network element requests the UPF network element to activate the corresponding static predefined rule. The UPF network element then identifies and matches the user's service based on the service flow description information in the static predefined rule. For matched traffic, the URF ID is accumulated in the static predefined rule and reported to the SMF network element. The SMF network element then uses the billing rate group RG corresponding to the URF ID for this reported traffic and performs billing statistics.
[0102] 302, the second network element sends a service quality poor request message to the first network element.
[0103] Please combine Figure 4 In some embodiments, the first network element is an NWDAF network element and the second network element is a UPF network element.
[0104] The second network element sends a service quality poor request message to the first network element, including: UPF network elements detect services through the service identification feature library and report poor service quality request information to NWDAF network elements when the service quality is substandard.
[0105] Specifically, the poor service quality request information includes: poor service quality application category and service flow description information. The poor service quality application category is the application category to which the service with poor quality belongs. Specifically, the poor service quality application category can include application category and application type.
[0106] Please combine Figure 5In some embodiments, the first network element is a NEF network element and the second network element is an AF network element; the AF network element sends a service quality defect request information to the NEF network element for a specified service. The service quality defect request information is information for quality defect protection for a specified service request, which may specifically include specified service flow description information and QoS parameters.
[0107] Specifically, when an AF network element expects to implement quality assurance for a specified service, it calls the northbound API service of the NEF network element to request quality assurance for the specified service from the 5GC.
[0108] 303. The first network element generates service policy information based on the poor service quality request information and outputs it to the PCF network element. The service policy information includes a normalized billing instruction identifier.
[0109] In some embodiments, the service policy information includes not only the normalized billing indication identifier, but also information elements such as service flow description information (Flows) and QoS parameters (qosReference).
[0110] In some embodiments, service policy information is sent based on the N5 session.
[0111] In different examples, the NWDAF network element generates service policy information for the N5 session based on the poor service quality request information. The NEF network element generates service policy information for the N5 session based on local configuration (specifically, the specified service flow description information and QoS parameters).
[0112] Specifically, the first network element requests quality assurance from the PCF network element via the Npcf_PolicyAuthorization_Notify request message. In different examples, the first network element can be an NWDAF network element or a NEF network element.
[0113] 304. The PCF network element generates a quality assurance PCC dynamic rule based on the service policy information and sends it to the SMF network element. The quality assurance PCC dynamic rule includes a normalized billing indicator.
[0114] In some embodiments, the PCC dynamic rules for quality assurance include, in addition to the normalized billing indication identifier, the service flow description information (flowinfos) to be guaranteed and the QoS parameters (qosDecs) to be guaranteed.
[0115] Specifically, the quality difference guarantee PCC dynamic rules are carried in the Npcf_SMPolicyControl_UpdateNotify request message.
[0116] 305. The SMF network element converts the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element. The dynamic rules for quality assurance execution include a normalized billing indicator.
[0117] In some embodiments, the dynamic rules for implementing quality assurance include, in addition to the normalized billing indication identifier, PDR and QER.
[0118] Specifically, after the SMF network element parses the quality-per-class guarantee dynamic PCC rules issued by the PCF network element, it converts the service flow description information, QoS parameters and normalized charging indicator in this PCC rule into the PDR, QER and normalized charging indicator of the N4 session, and sends them to the UPF network element through the PFCP Session Modification request message.
[0119] 306. The UPF network element implements service quality assurance based on the dynamic rules of the quality assurance execution, and performs traffic billing according to the billing rules in the static predefined rules based on the normalized billing indication identifier in the dynamic rules of the quality assurance execution.
[0120] In some embodiments, the UPF network element implements service quality assurance based on PDR and QER.
[0121] In some embodiments, after the UPF network element implements service quality assurance based on dynamic rules for quality assurance, and performs traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier in the dynamic rules for quality assurance, the system further includes: 307. The UPF network element responded to the SMF network element that the normalized billing rules have been successfully installed.
[0122] Specifically, the N4 session update response message enables the UPF network element to respond to the SMF network element that the normalized billing rules have been successfully installed.
[0123] 308. Poor response quality from SMF network element to PCF network element ensures successful execution of PCC dynamic rules.
[0124] Specifically, the SMF network element responds to the PCF network element via the Npcf_SMPolicyControl_UpdateNotify response, indicating that the quality assurance rule has been successfully executed.
[0125] 309. The PCF network element successfully responded to the first network element, indicating that the poor quality guarantee was successfully implemented.
[0126] In different examples, the first network element can be an NWDAF network element or a NEF network element.
[0127] In this embodiment, the service policy information generated by the first network element based on the service quality poor request information includes a normalized billing indicator. This ensures that the dynamic rules for quality poor protection execution ultimately sent to the UPF network element include the normalized billing indicator, allowing the UPF network element to perform traffic billing according to the billing rules in the static predefined rules based on the normalized billing indicator. This solves the technical problem of billing discrepancies between the static predefined rules before quality poor protection is initiated and the dynamic rules after quality poor protection is initiated, due to inconsistencies in service identification technologies between static predefined rules and key service quality poor dynamic protection. Furthermore, when the first network element is an NWDAF network element, configuring a normalized billing indicator on the NWDAF network element offloads the billing rule management function that should not be handled by the NWDAF network element, simplifying its billing policy management.
[0128] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0129] Based on the same inventive concept, embodiments of this application also provide a billing apparatus for implementing some of the billing methods described above. The solution provided by the billing apparatus is similar to the solution described in the corresponding methods above; therefore, some specific limitations / descriptions in the billing apparatus embodiments provided below can be found in the limitations / descriptions of the billing methods above, and will not be repeated here.
[0130] Figure 6 This is one of the schematic diagrams of a billing device provided in an embodiment of this application. See also... Figure 6 This application provides a billing device applied to a first network element, comprising: The receiving module 401 is used to receive service quality poor request information from the second network element.
[0131] In some embodiments, the first network element is an NWDAF network element and the second network element is a UPF network element.
[0132] In some embodiments, the service quality poor request information includes: poor quality application category and service flow description information. The poor quality application category is the application category to which the service with poor quality belongs. Specifically, the poor quality application category may include application category and application type.
[0133] UPF network elements detect services through the service identification feature library and report poor service quality request information to NWDAF network elements when the service quality is substandard.
[0134] Specifically, after completing the static predefined rule matching process, the service quality is judged. The UPF network element detects the service through the service identification feature library and reports the service quality poor request information to the NWDAF network element when the service quality does not meet the standard.
[0135] In some embodiments, the first network element is a NEF network element, and the second network element is an AF network element; the service quality deterioration request information is information for providing quality deterioration assurance for a specified service request. Specifically, when the AF network element expects to implement quality deterioration assurance for a specified service, it calls the northbound API service of the NEF network element to request quality deterioration assurance for the specified service from the 5GC. After receiving the northbound call from the AF network element, the NEF network element generates service policy information for the N5 session based on its local configuration.
[0136] Specifically, the poor service quality request information includes QoS parameters specified by the AF network element and service flow description information.
[0137] The generation module 402 is used to generate business strategy information based on the poor service quality request information. The business strategy information includes a normalized billing indicator, which is used to instruct that traffic billing be performed uniformly according to the billing rules in the static predefined rules.
[0138] In some embodiments, the service policy information further includes: service flow description information and QoS parameters.
[0139] In one example, the NWDAF network element generates service policy information based on the poor service quality request information reported by the UPF network element.
[0140] In one example, the NEF network element generates service policy information based on the poor service quality request information sent by the AF network element.
[0141] Request module 403 is used to request quality assurance from a third network element based on business strategy information.
[0142] In some embodiments, service policy information is sent based on the N5 session.
[0143] In different examples, the NWDAF network element and the NEF network element respectively generate service policy information for the N5 session.
[0144] Specifically, a quality guarantee is requested from the third network element via the Npcf_PolicyAuthorization_Notify request message.
[0145] In some embodiments, the third network element is a PCF network element.
[0146] In this embodiment, service policy information is generated based on the service quality poor request information. The service policy information includes a normalized billing indicator, which instructs that traffic billing be uniformly performed according to the billing rules in the static predefined rules. Therefore, when requesting quality assurance based on service policy information, traffic billing can be performed according to the billing rules in the static predefined rules based on the instruction of the normalized billing indicator. This solves the technical problem that inconsistencies in service identification technology between static predefined rules before quality assurance is initiated and dynamic rules after quality assurance is initiated can lead to billing differences, making it difficult to achieve billing consistency. Furthermore, when the first network element is an NWDAF network element, configuring a normalized billing indicator on the NWDAF network element offloads the billing rule management function that should not be borne by the NWDAF network element, simplifying its billing policy management.
[0147] Figure 7 This application provides a second schematic diagram of a billing device according to an embodiment. (See also...) Figure 7 This application provides a billing device applied to a second network element, comprising: The receiving module 501 is used to receive the quality guarantee execution dynamic rules issued by the fourth network element. The quality guarantee execution dynamic rules include: normalized billing indicator, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules.
[0148] In some embodiments, the second network element is a UPF network element and the fourth network element is an SMF network element.
[0149] In some embodiments, before receiving the quality assurance execution dynamic rules issued by the fourth network element, the method further includes: The service is detected by the service identification feature library, and when the service quality is substandard, a service quality poor request information is reported to the first network element; The normalized billing indication is issued by the first network element based on the received service quality poor request information. Ultimately, the second network element will receive the normalized billing indication.
[0150] Before detecting services through the service identification feature library, traffic billing is performed on the established services of UEs registered with the core network using static predefined rules.
[0151] Specifically, the first network element is the NWDAF network element.
[0152] Please combine Figure 5 In some embodiments, before receiving the quality assurance execution dynamic rules issued by the fourth network element, when the AF network element expects to implement quality assurance for a specified service, it calls the northbound API service of the NEF network element to request quality assurance for the specified service from the core network. After receiving the northbound call from the AF network element, the NEF network element generates service policy information based on its local configuration and issues it. Finally, the second network element will receive the normalized billing indication identifier from it.
[0153] In some embodiments, the quality assurance execution dynamic rules also include: PDR and QER.
[0154] Specifically, the dynamic rules for ensuring poor quality are issued to UPF network elements based on the N4 session.
[0155] The execution module 502 is used to implement business quality assurance based on dynamic rules for quality assurance, and to perform traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier.
[0156] In some embodiments, service quality assurance is implemented based on PDR and QER.
[0157] In this embodiment, the dynamic rules for quality assurance received by the second network element include a normalized billing indication identifier. Therefore, when the second network element implements service quality assurance based on these dynamic rules, it will perform traffic billing according to the billing rules in the static predefined rules, based on the indication of the normalized billing indication identifier. This solves the technical problem that inconsistencies in service identification technologies, such as those for static predefined rules and dynamic quality assurance for key services, lead to billing differences between the static predefined rules before quality assurance activation and the dynamic rules after quality assurance activation, making it difficult to achieve billing consistency.
[0158] In this application embodiment, the term "module" refers to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.
[0159] Figure 8 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 8As shown, the computer device may include a processor 601 and a memory 602. The memory 602 is connected to the processor 601 and is used to store computer programs. The processor 601 calls the computer programs to cause the computer device to execute the billing method described in some of the above embodiments. Furthermore, the computer device may also include at least one communication bus 603. The communication bus 603 is used to enable communication between components. The memory 602 may be a high-speed RAM or non-volatile memory, such as at least one disk storage device.
[0160] This application also provides a computer-readable storage medium storing a computer program adapted to be loaded by a processor and execute the billing method described in the above-described embodiments.
[0161] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the billing method as described in some of the above embodiments.
[0162] It should be understood that, in the embodiments of this application, the processor may be a central processing unit (CPU), but it may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.
[0163] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by hardware related to computer program instructions. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.
[0164] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to” and are used interchangeably with them.
[0165] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0166] The above-disclosed examples are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall fall within the scope of this application.
Claims
1. A billing method, characterized in that, Applied to the first network element, the method includes: Receive service quality poor request information from the second network element; Based on the poor service quality request information, service policy information is generated. The service policy information includes a normalized billing instruction identifier, which is used to instruct that traffic billing be uniformly performed according to the billing rules in the static predefined rules. Based on the aforementioned business strategy information, a request for quality assurance is made to the third network element.
2. The billing method according to claim 1, characterized in that, The first network element is an NWDAF network element, and the second network element is a UPF network element; The poor service quality request information includes: poor service application category and service flow description information.
3. The billing method according to claim 1, characterized in that, The first network element is an NEF network element, and the second network element is an AF network element; The service quality poor request information is information that provides quality assurance for a specified service request.
4. The billing method according to claim 3, characterized in that, The poor service quality request information includes the service flow description information and QoS parameters specified by the AF network element.
5. The billing method according to claim 1, characterized in that, The service policy information also includes: service flow description information and QoS parameters.
6. A billing method, characterized in that, Applied to a second network element, the method includes: The system receives dynamic rules for quality assurance execution issued by the fourth network element. These dynamic rules include a normalized billing indicator, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. Based on the aforementioned quality assurance, dynamic rules are executed to implement service quality assurance, and based on the indication of the normalized billing indication identifier, traffic billing is performed according to the billing rules in the static predefined rules.
7. The billing method according to claim 6, characterized in that, The dynamic rules for implementing the quality assurance mechanism also include: PDR and QER; Service quality assurance is implemented based on the PDR and QER.
8. The billing method according to claim 7, characterized in that, The second network element is a UPF network element, and the fourth network element is an SMF network element.
9. The billing method according to claims 6 to 8, characterized in that, Before receiving the quality assurance execution dynamic rules issued by the fourth network element, the process also includes: The service is detected by the service identification feature library, and when the service quality is substandard, a service quality poor request information is reported to the first network element; The normalized billing indication identifier is issued by the first network element based on the received service quality poor request information.
10. The billing method according to claim 9, characterized in that, The first network element is the NWDAF network element.
11. The billing method according to claim 6, characterized in that, After the normalized billing indication identifier is used to bill traffic according to the billing rules in the static predefined rules, the method further includes: The normalized billing rules have been successfully installed in response to the fourth network element.
12. A billing method, characterized in that, The method includes: For the established services of UEs registered with the core network, static predefined rules are used for traffic billing. The second network element sends a poor service quality request message to the first network element; The first network element generates service policy information based on the poor service quality request information and outputs it to the PCF network element. The service policy information includes a normalized billing instruction identifier. The PCF network element generates a quality assurance PCC dynamic rule based on the service policy information and sends it to the SMF network element. The quality assurance PCC dynamic rule includes the normalized billing indication identifier. The SMF network element converts the information in the PCC dynamic rules for quality assurance, generates dynamic rules for quality assurance execution, and sends them to the UPF network element. The dynamic rules for quality assurance execution include the normalized billing indication identifier. The UPF network element implements service quality assurance based on the quality assurance execution dynamic rules, and performs traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier in the quality assurance execution dynamic rules.
13. The billing method according to claim 12, characterized in that, The first network element is an NWDAF network element, and the second network element is the UPF network element; The second network element sends a service quality poor request message to the first network element, including: The UPF network element detects services through the service identification feature library and reports the poor service quality request information to the NWDAF network element when the service quality is substandard.
14. The billing method according to claim 13, characterized in that, The poor service quality request information includes: poor service application category and service flow description information.
15. The billing method according to claim 12, characterized in that, The first network element is an NEF network element, and the second network element is an AF network element; The second network element sends a service quality poor request message to the first network element, including: The AF network element sends the poor service quality request information to the NEF network element for the specified service.
16. The billing method according to claim 15, characterized in that, The poor service quality request information includes the service flow description information and QoS parameters specified by the AF network element.
17. The billing method according to claim 12, characterized in that, The business strategy information also includes: business flow description information and QoS parameters; The quality assurance PCC dynamic rule also includes: the service flow description information and the QoS parameters; The dynamic rules for quality assurance also include PDR and QER, and the UPF network element implements service quality assurance based on the PDR and QER.
18. The billing method according to claim 12, characterized in that, After the UPF network element implements service quality assurance based on the quality assurance execution dynamic rules, and performs traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier in the quality assurance execution dynamic rules, it also includes: The UPF network element responds to the SMF network element that the normalized charging rules have been successfully installed; The SMF network element responds to the PCF network element that the quality difference guarantee PCC dynamic rule has been successfully executed. The PCF network element responded to the first network element that the quality guarantee was successfully executed.
19. A billing device, characterized in that, Applied to the first network element, the device includes: The receiving module is used to receive service quality poor request information from the second network element; The generation module is used to generate business strategy information based on the poor service quality request information. The business strategy information includes a normalized billing indication identifier, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. The request module is used to request quality assurance from the third network element based on the business strategy information.
20. A billing device, characterized in that, Applied to a second network element, the device includes: The receiving module is used to receive the quality guarantee execution dynamic rules issued by the fourth network element. The quality guarantee execution dynamic rules include: a normalized billing indication flag, which is used to indicate that traffic billing is uniformly performed according to the billing rules in the static predefined rules. The execution module is used to implement service quality assurance based on the quality assurance execution dynamic rules, and to perform traffic billing according to the billing rules in the static predefined rules based on the indication of the normalized billing indication identifier.
21. A computer device, characterized in that, Including memory and processor; The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to call the computer programs so that the computer device executes the billing method according to any one of claims 1 to 5, or executes the billing method according to any one of claims 6 to 11.
22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and execute the billing method according to any one of claims 1 to 5, or execute the billing method according to any one of claims 6 to 11.
23. A computer program product, comprising a computer program, characterized in that, The computer program is adapted to be loaded by a processor and execute the billing method according to any one of claims 1 to 5, or to execute the billing method according to any one of claims 6 to 11.